PCMCIA-GPIB, errors 1073807195 & 1073807346

[jpkray]

I'm attempting to use LabWindows to take some measurements with an Agilent 53150A Frequency Counter. I'm using an NI PCMCIA-GPIB card. The device can be seen and queried in MAX (see attachment).

 Here are the exact errors from LabWindows:

 NON-FATAL RUN-TIME ERROR:   "AT53150a.c", line 253, col 12, thread id 0x0000154C:   Function viOpen: (return value == -1073807195 [0xbfff00a5]). The interface type is valid, but the specified interface number is not configured.

The above error only happens once. Then:

 NON-FATAL RUN-TIME ERROR:   "AT53150a.c", line 410, col 3, thread id 0x0000154C:   Function viWrite: (return value == -1073807346 [0xbfff000e]). The given session or object reference is invalid.

This repeats, but (I'm assuming) only because I'm repeating the measurement several times. I have to physically hit "continue" in order for the program to run at this point.

I can use NI Spy and see the errors happening (see other attachment). You'll notice after the first error, they repeat every six errors, again I'm assuming because I'm repeating my measurements. I've searched and found several other people having this problem in these forums, and have tried a few of the fixes to no avail. I think it's something with the driver as mentioned in other threads but I cannot figure this out. Any help here is appreciated. I'll be happy to provide more information when I can get back here, which will be tomorrow at the latest. Thanks for your time.

-Josh

[jpkray]

Ha! Figured it out. I had the address wrong in my code. Which is why it was talking in MAX but not when the code was running.

Please disregard. And I apologize for clogging the queue.

-Josh

[Justin_E]

Hey Josh,

Thanks for posting your solution to your issue! Hopefully this will help out future users who are also seeing this behavior

[qammer]

hi

could you please tell me where you put the wrong address

becasue i am getting the same error.

[Justin_E]

Hey qammer,

If you look at talking.jpg and NI Spy.jpg, you'll see that in one place he's trying to reference GPIB0::19::INSTR, and in another he's referencing GPIB2::19::INSTR. The talking.jpg screenshot shows that in MAX the device is listed as GPIB0::19::INSTR, so in his case the GPIB2::19::INSTR reference is invalid, within the viOpen command.