V15.3.3 Sensor Settings

[FSGOM]

During update to this version, Skyview lost some customized sensor settings. After reload the archive seetings it works again:
Example of lost user sensor: Fuel preasure for Rotax engines:
c37_p8={
valid=1
name=FUEL
id=Alex Road P906.B001.0S
alarm_type=OFF
range={
max_display=14.5038
min_display=0
range1_valid=1
range1_top=14.5038
range1_bot=10.8778
range1_name=R1
range1_color=RED
range2_valid=0
range2_top=7.25189
range2_bot=5.07632
range2_name=R2
range2_color=YELLOW
range3_valid=1
range3_top=10.8778
range3_bot=2.17557
range3_name=R3
range3_color=GREEN
range4_valid=0
range4_top=2.90075
range4_bot=2.17557
range4_name=R4
range4_color=YELLOW
range5_valid=1
range5_top=2.17557
range5_bot=0
range5_name=R5
range5_color=RED
}
show_units=1
}

 

[Dynon]

Just a note that if you're using custom engine definitions (ie, a custom .sfg file), you don't want to use our "method 1" update package, but instead use method 2 that lets you grab just the pieces you need - which is everything but the .sfg file. Unlike other configuration files, the .sfg file is loaded wholly and is not aggregated or concatenated. If you have custom sensors, method 1 will overwrite them with the latest revision of the factory definitions.