How to read ESC Data Hobbywing X ROTOR X8 100 Kv

Osman_Kadayif · September 27, 2023, 8:46am

Hi there ,

I am try to read esc data in Hobbywing X ROTOR X8 100 Kv. I am trying read esc data usb ttl but ı dont read actually data is coming but ı dont show serial port terminal. Can ı do without hobbywing datalink ? I couldn’t find any documentation on connecting to the ESC other than datalink. With which communication protocol does hobbywing XROTOR X8 ESCs send data?
Can you help me please ?

amilcarlucas · September 27, 2023, 8:50am

github.com/ArduPilot/ardupilot

Add support for HobbyWing ESC telemetry

ArduPilot:master ← peterbarker:pr/hwing-platinum-v3

opened 01:56AM - 13 Jan 23 UTC

peterbarker

+21757 -11

This PR now parses both v3 and v4 protocols. edit: added support for the XRoto…r-v4 edit: added support for DataLink devices Something like this: https://www.dragonrc.com.au/HW-100A-V3-Platinum-series-aircraft-system-p/drc-hw100av3.htm Reads telemetry data from this ESC and makes it available via ESC telemetry. Includes simulator for same. There are some things that we need to discuss: - tridge is uneasy with the new parameters, worried we're going to end up with way too many of them - he's thinking in the main firmware we have a single parameter, an enumeration of which (single) protocol you want to parse - so something like `AP_ESC_Telemetry::Protocol::HobbyWingPlatinumProv3`, `AP_ESC_Telemetry::Protocol::TMotor` etc - tridge suggested this go onto the IO thread - I'm uneasy with that, having looked at what else is on that thread. Given this has to be relatively-real-time, I'm not sure it should share a thread with SD card formatting, parameter-saving and SmartRTL cleanup. - perhaps we could have a thread dedicated to telemetry in general (and maybe move blheli to it?) - is the use of the serial timing-constraint code legit? ``` Board AP_Periph blimp copter heli plane rover sub Durandal 1304 1408 1408 1224 1416 1280 Hitec-Airspeed 0 KakuteH7-bdshot 1216 1264 1272 1240 1248 1216 MatekF405 0 0 0 0 0 0 Pixhawk1-1M 0 0 0 0 0 0 f103-QiotekPeriph 0 f303-Universal 0 revo-mini 0 0 0 0 0 0 skyviper-v2450 0 ```

But you will need to compile the source code.

Osman_Kadayif · October 2, 2023, 2:26pm

Thanks for answer I couldn’t find anything to solve my problem on the page you sent. My motor data cable colour are black , red and white but this video green and yellow .

Actually, I am trying to do the same thing as in this video, but when I connect to the drone can gui, I cannot access the data. I am sharing with you what I see on my screen. I would be happy if you help.

amilcarlucas · October 2, 2023, 4:09pm

Did you recompile the source code after applying the changes from that or branch?
Did you upload the resulting firmware to your flight controller?

Osman_Kadayif · October 3, 2023, 5:54am

Yes I applied this. My problem is ı cant see org.dronecan.gui_tool in the dronecan gui. İf ı read this probably ı solve problem.

amilcarlucas · October 3, 2023, 11:38am

The T-Motor datalink V2 does not speak CAN properly. You need to connect serially to it.

Have you read the GitHub PR text? It explains how to configure it.

Osman_Kadayif · October 17, 2023, 8:32am

16 01 02 33 39 00 87 00 87 04 0F 01 CC 00 03 00 23 D2 D2 00 00 D8 04
9B 16 01 02 33 3A 00 87 00 87 04 0F 01 CC 00 03 00 24 D2 D2 00 00 DA 04
9B 16 01 02 33 3B 00 87 00 87 04 10 01 CB 00 03 00 23 D2 D2 00 00 DA 04
9B 16 01 02 33 3C 00 87 00 87 04 10 01 CC 00 03 00 23 D2 D2 00 00 DC 04
9B 16 01 02 33 3D 00 87 00 87 04 10 01 CB 00 03 00 23 D2 D2 00 00 DC 04
9B 16 01 02 33 3E 00 87 00 87 04 11 01 CC 00 03 00 23 D2 D2 00 00 DF 04
9B 16 01 02 33 3F 00 87 00 87 04 11 01 CC 00 03 00 26 D2 D2 00 00 E3 04
9B 16 01 02 33 40 00 87 00 87 04 0F 01 CC 00 03 00 25 D2 D2 00 00 E1 04
9B 16 01 02 33 41 00 87 00 87 04 10 01 CC 00 03 00 25 D2 D2 00 00 E3 04
9B 16 01 02 33 42 00 87 00 87 04 11 01 CC 00 03 00 24 D2 D2 00 00 E4 04
9B 16 01 02 33 43 00 86 00 86 04 11 01 CC 00 03 00 22 D2 D2 00 00 E1 04
9B 16 01 02 33 44 00 87 00 87 04 10 01 CC 00 03 00 24 D2 D2 00 00 E5 04
There are my raw data and protocol file. Current data is wrong can you check this?