SystemLink Forum

cancel
Showing results for 
Search instead for 
Did you mean: 

Some client GPIB assets are missing (not detected?) from server

Solved!
Go to solution

I have certain GPIB connected instruments that are not showing up in Asset Manager. I can communicate to them without issue from client SW. Also they show up in NI MAX and respond queries there. What is the best way to debug why I'm not seeing these in Asset Manager?

 

Some of the makes of these instruments that don't show up are Chroma, Krohn-Hite.

 

~ Bertram

0 Kudos
Message 1 of 13
(2,902 Views)

Do those respond to the typical "IDN?" query?

Santhosh
Soliton Technologies

New to the forum? Please read community guidelines and how to ask smart questions

Only two ways to appreciate someone who spent their free time to reply/answer your question - give them Kudos or mark their reply as the answer/solution.

Finding it hard to source NI hardware? Try NI Trading Post
0 Kudos
Message 2 of 13
(2,886 Views)

@santo_13 wrote:

Do those respond to the typical "IDN?" query?


Good question. Yes.

0 Kudos
Message 3 of 13
(2,882 Views)

First, make sure you have NI VISA and NI-488.2 installed. Then, manually run Scan for Instruments in MAX locally on the client. Finally, the *IDN? has to return a serial number for the instrument in a way that NI-VISA can parse. If the serial number doesn't show up in MAX then it won't be tracked as an asset in SystemLink because we have no way to uniquely identify the instrument at that point.

0 Kudos
Message 4 of 13
(2,867 Views)
Solution
Accepted by topic author !SuperB!

If that doesn't work here is an example on how you can manually add additional assets on the client-side by populating some JSON files in a specific directory. You can use this mechanism if you have some other process for querying the instruments.

 

https://github.com/joshuaprewitt/systemlink-asset-management-api

0 Kudos
Message 5 of 13
(2,849 Views)

I appreciate the feedback.

  • NI-VISA is installed (version 19.0.0)
  • NI-488.2 16.0 is installed (version 16.00.49152)
  • Manually ran scan in MAX locally on one of the clients
  • Querying the instrument with *IDN? returns "Chroma,6314A,0,02.31,16,0
    "