I pose my concern in English to have at least 1 feedback....
on my 320 cockpit I systematically have the RAM AIR ON message written since a few updates (maybe no connection).
the korry light never comes on but I manage to turn off the message by pressing the button twice (2 stable states and latch activated on sioc creator). I redid the programming under sioc creator and it is not conclusive or even strange.
At home I have 2 PCs and test the update before doing it on the cockpit... I am starting from a blank config with an empty jeehellware.txt and no backup.
if I want to program a korry, the RAM AIR in the LOWER OVHD tab, apply, Apply configuration (compil sioc), and save config....
the result is always the same: no consideration of ram air in the files JeeHellWare.txt, FMGSServer.iocp.ini.
Applylog txt ok:
I tested with BATT1 and it works.Starting process
Compiler path: F:\SIOC\sioc_compiler.Exe
sioc_compiler.Exe exists
CreateIOCKeysINI OK
sioc.ini exists
FMGSServer.iocp.ini initialized
JeeHellWare.txt initialized
MCDU not enabled
FO MCDU not enabled
XPDR not enabled
ACP not enabled
RMP not enabled
FCU not enabled
EFIS not enabled
Low OVHD enabled
low OVHD OK
Upper OVHD not enabled
MISC not enabled
Finished writing
compiling...
compiling OK
I'm dry, I must be doing something wrong.... and don't understand, and would be happy to have some info like, yes we know you're not the only one or it will be ok soon.
See you soon on this topic.
Gilles