Which baudrate you are using for the HC12 link? From you param_for_joystick.param it should be 57600. But on mission planner COM8 you are using 115200. This is not matching.
sorry for wrong baud but because alot of error happen each time am test new thing do reset to default of param
after update baud serial2 to 115200
com8 try connect.txt (15.4 KB)
you can see in end get 1 heartback after this am try again and it get no heartback
setting am use in both
other thing happen i dont no is normal or not when am upload sketch to board esp32s3 and after that am disconnect and do wiring to hc to go in porgram mode (AT COMMAND) after that connect board to pc the hc if am write AT in serial must get ok am get garabage data must press reset button in esp to hc go in AT COMMAND every time am disconnect board and connect again must after connect press rest to hc go in program mode i dont know this can cause problem in normal work or not
Wrong way. Don’t try higher baudrate on FC and HC12 side use lower baudrate on Mission Planner. The textfile shows many lost packet information so reduce speed.
am reduce to 57600
com8 try connect.txt (52.1 KB)
from last response to you:
other thing happen i dont no is normal or not when am upload sketch to board esp32s3 and after that am disconnect and do wiring to hc to go in porgram mode (AT COMMAND) after that connect board to pc the hc if am write AT in serial must get ok am get garabage data must press reset button in esp to hc go in AT COMMAND every time am disconnect board and connect again must after connect press rest to hc go in program mode i dont know this can cause problem in normal work or not
try reduce to 38400??
I don’t understand what you are doing. Can you describe it a little more.
What wiring you are doing to get in programm mode.
Why you upload new sketch to esp32s3, better is to stay with one version and not to change to much different things.
Can you first use the testsetup, ESP32S3 via FTDI direct connected to PC and connect via COM8 to mission planner. And send again make com8 try connect.txt so that we see how a good attemp looks like.
Too low of a baud can also cause missed packets and timeout
But, on hc12 lower baud mean more range at cost of latency. If the esp is using hardware serial port, keep it at 57600, else try 19200 or 38400
first : i have other esp32s3 when am tell to you am upload sketch am upload sketch to esp32s3 second one i have not one on it ardupilot firmware mean i have 2 esp32s3
the wiring when go to AT COMMAND
ESP32S3 HC12
3.3V VCC
GND GND
GPIO4(RX) TX
GPIO5(TX) RX
GND SET
com8 try connect(TEST SETUP).txt (15.8 KB)(This by connect ftdi to gpio 11,12 serial2 in esp fc)
okay i will try your suggestion
So, I assume on this com8 try connect(TEST SETUP).txt mission planner connects to the ESP32S3, correct?
Why you are using GPIO4 & 5 for AT COMMAND? Is it a different ESP Software? I thought you execute AT COMMAND to the HC12 via FTDI.
yes
yes am use sketch to program hc by second esp i have
Why not using FTDI?
Is your extra ESP Software fully transparent from PC Port to HC12 port using same baudrate etc?
As I don’t know this software I can’t say if the behaviour you described above is correct. And due to this I am not sure if both HC12 are using same baudrate 57600 fully transparent. But this is a MUST. All com ports (ESP32S3 FC ; HC12 air unit; HC12 ground unit and PC Comport must use the same baudrate with 8bit, no parity, 1 stopbit.
i am sure of setting and am check after am set baud am check all setting by command AT+RX , Second am determine the both hc work when connect both hc , esp fc>hc12 ,ftdi>hc12 am see led tx and rx blink in both i think thats good sign But if you have any doubts about this method, suggest another one to me
update am edit by ftdi both and check is set to right setting
I don’t know on which port of the HC12 the leds are connected, either on the logic data port or the air port. But blinking only shows that there are some bit changes on that line. It is not showing if the bit change is with the correct baudrate.
Best methode to set and check the HC12 is
- Connect to ftdi
- Enter AT Mode and set parameter
- Release SET pin on HC12
- Unpower HC12 & FTDI
- Set PC to corresponding baudrate if changed
- Repower HC12 & FTDI with HC12 SET pin released
- Enter AT Mode by HC12 SET pin to GND
- Verify settings via AT Command
- Release HC12 SET pin.
am do like you said and check and try connect and is same 
So, if we assume the HC12 connection is fully transparent I momentary don’t understand why it is not working.
i dont know what problem but by test by esp32 drone bridge it work and connect why by hc12 dont work i dont know i will wait respond @Ishitbh which one is have can this be problem i dont know 
You can try to reduce the load on the port by reducing the mavlink stream rates to 0
MAV1 Parameters
MAV2 Parameters
MAV3 Parameters
and on Mission planner / CONFIG / Planner all Telemetry rate to 0
esp32 drone bridge is not using a transparent uart link. It uses wifi protocol between the bridge and mission planner. Same as the inbuild WIFI function of your ESP32S3 FC
Do the test with reduced stream rates with both setups the normal HC12 and the Test Setup to be sure that this work in principle