View Full Version : Offset 73BC not reading -1 when ACFT is OFF (but the battery voltage)
juleiin
04-12-2018, 04:50 PM
Hello,
It is written in the offset document that when the aircraft power is off offset 73BC reads -1 but in fact it reads the battery voltage*10..
How come ? And yes there's power somewhere cause the voltage figure appears but then what does "aircraft power is off" mean ?
In fact I'd like my fcu led that display hdg trk fpa v/s (it also works for qnh qfe spd mch) to be only switched on when the fcu is on.
Any help ?
Thanks,
Julien
juleiin
04-22-2018, 12:47 PM
Does anybody have an idea ?
jeehell
04-23-2018, 06:37 AM
actually this feature does not/ will no longer work because in real, the battery voltage displays always show the votlage value, even when ACFT is not powered up.
So I need to find another way to mark the powered up state..
juleiin
05-05-2018, 02:41 PM
Alright! Thanks! Hope you'll find a way so I can start in cold and dark :)
jeehell
05-07-2018, 07:23 AM
look at offset 73AD in next release
juleiin
05-07-2018, 10:49 AM
Alright! Thanks! Did you manage to do something about the "set value for dim/brt/test light" offsets also ?
Merci pour le boulot, c'est top ;)
jeehell
05-07-2018, 11:57 AM
Alright! Thanks! Did you manage to do something about the "set value for dim/brt/test light" offsets also ?
Merci pour le boulot, c'est top ;)
no if you want to use the DIM/BRT function you will have to do that in your own code.
juleiin
05-07-2018, 12:29 PM
Okay so it's not possible to test the light and go back to normal using offset then ? The question is not about having a dim and brt mode, it is just the possibility to get out of the test mode, which can't be done at the moment right (because dim position does not work on the overhead panel) ? For example a two position switch on its on position would set value for test mode (it can actually cf offset) and the other on position of the switch would set value for brt offset (which is missing) ? Because there is the dim light offset but it is not available on the overhead panel (on the GUI), you can only go back to brt.. Do you understand ?
And do you think of adding an offset for 100 or 1000 mode selection for the fcu altitude ? Like if we had a read value at least for this, we could use mobiflight to preconditionned the fact we are changing value by 1000 or 100.
Thanks a lot,
Julien
jeehell
05-07-2018, 04:17 PM
Okay so it's not possible to test the light and go back to normal using offset then ? The question is not about having a dim and brt mode, it is just the possibility to get out of the test mode, which can't be done at the moment right (because dim position does not work on the overhead panel) ? For example a two position switch on its on position would set value for test mode (it can actually cf offset) and the other on position of the switch would set value for brt offset (which is missing) ? Because there is the dim light offset but it is not available on the overhead panel (on the GUI), you can only go back to brt.. Do you understand ?
DIM or BRT will have the same effect... so if you REALLY want to have a 3 positions switch, wire the TEST input to the TEST command, and wire both DIM & BRT to the DIM position. If you want to have actual DIM/BRT difference on your hardware, use a relay...
And do you think of adding an offset for 100 or 1000 mode selection for the fcu altitude ? Like if we had a read value at least for this, we could use mobiflight to preconditionned the fact we are changing value by 1000 or 100.
no. if you want to use FSUIPC offsets, the only proper way to change FCU values is with programming and using the data pipe offsets.
I do not want to make any change to FSUIPC interface, it is way too slow to handle encoder inputs.
juleiin
05-08-2018, 06:03 AM
Hello,
My mistake, you're right dim does the same thing as brt. I was confused by the fact the switch could not get on the dim position on the 2d panel.
I did not really understand how to handle 100/1000 altitude change.
Edit : it's working now using a fsuipc custom offest!
The FCU is now 100% working with mobiflight!! :)
But thank you for your time. Issues get solved one by one and I love it!