Avatar

Please consider registering
guest

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Feed Topic RSS sp_TopicIcon
PsOPCServer and remote connection
March 11, 2013
13:18, EEST
Avatar
AlexSh
Member
Members
Forum Posts: 3
Member Since:
March 11, 2013
sp_UserOfflineSmall Offline

Good afternoon!
Whether the license trial for sentrol OPC SDK supports remote connection from the client to the server. It is impossible to adjust the PsOPCServer component. In attempt to change ServerName property there is a message “Could not connect to OPCEnum service at ‘192.168.1.84’: Range check error” (192.168.1.84 – IP address of remote OPC server). Despite it, other product “OPC client “Prosys OPC Client” is connected normally. In what there can be a reason?
Help please!

March 11, 2013
14:12, EEST
Avatar
Jouni Aro
Moderator
Moderators
Forum Posts: 853
Member Since:
December 21, 2011
sp_UserOfflineSmall Offline

Please, make sure that OpcEnum service is running in the remote computer. You also need to enable anonymous DCOM access for that computer so that the TPsOPCServer component can connect to the remote service.

If you know the server ProgID or CLSID, you can type that into the ServerName field and try to connect without using the OpcEnum service.

The Prosys OPC Client should also help you to diagnose the connection problems.

March 12, 2013
6:15, EEST
Avatar
AlexSh
Member
Members
Forum Posts: 3
Member Since:
March 11, 2013
sp_UserOfflineSmall Offline

Thanks!
But it is unclear why the “Prosys OPC Client” application is connected without problems, and PsOPCServer can’t connected even by means of CLSID. OPC client of other producer which we checked, also had no connection problems. In what feature of PsOPCServer?

March 12, 2013
8:03, EEST
Avatar
Jouni Aro
Moderator
Moderators
Forum Posts: 853
Member Since:
December 21, 2011
sp_UserOfflineSmall Offline

Do you get other errors as well, in addition to the OpcEnum error? That one is specific to the ServerName editor, which is using the TPsOPCServerList object internally.

Prosys OPC Client is using the same TPsOPCServer, so it should work identically, in principle.

March 12, 2013
9:32, EEST
Avatar
AlexSh
Member
Members
Forum Posts: 3
Member Since:
March 11, 2013
sp_UserOfflineSmall Offline

Yes, after the record CLSID in the field of PsOPCServer.ServerName and attempt to establish connection there is a mistake: “Cannot connect to OPC Server\\192.168.1.84\{0233D094-F7AE-48FE-9334-6691E9D22042}: Range check error”.
CLSID looked on “Prosys OPC Client”.

March 12, 2013
13:43, EEST
Avatar
Jouni Aro
Moderator
Moderators
Forum Posts: 853
Member Since:
December 21, 2011
sp_UserOfflineSmall Offline

OK, I will need to check if I can reproduce the problem. I suppose it is related to the failing connection to OpcEnum. If you manage to get a connection to that it will probably work better.

This can be a version specific problem, if Prosys OPC Client(compiled with a certain Sentrol version) is not suffering from the same problem.

Forum Timezone: Europe/Helsinki

Most Users Ever Online: 267

Currently Online:
11 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

hbrackel: 103

pramanj: 86

ibrahim: 70

kapsl: 57

gjevremovic: 49

TimK: 41

Fransua33: 39

fred: 38

Rainer Versteeg: 32

Thomas Reuther: 31

Member Stats:

Guest Posters: 0

Members: 1118

Moderators: 14

Admins: 1

Forum Stats:

Groups: 3

Forums: 15

Topics: 1034

Posts: 4352

Newest Members:

aldayr, Python techie, emanuel45q, Patrick, sammycontrols, hellema, linoy, subranna, ray, richN9177

Moderators: Jouni Aro: 853, Otso Palonen: 32, Tuomas Hiltunen: 5, janimakela: 0, Pyry: 1, Terho: 0, Petri: 0, Bjarne Boström: 559, Heikki Tahvanainen: 402, Jukka Asikainen: 1, Teppo Uimonen: 21, Markus Johansson: 24, Matti Siponen: 64, Lusetti: 0

Administrators: admin: 1