ID query -1074003951 with pressure Calibrator

[echarry]

Hello everybody, I´m trying to use a LV driver for a DPI515 Pressure Calibrator.  I downloaded this driver from the Druck download page. I got error -1074003951 from de Init.vi

I´m relative new to LV, but I know he´s trying to query its ID. The problem is the following: I have to uncheck and try to run it. Then I get this error. Then I check it back and try to run it twice. On the second time I don´t get an error, and the Get_Started.vi works perfectly. When I quit this VI and try to run the Init.vi again, i get the same error. I saw in the NI SPY, that the *IDN? string is reading "UNIT:PRES MBAR", instead of course of its ID (*IDN DRUCK, DPI515....). Obviously I´m writing before the *IDN? string before reading it. Anyone any ideas?

I´m using LV 8.0 and this driver was developed with LV 6.0 (says on Druck´s Internet page). Comm: RS232 VISA serial (9600/ none/ none/ 8 bits = for LV and the device).

Thanks in advance

Edgar Charry

[fsilveira]

Hi Edgard,

Have you tried to contact Druck to solve this problem? They must guide you on this issue. Also take a look at that driver's manual to find out how it must be handle.

Regards,

Fernanda Silveira.

[thehobbs]

There might be 'old' characters in the buffer from a previous query.  In the Initialize VI, it is possible that adding a VISA Clear after the VISA Open will solve your problem (see referenced Initialize template VI below).  Another thing to try is inserting a VISA Read before sending the *IDN? command.  This will read any old contents out of the buffer.

I have not looked at your driver, but you can try to take a look at the Initialize VI from the instrument driver templates that install with LabVIEW:

...\LabVIEW 8.0\instr.lib\_Template - Generic\Public\Initialize.vi

There is also code here that flushes the serial buffers that might be helpful for you.

At a worst case, you can disable the ID Query.  However, the 'old' data will still exist and eventually be returned as part of a future read.  If you got the driver from Druck, it would be a good idea to report the issue so they can fix it and prevent future users from experiencing this problem.