FDS Transponder with Squawkbox - won't leave STBY Mode

[sagrada737]

I'm using the new FDS Transponder/TCAS unit.

When I am logged into VATSIM, the Controllers only see the Transponder in Standby Mode (SYBY), eventhough the switch on the FDS transponder is set to either Auto or ON.  The TCAS switch is set to TA/RA.

Regardless what I do in Squawkbox, I can't seem to get it to go into "Squawk Mode C".  I click the box, but it does not change to Mode C - it just stays in STBY Mode.

Is anyone using a similar setup that could offer some help?  Thanks.

Mike

[sagrada737]

Follow up question:  Is anyone using FSUIPC Offsets to get around this issue in Squawkbox?

Mike

[jackpilot]

Mike

The appropriate way to deal with that issue is to talk first to FDS.

[Trevor Hale]

Hi Mike, 

I think what Jack was meaning to say was "Have you talked to FDS about your issue yet"  And if not, we can try to help you but if there is an issue with the Transponder you may want to ask them first.

I am guessing this is possibly something they can resolve warranty wise.

Please post your resolution back here after you talk to FDS, I am interested to know how you make out.

Trev

[Jetcos]

This is where we seem to run into problems.

Telephone message left at FDS
Email sent to me
Post in CB Forum

So where should I reply?


I sent the info to Mike, as soon as I was available.

This is a simple software setup and NOT a Warranty issue. The Transponder works as advertised and needs a specific xml to work with Sim-A to communicate with SquawkBox and to use Sim-Connect to also use the switches that are programmed to work.

***This does not apply to FS9, only FSX and Prepar3d***

[Trevor Hale]

Great Information Steve.

Thanks for posting the resolution here.

Trev

[sagrada737]

Hi Guys,

I think that there is a misunderstanding concerning my post on this thread.   As far as I know, I do not have a problem with my new FDS Transponder/TCAS unit.  It is a nice piece of engineering and it does seem to communicate correctly with FSX.

My question for the forum has to do with the total connectivity of the transponder (in my case the FDS transponder) using Squawkbox within the VATSIM environment.  I simply wanted to know if others had a similar setup and any constructive comments to aid me in getting a valid Mode C to show up in VATSIM.  That's all...

I have been in contact with FDS on all kinds of issues, including this one.  But that should not negate my asking questions on this forum as to other user's experiences concerning interfacing transponders with Squawkbox and VATSIM. 

Also, as far as I'm concerned, there is nothing wrong with my FDS transponder.  I am simply trying to establish connectivity with VATSIM using Squawkbox in FSX.  My problem is that the transponder status within Squawkbox shows "stuck" in the STBY mode.

I'm still interested in how others have gotten their transponders to work with Squawkbox within VATSIM.  Constructive comments are appreciated.

That said, Steve at FDS was kind to respond separately to a direct request for information on interfacing the FDS Transponder/TCAS unit.  The information he sent may be helpful concerning this issue.  I plan on giving it a try later today.

Mike

[blueskydriver]

Hi Mike,

Are you using the correct FSUIPC settings, as well as setting SB4 beforehand? FSUIPC has some unique settings for SB4, but you must make sure SB4 is setup within the program first; otherwise, the offsets will be problematic.

Also, once you have to pop-window onscreen, do you see which mode you're in at that point? Currently, I just go into SB4 window program and set the transponder to the correct mode (mode C), as VATSIM ATC guys and rules say to be in mode C right after you login...

John

[Trevor Hale]

Hey John, Great advice.  But! at busy airports Like we will have at Worldflight, you likely won't Mode C until you are on the runway.  things get way to confusing for the controllers.

[sagrada737]

Thanks for the constructive comments John. 

I understand that when I "Connect" on Squawkbox, that I can set the Transponder mode.  In my case, it is unresponsive.  Perhaps it does have something to do with an FSUIPC setting.  I'm still working with Steve on this one, so until I close the loop with him, I'm in a holding pattern.

Trevor - Good comment on VTSIM requirements.  They are friendly folks, but they do have a Code of Conduct for their operations, which everyone is suppose to follow.  That said, the Controllers are understanding with folks new to VATSIM, and they go out of their way to help.

Mike

[Bob Reed]

Hi Mike,

Are you using the correct FSUIPC settings, as well as setting SB4 beforehand? FSUIPC has some unique settings for SB4, but you must make sure SB4 is setup within the program first; otherwise, the offsets will be problematic.

Also, once you have to pop-window onscreen, do you see which mode you're in at that point? Currently, I just go into SB4 window program and set the transponder to the correct mode (mode C), as VATSIM ATC guys and rules say to be in mode C right after you login...

John

I will have to look into this. I know when I was flying Vatsim several years ago you did not go mode "C" until on the active. Quick look at how to log in should clear this up.

[Trevor Hale]

Thats correct Bob,  Not until "Position", Otherwise the controllers get cranky.

[blueskydriver]

Hey Guys,

I agree about World Flight because of all the people being logged. However, the rules changed and they want you mode C before moving from the gate because it shows them where you are no matter who the controller is.

Additionally, it helps them determine if you're setting idle for too long. If so, they'll boot you for inactive usage. Here is the link of the Code of Conduct...look at section B, item 4.

http://www.vatsim.net/network/docs/coc/

When they mean inital contact, it doesn't matter who or what position you call first, you must be mode C before doing so. And, believe me, I always fly VatSim for every flight I make, and they do tell you mode C if you're not already...as soon as you call in.

John

[Trevor Hale]

Interesting info John,  Thanks for that.

Perhaps their new software better handles on the ground aircraft.  Thanks a bunch.

Mike your right, sorry for Hijacking your thread.