DataSocket

I get the following error:
"Error -2147467263 occurred at Nicht implementiert
in DataSocket Select URL.vi->Browse To OPC Item.vi"
when using the shipped example "Browse To OPC Item.vi"
in LabView 2012 SP1 (64 bit) (12.0.1f2).
Something missing ?
Mathias Hucke
Solved!
Go to Solution.

Hi Stephan,
the example is located under
NI Example Finder => Communicating with external applications => OLE for Process Control => Browse to OPC item.vi.
see also the screenshots attached.
thanks,
Mathias
Attachments:
Browse OPC front panel.jpg ‏95 KB
Browse OPC code.jpg ‏45 KB

Similar Messages

Sir i am using datasocket read ,i am communicating with java but my problem is that bcz im using while loop to see if value has changed my labview consumes all the processors time ,sir i want a event like thing so that while loop is not in continuous loop

sir i have given lot of effort but i am not able to solve my problem either with notifiers or with occurence fn,probably i do not know how to use these synchronisation tools.

sir i am using datasocket read ,i am communicating with java but my problem is that bcz im using while loop to see if value has changed my labview consumes all the processors time ,sir i want a event like thing so that while loop is not in continuous loopHi Sam,
I want to pass along a couple of tips that will get you more and better response on this list.
1) There is an un-written rule that says more "stars" is better than just one star. Giving a one star rating will probably eliminate that responder from individuals that are willing to anser your question.
2) If someone gives you an answer that meets your needs, reply to that answer and say that it worked.
3) If someone suggests that you look at an example, DO IT! LV comes with a wonderful set of examples that demonstate almost all of the core functionality of LV. Familiarity with all of the LV examples will get you through about 80% of the Certified LabVIEW Developer exam.
4) If you have a question first search the examples for something tha
t may help you. If you can not find an example that is exactly what you want, find one that is close and post a question along the lines of "I want to do something similar to example X, how can I modify it to do Y".
5) Some of the greatest LabVIEW minds offer there services and advice for free on this exchange. If you treat them good, they can get you through almost every challenge that can be encountered in LV.
6) If English is not your native language, post your question in the language you favor. There is probably someone around that can help. "We're big, we're bad, we're international!"
Trying to help,
Welcome to the forum!
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Problems with enumerated type and DataSocket

I am publishing an enumerated type variable using DataSocket write and I am having problems subscribing to this with other clients on the network. I can get the program to work ok if I replace the enumerated type with a straight numeric or a Text Ring for example. Is there anything special I should be looking out for when using enumerated types in this type of application.
Thanks Kelly

Updating to the latest version of LabVIEw (6.0.2) should correct this problem:
http://digital.ni.com/softlib.nsf/websearch/F983BDA17B8F401B862569EC005A11C2
Also, I would suggest updating to the latest version DataSocket:
http://digital.ni.com/softlib.nsf/web%2Fall%20software?OpenView&Start=1&Count=500&Expand=6#6
Chris_Mitchell
Product Development Engineer
Certified LabVIEW Architect

Datasocket error when network cable unplugged

Hi,
I'm having problems with my datasockets. I have applications running on multiple computers, which publish data to a datasocket on the localhost. Whenever we unplug a network cable, or the network goes down, the datasocket write function reports the following error code: -2147014843 in Datasocket Write.
I can't find any information about this datasocket error code. Can anyone give me advice on how to find more information about this error code?
The result is that whenever there is a network issue, we need to go and resolve it, then we need to log onto each computer (25+) to get the datasockets working again.
Also interesting to note is this problem has only presented itself since upgrading the computers from NT to Win2k & WinXP.
Thanks for any help that can be given.
Slade Squire

Hi again,
Just in case anybody else looks here, and have a similar problem...
The error code we saw was related to the networking functions of Windows. In particular, the reason we did not see this problem in Windows NT, but it started appearing in 2000/XP, is the media sense functionality of Windows 2000/XP. In 2000/XP, if there is no connection detected, the OS dumps the IP stack, and with it, the IP address. As a result, when we try to write to a datasocket on the computers IP address, Windows returns an error, since there is no IP address anymore.
To resolve this issue, we turned off Media Sense on the affected computers. We followed the instructions on this page:
http://www.windowsnetworking.com/articles_tutorials/Disable-Media-Sense-TCPIP-Windows-XP.html
Now, when the network drops out, we keep the same IP address, and so the datasocket can continue to write to the local computer, without any problems.
Regards,
Slade Squire

