Charles K

Hi @cwatt While I am not the authority on this, I also had a similar problem on my Ubuntu Linux machine (same error on my AD2). I changed my USB cable to an Amazon Basic USB cable but alas, the error still came back (but was less frequent). I finally replaced my cheap USB hub with this one [1] and the problem never occurred again. My guess (and maybe a EE can better comment) is that this error has something to do with the "quality" of the USB signal going into the device. [1]: https://www.amazon.com/gp/product/B00V6ADRQC

Inside https://reference.digilentinc.com/waveforms/ref_manual Typo: "DwfDeviceReset" should be "FDwfDeviceReset" "Desacription" should be "Description" (near FDwfAnalogInStatusRecord) The following functions exists in dwf.h but are missing documentation inside Inside https://reference.digilentinc.com/waveforms/ref_manual Specifically missing Docs for: FDwfParamGet FDwfDeviceEnableSet FDwfAnalogInTriggerForce FDwfAnalogInStatusNoise2 FDwfAnalogInStatusTime FDwfAnalogInNoiseSizeSet FDwfAnalogInChannelBandwidthSet FDwfAnalogInChannelBandwidthGet FDwfAnalogInChannelImpedanceSet FDwfAnalogInChannelImpedanceGet FDwfAnalogInTriggerPositionStatus FDwfAnalogOutCustomAMFMEnableSet FDwfAnalogOutCustomAMFMEnableGet FDwfDigitalIOOutputEnableInfo64 FDwfDigitalIOOutputEnableSet64 FDwfDigitalIOOutputEnableGet64 FDwfDigitalIOOutputInfo64 FDwfDigitalIOOutputSet64 FDwfDigitalIOOutputGet64 FDwfDigitalIOInputInfo64 FDwfDigitalIOInputStatus64 FDwfDigitalInStatusNoise2 FDwfDigitalInStatusTime FDwfDigitalInTriggerInfo FDwfAnalogImpedanceConfigure FDwfDigitalInMixedSet FDwfAnalogInTriggerSourceInfo FDwfAnalogOutTriggerSourceInfo FDwfDigitalInTriggerSourceInfo FDwfDigitalOutTriggerSourceInfo FDwfEnumAnalogInChannels FDwfEnumAnalogInBufferSize FDwfEnumAnalogInBits FDwfEnumAnalogInFrequency Inside dwf.h DWFAPI int FDwfDigitalInSampleModeSet(HDWF hdwf, DwfDigitalInSampleMode v); // has trailing "//" comment Inside https://reference.digilentinc.com/waveforms/ref_manual FDwfAnalogIOChannelNodeName(HDWF hdwf, int idxChannel, char szNodeName[32], char szUnits[8]) but inside dwf.h DWFAPI int FDwfAnalogIOChannelNodeName(HDWF hdwf, int idxChannel, int idxNode, char szNodeName[32], char szNodeUnits[16]); missing idxNode Inside https://reference.digilentinc.com/waveforms/ref_manual FDwfDigitalInTriggerAutoTimeoutInfo(HDWF hdwf, double* psecMin, double* psecMax, int* pnSteps) but inside dwf.h DWFAPI int FDwfDigitalInTriggerAutoTimeoutInfo(HDWF hdwf, double *psecMin, double *psecMax, double *pnSteps); is pnSteps an int or double?

Hi Digilent, I installed the latest Waveforms on my Ubuntu Linux 20.04 computer. Inside /usr/include/digilent/waveforms/dwf.h I see ... typedef int DWFERC; const DWFERC dwfercInvalidParameter0 = 0x10; // Invalid parameter sent in API call const DWFERC dwfercInvalidParameter1 = 0x11; // Invalid parameter sent in API call const DWFERC dwfercInvalidParameter2 = 0x12; // Invalid parameter sent in API call const DWFERC dwfercInvalidParameter3 = 0x13; // Invalid parameter sent in API call const DWFERC dwfercInvalidParameter4 = 0x14; // Invalid parameter sent in API call But inside reference manual ... https://reference.digilentinc.com/reference/software/waveforms/waveforms-sdk/reference-manual Error Codes int Error Code Definition dwfercInvalidParameter0 5 Parameter 0 was invalid in last API call. dwfercInvalidParameter1 6 Parameter 1 was invalid in last API call. dwfercInvalidParameter2 7 Parameter 2 was invalid in last API call. dwfercInvalidParameter3 8 Parameter 3 was invalid in last API call. dwfercInvalidParameter0 = 0x10 is not the same as dwfercInvalidParameter0 = 5 Is this a typo or am I missing something? Thanks

Hey everyone. Senior Software Engineer and C/C++ programmer. I've been a long time user of the Analog Discovery 2 and now the Analog Discovery Pro. Can't wait to help the community. Charles