ESP32 S3 Cant connect to mission planner

yes am edited

Q1 How you catch these messages and was it during your WiFi-test?

from massage tab in mission planner

thats wierd am try remove esp from breadboard and remove wire and signal work immediately and to be know main problem am put heavy thing in module because I expected the problem can bad ground under module or pads not solder good and same thing.

am try do this 2 tests with second esp32s3 i have and same happen in first one happen with second one

am try to solve it and determine the main problem

am appreciate your help you and @Ishitbh

am success define and all of them work

mpu6500

compass hmc5883l

gps neo 7

barometer ms5611

ln298

joystick

Hello! You can give me files for flashing esp32s3?becase I have same problems with conections. Tanks

for the ms5611 you should see if alt is coming and properly and is not messed up because many modules use ms5607 which reports half pressure, and remaining register map etc is exactly same. if your above sea level alt readings look wrong for your place, like extremely high, change the baro mask param to ms5607.

yes am get the problem you said after buy baro ms5611 and try to test by simple sketch am get weird number and to be sure am go to windy.com and see the number is different in my place after search and see name of chip am determine it sell as ms511 but it use chip ms507

if am sent to you my bins it not help you because am use different module you will use read the thread will help you to determine a lot of problem i get and to success connect if use last version of mission planner check this (Reset in USB Connect ) in config tab in planner section and try connect and use for first test esp32s3empty and define each sensor one by one and when sure one of them connect and work go to other one

272b587d698ae14b95078aef6359cc8bf0a8cf8e

if we need other help ask :heart_eyes:

ms5611 is expensive and thus ms5607 is a common drop-in replacement but the issue is that no seller tells this.

1 Like

It looks like ESP32-S3 support in ArduPilot is still quite experimental, so connection issues with Mission Planner are not uncommon.

A few things you can try:

  1. Make sure the correct COM port and baud rate are selected in Mission Planner (try 115200 or 921600).
  2. Check if the firmware upload completed successfully without errors.
  3. Verify that MAVLink is properly initialized on the ESP32 side.
  4. Try connecting using a different ground control software like QGroundControl to see if the issue is specific to Mission Planner.
  5. Double-check USB drivers and permissions on Ubuntu.

Also, reviewing the logs you attached should give more insight into where the connection is failing (initialization vs handshake).

Since ESP32 builds are still under development, some features might not be fully stable yet.

Hope this helps!

Which AI you are using?

will this work for a rover?

@geofrancis can you a little more specify your question as this long thread has some different aspects

sorry, what state is this in at the moment, would your breadboard setup work to drive a rover in auto mode? i have replaced just about everything on my solar rover with esp32, so the only thing left is the flight controller.

I had read all about your project.
I didn’t testet my setup in an ardupilot auto mission yet as I used this setup with my own non ardupilut experimental code for an autonoumous rover.
But I am relative optimistic, that it will do the job if it is not a high speed rover. The loop rate on the ESP32 is lower as on the ST based flight controllers.

what do you mean lower? rover by default only runs at 50hz where aircraft run at 400hz.

Oh, I thought it is always 400hz on ST based FCs . Yes, the ESP32 rover firmware runs on 50hz

The only time 50hz has been an issue on rover for me is with high speed lidars and dshot.

I am using only standard PWM output for the ESC and I didn’t tried lidars.
Not sure if Ardupilot FW need a 3 dimensional position for an auto mission. My setup has only the hight information from GPS which is not always the best. No Baro

have you tried switching it to auto to see if it tries to move?

No, I didn’t, but I can reasample the platform back to my test car and check it.
I think I will try this within the next couple of days if this is ok for you

1 Like

@geofrancis
Today I was able to create with my (stationary) rover setup a small logfile.

logfile

1 Like

Hello @geofrancis
did you checked my last logfile?’
This shows that the ESP32 FC tries to turn and speedup in direction to the waypoint if I switch from Manual to Auto.
But there are still some big questionmark regarding running indefinitely.

1 Like