Closed GoogleCodeExporter closed 8 years ago
Thanks for the ideas.
Both packs? I fly 2S, 3S, 4S and 6S aircraft. The Fr-Sky system has only two
analogue inputs and on some versions, one of them is internally tied to the 5V
receiver power supply. That leaves only one remaining (or two at best) analogue
inputs.
What you have requested is certainly feasible -- but not using the Fr-Sky
equipment on its own. It will require a separate telemetry hub, configured with
multiple analogue inputs, which are set up to read LiPo cells individually --
and some kind of standardised data protocol onboard to send the information
back to the transmitter on the user data channel. Then and only then, the
gruvin9x firmware could be written to accommodate all that.
All of this is intended for some time in the future though. We're waiting to
see what comes of the Fr-Sky telemetry hub product and some other stuff before
committing to any particular plan.
Gruvin
Original comment by gru...@gmail.com
on 1 Jul 2011 at 7:36
I think everything asked here will be in my next drop (assuming these voltages
will be A1 and A2)!
Let-me time to test everything carefully before and don't forget the rule in
this FrSky branch ... under the trees for the first flights!
Bertrand.
Original comment by bson...@gmail.com
on 1 Jul 2011 at 9:04
Larger font size view is available from the new main screens telemetry view, by
pressing [RIGHT]. (This is the view that reads "NO DATA" in large font, when no
receiver is switched on and sending telemetry data.)
We're awaiting the return of the graphical bars and work is needed in the model
set-up so that the bar start/end and calibration settings are easier to use and
work better than now. Bertrand -- talk plz to Gruvin about this when you get to
it. Cheers.]
Original comment by gru...@gmail.com
on 26 Jul 2011 at 2:43
The telemetry settings (calibration) screen etc is the way Gruvin wants and
likes it -- but accepted to be lacking features for others. We plan at some
stage to add more "modes", for things like altimeter and air speed.
Meanwhile, we're mostly just waiting for the return of the graphical bars.
No need to burden Bertrand with this one, so I'm taking ownership back. It may
not be done for the end-2011 stable release though.
Original comment by gru...@gmail.com
on 14 Oct 2011 at 7:49
Original comment by bson...@gmail.com
on 14 Oct 2011 at 8:01
This issue seems to be outdated, no longer relevant or otherwise dropped. I'll
close it now.
Original comment by gru...@gmail.com
on 30 Dec 2011 at 2:26
Original issue reported on code.google.com by
flame_ha...@yahoo.com.au
on 1 Jul 2011 at 12:13