I've got a new NI GPIB-USB-HS adapter to use together with my old self written WB software.
The software works fine with AT-GPIB/TNT both for ISA-bus and PCI-bus.
The OS is Windows 2000.
If I run it with GPIB-spy I get these results.
1. ibdev(0, 16, 0 (0x0), T3s (12), 1, 0x0000)
Process ID: 0x000000E4 Thread ID: 0x00000824
Start Time: 12:28:31.258 Call Duration: 00:00:00.016
ibsta: 0x100 iberr: 0 ibcntl: 0(0x0)
> 2. ibclr(UD6)
> Process ID: 0x000000E4 Thread ID: 0x00000824
> Start Time: 12:28:31.274 Call Duration: 00:00:00.000
> ibsta: 0xc100 iberr: 6 ibcntl: 4(0x4)
The iberr is EABO (6)
If I run Measurement & Automation Explorer on the same computer with the same instrument I get these results in Spy:
1. ibdev(0, 16, 0 (0x0), T10s (13), 1, 0x0000)
Process ID: 0x000005A8 Thread ID: 0x00000760
Start Time: 12:32:11.274 Call Duration: 00:00:00.016
ibsta: 0x100 iberr: 0 ibcntl: 0(0x0)
2. ibclr(UD0)
Process ID: 0x000005A8 Thread ID: 0x00000760
Start Time: 12:32:11.290 Call Duration: 00:00:00.015
ibsta: 0x100 iberr: 0 ibcntl: 4(0x4)
Do you have any idea how to track this down. If i debug my software step by step and looking in GPIB-Spy I can see exactly the
same API-calls been sent by my application as well as NI Measurement & Automation Explorer. But my application generates EABO (6) and NI Measurement & Automation Explorer works just fine with no errors.
Best regards
/Marcus
