I did have a look at the protocol coming out of the arduino.
The protocol is very timing sensitive, the TX sends a request, the module (arduino) must answer after 5ms in a 2ms window. Every byte must have a 2ms delay between them and that 45x and all that within 200ms.
Ok, it seems I'm on the limit with the arduino and led, in my case it is working but clearly not everywhere.
I have find a way to shorten the processing time.
Btw, I never heard that v083 is working and v095 not. That is really the first or could it be that the user is using a low autoquad fw?
Now for the sequence between transmitter and module.
Graupner made the (stupid) decision that a transmitter will automatically request all available sensors. That sounds great but the implementation is just silly. The transmitter will only request all sensors for 8 seconds and that's it, after that no more.
So, basically (IMHO) it violates the flight readiness I learned: switch on the Tx and than the rest.
Now the rest must be in that 8 seconds. The AQ need some boot time, the arduino etc so it can be to short.
Solution is to switch on the AQ+ mav2hott and then the tx or power cycle the tx
.
Every 3rd party implementation has this 'problem' and there is nothing I can do about that. You can always revert to a graupner firmware before April 2013
.
Even with graupners own modules this is silly, if you not power your plane within 8 secs you will not have telemetry. I will NEVER power cycle a tx with a hot plane or heli...
Hope they will revert this procedure in the future.