Last AT/GPIB/TNT driver version built with DECL-32.h ?

[gpibtester]

I realize that the problem goes away with NI Spy. However I am interested to see what GPIB calls are made by the application to see if some of the calls are overriding any settings made in the Configuration Utility. And maybe just seeing what calls the application makes might help figure out where the problem is. For instance, is the application looking for RQS using ibwait or ibnotify? How close is the read call being issued after the write?

gpibtester

[precaud]

OK. I've attached the capture of the calls made after starting up the HTBasic driver.

I am unable to capture the stream during data transfer; as soon as I stop the capture, the computer locks, and everything is lost...

[gpibtester]

Thank you for the exported capture file! It's too bad that you were only able to capture were the startup calls.

Looking at the startup calls, it doesn't look like anything is overriding the timing settings. That at least tells us something.

We'll see what else we can come up with, but right now, I don't have any other suggestions of what to look at or try.

gpibtester

[precaud · Accepted solution]

Problem solved, by leaving the card set up for INT 11 and switching the properties in the NI driver setup for each requirement. Turns out the HP NA is happy with the card interrupt jumper is on, as long as interrupts are disabled and serial polling is turned off in the card properties in the device manager. For HTBasic, re-enable the interrupt and serial polling. Minor inconvenience, but it works fine.

gpibtester, thanks for your help with this. Much appreciated.

[gpibtester]

That's great that you found a workaround! I thought you only had executables and were not able to modify code, so I am glad to hear that you are able to enable and disable interrupts using HTBasic.

I've been conferring with a developer who is still thinking about the information that you provided last week and I have informed him of your workaround. If he comes up with any suggestions or questions, I will post them.

In the meantime, I remembered that there were some changes that affected timing between TNT4882AQ and TNT4882BQ chips (http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/What-are-the-differences-between-TNT4882AQ-an...). I would be curious about what chip you have on the AT-GPIB/TNT boards. If you want, you can post which chip you have (and if you need help in knowing where to find the info on the chip itself, I can post that). But I'll leave it up to you as to whether you want to look into the chip aspect of the problem. I don't guarantee that I'll be able to do anything once I get that information. Like I said, I'll leave it up to you.

Thanks for posting the information about your workaround! And if we have any additional suggestions or questions, I will post them here.

gpibtester