samuelsadok

`make_protocol_ro_property` is no longer part of the new Fibre architecture (on the `devel` branch). The new way is to expose properties and functions is by adding them to the interface...

How did you launch the container? The preferred way to communicate with the ODrive is directly via USB endpoints, so you need to pass the whole device through (not just...

Sorry for the late answer. Since this is still in a very early stage and I didn't (yet) have time to finish the major overhaul, integrating the C++ library is...

The Python implementation of Fibre will very soon be replaced by a C/C++ implementation and a thin Python wrapper that binds to the compiled library. I will check if the...

I'm currently too detached from this part of the codebase to quickly judge if this change is good. Is it tested? Please also add a note to the changelog.

In case you're using this with a recent ODrive Pro/S1 DBC file, as a workaround it should work if you prefix the message name with `Axis0_`. So `Axis0_Set_Axis_State`. Same for...

Does the rate setting work for other messages? Can you copy&paste the diagnostics info from the GUI?

What's your firmware version? (see previous message to copy diagnostics info) Do you have a way to log CAN messages? For instance on Linux you can install python-can (`pip3 install...

Sorry forgot to follow up here. This is now possible on ODrive Pro/S1 using [Arbitrary Parameter Access](https://docs.odriverobotics.com/v/latest/guides/can-guide.html#arbitrary-parameter-access).

~~Yeah sorry I didn't get to it yet but the plan is to autoclear them as outlined in the other issue.~~ **edit:** @liborw ah just saw your PR, thanks, I'll...