• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by JColvin

  1. Hi @tfcb, I apologize for the delay. The data lines are not 5V tolerant; they will only work reliably in the 3V to 3.6V voltage range. As for the Pmod ISNS20, it seems that the demo code that was posted on the Resource Center was an old version that still has some bugs in it making it unusable. I am working on an updated version that correctly calculates the measured milliamps and amps as well as tests for the the initial offset error (which according to the ACS722 datasheet likely has an offset voltage of somewhere in the range of +/-12 mV or +/- 0.18A with the 66mV/A typical sensitivity) that will be used to get more accurate readings. Thank you, JColvin
  2. Hi @Julia Elkouby, I apologize for the delay. I don't have express VIs that you do so I am not able to test your setup myself, but I suppose it looks okay? The folks over at the NI forum would be better able to evaluate your VI setup. Otherwise, I know that stepper motors do have diminishing returns with regards to speed since you need fast slew rates (in both directions) so that both sets of coils aren't simultaneously "running" otherwise the motor will not rotate. I wasn't able to find any specific details for your stepper motor that you are using with regards to this, but since the motor adapter board (and myRIO) are only 5V outputs and the motor itself uses 1.8 deg steps so your rotation speed will be limited, though I would expect higher than 30 rpm. Thanks, JColvin
  3. JColvin

    JTAG STM1 stopped working

    Hi @eskull, Digilent does not have this board to test for ourselves so I am not certain how the switches on the VC709 adjust and change configuration options, so I suggested the JTAG configuration as a safe option. I do not know if leaving it to be powered on via the BPI flash would change anything, though switching it to JTAG will not hurt. I suppose with your setup there is a chance that a ground loop could have occurred though Xilinx will better know what sort of potential damage could occur with this board in terms of any grounding issues. Thanks, JColvin
  4. JColvin

    JTAG STM1 stopped working

    Hi @eskull, I have sent you a PM with some more details on this issue since I think the EEPROM on the JTAG SMT1 needs reprogrammed, presuming you have set SW11 to 101. Thanks, JColvin
  5. JColvin


    Hi @AndreaD, There is a VISO; you can see it on the Pmod RS485 schematic as well as how it is generated from Vcc in Figure 1 in the Pmod RS485 reference manual. Let me know if you have any questions. Thanks, JColvin
  6. Hi @andrewkhardy, I'm not certain what the rest of your code is (in terms of viewing the result you received and the voltage conversion), but here is some example code that I used to test the analog conversion on a uC32. I would also recommend making sure that whatever you are using to supply to voltage has it's ground connected to the uC32 ground pin to create a common reference. With regards to the ADC itself, it is my understanding that the on-board ADC only runs up to 1 MSPS, though you can change some of the internal parameters detailed in this Microchip datasheet. Let me know if you have any questions. Thank you, JColvin
  7. Hi @Joyanta, I would recommend asking the NetFPGA group directly (as they are a dedicated group towards in the email group that they have set up. If you have not done so already, you can register for this on the NetFPGA Wiki here, though note that it can take a few business days before you get a response. Thank you, JColvin
  8. Hi @Ozan Gunaydin, Currently the MPLAB X project for the OpenScope MZ is not yet released; I think I have heard of some plans to release it, but do not know what the timeframe is for this. Thank you, JColvin
  9. Hi @sgrobler, I have a revA of the Screw Terminal Adapter rather than a rev B, but I am able to measure the expected voltages on either DCOUT. I wasn't able to see a difference in the schematics between Rev A and Rev B, but have asked what the change was between the two revisions. I imagine you already checked this, but in the interest of covering all of the bases, I presume you have attached the screw terminal adapter as shown in the images for it's associated reference manual? Thanks, JColvin
  10. 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
  11. Hi @Ehud Eliav, Unfortunately, we do not know of any already ported libraries for the SVF commands that you can already use. Thanks, JColvin
  12. JColvin


    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
  13. 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
  14. 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
  15. 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
  16. 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
  17. 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
  18. 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
  19. 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
  20. 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
  21. 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
  22. 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
  23. 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
  24. 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
  25. 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