Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC: OPC XML-DA

OPC XML-DA 15 years 4 months ago #321

  • Valdemar
  • Valdemar's Avatar
  • OFFLINE
  • Junior Boarder
  • Posts: 28
  • Karma: 0
Hi Robert / Claes,

I would appreciate your help to configure the XML-DA communication in Proview:

OPC server : the OPC_server Config object is placed below the node 'acdesktop'.
Port : 8080
OPC Client Access : the IP address of OPC client and Read access.

The status monitor shows : opc_server - Server running

OPC Client : extern volume is created using the GlobalVolumeList : 'MyOPCVolume' , Vol Id : 0.1.99.55

Mount object is created in the plant hierarchy with objid _O0.1.99.55:0

Additionally the appl. file with 'ld_appl_acpc_508.txt' has been added to $pwrp_load. The file contains the lines:

opc_provider, opc_provider, noload, run, opc_provider, 9, nodebug,
http://acdesktop:8080 0.1.99.55 MyOpcVolume

(acpc and 508 are the name of client node and qcom bus no. respectively)

The terminal window on the client side shows the following :

I Starting opc_provider, file: opc_provider, prio: 9
I Started opc_provider, prio: 9, pid: 6973
file: opc_provider
sched_setscheduler: Operation not permitted
failed to set pid 6973's policy
remote_pvd_pwrcli Proview provider client

Arguments:
1 Opc server URL
2 Extern volume id
3 Extern volume name
4 Server identity (optional, default 200)
I Process pwr_linksup_508 exited with status 0
I Process pwr_remh_508 exited with status 256
java.library.path = /lib/i386/client:/lib/i386:/../lib/i386:/usr/pwr45/os_linux/hw_x86/exp/exe
I Process pwr_elog_508 exited with status 256
MaxNoOfAlarms: Nodes-acpc-WebHandler-User 0 false
I Process opc_server_508 exited with status 8704
I Process opc_provider exited with status 0

What is wrong in the configuration?

I also tried to use an OPC XML-DA client tool, but it is not possible to browse any items. It seems that I am not using the right syntax. If the item is Lvalue in the tree DEMO-Modbus-Signal-Lvalue and float datatype.

How is the syntax to access the data?.

Many thanks in advance.

Valdemar
The administrator has disabled public write access.

Re:OPC XML-DA 15 years 4 months ago #322

  • claes
  • claes's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 3170
  • Thank you received: 497
  • Karma: 133
Hi Val,

The fourth argument to opc_provider (server identity) is supposed to be optional, but actually, when I look in the source code, it is not. So add 200 in the argumentlist to opc_provider in ld_appl_acpc_508.txt.

If you have called the mount object MyOpc, the reference to the float value should be

MyOpc-DEMO-Modbus-Signal-Lvalue.Value (in Ge, as usual followed by ##Float32).

/Claes
The administrator has disabled public write access.

Re:OPC XML-DA 15 years 4 months ago #323

  • Valdemar
  • Valdemar's Avatar
  • OFFLINE
  • Junior Boarder
  • Posts: 28
  • Karma: 0
Hi Claes,

Thanks for your help.

I did not manage yet to configure the OPC XLM-DA communication. I have the following doubts:

- On the server side, is there anything else to be done except for adding the OPC_ServerConfig object and configuring the port and client access?.

- On the client side :

When the extern volume is registered using the GlobalVolumeList, should it be done with VolumeReg object?
(there is also a class in pwrs named $ExternVolume in the Navigator Volume)

Shall the new registered VolumeReg object have the same name and Id as the volume on the server side to be mapped?

The mount object is created in the plant hierarchy on the client side with the same Id as the new reg. volume id. It seems that the appl. file starts the opc provider but Client/Request Cnt in OPC Server status is always 0.

Regards,

Valdemar
The administrator has disabled public write access.

Re:OPC XML-DA 15 years 4 months ago #326

  • robert
  • robert's Avatar
  • OFFLINE
  • Gold Boarder
  • Posts: 178
  • Karma: 7
Hi Val,

To me it seems you have made the configuration correct. Did the opc_server start after your last changes ? I guess it did.

What version of Proview are you running ? There was until may a bug where you were forced to use port number 18083. Can you please try to test this. If you run the latest version this bug should however be fixed.

What OPC XML-DA client-tool did you test ? I've used the client from Kassl aswell as a client from Matrikon with no problem (I think maybe though the Matrikon-client had problems with certain variable-names).

/Robert
The administrator has disabled public write access.

Re:OPC XML-DA 15 years 3 months ago #327

  • Valdemar
  • Valdemar's Avatar
  • OFFLINE
  • Junior Boarder
  • Posts: 28
  • Karma: 0
Hi Robert,

I am using Proview 4.5.0-5.

The instructions on previous messages were followed, but the objects are not mapped on client side.

- added 200 in the argument list of opc_provider
- changed the port to 18083

The terminal window shows:
I Starting opc_provider, file: opc_provider, prio: 9
I Started opc_provider, prio: 9, pid: 7204
file: opc_provider
sched_setscheduler: Operation not permitted
failed to set pid 7204's policy
remote_pvd_pwrcli Proview provider client

Arguments:
1 Opc server URL
2 Extern volume id
3 Extern volume name
4 Server identity (optional, default 200)
java.library.path = /lib/i386/client:/lib/i386:/../lib/i386:/usr/pwr45/os_linux/hw_x86/exp/exe
MaxNoOfAlarms: Node-acpc-WebHandler-User 0 false

It is possible to communicate with Kassl OPC-XML client tool - ProviewOPC server.

It seems some problem in the OPC client side configuration.

Thanks for your support.

Valdemar
The administrator has disabled public write access.

Re:OPC XML-DA 15 years 3 months ago #328

  • claes
  • claes's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 3170
  • Thank you received: 497
  • Karma: 133
Hi Val,

The opc_provider is terminating because it is not satisfied with the argument list.
I think the problem is that the text for the opc_provider in the application file has to be written on one single line. The text should be, with 18083 as port number

[code:1]opc_provider, opc_provider, noload, run, opc_provider, 9, nodebug, http://acdesktop:18083 0.1.99.55 MyOpcVolume[/code:1]

written on one single line.

/Claes
The administrator has disabled public write access.
  • Page:
  • 1
Time to create page: 8.820 seconds