-
-
Notifications
You must be signed in to change notification settings - Fork 8
Open
Labels
questionFurther information is requestedFurther information is requested
Description
Hi Alex,
sorry, I need to ask one more question as I can't really figure that out.
The visca protocol has message Ids that can have variable long message ids, without a size or lenght field.
I wanted to use it like that:
<enum name="ReturnId" type="uint32" length="3" availableLengthLimit="true" semanticType="messageId">
<validValue name="Ack" val="0x41" />
<validValue name="Completion" val="0x51" />
<validValue name="SyntaxError" val="0x6002" />
<validValue name="CommandNotExecutable" val="0x6141" />
<validValue name="PanTiltPosInq" val="0x50" />
</enum>
...
<frame name="CameraFrame">
<layers>
<value name="CameraId" interfaces="CommandInterface">
<interfaceFieldName value="CameraId" />
<field>
<int reuse="CameraId" serOffset="0x8F" />
</field>
</value>
<id name="ReturnCommand" field="ReturnId" />
<payload name="Command" />
<checksum name="FrameEnd" alg="custom" algName="EnforceFrameEnd" from="CameraId">
<int name="FrameEndField" type="uint8" />
</checksum>
</layers>
</frame>With that it will correctly create the expected byte sequence, however the deserialization to the message object fails.
Do you have an idea on how to do that?
Metadata
Metadata
Assignees
Labels
questionFurther information is requestedFurther information is requested