+\r
+/*\r
+ * FLAGS\r
+ *\r
+ * Taken from include/low-can/can-message.hpp in agl-service-can-low-level.\r
+ * The flags values in the generated message_definition_t definitions needs to\r
+ * match usage of these flags in the binding, e.g. in the various member\r
+ * functions in low-can-binding/can/message-definition.cpp.\r
+ *\r
+ * ATM the only flags known to be used are:\r
+ *\r
+ * CAN_PROTOCOL_WITH_FD_FRAME\r
+ * J1939_PROTOCOL\r
+ * ISOTP_PROTOCOL\r
+ * BYTE_FRAME_IS_BIG_ENDIAN\r
+ *\r
+ * Note that for BYTE_FRAME_IS_BIG_ENDIAN, even though it is referenced in\r
+ * message-definition.cpp, the member function that does so seems currently\r
+ * unused, so it is not clear what the intended usage actually is.\r
+ * The JSON parser for CAN messages would likely need an additional field\r
+ * added to allow setting it, for now that is being left for a future update.\r
+ */\r
+\r
+#define CAN_PROTOCOL 0x0001\r
+#define CAN_PROTOCOL_WITH_FD_FRAME 0x0002\r
+#define J1939_ADDR_CLAIM_PROTOCOL 0x0004\r
+#define J1939_PROTOCOL 0x0008\r
+#define ISOTP_PROTOCOL 0x0010\r
+#define ISOTP_SEND 0x0020\r
+#define ISOTP_RECEIVE 0x0040\r
+#define BYTE_FRAME_IS_BIG_ENDIAN 0x0080\r
+#define BIT_POSITION_REVERSED 0x0100\r
+#define CONTINENTAL_BIT_POSITION 0x0200\r
+#define INVALID_FLAG 0x8000\r
+\r
+\r
+#define VERSION_LOW_CAN "2.0"\r
+\r
+\r
+std::string VERSION_FILE = "1.0";\r
+\r