[Wendingo]

Has anyone ever had an issue with cleanflight not maintaining settings? I have a taranis transmitter, X8R receiver, and a NAZE 32. I can't get Cleanflight to accept inputs from the taranis, and I am pretty sure the reason is that everytime I start up cleanflight I notice that the RX_SERIAL option I enabled the previous time I used cleanflight has disappeared.

[uberjay]

yeah, that would be a problem if your settings are getting nuked. Sounds odd though... the Naze shouldn't do that. You don't have a short on the board anywhere or have the board's bottom directly sitting on a carbon frame or anything?? Also, you don't have the boot pads shorted right?

I believe all the settings once you connect are pulled from the Naze board itself. So it would appear that the board is not retaining its programming. That makes me question whether the boot pads have been shorted / jumpered - which is how one does a factory reset. So in effect each power cycle it starts from scratch.

Just brainstorming.... I may be way off.

Cheers,
J

[Wendingo]

Originally Posted by uberjay

yeah, that would be a problem if your settings are getting nuked. Sounds odd though... the Naze shouldn't do that. You don't have a short on the board anywhere or have the board's bottom directly sitting on a carbon frame or anything?? Also, you don't have the boot pads shorted right?

I believe all the settings once you connect are pulled from the Naze board itself. So it would appear that the board is not retaining its programming. That makes me question whether the boot pads have been shorted / jumpered - which is how one does a factory reset. So in effect each power cycle it starts from scratch.

Just brainstorming.... I may be way off.

Cheers,
J

I really appreciate the brainstorming. I really really do, but I found the issue. A poorly documented requirement of running S.BUS on a NAZE32 is that you have to open up a software port.

[uberjay]

Originally Posted by Wendingo

I really appreciate the brainstorming. I really really do, but I found the issue. A poorly documented requirement of running S.BUS on a NAZE32 is that you have to open up a software port.

No worries... glad you got it figured out. Of course, now that you mention it I remember having to do that step too . Just don't remember the saving issue... probably was following someone else's instructions at the time and got it right (lucked out) the first time .

Cheers,
J