Datasocket does not work with two network cards

If I have two ethernet card in a PC. The Datasocket server does not work if the second card is enabled. It keeps displaying resolving IP Address. I am wondering if there is a solution for this problem.
Thanks

Thanks for you reply. One card has a static address(10.20.35.1), which is used for Data socket, and the other card uses a dynamic IP address. The card with dynamic address is only used for connecting the PC to the company’s network.
The second card, when turned on causes the Datasocket server problem. In the Datasocket Server manager I have only two IP addresses under Permissions Groups. (10.20.35.1 and 10.20.35.11. 10.20.35.11 is the IP address of the remote PC with labview application. The Datasocket is used to transfer data between the two PC’s)
I am wondering if my set up for hosts in Datasocket Server manager is not correct.

How to read enumerated values from an OPC server via Datasocket

Hi Labviewers,
I am using LV8.2 and I am trying to find if it is possible to read enumerations from an OPC server via Datasocket, not just the values.
I can successfully read a value for an OPC server via Datasocket and I get a value for example 3, is it possible to get the enumeration/string that corresponds to this value i.e. "Open".
Many thanks in advance
Dimitris

Hi Sarah,
With the input type as variant I get the following response:
1                                     <-This is the current numeric value of the parameter
4 Attribute(s):
   'Quality' -> 192
   'TimeHigh' -> 29861723
   'TimeLow' -> -665408304
   'Timestamp' -> 39.238E+3
With the Input set to         Enum constant I get no values or strings coming back. With the Input set to             Ring constant I just get the numeric value
Dimitris

Cannot create a VI equivalent of a boolean front panel indicator/switch directly connected (subscribing) to a datasocket

I am attempting to create a boolean output from a simple boolean datasocket source the VI's is attempting to subscribe too. But for some reason it does not seem to be able to determine the boolean value from the data received. This VI was designed from the standard example DS Reader with Attributes.vi. Although I have tried many other approaches and can't get it to work. I'm not sure if i'm handling the datatype correctly. I'm pretty new to Labview too!
Attachments:
DS_Boolean_Reader.vi ‏37 KB

I finally worked it out myself! Silly me...I just had to put the indicator inside the loop so it was constantly updated I guess! The learning curve can be steep for this no structured text language. I'm still not convinced it is faster than coding the old way. :-)
Attachments:
DS_Boolean_Reader.vi ‏37 KB

Datasocket connection failure requires restart of VI

I'm using LabView RT 8.5 together with a cFP-2110. I have shared variables hosted on the cFP, as the cFP application works by itself without the need of a host PC application. However, a host PC application can be connected and read/write shared variables to work as a GUI. The shared variables are accessed with Datasocket VIs, as the same application is to be used on different cFPs with different IP addresses.
The Datasocket connections is opened once and then the variables are accessed in a while loop. Before accessing the variables, RT Ping Controllers.vi checks if the cFP is still accessible. If not (or if the Datasocket Read operation fails), the Datasocket connection is closed. Now here comes the problem. When I want to re-establish the connection with Datasocket Open, I only get Error 66 (Connection closed by the peer). The only way I have found to "reset" this behaviour, is to close/stop the host VI and start it again. Is there an easier way to solve this? I assume the reason lies in something not being reset in the connection between the PC and the cFP. But what, and how can it be reset? Note that I have closed the connection with Datasocket Close in case of a failure.
I do not need answers about how I can avoid the connection failures in the first place. They can e.g. be caused by the cFP being temporarily too busy or something. The issue is when a failure HAS occurred, I want to be able to re-establish the connection without restarting the VI. How?

Isn't there anyone with similar experiences?
I would assume that someone would be interested in being able to restore a connection after a failure. Improving connections to minimize the risk of failures is not anyway a 100% solution. Sooner or later a failure will occur. And in that case I am not pleased with having to restart the application in order to get the system back on track.
I have already tried searching for previous posts regarding this, but the search results are very poor. Any ideas?
Tom C

