0XBFFF003F A format specifier in the format string is invalid ( NI Spy file included )

[Kobi_K]

Hello ,

I am Trying to init my 8808a fluke using the NI Driver , function - fl8808_InitWithOptions("ASRL1::INSTAR", VI_TRUE , VI_TRUE , "Simulate=0,RangeCheck=1,Quary..=1,Chache=1" , &fl8808)

But I'm getting the following error : 0XBFFF003F A format specifier in the format string is invalid .

I have attached a NI Spy file the *ESR? command Reads the Event Status Register ( User Manual http://us.fluke.com/Fluke/usen/Support/Manuals/default.htm?ProductId=55446 )

I cant understand why i'm getting this error and is it the CVI or The Fluke, any ideas ?

Thank YOU

Kobi 

[jrmyers]

Hello KobiKal,

I beleive there is an error in the instrument resource string. Try "ASRL1::INSTR".

Joe

[RobertoBozzolo]

Hi KobiKal,

I never used your instrument, but having integrated a 8846A into a testing equipment of ours there are some things I want to point you to.

In the command you are using there are some odd characters that I suggest you to check: could it be that you retyped the command in the post instead of copying and pasting it from actual source code? Anyway, I have highlighted in red the parts of the command that sound strange to me:

fl8808_InitWithOptions("ASRL1::INSTAR", VI_TRUE , VI_TRUE , "Simulate=0,RangeCheck=1,Quary..=1,Chache=1" , &fl8808)

Keep in mind that the message-based instruction set you are using is very powerful and can be tested directly from some communication program like hyperterminal before attempting to use the VISA driver (see user maual, page 4-6 and after). Additionally, the driver normally adds some checks and additional instructions that in the initial step of communication may be confusing. I suggest you simply test communications either with hyperterminal op writing some simple lines of code in the Interactive execution window to test wether the communications is succesful or not; after being sure it is OK you can come back to the driver and check the command you are using.

As an ultimate resource, if the driver is distributed with source code you can execute it step-by-step trying to understand where that error arise and investigating on it.