Ability to run platform (modules, services) "standalone" on the edge #464
Comments
|
Hi,. Thank you for the request. It is not possible at this point. We will however add it to our internal long term planning backlog. |
|
This would be helpful! |
marcschier
changed the title
|
Hi @ma3goul @PWSys, I'm a PM helping to coordinate the internal planning. Would you like to set up some time to chat so that we can capture your requirements and align it with our backlog? If so, feel free to email me at [email protected]. |
|
Has there been any progress on this? I am working on a project where we want to add the Twin module and microservice to our existing setup. We are currently subsribing to OPC Publisher though an IoT edge device, and we need to add on the ability to set values on the OPC server. As far as we can tell, the twin module and microservice is our best bet, and we want to add those two, and only those two if we can to our existing deployment. Is there a way to do this at the moment? |
# Changes introduced: - New Namespaces for all projects and simplified code structure. There are now 2 SDK projects, one for the OPC Publisher module, and another for the optional cloud WebAPI companion service. - Ability to run platform (modules, services) "standalone" on the edge #464 - [OPC Discovery] has been included into the OPC Publisher module, the container name must be updated to refer to OPC Publisher. - [OPC Discovery] A new synchronous FindServer API has been added to allow discovery by discovery url through a single API call. - [OPC Twin] has been included into the OPC Publisher module, the container name must be updated to refer to OPC Publisher. - [OPC Twin] we removed the Activate and Deactivate calls. - [OPC Twin] OPC TWIN Method call #996 - Support for opc-twin module api direct method calls with input arguments (not requiring OPC Twin micro services) #1512 - Support for a new TestConnection API to test a connection to a server and receiving detailed error information back. - [OPC Publisher] (breaking change) The publisher id in each message is now always the same value across all writer groups rather than previously where a random guid was used per writer group when a publisher id was not configured. - [OPC Publisher] Several bug fixes for preview 1 (#1964) - [OPC Publisher] DatasetMessage SequenceNumber is now correctly incremented (preview) (#1961) - [OPC Publisher] Enabling using DisplayNames defined for the event fields in pn.json as keys in the payload of dataset messages (#1963) - [OPC Publisher] Request opc server's nodes information #1960 - [OPC Publisher] dotnet publish can be used to build a docker container for OPC Publisher #1949 - [OPC Publisher] Metrics output and log output showing number of sessions currently active (related to #1923) - [OPC Publisher] Added new OPC UA stack which addressess #1937 and latest CVE's - [All micro services] Have been combined into a single WebAPI with the same resource paths as the 2.8 AKS deployment and all-in-one service. - [OPC Registry service] Supervisor, Discoverer entities have been removed, but the API has been layered on top of the publisher entity for backwards compatibiltiy. Do not use these API's anymore. - [OPC Registry service] A new RegisterEndpoint API has been added that calls the new sync FindServer API and adds the result into the registry in one call. - [Telemetry processor] The telemetry and onboarding processors have been integrated into the WebAPI, but only forwards to SignalR. The secondary event hub has been removed. If you need to post process telemetry you must read telemetry data directly from IoT Hub. - Document the diagnostics output and troubleshooting guide #1952 # Stats: * Consolidated down to 1 edge module and 1 optional cloud companion web app. * Maintained 99% of API and even added new capabilities/functionality such as Event and MQTT broker support. * Reduced LOC for shipped binaries by 53% from to 641844 in 2.8.6 to 297144 in 2.9.0 preview 2 * Increased Test coverage (blocks) by around 50% from 51.34% to 76.36%
|
Hello Team / @Adrian-Wennberg / @rowenwu / @PWSys , I have the same need to write back to OPC UA Server. I know @marcschier has mentioned to my post (#1973 (comment)) that this will be part of 2.9.0 Preview 2 where we can using REST Interface to update values back at OPC Server level. General question: Can we develop a custom C# module to write back at OPC UA Server level meanwhile? I believe the OPC.UA Nuget packages allow for this functionality. Also, if I am correct, this Nuget package is the backbone of the OPC Publisher module currently that we can deploy standalone. |
|
I assume yes you can do it with a C# module. I ended up getting in contact with the IoT team directly and they gave me the pointers I needed to set up a javascript module module using the node-opcua package. The biggest hurdle for me was learning to develop and deploy my own module, but it was otherwise fairly simple 🙂 |
|
This is possible using a custom module. Here is a basic write example using the OPC-UA .Net Standard library: |
|
We released 2.9.0-preview2 which has these capabilities, documentation regarding API and samples are following in the next months. |
Is your feature request related to a problem? Please describe.
Hi All ,
I prototyped a simple POC using a simulation OPC UA server and OPC publisher with legacy configuration .
Now I want to run an OPC twin with the OPC publisher .
Describe the solution you'd like
Is it possible to run OPC twin (and maybe OPC discovery) in standalone mode ? without deploying the whole industrial iot platform ?
Describe alternatives you've considered
Is it possible also to call methods via the OPC TWIN using a customised module running on the edge ?
Thank You in advance .
The text was updated successfully, but these errors were encountered: