Initialise NUSense -> NUC communication protocol #3
Conversation
|
Don't commit generated code, generate it on the fly instead |
|
@TrentHouliston that would probably involve the whole nanopb repo/build to be included somewhere in the tools section in NUbots/NUbots then use subprocess to run the generator script then probs use firmware installer to write the files to NUsense. Is this how you expect this to go? The pb.cc and pb.h counterparts of a normal pb message have to be in NUSense for the code to compile in that side if we're going with this. |
|
TODO add callback function to extract ServoTarget field from ServoTargets update: Not needed, just went with the .options file route so we can just treat our targets buffer as a vanilla c array |
… with ten bytes of zeroes, another where the memcpy was overflowing. This should work mostly fine at 100 Hz.
…ss. Changed the global variables relevant for the protobuf-handling to volatile. Changed some of the memcpy's to std::copy's as a result. Works under the optimiser set at -Ofast.
debug folder name is used in OpenCR
|
Might have to bring some of the necessary .cproject files, etc., it is very inconvenient to not be able to build after initial setup. |
JohanneMontano
changed the title
Written the test, next TODO is to decode the packets that are coming from the NUC, encode status returns in NUSense and send to NUC then decoding in the NUC side