Jump to content

attila

Technical Forum Moderator
 View Profile  See their activity

  • Posts

    6,990

  • Joined

  • Last visited

 Content Type 

Everything posted by attila

  1. attila
    Hi @AudriusM You are the first to request this option. We can add it.
  2. attila
    Szia @Andras Are you allocating sufficient buffer for the data ? The buffer size should be at least the number of samples you request to be retuned by FDwfAnalogInStatusData (hdwf, channel, buffer, number of samples) If you are collecting data in a larger buffer make sure to not pass the end of the allocation. For circular buffers use FDwfAnalogInStatusData2. The AD2 with 16k samples device buffer can capture or fetch chunks of up to 16384 samples. The AD3 has shared Scope buffer between channels, so 32768 when two channels are enabled and 65536 when one channel.
  3. attila
    Hi @Walter76 Thank you for the update. This is the first time I see such a phenomenon... speculating... it could be a faulty, cracked and/or corroded resistor
  4. attila
    Hi @Satian Anantapanyakul It depends on the cabling. Notice the columns with and without BNC.
  5. attila
    Hi @matsuya You can find more details here. Let me know if you need the full spec document, EMC testing...
  6. attila
    Hi @mowoodsiii Use Wavegen.State.running() Wavegen.States.Run refers to the Run time, see status-tip:
  7. attila
    Hi @Arno For warranty and replacement contact the support.digilent @ ni.com specifying the Date of Purchase, Seller and Purchase Order/ Web order Number.
  8. attila
    Hi @sam5991 The latest version is working on 32bit RPi OS and 64bit kernel.
  9. attila
    Hi @sam5991 It looks like the new 32bit RPi OS uses by default 64bit kernel. After adding arm_64bit=0 to /boot/config.txt to load the 32bit kernel the WF app is working.
  10. attila
    1Hi @sam5991 Works with Ubuntu (16) on RPi. I'm troubleshooting the RPi OS...
  11. attila
    Hi @matsuya Safety ： UL / cUL / GS / PSE / BSMI / CB / RCM Let us know if you need more information.
  12. attila
    Hi @RealPersonIPromise The AD2 provides only software time but for newer devices AD3, ADP3X50... high precision T0 trigger time is returned by the following function, so the samples will be timed as T0 + sample position / capture rate, or for more accurate value T0 - FDwfAnalogInTriggerPositionStatus + sample index / FDwfAnalogInFrequencyGet
  13. attila
    Hi @Yakudza With such holy damage it may be beyond repair, internal layers could be broken and other ICs burned. Here you can find further info if you need it:
  14. attila
    Hi @Ali_Hussain See the following example:
  15. attila
    Hi @nurber3 Probably the probe is not compatible with this device, the compensation range is not enough.
  16. attila
    Hi @yusuke_Adv The Reference Clock (10-50MHz) configured under Device Options will make the device use this (multiplied to be 50-125MHz), instead of the internal oscillator for the entire device, driving ADC,DAC,DIOs.. This ensures no jitter or drift over time between such synchronized devices. With Sampling Clock (<50MHz) the device runs at the specified frequency (50-125MHz), the device logic looks for edge on the trigger line and stores the last samples (or delayed). This can be used at arbitrary frequencies but the jitter will be about 10ns, the period of the specified system frequency.
  17. attila
    Hi @yusuke_Adv No, the reference clock is the input of a PLL that requires at least 10 MHz.
  18. attila
    Hi @johnea Such connection is not supported, however, see the following posts:
  19. attila
    Hi @Jan Mrázek Could you try using the device with another computer ? Such random errors indicate contact issue or lost/corrupt USB data packets, like on Raspberry PI 1,2,3
  20. attila
    Hi @chuqdd See the examples in WF SDK/ samples/ py/
  21. attila
    Hi @JosefS Only the above commands are recognized and the others printed as byte. Since there are printed in hexadecimal it should be simple to interpret as 16bit values.
  22. attila
    Hi @amiller112 The Adept System Windows Installer is now available.
  23. attila
    Hi @ALloydFlanagan @amiller112 It should work now. Added public read access to Adept Runtime 2.27.9 packages
  24. attila
  25. attila
    Hi @boilerwolverine @mawyatt @m-m-adams It should work now. I don't know what happened on the aws server, but now I have given public read access to each installer. Thank you for the notification.
×
×
  • Create New...