JColvin

Administrators
  • Content Count

    2937
  • Joined

  • Last visited

  • Days Won

    87

Everything posted by JColvin

  1. JColvin

    Pmod DA3 clocking

    Hi @Ahmed Alfadhel, "According to the manual, it must only be 0 when ~CS is 1" -- this is incorrect. As you directly highlighted in the image you attached: The timing diagram instead shows the situation presented in the previous sentence that discusses pulsing the LDAC rather than holding it low. Thanks, JColvin
  2. Hi @Denci, It's hard to say from your setup for sure; the main reason for this is that a rat trap snapping sound does not last very long (presuming it's about the same length as a snap of your fingers, this thread shows it might only last for about 5 milliseconds including the aftershocks), so during your 10 millisecond delay that you have in your main, you can very easily miss the snap happening. I presume the demo that was posted on our website presume a more continuous sound would be used so the implemented delay could be still be used and have the board be verified as working. Since the ADC runs at 1 MSPS, you can likely reduce the delay to 1 or 2 ms and hopefully get a cleaner result, though you may have to also increase your SPI clock frequency from 1 MHz to the stated maximum of 20 MHz (as per the ADC datasheet) to get this result. Let me know if you have any more questions. Thanks, JColvin
  3. Hi @RussGlover, I apologize for the delay; the details you are looking are as follows: TCK - ADBUS0 TDI - ADBUS1 TDO - ADBUS2 TMS - ADBUS3 OEJTAG - ADBUS7 OESRSTN - ACBUS4 Let me know if you have any more questions. Thanks, JColvin
  4. As a bit of further clarification, you would request any licenses from Xilinx, though it is my understanding that all of the Vivado WebPACK versions since 2016.4 or so are license free. I know that Digilent used to sell the original Arty board (now called the Arty A7) with a voucher for the Vivado Design Edition, but that was discontinued a few years ago (around the same time when Xilinx changed their own licensing policy and what was included in each edition). Thanks, JColvin
  5. Hi @Peggy, It should be as far as I can tell from my end, based on the screenshots I have attached. I was able to connect the SD card and log to it. I did have to close out of the GUI to disconnect and then reconnect to the OpenLogger before it showed that the SD card was available in the "Log to" dropdown box since it didn't dynamically update (though hot plugging is okay to do with OpenLogger). However, what I did learn (a bit unexpectedly to be honest) is that the data is sent over and logged in a binary format and would need to be parsed before it is readily readable. I know that a logging utility is being worked on and will be incorporated into the Digilent agent so that the data can be readily converted into a log file without needing to install anything else, though I do not know when this will be completed. Let me know if you have any questions. Thanks, JColvin
  6. Hi @Peggy, I asked some of the other engineers more familiar with OpenLogger and I think the problem you are running into is that the OpenLogger is only designed to work with SD cards that set up as a FAT32 (as opposed to NTFS which the larger cards you are using are probably formatted as). You will need to use a smaller SD card (32 GB or less) or partition one of the larger drives and re-format it as FAT32 in order for it to work correctly. Let me know if you have any questions about this. Thank you, JColvin
  7. Hi @oreo, I'm not immediately certain what the root cause of this might be so I have a few questions for you: - Are you an administrator or at least have appropriate permissions to install new things on the computers you referred to? - Were the other two computers you mentioned (an 1803 version and a second 1809 version) also Windows 10 Education edition computers? - To confirm, you were downloading the latest WaveForms and Adept 2 from their respective resource centers here and here? (WaveForms is on version 3.9.1 and the Adept System is on version 2.19.2) - Have you installed either of these software programs before or are these new installations to the computer? If you have installed them before, is WaveForms, Adept, or one of Digilent's instrumentation devices (such as an Analog Discovery 2) connected to the computer while you are installing the new version? - You might also try restarting the computer and re-downloading a fresh version WaveForms/Adept installer to see if that helps (since the "turn it off, turn it back on again" method works more often then it should) - If the above doesn't work, can you also try having Adept log it's installation process to an empty text document? You can do this as follows: If you have an e: drive (or something similar) create an empty text document named "adept_install_log.txt" (without the quotation marks in file name) Run the following command from the command line (it assumes that the installer executable for Adept is also located at same location as the empty text file, in this example this is at the root of the e: drive) "digilent.adept.system_v2.19.2.exe /LogFile="E:\adept_install_log.txt"" Be sure to use quotes around the file name that is specified for the log file. My understanding (based on this thread where the user also got the same error when installing Adept) is that the error doesn't say more than 3 driver packages were not able to be installed, so hopefully this will give us some more details. Thank you, JColvin
  8. Hi @Brent Gardner, Thank you for pointing this out; we will correct the image and get the appropriate resources updated. Thanks, JColvin
  9. Hi @Ali Asim, Unfortunately, none of us here at Digilent have used the Pynq Z1 with MATLAB's Simulink. You can view the list of supported devices for this on the MathWorks website here. Thanks, JColvin
  10. Hi @Peggy, The only thing I can do to reproduce this is when I do not have an SD card inserted into the OpenLogger itself as opposed to in a computer slot. Can you confirm if you have a functional micro SD card plugged into the OpenLogger? Thank you, JColvin
  11. Hi @KL-ROBOLUV, In addition to what @vicentiu said, I think one of the biggest benefit of the Analog Discovery 2 compared to a DMM with regards to this situation is that the Analog Discovery 2 provides a look of how your robot responds over time (either long or short) to inputs, such as starting or stopping motors, whereas a DMM will only give you a single point in time. This can be a nice benefit to see how fast your robot responds or be able to see how it is reacting if you view unexpected behavior. Let us know if you have any further questions. Thanks, JColvin
  12. Hi @Younammar, If you are measuring an external circuit, there is not a direct method to measure the current flowing through a different board built into the Analog Discovery 2 or WaveForms. In general, you would need to some additional setup like it is shown in this tutorial here. I believe the python script you are referencing takes advantage of a current sensing IC that is already built into the Analog Discovery 2 so it will not be of use in this case. Let me know if you have any questions. Thank you, JColvin
  13. Hi @6o{pb, The Analog Discovery 2 can certainly work with the 10 MS/s to get the data with a PWM running at a 20 kHz rate. What I do not know is how the MATLAB Data Acquisition Toolbox implements these functions as MathWorks created all of the MATLAB functionality and compatibility with the Analog Discovery 2. Let me know if you have any more questions. Thank you, JColvin
  14. Hi @Ahmed Alfadhel, The DDR3 chip on the Arty A7 (datasheet link for the MT41K128M16) is designed to only operate at either 1.35V or 1.5V and as per the Arty A7 schematic the 1.35V configuration was chosen (you would have to change resistors around to adjust this configuration as mentioned on page 11) and is what our .prj file (github link) for the Arty A7 to configure the DDR3 and MIG IP uses as well. Going over the voltage input limit for the supply and IO supply voltages are limited to 1.45V (as per Table 41 on page 52 of the datasheet I linked) and if those maximum limits are exceeded, the input levels will be governed by DDR3 specifications (as per Note 5 on page 52), which limit the maximum supply voltages to 1.575V (with respect to Vss, as per Table 7 on page 26). Either way, using a clock signal that would be fed into the DDR3 chip that will go up to 3.3V will wildly overshoot the acceptable input levels (limitations detailed on page 57 in Table 46 of the datasheet, generally limited to 0.4V for a very small amount of time), effectively frying that pin on the DDR3 chip and possibly more. I would recommend carefully following voltage limitations of both the DDR3 chip and the Artix 7 if you are going to choose to configure and constrain the FPGA pins yourself. Thanks, JColvin
  15. Hi @eskull, I heard back from one of our design engineers and learned that the IC's present on both the SMT1 and SMT2 are powered from the 3.3V and VREF pins and not VBUS (which isn't connected to anything on the module) so using a USB isolator that does not provide 5V power will be fine. Thanks, JColvin
  16. Hi @byro3227, I apologize for the delay. I'm not able to open your VI itself since it was created in a later version than I have. I looked into the WaveForms SDK reference manual (part of the WaveForms download and what the AD2 VI calls) and don't see anything that would directly limit this. From my understanding This thread may also be of some help to you if you have not read it already. I'm sorry I could not be of more help. Thank you, JColvin
  17. 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
  18. 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
  19. 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
  20. 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
  21. JColvin

    PMODRS485

    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
  22. 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
  23. 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
  24. 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
  25. 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