New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spec is misleading when it comes to "known" metrics. #370
Comments
Or is it meant to be used like this?
|
I'm not sure I understand your question. Known means known. If you send an NDATA/DDATA with a new Metric, that would be invalid and the Host Application will require you to send a new NBIRTH/DBIRTH that contains your new Metric in order to move forward. Your Node/Device will be set as offline until you send an appropriate NBIRTH/DBIRTH. In other words, sending an NDATA/DDATA with a new metric is wrong and should not be done. What exactly is not clear? PS.: I don't think this is the appropriate channel to discuss the Sparkplug B specs |
@ArFe Thank you for the clearification. I just had the question within my project several times. Need to check it, so keep it open for now :) |
Check
--> All metrics need to be known in DBIRTH / NBIRTH already?
But still, metrics can be new from DDATA or NDATA messages? How do these requirements fit together?
The text was updated successfully, but these errors were encountered: