-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZTW Mantis G2 ESC telemetry support #112
Comments
Without doc about the protocol, it is not possible to implement it. |
I got the protocol information from the ESC manufacturer. |
I propose that you keep it currently. |
OK -no problem. |
I hope to be able to look at the doc quite soon. |
This the info I got: This data package is used by the ESC for reporting data in real time, and it reports every 50ms. UART Baud 115200 Bps. Byte17: UART-TH serial throttle input |
Thanks for the info. |
Wow - that was quick. Testing may take some time as I aam not at home at the moment. |
OK. |
I have connected everthing to a FrSky Archer M+ receiver with FBus. PWM is generated correctly since esc is running the motor on ch3. But the LED is blinking red and no EXC telemetry. Version = 2.9.26 Protocol is Fbus(Frsky) Gyro is not configured No sequencers are defined Config parameters are OK |
I changed to a Jeti receiver but still the LED on the 2040 is blinking red although Telemetry is received in the transmitter and servos outputs are working. I also added a temp sensor on V3. Protocol is Jeti (Exbus) Gyro is not configured No sequencers are defined Config parameters are OK the 80F0 line onl appears if the motor is not running. The other output is during a motor run. Hope that info is helpful to get the telemetry to work. |
Thanks for the feedback. I would have to make a check on my side in order to generate a valid frame with another computer and see if oXs can get it. About the temp, I can change the text being displayed and the symbol for the unit. |
I made some tests. |
I flshed the 2.10.3 and tested it with the same configuration. Protocol is Jeti (Exbus) Gyro is not configured No sequencers are defined Config parameters are OK Same sequence at the beginning motor is off and I do get the 80E0 Regarding the temperature it might be most flexible (if this can be done) to have a kind of "Vx_type" command. Best regards and many thanks for your work |
The characters read by oXs are in no way a valid frame. So it is normal that you do not get data on the handset. Perhaps the issue is linked to the way the ESC output is build at hardware level. |
With a3k9 Pullup at the ESC telemetry input it looks like this: 8040 |
This does not match the expected frame at all. I have no more idea. |
It seems that there are several projects that use a RP2040 as logic analyser. |
I have done a hex dump using my picoScope software. Maybe this helps |
Thanks for the capture. |
For the capture, did you used a set up : 8bits Even parity 1 stop bit? |
For the capture I have used 115200 8N1. Do you need other parameters (8E1)? |
In the doc (some days ago) , it was said that signal was 8E1. So I used this setup in oXs. |
I can't find the 8E1 setting in my docs. |
Sorry, it was not specified if it was 8N1 or 8N1. |
Real-time Data Protocol.docx I have attached the original doc file I got from ZTW to avoid any transmission error. It was just converted to a docx. |
I have a ZTW Skyhawk ESC. Does the current Implementation support this ESC? |
I implemented the ZTW telemetry protocol that is documented in a post here above. I can try to fix eventual bugs if I get some feedback. |
Hmm, until now i cannot see a sensor on my transmitter when i select discover new sensors. Do i need this resistor between TLM and RX? |
I do not think that you need a resistor. Question: do you have a logic analyser? Some captures could also help to debug the issue. |
These are the frames that i get if i give a little bit power on the motor: I have a Saleae logic analyzer, but don't know how to use it. If you can give me some support here i can have a try. |
The debug messages are not the expected one. I propose to make a capture with a logic analyser. Did you already installed the software for the Saleae logic analyser. Here a link to it: Here a link on how to make a capture. To make a capture: You can then send me this capture e.g. by mail at [email protected] |
@mstrens Are you still interested in getting this fixed? Tried it today with a Mantis G2 65A but no luck. I used a RPi2040 which is working flawlessly with a BLHeli_32 ESC and changed the ESC type but no luck. The ESC sends out telemetry to the program card so there is data available. I do have another RPi2040 setup with the uLA firmware and can get some PWM signals from a receiver in Pulseview. I also get UART binary code when I listen to the ESC, but then my limited knowledge on logic analyzers reaches it's end. ;) |
Yes I am interested in getting this fixed. |
@mstrens friendly reminder; just ping me when you have time for this and let me know what you need. |
ZTW is one of the major ESC manufactureres and many other brands offer these ESCs as OEM solution.
https://www.ztwoem.com/product/mantis-g2-85a-105a-125a/
The current Mantis G2 series come with a RX/TX port and using the BT Adapter telemetry values can be read out.
Maybe OxS can take advantage of this in order to implament a telemetry feature for this series similar to the Hobbywing Telemetry support.
Unfortunately I have no information about the data protocol and my reverse engineering skills are very bad to non existing.
The text was updated successfully, but these errors were encountered: