NI MAX cannot see / looses network instrument

[Ray.R]

There appears to be a bug with NI MAX where a network instrument which was previously configured suddently dissappears and when we attempt to re-establish the instrument, MAX claims that it cannot find the instrument.

This was seen on 4 different stations, all sharing the similar behavior.  This was also seen at a completely different customer where the configuration was setup by a fourth person.  At client # 1 there are 4 stations.  They were setup by 3 different people using the same instructions.  Everything was fine on all 4 stations.  All of a sudden, the information dissappears from the network instrument list and it is not possible to re-configure the network instrument within MAX.  A similar behavior was reported by another client which is totally different than the first client.  NI MAX was configured by a different person than at client 1, possibly using different steps (although it is quite simple to setup a network device within NI MAX).

NI MAX at client #1 are versions 5.40f0 and 14.0.0a2.

NI MAX at client # 2 is version at least 14.0.0a2.

If we copy an exported settings file from another station, the network devices are restored and it is possible to use the network instrument.  However, if you attempt to setup the instrument manually, because MAX cannot find it automatically, it is not possible to validate the instrument and complete the setup.  Even if you cheat and complete the setup, the PC will not communicate with the instrument via VISA.  However, it is possible to communicate with the instrument outside NI MAX.  The instrument is seen by the PC and does respond to ping requests.

See image below.

 

When trying to validate the instrument, NI MAX responds with the fact that it could not open a VISA session via TCPIP.  

My first question is:  why does the instrument dissappear in the first place?

Rebooting the PC did not help.  Basic troubleshooting did not resolve the issue.  This is not the first time I work with NI MAX and with network instruments; however, this is the first time I see them dissappear fromNI MAX.  

I did not find anything while searching for posts for similar issues, so I do not know if anyone else has seen this.  I did encounter a similar description for a bug that was supposidly fixed in MAX 5.4

Does anyone at NI have a clue at how to make NI MAX more solid with respect to network instruments?

Thanks,

RayR

[Ray.R]

Correction:

NI MAX at client # 1 is version 5.5.  There is only one station which has version 5.4 and this station (with version 5.4) did not show the symptoms, yet.

[Rscd27]

Hello Ray.R

Can you give more information about the device. The error seems to be not very common. Specially since is responding to the ping. Did you have any changes in the network that could possible affect the functionality of the device?

Randy 

Applications Engineer

National Instruments

[Ray.R]

It affects a number of instruments, including an Agilent N5172B Vector Signal Generator and a powe supply by Associate Power Tech 7000 series.

The station was working fine.  There were no changes to the station or the network that I am aware of.

It was strange that it happened to multiple stations at one site, but to see it happen at a completely different customer by someone else... that makes it sound like a bug..

I do not know what other information to offer at this time.

[AnalogKid2DigitalMan]

Ray:

In your case, are there dependancies on any NI Services needing to be running?

I mention it because I have had 6 systems running without issues here for 8 years. Then late last year one system could not find the DAQ card after a reboot- the DAQ discovery service would not run at startup.

In the past couple months 3 other systems showed the same issue. Corporate or Windows updates would not permit the automatic services to be started.

Had to set it to delayed start and all all has been well since.

-AK2DM

[Ray.R]

Hello AK2DM,

I was just north of you last week in Sedona.  Beautiful place.  Our next trip in your area will take us to Phoenix.  We'll have to get together.  🙂

There are no dependencies on any NI Services that I am aware of.  A customer just reported a similar issue at their Penang CM site.  They are now in a bit of a panic.  I did not work on the code at that site, but 3 sites, 2 customers reporting the same issue???  That's not a coincidence.  Something is wrong with MAX.  The only way to recover is to import the configuration file within NI MAX.  It was impossible to simply scan for the instrument to get MAX to communicate with the instrument, although the PC, that has NI MAX installed, is able to ping the instrument.

I may have seen a similar issue a few years ago with another client where we kept loosing the network communication, but gave up and switched to GPIB.  At the time, we thought the network switches were causing issues and blamed it on the network.  Today, I may think otherwise...  I do not know what to investigate to verify why this is occurring.  Strangely enough, these systems ran for a year before we started seeing the symptoms.  I thought windoze upgrades was turned off...  It may be related to some recent upgrade, because we only started seeing these unusual behaviors since November (?).   I can't remember exactly when we first saw it. Late fall / early winter??

It is strange that you started seeing an odd behavior around the same time.  Running windoze, right?  I never liked windoze...  Everyone should move to Linux/Unix/Solaris.  LOL!  😉

[AnalogKid2DigitalMan]

Hi Ray:

Yes, Win 7 Pro 64. We get hit with just not MS updates but Corporate ones too.

Sedona, very nice, good mountain biking there too. Last time I was there in Dec 2010 we took one of those Pink Jeep Tours- in a heavy snowstorm to boot. Very cool!

PM me when the time comes to head out to Phoenix.

-AK2DM

[Jeff469]

I am seeing this problem also with NI-MAX 5.4. I am loosing networked instruments (mainly agilent power supplies) that have been on the stations for years. I am able to manually add them back via IP addresses however.