Jump to content

JColvin

Administrators
  • Posts

    6,607
  • Joined

  • Last visited

Posts posted by JColvin

  1. Hi @jcanion,

    The 12 V variant of the PowerBRICK could be powered by the +5 V supply of the Analog Discovery 3 to then provide both +12 V and -12 V to other components on a breadboard. The output current for each rail is 100 mA, but if you are just needing a 12 V reference so that your amplifier does not clip on the edges then this should be okay.

    At the very least it cheaper than getting an Analog Discovery Studio which has +/- 12 V as one of its fixed rail supplies, and probably less janky than getting an entirely separate wall wart 12 V power supply and an adapter for the barrel end.

    Let me know if you have any questions.

    Thanks,
    JColvin

  2. Hi @JAlaj,

    The Digital Discovery has enough pins to support this, though with so many separate devices that are being driven by the clock and controller out peripheral in (MOSI) lines, I would image that the drive strength of the signal would start to become a concern as well. However, it is my understanding that the Multi MISO option is only available in the Spy sub-tab for the SPI function within the Protocol instrument.

    Ostensibly, it may be possible to do some sort of custom setup where you have the Logic Analyzer continuously capturing data on the 32 MISO lines and then a separate Pattern Generator instrument running a custom pattern controlling the remaining three SPI control signals to tell all the peripheral devices to periodically take a sample (or whatever function the peripheral devices are doing), but I have not attempted such a large scale setup.

    Thanks,
    JColvin

  3. Hi @ryoryo10,

    I might be mistaken, but I don't believe Digilent has defined this particular parameter.

    I likely did not do a proper setup or test, but with the AD3 at my desk outputting a 40 kHz clock from one of its channels, this is what I measure on the ADP2230 oscilloscope (using a different instrument purely to show a different internal oscillator being used for timing) after over 5000 acquisitions at 100 MHz sample rate (with the default 32768 sample per acquisition size, this works out to about 65k 40 kHz pulses being analyzed):

    image.png

    When the precision is scaled to the 1 mHz level (the first row in measurements), I get (to be clear, with a single AD3 on a singular hardware setup) an average measured frequency of 39,999.669 Hz, or -8.275 * 10^-4 % less than a precise 40 kHz.

    When I ran a similar setup (again, one unofficial, probably poorly setup singular test on a singular hardware setup) for a 1 MHz digital square wave, the difference between the measured average and the theoretical was very similar at -8.273 * 10^-4 % less, though the measured minimum and maximum were less close when compared to the 40 kHz counterpart.

    image.png

    Let me know if you have any questions.

    Hope this helps,
    JColvin

  4. Hi @digitalone,

    For the split termination setup that is used on the Pmod CAN (both ends terminated if they are the ends in your system), my understanding is yes you will want to use JP2 to enable the capacitor load, at least based on this TI App Note (section 4.5.2), https://www.ti.com/lit/an/slla270/slla270.pdf, which is also reiterated in this Technical Article from TI here, https://www.ti.com/document-viewer/lit/html/SSZTB40.

    Let me know if you have any questions.

    Thanks,
    JColvin

  5. Hi @digitalone,

    They should be able to be connected directly together without issue via a RS232 cable, yes.

    Each Pmod CAN has a jumper (JP1) to optionally enable the 120 Ohm termination between CANH and CANL, as well as an additional JP2 jumper to optionally terminate the lines with a capacitor to ground. You can see the setup in the Pmod CAN schematic, https://digilent.com/reference/_media/reference/pmod/pmodcan/pmodcan_sch.pdf, which can also be found on the right-hand side of the Pmod CAN Resource Center: https://digilent.com/reference/pmod/pmodcan/start.

    Let me know if you have any questions.

    Thanks,
    JColvin

  6. Hi @tm_c,

    I have not been able to convince the key stakeholders as of yet to post a 3D model or official dimensional drawings, but after a bit of searching I did learn that the drawing @SINAPTEC COMBLEZ used is an official one that was originally posted by the WaveForms developer about 4 months earlier in this post, https://forum.digilent.com/topic/26785-analog-discovery-3-dimensions/#comment-81182, so I can at least confirm that the listed dimensions on that drawing are accurate.

    Thanks,
    JColvin

     

  7. Hi @Neil22,

    I agree that the two boards are suffering from a manufacturing defect.

    Please send me a private message with the Digilent order number Haley Tech made with the purchases and purchase date if it is different from what you listed in your original post (you already provided the serial number) and I will get the information to our Sales team who will help process the replacement.

    Thanks,
    JColvin

  8. Hi @E_S,

    I am not certain on the latest driver versions as I have not personally tested them, but as the ADP5250 is effectively a reskin of the VB-8012, software support is fairly interchangable between the two devices.

    You can use the Digilent WaveForms software directly with the VB-8012:

    Similarly, you can use your own LabVIEW code designed for the VB-8012 and the VirtualBench driver with the ADP5250:

    Let me know if you have any questions.

    Thanks,
    JColvin

  9. Hi @Fukuda,

    You can find the Declaration of Conformity for the Analog Discovery 3 in the "Analog Discovery 3 Certifications" pdf that is available in the Additional Resources section of Analog Discovery 3 Resource Center: https://digilent.com/reference/test-and-measurement/analog-discovery-3/start#additional_resources.

    Otherwise, the ROHS Certificate of Compliance and REACH Certificate of Compliance for all Digilent products can be found here: https://files.digilent.com/resources/documents/Digilent RoHS CoC.pdf, and here: https://files.digilent.com/resources/documents/Digilent_REACH_CoC_235_SVHC.pdf, respectively.

    Let me know if you have any questions.

    Thanks,
    JColvin

  10. Hi @Bastien Lemaire,

    I'll mention again that the WaveForms SDK material on GitHub is not maintained at this time (that might change in the future if my boss notices that I'm working with the material), but looking at your supplied code the biggest issue (and likely the root of the problem) is that on line 23 in your logic.record function you specify the channel to record on is channel 29, which is incorrect. You actually want to be recording on channel 0 as pin 29 is the IO pin you are outputting your 1 Hz square wave on.

    Similarly, the commented out logic.trigger function is also trying to trigger on channel 29 rather than the intended input of pin 0.

    The test_logic-pattern.py example from the GitHub page looks like it defines the DIO_OUT pin as 0, which won't work as is because the pattern.generate function always subtracts 24 from the supplied channel number, and there is of course no "-24" pin to use as an output.

    Let me know if you have any questions.

    Thanks,
    JColvin

  11. Hi @dr.whom,

    I'm slightly surprised that you find the Digilent sold B200/B210s of better quality. My understanding is that Digilent is just, more or less, a different distributor for these boards, or at least I am not under the impression that we manufacture them as opposed to NI, or at least I have been told that the boards are identical. I might be wrong on that though, I'm not tied in to manufacturing side of things and it's been awhile since I've looked into it.

    Regardless, Digilent unfortunately does not have RF Signal Generators or Power Meters of any kind.

    I would personally, and have been recommended by Ettus team to, reach out to the Ettus mailing lists, https://kb.ettus.com/Mailing_Lists, where Ettus Research engineers, Ettus support, and customers themselves have been active for the last 10+ years to find out what signal generator or power meter they would recommend.

    If anything, this will at least reduce the time it takes for you to receive an accurate response since the Digilent staff will end up reaching out to the Ettus team about this anyway and echoing the answer back to you.

    Thanks,
    JColvin

  12. HI @Bastien Lemaire,

    I'm not familiar with the Github implementation (it hasn't been maintained or updated for awhile), but in terms of the built-in DigitalIn_Acquisition.py for the Digital Discovery, you'll need to make sure the correct physical pins are connected.

    The DigitalOut and DigitalIO functions 15:0 index corresponding to pins 39:24. The DigitalIn functions correspond to 31:0. There is more specific details in Section 14.4 Digital Discovery (page 142) within WaveForms SDK Reference Manual (which you can quickly get to by clicking on the WaveForms SDK link in the upper right hand corner in the Welcome tab of the application).

    image.png

    If you're confident that the wires and correct signal names are called in your setup, feel free to attach your script to see if we can reproduce the problem.

    Thanks,
    JColvin

  13. Hi @Abhishek,

    1) The AMD/Xilinx Vivado software supports the Artix 35T FPGA chip from (if I remember correctly) Vivado 2015.1 onwards. So effectively, you can use whichever version of Vivado you prefer. Newer versions will have some software improvements for various things (IPs, SDK/Vitis changes), but that will of course come at the cost of an increased installation size (probably ~50 GB for recent versions, even if you deleted unnecessary portions out of the installation after the fact). There isn't really a "right" or "wrong" version to use per se. If you are planning on just doing HDL based work on the Arty A7, then any version will work.

    On Digilent's end of things, we have existing tutorials and example projects supported in 2022.1 (and a number of earlier versions): https://digilent.com/reference/programmable-logic/arty-a7/start.

    2) A micro-B to USB A cable would be the one you want to use, with the micro-B connecting (tab side up) to the J10 micro-B port just above the Ethernet port on the Arty A7. I have not seen the "Power Surge" message before when connecting a device before, but regardless that is not the expected nor intended behavior. Has this board been used before or is it new?
    When you connect the other cable, does the power indicator LED (LD11 in the bottom right corner below the barrel jack) light up and does your operating system detect that a device has been connected? If it does light up, and you have the MODE jumper JP1 (upper right corner) loaded, do the RGB LEDs start changing color on their own after a few seconds of waiting? (this would only happen if the Arty A7's flash memory has not been overwritten).

    Thanks,
    JColvin

  14. Hi @Al B.,

    Thank you for the detailed information. I agree that the board is suffering from a manufacturing defect and is eligible for replacement.

    Presuming that you ordered the device directly from Digilent, please send me a private message with the following information:

    • Order number
    • Preferred email contact
    • (you already provided the purchase date and serial number)

    I will then get the information to our Sales team who will contact you to confirm any additional information that I do not have access to, such as shipping address. I will also request the Sales team arranges to have the defective board sent back for analysis.

    If you instead purchased the board from a distributor (Mouser, Farnell, Amazon, etc.) you will need to contact them for a replacement. They will then contact Digilent as needed for their own RMA. Feel free to use this Forum thread as evidence of having worked with a Digilent engineer.

    Thanks,
    JColvin

  15. Hi @sceasary,

    I am uncertain what the case might be for custom drivers, though I know that you can use the WaveForms software directly with the VirtualBench (at least the VB-8012 and presuming you are on Windows):

    Similarly, I know you can also your own VB-8012 LabVIEW code and VirtualBench driver with the ADP5250:

    To be clear, the ADP5250 is based off of the VirtualBench VB-8012, not the VB-8054. I am not familiar with the driver nuances, but at the very least the higher end specs for the Oscilloscope, Function Generator, and Power Supplies on the 8054 would not be accessible on the ADP5250.

    Let me know if you have any questions.

    Thanks,
    JColvin

  16. Hi @Sam S.,

    I'm guessing you're opening the Analog Discovery 3 in it's default configuration which assigns 16384 as the default configuration size for each of the analog input channels.

    To open the second configuration (configuration 1 with the zero based index) you'll want to use the function "FDwfDeviceConfigOpen" instead of just "FDwfDeviceOpen".

    So for opening the first available device in the second available configuration, you'll want

    FDwfDeviceConfigOpen(-1, 1, &hdwf);

    The built in device_enumeration.cpp example will list out all of the configurations for you.

    Here's a forum thread on the same topic:

    What I'm not certain on how to do is how you might allocate extra buffer that is associated with disabled analog channels to the remaining channel like you can in the application for the AD3.
    Simply disabling the channels, reconfiguring the device, and then checking the available analog buffer size didn't seem to yield the 64k I was looking for when I tested it out in python..

    I'm hoping the developer will offer some insight on how this might be done once it is regular work hours in his timezone.

    Let me know if you have any questions.

    Thanks,
    JColvin

  17. Hi @asdfex,

    You are correct that the WaveForms Reference Manual on the Digilent Reference site is not up to date; instead, the most up to date version of the material is going to be in the Help tab (next to Welcome) of the WaveForms application itself.

    I will see if we can get the reference material updated, though finding such time to manually migrate the material to a different format will be unlikely to happen if it doesn't happen soon (as evidenced by the reference site version not having had a real update in a number of years).

    Thanks,
    JColvin

  18. Hi @JonD,

    I can't quite tell from your post, but I presume that you are referring to the various add-on boards for Analog Discovery 3 / 2 such as the BNC Adapter or Transistor Tester or whichever? The Analog Discovery 2 and 3 both come in their own case that has rubber feet.

    As for the various adapters, it is true that many of them do not have rubber feet (Impedance Analyzer does if I recall correctly), but they are all exposed circuitry. From my understanding, any metal standoff feet on Digilent devices, whether that is the BNC Adapter or Zybo Z7, are not electrically connected to anywhere else on the boards.

    Anecdotally speaking, as Digilent started out primarily making educational based boards, our devices tend to be fairly resistant to abuse, particularly the Test and Measurement devices as they were planned with classroom teaching and inexperienced students inadvertently shorting things in mind. The automotive support within WaveForms only became a thing less than 1 year ago (July 2023 according to the Beta download changelog).

    I'm guessing that in terms of automotive work, simply using rubber stops for kitchen drawers won't quite be sufficient (and dripping epoxy over the exposed material is a hassle). What style of enclosure would you be looking for? Just some covers like the for the Pynq Z1, Plexiglass Covers: Recommended Addition for the PYNQ-Z1 - Digilent, https://digilent.com/shop/plexiglass-covers-recommended-addition-for-the-pynq-z1/, a more robust enclosure like for the Eclypse Z7, https://digilent.com/shop/eclypse-z7-enclosure-kit/, or something else (I'm guessing not just a soft case that holds both the AD3 and whatever adapter, https://digilent.com/shop/analog-discovery-3-soft-case/)? Would this enclosure be form fitting to individual adapters, or more modular and workable among a wide range of adapters (this would be difficult as the adapters are all wildly different sizes).

    As a side point, as far as I remember, you're also the first person to request this sort of thing for the adapters, so the market for it is, presumably, relatively small which will make it hard to convince the various stakeholders to invest time into making such such a protective case.

    Thanks,
    JColvin

×
×
  • Create New...