wernerdaehn

So it starts and ends with speed = 0? Okay, will do that. $p reports the start/end and the actual position.

Still considering how to do that best. Should the code stay as is and it is more like a virtual movement of the end points + play? Simple but limited....

Yes. Was skiing a lot recently. Yesterday I started to add the odrive control code. Still at the early stages but at least some progress. Things I keep thinking about:...

Check the bottom of this page: https://github.com/wernerdaehn/CC3D-CableCam-Controller/blob/master/Step%206%20-%20Connecting%20the%20Position%20Sensor.md The point is not that N/S poles are 8mm apart and so is the sensor, it should be 8mm to 13mm for example....

I don't know the effects of slippage. And I expect it to be dependent on many external factors. A heavy rig on a steep hill and aggressive driving and running...

There are three things to consider. 1. Do we send position commands to the ESC (or thrust or speed)? 2. Where do we get the actual position from? 3. What...

Best starting point is the source code for now. https://github.com/wernerdaehn/CC3D-CableCam-Controller/blob/master/src/odrive.c Yes, it is connected just like the VESC via UART.

I am planning to get back to this project in the next months but do not have any spare time at the moment. What ESC are you using? I am...

I am testing if the connected chip is an EEPROM during init. For that I check for specific vendor IDs and my guess would be on that board it is...

Correction, I do not check for the vendor id. That part got removed already. So it is the write itself that has a problem. Hence I would need to know...