-
Notifications
You must be signed in to change notification settings - Fork 38
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
MID 0002 revision 6 is incorrectly implemented #40
Comments
Just realized that the type for |
Hello @ferm10n , it seems that you are the only one active member in the project. I have a machine IxB ready in my lab that I would like to use for creating MID0900. I am currently using MID0008 I always receive an error and to be honest I am not able to debug it. Would you be interested on stablishing a kind of collab o working session in order to help me to debug it? Thanks in advance |
I don't have a whole lot of time lately, but I could try to help! I'll reply on your MID900 issue |
Open Protocol spec defines rev 6 with these new fields:
sequenceNumberSupport
linkingHandlingSupport
stationID
stationName
clientID
Missing Keys / Fields
The parser is missing the last three keys:
node-open-protocol/src/mid/0002.js
Line 72 in f514d00
node-open-protocol/test/0002.spec.js
Lines 191 to 205 in f514d00
Interestingly, the serializer has all the keys:
node-open-protocol/src/mid/0002.js
Lines 191 to 200 in f514d00
node-open-protocol/test/0002.spec.js
Lines 378 to 395 in f514d00
I would expect the parser and serializer to behave as inverses to each other.
Wrong type for
stationID
Additionally, the type for
stationID
is also wrong. The official protocol says it's supposed to be a number, but node-open-protocol tries to interpret it as a string!The text was updated successfully, but these errors were encountered: