JColvin

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

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

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

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

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

Hi @Qmellory, I have sent you a PM. Thanks, JColvin

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

Hi @hiroki, I have sent you a PM. Thanks, JColvin

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

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.

Hi @craigec, I have sent you a PM. Thanks, JColvin

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

Documenting that this was responded to in the other post here: .

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

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

Hi @ez4game, I have sent you a PM on how to restore the SMT1 present on the VC707. Thanks, JColvin

Hi @gnarco, I have sent you a PM. Thanks, JColvin

Hi @zzz, I'm sad to hear the customer experience is not what you wanted. The Forum here is where the Digilent support engineers, such as myself, are able to answer questions in such a way so that other customers with similar queries can also benefit from the answer. Cancelling the order would be done through your Store account, or there's likely a way on the order confirmation email to send a message to the order support team with your order number already associated with the message. Otherwise you can fill out the form on here: https://digilent.com/shop/sales-and-order-support/. In terms of deleting personal information, there is a form for it available in our Legal & Privacy page, https://digilent.com/shop/legal-privacy/. Ctrl+F for "Data Request Form" will jump to the form you're looking for. I doubt you're inclined at this point to let me know which particular aspect you feel is unfair, but feel free to post back or private message me with details. I'm not on the compliance team or anything like that, but my gut feeling is that particular line items are more likely to be considered than blanket statements. Thanks, JColvin

Hi @ctkilian, I asked another engineer who was more familiar with the Pmod ToF about this and they reminded me that the embedded ISL29501 chip needs to be calibrated before any data is taken (which isn't very well explained in the datasheet that I linked earlier). Digilent has some additional information on this Chip Initialization step within the documentation for the FPGA Hierarchical Block Library, https://digilent.com/reference/pmod/pmodtof/libraryuserguide#isl29501_-_time_of_flight_tof_integrated_circuit. Renesas also has information on this initialization and a mention that a set of registers need to be initialized before you can calibrate the module so you can properly take measurements in their Application Note here: https://www.renesas.com/us/en/document/apn/an1724-isl29501-firmware-routines. After those registers are set up, you can then load the Digilent provided factory calibration that is stored in the EEPROM into the ISL29501. The reading of the EEPROM, described a bit more in the Library User Guide I linked, is a bit more involved, with several functions in the library Digilent facilitated to read the values and write them to the volatile ISL29501. The PmodToF_RestoreAllCalibsFromEPROM_Factory function starting on line 472 in the PmodToF C source file, https://github.com/Digilent/vivado-library/blob/hierarchies/hierarchies/PmodToF/sdk_sources/PmodToF/PmodToF.c, will probably be the most helpful to you in terms of determining all of the needed steps to get the factory calibration loaded. Thanks, JColvin

Hi @rbuisson_tdk, I have sent you a PM. Thanks, JColvin

Hi @Abhijan, The first thing I would be checking with the 1:10 ratio would be the attenuation setting on the BNC probe. It's also worth ensuring that your two devices share the same ground connection. Let me know if you my guess is not accurate to your situation. Thanks, JColvin

Hi @jfm, When you connect to the micro USB port to your laptop, is the jumper that is next to the barrel jack set to the USB setting side (as opposed to the external power side)? The power good LED next to that same jumper should light up. If the jumper settings are correct and the LED doesn't light up, I would first recommend trying a different USB cable (especially if when you connect to your computer you are not able to find evidence of the connection in the Device Manager). It is also worth noting that the Cora Z7 does not have any flash memory, so there is not an out-of-box demo that will load on power-up as there is not static memory to load from (presuming I remember correctly that the Cora Z7 does not ship with an SD card). If the power LED is lighting up, you can test the Cora Z7's functionality though the Example Projects available on its Resource Center: https://digilent.com/reference/programmable-logic/cora-z7/start#example_projects. Let me know if you have any questions. Thanks, JColvin

Hi @Ahmed Bahaa, When you initially added the CAN to the Logic Analyzer instrument, what settings did you use? Additionally, what voltage is your CAN network operating at and could you attach a picture of your setup? Thanks, JColvin

Hi @Airmanblu, The SPI protocol, even though there is only a singular device on this bus, dictates that the chip select line is pulled low during every transaction because there is not an addressing scheme like I2C (https://www.ni.com/en/shop/labview/understanding-the-spi-bus-with-ni-labview.html). Because there is no pulldown resistor on the SS line of the Pmod CLS (you can verify this for yourself on the schematic, https://digilent.com/reference/_media/reference/pmod/pmodcls/pmodcls_sch.pdf) you'll need the jumper on JP1 set to short the middle pin to the SS side, as well as needing to connect a wire from the NI myRIO to pin 1 header J1. Let me know if you have any questions. Thanks, JColvin

Hi @tom.des, I have sent you a PM with some instructions. Thanks, JColvin