LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

shared variables - multiple networks

Solved!
Go to solution

Hi,

I am having problems publishing shared variables to the correct network in a multiple network configuration. (NIC1, NIC2, Wireless)

I've followed the info in Deploying Shared Variables to a Specific Network Card 

For a Windows-based system: If one does not already exist, create a file in the C:\WINDOWS directory named logos.ini and add the following lines to the file: [LOGOS] ServiceBindTo=XX:XX:XX:XX:XX:XX where XX:XX:XX:XX:XX:XX is the MAC address of the Ethernet card to want to bind to.

 

Right-click on My Computer within the LabVIEW Project Explorer, click on Properties. Under the General tab, click the Specify Custom Address checkbox, and enter the IP address of the network card that the shared variables will be deployed to.

 

but this is for 8.2.1 - is it still relevant for 8.5?

After these changes my shared variables still get deployed to the default (wireless)

I am running XP on both computers and LabVIEW 8.5

0 Kudos
Message 1 of 5
(3,264 Views)

My temporary solution at the moment is to disable the wireless network and fortunately the network that becomes default is the correct one. Once the VI is running I can then re-enable the wireless network.

How do I select the correct network to deploy my shared variables to?

I specify a custom address in "LabVIEW project" | My Computer | Properties | General but this is ignored during deployment of the shared variables.

My IP addresses for the network cards in my PC are 192.168.0.99, 192.168.1.99 and 192.168.2.99 so surely defining the custom address will also define the card that I am intending to use?

Any help would be appreciated.

Al

0 Kudos
Message 2 of 5
(3,250 Views)

some help would be appreciated...

 

"How do I select the network card that the shared variables will get deployed to on a multi network card PC?"

0 Kudos
Message 3 of 5
(3,219 Views)
Solution
Accepted by topic author Al1234

Hello Al,

 

I think you may have to just change your default interface card.

Here is an article that should help you further:

http://digital.ni.com/public.nsf/allkb/FB4B94AE226BEA2986257559006D0FF1

 

And also, point number 8 on this refers to a similar troubleshooting route:

http://digital.ni.com/public.nsf/allkb/6E37AC5435E44F9F862570D2005FEF25

 

I hope this helps,

Let me know if the issue persists.

Kind Regards,

Michael S.
Applications Engineer
NI UK & Ireland

Message Edited by sahpek on 11-02-2009 11:01 AM
Message 4 of 5
(3,198 Views)

Thanks Michael that fixes it!

 

0 Kudos
Message 5 of 5
(3,192 Views)