LabVIEW Real-Time Idea Exchange

[#1]

Many developers have the primary ethernet port of their development computer reserved for the corporate intranet/internet access.

Unfortunately, MAX and other tools like RT System Deployment Utility expect the targets to be connected to the same primary port for initial configuration, because they do not allow the specification of a local IP on which to exchange the UDP configuration packets.

Being able to select the ethernet port on which the RT system is connected, e.g. through a ring control populated with all available NICs and their local IPs, would facilitate devolopment enormously in such constellations, because the developer would not need to switch cables and IP configurations every time he needs to reconfigure the RT system.

Thanks,

Sebastian

[#2]

That feature would have saved me a lot of time in the past when I was unsuccessfully trying to detect unconfigured RT targets with MAX on some machines.

[#3]

Wow so many kudos in only 1 day.  I have my primary Ethernet port connected to my corporate intranet/internet access and my other static.  I use MAX and a RT system deployment utility every day and don't have any problems.  Can you please explain this problem in more detail?

[#4]

Hi dwisti,

once your RT system is configured, everything works fine even if it is connected to a secondary NIC. The trouble only starts with new or reset systems on 0.0.0.0, see e.g. http://digital.ni.com/public.nsf/allkb/E50CB56DBDA192E08625769B0074B09A?OpenDocument or http://digital.ni.com/public.nsf/allkb/471DB0C8F58725ED8625763B00677921?OpenDocument for similar effects with other systems...

Best regards,

Sebastian

[#5]

I don't have any trouble with new or reset systems on 0.0.0.0.  I can see the remote system on either subnet with MAX and set the IP address without any problems.  I've been using RT since Labview 8.5 and this has never been an issue on all the machines and laptops I've used.  Could this be a new problem?  What version of MAX are you using?

[#6]

Hello,

the problem occurs since Windows 7. UDP commands are transmitted to the default network adapter only. If the second network adapter is connected to an unconfigured RT target, the MAX is not able to find the RT target because of not UDP response. It is the same problem in the RT System Deployment Utility.

Best regards,

Daniel

[#7]

I'm using Windows 7 and still no problems here.  I don't want to sound like a stick in the mud here against new ideas but I truly do not have this problem.  What are the specific steps or setup used to cause this problem?  I can't seem to put my system in a situation were I can't see or change the IP address of my RT targets.  What does it mean by default network adapter?  How can I set a default network adapter?  If 26 people already kudo'ed the idea then many people must have this problem.  How is your system setup when your having problems?

[#8]

It looks like this issue was fixed in MAX 4.5 back in 2008.

http://digital.ni.com/public.nsf/allkb/4DA2BCEF4200FF1B862573A600741AF9

[#9]

Hello,

the problem still occurs in MAX 4.7 32bit with Windows7 64bit.

If two network adapters are mounted e.g. 1st ip: 172.40.80.173; 2nd: 192.168.0.1 (connected to RT) Windows 7 has a default communication order. This order can be set in the advanced network settings (only admin). Is the network adapter connected to RT not the 1st one, all UDP broadcasts commands are transmitted to the wrong network, because UDP still use the default network adapter if no one is specified. See LabVIEW help: http://zone.ni.com/reference/en-XX/help/371361G-01/lvcomm/udp_open/ net address: This function broadcasts only on the default network address.

Best regards,

Daniel

[#10]

Yes, but MAX is not written using these VI's.  It actually enumerates every network adapter and performs the query on each port.  So, MAX it self should not have this limitation. 

[#11]

Was this issue ever resolved?  I am having the same problem on my Wndows 7 development system.  I have two network cards, one for the corporate network, and the other connected to my sbRIO.  I tried all permeations of setup and all failed to see the card.  I tried disabling the primary card and connecting the rio to the secondary, no luck; disabling the secondary card connecting the Rio to the primary card, no luck; disabling the firewall (both while connected to primary and secondary), no luck; Also tried under my domain login and also in my local login, no luck.  I had to connect it to an old XP system to get the IP set.  WHat is blocking the 0.0.0.0 address on WIndows 7?

Regards,

Frank