• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by JColvin

  1. Hi @sgrobler, I tested with the latest available firmware (0.1691.0) and this is working for me. I measured DCOUT1 (set to 1.324 V on the red wire) and DCOUT2 (set to -2.750 V on the green wire) and referenced a digital ground (black wire) and found them to be accurate within a few millivolts. I was able to measure the changes with WFL either streaming or not streaming. Are you measuring it in a similar way? What firmware are you using? Thanks, JColvin
  2. Hi @Julia Elkouby, I don't have LabVIEW 2017 so I am unable to open your VI; could you attach a screenshot/output of the block diagram? Additionally, what stepper motor are you using? Thanks, JColvin
  3. Hi @sgrobler, I have asked another engineer more experienced with WFL about your question; I also confirmed with them today that they are looking into your other question as well; they confirmed the resolution error and I believe they have found the root cause and are looking into it. Thanks, JColvin
  4. Hi @ebattaglia42, What operating system are you currently on? If you are Windows, can you attach a picture of what is shown in the Windows Device Manager and what you see in the WaveForms Device Manager (it should pop up when you initially connect the EE Board). The other thing I would suggest to try would be to use a different USB cable (make sure it's not just for charging only) and/or USB port on your computer as that is another source of error that is easy to check. Thank you, JColvin
  5. Hi @GCL, So I am properly understanding what you are wanting to do, you are wanting a way to trigger your pattern generator output (in this case a pulse) based on one of the waveform generators? From what can see in the trigger options on the pattern generator is that you can set the trigger to be based on Wavegen 1 or 2 and with the little gear icon next to it set the trigger condition to be rising, falling, or either, but I'm suspecting this isn't quite what you are looking for. It sounds like you already have the two Waveform Generators synchronized (via the dropdown channel next to the channel enable dropdown), is this accurate? Thanks, JColvin
  6. Hi @opethmc, Powering it from a battery should definitely help. They mentioned to me that when they use a bench power supply, they use a 12V lead acid battery in parallel with it and set the bench supply to output 13.7V which effectively float charges the battery. This way the battery acts like a very large capacitor unless the continuous current draw is more than the continuous output current that the bench supply can provide. Let me know if you have any questions. Thanks, JColvin
  7. JColvin

    please help me

    Hi @Asmaa_as, As I implied in my previous post we have not tried LabVIEW 2017 (since the last update to the WaveForms VI was in 2016), but the look of how the WaveForms generator connected to the oscilloscope is described in steps 3 through 6. It is for the Analog Discovery 2, but the LabVIEW side of things will be exactly the same for the Electronics Explorer board. The oscilloscope outputs and waveforms generator outputs are labeled on the electronics explorer board. Let me know if you have any questions. Thanks, JColvin
  8. Hi @Fez1234, I have moved your thread to a different section of the Forum since Digilent does not have any Lattice based FPGA boards, so we will not be able to provide specific help to you on this; as noted on this thread, our boards use Xilinx FPGAs. Otherwise, if you are starting out I would recommend taking a look at fpga4fun and asic-world as some good resources for getting started with FPGAs and the associated HDL such as Verilog. Thanks, JColvin
  9. Hi @Dejdys, The noise band in WaveForms is actually the semi-transparent darker yellow band that you see in the background (more details on this thread). As for why the signals are different, my guess is that the sample rates between the two software are different so different data is being collected. What sample rates are you using for each setup (WaveForms and LabVIEW)? Thanks, JColvin
  10. Hi @sgrobler, I have asked another engineer more familiar with WaveFormsLive to see if there is some limitation on that end regarding this. You are correct though that the resolution achievable with the embedded ADC (taking into account the front end gain of 0.1392) is 329 uV per LSB. Thanks, JColvin
  11. Hi @dougBe38, Could you attach the code that you are using to read the Pmod TC1? Additionally, are you using any sort of voltage translator while working with the Pmod TC1? The embedded chip on the Pmod TC1 only accepts voltages from 3V to 3.6V and from my understanding the Arduino MEGA only uses 5V logic, so that would change the operating specifications. Thank you, JColvin
  12. Hi @opethmc, I heard back from the other engineer. They let me know that the following: Let me know if you have any questions. Thanks, JColvin
  13. Hi @aeon20, To add on to what @jpeyron said, the cable drivers are effectively (as per page 11 in this document you linked) proprietary device drivers that allow the design software (i.e. Vivado Hardware Manager or Xilinx ISE iMPACT) to communicate with a Xilinx USB cable. Digilent boards do not use a Xilinx USB cable (such as a Platform Cable II) directly, but has the equivalent circuitry on the board that also need these device drivers. The Digilent Runtime and Utilities are part of Adept (available for download on the right hand side of the Adept 2 Resource Center and listed as "Runtime" and "Utilities", respectively) and from my understanding help facilitate the Xilinx software communicate with Digilent boards. Thank you, JColvin
  14. Hi @Sduru, We do not have any formal documentation regarding the ESD & Safety protections for the Zybo Z7 boards. In the end the best practice would be to use appropriate protection with grounding mats and wrist bands to ensure no unitentional shock is delivered to the board. The board does have over-voltage protection up to 20V on the power inputs as well as Pmod JE which has series protection resistors, but there is no specific circuitry to protect the board from stray ESD. On anecdotal note, we have touched actively operating boards without experiencing any detriment to performance or otherwise, but if you know that you will be working in an environment where ESD will be an issue, I would recommend erring on the side of caution. Let me know if you have any other questions. Thank you, JColvin
  15. Hi @Cherrih, Unfortunately, we do not have any experience using the Xilinx System Generator so we do not have any board files for it; I would suggest to reach out to Xilinx support here. Thank you, JColvin
  16. Hi @opethmc, I have asked another engineer about this and am waiting to hear back from them. Thank you for your patience, JColvin
  17. Hi @Deskarano, The only other thing that Jon and I can reasonably think of to try (to see if we can get different results to hopefully point to a root cause) would be to load the program (such as the button and switch project from earlier in the thread) onto the flash memory (a guide for the Arty is available here) and then power the board with an external power supply and see if the FPGA is still hot to the touch (since viewing it in Vivado will end up using the cable and USB connection again). If you happen to have a JTAG HS2 or something similar we can try that as well (since we can also view the temperature profile that way), but it's fine if you do not have that. Thank you, JColvin
  18. Hello @lahane123, Unfortunately, those of here on the Digilent forum do not have the experience with ASP.NET so we will not be able to answer your questions. I would recommend asking your questions on a forum more suited for these types of questions such as stackoverflow. Thank you, JColvin
  19. JColvin

    please help me

    Hi @Asmaa_as, Yes, you can post back on this thread if you have a question. Please note though that the toolkit that Jon linked to (I believe) and LabForms here is only working with LabVIEW 2014 through 2016. I've personally only tested and confirmed that it works correctly with LabVIEW 2014 though. Thanks, JColvin
  20. Hi @arlene703, Could you attach a picture of your physical setup? The only thing I was able to find that closely replicated your setup was that the WaveForm generator (yellow wire) was connected to Oscilloscope channel 2 (the blue wire) rather than Oscilloscope channel 1 (orange wire). Let me know if you have any more questions. Thanks, JColvin
  21. Hi @Deskarano, Thank you for the information; the voltage all look pretty good to me as well aside from the 5V. How are you powering your board? If you are powering it via USB (direct to PC or USB hub?), could you test that voltage? You can access it by measuring between the underside of J13 (the regulator vs USB power jumper) and J11 (an unloaded single pin next to the Ethernet port); this value should be pretty close to 5V (mine is 4.98V). Also, did you get the opportunity to try a different USB cable or computer (to see if that affects power delivery)? Thanks, JColvin
  22. Hi @opethmc, Can you attach a picture of the setup that you are using so that we can better understand your configuration? I presume also that you are keeping PWM pulse width within the parameters described in this section of the Reference Manual here? Thank you, JColvin
  23. Hi @Deskarano, I apologize for the delay; I thought I had sent this off, but apparently not. In the meantime I relooked at this and realized that we inquired about capacitors that are for a newer revision of the Arty, rather than the Rev C board. The newer revisions have some additional protection and capacitors for the DDR memory, so a lot of the numbering system was shifted around, while the board between revisions functionally remained the same. The correct schematic for the Arty Rev C is available here: https://reference.digilentinc.com/_media/reference/programmable-logic/arty/arty_sch.pdf. With that, here are the correct capacitors that line up with the voltage rails we were intending to have you measure: C143 (should be 5V): C64 (should be 0.95V): C162 (should be DDR 1.35V): C159 (should be 1.8V): C152 (should be 3.3V): I have attached a picture for your convenience showing the location of C143, C162, C159, and C152. C64 is on the back of the Arty underneath the letter 'N' in the "Xilinx" silkscreen label. I apologize for the confusion and let me know what you find. Thanks, JColvin
  24. Hi @Nianyu Jiang, Not quite; the mux selects external feedback resistor used. The programmable gain (1x or 5x) is controlled by bit D8 in the Control register (address 0x80) within the embedded AD5933. Similarly, the output voltage range (whether 2V, 1V, 400mV, or 200mV peak-to-peak) is also controlled by bits D10 and D9 in the same Control register address. Can you also link to the paper you saw that talks about expanding the number of electrodes? I'm having difficulty finding it. Let me know if you have any further questions. Thanks, JColvin
  25. Hi @contraption, You'll actually be in SPI Mode 1 (clock idles low and the data is sampled on the falling edge of the clock) since that's what the IC for the DA2 needs. This is what I used on the ICSP header for an Arduino Uno (I don't have a Leonardo available). Let me know if you have any questions. Thanks, JColvin