Jump to content

attila

Technical Forum Moderator
  • Posts

    6,667
  • Joined

  • Last visited

Everything posted by attila

  1. Hi @nott1999 To overcome the problem, in case of error you could try to reconnect to the device (close and open), but this would interrupt (need to restart/resume) the recording.
  2. Hi @Hamza Oncuer You can use a script like this: if(Index > Maximum) return; var data = Scope.Channel1.data; var c = data.length; var dmax = []; for(var i = 0; i < c; i+=2){ dmax.push(max(data[i], data[i+1])); } FileWrite("~/Desktop/scope/acq"+Index+".txt", dmax); Index++;
  3. Hi @xchg.ca See the Peak hold option in Spectrum Analyzer Trace and Scope FFT view.
  4. Hi @timnrp Try to use an external pull-up. The inter pull-up on PB2 may be activated only after programming. During and before this the very low (~1M) pull-down from AD2 DIOs may hold the signal low.
  5. Hi @Mavitaka The GPS satellites use atomic clocks which are extremely precise and these also take in account the time dilation. I don't know how accurately does the receiver forward the signal but probably it is still more precise than any device using crystal oscillator.
  6. Hi @TaliaS There is no such feature in the WF app but it could be implemented in custom app/script. AD3 and newer devices have support for in device Scope to AWG routing, analog in to out.
  7. Hi @nott1999 Have you tried to disable sleep and usb suspend ? The erc indicates data transfer error with the device, probably caused by disconnect, like the following message:
  8. Hi @Hamza Oncuer See the "sample mode" option or called FDwfAnalogInChannelFilterSet for custom app/script.
  9. Hi @diligent1 The VI package provides a limited set of features. FGen synchronization is not available in this but in the WF API/SDK.
  10. Hi @Mavitaka See the Counter in the Logic Analyzer. Here 1Hz is generated by one device and captured by another. The difference is the crystal oscillators tolerance.
  11. Hi @cpitman Make sure you are looking at the correct wire/signal and have ground connection between devices also when using the digital wires.
  12. Hi @Juan05 By default the DIOs are in high impedance. These can be controlled to drive low/high/Z by the digital-out and digital-io functions. Before the device is powered up the DIOs are pulled to GND by the protection circuit.
  13. Hi @nott1999 Isn't this caused by computer sleep or usb suspend ?
  14. Hi @nott1999 Such disconnect usually indicates USB contact issue or lack of power. Try using other cable, port, auxiliary 5VDC power supply.
  15. Hi @AndreasGroell If the lower range is sufficient, for better resolution set the Range to 5V It could be caused the initial temperature drift, it should settle after the device heats up in about 10 minutes. You could recalibrate the oscilloscope under Settings/ Device Manager.
  16. Hi @notthetup Yes. The Network Analyzer has option for differential drive on the two AWG outputs and the Scope inputs are differential.
  17. Hi @Ostin Flores Your oscilloscope capture looks AC coupled and attenuated. Do you have proper ground connection between the device and scope ? Could you attach a photo from the setup ?
  18. Hi @Loic VINET You are not using the capture properly. You stop after capturing 99% of intended samples, but you should collect until done state is reached. As mentioned in an earlier reply, try using the much easier to use the 'single' acquisition mode.
  19. Hi @Loic VINET Are you driving DIO 31 or 12 or using pull up/down ? If not, these are in high impedance which can capture any radiation, specially if wires are connected to it, usually the 50/60 Hz from electrical grid. In a setup the ground may be floating (power supplies without earth connection like most of USB chargers) or connected to earth (some laptop supplies and most computers), which also influence noise reception.
  20. Hi @Mavitaka The sampling of data lines should be performed on the same clock that the ADC receives, with the required phase to satisfy setup and hold. If you are using Digital Discovery Sync capture mode you could try using falling edge instead of the rising edge, to have 180* shift. With normal capture mode sample at least at 400MHz and interpret the data according the clock, like:
  21. Hi @joe.a I2C slave is only available in the WaveForms application. The SDK provides functions for master and 'spy', which can be used sequentially like this: Digital_I2c_SpyMaster.py
  22. Hi @Dat Nguyen I managed to reproduce the issue, using USB cable + unpowered hub + extension cable + another cable. The analog circuitry is reset or not turning on due to low USB voltage. The next software version will report such problem.
×
×
  • Create New...