jackybek
jackybek
this is what i found: ReverseConnect Purpose: The ReverseConnect feature allows an OPC UA Server to establish a connection to a Client when the Client is behind a firewall or...
Can I check whether the following behaviour is correct: Scenario 1 1. Disable the reverseconnect module in my code (i.e. dont run) 2. Connect normally using uaExpert and Matrikon using...
During runtime, i am getting these messages BadTimestampNotSupported when attempting to read Historical data. I checked my code and confirmed that i return UA_TRUE: ~~~ UA_Boolean IsReturnTimeStampSupported(MYSQL *conn, const UA_NodeId...
Hi, i am also keen to explore such technologies. Currently my implementation of open62541 is based on rpi running debian bookworm on v1.4.14. i have both client and server implementation...
i checked the part 14 opcua specs and saw that the standard uri is mqtt(s)://domain name:port does this mean i should be sending mqtt://virtualskies:1883, where virtualskies is the machine name...
i did a check as follows: ~~~ UA_PublishedDataSet *currDS = UA_PublishedDataSet_findPDSbyId(uaServer, BpublishedDataSetIdentifier); retval = UA_Server_addDataSetField(uaServer, BpublishedDataSetIdentifier, &dsfCfgDataBlockVersion, NULL); //&f_DataBlockVersion_Id); ... (add 10 fields) printf("fieldsize in publishedDataSet(Node) is %d\n", currDS->fieldSize); ==...
Can someone advise how to go about verifying the parameters for pubsub MQTT? Here is a list of parameters i manage to inspect in ua_pubsub_eventloop.c ~~~ wg->config.name [Airgard WriterGroup Broker]...
i manage to find a way to print out the pubsub connection parameters passed into the library, by going into the source code : pubsub/ua_pubsub_connection.c. Based on these parameters captured...
I already confirmed that by running the following on the same machine as OPCUA, i can send the message. mosquitto_pub -h 192.168.1.157 -p 1883 -u jackybek -P molekhaven24 -t AirgardTopicEdgeToCloud...
I did a trace and found out that the dataSetMetaFields are not populated correctly. Based on the code sequence call train: 1. UA_Server_addDataSetField() calls UA_DataSetField_create() 2. UA_DataSetField_create() initialise field metadata...