Data socket port

I want to serve data sockets over the internet. I can get them to work over our local network (all the computers are 192.168.1.100, etc), but they're not working beyond our local network. Do I need to forward port requests on our router to enable this (we just have a simple DSL modem and a router)? In Labview, looked under Tools >> Options >> Vi Server Configuration and see Port 3363 listed. Is this the port that data sockets work on? If so, do I just need to configure the router to forward port 3363 requests to my computer that is running the data socket server?
Alex

Hi Alex,
It sounds like you have the right idea. Datasocket uses port 3015, so you should be able to forward requests to this port to a certain local IP address. The links below might be of some help to you:
Error 63 When Using DataSocket
http://digital.ni.com/public.nsf/websearch/CE62D869535D602F86256D330060F5F1?OpenDocument
What Ports Do I Need to Open on My Firewall for National Instruments Software Products?
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/fe6a63983ac8289e86256b22005a067a?OpenDocument
Hope this helps,
Travis H.
LabVIEW R&D
National Instruments

Similar Messages

Problem with data socket server

We have developed a program (from LabVIEW 6.1 running on Windows NT) consisting of a main executable and four other executables dedicated to collecting various i/o information. The four i/o executables convert raw data into process data and pass it on to the main executable using Data Sockets. The data is assembled as a cluster, then flattened into a string, which is published to a data socket variable. The data cluster contains a time stamp used by the main executable to verify i/o is being updated periodically (at least once a second). The main executable generates an alarm if the timestamp gets to be more than 5 to 15 seconds old, depending on the expected data. Typically, this alarm never happens, unless an i/o device is powered down o
r disconnected, or an executable or Data Socket Server is terminated.
The problem we are is experiencing is that false alarms are being generated, at precise intervals of exactly 5 days, 18 hours, 1 minute, and 1 second. The alarm condition occurs then clears immediately. The only thing I can think of is the data socket is somehow "cleared" for some reason at this interval, causing the main executable to momentarily read a time stamp of zero, and generate an alarm. Is there anything that might be corrupting the data sockets at a long interval like this? The worst thing is that the alarm horn gets falsely triggered, so we are trying to resolve this but can not see anything in any of the code to cause such an occurrence.
Thanks in advance for your help.
Brian Hajder
Despatch Industries
8860 207th Street West
Lakeville, MN 55044
Phone: 952.469.8111
Fax: 952.469.4513
[email protected]

Hello Matt,
Thank you for reading & responding. I should try to summarize this specific application in a little more detail.
We have built a manufacturing tool for a customer that is controlled by a single Windows NT PC, for which we have developed 5 executables using LabView 6.1. The main executable provides the user interface. The other four executables are dedicated to control & monitoring of specific i/o devices (serial or IEEE-488). The i/o executables pass data to and receive commands from the main using data sockets. The PC is not on any type of network. The main executable supports an optional SEMI standard host link through its ethernet port, but that is not currently active or connected. A total of 13 data sockets are used, to implement si
mple "one way" traffic through any socket, making buffering unnecessary. Some data sockets (i/o data to and from main) are updated a few times a second at most, commands from the main may only be updated a few times a day.
Data from each of the i/o executables includes a time stamp indicating the last valid i/o hardware read time. The main uses this data from each i/o executable to determine whether i/o hardware is responding properly - if the timestamp gets to be anywhere from 5 to 15 seconds old (depending on which i/o is being checked), an i/o failure alarm for that device is raised.
What seems to be happening is that, periodically, precisely every 496,861 seconds, two or more of the timestamps are found to be too old; I am assuming some external event is momentarily clearing socket data & the zero value timestamps look very old, thus triggering alarms at the exact same second. The alarm conditions clear up in less than one second.
I wonder what you mean by "the datasocket
server resetting"? Is this documented anywhere?
Thanks for plowing through this wordy description, I appreciate any help you can suggest.
Brian

Problems with data socket connection

