> For the complete documentation index, see [llms.txt](https://bing-rover.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bing-rover.gitbook.io/docs/software/network/protobuf/debugging-protobuf.md). # Debugging Protobuf Reading non-human-readable Protobuf data ## Introduction Protobuf, as opposed to JSON and other formats, is non-human-readable. This means, as efficient as they are, buffers cannot be read just by looking at a log file or print statement (note that printing the *generated* class/struct works fine, but not the serialized buffer). To solve this, we use a tool called [ProtobufPal](https://www.protobufpal.com/). Think of it as a pre-written script that can encode or decode your messages. ## Getting your buffer As mentioned, if you're able to print or log your data in the code, this is always preferable as you can access individual fields on the class/struct. This form of debugging is when sending data *over the wire*, ie, through the network. If, for some reason, the data becomes corrupted along the way or you suspect it is otherwise not being parsed correctly, you can inspect the raw buffer instead. These issues may be caused by: * a broken network setup, such as a loose CAN wire * data changing before it is actually sent * out-of-sync generated code on each endpoint * default values not being sent Note that the last two don't indicate a problem with the network, but it can still be helpful to capture the buffers on the sender and leave the receiver alone. When dealing with the CAN bus, use `candump` as detailed in [Debugging CAN](/docs/software/legacy-docs/can-bus/debugging.md). When using UDP, it is often simpler to just print the buffer right before it is sent or right as it is received rather than using a tool like [WireShark](https://www.wireshark.org/). ## Using ProtobufPal You'll be greeted with a screen like this:

The ProtobufPal tool allows for easy and quick debugging

To start: * upload or copy-and-paste your Proto code into the left window and click `Validate Proto` * If you have a buffer you'd like to check, enter it in the bottom windows and click `Decode` * If you have some data you want to encode, enter it in JSON on the right and click `Encode` For example, you can enter buffers you see from `candump`, or manually enter your own commands as JSON and send the buffer using `cansend`. Either way, using ProtobufPal allows you to visualize your buffers as easily as JSON would.