Error 63 occurred at DataSocket Write in getWavelength_v80 EDITED.vi, help? please!

Hey guys, I am new to LabView and I have thought myself everything that I know. I am an undergraduate student at NC A&T.
Okay so I took a peice of code that I acquired from Bristol, and it's for a Bristol Wavemeter V1.22. I first edited it to get a graph in there to show the data, and get a slope and Y intercept. Now I am trying to connect it to a computer that controls a COntinuum ND6000. We have existing code for the ND6000 that lets the two computers connect. I took the code out of there that was the part that connects them and now when I wired everything up, I get the "Error 63 occurred at DataSocket Write in getWavelength_v80 EDITED.vi" error message. it states; Possible reason(s):
LabVIEW: Serial port receive buffer overflow.
=========================
LabVIEW: The network connection was refused by the server. For TCP/IP, make sure the server is running and listening on the port you are trying to use. Firewalls can also cause a server to refuse a connection. For VI Server, make sure you have enabled VI Server from Tools>>Options>>VI Server:Configuration."
I tried making sure everything in the configuration was correct and it all is. Can you guys please help me?
Thank you.
I have attached the folder that it is located in because you do have to have the library function. The file is located in the Bristol Wavelength Meter V1.22\Programming Interface\LabVIEW example I.
Thank you again!
Solved!
Go to Solution.
Attachments:
6.jpg ‏153 KB
7.jpg ‏112 KB

So I went through and realized that I had the wrong port typed in by 1 number, I changed that and put in the correct port for the TCP address. Now when I run it I get this error message 66....
"LabVIEW: The network connection was closed by the peer. If you are using the Open VI Reference function on a remote VI Server connection, verify that the machine is allowed access by selecting Tools>>Options>>VI Server:Machine Access on the server side."
Any help?? I checked the Server Machine access and all of them are set to allow.

Front Panel DataSocket takes long time to connect

Hi,
I have build a very simple DataSocket application.(Front panel DS only)
I transferring data between two applications running on 2 PC's connected via a wireless network
What hapens to be is when the router is connected to internet (via ADSL modem) the connection between clieant and server is established imidiatly.
However when Modem is disconnected it takes about 1 minute to establish connection.
At both cases I am using the internal IP of the server PC (the PC datasocket server is running on)
1. I used 2 different wirless routers and result is the same
2. I used static IP addres on both client and server PC's
3. DSTP url I use is "dstp://l192.1.128.106/number" (not computer name but rather ip number)
4. datasocket server is running on one commputer. The other (client) is running under Runtime (its an "exe" file)
5.When I look at data socket server I see that "process connected" is updated immediately. BUT the front panel controls are waiting for about a minute till datasocked LED is turns green. During this time the datasocket server looks very busy.
I have to emphasis again when the router is connected to internet connection is established immediately.
My gut feeling tels me it has to do with DNS. I don't usderstand why.
Is is related to the server PC DNS?
The client PC DNS?
The router DNS?
Any help would be extremely appreciated!

