Open jasc76 opened 6 months ago
Same question from my side, I would really like to have it. It serms the protocol is public:
Jeti Ex telemetry is implemented. It was developed with arduino legacy and ported to rp2040. It should work as is now, but it haven't been tested on rp2040 yet. Please select Jeti Ex Bus in receiver protocol. If any issue please post the debug output. See Jeti Ex Bus in readme
Seems to be a misunderstanding. What's needed is to read out the telemetry values from a Jeti Mezon Speed controller and send it to FrSky SmartPort receiver.
config->esc_protocol == ESC_JETI ;-)
The Mezon sends the telemetry in Jeti Ex format which is implemented for the receiver. In Ex bus, the telemetry is requested from the receiver and it also sends the channels data.
I need to confirm this and identify each sensor instance from the Mezon to the equivalent MSRC sensor. For that I've added a serial monitor to msrc. Connect esc to GPIO5 as usual and select Receiver protocol->Serial Monitor with the following parameters and post output:
Please help me out! I wired the RP2040 like shown in the msrc_gui.exe and in the picture below:
I flashed the current release from https://github.com/dgatf/msrc/releases and put the lua from https://github.com/dgatf/msrc/blob/master/lua/msrc.lua to the transmitter sd-card. The selected protocol in msrc_gui.exe is FrSky Smartport.
The problem is that when I start the msrc.lua it hangs in "connecting..." and nothing happens. I testet it on a Taranis X-Lite and a Horus X12S as well a X6R with ACCST and a RX6R with ACCESS..
Sorry, lua app needs to be updated. Please use msrc_gui for configuration.
Which esc model are you using?
It seems that you have no sensor enabled.
If something is not working, please post the debug.
Im using a Mezon lite 160. I tried it with the msrc_gui, switched it to ESC PWM and got this log (from the very beginning incl. ESC protocol switch):
USB. Debug enabled USB (126) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB. Processing (142) 0x30 0x30 USB. Updated config USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB (104) USB. Debug enabled USB (126) Esc PWM (216) < Rpm: 0 Esc PWM (98) < Rpm: 0 Esc PWM (98) < Rpm: 0 Esc PWM (98) < Rpm: 0 Esc PWM (98) < Rpm: 0 Esc PWM (98) < Rpm: 0 Esc PWM (98) < Rpm: 0 Esc PWM (98) < Rpm: 0 Esc PWM (98) < Rpm: 0 Esc PWM (98) < Rpm: 0 USB (104) Esc PWM (98) < Rpm: 0 Esc PWM (98) < Rpm: 0 Esc PWM (98) < Rpm: 0 Esc PWM (98) < Rpm: 0 Esc PWM (98) < Rpm: 0 Esc PWM (98) < Rpm: 0 Esc PWM (98) < Rpm: 0 Esc PWM (98) < Rpm: 0 Esc PWM (98) < Rpm: 0 Esc PWM (98) < Rpm: 0 USB (104) ....
If I did it wrong please give me a step by step instruction what to do. I think there is something I currently do not understand.
Does Mezon lite 160 output rpms in pwm?
Couldn't find that.
Jetiex for mezon is not implemented. Though you can select serial monitor in receiver protocol at 115200 and post output. Connect telemetry line of the esc to gpio5 while connected to the receiver. And gnd to gnd.
Got it. It was completely my fault: too late - didn't carefully read. Here is your log: Mezon 160 lite 1st log.txt Please tell me if you need more!
The output doesn't look good. Almost all zeroes. To be sure, to reverse engineer the mezon, it is needed a jeti receiver. Which receiver are you using?
I am using a FrSky RX6R and I do not have a jeti receiver. But I can borrow a jeti system including different sensors from a friend next week. So we have to wait. I will give you feedback if I have more information.
Ok
Am 17.10.24, 21:18 schrieb DanielGeA @.***>:
Were you connecting the telemetry of the esc to the smartport? If not using jeti recevier, it must not be conected. If you did, that might be the reason it didn't. You can try connecting esc telemetry line only to gpio5 (not to smartport also) and gnd to gnd.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
I did not connect the sport. The only connection to the RP2040 is the usb and signal and gnd to the telemetry port of the esc. The smartport connection is open/not used at RP2040 and receiver.
...but good question: If I'm using jeti, I must connect the esc telemetry to both the RP2040 and the receiver telemetry port?
When using jeti receiver, yes, you have to, because the telemetry is polled from the receiver.
Okay, I will do so.
Here a picture of my FrSky setup:
Ok
Here the first two logs from the jeti communication. The MULI is a 6S LiPo sensor which had 6 cells connected while logging.
log 2 - jeti MULI 6S.log log 3 - jeti Mezon 160 lite.log
I know it looks already strange. So I have some questions regarding the jeti ex bus spec:
Could it be that I need a 2.4k resistor at the pin to the esc/sensor? I tried this but it doesn`t change anything. And is the baud rate correct? Jeti mentioned 125kBaud for low speed and 250kBaud for high speed, but the gui offers just 115kBaud.
I've made the baudrate editable, so you can set any value. Download updated msrc_gui.
You don't need to bother with resistors. Connect jeti sensor to ex port of the receiver and connect (between), data line and gnd to rp2040. Don't make other connections to rp2040.
Connect as shown below:
Hi
any plans to include Jeti Mezon EX telemetry ??
Regards Jan