JColvin

Hi @otherguy, You're correct in that it would be ignoring any reactance/reflections from the other wire as it is unconnected/not under load. I suppose in theory that the ADP3450 with its 4 analog inputs and pair of analog outputs would, at least on paper, be able to properly do impedance analysis on a twisted cable pair, but right now the Impedance Analyzer tool within WaveForms does not support it (WaveForms SDK would not be of any help either). The WaveForms developer is out of office this week, but I will ask them when they get back about the feasibility of adding this sort of feature. Thanks, JColvin

Hi @Aidanw, Digilent doesn't offer repair services for our products; this is mostly because the cost of getting a product shipped, evaluated, repaired, retested, and shipped back usually ends up costing more than just sending a new board, though I'm not sure if that line is crossed with the Genesys ZU board. If the board is outside of our warranty (https://digilent.com/shop/shipping-returns/#warranty), we will try to help offer some troubleshooting and insight as to what particular component might be malfunctioning with our boards here on the Forum though. I haven't looked too much at the ZCU102 to be able offer an extensive list of the differences between the boards, though I can see that the ZCU102 uses a 9EG which has quite a bit more resources than either the Genesys ZU 3EG or 5EV; higher speed grade, more I/O, logic, RAM, two sets of HPC FMC rather than just one LPC FMC, 4 SFP+ Cages instead of 1, etc. As for the technical questions, I will likely be the person answering them. I'm not certain what specific questions you have, but I figure the most useful resources I can offer right now would be the Resource Center, https://digilent.com/reference/programmable-logic/genesys-zu/start, and the Reference Manual in particular the Features and Low-pin count FMC sections. Thanks, JColvin

Hi @Ariaaa, Digilent does not make our products in line with/accredited by ISO/IEC 17025, nor do we offer such calibration services. Thanks, JColvin

Hi @otherguy, The biggest caveat I can think of with regards to measuring a twisted wire pair with either the Impedance Analyzer Adapter or directly without the adapter (so you use your own reference resistor) is that you would only be able to analyze one wire at a time; with one end connected to the 1+ and the other end connected to the known resistor value. It's not the most aesthetically pleasing setup, but this is how I would set it up with the Impedance Analyzer Adapter with one of the twisted pair cables that come with the Digital Discovery High Speed Adapter, with either end of the red wire in each of the prongs (I used a 1.5 cm male to male header to get the wire to attach). The other catch I can think of would be what length of cable you have and what impedance you are expecting. The Adapter goes down to 10 Ohms (each reference resistor is 0.1% rated on the adapter), but if you are measuring a much longer cable or are expecting a super low impedance so that the 10 Ohm reference is comparatively a couple of orders magnitude larger than what you are measuring, I would be more likely to hedge my bets on how effective this would be. Let me know if you have any questions. Thanks, JColvin

Hi @Steely, I'm not certain what you mean by 'impedance window' but the AnalogImpedance_Meter.py and AnalogImpedance_Measure.py examples within WaveForms SDK will probably be the most helpful for you. In case by scripting you meant the in-app Script instrument, then these other Forum threads that the WaveForms developer responded to (they are out of office this week) that explained more about the Impedance Analyzer with regards to some automation and the resistor warnings. Let me know if you have any questions. Thanks, JColvin

Hi @Dominic, I don't have MATLAB installed so I can't readily test this, but based on the examples that are part of the Digilent Toolbox, https://www.mathworks.com/matlabcentral/fileexchange/122817-matlab, and the start function I believe is part of the Data Acquisition toolbox, https://www.mathworks.com/help/daq/daq.interfaces.dataacquisition.start.html, you can set a parameter to have the data be running continuously. It looks like there is a specific Digilent example using this feature here: https://github.com/Digilent/matlab/blob/master/digilent/examples/analog_out_stream_nonblocking_continous.m. Let me know if you have any questions or if this is not same functionality that you are looking for. Thanks, JColvin

Hi @zygot, You'll want to download the .xpr.zip rather than the Source Code (zip), as per the Using the Latest Release dropdown in the guide that Ionut linked to here: https://digilent.com/reference/programmable-logic/nexys-video/demos/oled#download_and_usage_instructions. You'll find all of the materials you're looking for in the usual folder (hw->hw.srcs->sources_1->imports->src->hdl). Thanks, JColvin

Hi @Håvard, I believe the Out of Box demo for the Genesys ZU implements a WiFi stack within it's PetaLinux OS; there are some additional details on how to access it as well as instructions for rebuilding and sourcing the files for yourself in this guide here: https://digilent.com/reference/programmable-logic/genesys-zu/getting-started. I am less certain on the baremetal side of it, I have asked another engineer more familiar with the Genesys ZU material for their insight into this. Thanks, JColvin

Hi @silverdiamond, The 60 Hz is almost certainly from the ambient environment via the power grid; on my own AD3 with a BNC adapter and probe, I see this most notably when I am holding the probe tip without any load connected, though the amplitude on mine is much smaller (11 mV peak to peak vs your 46 mV and only around 55 dBV). When I am no longer holding the probe (still floating), the 60 Hz portion disappears from the plot view and the magnitude from the FFT drops to ~-70 dBV. (me holding the probe at the tip) (probe lying on my desk) If you wanted to remove this source (presuming you're seeing the frequency when you are holding the probe), I would recommend making sure that your device under test and yourself are properly grounded. The device under test can have a shared ground line through one of the MTE cables, you can ground yourself either by touching one of the ground pins or BNC shields on the BNC adapter, or use a grounding strap to help keep this noise to a minimum. The FIR filter on the Analog Discovery 3 can be used to filter out certain frequencies, although it's frequency range you can use is between 500 kHz and 30 MHz. Alternatively, you would use the FIR Windowing to eliminate noise and high frequency components from a signal (this would be used in case your system was sensitive to overshoot or ringing). From my testing, this works up to around 2 MHz before you start to experience signal attenuation that can occur with FIR filters. The pink and green traces in the splash screen for the oscilloscope section of the reference manual offer a visual of smoothing out a signal: https://digilent.com/reference/test-and-measurement/analog-discovery-3/reference-manual#oscilloscope. Let me know if you have any questions. Thanks, JColvin

Hi @GRe, The function you are looking for is FDwfDigitialInTriggerSourceSet (Section 9.3 in the WaveForms SDK Reference Manual) to use an external trigger as the default setting is to have no trigger source (the options for the trigger sources are within Section 4 on page 6 because the global trigger bus applies to the whole device both analog and digital, or starting on line 45 in dwfconstants.py). You can then set to receive a rising, falling, or either edge through FDwfDigitalInTriggerSlopeSet (variables defined on line 106 of dwfconstants.py). The FDwfDigitalInTriggerSet function is used when you want your acquisition to trigger on based on one of the existing Digital I/O pins (rather than on a dedicated external trigger pin), setting the appropriate field to 1 and bit shifting to the pin of interest. There are a couple of examples using this function and similar functions in DigitalIn_PulseTrigger.py and the DigitalIn_Trigger.py examples which are readily accessible within the SDK installation location. (or alternatively, there is a more specific example that uses the external trigger option in AnalogOutIn_Synchronization.py) Let me know if you have any questions. Thanks, JColvin

Hi @rcross, This is correct. The 5 V range is +/- 2.5 V as per the Analog Discovery 3 Specifications, https://digilent.com/reference/test-and-measurement/analog-discovery-3/specifications#analog_input_channels, so applying a 3 V signal is outside of that range. You can apply an offset of -2 V (to shift the range down by 2 V, so the 5 V range is instead -0.5 V to 4.5 V), and then accurately measure the 3 V signal with the low-range measurement. You can also measure the same 3 V signal on the Scope instrument by setting the offset to -2 V, the range to 500 mV/div (the largest voltage division that maintains the low range setting for better resolution), and click on the Measurements tab to add a defined measurement, such as the Average voltage value of the visible data on the screen for Channel 1 (or whichever channel you are measuring). Let me know if you have any questions. Thanks, JColvin

Hi @Takashi "The Yaka mein", I received the following information from the Engineering Services Manager regarding the Ferrite bead / cable snap-on: 8547.10.8000 and EAR99 They also mentioned that the ferrite bead is part of the existing Analog Discovery 2 kit (as opposed to the ferrite being an extra line item within in the bundle), so it would be covered by the existing classifications for the Analog Discovery 2 kit (SKU 421-321 // 1286-1117-ND). Let me know if you have any questions. Thanks, JColvin

Hi @daily, A mobile phone charging cable I am less confident of in terms of for sure working simply because if the cable only supports charging and does not properly support data, then the Analog Discovery 3 would not be detected/work. I personally haven't encountered any USB Standard A to USB Type C cables that do this, but own several USB Standard A to USB Micro-B cables that do not support data, so it's a possibility, but hopefully not as prevalent of an issue as it once was. A USB Standard A to USB Type C adapter should be fine, so long as it also handles data and isn't power only. Realistically, most cables that you can find online should be okay as long as they say that they support USB High Speed or mentions USB communication. Let me know if you have any questions. Thanks, JColvin

Hi @mize6entprz, Could you let me know a bit more about your setup? What OS are you using Which version of WaveForms are you using How are the Analog Discovery 2 devices connected to your host computer (what kind of computer; laptop, desktop, etc)? Through a (powered/unpowered) hub, connected to a root host controller on your computer, etc? My initial guess from your description is that you have multiple devices connected to the same port and are running into a power limitation, but I can't tell for certain based on your description. Thanks, JColvin

Hi @cptn, In addition to describing a bit more what you are experiencing and setup like @zygot mentioned, you might be (I'm not a Linux expert nor do I know which Linux you using) running into an upstream Linux bug that is mentioned in this thread here: Thanks, JColvin

Hi @Takashi "The Yaka mein", I am finding out this information for you. I will let you know what I learn. Thanks, JColvin

Hi @zeckjia, I'm not personally sure on the accuracy of the clock for the AD2. The Hardware Design Guide has a small section on it here: https://digilent.com/reference/test-and-measurement/analog-discovery-2/hardware-design-guide#clock_generator, and there are a couple of threads on the AD2 clock which might help give you some insight here: https://forum.digilent.com/topic/20004-ad2-pattern-generator-creates-clock-drift/ and here: https://forum.digilent.com/topic/24529-repeatability-issue-using-ad2-oscilloscope-and-waveform-generator/?sortby=date. Let me know if you have any questions. Thanks, JColvin

Hello, The particular screenshot of the Help Tab I pulled is also available in the 3.20.1 release version that launched with the AD3, and was mentioned in this thread: https://forum.digilent.com/topic/25916-analog-discovery-3-information/#comment-77521 and also referenced via proxy here: https://forum.digilent.com/topic/25915-analog-discovery-3/#comment-77556. Based on WaveForms change logs, the ADP3000 series boards first had access to external clock back in 3.17.1 which released back in October 2021, https://digilent.com/reference/software/waveforms/waveforms-3/change-logs/3-17-1 (which I confirmed just now after downloading 3.17.1 and checking the in-app device options), but as best as I can tell, there has been only a single question about it on the Forum in September 2022: https://forum.digilent.com/topic/23871-external-reference-clock/. I'm not as familiar with the API/SDK side of things as I would like to be, but this function was also available in the 3.20.1 Release of the SDK as well via FDwfParamSet; it only says it's supported by the ADP3000 series boards (not sure when they gained this particu but I would think this would also be supported by the Analog Discovery 3. I will defer to @attila on this detail. Truthfully though, thank you for the feedback and desire to know more about this particular feature; I'm not sure when came into existence i.e. if it was an idea Attila had or if it came from a customer request like the one for Dual Mode to use two identical devices to extend the number of analog / digital channels and have all of the data (and synchronization of the two devices) handled within a single instance of WaveForms which takes advantage of the external clocking (a blog post on Dual Mode that was started before this thread I'm typing on will be published relatively soon). I believe the ADP3000 series boards gained support for Dual Mode towards the end of April 2023 in 3.19.34, https://forum.digilent.com/topic/8908-waveforms-beta-download/. Clearly, Digilent underestimated the perceived value of this particular feature (I wouldn't have even called it a hardware feature per se, though I suppose it technically is as Attila had to add FPGA logic in order to support it, as is the case for many of the new WaveForms features). We will work on getting this feature better publicly documented. Thanks, JColvin

Hi @swapnilbarot, I have uploaded the JTAG SMT3-NC Statement of Volatility to its Resource Center: https://digilent.com/reference/programmers/jtag-smt3/start#documentation. Let me know if you have any questions. Thanks, JColvin

Hi @zeckjia, The Analog Discovery 2 does not support having an external clock signal. The Analog Discovery 3 can support an external clock ranging between 10 MHz and 50 MHz (with the ability to adjust the Phase for better alignment) on the Trigger 1 line; there is some additional information on this within the WaveForms Help Tab in the System Frequency section of the Analog Discovery 3 category: Let me know if you have any questions. Thanks, JColvin

Hi @Shawn_Cary, I am presuming by nothing you mean when you connect the board Windows does not do its "device detected" noise and that you can neither see a COM port or, more importantly, a listing of USB Serial Converter A and B with a Bus reported device description of Digilent USB Device, as mentioned in this specific post: If you cannot see anything show up in the Windows Device Manager, this is a strong indication that the USB cable (or perhaps USB port, I've had both a cable and a port die on me) does not properly transmit data and only supports charging, so I would recommend trying a different USB cable. Let me know if you have any questions. Thanks, JColvin

Hi @AjayLeafi, I would recommend taking a look at this thread (and it's contained thread): Let me know if you have any questions. Thanks, JColvin

Hi @Michael Fischer, Yes, you may use an external JTAG programmer via J8 alongside the on-board USB-JTAG port J10, though I am not certain why you would want to do this as the JTAG chain will not allow two simultaneous connections to the same FPGA. Additionally, the Xilinx Hardware Device Manager is usually quite aggressive about maintaining access to all of the JTAG connections it can detect. In general I would also recommend not deliberately attempting to produce a drive conflict on a system, but that's neither here nor there. Otherwise there are buffers and pull resistors on the JTAG lines between the on-board FTDI chip and the FPGA, though Digilent has chosen not to share this page of the schematic for any of our products. Let me know if you have any questions. Thanks, JColvin

Hi @HUANGWJ, The Xilinx toolchain has not required a license for individual non-enterprise users since 2016; the Zynq-7000 series board support is freely available with the free WebPACK / Vivado ML Edition edition of the AMD (Xilinx) toolchain. Digilent has a dedicated guide on how to install Vivado and Vitis from the Xilinx available here: https://digilent.com/reference/programmable-logic/guides/installing-vivado-and-vitis. Let me know if you have any questions. Thanks, JColvin

Hi @Thunder, I'm not certain what other vendor you are referring to, but if this other specific driver blanket catches the default FTDI Vendor and Product IDs (such as tools like Zadig, https://forum.digilent.com/topic/25705-windows-recognises-eclypse-z7-board-incorrectly-as-a-trion-board-in-device-manager/?do=findComment&comment=76839, among doubtless countless other similar tools), then likely the easiest solution to separating out your configuration processes will be to use separate host machines as zygot suggested. Perhaps there is a more elegant solution (that likely requires specific driver rules) available, but that is very likely going to be application and workstation specific. Thanks, JColvin