Jump to content

Mathias G.

Members
  • Posts

    26
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Mathias G.'s Achievements

Member

Member (2/4)

2

Reputation

  1. Hi @attila ! Thank you, the problem was dwf.FDwfParamSet(DwfParamOnClose, c_int(0)) :)
  2. Hi ! This link works : https://click.pstmrk.it/3s/lp.digilent.com%2Fcomplete-waveforms-download/ZSSe/4r_tAQ/AQ/52684c65-de85-4027-9298-81af629ebeef/2/Pvcv9IRJsq
  3. Hi @attila ! I try the single mode, generally that's works, but sometimes (even half the time) the acquisition have an easily observable problem (pictures 1 and 2. This problem only happens when I have a range less than or equal to 2 volts. I notice that the signal amplitude has been reduced x25. I see with Waveforms that the signal amplitude is egal to 0.33 and doesn't vary.
  4. Yes, single mode works as expect but we need to have a large amount number of samples so it's why we start with this mode. As I say, I notice that a new version without the delay when the trigger is set to 0 for the record mode. But I try and I have again a random delay with the record mode, so I gonna try with the single mode, which is more easily.
  5. For these features I had to drop the backward compatibility of the new firmware with the record used in the older software. => That's exactly the problem that I have. No problem about that if we can use the single mode and get 128MiSamples in total. And in the software/firmware version 3.20.10 (but I just saw that you put a new beta version), I have the problem of stability with the record mode. It's why we want to downgrade the firmware. 102_AnalogIn_SamplingClock_test_GM.py
  6. Hi @attila ! I know how to get the software version but I need to get the firmware of the ADP. And, if it is possible how to downgrade the firmware because we have seen that with the new version, we have a problem that we don't have in the old version of firmware. We have few ADP, and we use them to test in same condition with the same program. If I ask many questions, it's because I am in a research lab specialized in CPS and we are interested to use the ADP to characterize CPS so we need anything of really stable and with high capacity of memory (minimum 10 MS). About the last point, can I get more than 32,768 samples with the single mode ?
  7. Hi @attila I don't know that we need to set the frequency, I understand the problem ! Thank you !!
  8. Hi @attila I have try with your program, I have change the frequency to use the frequency of the external clock (I see later that you have already do it... sorry !) . When I use a low quantity of samples, I think that I have a signal synchronous. But when I take more samples (here 640) you can see, that I have different delays everytime. AnalogIn_SamplingClock_test_GM.py
  9. Can I have a beta test version with problem of (+/-10..20) sample trigger delay for external sampling clock resolved or that's not possible ? Maybe, you have already test the code I posted before, because now I can't get anything to synchronize at all. (I don't remember changing any parameter other than the triggerpositionset or the number of samples, so the problem is either there or in the software, perhaps).
  10. Thanks you @attila! I gonna check the SW version, and I had already modified oscilloscope source in External 1 and the trigger on external 2. (That's my actual code) Error with AIStatusRecord happens only when I set a low number of samples (by example 32) and I have the trigger on. I tried and I gonna try many setup with different number of sample then different trigger delay and length of acquisition (both make that works sometimes and sometimes not so I can't say why). Update : Now the device update is done (I was at the 3.19.1 or .2 ... ) AnalogIn_record_test_4bits_vidor.py
  11. For the third question, I found that putting an offset of 50% erases the problem, but why ?
  12. Hi @attila ! I don't know if I can post three another question here, so I try but if you prefere, I can create a new page. 1 - Can the ADP stop the acquisition if it exceeds 70°C ? Today, I have a bug few times, and each times the ADP is relatively warm. 2 - Can I get the frequency of the external clock that I use as source for the oscilloscope ? (It's connected to the trigger 1) 3 - I have a delay equivalent to 4 tick when I acquire more than 320 samples, why? For the first question, the ADP block (bug) at this step (precisely it's when I do the AnalogInStatusRecord function) so I have to interrupt by myself.
  13. Hi @attila ! I have these two figures that I made myself, I collected 100 samples on 4 channels. (I'm sorry for the language) Courbe tps en fonction clock externe.pdf Courbe tps en fonction période clock externe 10 - 1000 MHz.pdf
  14. Thanks you @attila I don't know but I try with another code and that's work as for you ! But sorry, I have an another question : Why I have an important time of configuration, which is proportionnal with frequence of the external clock from 100 kHz. (between 2-3 seconds for 100 kHz, 20 seconds for 10 kHz, ...)
  15. Hi @attila ! Currently, I generate a clock with the pattern generator (in the code, it is the pinClock). The problem is that the program starts the acquisition without waiting the condition of trigger. I tried disconnecting the cable I use as a trigger and disabling the auto trigger and I didn't get a message telling me that the AD is waiting, and the acquisition has started. I made few modifications in the code to try and one thing is to use the channel 4 as detector because it has a periodic signal on 9 samples. As you can see, on the pictures, if I made two (or more) acquisitions I didn't have the same result. (I just try to change the analogIntriggersourceset value, from trigsrcDetectorAnalogIn to trigsrcAnalogIn but nothing change). test_record_pattern_4bits.py
×
×
  • Create New...