NI MAX Network Device doesn't show information (serial number, vendor, etc.)

[Marcel_K]

Hello,

I'm facing an issue in NI MAX (20.0), which isn't important for functionality of the system. It's more about the maintenance, because we're collecting the data (serial number, firmware, vendor, etc.) of the devices in our system for our database. The used devices are all present in NI MAX, but sometimes some of the network devices are not recognized correctly as shown in the attached screenshot. In this case PS1 and PS3 are recognized as N6770C and N5772A, but PS2 is only named with its VISA Ressource.

I've already reinstalled NI-Visa (20.0) as well as the IVI Driver for PS2 and the driver is also assigned to the logical name of the device. I also deleted the device and tried to connect it again, everytime with the same result that it shows up without its details. We have another system with the exact same software and hardware, but without this issue. The import of the configuration file of this system didn't bring the solution either. 

Does anybody have an idea?

Thank you in advance for your help! 

[rolfk]

There is no attachment, but there is no standardized way of querying instrument information. Most modern GPIB instruments will respond to the IEEE 488.2 command syntax and support device specific SCPI commands in addition to that. But these are conventions that are followed by many instrument manufacturers but long not by all. And modern network or serial port connected device often also respond to these commands but again many do not.

NI-MAX simply tries to send this *IDN? command to all devices it knows about and tries to interpret the response. If the device knows this command and responds with the comma separated list of device identifiers as defined by the IEEE 488.2 standard then it will work, if not there is no easy fallback mechanism for NI-MAX to try something else.

Some (rather old) HP devices used the command ID, to query for this information but the response was rather arbitrarily formatted so not easy to parse for device name, firmware version number, and serial number (if present at all). But there are devices that require VER (with or without question mark) or some other arbitrary command to query SOME information which may or may not contain a device name an/or serial number.

[Marcel_K]

Thank you for your answer. Now the attachment should be working. 

Your explanation is very good, but I think this isn't the problem I'm struggling with. The affected device is a power supply from keysight and it worked fine on windows 7. Now we're trying to run the same setup on windows 10.

[Clemens151]

You should read this out may this help you https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P70YSAS&l=en-IN 

VW Credit Login