• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by JColvin

  1. Hi @ub3rmike, I have sent you a PM about this. Thanks, JColvin
  2. Hi @amitceder, I don't quite know what you mean by it behaved the same prior to rebooting, but I confirmed with the design engineer who created Adept that Adept will not initialize on any UltraScale+ boards from Xilinx. Let me know if you have any questions. Thanks, JColvin
  3. Hello @amitceder, What platform are you attempting to use Adept and the JTAG HS3 with? Thanks, JColvin
  4. Hi @electronic, I have sent a you a PM about this. Thanks, JColvin
  5. Hi @amitceder, The Digilent Adept software is not able to program the Xilinx UltraScale plus board. If you want to program the UltraScale board, you will need to you Xilinx's Vivado software with the JTAG HS3. Let me know if you have any questions. Thanks, JColvin
  6. Hi @ub3rmike, I have reached out to another engineer about your question. Thanks, JColvin
  7. Hi @Ujjal, Based on the description of the YouTube video in the comment above yours here, it is only compatible with Window's systems. Thanks, JColvin
  8. Hi @Luke Abela, You would only receive that screen if you double clicked on the the MIG, which the tutorial you linked to does not instruct you to do. I just ran through the tutorial on Vivado 2018.2 and was able to generate the bitstream. Did you avoid clicking the "Run Connection Automation" on step 2.6? I was able to see the "Run Block Automation" for the mig_7series_0 block in step 4.1. Thanks, JColvin
  9. Hi @tfcb and @Diego, Had an epiphany just now and figured you were owed it now in the middle of the night rather than waiting till after the Labor Day holiday in the US. The reason the Uno isn't working is because of the required voltage translation; all of the code is working off of the 3.3V logic that the Pmod ISNS20 uses, but because the Uno uses 5V logic, this rescaling needs to be reflected in it's material as well. So any number in the code that relies on 3.3V logic being used will likely need to be scaled to 5V. I will provide an update tomorrow of how the numbers will look with this change (in general should be divide by 3.3 and multiply by 5, though that might need to be different for values that depend on specific Vrefs) and be able to formally test the changes in the office on Tuesday. Thanks, JColvin
  10. Hi @tfcb and @Diego, I have not been able to get the Pmod ISNS20 to work on an Arduino UNO; I have it set up so that I can simply move the connection wires from the Arduino UNO to a Digilent microcontroller (that operates at 3.3V for it's IO rather than 5V) and the module works correctly on the Digilent microcontroller but not the Uno. Originally, I had left the inputs on the ISNS20 floating, but attached the same ground source to both of them to help ensure no voltage potential was present, but to no avail. When I power cycle the Arduino Uno and restart the data collection, I get different values reported from the ISNS20 (and wildly different values, i.e. different by several amps) between each sample. I put delays in the code to ensure the data was not moving faster than the AVR could maintain and checked that the level shifter that I was using was operating as intended, but to no avail. I wish I had better news, but I do not know what else could be done differently to make it work correctly. Thanks, JColvin
  11. Hi @robzane, It looks like there code examples for PIC32 interrupts within that document that you linked. There are some additional interrupt materials available in the Relate Materials box on the right side of the screen here as well: https://learn.digilentinc.com/Documents/216. Thanks, JColvin
  12. Hi @Allmoz, We're not able to provide the schematics for the USB connectivity on the Basys 3, though there is a thread detailing what sort USB port would be needed here, though I personally have never been able to find a part that matches the dimensions. If some of the USB connectors do not have the traces ripped off, there is a possibility that you could solder the connector directly back onto the board, though there's no guarantee that'll work. Some of the connectors could still be okay; I have seen some boards come get returned where the user had plugged in the micro-USB cable upside down in the connector, but after carefully bending the connector back to the correct orientation (I used a small flathead screwdriver), I was able to plug a cable back in and have the board work with no issues. As for the switches, contact cleaner or compressed air would be what I would suggest to clean them. It is possible to remove the top half of the switch from the bottom half (since it's held on by four small tabs) to get easy access to the conductor to clean off the dirt or any sort of corrosion, though I don't know how easy it would be to get those tabs secured back into place (I would guess that it is not so easy). The part we specifically used for the Basys 3 is here, though apparently it's not stocked any more, but since it is a straightforward SPDT switch, any switch that has 4 mm of space between the centers of each of the through hole pins would work as a replacement. Let me know if you have any questions. Thanks, JColvin
  13. Hi @mustafasei, When you provide the different serial port options, such as the /dev/ttyACM0, as the LINX Resource Input, could you provide a screenshot of this input? My understanding is that the drop-down menu options do not contain the correct path to the serial port (or at least do not show up correctly). Thanks, JColvin
  14. Hi @bixie, I have moved your question to a more appropriate section of the forum where the Digilent engineer more familiar with WaveForms and WaveForms SDK will be able to see and respond to your question. Thank you, JColvin
  15. Hi @Zosty, I reached out to another engineer more familiar with Adept and learned that particular CPLD was likely added by mistake to the recognized device list within Adept, but (as you have found out) was never tested to confirm to work correctly like other CPLDs that are also on the list and within the same family (such as the XC2C256 or the XC2C32A). The solution at this point would be to use ISE to program that CPLD. If you are upgrading your machines/OS's, and still need to program this CPLD, I would recommend setting up a virtual machine on a separate partition to host and support ISE programming. Thank you, JColvin
  16. Hi @GrouchEng, Do you have a technical question associated your post? Otherwise, the link to the Digilent blog is located at the top of this page. Thanks, JColvin
  17. Hi @labviewkozou, I apologize for the delay. I must also admit I am a little confused; you have LINX 3.0 installed on a Windows 10 machine (and presumably LabVIEW 2014 Home Edition if you managed to connect to the target). But you say that you are getting an error when you are installing LabVIEW 2014 Home Edition? Where are you attempting to install LabVIEW? Thanks, JColvin
  18. Hi @Mats, I think you may have heard back from a different Digilent channel, but to reiterate here for other readers benefit, we will not be able to release the gerber files and other needed material for the Analog Shield. Thank you, JColvin
  19. Hi @mustafasei, I heard back and have a couple of follow-up questions since a couple of things are unclear to me. When you try alternate serial port options (such as the /dev/ttyACM0 that was found in the dmesg | grep tty command you used) in the string input, do you still receive an error from LabVIEW? Can you attach some screenshots of this? Currently, I only see the screenshot for the ASRL4 string input with the 5006 error and that you got this same error for other things, though I do not know what you attempted. Thank you, JColvin
  20. Hi @mustafasei, Unfortunately, I don't have any further advice for you, since I don't have a Raspberry Pi of my own. I'm not familiar with the visaconf.ini file, so don't have any comments on how that would work. You could try posting on that thread, though since the thread is a couple of years old I don't know the response you would get. I will reach out to another engineer to see if they have any suggestions on this, though they don't spend much time on this anymore so I don't know when they will respond. Thanks, JColvin
  21. Hello @PrasadK, You will need to use a newer version of ISE. As per this page on our store, the JTAG HS2 is only supported in ISE 13.2 and later as well as only have Xilinx Plug-in support from ISE 12.1 and later. Thank you, JColvin
  22. Hello @mustafasei, It looks like from your screenshot you did not create a string constant but are still using the VISA Resources drop-down since the correct USB device for the Arduino will not appear on the list. I imagine you are using a cdc-acm USB serial device (such as the Arduino Uno or Leonardo) so there was a bug in VISA that got an update though I don't know if it was ever formally rolled out, but this LabVIEW MakerHub thread discusses this. You might also use "dmesg | grep tty" as a way to find out the attached devices rather than listing everything. Thanks, JColvinn
  23. Hi @Mats, The co-worker in question is out of the office, so unfortunately I do not expect to hear back from them until next week. Thanks, JColvin
  24. Hi @PhilG, 1. That is accurate; the aggregate input is divided based on the number of channels that are being read, so if you read all 8 channels, the sample rate ends up being 62.5 kS/s per channel (I think you missed a decimal point there). However, it is a bit more nuanced as the embedded ADC within the on-board MZ chip limits how channels are read. What I mean by this is if you choose to read only channels 3 and 7, the sample rate will be limited to 71.43 kS/s because the embedded ADC (by internal design that isn't changeable by a register setting) will read channels 1 through the last channel enabled (in this case channel 7) even if the in-between channels are not enabled. So if you want to read multiple channels, make sure they are on the lower analog channel numbers to minimize the impact to sample rate. A single channel enabled (even if it is channel 7) will still keep a 500 kS/s sample rate though. 2. It should have a max logging rate of 500 kS/s; I have corrected that bit of detail on the OpenLogger Resource Center, let me know if you see that elsewhere in the documentation. Originally, it was only going to be 400 kS/s but the firmware was streamlined to make 500 kS/s achievable. 3. Well, they aren't powered by Digital to Analog chips directly (it's done through through discrete components), which to be fair is all DAC's are made out of anyway. But I think the idea that the they have their own op-amps to produce the DC outputs (IC8 on page 6 of the schematic, https://reference.digilentinc.com/_media/reference/instrumentation/openlogger/openlogger_sch.pdf) makes it fair to call them power supplies. They are not beefy power supply lines, but do provide more current (50 mA) than a typical digital-to-analog converter (at least as far as I know). Let me know if you have any questions about this. Thanks, JColvin
  25. Hi @Sbacica, I took a look at the Digilent Digital WaveForms example (Digilent_WaveForms_Digital (DIG).vi), and when using the Analog Discovery 2 it is correctly providing a logic high voltage of 3.3V as verified by a multimeter and an LED. I think the pins might be tristated when the Analog Discovery 2 is initialized and the outputs aren't configured, but I don't know for certain. Thanks, JColvin