SB3 / FSINN transponders

[jcboliveira 1]

Until now the FS transponders were dummy ones, the new clients allow another step in simulation since they allow the transponder to fully operate giving new meaning to transponder mode, ident and ATC indicator. The two clients have different developing interfaces for transponders. SB3 is using a FSUIPC interface; FSInn is using a gauge named var interface. Even with these two interfaces the XML gauges were left out. This small text presents the interfaces and a module that allows combining all these 3 interfaces in one allowing developers to develop in its favorite platform, the ultimate goal is to make developers aware of the online activities and develop with them in mind.Interfaces:FSUIPC based as adopted by SB3Offset 0x7b80, 1 byte, SB3 State, 0 = not running, 1 = running as an external app, 2 = running as a Flight Simulator moduleOffset 0x7b91, 1 byte, Transponder mode, 0 = normal, 1 = standbyOffset 0x7b92 1 byte, ATC activity indicator. This value is normally set to 0. When SquawkBox receives a ping from a nearby ATC, it sets this value to 1. If you want your gauge control to flash your ident light you should check this value periodically. As soon as you notice the value is set to 1, you must reset it to 0. Offset 0x7b93 1 byte, Transponder Ident pressed. When the user presses the ident button on your transponder gauge, you should set this value to 1. When SquawkBox notices it is set to 1, it will transmit an ident on the network and reset the value to 0.BOOL32 named var as adopted by FSInnFSCOPILOT_TRANSPONDER_MODE, BOOL32 named var transponder is client, Transponder mode 0=Standby, 1=Normal, 2=IdentFSCOPILOT_INN_MODE, BOOL32 named var transponder is client, 1=FSInn running, 0=FSinn not runningXML L:VAR859Mode: XML L:VAR, Transponder mode 0=Standby, 1=Normal859ID: XML L:VAR, Transponder ident pressed, 0=Not pressed, 1=Pressed859ATCInd: XML L:VAR, 0=No interrogation from ATC, 1= interrogation from ATC859VFRMode: (optional), XML L:VAR, 0=IFR,1=VFR, The module will put in FS the transponder code indicated in the file sb3gaugebridge.ini at FS root directory under section [Transponder] and indicated by vfr=Note1: The FSInn interface doesn

[Guest Karl R Pettersen]

I have made a few transponders using xml, which doesn't have any link to fsuipc. I have however made it squawk 0000 in the event that the unit is turned off or is set to standby. The displayed squawk will correspond to the assigned squawk only when the unit is in "on" or "alt" mode.Maybe this special squawk 0000 could be interpreted as unit being off or in standby by SB3? Not totally to real life, as at least a visible or invisible status depending on an xml gauge could be possible.