After waiting for weeks for my new Taranis B01 (Mode 2) I finally got it a few days ago. I currently have an LRP UpStream 1400 (Bixler clone) equipped with an X6R, FLVSS, GPS and Vario; the usual thing - first fly a testship.
Today I have had a strange thing happen to me for the second time...
When I started, Logical switch 1 was configured as "(S1 > 80) AND SF up".
During the flight it reconfigured itself to "(S1 > 80) AND !SA up"
I noticed the difference only during landing preparation when the motor didn't behave like it should. I happen to have *.eepes before and after, so I am not halucinating.
As mentioned this has happened to me before (the exact same thing) but at the time that was my first flight and I attributed it to my fault during programming. I do not recall which exact version that was but I think it was 2.0.10 WITH compiler trouble, which had its own problems...
My model configuration can be seen in the attached *.eepes (the version with _AF was read from the radio after the flight, the other one is the one the went into the radio yesterday evening. The model in question is model 1). My current version is Bootlaoder 2.0.12 and OpenTx 2.0.12 / 2014-09-16 / 23:30:05 / EEPR: 216; Options ppmus and lua. Never mind the difference in trainer setup - that was wanted.
I am using the example telemetry screens from the homepage with this model. The flight was logged, with 2.0.10 I once had the "SD-Card error" happen to me. This flight was (other than L1) calm with nothing special to remark.
Obviously I don't appreciate this happening in flight... luckily I understood the new configuration for L1 and was able to safely land nonetheless.
So the questions to the experts:
- Is this a bug in OpenTX?
- Am I missing something?
- Or do I have a broken radio (defective RAM maybe)?
- Is there a hardware test firmware I could use to test the radio?
P.S.: I don't think it matters, as this happened in the radio, but I am using Companion 2.0.12 on Win7 32 bit.