attila

Hi @martin1701 In case the USB device is not detected (hardware id/unknown) and this is due to the erased firmware, you need steps 1-4. Other possibility could be data signal contact issue (cable, plug problem), issue with the supply or damaged IC.

Hi @Hans_ESC The cursors are not accessible from script.

Hi @martin1701 I have not heard such problem with newer revisions but you could try the following procedure:

Hi @martin1701 It could be problem with USB cable or connector, the differential data lines not making contact. Try using other cable and computer plug. On EE revF or earlier boards, the problem could also be due to erased USB firmware. Do you have a revF or board? You can find this info on the bottom of the board under the Xilinx TI logo. You have the reprogramming application in private message and instruction in the following post:

Hi @Stretch You can find phase measurement under oscilloscope measurements add global measurement. The XY view does not have cursors.

Hi @Camarillo It is most probably the C2 ADG612 damaged, the first IC in the input path. The 2.7v is the maximum input reading with high gain, <= 500mV/div Sorry for the late reply, I'm off work this week.

Hi @slalps Good to hear it is working. Than you for the feedback.

Hi @slalps Probably the FTDI drivers/libraries are messed up on your system, causing application crash. This is the first time I see such... You can use the CDM uninstaller to remove the installed drivers: Readme: https://www.ftdichip.com/Support/Utilities/CDM_Uninst_GUI_Readme.html Application: https://ftdichip.com/utilities/#cdm-uninstaller Add the following products: 6001, 6010, 6011, 6014 (most common devices) and press Remove Devices. See picture below. Connect your device and install the driver from Windows Update or FTDI setup (it should be the same): Page: https://ftdichip.com/drivers/vcp-drivers/ Installer: https://www.ftdichip.com/Drivers/CDM/CDM212362_Setup.zip

Hi @1bioKAT The orientation was good but the direction not...

Hi @Camarillo According your measurements the offset DAC is working. I almost forgot that odd reading or output offset could be due to wrong calibration. Since the offset voltage is applied this it likely good, but please perform a "Load factory" and see the oscilloscope readings again to make sure the calibration is not culprit. Otherwise the 21V reading is likely due to damaged ADG612. The one for channel 2 is on the right side, the 16pin IC above the trimmers.

Hi @1bioKAT 2020-02-21_Encoder_Debug.dwf3work // Decoder c = rgData.length var pA = 0 // previuos encoder A value var cnt = 0 // initial phase/counter for(var i = 0; i < c; i++){ fA = 1&(rgData [ i ] >>14) // DIO 14 fB = 1&(rgData [ i ] >>15) // DIO 15 if(fA==1 && pA==0){ // encoder A rising edge if(fB==1){ // encoder B label indicates direction cnt++ }else{ cnt-- } } rgValue [ i ] = cnt rgFlag [ i ] = 1 pA = fA } function Value2Text(flag, value){ switch(flag){ case 0: return "X"; default: return (value > 0x7FFFFFFF) ? value - 0x100000000 : value; } } // Math 7 (Steps > 0x7FFFFFFF ? Steps - 0x100000000 : Steps)

Hi @1bioKAT Please post your workspace with acquisition data. Note the warning in the last screenshot "Samples were lost. Reduce sample rate" !

Hi @nikko I'm glad to hear it is working.

Hi @slalps 1. In the "USB Serial Converter" properties, make sure the "Load VCP" is unchecked: In case it is checked other application may try to use it as COM device, blocking access to it. 2. Make sure you have the latest driver installed: Reinstall WaveFroms and check the Adept Runtime section or install the driver manually: https://www.ftdichip.com/Drivers/CDM/CDM21228_Setup.zip Reconnect the device in order the new driver to be loaded. 3. The USB EEPROM might be erased by other USB development applications. In this case use the "My device is not listed", reprogramming option in WaveForms Device Manager.

Hi @slalps This looks like a PC/OS issue... The AD2 should be detected as "USB Serial Converter" in Windows's Device Manager. Do you see such or "unknown device" showing up when you conned the device? It may take a minute to be detected as "unknown device"...

Hi @1bioKAT Use the following code to follow the phase, encoder steps: // Decoder c = rgData.length var pA = 0 // previuos encoder A value var cnt = 0 // initial phase/counter for(var i = 0; i < c; i++){ fA = 1&(rgData [ i ] <<0) fB = 1&(rgData [ i ] <<1) if(fA==1 && pA==0){ // encoder A rising edge if(fB==1){ // encoder B label indicates direction cnt++ }else{ cnt-- } } rgValue [ i ] = cnt rgFlag [ i ] = 1 pA = fA } function Value2Text(flag, value){ switch(flag){ case 0: return "X"; default: return (value > 0x7FFFFFFF) ? value - 0x100000000 : value; } } In the Scope Math channel you also need to convert to signed value: (Encoder > 0x7FFFFFFF ? Encoder - 0x100000000 : Encoder) Edit: The insert code is not working and I just notice the indexing text ( [ i ] ) was removed. Now I added these with spacing...

Hi @nikko In case it is an F or earlier revision the USB firmware could be corrupt. See the following instructions and try to reprogram with the Windows application you have in private message.

Hi @Camarillo I meant measuring the VOFF_SC2 relative to the device GND with external DMM. Having the scope channel 2 range 500mV/div or lower, changing the offset between -2.5V and 2.5V should change the VOFF_SC2 between ~1V and ~3V Above 500mV/div for offset between -25V and +25V change VOFF between ~1V and ~3V.

Hi @laurent In case your script quits the device gets closed and the outputs stopped. Set the following parameter before opening the device to keep it running on quit/close: dwf.FDwfParamSet(DwfParamOnClose, c_int(0)) # 0 = run, 1 = stop, 2 = shutdown The VIO could be stopped due to over-current. See the SDK/ samples/ py/ AnalogIO_DigitalDiscovery.py

Hi @nikko The device looks to be detected by the OS correctly. I'm not sure how critical the "Resource temporarily unavailable (11)" info is... Did you install the digilent.adept.runtime and digilent.waveforms packages ? https://reference.digilentinc.com/digilent_adept_2 https://analogdiscovery.com/ Do you get any error when you lunch the application ?

Hi @Ferda You can find the latest manual, corresponding to the software version in the SDK installation:

Hi @Camarillo Probably some high voltage transient input or accidentally having the probe at 1x with high voltage damaged the ADG612. Before replacing the ADG612 you could verify the VREF_SC2 and VOFF_SC2 voltages. https://reference.digilentinc.com/reference/instrumentation/analog-discovery-2/reference-manual#scope_reference_and_offset - the VREF should be about 2V - the VOFF with: 0V offset about 2V +2.5V offset with 500mV/div range about 3V, like the screenshot below --2.5V offset with 500mV/div range about 1V Some further troubleshooting posts:

Hi @Ferda The minimal differences between in AD1-2 are the analog io, power supplies and monitoring:

Hi @1bioKAT I forgot to mention that the values/flags are stored and represented by default as unsigned 32bit integer. In case you use signed values have the following in the Value to Text code: return (value > 0x7FFFFFFF) ? value - 0x100000000 : value;

Hi @nikko The entire board, including the USB controller is powered from the 12V power supply. Make sure this is working correctly. Does the lsusb list "ID 1443:0007 Digilent" device ?