highlandfpv
New Member
Hi guys, new to the forum and relatively new to the hobby. briefly had a DJI FPV quad last Christmas and quickly sent back and got a iFlight Nazgul5 Evoque which I racked up around 5hrs on before 6 months later losing up a mountain.
Recent release of DJI Avata has me curious again and bought a 2nd hand green hornet which had a DJI air unit preinstalled but uses crossfire for rx. Disconnected the crossfire and hooked up the SBUS and ground terminals onto the air unit before connecting to betaflight and this is where it started to go wrong.
Changed UART2 to UART1 for rx and selected SBUS in the receiver tab.
betaflight had the quad doing backflips in the receiver tab, I figured there was something wrong with one of the settings so thought rather than hunting through all the settings it would be easier to start fresh. I was clever enough to backup the firmware onto my desktop before selecting update using the autofind button. The firmware it found was betaflight 4 which I thought was odd as I expected it to be the name of the FC as it was with my Nazgul.
Anyway, new firmware has no motor output protocol selected and I have no idea which one I should pick. I tried to reload the old firmware but the betaflight firmware loader doesn't seem to recognise it.
Any help would be much appreciated, sorry for the big shpeel.
Recent release of DJI Avata has me curious again and bought a 2nd hand green hornet which had a DJI air unit preinstalled but uses crossfire for rx. Disconnected the crossfire and hooked up the SBUS and ground terminals onto the air unit before connecting to betaflight and this is where it started to go wrong.
Changed UART2 to UART1 for rx and selected SBUS in the receiver tab.
betaflight had the quad doing backflips in the receiver tab, I figured there was something wrong with one of the settings so thought rather than hunting through all the settings it would be easier to start fresh. I was clever enough to backup the firmware onto my desktop before selecting update using the autofind button. The firmware it found was betaflight 4 which I thought was odd as I expected it to be the name of the FC as it was with my Nazgul.
Anyway, new firmware has no motor output protocol selected and I have no idea which one I should pick. I tried to reload the old firmware but the betaflight firmware loader doesn't seem to recognise it.
Any help would be much appreciated, sorry for the big shpeel.