TKDS30xx Driver Error Reporting

[Paul_Knight_Lockheed_Mart]

I am using the TKDS30xx driver to control a TDS3052C

Driver Revision:                          5.0.1
Driver Vendor:                            National Instruments
Prefix:                                        tkds30xx
Description:                                Digital Phosphor Oscilloscope

I am using the tkds30xx_WriteInstrData to send a command to the instrument.  My question is does the function return both driver error and instrument errors?  Or does it only return driver errors and you have to query the instrument for any errors?

My issue is that when I query the instrument with the tkds30xx_WriteInstrData(handle, "*IDN?") the driver return 0 and if I then query the instrument to check for errors, I get an error 410 query interrupted.

[Al.B]

Hi Paul,

The instrument driver error handler returns errors in the driver, not the instrument.  If you are not getting a correct result with the *idn? query, I would suggest testing your instrument in Measurement and Automation Explorer, or using the lower level ibrd() and ibwrt() functions in CVI.  If you are still having trouble, I'd recommend posting on the instrument control forum.  

Message Edited by Al B on 06-26-2009 03:43 PM

[Paul_Knight_Lockheed_Mart]

Thanks, that is what I thought, the driver does not report any instrument error.  I think this is a mistake.

There is nothing wrong with my instrument.  The issue is:

I do an instrument error check after each tkds30xx_WriteInstrData command.  This works find if the command is not a query, the instrument is not providing any response to the command.  So when you do the instrument error check, you don't get a 410 query interrupt error.

However if you use tkds30xx_WriteInstrData to send a query, any query, in my example I picked "*IDN?" the driver reports 0.  If you then query the instrument to see if the command caused a error before you do a tkds30xx_ReadInstrData you get a 410 query interrupt error because you ask the instrument for any error information before you read the data back from the query.

Most of the other instrument drivers I have been using have an InstrumentCmdQuery which sends does a Write and a Read in the same driver function.  This driver only has seperate write and read commands.