Closed silverv closed 2 years ago
The error message is correct though: the data specifier is malformed because it should be uavcan.node.ExecuteCommand.1.1
instead of uavcan.node.ExecuteCommand
.
The message is not straightforward, you wouldn't know that as the creator
My unintentional usability test says revealed that my thought process is: "Okay, I need to change the way that I present the data to the uavcan.node.ExecuteCommand request constructor." While it should've been: "Oh, uavcan.node.ExecuteCommand doesn't exist, I forgot that I need to use the versioned notation"
Okay, I see. Ideally, we should default to the latest available version if at least one version number is omitted.
This was confusing to me, I ended up trying 20 different ways to write '{command: 65533, parameter: hello}', eg 'command: 65533, parameter: hello' whereas the problem is the datatype name.