06-14-2011 12:55 PM - edited 06-14-2011 12:56 PM
Using MAX Devices and Interfaces, Network Devices, I have a device connected, I can ping it manually from Start run window. Under Network Devices Hostname or IP Address shows the proper IP address of the test equipment. But under Actual IP address it says unknown.
Test equipment is an Aeroflex 3920 and LabVIEW 2009.
06-14-2011 01:07 PM
My question is this, how do I enter or edit the greyed out box to put the IP address in there. It also does not let me validate since the IP address is undefined.
06-15-2011 11:14 PM
Hello,
MAX will typically not show 3rd party devices. It is designed for devices with NI devices which it does not appears this device is. It sounds you are conneted to the device since you ping it.
Regards,
Patricia B.
06-16-2011 06:25 AM
Actually, this is for a co-working who is having this problem with the same equipment as I have. I am actually communicating without any problems. I have tried to duplicate my set up on her computer as well as I can but she is getting the IP address portion greyed out where mine shows the IP address and is working properly. We duplicated everything we could think of to be as close to my setup.
06-16-2011 07:13 AM - edited 06-16-2011 07:16 AM
Is her machine set up the same as far as network addresses, etc. She on the same sub-net, etc.? As far as the post about MAX being for NI instruments, that is generally true, as far as plug in DAQ, etc., but when you are trying to set upVISA TCP/IP resources and similar you definitely can configure them in MAX. Can you post a screen shot of the MAX screens (".png" format please!), ideally of both working and non-working instances.
N4KSS, Mark? WA2UPA
10-04-2012 01:56 PM
Mark here.
I'm unable to ping my 3920 now.
I'm unsure why. I made too many changes to the system and not sure where it stopped.
It isn't a MAX issue though. It is IP related. MAX can see all my other equipment but my Aeroflex 3920.
The 3920's format is TCPIPO::XXX.XXX.XXX.XXX::1234::SOCKET"3920" all my other equipment has been simple to set up.
It might have something to do with it being a socket. I don't know. I am pretty sure it on the eithernet side since I can't even ping it now.
10-05-2012 01:31 PM
It sounds like there could be any of a number of things wrong. There are some useful things in this KnowldgeBase article, even though your instrument isn't the exact same kind:
http://digital.ni.com/public.nsf/allkb/abe4bc247e8ac9bc8625734e005cab42?OpenDocument