In folder OPC-UA-OOI/Networking/ReferenceApplication/Release.bin/ I have added binary release of the
ReferenceApplication containing ready to use binaries. Unzip and run exe file to get started. Nuget package will be created after getting more feedback from MQTT and AMQP testing, which are in progress.
Maybe one for development and one for using.
That would help many people to get a better idea, what it is and how it works.
Hi Piotr @Drutol - let me inform you that I have finished working on the documentation for now. The relevant for HMI implementation documentation is at https://commsvr.gitbook.io/ooi/deployment/walk-through-referenceapplication and subsections. Add issue or PR if there is something missing or not clear. Good luck and inform us about all you successes.
Hi Klaus @biancode I am still not ready to create video introduction, but the let me inform you that the project documentation has bee improved and are available as the ebook at https://commsvr.gitbook.io/ooi/. Hope it helps for now. Current priority of the work is defined on the Milestones page: https://github.com/mpostol/OPC-UA-OOI/milestones. Let me know how it works for you. Any suggestions are welcome :).
. Now I need to figure out how to distinguish publishers of this data... Is each publisher meant to have separate
Gitter doesn't play well with images apparently
Not sure if I have got the question. Filtering is implemented in the library, so you should not care about it. Filtering and data content is setup in the configuration.
You should use the couple (RepositoryGroup, ProcessValueName) to find where the value must be written. If your HMI interface need additional configuration the provided configuration should be expanded. For example:
RepositoryGroup = Boiler.1
ProcessValueName = PipeIn_Presure
You can use the simulator to display generated values on selected picture or place on the screen - don't touch the MessageHandlers configuration to make sure you are getting everything form the producer.
@Drutol The content of the DataSets you have described in https://commsvr.gitbook.io/ooi/deployment/walk-through-referenceapplication/referenceapplication-producer-interoperability-test-data-generator
Let me inform you that have accomplished the milestone Architecture improvements and it is available on the main track
master. It needs harmonization of any derived libraries as the result of some minor architecture changes. The work on Rel 4 is underway so I cannot guarantee that the API will not change in future, but once more it is to be more stable for now.
Hi Piotr @Drutol; let me recall you that all the tasks relevant to the development of the HMI I am assigning to the project Networking.HMI. Review if the list is what you are expecting to keep going. The priorities of the work are defined on the milestone page. Let me know or add what is missing.
A bit of an update from me. I managed to neatly wrap around library to expose gathered data to UI. I've adjusted current producer simulator to suit my needs (2 boilers which are indetified via
repositoryGroup, and while it works locally (on single machine) I ran into issues with receiving this data on mobile device in local network I'll try to debug it now. I tried enabling events on EventSource of UDP message handler but I didn't receive any... I wonder whether it has to do with Mono's implementation of these.
Thanks for update. The critical point for logging the network traffic is application configuration, there is the switch:
<add name="System.Net.Sockets" value="Information" />
<!-- value: Required String attribute. Sets the verbosity of the output.
Legitimate values are Critical, Error, Verbose, Warning, and Information.
-->
<!-- maxdatasize: Optional Int32 attribute. Sets the maximum number of bytes of network data included in each line trace.
The default value is 1024.
-->
<!-- tracemode Optional String attribute. Set to includehex to show protocol traces in hexadecimal and text format.
Set to protocolonly to show only text. The default value is includehex.
-->
</switches>change Information to All
The network traffic is logged by the Microsoft stuff, so the behavior may depend on the platform.
@Drutol I am working on the simulator behavior. The simulator is implemented using generated code by the ModelCompiler translating OPC UA Information Model to Address Space. In our case we don't have Address Space so the code is not well suited but we don't have any better replacement. hopefully I will finisher this part today.
Sorry for late reply. Hmm I'm afraid that this switch does not apply to non .Net Framework applications. I've got wireshark running and I see packets properly propagating.
I've tested obtaining events from
I'll try importing UDP handler project manually and thoroughly see what's going on.
I've tested obtaining events from
UDPMessageHandlerSemanticEventSource and while in WPF application it works, on mono it doesn't. I'm also not sure how I'm suppposed to obtain its instance since Log property is internal. For now I've been using reflection to test (but it wasn't very helpful).I'll try importing UDP handler project manually and thoroughly see what's going on.
I'm trying to change producer configuration but to no avail. Is just changing
.xml config files sufficient? I'm now adding one more DataSetConfiguration with only AssociationName and RepositoryGroup changed. Additionaly I'm adding ProducerAssociationConfiguration entry with updated AssociationName to match the ones defined in DataSetConfiguration
@Drutol it is good that the UDP works for now. As I remember main project (.exe) references this assembly to make sure it is copied to the destination folder.
IEncodingFactory is implemented by the code-base as .NET Standards so you can use it instead of implementing it. I don't see any reasons to rework this lib , or maybe I am not following you.
@Drutol consumer and producer configuration must be symmetrical, namely should have the same DataSetConfiguration set and the same associations. It doesn't mean they are identical, but semantically equivalent . Changing only the producer configuration you can observe different network traffic and packages payload using
Wireshark. Let's think about a piece of software converting the producer configuration to consumer configuration - for example as a unit test. Yes .xml file consist all details for selected producer or consumer. In a few days I should have the configuration generator for the simulator I am working on. Maybe it helps. Lets think about conf call or F2F meeting - details we exchange by separate conversation by email.
I'll read more about of EventSources in cross-platform scenarios and then create an issue, I may be missing something.
The problem with library's implementation of
The problem with missing packets is that even though I'm changing producer configuration I only see data produced for 1st data set, I'll wait for this configuration generator while working on other stuff.
The problem with library's implementation of
IEncodingFactory is that it forces repositoryGroup which is undesirable, I just made my own without this check.The problem with missing packets is that even though I'm changing producer configuration I only see data produced for 1st data set, I'll wait for this configuration generator while working on other stuff.
@Drutol You are right, the repositoryGroup in
```C#
/// <summary>
/// Sets the converter, which is used to provide a way to apply custom logic to a binding.
/// </summary>
/// <value>The converter as an instance of the <see cref="IValueConverter"/>.</value>
IValueConverter Converter { set; }
~~
The check is redundant and may be simply removed - I will add issue addressing this
IEncodingFactory is required in case you need to provide a data converted.```C#
/// <summary>
/// Sets the converter, which is used to provide a way to apply custom logic to a binding.
/// </summary>
/// <value>The converter as an instance of the <see cref="IValueConverter"/>.</value>
IValueConverter Converter { set; }
~~
The check is redundant and may be simply removed - I will add issue addressing this
The
/// <summary>
/// Updates the value converter.
/// </summary>
/// <param name="binding">An object responsible to transfer the value between the message and ultimate destination in the repository.</param>
/// <param name="repositoryGroup">The repository group.</param>
/// <param name="sourceEncoding">The source encoding.</param>
/// <exception cref="ArgumentOutOfRangeException">
/// repositoryGroup
/// or
/// binding
/// </exception>
void IEncodingFactory.UpdateValueConverter(IBinding binding, string repositoryGroup, UATypeInfo sourceEncoding)is the pace where you can assign to the Converter property used by the library to handle additional type conversion if needed.
@Drutol Details you can find in the
IBinding definition.
@Drutol Configuration: the best practice -I recommend - is testing new configuration in the WPF environment using base-code. If there are any doubts about if something is correct or not you can PR additional UT. Let me recall one of the primary rules: UT should be also be used to understand the code - intention of the author.