Peter,
I recently configured my Skyview Touch to take advantage of the increased Landing Gear contacts. If you follow the naming conventions ("GEAR", "GEAR1", "GEAR2", or "GEAR3") and status them correctly "UP" and "DOWN", any combination of "GEAR(x)" that is "UP" when you slow below IAS set speed will trigger the audio response "CHECK GEAR". If any "GEAR(x)" is "DOWN" and IAS is above MAX GEAR SPEED you will get the audio response "GEAR OVERSPEED".
In previous SV versions it only had one "GEAR" contact available for the audio responses. I previously had only the nose gear monitored by naming it "GEAR". The two main gears were named "LMAIN" and "RMAIN". all three were displayed on the screen but only the nose gear was monitored for the audible response. So, the new SV software is an improvement as it monitors all three gear legs in case something causes one to hang.
My only complaint is the naming convention GEAR, GEAR1.... I did prefer my own naming convention "NOSE", "LMAIN", "RMAIN". But if I named these custom, I would loose the Audible response.
Not sure what you can do about an "In Transit" as the gear contacts are binary (up, down). If any/all of the enabled contacts meet the speed threshold, it will drive the appropriate audible response. Any missmatch of the GEAR(x) contacts is a in-transit condition.
Kurt Rutkowski
Glasair Super II -RG
Skyview 10" Touch