UDP Multicast Fix for Labview Runtime?

Hi All,
I am using the Labveiw Multicast vis and have been generally happy with the way they behave. Happy to provide any assistance to anyone who would like help with this in general as I think I have a bit of understanding on this now.
My problem is that when more than one socket is opened to the multicast address either by labview applications or other C++ applications, I get an error 60 which says that the IP address is in use.
I dug up an old posting (http://forums.ni.com/ni/board/message?board.id=170&message.id=107610&query.id=23434#M107610) which had a FANTASTIC solution for this from within Labview. Basically, editing the Labview.ini file allows sharing of the sockets and error 60 goes away when you are running vis within Labview.
My problem NOW is that the solution does not work for exe files built with application builder. I therefore have a vi happy to share sockets within labview but when I build this vi into an exe, it comes back with error 60 under the same test scenarios.
Is there some magic ini file somewhere for Labview Run Time 8.2? Any help would be much appreciated.
Cheers
Peter

The relevant INI file is the one for the application, so if your application is called FOO.exe, you should also have a FOO.ini in the same folder.
In that file you should have (or create) a [FOO] section and place the key in that section. This should work for most LV keys.
Try to take over the world!

Similar Messages

Is there a .sld file for LabView runtime engine when creating Embedded XP image

I'm looking for a .sld file to aid inclusion of LabView runtime engine in my embedded XP image. Has anyone already written one?

Hi,
unfortunately, National Instruments doesn't have any sld files for embedded OS'es, however, please checkout the links from the Lookout discussion forum, where someone was trying to do something similar.
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=506500000008000000AD5C0000&ECategory=Lookout
Although there's no definitive resolution to this thread, the person who answered has said he could be contacted.
Hope that helps
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

UDP multicast subscriber for RT using CVI 8.5

Does anyone know of a way to implement a UDP multicast subscriber on an RT system using CVI 8.5? I know that CVI 2009 supports UDPMulticastSubscribe/UDPMulticastUnsubscribe functions, but I'd rather not upgrade if I can avoid it.
Can this be done using the Windows SDK? Is it even possible?
--NDo
Solved!
Go to Solution.

The reason that the CVI library multicast functions weren't supported until version 2009 is that the underlying Windows SDK implementation provided by LabVIEW Real-Time did not support UDP multicast. This means that unless you have LabVIEW Real-Time 2009 on the system, multicast is impossible. It might be possible to install LVRT 2009 and use the Windows SDK directly, without upgrading to CVI RT 2009. I have not tried this, though, so I can't guarantee you won't run into problems.
Mert A.
National Instruments

Is UDP Multicast support in LV RT 8.6?

Is UDP Multicast supported in LabVIEW Real-Time 8.6?

No, this is definitely not "normal", it's an unfortunate example of mis-tagging the example VIs. VIs are tagged in a number of different ways in the example finder, the ones you mostly see are:
1. Written specifically for RT
2. Written specifically for LabVIEW (Host)
3. Written for LabVIEW but could still work on RT.
The multicast examples were tagged with the "Written for LabVIEW but could still work on RT" when they should have been tagged, "Written specifically for LabVIEW (Host)." We apologize for any confusion, we'll try to make sure this is fixed in the next release of LabVIEW.
-Danny

I have to send messages through UDP multicast and unicast from same port. In Labview I tried that it throws error. I heard it is possible by means of Datagram (UDP unicast and multicast) Port Sharing. How can it be achieved in Labview?

I have to send UDP multicast and Unicast messages to a remote port from a single source/local port. I tried by opening UDP unicast and multicast in the same port and got the expected error. I tried by opening a unicast connection and sending unicast messages.After that when multicast messages has to send I closed unicast and opened multicast in the same port.This is not throwing any error. But my requirenment is to comminicate with another application in C ++ which recieves this data, throwing an error of lost connectivity and both the applications are not abled to communicate properly.
In the other application with C++ this is implemented using port sharing. So how port sharing can be implemented in labview so that I can send both multicast and unicast messages from the same port?
Thanks in advance

UDP is a sessionless protocol, meaning that anyone listening on the specified port CAN receive the data. CAN because as you noted there is no guarantee in the protocol that it will be received. And if you send the data not to a specific address but a multicast address not only one computer can receive it but in fact every computer on the same subnet listening to that multicast address and depending on the TTL of the packet also computers in neighbouring subnets, although that last one is not a very reliable operation since routers can be configured to drop multicast packages anyhow despite of a different TTL saying otherwise.
Accordingly there is no real way to make sure that a receiving UDP port is not already in use, since you don't build up a connection. UDP is more or less analogous to shouting your messages through a megaphone, and anyone listening on the right frequency (port) can hear it. You do bind the sender socket to a specific port number but that makes little difference.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Unable to determine the install root path for the LabVIEW Runtime Engine

Hi,
i have an issue with using a LabVIEW interop assembly in a .NET application. I get an exception "Unable to determine the install root path for the LabVIEW Runtime Engine" when calling the assembly.
The little test program is attached below. It's called dotNETHost.exe. If you excecute the programm a dialog with an button appears. Clicking the button shall open another dialog (the LabVIEW Interop component). But the only thing I get is the exception message. The ZIP folder also contains the complete exception meassage (ExceptionMessange.jpg & ExceptionDetails.txt).
The Interop Assembly was built with LabVIEW 2011. We use Visual Studio 2010 and .NET 4.0.. The dotNETHost.exe.config file is prepared as mentioned in Knowledge base - Loading .NET 4.0 assemblies.
The Interop assembly contains only one simple dialog (loop is finished by clicking OK) without calling any other VIs or other DLL's. In case of this there's also no support directory generated by the build process.
I have no idea why it doesn' work. I hope anyone can help me.
Thanks in advance
Kay
Attachments:
Debug.zip ‏75 KB

This may be unrelated, but Labview and .Net4.0 dont work well together. Not yet anyway. I had to compile my assembly in 3.5 to get it to work.
Please read the following:
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/configuring_clr_version/
http://digital.ni.com/public.nsf/allkb/32B0BA28A72AA87D8625782600737DE9
http://digital.ni.com/public.nsf/allkb/2030D78CFB2F0ADA86257718006362A3?OpenDocument
Beginner? Try LabVIEW Basics
Sharing bits of code? Try Snippets or LAVA Code Capture Tool
Have you tried Quick Drop?, Visit QD Community.

Whilst updating itunes software to latest version I get runtime error R6034 and cannot get into itunes. Is there a fix for this problem?

Whilst updating itunes software to latest version I get runtime error R6034 and cannot get into itunes. Is there a fix for this problem?

Click here and follow the instructions. You may need to completely remove and reinstall iTunes and all related components, or run the process multiple times; this won't normally affect its library, but that should be backed up anyway.
(99376)

[svn] 3420: Fix for Runtime Configuration issues.

Revision: 3420
Author: [email protected]
Date: 2008-09-30 11:13:54 -0700 (Tue, 30 Sep 2008)
Log Message:
Fix for Runtime Configuration issues. If the destination is initialized, then you'll want to initialize the instance when it is created. Otherwise, you want to wait until the destination is initialized. Typically, when using runtime configuration, the destination is not initialized and the instance is not initialized, instead the properties on the instance are set.
qa: no
bug: n/a
checkintests: passed
Details:
modules/core/src/flex/messaging/Destination.java
* add an initialized flag and a method for retrieving the value
modules/core/src/flex/messaging/factories/JavaFactory.java
* fix typos in comments
modules/core/src/flex/messaging/factories/JavaFactoryInstance.java
* if the destination is initialized, then you'll want to initialize the factory instance when it is created
modules/core/src/flex/messaging/FactoryDestination.java
* if the destination was not initialized before the factory instance was created, the factory instance will be initialized when the destination is initialized
Modified Paths:
blazeds/trunk/modules/core/src/flex/messaging/Destination.java
blazeds/trunk/modules/core/src/flex/messaging/FactoryDestination.java
blazeds/trunk/modules/core/src/flex/messaging/factories/JavaFactory.java
blazeds/trunk/modules/core/src/flex/messaging/factories/JavaFactoryInstance.java

Hi JBKL, and a warm welcome to the forums!
For the Ethernet Location... Is that Interface dragged to the top of Network>Show:>Network Port Configurations?
It may be that the Router needs a Firmware update to keep up with the OS Updates... check online, don't trust any automatic checking feature in the Router.
Where are we now?

Is LabVIEW Runtime required for a DLL created by LabVIEW ?

Hi
Could some one advice me on this matter please.
I am trying to build a DLL for a set of functions created in LabVIEW. Now I am wondering if I need to use it with some other language like VB or C++, do I need to install the LabVIEW runtime of the same version as the original functions ?
Any settings required while creating the DLL ?
I am trying to create it in LV 7.0
Thanks in advance
Deepu.

Alright Mike,
Thanks !
I was hoping it would work without the LabVIEW runtime. Anyway, thanks for the quick reply.
Rgds
Deepu.

LV2011 udp multicast open error 54

Hi guys,
I'm working on conversion from LV8.6 to 2011 for one of my projects. One thing I found was that the UDP broadcast module no longer worked. After digging into the vi i found that the "UDP Multicast Read-Write Open.vi" did not work the way as in 8.6.
I used a net address string input of "172.16.1.234" (my secondary network card), after string-to-ip conversion it gave 2886730218. then the UDP vi gave an error 54 in LV2011. (in 8.6 this does not happen)
I even tried using 127.0.0.1 or with ONLY my primary network card enabled (172.22.1.100), it always gives error 54.
The only input to make it pass i found was 0.
I have attached a ss of my test vi. Thanks for your inputs.
LabVIEW 2011 newbie >.<
Certified LabVIEW Developer
Solved!
Go to Solution.

Thanks for the reply. I have also checked that example. Please note that in the example it doesn't have an input for the net address, which i assume labview 2011 will use 0.
I have also just received a reply from NI and confirmed it's a known bug in 2011. i will post it below.
I hope this finds you doing well. I am glad to hear that you are starting to upgrade to 2011 and I apologize for the issues you are seeing. I suspect you are using this on one of our Real-Time targets if so the good news is that this behavior has been documented in the form of a CAR (actually a
few): Broadcasts and the UDP Open VI have an INCONSISTANT behavior depending on the OS. Pharlap/Windows receive broadcasts when the "net address" terminal is wired while vxWorks/Linux don't. These CARs are scheduled as major incoviencience and will be fixed in a future version of LabVIEW as of now the work around is to simple not wire the net address field.
The CAR numbers incase you would like to see when they are fixed are:
257627, 233344,235444, 283205
LabVIEW 2011 newbie >.<
Certified LabVIEW Developer

WES7 UDP Multicast Open problem

Hi
I am using LabVIEW 2012 SP1 programming a TPC-2206 touch-panel computer running Windows Embedded Standard 7.
I have a fairly simple program which uses the LabVIEW "UDP Multicast Open" VI to open a Read-Only multicast port, then reads data continously from it using the "UDP Read" VI.
The routine works by calling the "UDP Multicast Open" VI and if successful, then entering a continous While-loop which reads from the opened port via the opened Connection-ID refnum. If unsuccessful at opening, the routine sits there waiting for the Open to succeed, displaying a message to the user that the network is not plugged in (or similar).
My problem is that if I open the port without a network connection, the open operation succeeds (which is great as its a multicast open and that seems like the right thing it should do), but subsequently when I plug in the network with good data being sent on it, I do not receive anything?! I would have expected data to be received if the port succeeded in opening, no matter what the initial condition of the connection.
When I tried this on Windows XP, I got a open failure which let me know the network was not plugged in. I subsequently programmed it to put up the flashing message and waited for a good connection such that "UDP Multicast Open" then succeeded. Subsequent reception was then good.
Is this a known difference between WES7 and WinXP and LabVIEW "UDP Multicast Open"/"UDP Read", or am I missing something?
Thanks for any help you can give.

Thanks for the reply. I have also checked that example. Please note that in the example it doesn't have an input for the net address, which i assume labview 2011 will use 0.
I have also just received a reply from NI and confirmed it's a known bug in 2011. i will post it below.
I hope this finds you doing well. I am glad to hear that you are starting to upgrade to 2011 and I apologize for the issues you are seeing. I suspect you are using this on one of our Real-Time targets if so the good news is that this behavior has been documented in the form of a CAR (actually a
few): Broadcasts and the UDP Open VI have an INCONSISTANT behavior depending on the OS. Pharlap/Windows receive broadcasts when the "net address" terminal is wired while vxWorks/Linux don't. These CARs are scheduled as major incoviencience and will be fixed in a future version of LabVIEW as of now the work around is to simple not wire the net address field.
The CAR numbers incase you would like to see when they are fixed are:
257627, 233344,235444, 283205
LabVIEW 2011 newbie >.<
Certified LabVIEW Developer

Running Datasocket in labview 2013 open labview runtime engine 7.0

Hello All,
I am trying to communicate with a COGNEX camera using Labview 2013. I am using Datasocket to read tags from cognex OPC server.
but when I open labview and run the code for the first time. An installer will automatically pop up trying to install labview runtime engine 7.0.
When i cancel the installation datasocket throws an error. Again if i run second time, datasocket works fine and communicate with cognex camera using OPC.
This problem comes everytime I open labview and run the datasocket. I cancel the installer. second time onwards when i run the code everything works fine.
This is actually annoying and i doubt how things will work when i make an executable.
Need help.
Is this due to datasocket version installed... how to resolve this.

Hi phil,
That is interesting that you were unable to find the offending key that the installation is having trouble with. Do you have Administrator privileges on your computer? You may even want to try to log in as the actual Administrator itself to make sure that you have access to all of the proper registry keys. Also, I was going to say that I do think you're right with Windows XP not having the Scanreg/fix function, but there are several free programs that you can download as registry checkers. You may want to try one of those to see if you can find the key and give it the proper permission.
As far as the other part of your question, the Run-Time Engines are very important for LabVIEW to be able to run, but the 7.1.1 Run-Time Engine should not be affecting a LabVIEW 8.2 installation as it will use the 8.2 Run-Time Engine. One thing that you can do is go into your Control Panel under Add or Remove Programs>>National Instruments Software and you can try and repair/modify your Run-Time Engine there. If you already have the 7.1.1 Run-Time Engine on your computer, this is where it will show up so you can make any changes you want. Also, if you go to www.ni.com and click on "Drivers and Updates" on the right, you will be able to find the Run-Time Engine there that you will need, but I would definitely try using a downloadable registry checker first before attempting to change any of the software that is currently on your computer. As stated in the Knowledgebase article, this is actually an error from Windows saying that the registry key does not have the proper permission settings, so I am reluctant to say that downloading the new Run-Time Engine from our website will help much. Please try some of these suggestions out and let me know how they work out for you. Thanks!
Regards
Noah R
Applications Engineering
National Instruments

UDP/Multicast Broadcasts

Hello,
I am interested in writing some P2P-ish type networking
applications which need to use UDP multicasting to discover other
participating hosts on the network. Does AS3 networking libraries
have the ability to do UDP and multicasting?
Thanks,
Brad

If you want the UDP connection to have multiple listeners:
- Open the file: LabVIEW.ini (it is most likely located in C:\Program Files\National Instruments\LabVIEW 7.x, where "x" is the version number.)
- Add the line: SocketSetReuseAddr=TRUE
- Restart LabVIEW. The changes should take effect.
If you do not want to have multiple listeners, but want to be able to have multiple writers to the same port, this does not apply. You can open different local ports so as not to generate Error 60 and then write to the same remote port without causing an error.
If you are trying to communicate with multiple devices using the LabVIEW UDP VIs where each device has a unique IP addresses that are both listening on the same port in parallel, you can do the following:
This error occurs because you cannot open multiple connections on the same local port. However, the local port and the remote port do not need to be the same. The local port is determined by the "port" inputs of the UDP Open VIs. The remote port is determined by the "port" inputs of the UDP Write VIs. For each write, set the remote port to the one on which the corresponding device is listening.
I would also recommend that you look at the following link:
http://zone.ni.com/devzone/conceptd.nsf/webmain/BB41313D7AB28CBD86256802007B8DC5?opendocument
Nandini Subramaniam
Applications Engineer
National Instruments

What is the difference between "UDP Multicast open.vi " and "UDP open.vi " ?

What is the difference between "UDP Multicast open.vi " and "UDP open.vi " ?

Someone correct me if i am wrong, the difference is "multicast"
-Based on my General Computer Network knowledge, multicast means sending data/packets to selected group of nodes. Which will be UDP multicast
-UDP open.vi might be for unicast which is to one node specifically.
-One more difference is in first one(multicast open), you have additional read,write and read write funcionality which is not available in normal UDP open.vi
Thanks
uday,
Please Mark the solution as accepted if your problem is solved and help author by clicking on kudoes
Certified LabVIEW Associate Developer (CLAD) Using LV13

Using UDP broadcast instead of UDP multicast on a LAN (multicast not working on a major UK ISP router)

I've built an Android app using Cirrus that allows users on a LAN to chat in Morse code! - You can find it on the Android Market by searching for 'Morse Intercom'.
It works fine on my network, lots of other networks, but not on probably the most popular fast broadband fibre network in the UK
A friend of mine has let me piggyback on her network from this provider, and the problem appears to be that the UDP multicast packets RTMFP transmits just aren't being put on the wireless network. FYI the multicast address I use is IP 225.226.227.1 port 32112 .
This is probably fixable in the router, but 99.5% of users will never mess around with the router (and why should they), and if possible I would like to fix this in RTMFP.
Is it possible for me to ask RTMFP to not use UDP multicast, but instead to use UDB broadcast for discovering peers on the LAN ? The problematical router (and all others?) supports UDP broadcasting.
I tried setting 'groupspec.ipMulticastMemberUpdatesEnabled = false;' but this just stopped the app working on anything! What is the purpose of this option?
FYI:
To connect without using Cirrus server assistance I use: nc.connect("rtmfp:");
The complete function I use for setting up multicasting is:
private function setupGroup():void
// Create a new Group Specifier object
//trace("setUpGroup: groupSpec = new GroupSpecifier('myGroup/groupA')");
trace("setUpGroup: groupSpec = new GroupSpecifier('" + MY_UNIQUE_GROUP_NAME + "')");
var groupspec:GroupSpecifier = new GroupSpecifier(MY_UNIQUE_GROUP_NAME);
// Enable posting
trace("setUpGroup: groupspec.postingEnabled = true");
groupspec.postingEnabled = true;
// Specifies whether information about group membership can be exchanged on IP multicast sockets
trace("setUpGroup: groupspec.ipMulticastMemberUpdatesEnabled = true");
groupspec.ipMulticastMemberUpdatesEnabled = true;
// Causes the associated NetStream or NetGroup to join the specified IP multicast group and listen to the specified UDP port.
//trace("setUpGroup: groupspec.addIPMulticastAddress('225.225.0.1:30000')");
trace("setUpGroup: groupspec.addIPMulticastAddress('" + MY_MULTICAST_ADDRESS + "')");
groupspec.addIPMulticastAddress(MY_MULTICAST_ADDRESS);
// Constructs a NetGroup on the specified NetConnection object and joins it to the group specified by groupspec.
trace("setUpGroup: group = new NetGroup(nc,groupspec.groupspecWithAuthorizations())");
group = new NetGroup(nc,groupspec.groupspecWithAuthorizations());
// Set the NET_STATUS event listener
trace("setUpGroup: group.addEventListener(NetStatusEvent.NET_STATUS,netStatus)");
group.addEventListener(NetStatusEvent.NET_STATUS,netStatus);
In conclusion - On a LAN with up to 250 or so hosts, I can't see why RTMFP shouldn't be able to use UDP broadcasting as an alternative to UDP Multicasting. Can it, and if so how?
Graham

Here's more information...
When trying to connect with a 3rd party product, the connection request is sent out to my ISP's DNS server with details of the service ID. Of course it won't find anything there.
So then is tries to use NBNS (Netbios Naming Service) on 192.168.1.255, and still can't connect. Then comes back with a TNS error. i tried TNSPING on this address, and it doesn't find it. I have no clue where it gets this address from.
WHY WON'T IT JUST CONNECT TO THE HOST MACHINE AS DEFINED IN THE TNSNAMES FILE???
PLEASE HELP!!!!

UDP Multicast Fix for Labview Runtime?

Similar Messages

Maybe you are looking for