![cleanflight firmware for naze32 hex cleanflight firmware for naze32 hex](https://ftforumx2.s3.amazonaws.com/2018/07/188042_516d8876020b6c72e1101375e0683d2e.jpg)
#define IBUS_MEAS_TYPE_RESERVED 0x0f //2 bytes Pressure in #define IBUS_MEAS_TYPE_GPS_GROUND_SPEED IBUS_MEAS_TYPE_SPE //2 bytes will be handled by build in km/h formatting - format method must be checked #define IBUS_MEAS_TYPE_ERR 0xfe // Error rate #define IBUS_MEAS_TYPE_NOISE 0xfb // Noise #define IBUS_MEAS_TYPE_ALT 0xf9 // Altitude //2 bytes signed in m #define IBUS_MEAS_TYPE_SPE 0x7e // Speed //2byte km/h
![cleanflight firmware for naze32 hex cleanflight firmware for naze32 hex](https://blog.seidel-philipp.de/wp-content/uploads/2015/02/download-300x243.jpg)
#define IBUS_MEAS_TYPE_ODO2 0x7d // Odometer2 #define IBUS_MEAS_TYPE_ODO1 0x7c // Odometer1 #define IBUS_MEAS_TYPE_PRES 0x41 // Pressure #define IBUS_MEAS_TYPE_EXTV 0x03 // External Voltage #define IBUS_MEAS_TYPE_TEM 0x01 // Temperature #define IBUS_MEAS_TYPE_INTV 0x00 // Internal Voltage #define IBUS_CMD_TEL_MEAS 0xA0 // Command to get measurement from a telemetry module #define IBUS_CMD_TEL_TYPE 0x90 // Command to discover type of a telemetry module #define IBUS_CMD_TEL_DISC 0x80 // Command to discover a telemetry module
![cleanflight firmware for naze32 hex cleanflight firmware for naze32 hex](https://i5.walmartimages.com/asr/6752a1fd-1292-4472-a97d-fab594639b5b_1.32890678e6159a8e2062f135140b1098.jpeg)
#define IBUS_CMD_TIMER_SYNC 0x81 // Command to synchronize a telemetry What do you think? #define IBUS_TELEMETRY This more is very limited one and used by multi sensors from FlySky - I have skipped this mode completely so I can send my long telemetry. This more requires confirmation from RX before allowing telemetry packet being send. It is working but not with i6 it has 64k flash and RX fw is about 32kB.īTW I have figured it out what was wrong with my telemetry - if I send something larger than 4 bytes I am writing to memory area starting "4th telemetry mode" (just switch value).