#94 (Bd)SeqNum flow control issue's

accepted
None
21 hours ago
3 days ago
h-hermsen
No

The EoN sends NDATA payloads.
The Device is allowed to send DDATA payloads (by/through command of the EoN)
It seems that the DDATA payloads are tagged with a SeqNum that is too high (it needs to be N, but is tagged with N+1)

This incorrect tagging (N+1) causes/triggers the Server Node to issue a DBIRTH NCMD.
This results in a Sparkplug EoN Node that is in a continuous cycle;

NBIRTH, 
NDATA, 
DBIRTH, 
DDATA, 
NCMD-ReBirth (next step is NBIRTH again)

Improve "assigning of seqnums to payloads" by implementing a mechanism to tag payloads "just in time" with a correct seqnum. This ticket also has a certain relation with "Improve control of/over/with statemachine [#93]"

Related

Tickets: #93

Discussion

  • h-hermsen

    h-hermsen - 3 days ago

    Incorrect SeqNum tagging is solved in V1.1.0.10 in my branch.

     

    Last edit: h-hermsen 3 days ago
  • h-hermsen

    h-hermsen - 21 hours ago

    V1.10.0.11 has resolved the issue completely.

     

Log in to post a comment.