Topic RSS15:32, EEST
February 21, 2014
OfflineGood day,
I have configured 2 DataSetWriters in a single WriterGroup (using the same publishingInterval). The UadpNetworkMessageContentMask does NOT contain the DataSetClassId (i.e. it is null). The DataSets only comprise 2 and 3 double values, respectively, which should fit well into the maxMessageSize of 4096 bytes.
What could be the reason for sending multiple networkmessages with one dataSet each instead of one networkMessage containing the dataSets from both dataSetWriters?
Some shortened log messages below. My expectation would be that a single networkmessage would transport both dataSets (dataSetWriterIds=[1,2]). Could this be related to the issue of the dataSet seqNos counting across all dataSetMessages? (see previous forum entry)
INFO XXXXXService – PubSubUdpUadpConnectionNetworkMessageReceivedEvent: seqNo=347, publisherId=String:yyyy::1/1, writerGroupId=1, dataSetClassId=null, dataSetWriterIds=[1], dataSetMessageCount=1
12:04, EEST
Moderators
May 5, 2020
OfflineHello,
I checked the code and it seems like the current implementation never bundles values from different WriterGroups into the same NetworkMessage while the documentation states otherwise. I cannot however currently tell why this is, it’s possible that this is a bug that hasn’t been tested. Regardless, either the docs or the implementation needs to be adjusted.
Thanks for the report, I’ll create an issue on this.
16:21, EEST
April 3, 2012
OfflineHi,
Well … so far basically there has been no demand to do it differently. Do you have a use-case where it would be of use?
Currently the logic is shared with MQTT-UADP. In MQTT it is likely that each Writer has a different Topic. It is not possible to publish to multiple topics in a single MQTT network message. Thus, at the moment the WriterGroup simply does loop all Writers and each Writer will produce the NetworkMessages related to it. The only scenario where multiple DataSetMessages would exist in a single NetworkMessage at the moment are for Event-DataSets.
P.S.
It is not related to the sequence number issue.
1 Guest(s)

Log In
Register