#Vision40 Issues

1 messages · Page 1 of 1 (latest)

coarse tangle
#

I'm so embarrassed about this post. Newbies gotta be new I guess. I have exhausted the internet and need to bring in the professionals.

While I was able to fly my drone a few times, I got a firmware mismatch warning and attempted to update everything and I think I botched everything up in the process. I ended up rolling back my Vision40 drone firmware to manufacture spec (v4.4.3) but can no longer ARM the drone using my TX16s radio or connect to my WalkSnail Avatar X goggles (v38.43.8).

Arming Errors in Betaflight

  • MOTOR_PROTOCAL (No motor output protocol selected): I've tried DSHOT150, 300 and 600. Regardless of what is selected - same error.
  • THROTTLE MSP (Throttle channel is too high): Betaflight setting is 1050/1500/1900. RM TX16s low is 988 (100/-100).

What works:

  • Betaflight>Motors: I am able to spin up motors using test mode.
  • Betaflight>Receiver>Preview: bars move in as expected with radio.
  • Betaflight>Modes has Arm and operates as expected.Betaflight>Motors>DSHOT300 selected (also tried 150 & 600).

I suspect this is all a firmware mismatch situation but I'm unsure how to proceed. Can you kindly provide me with any advice you have to get up and running again? For example, should I roll back my AvatarX firmware? If so, what version?

Thank you for your help!

DroneSlides_3.png DroneSlides_2.png DroneSlides_4.png DroneSlides_5.png DroneSlides_1.png
odd palm
#

Firstly, separate the Video System from the drone's firmware in your mind. They are separate entities with different jobs and firmwares.

#

Once that's done, we can sort the drone's firmware out. That can be a lot more involved, depending on exactly what you know, and what you've done to it. 💛

#

Rotor riot don't appear to have made the "tune" (a cli dump, or preset) available to download anywhere, which is... Deeply unhelpful.

I hope you made a backup of the drone's firmware in it's "stock" configuration.

coarse tangle
#

OMG, thank you for responding!! I got the factory CLI dump from RotorRiot and got it on the Vision40. Good news, is that I am able to arm the drone and spin the motors. The issue I have now is that my goggles will not pair with the drone. According to RR, the drone shipped with firmware 38.43.4. My Avatar goggles are currently on firmware 38.43.8. In ExpressLRS Configurator, it says my Vision40 firmware is "ver.unknown (486c9c) ISM2G4". I was also unsuccessful in downloading my goggles back to 38.43.4. I appreciate any guidance you have!

odd palm
#

That will trick it into thinking it's an upgrade in version and install it over the newer version.

odd palm