• Content Count

  • Joined

  • Last visited

  1. Hi @attila, any news about arm64? sources? Thanks a lot! Pazzo
  2. Hi @attila do you have any update? BR, pz
  3. Hi @attila! Thank you so much but the best will be to have sources 😉 pz
  4. Hi @attila! Thank you for your help! I can sample at 500KHz using 2nd configuration (doing some changes on cpugovernor). I would like to add that using the kernel with RT_PREEMPT I can get data at 1.25MSample/s (!!!) pz
  5. Sorry, for the noise. I found the answer in this note of FDwfAnalogInStatus(HDWF hdwf, BOOL fReadData, DwfState *psts) documentation Note: To ensure consistency between device status and measured data, the following AnalogInStatus*functions do not communicate with the device. These functions only return information and data from the last FDwfAnalogInStatus call. So it's needed to get all the information from device... As result I test my acquisition example on a i7 using a direct usb3 connection and I can reach only 700KSample/s .. Could anyone share an example of C code to get samples at 1MSample/s? Does anyone try to use rt patches? Thanks! pz
  6. Hi, I'm trying to acquire at 1MSample/s using WaveForms SDK (DWF Version: 3.10.9) I think that I should use acqmodeRecord mode with infinitum length so I use: FDwfAnalogInRecordLengthSet(hdwf, 0.0); But then in the while loop I'm a little puzzled due to the call if(!FDwfAnalogInStatus(hdwf, true, &sts)).... Shouldn't be done only once to reach Running state? According to section "5 Analog In (Oscilloscope)" in SDK documentation the AD2 should remain in Running state... So I change the example to do only once but I have always the same samples...any clue? Should I use other acquisition mode like ScanScreen? like reported in Thank you for your help pz
  7. Hi, I'm using a RPi4 with Analog Discovery 2 and I'd need to use AD2 at 64bit so I'm wondering why you are not sharing sources to build libraries for a specific system with proper optimization. Best, pz