Back to Board Index
Back to Board Index
Forum help
| Changing Squawk, Changes Frequency in TS3 | |
Richard Coton   1st Aug 2014 20:33:05 | Hello.
Our Server (FSXEU.com) has recently migrated to the Teamspeak 3 FSX link system for comms, and as part of our server, we have an emergency channel for users who declare distress with no ATC online. This frequency is 136.000MHz. It has been reported on our server that many times people have been moved into this channel by the mere presence of loading a save file, a payware plane with comm two switched off, and the title of this thread method, by physically changing the squawk setting, it physically moves the pilot out of a specified frequency channel. This seems highly unusual as the SQUAWK should have NOTHING to do with the frequency changer, yet it seems to demonstrate the ability to do so, and does so frequently. This has also been demonstrated in default FSX aircraft and no root cause has been found by anyone, including our resident mechanic and content creator, Tim Walters. Any ideas what might be causing this? |
| Richard Coton 1st Aug 2014 20:43:02 | Quoted Pattern I Told Tim I found
"It seems as though the squawk setting ignores the '1' in 1xx.xxxMhz and fills the frequency with the squawk value, hence SQK: 3000 = Freq 130.000 SQK: 3600 = Freq 136.000 SQK: 2360 = Freq 123.600 It does seem as though the squawk value changes the frequency to that of the squawk code itself when the systems would be entirely separate. It can be noted I have experienced it on Payware aeroplanes where you must turn COMM2/NAV2/TX on and the default frequency is 136.000 for COMM2, however changing the TX does change the Freq in TS. This clearly should not happen, by a similar observation, many users seem to end up in the Emergency channel when not tuned to it, and I find that in my Payware Piper. So I am not quite sure what the problem is, regardless, here is my report, hopefully this helps clear some mess up." |
| Richard Coton 2nd Aug 2014 11:39:07 | Further note:
Tim Walters changed Emergency channel from Frequency 136.000MHz to 136.500Mhz and this appears to have solved the moving bug to that channel, however with the same load as previous, the switcher now puts me into UNICOMM (122.800MHz) not necessarily a bad switch but it still does seem to auto-switch without a prompt. |
| Richard Coton 2nd Aug 2014 14:01:58 | Further note:
SQK 2603 switched to 130.000 |
Dave Wave  11th Aug 2014 15:42:58 | Richard, I cannot replicate this error with a standard plane.
Please tell me what standard plane you are using and what squawk code you set and what frequency it moves to. |
| Richard Coton 25th Aug 2014 12:25:38 | After Tim Walters changed the channel frequencies to those not ending in .000 the bug seems to have been fixed, but it does seem like those frequencies above do it, I cant seem to replicate it now though.
Members say 737-800, squawking anything 3xxx put in emergency channel 136.000 as above. |
You need to Log on to post a reply. |
Forum help