Ticket #94: (Bd)SeqNum flow control issue's discussion

Page 1.0 of 1.24

  • hermsen

    hermsen - 2020-11-21

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

     

  • hermsen

    hermsen - 2020-11-23

    V1.10.0.11 has resolved the issue completely.

     

  • hermsen

    hermsen - 2020-11-26
    • status: accepted --> pending
     

  • hermsen

    hermsen - 2020-11-26

    Fix present in 1.1.0.13 in personal branch => merge into trunk

     

  • hermsen

    hermsen - 2020-12-12
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -2,13 +2,6 @@
 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;
+This incorrect tagging (N+1) causes/triggers the Server Node to issue a DBIRTH NCMD.

-    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

  • hermsen

    hermsen - 2020-12-12
    • status: pending --> closed
     

Log in to post a comment.