I purchased a Aaris Explorer 280 long range 5" quad a couple of months ago. Shortly after getting it i had issues with front right motor not spinning when armed. I swapped ESC around to a working motor and the motor failed to spin so I concluded it was a bad single motor 30 amp flycolor ESC. A month later it arrives and when I install it, it turns out the original motor for that arm was also defective (I should have checked it at the same time) Another month goes by and the motor i ordered is nowhere to be found and cant even track it. I will never buy from Aaris again. I shop GETFPV now. I had 4 smaller motors from another quad lying around so I swapped just the one bad motor before replacing all 4 just to see if it would spin up. hooked up to Betaflight which I have done many times before and get this message "Non betaflight firmware is NOT supported, except CLI mode"

Does this mean I don't have betaflight in this fc anymore?
Do I need to re-flash?
Is this common when ESC's are swapped?
Does having 1 odd motor contribute to any of this?

Any suggestions would be appreciated more than you know. I'm really about fed up with this thing as it seems to be a money pit with no hope of flying anytime soon in sight. I've got over $500 in FPV equipment just setting on a table and I would really like put it in the air. I'm just way over my head with the electronics. Thank you in advance for any help that can be offered.

Go to CLI mode and type "dump" . Copy everything into a text file. Post the text here. Let's see what is on your FC.

Changing ESC has not bearing on the FC firmware.

Sure sounds weird but as voodoo says, give a dump and the guys here will be able to give you more info. If my googling is correct that quad seems to come with an omnibus F4 flight controller with BF installed and none of that should be ruined by an esc and motor going wonky. I guess freak voltage spikes can do strange things but for it to mess upp BF... We shall see what the dump says

Whyt didn't yoiu return the whole drone as soon as you found out that a motor wasn't spinning? And yeah Arris...... I wouldn't put too much faith in their product. You should have gotten a full refund as soon as you saw the motor didn't work. The implication is that the drone was new at this time right? You definitely should've returned it.

(03-Jun-2021, 07:23 AM)voodoo614 Wrote: Go to CLI mode and type "dump" . Copy everything into a text file. Post the text here. Let's see what is on your FC.

here is the file dump in the google keep file. Thanks for taking a look at it

You have iNav flashed. You can easily flash back to Betaflight using the firmware flasher in Betaflight configurator. Make sure you have the correct target selected. If you aren't sure, take clear pictures of everything and post them here.

If you intend to just do long range cruising iNav has better GPS functionality than Betaflight. You'll just need iNav configurator to configure it.

(08-Jun-2021, 01:36 AM)V-22 Wrote: You have iNav flashed. You can easily flash back to Betaflight using the firmware flasher in Betaflight configurator. Make sure you have the correct target selected. If you aren't sure, take clear pictures of everything and post them here.

If you intend to just do long range cruising iNav has better GPS functionality than Betaflight. You'll just need iNav configurator to configure it.

Wow! I cant believe I wasted your time with that one. I completely forgot it came with iNav flashed bc it is set up for long range flight. Sorry about that and thanks for the response. My other quad is a tinyhawk 2 freestyle. After a small crash into a bush this started. When i connect the battery it will beep 3 times (which i believe means no communication between rx and fc) It gives 5 blue flashes, 4 green flashes, and 1 red flash. it will repeat this 3 times and then no lights or sounds. When i connect it to Betaflight it will not connect. It just acts like nothing is plugged up. Any thoughts?

(04-Jun-2021, 09:19 AM)bLoWsMokE Wrote: Whyt didn't yoiu return the whole drone as soon as you found out that a motor wasn't spinning? And yeah Arris...... I wouldn't put too much faith in their product. You should have gotten a full refund as soon as you saw the motor didn't work. The implication is that the drone was new at this time right? You definitely should've returned it.

Ok maybe I left out the part about crashing it. It worked until a crash occurred