I have two computers on a network both running labview. I would like to
exchange the value of a variable in both directions. For example
computer A sets the variable to a certain value, computer B reacts and
changes this variable. Computer A now reads the new value.
So I tried this using (front panel) data sockets but I could not
establish a connection the way I want it. Also I couldn't find answers
here or in the labview help file, so I hope you can give me a short
hint on how to do that (do I need to run socket server on both
machines? What IP address do I need to enter in the front panel dialog?)
Thank you very much,
Michael

Thanks for the Port number, I got it to work now.
I will summarise what was necessary to establish a connetion in case other people are interested:
If you need a bidirectional communication between computer A (IP:192.168.0.1)
and B (IP: 192.168.0.2) the following steps may be necessary:
- Run DataSocket Server on *both* computers before you start LabView
For communication A to B:
- Select a variable on computer A, and enter the following in the connect to field:
   "dstp://192.168.0.1/var1", click on "publish"
- Create a variable of the same type on machine B and enter in the connect to field:
   "dstp://192.168.0.1/var1", click on "subscribe"
For communication from B to A do the following:
- Select a variable on computer B, and enter the following in the connect to field:
   "dstp://192.168.0.2/var2", click on "publish"
- Create a variable of the same type on machine A and enter in the connect to field:
   "dstp://192.168.0.2/var2", click on "subscribe"
Maybe this is not the most elegant way because I don't know how to use the "Publish and subscribe" field
but at least it works this way.
Michael

What is the purpose of open/close connection data socket?

Hello everyone,
I am writing and reading values in OPC Server through data socket. What is the purpose of open/close connection data socket when writing /reading a value? Without the open/close connection element, it still work correctly. I am writing values in the server thru event stucture.I do not need any buffered reading or writing. What will happen if I didnt not use the open/close connection? Maybe it may cause some problems in my program which i didnt realise?
And I have attached an example of my program. Thanks
Yehchia
Attachments:
Test Event.vi ‏11 KB

Hi YehChia,
I was talking about something like that:
1. Not good. since with every iteration the DS connection needs to be opened and closed.
2. Good. Since you open the connection only once then do the reads and close it afterwords.
Christian

Can I send data from a PC to another PC using Data Socket Servers?

I need to send an array to a computer. Both computers use LabVIEW. The computer that writes the information also runs the Data Socket Server. What I want to do is read that array from another computer via internet. So the main issue is: Can I read from a Data Socket Server via internet?
I'm writting the array using the dstp where I'm supposed to type the URL.

Integrating the Internet into Your Measurement System – DataSocket™ Technical Overview
Found using a simple search.

Data socket problems with LVRT 8.2

I am in the process of migrating to LV 8.2 from LV7.1.1. My system has 18 RT targets which send data to a Host PC through data socket (DS). The Host PC runs LV on Windows XP Pro. With LV7.1.1 on both host and RT targets DS works perfectly. The RT targets update the host every 500 ms.
I've taken a three-step process in the migration. First tests were done with the host migrated to LV8.2 while keeping the RTs at LV7.1.1. Result: the system worked perfect. Then I changed one RT to 8.2 keeping the rest the rest at LV7.1.1. Result: DS timed out before all the data could be sent to Host. Finally, all RTs were migrated to LVRT 8.2. Result: Only about 5 out of the 18 RTs report to the Host before DS times out. However, if only one RT target is used, i.e., the other 17 RTs are diasbled, communication is very fast. Is there a special setting that I need to make? Btw, the roughly 5 RTs that report vary randomly from test to test, i.e., there is no bias towards any particular RTs.
I am using the same source code developed under LV7.1.1, so the only changes made are the ones that take place when one opens LV7.1.1 code in LV8.2. Some VIs get converted in the process.
Any ideas?
Chatonda Mtika
Algis Corp
Vancouver, Canada

