Hi,

in the vicinity of EDDK Radar uses the frequency 135.350. When tuning in the frequency on stby side, P2A acknowledges it as "LANGE Ctr". When switching this to the active frequency, just "---" is shown then for this frequency. I don't get chatter then, so I assume this is the reason. 

Anything I'm doing wrong here? 

Screenshots: http://imgur.com/a/llcms6J

Best regards,

Rolf

 

The behavior you describe is correct for frequencies that are "out of range".  When on the ground, that distance is much shorter than when airborne.

At EDDK, 118.75 (At the top of the frequency list) is the nearest Center frequency and will work on the ground, but since it is a controlled airport, there is no need to contact Center until after airborne and assigned a Center frequency. 

This ability to contact center on the ground using the top Center frequency is to accommodate uncontrolled airports without telephones for clearance and IFR Release.

 

Thanks a lot for the answer and now I understand much better how this behaves, wow. But I also don't get 135.350 tuned in when e.g. at FL80. In the real world, just 135.350 is used for quite a while already. Is that something to tell Laminar? 

And would it be an intermediate solution to change that apt.dat myself? 

Current departure chart EDDK

 

As a side note, why I am so sticky and just don't want to use 118.75: When flying in the real world, I don't want to realize I trained a wrong habit, tuning to the wrong frequency.

If you want to change the frequency, you need to change it in P2A's  TaxiMnt screen which has an ARTCC tab where all the Center boundaries and frequencies are stored.  

Put EDDK in as the airport to edit, then zoom out on the map, keeping the airport in the middle.  Then you will see the Center boundaries and their names and frequencies.  Find the Langen Radar with 118.75 and change it to 135.35. 

Save the data and restart P2A to get the new data loaded into the main program.

Dave

 

Thank you so much, worked like a charm!