Jump to content

JColvin

Administrators
  • Posts

    6,608
  • Joined

  • Last visited

Everything posted by JColvin

  1. Hi @xthunderheartx, I would likely recommend looking into the WaveForms SDK examples (there are a couple of DigitalOut_Custom examples) Otherwise, there are a number of threads that you might find helpful here: Let me know if you have any questions. Thanks, JColvin
  2. Hi @BMiller, I received confirmation that the 2023.1 OOB material, both hardware and sw branches, is not yet ready; once it is completed (I do not know the timeframe on this) it will move out of the /next branch and into /master. You are also correct that the patch isn't needed in 2022.x onwards; Digilent will remove that note from the appropriate readme file. However, regardless of the version of the tool suite used, the OOB demo uses the HDMI IP which needs its own license, as noted in the Reference Manual, https://digilent.com/reference/programmable-logic/genesys-zu/reference-manual#software_support. I verified that the exact same error comes up on my license free machine for 2020.1 which the OOB material is based on: Unfortunately, there is not a real workaround to this outside of removing the licensed IPs from the design and then regenerating the bitstream. It might be possible (I have not tried nor investigated the following) to use some sort of DVI implementation instead, but you would not be able to get the 'full' HDMI 1.4b/2.0. Thanks, JColvin
  3. Hi @KatharinaSt, Once you set up a triggered waveform by changing to Independent or synchronized as @jruff indicated, you can then create the biphasic square wave by setting the run time to be equal to the period of your square wave. The length in-between each 'pulse' can then be adjusted by changing the Wait time. If you only want it to occur a set number of times, change the Repeat option off of Infinite to whatever value you need. Let me know if you have any questions. Thanks, JColvin
  4. Hi @nics17, You are right that only one COM port should be associated with the Arty Z7-20. I believe you should be able to fix it (presuming you are on Windows) by going into the Windows Device Manager, opening the Universal Serial Bus controllers dropdown, and going down to USB Serial Converter A. Go into its Properties, go to the Advanced tab, and uncheck Load VCP. This should remove the virtual COM port association with that particular sector (I don't know what the actual vernacular is offhand) from the FTDI chip, and leave you with just one working COM port (on USB Serial Converter B), and the ability to configure the board over the PROG/UART micro USB port. Let me know if this doesn't resolve the issue and we can troubleshoot some more. Thanks, JColvin
  5. Hi @BMiller, I tried building the 5EV OOB for 2023.1 as well on my machine (I don't have any licenses) and got the same error as well. Admittedly, I had forgotten to apply the patch that was mentioned at the bottom of the readme (https://github.com/Digilent/Genesys-ZU-HW/tree/5ev/oob/next) before generating any IPs, but regardless I've reached out for some additional insight into this. Thanks, JColvin
  6. Hello, I don't have LabVIEW installed, but by default the Analog Discovery 3 works on repeated acquisitions, which will result in a gap in the data; you can reduce between repeated triggered acquisitions in the WaveForms application or SDK by enabling Device Buffering, but I don't think this is directly supported within the LabVIEW VI set. You would likely be wanting to use one of the Record mode examples; there are some additional threads on this topic here and here. Let me know if you have any questions. Thanks, JColvin
  7. Hi @venkateshj, Digilent doesn't have a device with a Zynq 7030 on it, so I don't know how your particular board is set up in terms of its connections, but generically speaking you can follow something like Digilent's guide here, https://digilent.com/reference/programmable-logic/guides/getting-started-with-ipi, which sets up some simple GPIO access from the PL side and also prints via one of the UART ports, which in the case of Digilent's boards, is accessible over a generic serial monitor on the host computer. Otherwise, if you are using some sort of external UART through generically available IO pins (you'll still need some sort of USB controller to receive the signals and interface with the computer for you), these two posts (link1, link2) may be of interest to you. Thanks, JColvin Edit Dec 15th 2023: For clarity, the initial guide linked really only works if you have a Zynq board with the PS USBUART routed to a USB controller (along with heavily benefiting from having a Zynq IP preset to work with). I do not know what resources your particular Zynq 7030 comes with or how it is laid out. The external UART bits could still work through MIO or EMIO depending on the layout and Zynq block configuration.
  8. Hi @nakajii, I have moved your question to a more appropriate section of the Forum. I don't know your exact setup, but the Logger instrument by default uses the Low gain / full range of the Analog inputs, so for more accurate measurements you would need to make sure you using the 5 V range (adjustable through the "Gear More" dropdown next to the update rate). I presume you already connected the grounds between the devices for good measure. Other potential sources of error that I could think of would be that the BNC probes are not set to 1x attenuation, or that you are using a BNC probe on the Wavegen output rather than just a BNC passthrough cable that has no additional circuitry. Let me know if I have misunderstood your setup. Thanks, JColvin
  9. Hi @fepc3, Where do you see that the JTAG-SMT2-NC is discontinued? As far as I am aware, it is in production and available: https://digilent.com/shop/jtag-smt2-nc-surface-mount-programming-module/. The only alternates I am aware of for the JTAG-SMT2 would be 410-251 (https://digilent.com/shop/jtag-smt2-surface-mount-programming-module/) which already has the USB connector on it, or maybe you are thinking of the MSL3 level packaging option? Regardless, no 'variant' of the JTAG-SMT2-NC has any differences in the boards that they support, https://digilent.com/reference/programmers/jtag-smt2-nc/reference-manual#supported_target_devices. Let me know if you have any questions. Thanks, JColvin
  10. Hi @Matty333, I've moved your question to a more appropriate section of the Forum. This would not be very feasible to do with the Analog Discovery 2/3 with the BNC Adapter, mostly because the Impedance Analyzer instrument within WaveForms relies on using the differential analog inputs of the Analog Discovery device, but BNC cables are single-ended, ultimately resulting in you not having enough analog inputs while using the BNC adapter to correctly set up the needed topology. You 'could' forgo the BNC adapter and potentially create a setup with the MTE cables; it will be a "little" janky and not getting to use the higher bandwidth of the BNC, but it would work (depending on how accurate of an impedance measurement you are wanting to get from the coaxial cable; impedance measurements work best when your reference resistance is highly accurate and already close to the unknown impedance value). The Analog Discovery Pro ADP3450, https://digilent.com/reference/test-and-measurement/analog-discovery-pro-3x50/start, does have enough analog inputs to correctly support the topology needed for the Impedance Analyzer (though you might need various t-adapters for the BNC connections presuming I understand your setup), but that costs more than the AD2 already on your desk. Let me know if you have any questions. Thanks, JColvin
  11. Hi @steffoe, I do not think this feasible to change on the Cmod A7. You would have to somehow cut the trace supplying power to only pin 6 on the LTC3569 (since right now it is in the Vrt = SVin configuration), get an external clock signal to the MODE pin, and then select the correct RT resistance as explained in the Applications Information section of the LTC3569 datasheet: https://www.analog.com/media/en/technical-documentation/data-sheets/3569fe.pdf. It might be technically possible to modify the Cmod A7 in its already limited space to support this, but I would not attempt such a modification. Let me know if you have any questions. Thanks, JColvin
  12. Hi @Asher Webb, I don't have exact component details to provide (when I'm trying to look up the specific parts, I'm just seeing "connector header, 1x3, male, straight" or "terminal block, 1x2 position, screw terminal") which doesn't help for looking up datasheets. However, if we use this datasheet as a general representation of the 1x3 100 mil spaced header, https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/937/Female_Headers.100_DS.pdf, it states a maximum current of 3 Amps. Screw terminals of course tend to have higher current ratings due to their increased size. I don't know what kind of cable you'll be using to connect from the 1x3 100 mil header, but I would anticipate that if you're using a wire style similar to UL1015 that you aren't going to have a drastically better current or wattage rating (this detail isn't readily specified from what I can see, https://iq.ul.com/awm/stylepage.aspx?style=1015). Regardless, the question is if when the 4 servo motors are drawing their start/stall current of 2.5 A for a brief period of time, will the 'weak point' of the system (i.e. the jumper block that selects whether you are using external power or host board power for powering the servo motors) be able to handle up to 10 A for some small amount of time? I don't have a definitive answer for this, but my gut says that as long as you aren't deliberately stalling them (thus giving any materials time to dissipate any accumulated thermal energy), I think you could be okay. To be clear, I'm presuming this based on the fact that the Pmod CON3 has four different outlets and that Digilent would have tested running four different motors simultaneously when this module was designed way back in 2005, though the specifics on that have been lost to time and I don't have 4 servo motors nor a 10 A supply to try this out myself. Anecdotally, you can find a number of tutorials showing people attaching their external power supply to solderless breadboard rails which aren't rated for high current or wattage, so pragmatically speaking you should be okay (again making sure you aren't stalling the motors). Let me know if you have any questions. Thanks, JColvin
  13. Hi @cmartema, I apologize for the long delay. In terms of ruling out easy possibilities since you didn't directly mention it, did you double check your SD card contents to make sure it has an image designed for the Pynq-Z1 (latest image available pynq.io here, http://www.pynq.io/board.html) ? Your jumper settings otherwise look correct. I'm guessing the SD cards are all formatted as FAT32. If you power off the board and switch the jumper JP4 (next to the USB Host) from SD to QSPI, does the board power up with an out-of-box material with various LEDs flashing? (This of course won't help if you have overwritten the flash memory on the device before). Is the Pynq Z1 detected by your host OS? For Windows, it should show up in the Device Manger similar to this post. For Linux, you can use dmesg and ideally see information similar to this post here. Let me know what you learn. Thanks, JColvin
  14. JColvin

    pmod PIR and Pmod TMP2

    Hi @user1, I'm not sure what your definition of good is, but the Pmod TMP2 should be a reasonable project; it powers up and starts converting temperature by default with the first two registers of embedded ADT7420 containing the two's compliment data. The catch is that Digilent doesn't have a reference example for the Pmod TMP2. The Pmod PIR does have an existing example and is even easier to work with; you simply check the status of one of its pins to see if motion has been detected or not and can adjust the sensitivity with an on-board potentiometer. I suppose the catch with this module is that it takes 30 seconds of waiting before the on-board chips are ready and operational and I haven't personally used this Pmod to be able to vouch for its efficacy / range(cone) of vision usability. I seem to recall it working reasonably well when I helped product test it for the different "shell" shields over the sensor many years ago. Let me know if you have any questions. Thanks, JColvin
  15. Hello, Digilent does not typically provide netlists for our products. You can find a BSDL for the Spartan 7 25 chips in a couple of places that AMD provides as per this thread: https://support.xilinx.com/s/question/0D54U00007hXkHRSA0/where-to-find-bsdl-files-for-xc7s25-?language=en_US. Thanks, JColvin
  16. Hi @Qmellory, I have sent you a PM. Thanks, JColvin
  17. The pins are 0.64 mm square as cnegrea correctly indicated. You can find some more details in this thread: I'll work on getting this detail into the Cmod A7 Resource Center for easier future reference. Thanks, JColvin
  18. Hi @hiroki, I have sent you a PM. Thanks, JColvin
  19. JColvin

    ARTY Z7-20

    Hi @Joek, In general, Digilent does not provide this sort of layout material for our boards. If you have specific passives already in mind that you are wanting to switch out, let me know and I might be able to provide you with the information. Thanks, JColvin
  20. Hi @magnitudephase, This post may be of interest to you: From my understanding, the ADP3450 will always be at, or beyond, feature parity with the Analog Discovery 3 due to the larger Zynq device present within the ADP3450. There is not any hardware features unique to the AD3 that the ADP3450 does not have access to or won't be able to implement within its own FPGA hardware (unless you count the USB C connector on the AD3, but I would not count it as it operates at USB 2.0 speeds). Let me know if you have any questions. Thanks, JColvin P.S. Technically, the FIR filter was added to the ADP3x50 and device loopback in the 3.19.30 beta version, with IIR filter added even earlier in 3.19.21.
  21. Hi @craigec, I have sent you a PM. Thanks, JColvin
  22. Hi @agentsmith, I'm not a python expert (as in minimal experience) and the WaveForms developer is out of office, but I was able to verify the behavior you are seeing with your existing code. However, when I attempted to replicate this behavior with the built in AnalogIn_Record.py which also generates a sine wave, records the data, and spits out a pyplot graph, I was not able to reproduce this behavior when passing a 0 or a 1 to FDwfAnalogInRecordLengthSet. Best that I could tell from my limited experience is that the built-in example used numpy.fromiter to create the array rather than concatenate like you used, though I don't know why this made all the difference. Regardless, I'll make a request to have the documentation be updated for clarity on the correct value to pass for infinite record length. I hope this helps. Thanks, JColvin
  23. Documenting that this was responded to in the other post here: .
  24. Hi @Anthocyanina, Thank you for the feedback; I believe Attila is out of office at the moment to be give any further feedback, so I wanted to clarify that Digilent has seen the feedback. With regards to displaying multiple traces on the same plot within Impedance, you can run an acquisition, click the green + button to "Add Trace as Reference", then re-set up your circuit to get different data and have the existing reference trace persist on the screen. Thanks, JColvin
  25. Hi @Testee, The most up to date WaveForms SDK documentation (and functions referenced) is included within the WaveForms installation, most easily accessible from within the GUI in the Welcome tab which will open up the file location on your computer. The two functions are then listed out (at least time of writing for the documentation included in 3.21.16 beta) on page 133. iNAK is defined as the "NAK index + 1. Negative values indicated error", with the NAK index better explained in the FDwfDigitalI2CWriteRead function on page 132. The online material you referenced is not the most up to date; I will work on putting a more clear disclaimer about this on the Reference site as well as a date stamp of some kind. Let me know if you have any questions. Thanks, JColvin
×
×
  • Create New...