Ben,
I must say I am very surprised by Nadim's email. His point, which I must say I don't agree with, was made quite clear to me yesterday during a conference call between my team and the NI team comprising Chris, Nadim, and Avinash. So I don't know what purpose this morning's email is supposed to serve. Be that as it may, I think NI has gotten it wrong here. I do not think it should be one or the other. The discussion forum is a much wider forum comprised of people with varying experiences - not just NI employees. That is precisely why I posted my problem to the forum: to tap into the vast experiences of the discussants. But when I did not get any responses after I had posted answers to Nadim's questions, I decided to make a formal service request to NI, all perfectly legal. So I was really surprised when I was being blamed for tying up NI resources on one problem. I believe the resource allocation issue should be NI's to solve, not mine. I have no way of knowing that NI had formally assigned somebody to my problem. What if nobody from NI responds, am I allowed to make a service request to NI? My feeling is that NI's logic is flawed here, assuming Nadim's views are NI's views.
Thanks,
Chatonda Mtika
Algis Corporation
Vancouver, Canada

How can I read realtime data from a data socket using DIAdem

I am currently routing data from an instrument using LabView 7.1 to a data socket. I was trying to figure out how to access that data in real time in DIAdem through the data socket. Another option would be to use the downloaded LabView/DIAdem VI package, but I haven't figured out how to get that to work either, despite the forums here. I would prefer to access it through the data socket, if possible, as the amount of information being transferred is negligable (a string and a double).
Thank you,
Sinan Sutcu

You have to use one of the ScriptDAC blocks. In your case, as you would like to fetch data from a LabVIEW vi, choose the out of the driver input palette. Inside the configuration dialog you can generate a sample script, which is then copied to the windows clipboard. It contains a lot of function prototypes which will be automatically called later during the measurement.
Basically, the init functions are called during the start of the measurement - here you should connect to the activeX server, the deinit functions are called when stopping the measurement - disconnect from the server here.
Then there is the function SFD_Readchannel, which is called once for eych tact and each channel you configured. Here, you should exchange the data with your VI.
I am attatching an example I wrote to control a LabVIEW vi (doing a counter output operation)- that is why the data exchange works the other way around, but I hope it explains the principle.
Additionally I am adding documentation about the ScriptDAC driver interface.
Regards
Ingo Schumacher
Systems Engineer Sound&VibrationNational Instruments Germany
Attachments:
MultiCounterOut.zip ‏995 KB
Script DAC Driver.zip ‏734 KB

Error while starting the Wily : A socket port was already in use

Hello,
When I strat the Wily intro scope I am getting following error.
Kindly help me resolving this issue.
er3esu31:p43adm 4> nohup ./runem.nohup.sh &
[1] 20549
er3esu31:p43adm 5> Running Enterprise Manager with IHOME=.
Running Enterprise Manager with JAVAPATH=/usr/sap/ccms/wilyintroscope/jre
java version "1.5.0.03"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0.03-_13_feb_2006_16_39)
Java HotSpot(TM) Server VM (build 1.5.0.03 jinteg:02.13.06-21:25 IA64, mixed mode)
log4j:ERROR Failed to flush writer,
java.io.InterruptedIOException:
        at java.io.FileOutputStream.writeBytes(Native Method)
        at java.io.FileOutputStream.write(FileOutputStream.java:260)
        at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
        at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)
        at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:408)
        at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152)
        at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213)
        at com.wily.org.apache.log4j.helpers.QuietWriter.flush(Unknown Source)
        at com.wily.org.apache.log4j.WriterAppender.subAppend(Unknown Source)
        at com.wily.org.apache.log4j.RollingFileAppender.subAppend(Unknown Source)
        at com.wily.org.apache.log4j.WriterAppender.append(Unknown Source)
        at com.wily.org.apache.log4j.AppenderSkeleton.doAppend(Unknown Source)
        at com.wily.org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(Unknown Source)
        at com.wily.org.apache.log4j.Category.callAppenders(Unknown Source)
        at com.wily.org.apache.log4j.Category.forcedLog(Unknown Source)
        at com.wily.org.apache.log4j.Category.log(Unknown Source)
        at com.wily.util.feedback.backend.log4j.Log4JBackend.log(Log4JBackend.java:139)
        at com.wily.util.feedback.ADefaultModuleFeedbackChannel.doLog(ADefaultModuleFeedbackChannel.java:545)
        at com.wily.util.feedback.ADefaultModuleFeedbackChannel.logbottleneck(ADefaultModuleFeedbackChannel.java:524)
        at com.wily.util.feedback.ADefaultModuleFeedbackChannel.log(ADefaultModuleFeedbackChannel.java:479)
        at com.wily.util.feedback.ADefaultModuleFeedbackChannel.error(ADefaultModuleFeedbackChannel.java:313)
        at com.wily.util.event.ListenerTracker.sendEventToOneListener(ListenerTracker.java:148)
        at com.wily.util.event.EventPump.immediateDeliverEventIfListenerNotDead(EventPump.java:152)
        at com.wily.util.event.EventPump.immediateDeliverBroadcastEventAsync(EventPump.java:123)
        at com.wily.util.event.EventPump.access$300(EventPump.java:23)
        at com.wily.util.event.EventPump$Posting.deliver(EventPump.java:512)
        at com.wily.util.event.EventPump$EventPumpThread.run(EventPump.java:760)
