Jump to content

attila

Technical Forum Moderator
  • Posts

    6,469
  • Joined

  • Last visited

Everything posted by attila

  1. Hi @BSc For ADP3X50 embedded Linux use digilent.waveforms.adp3X50_x.x.x_armhf.deb
  2. Hi @Dinu 1. The Protocol/UART does not have auto rate option. The continuous Spy mode on multiple UART lines is not suitable for high rates specially with Digital Discovery since this does not support data compression. 2. FileAppend("~/Desktop/uart.csv", Logic.Channels.UART.events.join(""));
  3. Hi @HasNoCreek The easiest way, if ms precision is sufficient, would be software control using FDwfDigitalIO... functions. You can use digital-out function for automated precise control, see FDwfDigitalOut... functions. For fully independent control the analog-out functions can also be used, see FDwfAnalogOut... functions.
  4. Hi @aaaaa You can use the Script tool like this: Impedance.run(); var t0 = Date.now() for(var i = 0; wait(0.999) && i < 1000; i++){ // wait 999ms var v = (Date.now()-t0)+","+Impedance.Traces.Trace.getData("Impedance")[0]; print(v); // ms, ohm FileAppendLine("~/Desktop/imp.csv",v); }
  5. Hi @gcb Continuous digital play is not available with any device. The Digital Discovery has Play mode for up to 256MiB of data. Other device support 'unlimited' AWG Play which could also be used as 1bit digital line. Analog Discovery with 32k device buffer up to about 4MS/s. ADP3X50 has 32Mi AWG sample device buffer, ADP2230 has 128Mi buffer and USB3.
  6. Hi @bryan78 Thanks for the observation.
  7. Hi @pfm Corrected here: I accidentally left it there in the previous version when trying to make it compatible with other RPM distributions. Unfortunately the packages have different naming in repositories.
  8. Hi @bryan78 It is corrected in the latest version:
  9. Hi @Sam S. For Network Analysis triggering is usually not important but your trigger settings seems to be ok. For stability, to not to trigger on opposite edge due to noise, you can use FDwfAnalogInTriggerHysteresisSet. Better use trigsrcAnalogOut1. The NA interface uses this for coherent averaging. You could also apply to FDwfAnalogImpedance... functions which can be used for NA, see the example. Crosstalk depends on the setup. Leaving the high impedance oscilloscope inputs open, specially with wires attached will catch more noise and crosstalk. Use BNC cables or twist positive/negative inputs and signal wires with ground for better noise rejection and less crosstalk.
  10. Hi @rjratnip It could be a similar hub or driver problem as it is with RPi1,2,3 where FTDI USB packets are randomly lost or corrupt.
  11. Hi @woldes The I2C should be read as logic high in idle. Do you have pull-ups on the SCL and SDA ?
  12. Hi @m72 Set the UART Baud to Manual. With Auto the Rate is recalculated for each capture which is handled as configuration change and the Buffer counter is restarted. It will be corrected in the next version.
  13. Hi @StefKay Looking at the project, unfortunately there are no clock capable DIOs, so reference clock for device synchronization is not really possible with EclypseZ7.
  14. Hi @GCompton You can use Logging/Script or the Script tool for custom export.
  15. Hi @GCompton With the current sw version you can select Trigger 1 to output 'Scope Detector' and select Sampling Clock T1 This will store one sample for each trigger event with 15 cycle delay, 150ns delay for 100MHz or 120ns with 125MHz system frequency. The next version will let you select directly 'Scope Detector' as Sampling Clock.
  16. Hi @Rohan16 If you referring to the SPI mode with '0th clock pulse' ? This can be adjusted with Polarity and Phase options.
  17. Hi @StefKay It looks like dual mode with reference clock is not supported with EclypseZ7. I will try to add support for this next week.
  18. Hi @rjratnip 1. It could be an adapter/cable contact problem. 2. The AUX supply can only be blocked by the the under/overvoltage 4.11V/5.76V protection circuit. You could have a grounding issue. Are the RPi and 5V supplies floating or grounded ? If both are grounded make sure to use nearby sockets, same splitter. With the default 'USB Power' 'Stop with AUX' the USB supply line is turned off if the AUX voltage is ok, 4.5V...5.5V If this option is 'Always ON' the USB and AUX currents will balance according the voltage/cabling resistance. If the USB voltage is higher than AUX, the AUX current will be lower. Verify the voltage of your supply or use powered HUB.
  19. Hi @Rohan16 The embedded JavaScript does not support binary number format but the interface does.
  20. Hi @Marcus Watson Are you using similar vertical range for C2 in WF and script ? The AD3 scope inputs have two input ranges. If C2 with WF app is in low range (high resolution) and with script in high range, the lower resolution could hide details. dwf.FDwfAnalogInChannelRangeSet(hdwf, 1, c_double(5.0)) # C2 low range Approximate overlay looks like this:
  21. Hi @StefKay T1 = DIO14 = B6
  22. Hi @GCompton The AD3 bandwidth of 9/30MHz may be too low for such pulse lengths. The device has sampling clock option trigger IOs but this requires digital level signal. Now I tried to enable a sample on analog trigger event but this with the current 'firmware' has a minimum trigger to sampling delay of 12cycles, 96-120ns The only eventual option I see is capturing more data, with min/max sampling and processing it.
  23. Hi @Ammar Kh See the user supplies schematic: https://digilent.com/reference/test-and-measurement/analog-discovery-2/hardware-design-guide#user_supplies_control
×
×
  • Create New...