ADC1032.xls with USB Adapter

We are trying to run the ADC1032.xls macro with the ADC10 and the PICO
USB Adapter. The OS is Windows 98. Excel 97 gives "release" as 8.0a.

Stepping through the macro returns the following information:

ADC10/12/40/42 USB Driver V2.5
ADC-10 on USB-PP1
PICOPP.SYS V1.2

When adc10_get_times_and_values is executed, the following message
appears:

Assertion failed: (current_unit_ptr->state
==US_BLOCK_COMPLETED)||(current_unit_ptr->state
==US_BLOCK_FULL), file adc10usb.c line 595

Then "abnormal program termination" quits Excel.

This is with PICO software R 5.08.6 and the 5.09 download.
The USB operation is more of a convenience for our customers. The macro works fine with LPT1.

Thanks for the information,

We do know about this problem and are trying to resolve it by the next software web release (after 5.09.4), as you suggest, it only affects the USB operation, so using the LPT1 port is a temporary solution.

Best Regards,

Hi again,

It appears that this has already been fixed last year, try downloading the latest software again (download buttom at the bottom of this page). When you reinstall make sure you overwrite the previous installation. The file you are interested in, is adc1032.dll. Place this file into the same directory as your xls spreadsheet (overwrite the current one) and this should fix the problem.

If the error still occurs, send a PicoLog or PicoScope settings file to tech@picotech.com together with instructions on how you can easily repeat the crash.

Best Regards,

We are having the same problem with the ADC100.
The software opens the port (101) ok. But when trying to get data it gives a similar error:
Assertion failed: (current_unit_ptr->state
==US_BLOCK_COMPLETED)||(current_unit_ptr->state
==US_BLOCK_FULL), file adc100usb.c line 656

Then "abnormal program termination" quits Excel.

We are using the dll: adc10032.dll dated: 3/19/2003

The same error occurs when running adc10032 Visual Basic Project. Using the 'fast' option. 'Start slow' and 'Stop slow' work ok.

Hi,

Yes this problem does exist on the ADC-100, and is being addressed for a future software release. Keep an eye on our downloads page (see the button at the bottom of the page).

Best Regards,