Unable to acquire serial COM1 lock on Fluke 45 in LabVIEW

[Albert.Geven · Accepted solution]

I checked the basic serial read and write and see that it opens the port and immediately writes the string followed by a wait and then a read.

Maybe this is too fast because sometimes a break is sent out that can upset the fluke.

So maybe add a wait after the open of the serial port.

I saw that by default the string is in \codes display so I beleive that that was OK.

Another possibility is to use the advaced serial write and read. That offers a wait because you can write later.

[ndbs]

I was just experimenting with delays and have found that this appears to be the issue.

Funnily enough, this appears to be an issue with the Fluke 45 driver example VIs too.  Over RS232 serial communication, the DMM does not respond quickly enough.  I'm not sure if this issue exists using other communication protocols.

Thanks for your help.

[ndbs]

To add on, the initialization command in the Fluke 45 driver causes an error using the default setting every time.  It appears that when the driver uses an ID query in the initialize command, it times out or otherwise fails:

Error -1074003951 occurred at an unidentified location

Possible reason(s):
Fluke 45 Initialize
The ID Query failed. This may mean that
you selected the wrong instrument or
your instrument did not respond.
You may also be using a model that is
not officially supported by this driver.
If you are sure that you have selected
the correct instrument and it is
responding, try disabling the ID Query.

Disabling the command results in successfuly initialization.

There also appear to be a few other issues with the driver (getting strange measurement values), but I'll have to troubleshoot separately regarding that or just use VISA commands.

[Albert.Geven]

good work

please write to the instrument driver group when you found out what really happens.

Thanks for being so stubborn to keep trying

[Shawn_S.]

Hello,

Yes, please write instrument.drivers@ni.com when you have more details on the initialize and measurement issues.  We would be very interested in helping resolve the issue and then revise the driver, if necessary.