JColvin

Administrators
  • Content Count

    2937
  • Joined

  • Last visited

  • Days Won

    87

Everything posted by JColvin

  1. Hi @enriqeat, Presuming you are not using the same physical R1 in both circuits, the short answer is that you can run both circuits at the same time for your particular setup*. If you attempted to have the same physical R1, you will have D2 on all the time and D1 on some of the time, and a short whenever JE2 is set high (so don't set it up like I show in the attached picture). Two independent circuits will work in this situation though. As for why the circuit on the right (VCC going to JE2) works, this is because when JE2 is set as an output logic low (effectively ground with the CMOS logic), there is enough voltage potential from JE6 (VCC) to the grounded JE2 for current to flow through the LED, even though JE2 is technically an output. * As a caveat to consider though, the set-up on the right (with JE2 effectively acting as the "gatekeeper" to whether or not current flows) is not recommended as good hardware practice. The reason for this is because when JE2 is set to output logic high, what you are counting on is that the logic high voltage it provides matches VCC so there is no voltage potential between the two points and consequently no currently flow. If there was some difference in voltage, current would flow and damage one of those points (either the VCC rail or the JE2 output). The reason this works a bit better for your setup is because you have an LED which will not allow current to pass through unless the voltage threshold is met (usually around 0.7V), so with the combination of this and the over-voltage protection on these pins and on the Zybo board (I'm presuming you are using the original Zybo rather than one of the Zybo Z7's, though this should still apply on port JE in either case), you should not have any differences in voltages to be worried about. I can also confirm that I ran both circuits (separate circuits) at the same time without any issue. Let me know if you have any questions. Thanks, JColvin
  2. Hi @Ehud Eliav, Unfortunately, we do not know of any already ported libraries for the SVF commands that you can already use. Thanks, JColvin
  3. JColvin

    sandor

    Hi @Sandor, Presuming you are referring to the Ethernet LAN (as opposed to just communicating with the board over USB) I believe we only have the Max32 with the Network Shield that is readily accessible through LabVIEW with the LINX add-on. If you are just wanting to communicate with the board and get the data you are looking for (turning the logging on and off, a time stamp, etc), you could use any of the Digilent supported devices with LINX as listed here. Thanks, JColvin
  4. Hi @Ted, Unfortunately, we do not have a 3D model for the Zybo Z7-20 board (or the -10 variant). We can take some caliper measurements for you if let us know what specific dimensions you need though. Thanks, JColvin
  5. Hi @richieHH, I've moved your thread (but also left the link in the new users introduction area) to the Scopes and Instruments section of the forum so that you can hopefully get some more specific feedback from those users. I personally haven't heard of any Sigrok integration for the Analog Discovery though. I'm clearly a Digilent employee so take my feedback with a grain of salt, but I like to think that one of the main reasons people appreciate the WaveForms software is that they get to talk directly with the developer of the WaveForms software who provides frequent updates based on user feedback and requests (as seen here: https://forum.digilentinc.com/topic/8908-waveforms-beta-download/) Thanks, JColvin
  6. JColvin

    please help me

    Hi @Asmaa_as, The steps can be found at this Instructable here: https://www.instructables.com/id/Analog-Discovery-2-USB-Oscilloscope-LabVIEW2016-Up/. Thanks, JColvin
  7. 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
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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
  16. 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
  17. 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
  18. 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
  19. 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
  20. 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
  21. 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
  22. Hi @opethmc, I have asked another engineer about this and am waiting to hear back from them. Thank you for your patience, JColvin
  23. 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
  24. 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
  25. 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