teraterm.log (6.8 KB) am try and still failed
(last one sorry miss thing in tera term do)
Next test :
hwdef.zip (960 Bytes)
teraterm.log (9.7 KB)
same not connect to mission 
Hm, can you try to connect via wifi TCP? the ESP acts as WIFI AP with SSID ardupilot123 and PSWD ardupilot123
it work 
and connect to misson but still with com not why this happen and what next must do
it connect with peripheral and without it connect in 2 method
Your board has two connectors at the front, which one you are using for connection with programmer, terraterm and mission planner?
Did you also checked the other port?
am use uart one because can get serial , other is usb native otg
am try by same cable (usb to type c) it work by program with arduino and same to upload firmware it work in all and am try to (type c to type c ) 2 cable failed and if am try to connect by com port by other port get this message connect failed with this in exception details
I don’t get your info. I tr< to describe what I understand
- you connect PC to UART1 via USB[A] to [C] cable and it work well with arduino ide, ardupilot firmware upload and terraterm but not mission planner.
- you connect PC to UART1 via USB[C] to [C] cable and it failed at all or only mission planner?
- you did not tried PC to USB native otg at all.
Which mission planner version you have.
Did you checked Andras Schaffers post above?
1-yes all work only mission planner dont work
2-only mission planner
3-am try and failed connect to mission
am try me method Andras said and failed
So you have both types of connectors USB [A] and USB [C] on your PC?
Can you test with terraterm connection like No 2 and No 3?
What is shown in Windows Devicemanger under COM & LPT ports if you connect like No 2 and No 3
yes have both USB [A] and USB [C]
teraterm by no 2 UART1 by port usb by cable (usb type c) to (usb type c)
teraterm.log (2.7 KB)
what am show in com & lpt (this by port usb)
and (this by port uart)
other thing am determine in last before start to ardupilot
the port uart if am use cable (Type c to type c)
When using a Type C cable to connect to the ESP32, it has to be rotated. Imagine the connector connected to the ESP32. We’ll assign a number to each side of the connector. When connecting the ESP32, we’ll assign the number 1 to side and 2 to the other side (in A side only ). The connector connected to the board works with side 1. If I flip it to side 2, it doesn’t work.
i dont know this will do problem am get or not but by cable usb A to type c the type c connect to esp work in both side
after do some search am find this problme related to thing has name of uart has name i think c01 ,c02 thing like that (i dont know can problem of side okay and side not okay do my problem or not)
update:2
am edit file dwdef for (esp32s3empty) original one when download ardupilot from git hub to work with tcp and it connect to mission planner by tcp but by com still failed
update: 3
am check in config section in mission am check this (reset on usb connect (toggle dtr)) and after it am try to connect and it connect by com am try to test it after connect
Maybe I found some interesting point.
I just updated my mission planner to latest 1.3.83 build 1.3.9384.38258 and now I can simulated your behaviour.
If both control fields under Planner / Connect Reset are enabled mission planner don’t connect to my ESP32. If both are unchecked or only one is checked connection worked.
am test of problem com port for this with 2 optioon in section (connect reset) in tab config
if am check only (DIsable RTS reset on ESP32 Serial USB) not connect
if am check only (Reset on USB Connect (togglee DTR)) it connect take about 5 sec to connect
if am check both it connect but am see it take longer to connect i think both option They influence each other because this it take long to connect about 15 to 25 sec
Q1) i want any docs help to configure file hwdef i mean docs tell option about wifi to use tcp or udp whats value must put to get am need and etc like mpu
Q2) after am get my problem am open ticket in github (ESP32 S3 Cant connect to mission planner · Issue #3636 · ArduPilot/MissionPlanner · GitHub) to my problem but after suggestion in github not help am come here to get more help i want to do mention or any method to developer to edit repo of esp32 to know other people want use esp which thing to check and after you test my problem is work in different version like mission planner i want to tell developer to know why this happen (this question i know is wierd but am new in this like how developer handle thing in big project and i want help )
am test upd is last thing not work in last test and am upload new thing happen after test
Please, take in account ESP32 is not the best for Ardupilot so most developer work on the ST32 based FC using Chibios. The Hwdef comes mainly from this side. So you will not find any good information regarding ESP32. If you like writing a wiki is not only limited to developer.
I know from my experience with ESP32 not only Ardupilot, that some boards have problems with softreset and detection of boot mode. These boards need than additional capacitor 10yF between Pin EN and GND
The Hwdef file is simply editable with the normal editor.
If you open my file, you can see the pins used. Also you can find the wifi entry which is now is set to 1 (TCP) If changed to 2 you have UDP.
Lines for your MPU are comment out by the leading ‘#’. Delete this sign and try
If you change anything in the Hwdef you have to recompile your complete project.
am test udp and it work , am calabiration mpu and it work
but i want to connect hc12 to mission planner am try by test dwdef you sent to me am connect pin rx and tx to uart 1 ,2 (mean test by 2 uart)and configure baud and protocol in full paramter my target is control rover by keyboard like (w,s,a,d) and other hc connect by ftdi and control happen by python script it failed in all tests to commuincate to each other and am be sure the 2 hc in same baudrate (9600)
you have any suggestion or any thing missing not do
I am not sure how it works, I never tried this.
I think you have to use the RC_CHANNELS_OVERRIDE function as shown here:
Your ESP32 FC is not supporting on board scripts at this time. So your python script runs on your PC I assume.
If you have a USB 2 TTL UART (FTDI) converter you can first directly connect this converter to your desired serial port on the FC and test the functionality. Later you can change to your simple wireless UART-bridge (HC12). It is better to go step by step.
After some search am determine am not use RC my situation go under telemetry i am use dwdef file you sent to me last one and am comment mpu to not happen any conflict and am connect hc12 to uart 2 and am be sure about bandwidth am test by loop back and am get response and am try to decrease telemetry rate to 0 and try connect ftdi to pins uart2 to be sure is assign and work and am get on it mav data
my situation is hc 12 connect to ftdi not connect to mission planner when test and get error no heartbeat but when both hc12 connect / one to ESP and other to FTDI am see led tx blink in ftdi when am connect esp and when try to connect to ftdi in mission planner am get no heartbeat and am see both tx and rx blink but still failed am try to change this paramter in full paramter list
serial 2 baud set to 57600
serial 2 protocol am test with mavlink1 and mavlink2
arming requeire
arming rudder
if you have any suggestion
hwdef.zip (1.1 KB)
I have no HC12 available and I don’t know what your FTDI is?
I think you have some configuration HW and / or SW error. So to help I need all information about your setup.
Show pin by pin your wiring from ESP to HC12 and / or FTDI
Show pin by pin wiring from 2nd HC12 via FTDI to PC
Did you tried to simply connect FTDI directly one side to ESP (UART port you want to use with HC12) other side to PC and try to connect with mission planner?
Show all Ardupilot PARAMs you are using by sending your PARAM File.
Show all settings of your HC12
Disabling the RC pin and MPU in HWDEF is not necessary. These are only assignment. If the pins are not used by real other HW leave it enabled as I send to you. To use RC protocol or not you can select by ardupilot parameters
RC_PROTOCOLS = 0 <> NO RC used.
But this has nothing to do with your communication problem.
my ftdi is this
wiring esp:
esp pin (11 TX) connect to RX pin HC12
esp pin (12 RX) connect to TX pin HC12
HC12 SUPPLY BY 5V by external source and do with him common ground connect to external and hc and esp
Wiring hc12 to ftdi
pin (TX) FTDI CONNECT TO PIN (RX) HC12
pin (RX) FTDI CONNECT TO PIN (TX) HC12
your question:
Did you tried to simply connect FTDI directly one side to ESP (UART port you want to use with HC12) other side to PC and try to connect with mission planner?
Ansrew:
in this am try connect ftdi to pins in esp UART_NUM_2 (11,12) i want to use with hc and when connect and open serial am get mav data that am determine both pins is work and assign right
PARAM FILE(it see on it all param avaible)
PARAM_USED.param (13.2 KB)
but am used only this param am edit it this is param am used and try to solve my problem
Your Question:
Show all settings of your HC12
Ansrew:
if you mean param am try this is param am try to configure hc in mission planner
if you mean setting by AT command : this setting in both hc12 is same
my test to be sure both module communicate with other am do trick name loop back by the hc connect in esp am disconnect it and short rx tx and in other side by hc connect to ftdi am open serial and am try to write any thing am get response in same serial am write on it in this am determine both communicate with them
when am connect one esp to mission in am inside mission am see the other one hc connect to ftdi led tx blink and when try to connect hc connect to ftdi to mission planner am see both led rx tx blink