LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

datasocket opne fails with 1184 error accessing an OPC server

Hi,

I'm trying to access an OPC server from a client using datasockets.  DataSocket Select  URL.vi works fine and provides the URL of the tag(s) I would like to retrieve. Using the provided URL I try to access the server with DataSocket Open, but I get the following error:

Error 1184 LabVIEW:  Path not found, FTP login incorrect, or no FTP write permission.

 

The  path should be correct as it is provided by the DS Select VI  and anyway is in the form:

opc://t2-opc-server.lnl.infn.it/EEI.Modbus/tt.pp where pp is the item I need to read

 

I'm working with Labview 8.6.1 on a WindowXP machine and I'm accessing another WindowXP machine where an  OPC server  Eldridge Engineering (Modbus TCP) is running. I'm even using DSC to access the same OPC server and it works (even if in this case  I have other issues that I hoped to fix with datasocket),  so I should not have problems with security issues.

 

Any help is really welcome

gaetano

 

0 Kudos
Message 1 of 8
(7,665 Views)

Gaetano,

When you open the datasocket there shoudl be an option called access mode, which you can change to Read only instead of readwrite.

 

Try this and let me know if it helps.

 

Amit

0 Kudos
Message 2 of 8
(7,611 Views)

Hi Amit,

access mode is read only, but I have the same behaviour.

thank you for the help

gaetano

 

0 Kudos
Message 3 of 8
(7,600 Views)
Hello gaetano_maron,

I had the same problem. It happens only by remote access to the OPC-Server. In my case the service "Remote-Registry"
(I'm german, maybe the english name is a little bit different) was not running on one PC. LabVIEW need to read in the registry.

Remote access to an opc-server is complicated, try to avoid it. Learn about DCOM.

Look at:
http://digital.ni.com/public.nsf/allkb/5C8A90CD57B279F286256C2C006F1EB4
http://zone.ni.com/devzone/cda/tut/p/id/2918
To get a hint to the reason of the problem I used the "NI Server Explorer 2.4.1" and "OPC Security Analyzer" Advosol.

Good luck

Samoth
Message 4 of 8
(7,419 Views)

great !!

 

with the "remote registry" service started, it works !

 

thanks a lot, and good luck for all the other users of OPC via datasocket...

 

Adeline.

Message 5 of 8
(6,098 Views)

I had the exact same problem and starting the remote registry service on the server also solved it, thanks!

Message 6 of 8
(3,870 Views)

Hallo...

Just the same problem but, after "remote Registry" enabling , I got an "error 42"....

Using a standard OPC client , it works....

Some suggestion?

Thanks in advance!

Luca Nitopi

0 Kudos
Message 7 of 8
(3,045 Views)

Hello Luca, I have the same problem. Were you able to resolve it?

 

Samantha

0 Kudos
Message 8 of 8
(2,633 Views)