Endpoint definition file

dakejahl · November 7, 2021, 3:55am

I see on the forums this used to be generated using odrivetool generate-code

Where do I find this file and/or how do I generate this file? I spent hours (finally successful) trying to get the native protocol working and it ended up being the “API CRC” was wrong, I was looking at this

github.com

odriverobotics/ODrive/blob/master/Arduino/ArduinoI2C/odrive_endpoints.h

/*
* This file was autogenerated using the "odrivetool generate-code" feature.
*
* The file matches a specific firmware version. If you add/remove/rename any
* properties exposed by the ODrive, this file needs to be regenerated, otherwise
* the ODrive will ignore all commands.
*/

#ifndef __ODRIVE_ENDPOINTS_HPP
#define __ODRIVE_ENDPOINTS_HPP


namespace odrive {
    
static constexpr const uint16_t json_crc = 0xbe97;

static constexpr const uint16_t per_axis_offset = 101;

enum { 
    VBUS_VOLTAGE = 1,

This file has been truncated. show original

towen · November 7, 2021, 2:21pm

This file is generated by ‘tup’ based on odrive-interface.yaml afaik.

If you want to re-generate it, you can delete the ‘autogen’ folder. Obviously you should never make any manual changes to files inside ‘autogen’.

dakejahl · November 8, 2021, 8:31pm

Is the JSON CRC computed at compile time and saved anywhere? Would be nice to know this value at compile time. I don’t really want to copy/paste this endpoint file since I’d have to modify it to remove all the fibre stuff anyway.

dakejahl · November 8, 2021, 8:35pm

Sorry another question in the same vein… is there not an equivalent of ODrive/odrive_endpoints.h at master · odriverobotics/ODrive · GitHub autogenerated? I really am just looking for an enum for those and a uin16_t for the CRC. Thanks!