Introscope Enterprise Manager failed to start because:
A socket port was already in use (see the log for the port number)
Press 'Enter' to acknowledge....
[1] +Stopped (tty input) ./runem.nohup.sh
Thanks & Regards
Girish

Hi
Check whether introscope is already running. if it is then kill that process manually and start willy again.
You use the following command to check whether any other program is using the same port
netstat -an | grep -i listen | grep 80

Outbound IDOC( Error passing data to port)

Hi,
We have an interface running daily configured such that the idocs are converted to files and placed on a directory path.
All the idocs are processed successfully but for one hour the idocs failed and the error message says:
Status: Error passing data to port
Error at OPEN (Directory path) with operating system error msg.:No such file or directory.
The missed data from the error idocs have been sent via PFAL.
But again after this one hour the idocs were successfully posted for the same directory path.
Please let me know what the issue can be here or how can we avoid this.
Thanks.

Hi
*Some times it may happen that IDOC doesnt reach to the port , in case if you are using Transactional RFC port so*
*you can use the report RSEOUT00 for sending the IDOC to port .*
*Hope it may help you .*

Error in Production Load: Error passing data to port

Hello All,
I got this unexpected error in production. The Jobs are still processing for a long time(in Yellow status) with the error message :
Extraction (messages): Missing messages      (Status:Yellow)
     Missing message: Request received      (Status:Yellow)
     Missing message: Number of records sent     (Status:Yellow)
     Missing message: Selection Completed     (Status:Yellow)
Transfer (IDocs and TRFC): Missing messages or warnings           (Status:Yellow)
     Request IDoc : Application document posted                (Status:Green)
     Info IDoc 2 : sent, not arrived ; Error passing data to port      (Status:Yellow)
     Info IDoc 3 : sent, not arrived ; Error passing data to port      (Status:Yellow)
     Info IDoc 1 : sent, not arrived ; Error passing data to port      (Status:Yellow)
I went through the below forumn, and asked the basis to look in to it. In the meantime can any one please suggest me any solutions.
Some problem with IDoc's Settings while loading data

Hi Ram,
The problem may be with the connection to the source system you are loading the data from. You can check the connection using the note 140276.
Best Regards,
Des.

Create OPC I/O server and front panel data socket problem

Hi all!
I installed the NI OPC server. When I try to create a new server I/O in a LabVIEW project I don't see the "OPC client" possibility.
Is something software missing?
Other question: I tryed to connect to OPC server using front panel data socket but my problem is same. When I click the numeric control and I go to the "data operation" menu there is no possibility to make data socket connection.
I don't know what is the problem.
I attached two pictures about my problem.
Solved!
Go to Solution.

