issues with my M5 Atom Fly and Joy
-
I'm having several issues with my M5 Atom Fly and Joy.
Specifically, I'm having trouble selecting flight modes (Sport, Stable) and altitude (Auto, Manual) using the R and L buttons. These controls are very unreliable, and I can't figure out why they sometimes work and other times don't.
Furthermore, as soon as I turn on the drone and controller, and try to take off in Stable/Auto mode, the drone rises very little off the ground and starts moving backwards, ignoring my commands. It continues to fly backwards until it hits something and stops. After several attempts, sometimes the drone finally starts responding to commands, but by then the battery is almost empty and I have to stop flying.
Has anyone ever had similar problems? What could be causing this abnormal behavior? Thanks in advance for any suggestions.I've tried updating the firmware on both the joy and fly using m5 burner, but it hasn't fixed the problems
best regards
-
@cepics I've recently been experiencing this exact behavior. From all the debugging I've done, I've determined it has to be the controller. I've tried all the firmwares I can find for the AtomS3, but it seems to be working. It's just that it can't communicate with the controller itself.
Serial output shows i2c device discover all over the place. This is driving me crazy. The drone is unusable until I get this fixed.
Scanning... Wire1 No I2C devices found Version 1 E (287) esp_core_dump_flash: No core dump partition found! M5AtomS3 initializing...OK 3,CC,8D,A2,21,A6,F8 ESPNow Init Success Scanning... Wire1 I2C device found at address 0x78 ! I2C device found at address 0x7C ! done Version 1 E (287) esp_core_dump_flash: No core dump partition found! M5AtomS3 initializing...OK 3,CC,8D,A2,21,A6,F8 ESPNow Init Success Scanning... Wire1 No I2C devices found Version 1 E (287) esp_core_dump_flash: No core dump partition found! M5AtomS3 initializing...OK 3,CC,8D,A2,21,A6,F8 ESPNow Init Success Scanning... Wire1 I2C device found at address 0x6E ! done Version 1 E (287) esp_core_dump_flash: No core dump partition found! M5AtomS3 initializing...OK 3,CC,8D,A2,21,A6,F8 ESPNow Init Success Scanning... Wire1 I2C device found at address 0x4E ! I2C device found at address 0x4F ! I2C device found at address 0x51 ! I2C device found at address 0x55 ! I2C device found at address 0x57 ! I2C device found at address 0x58 ! I2C device found at address 0x5B ! I2C device found at address 0x5C ! I2C device found at address 0x5D ! I2C device found at address 0x61 ! I2C device found at address 0x62 ! I2C device found at address 0x66 ! I2C device found at address 0x6C ! I2C device found at address 0x6D ! I2C device found at address 0x6F ! done Version 1 E (287) esp_core_dump_flash: No core dump partition found! M5AtomS3 initializing...OK 3,CC,8D,A2,21,A6,F8 ESPNow Init Success Scanning... Wire1 I2C device found at address 0x6F ! I2C device found at address 0x71 ! I2C device found at address 0x72 ! I2C device found at address 0x74 ! I2C device found at address 0x75 ! I2C device found at address 0x78 ! I2C device found at address 0x7A ! I2C device found at address 0x7E ! done Version 1 E (287) esp_core_dump_flash: No core dump partition found! M5AtomS3 initializing...OK 3,CC,8D,A2,21,A6,F8 ESPNow Init Success Scanning... Wire1 I2C device found at address 0x19 ! done Version 1 -
@AreaKode While I'm waiting for new batteries and a battery charger, I'm charging the batteries by inserting them into the two slots of the joypad and connecting the joypad's USB-C port to a USB charger. When the two LEDs are green, I've noticed that as soon as I install the charged batteries, I get readings of over 65V on the joypad... after a few takeoff attempts, the value drops to around 4V and the system starts working as it should
-
@cepics My batteries always read 65.5V regardless of their charge status. I'm glad you're getting at least partial control. My controller seems entirely unresponsive other than the S3's button.
-
@cepics Figured it out. If I press really hard on the Atom toward the top of the controller, suddenly everything works. I have to keep a lot of pressure on it, thus the clamp. Looks ridiculous, but now everything works 100%. Super annoying, and I might contact support to see if they have any permanent suggestions since, I just got this in the mail a week ago, but I have a potential solution for you.
