LabVIEW
The ID Query failed (-1074003951) in Keysight MSOS804A
@LTBALAZS wrote:
Hello
I am having "The ID Query failed (-1074003951)" issue with LMG95 power analyser, since i got new developer PC.
Old labview version: Labview 2016
New labview version: Labview 2016 f7
Can this issue be caused by the difference of labview versions? The project is the same as before.
Kind regards,
Balázs
After seeing your post and reviewing the original post, the issue the OP was having is just as they said, the capital letters returned by the ID string were causing the ID to fail. I extracted out the part of the driver where the match first string comparison is done and changed the prefix array to all caps and the match worked.
So basically, you need to double check in the initialize VI, first of all, if your specific device is listed (compatible) and secondly, make sure that the value returned by the ID matches the value in the prefix array (letter case, spacing, etc). This assumes the drivers were created by NI and follow a similar format as the drivers above.
@aputman wrote:
@LTBALAZS wrote:
Hello
I am having "The ID Query failed (-1074003951)" issue with LMG95 power analyser, since i got new developer PC.
Old labview version: Labview 2016
New labview version: Labview 2016 f7
Can this issue be caused by the difference of labview versions? The project is the same as before.
Kind regards,
Balázs
After seeing your post and reviewing the original post, the issue the OP was having is just as they said, the capital letters returned by the ID string were causing the ID to fail. I extracted out the part of the driver where the match first string comparison is done and changed the prefix array to all caps and the match worked.
So basically, you need to double check in the initialize VI, first of all, if your specific device is listed (compatible) and secondly, make sure that the value returned by the ID matches the value in the prefix array (letter case, spacing, etc). This assumes the drivers were created by NI and follow a similar format as the drivers above.
I find many, many HP/Agilent/Keysight drivers suffer from this issue. I even found a case where new firmware reported a string different enough not to find a match with the strings they were using in the driver!
@aputman wrote:
@billko wrote:I find many, many HP/Agilent/Keysight drivers suffer from this issue. I even found a case where new firmware reported a string different enough not to find a match with the strings they were using in the driver!
And they are usually NI certified. 🙄
NI Certified does not guarantee the driver will work, it is the driver developer's responsibility
Certification just ensures compliance with the guidelines, so, you cannot quote "NI" on anything unless it is an "NI Driver"
Here is how you can get anything certified to be on IDNET - https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000015CfoSAE&l=en-US