Thanks again Kyle, I have followed up some of you suggestions. With some trial and error (and a fiew bucks...) the problem was solved. The way I solved it: 1. I bought a new router (Edimax BR-6424 ~$40)2. I have configured the PC the Datasocket server was running on, as with dynamic IP and obtain DNS automayicaly. The router was not connected to Modem and everything is working fine. (if you look at atached VI - "time to establish connection was about 2S. This is the VI I am running on the client PC) Alternate 2. is configure static IP BUT LEAVE DNS VALUES EMPTY. that works fine too. (2S for connection) When I used static IP with some values in DNS the time to establish conection was ~16S. Aperrantly my problem was not related to modem at all.I have made my test with one bad (or misconfigured) router (level one WBR-3406TX).The test I made with the other router (old Edimax I borowed from a friend) were with bad DNS configuration.So I got wrong impression that my problem was related to absence of modem. I am going to use the new router. But just for curiosity. Do you have any Idea what could get wrong with the old router (level one). The DNS was configured correctly. (obtain DNS automaticaly) but still when I ran the attached VI it took 16-20 S to establish connection.??? Best regards, Hazkel
Attachments:
Dataocket Example.vi ‏11 KB

DataSocket memory leak problem (2VO0SF00) -- more info?

When upgrading to LabVIEW 8.5 recently, I noticed the following known issue in the readme file:
"ID: 2VO0SF00
DataSocket/OPC Leaks Memory using ActiveX VIs to perform open-write-close repeatedly
If you call the DataSocket Open, DataSocket Write, and DataSocket Close functions in succession repeatedly, LabVIEW leaks memory. Workaround — To correct this problem, call the DataSocket Open function once, use the DataSocket Write function to write multiple times, and then use the DataSocket Close function."
Looking back, I think this problem may have been present in previous LabVIEW releases as well, and might be giving rise to a problem that's been dogging me for quite some time (see my thread, "Error 66 with DataSockets", http://forums.ni.com/ni/board/message?board.id=170&thread.id=187206), in addition to general slow/glitchy behaviour when my VI's have been running continuously for a long time. But in order to determine whether or not this issue affects me, and how I should go about fixing it in the context of my own programs, I need a bit more information about the nature of the issue itself and the inner workings of the DataSocket VI's. Any help or insight the community can provide into this would be greatly appreciated!
Here are my questions:
It is my understanding from the "known issue" description above that the memory leak happens when you have a DS Open wired to a DS Write wired to a DS Close, all inside a loop (example 1), and that the suggested workaround would be to move the DS Open and DS Close functions out of the loop on opposite sides, wired to the DS Write which remains inside the loop (example 2). Is this correct?
Does this leak also happen when performing DS open-read-close's repeatedly (example 3)?
What happens when a DS Write (or DS Read) is called without a corresponding DS Open and DS Close (examples 4a and 4b)? Does it implicitly do a DS open before doing the write operation and a DS close afterwards? What I'm getting at is this: would having an isolated DS Write (or DS Read) inside a loop, not connected to any DS Open or DS Close functions at all, cause this same memory leak?
If one computer is running the DS server and a second computer is running the VI with the repeated open-write-close's, on which computer does the memory leak occur?
In my question #1 workaround (example 2), the DS Open and DS Close outside the loop are routed through a shift register and in to and out of the DS Write inside the loop. If the DS connection id goes into the DS Write "connection in" and then splits and goes around the DS Write and out to the DS Close, without coming out of the DS Write "connection out" (example 5), will the memory leak still be avoided? I.e. if the DS Write function doesn't have anything connected to its "connection out", will it try to do an implicit DS Close?
If the VI causing the memory leak is stopped, but LabVIEW stays running, will the leaked memory be reclaimed? What if the VI is closed? What if all of LabVIEW is closed?
FYI, in the examples above "x1a" is a statically-defined DataSocket on the DS server running on the computer Max, to which the computer running the example VI's has read/write access. My actual application has numerous VI's and hundreds of DataSocket items, many of which are written to / read from every 50-100 ms in the style of examples 4a and 4b.
Does anyone have any idea about this stuff?
Thanks in advance,
Patrick
Attachments:
examples_jpg1.zip ‏63 KB
examples_vi1.zip ‏40 KB

Hi Meghan,
Yes, some of the larger VIs in my application do write to / read from several hundred DataSockets, so it's not feasible to use shift registers for each one individually, and hence why I'm passing the references into an array, etc.
Your Alternate Solution 2 is more along the lines of something that would work for me. However, my actual code has a lot of nested loops, sequences and DataSocket items which are not all written to in the same frame, so this solution would still be difficult to implement: it would be cumbersome to unpack the entire 500-element reference id array and build a new one (maintaining the positions and values of the unaffected elements) every time I write to some small subset of the DataSockets.
I think I have a solution which solves the problem and is also scalable to the size of my application -- I've attached it as Example 7. Do you think this will avoid the memory leak? It's the same as your Alternate Solution 2, except that instead of building a new array out of the DS Write reference outs, each reference out replaces the appropriate element of the original array.
If I understand you correctly, in order to avoid implicit reference opens and closes, a DS Write needs to have both it's reference in and reference out wired to something. Thus, even though my Example 7 replaces an element of the array with an identical value, and therefore doesn't actually change the array (which would be a silly thing to do normally), the DS Writes have their reference outs wired to something, and eventually in a convoluted way to a DS Close, so it should avoid the memory leak.
Just out of curiosity (I don't think anything like this would apply to my application or any fixes I implement), when would the implicit reference close happen in the attached Example 8? The DS Write has its reference in and reference out both connected to temporally "adjacent" DS Writes via the shift register, so perhaps it wouldn't try to close the reference on each loop iteration? Or would it look into the future and see that there is no DS Close and decide to implicitly do that itself? Or maybe only the DS Write on the last loop iteration does this?
Thanks for bearing with me through this,
Patrick
Attachments:
example73.JPG ‏40 KB
example83.JPG ‏14 KB

Datasocket calls from Fieldpoint - performance issues

I'm noticing that it takes A LONG TIME for the fieldpoint units to READ data from a Datasocket Server. My program is currently looping and reading 4 Datasocket Items from a server computer(in a for loop) but it takes around 3 seconds for this process to occur. Any suggestions as to how i can "speed" up these datasocket reads? Would using a different protocol (to read datasockets item) be quicker?
Regis

"the loop time dropped from 3 seconds
to under 1 sec (about 750ms)"
I wanted to mention that the 750ms was a pre-defined wait time i placed
in the loop. Without a wait time, I dropped the loop time
to about 80ms.
Also, can anyone please help me with this issue?
Datasocket ReadWrite Mode
Message Edited by RegisPhilbin on 07-20-2005 11:00 AM

How can I read published data from a datasocket server running in a different network?

Hi all,
I have been trying to solve this problem but without any success. I want to develop data acquisition Vi to run on a computer on a remote location. I want to use the datasocket technology to acquire and publish this data so that in my office (in a different network), I can read the published data and perform analysis with it. I can successfully use this approach for the two computers in the same network but not when they are in different networks. My real problem is how to specify the URL for the acquisition computer in one network while the analysis Vi runs on a different network.
I have attached two Vis to illustrate my point (I simply want to be able to read the random numbers generated in the acquisition computer in a different network). The first Vi (RemoteDatasocketWrite.vi) will run on the remote computer with an IP address (192.168.0.110). My office computer on which RemoteDatasocketRead.vi runs has an IP address (192.168.0.11) and I can log in remotely into the remote computer using Remote Desktop Protocol with name (emelvin.001.eairlink.com) from my office computer.
Is it possible to do what I am trying to do or is there a simpler way to solve this problem?
I will really appreciate any help towards a solution to this problem.
Thanks
Attachments:
RemoteDatasocketWrite.vi ‏9 KB
RemoteDatasocketRead.vi ‏9 KB

Are you getting an error? The way you have it set up, you can have an error and it will never be displayed. Put and error control on your front panel and see what it gives you. Also, shared variables in a project can be useful. Look at some examples for that.

How do I detect whether a publishing object is connected to the datasocket server or not?

I have 2 vis which communicate via datasocket. The behaviour of the second vi depends on whether the first vi is running or not, and both vis can be started and stopped independently of each other. I need vi 2 to be able to detect whether vi 1 is running or not. Simple, I thought, I'll have a boolean in vi 1 called Running which is set to True when the vi is running and False when it shuts down. I'll publish that vi to datasocket and have a matching boolean in vi 2 which subscribes to it.
It doesn't work, because as soon as vi 1 stops, Running disconnects and the matching boolean in vi 2 misses the fact that it got set to False before it disconnected, and just gets stuck in the True state.
So it seems to me there should be a "Is object connected?" vi or function somewhere, but I can't find it.
Is there another way to detect whether a vi is running or not? Preferably without using shared globals as I find that quite ugly, in fact I've switched to using datasocket from using shared globals because the latter just seemed like really ugly programming.
Note: I will have several variants of vi 1 with different names, so I can't just try to open a reference to the vi. That's why I wanted to use a datasocket object; all the versions of vi 1 can have a boolean called Running.

I found a solution. The subscribing boolean in vi 2 is now in its own little loop that executes every 50ms in parallel to the main program loop.
In vi 1 there is a delay of 500ms between the publishing boolean being set to false and the vi stopping.
That way the subscriber boolean has plenty of opportunity to read the False state of the publisher.

How do you read a cluster over DataSocket with C?

Hello All,
I am new to Labview and DataSocket in particular, so any help would be greatly appreciated.
I am trying to write a data viewer program in IGOR (www.wavemetrics.com) which will receive multi channel data being published to a DataSocket server and display the requested channel real time. In order to do this I had to write a dll in C, then import that into IGOR, which allowed me to access all the functions in dataskt.dll (DataSocket Library - NI LabWindows™/CVI™ 9.0 Help ).
I have successfully compiled this dll with the DS_Open, DS_IsConnected, DS_DiscardObjHandle, DS_GetDataValue functions and tested them by publishing and retrieving a type double from the server. The problem I am having is that the real data is published as a custom cluster of a double, two singles, and a 1D array of singles (the datapoints at that time slice).
The second input of the DS_GetDataValue function is an unsigned int which represents the type of data expected from the server. There is a list of acceptable data types is in cviauto.h, but as you can see none of them are for a cluster (or structure for that matter):
/* Use these to specify the type of a function parameter, function return */
/* value, and a property. */
enum {
CAVT_EMPTY = 100,
CAVT_NULL,
CAVT_SHORT,
CAVT_LONG,
CAVT_INT = CAVT_LONG,
CAVT_FLOAT,
CAVT_DOUBLE,
CAVT_CY,
CAVT_DATE,
CAVT_BSTR,
CAVT_DISPATCH,
CAVT_ERROR,
CAVT_BOOL,
CAVT_VARIANT,
CAVT_UNKNOWN,
CAVT_UCHAR,
CAVT_CSTRING, /* null terminated ansi (multi-byte) string */
CAVT_OBJHANDLE,
CAVT_CHAR,
CAVT_USHORT,
CAVT_ULONG,
CAVT_UINT,
CAVT_LONGLONG,
CAVT_ULONGLONG,
CAVT_BASICTYPE_MASK = 0x0fff,
CAVT_MODIFIER_MASK = 0xf000,
CAVT_ARRAY = 0x1000,
CAVT_BYREF = 0x2000,
CAVT_IN = 0x4000,
CAVT_OUT = 0x8000,
CAVT_AUTO_CLEAR = 0x0800 /* valid only for VARIANT arguments. VariantClear is called on the variant after the function call */
Then the third input is a pointer to a variable that is the same data
type. I have created a structure to match the cluster and tried to
pass that but it does not change the values of the structure.
Another thing I have tried is the DS_GetDataType function, but that returns 100 which corresponds to CAVT_EMPTY.
Is there any way to define one of these for a cluster? Is there a better way to do what I am trying to do? Any help would be appreciated.
Thanks,
-Jeff VT

Thanks for the response.
Unfortunately I do not have control over how the data is published to the server. There are actually several clusters like I have described, each with data for a particular location during the test, all being published to the same server. The data recording program that we have is written to accept the cluster (it is a labview program) so we don't want to change the way it is published right now. Also we are dealing with a couple hundred datapoints in the array for each cluster.
-Jeff VT

"DataSocket Server has encountered a problem and needs to close" - why?

I am trying to use DataSocket to publish a Front Panel control. First I start the DataSocket Server and then run a corresponding VI. It goes well once or twice but in the end DataSocket Server crashes producing an error message and offering to send an error report to Microsoft:
"National Instruments DataSocket Server has encountered a problem and needs to close. We are sorry for the inconvenience".
I wonder if there is any remedy for this. Windows firewall does not seem to be the cause - the crash happens with the firewall disabled.
Alternatively - is there any way other than using DataSocket to dynamically access data from a running VI?
Regards,
Danielis

Hi Danielis
This kind of errors usally occurs when there is a file corruption. In either the application of the configuration files. The Datasocket configuration is save in the 'cwdssini.dss' file. this is by default installed in 'C:\Program Files\National Instruments\DataSocket'. Yu could try and remove this and then run the Datasocket Server Manager once to recreate a file with default settings.
We it is a problem with the Application you could try and install a fresh copy on a other machine and run the VI and server on that machine. Or just run the server on the other machine and connact you Front panel object to that server instead.
As for other ways of doing this you could look into the Shared Variables that have been introduced in LabVIEW 8
Hope this helps
Karsten

DataSocket

Similar Messages

Maybe you are looking for