|
Re: SUBSCRIPTION FB connection problem (OPC UA) [message #1854901 is a reply to message #1854872] |
Fri, 16 September 2022 18:20 |
|
Hi,
In the 4diac FORTE logs I see : WARNING: T#18446743417839439402: [OPC UA LOGGER] warning/network Trying to connect to opc.tcp://localhost:62541 timed out . Therefore I would expect that your OPC UA server is not reachable under localhost:62541. What address and port does your OPC UA have?
Cheers,
Alois
|
|
|
|
|
Re: SUBSCRIPTION FB connection problem (OPC UA) [message #1855049 is a reply to message #1855047] |
Mon, 26 September 2022 12:08 |
Kirill Dorofeev Messages: 70 Registered: February 2016 |
Member |
|
|
Hi Yegor, I don't see anything wrong with your FB parameters and server settings. Besides changing the port of the server, as suggested by Alois, you could also try to disconnect UA Expert from the server, while you run forte. Some servers do limit the number of client connections that are allowed simultaneously. Haven't seen it that often, but maybe this is your case?
[Updated on: Tue, 27 September 2022 11:28] Report message to a moderator
|
|
|
Re: SUBSCRIPTION FB connection problem (OPC UA) [message #1855080 is a reply to message #1855049] |
Tue, 27 September 2022 21:42 |
|
Alois,
FORTE creates a server by using port 4840. So I run two servers at :4840 and :62541 (I don't need two of them simultaneously, but I've checked in purpose if there is a port conflict)
INFO: T#528072969456: [OPC UA LOCAL]: Starting OPC UA Server: opc.tcp://localhost:4840
I don't know if this can cause a problem, but in theory both servers don't bother each other, or?
Kirill,
According Ignition documentation it has no client connection limitation. The only thing i found on Ignitions's forum is:
Quote:
You may be dealing with a broken client implementation that does a "two step" connection:
1)connect, get endpoints, find a matching one
2)connect to the matching endpoint, create/activate a session
Does it a case of Subscriber FB in 4DIAC?
|
|
|
|
|
|
Re: SUBSCRIPTION FB connection problem (OPC UA) [message #1855346 is a reply to message #1855304] |
Sun, 09 October 2022 22:53 |
|
Kirill,
it did help, thank you. It connects with IP instead "localhost" (I have only one PC for both Ignition and 4Diac), but i still cant receive any data. What did i miss?
Ignition OPC config (I did not forget to reload OPC UA module):
Forte logs:
4diac:
I have tried to use ID in the format BROWSENAME (RandomInteger1 is a sample node of Ignition)
"opc_ua[READ;opc.tcp://127.0.0.1:62541#;/Objects/2:Tag Providers/Sample_Tags/Random/RandomInteger1]"
aaaaand BROWSENAME,NODE_ID
"opc_ua[READ;opc.tcp://127.0.0.1:62541#;/Objects/2:Tag Providers/Sample_Tags/Random/RandomInteger1,2:s=Sample_Tags/Random/RandomInteger1]"
but if I use only NODE_ID
"opc_ua[READ;opc.tcp://127.0.0.1:62541#;,2:s=Sample_Tags/Random/RandomInteger1]"
forte shows:
ERROR: T#18446743469341962754: [OPC UA CLIENT]: Reading for FB CLIENT_0_1 in client opc.tcp://127.0.0.1:62541 failed because the response for index 0 has status BadNodeIdUnknown
and 4diac looks like:
I have only one guess, that it is probably because of square brackets. UaExpert shows "[Sample_Tags]" in the Identifier (and basically all subfolders of the folder Tag Providers have [...] in ID. Even the ones created by user/me), but 4diac does not allowed to add square brackets into square brackets (like opc_ua[ACTION;ENDPOINT;....[...]...]), so i used just "Sample_Tags" in ID.
|
|
|
|
|
Re: SUBSCRIPTION FB connection problem (OPC UA) [message #1855373 is a reply to message #1855365] |
Tue, 11 October 2022 06:55 |
|
Hi,
unfortunately we currently don't have a good escaping for communication IDs. Both $ and \ are problematic as escape characters. $ is not possible because it has a special meaning in IEC 61131-3 and \ as it has the same specialties in C/C++ or Java. We just had in an other occurrence a problem with it.
Therefore we need a dedicated escape character that is only analyzed in IDs. Maybe using the [ and ] are good escape characters. If you have a single [ or] it would be the delimiter of the id params, double would be inside.
|
|
|
|
Re: SUBSCRIPTION FB connection problem (OPC UA) [message #1855387 is a reply to message #1855375] |
Tue, 11 October 2022 16:29 |
Kirill Dorofeev Messages: 70 Registered: February 2016 |
Member |
|
|
in the meantime... the speification over the browse path should actually work..
just be sure that you need to specify the namespace index for every node in the browse path. probably, instead of:
"opc_ua[READ;opc.tcp://127.0.0.1:62541#;/Objects/2:Tag Providers/Sample_Tags/Random/RandomInteger1]"
you need smth like
"opc_ua[READ;opc.tcp://127.0.0.1:62541#;/Objects/2:Tag Providers/2:Sample_Tags/2:Random/2:RandomInteger1]"
assuming all the nodes in the browse path starting from "Tag Providers" are in the 2nd namespace (better double-check every single node;s ns index in UAExpert)
[Updated on: Tue, 11 October 2022 16:30] Report message to a moderator
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04273 seconds