How are on the receiving HC12 (PC side) and FTDI VCC and GND connected?
With the direct connected FTDI connected to ESP did you tried to connect to mission planner?
Did you set mission planner to 57600 Baud?
the vcc and gnd for hc connect to ftdi is get power from power rail breadboard and this power rail supply other hc12
you mean connect ftdi to pins tx ,rx of uart chip or ftdi connect to pins 11,12 assign to hc?
yes am sure is set to 57600 , but in some time is connect to mission but when try again with same setting in mission like arming disable or decrease telemetry rate not chnage any thing get no heart beat
Connect FTDI TX to ESP pin 12; FTDI RX to ESP pin 11; FTDI GND to ESP32 GND;
Plug FTDI USB to PC USB port. Check if this port is running with terminal. If yes close terminal and connect mission planner to this COM Port.
As you don’t have GPS set
SERIAL3_BAUD = 57;
SERIAL3_PROTOCOL = -1;
SERIAL4_BAUD = 57;
SERIAL4_PROTOCOL = -1;
i connect both to pc and do your connection and am try to connect to mission with baud 57600 and it connect
If this works than the FTDI is just simulating your telemetrie link.
So, from ESP; FTDI and MISSION PLANNER side every think works well.
The problem must somewhere with the HC12 modules.
Don’ change any setting on ESP or MISSION PLANNER
Set both HC12 to 57600 baud and verify that this is not changed by power reset.
Maybe reduce HC12 transmit powerlevel if the boards are nearby each other
Disable RTS/CTS flow control if set on both HC12 and verify that this is not changes by power reset.
Check that your FTDI is set to logic level 3.3V by the jumper near to the pin header
Connect ESP32 pin 11 to first HC12 RX
Connect ESP32 pin 12 to first HC12TX
Connect ESP GND to first HC12 GND
Connect FTDI TX to second HC12 RX
Connect FTDI RX to second HC12TX
Connect FTDI GND to second HC12 GND
I am not sure if your FTDI VCC pin can power the second HC12, so power this modul from your rail. But don’t connect this rail to the FTDI VCC pin as this is an output on FTDI.
Plug FTDI USB to USB as before and make same procedure with terminal and if successful with mission planner as before
DISABLE RTS /CTS This not avaible in hc12 or is in mission if in mission what is exact name of it
and still not connect error no heart back
OK, jst checked some settings of HC12. It seems the module is not using RTS/CTS by it own. So ignore this.
But also it looks something wrong, so the communication seems to be not so transparent as the direct connect test before. Try to play with FU1 mode on HC12
Hi
I am using hc12 telemetry and maybe can help. For me, it works atleast.
My settings are fu3 and 57600 baud. Remember to swap tx rx
First set fu3 and then 57600 baud and just verify before end.
In my first hc12, I accidently powered without antenna and the first didnot work, because of no antenna
Also try to use external antenna as it improved range
Latest mavlink2 works.
Can do tests on my setup if needed for debugging bere
If you have spare Arduino, even one, try t sting hc12 with it
Even two ftdi are enough
Also, you can try connecting ftdi to the serial port of hc12 and no hc12 and test once to see if esp is giving data
I have not read the entire thread so I might have said something that you have previously attempted.
still failed 
am try by baud 57600 ,115200 is failed
am use with fu3 and try to decrease power transimation
am work with soldering antena
am program hc by esp32 s3 and it work and verify all setting like am want by AT+RX
am try to connect ftdi to gpio i want use and it get data and try to do connect to mission and it work
all test above am try and still failed
but i have idea to test by esp drone bridge because i have other one esp32 s3 to see it connect or same not connect
Any success?
Can you again make some test with terraterm log?
- normal setup ESP → HC12(air) → HC12(ground → FTDI → PC (terraterm);
- test setup ESP (HC12 port) → → FTDI → PC (terraterm);
Both test press reset on ESP32 and than run 45sec.
teratermcom4.log (9.4 KB)
teratermcom8.log (3.5 KB)
com4 is esp ardupilot fc postion
com8 is ftdi>hc12>pc
nice news am try to use telemetry by dronebridge (second esp32 s3 )by same pin (gpio rx 12 ,tx 11 )same setting in mission planner same baud same protocol only this 2 paramter am use
serial 2 baud
serial 2 protocol
it connect and work by both tcp , udp
but to be honest i still want use hc12 if you have suggestion am want to know
The dronebridge test only shows what we already know from the test with ESP32 directly connected to PC (Mission Planner) via FTDI. Your problem is the HC12 connection.
Describe a little more how the setup was for the teratermcom8.log.
I need the two logs as said in my last post. The terraterm log must be set to “Binary Mode” without timestamps. Set the teraterm baudrate to the same setting as the ESP32 FC telemetrie port.
In both logs use the ESP32 FC telemetrie port (gpio rx 12 ,tx 11 )
- normal setup ESP(gpio rx 12 ,tx 11 ) → HC12(air) → HC12(ground → FTDI → PC (terraterm);
- test setup ESP(gpio rx 12 ,tx 11 ) → → FTDI → PC (terraterm);
Check also again if mission planner is connecting for one or both connections
normal setup com8.log (1.4 KB) (thats am try to do connect by esp fc (com4)in mission planner)
test setup com8.log (438.2 KB) (thats am try to connect by esp fc (com4)in mission planner)
normal setup com4.log (33.3 KB) (thats am try to do connect to by ftdi>hc12 in mission planner)
in test setup the postion of ftdi>gpio(12,11 in espfc) it connect to mission planner
in normal still failed
but when am try to connect to mission by normal setup (in ftdi>hc12 )am see both led tx, rx in esp fc and both led tx,rx in ftdi blink thats mean the both hc12 is communicate with other
can do sketch to both hc12 to see is communicate with other or not (i think is usless because in up when am said both blink is good sign is both in same setting about baud. channel , mode )
edit 2:
in file dwdef am used if any thing must add or edit to can connect motor and detect my esc is use blheli s , and am configure to work in motor work in bidirectional am try to connect to and configur joystick by usb and but in test motor when try it not move and when see docs some paramter and not find when search in full paramter
hwdef.zip (992 Bytes)
The setup use joystick by usb and use esp fc and connect to it esc signal ,gnd pin
Am edit paramter arming check to can arm and am see in statur ch1out ,ch3 out the number change when use joystick ,
The problem is esp fc can detect esc because when go to test motor is not move any motor
All your 3 logfiles show mavlink heartbeat messages.
Can you a little more exact describe which setups you are using for which log.
I assume (hope) that
- normal setup com8.log == ESP(gpio rx 12 ,tx 11 ) → HC12(air) → HC12(ground → FTDI → PC (terraterm on comport 8);
- test setup com8.log == ESP(gpio rx 12 ,tx 11 ) → → FTDI → PC (terraterm on comport 8)
- normal setup com4.log ???
- what does mean “thats am try to do connect by esp fc (com4)in mission planner”
Regarding your setup of ESCs and Motor this has nothing to do with a hwdef file. The hwdef only describes the HW of the FC in this case your ESP32S3 board.
All other must be done by correct configuration of params. So show save your params to a file an show it here.
What exact ESC and Motors you are using. Supports the ESC bidirectional motor rotation? ESP32 only supports standard PWM control for ESCs
normal setup same to your describe
test setup same to your describe
normal setup com4.log: mean thats a data am get when am try to do connect by normal setup in postion ftdi>hc12>pc (because you know cant open com port am use in other thing ) in this am open teraterm to save log of com4 espfc when am try to do connect in com8 ftdi>hc12>pc
idea : (do a normal sketch to see both hc12 communicate to each other or not )???
the param am use:
parm_for_joystick.param (13.2 KB)
am change some param to by pass arm errors to can get number when in chout , can do test motor
esc use is 45A: https://ar.aliexpress.com/item/1005007500019321.html?spm=a2g0o.order_list.order_list_main.36.2dfc1802sNBGtt&gatewayAdapt=glo2ara
motor is normal one 1400kv A2212/10T (am use only one motor with on esc for test to see it work or not)
this is configuration in am do in blehli_suite
you said this : ESP32 only supports standard PWM control for ESCs
am try before start in ardupilot to control motor by esp to work in bidirectional and it work by use this library: GitHub - DrGlaucous/DShotRMT_NEO: DShot support for ESP32
Do I understand correct that “normal setup com4.log” is a second parallel connection between PC and ESP32S3 to one of the USB-C connectors while the ESP32S2 pin 11/12 are connected via HC12 to mission planner using com8?
You are right, I was not exact. ESP32S3 is just a micro controller and so the micro controller itelf can also handle DSHOT with the correct piece of software like your DrGlaucous link. But this piece of software, the DSHOT driver is not implemented to the ESP32(S3) Ardupilot Firmware. So to be exact ESP32S3 based Ardupilot Flight controller can only use normal PWM for the ESC.
But I hope your cheap ESC is backward compatible and also can use normal PWM. I also hope you have some manual for this ESC, I didn’t found this on www.
Set MOT_PWM_TYPE to 0 (default)
You are trying to setup a skid steering rover correct? So you need at least 2 ESC and 2 motors.
Also as said before, as long as you don’t have a GPS set
SERIAL3_BAUD = 57;
SERIAL3_PROTOCOL = -1;
SERIAL4_BAUD = 57;
SERIAL4_PROTOCOL = -1;
yes
yes it can it come with default support pwm
my setup rover is 2 brushless in back and servo in front for steering
i will try this for hc12 , but do disable arming check or reset to default , or dont change any thing in param only change this (SERIAL3_BAUD = 57;
SERIAL3_PROTOCOL = -1;
SERIAL4_BAUD = 57;
SERIAL4_PROTOCOL = -1;)??
update : am test the my motor with esc not one am said to you because am determine the one am sent to you above is work in dshot not pwm am try to search what method to can work in pwm or multishot
am test with with other esc has cover yellow it work by set
arming reqerd to 0
min , trim in servo output to 1000
and am test with joystick and motor test and it work
If I understand correct now in principle your ESP32S§ based FC can control one (or more) ESC / Motors via Joystick input. So this problem is solved.
Still the HC12 connection problem is open.
Did you tried this with some other GCS?
If you open Mission Planner do you have one or two windows?? The normal “Mission Planner 1.3.83 built” in foreground and a “Mission Planner” message window in the background.
If you have this second message window, can you send a copy of all information shown during you try to connect your ESP32S3 via HC12 to mission planner?
tried with other GCS?
NO
com8 try connect.txt (11.5 KB) (log in bacgroun terminal open when open mission planner)
am copy in file all massage appear from try to connect ended to failed connec
com8 (ftdi>hc12)