LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Reentrant execution of Keysight 34465A DMM?

Solved!
Go to solution

@1984 wrote:

Thx everybody for the useful insights.


Except for me, who had an entirely useless post.  😄

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 11 of 12
(209 Views)

@crossrulz wrote:

@James_W wrote:

You're own drivers is also very useful - It has caught out OEMs updating the F/W in the past and changing the way calculations are done on a customer system and invalidating a whole medical test system until the OEM fixed their F/W (using the OEM driver would not have caught that!)


Last year, I ran into sort of the opposite problem: the OEM driver broke due to an OEM firmware update.  Luckily, I was only using the OEM driver as an example as I developed my own driver.


I've had this as well.  Many (all?) of the Agilent drivers depend on the instrument model because, for some reason or other, the commands aren't consistent over the various models of the same type of instrument.  So if you get a firmware update, sometimes the ID strings are different and breaks the driver.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 12 of 12
(209 Views)