Dear vajasgeri1,
do you have LabVIEW DSC module installed? Without it you will not have the OPC client funtionality.
And to configure DataSocket binding you need to go to the Data Binding tab in the Properties of a control.
BR,
Mateusz Stokłosa
Applications Engineer
National Instruments

Data Socket related Crash

Greetings,
I have an LV 8.6 HMI that performs Data Socket reads
from Network Shared Variables. I am finding that it works well until I
try to shut down and close all the DS references. I can usually get
away with this
once, but if I try to restart the application I often
will not be able to reopen the DS reference and it will always crash
when I try to shutdown again. I have narrowed it down to just DS opens
and closes
and the problem persists. Attached is the error message
that pops up when LV crashes, not much to go on but any ideas would be
greatly appreciated.
Attachments:
DS Related Error.PNG ‏10 KB

Hello,
Which version of Windows are using? There are some cases in the past with NT that relate to this error because windows was updated. A Microsoft KB explains that here.
This also may be an issue with the Shared Variable Engine having a conflict with the firewall or antivirus software. You may need to go through this document to configure your windows firewall if you already have not.
National Instruments
RIO Embedded Hardware PSE
CompactRIO Developers Guide

Data Socket

I am reposting this message and hope someone can help me....
I have been using Data Socket to pass information from a control computer
to two
remote computers. At various times throughout the day the connections, between
the control computer and the remote computers, are being dropped (the number
of connections drops from 3 to 1). The remote computers still believe that
they are connected to Data Socket, however they are no longer receiving updated
data. Has anyone else experienced this? Does this seem like a "network
traffic" issue?
Any help is appreciated.
Thanks,
Ari

I got this answer from another question posted on the NI website. I don't know if it will help but it seems like this may be the same problem.
Jeff M. on 8/8/2001 answered:
"There isn't a limit to the number of packets that the datasocket server can handle. What I surmise is happening (had this happen to me) is that the power savings features on your system are turning on (system goes to standby) and this basically disables the ability for the server to function and kills datasockets."

Data socket buffer overflow detection

Hello,
I plan to use data socket to access SharedVariables. I started with the example Buffering.vi from the Shared_Variable_Buffering.lvproj shipped with LabVIEW 2009 SP1 (DSC-Module).
This example leads to a read buffer overflow caused by the high speed write loop and low speed read loops. The interesting part is, that reading the SharedVariable values using a SharedVariable-Node delivers a warning for that buffer overflow situation. But, the DataSocket-Read doesn't deliver any warning or error and I didn't find a way to detect the overflow. Does someone know how to get this done?
Thanks for your help.
Thomas

Hello Maria,
thank you for your reply.
It took a while, but today I checked out the Variable Client - Server.lvproj example shipped with the newest LabVIEW. And I was surprised to find even another possibility to interact with Shared-Variables: the new VI's contained in the DataComunication/SharedVariables palette (used by the Variable Refnum API Client.vi in the example).
And with the DSC-Module, another possibility is available: the also new VI's contained in the DSC Module/Tags palette (try the DSC Tag API.lvproj example, but don't forget to manually deploy the libs before starting the VI's).
So, plenty of possibilities available. It will take some time to realize the advantages (or disadvantages) of each one, especially for the new VI's.
Let's see what possibilities we gain with LabVIEW 2010...
Regards,
Thomas

Data Socket Connections Dropped

I am using Data Socket to pass information from a control computer to two
remote computers. At various times throughout the day the connections, between
the control computer and the remote computers, are being dropped (the number
of connections drops from 3 to 1). The remote computers still believe that
they are connected to Data Socket, however they are no longer receiving updated
data. Has anyone else experienced this? Does this seem like a "network
traffic" issue?
Any help is appreciated.
Thanks,
Ari

Hey Rick,
This is a bit of a labor-intensive answer, but it will help you with any future DataSocket programming you want to do. Read through this DataSocket Tutorial to get started. You will probably also need some information on configuring a DataSocket server after you read through the tutorial. Hope this helps!
Cheers,
kgarrett

Data socket port

Similar Messages

Maybe you are looking for