Closed becas22 closed 4 years ago
This is most likelly a configuration issue.
Update the settings file src/settings.py#L46 clr_freq
and dep_freq
options for all airports affected.
There are two different classses of frequencies considered:
Configurable per airport, in the settings file, using the entries:
clr_freq
dep_freq
respectively.
The behaviour is to show the frequency for each classification when that frequency does not match the information on the charts (there are some exceptions made for the VATSIM reality). This is the behaviour of the real ATIS, as far as I recall.
The implementation, however, is very straight forward. The first frequency from a list that is online is shown (works the same for clearance and departure frequencies). It is a matter of having the correct frequencies in the correct order.
As an example, the current list of clearance frequencies for Lisboa can be found in src/settings.py#L46
'clr_freq': (
('118.950', '[FOR DEP CLEARANCE CONTACT DEL 118.950]'),
('121.750', '[FOR DEP CLEARANCE CONTACT GND 121.750]'),
('118.100', '[FOR DEP CLEARANCE CONTACT TWR 118.100]'),
('119.100', '[ON THE GROUND CONTACT APP 119.1]'),
('125.550', '[ON THE GROUND CONTACT 125.55]'),
)
_Note. All messages that mention the position (DEL, GND, TWR, etc) are so because they are in the real ATIS. Messages that do not mention the position are not in real ATIS (125.55 is never the departure frequency, but can be on VATSIM)._
closed in b3f6258d16c8fc21942a0a7ea742e8f9f2d00609
ATIS instructs to contact 125.55, even if you have a sector split (LPPC_N_CTR) Frequencies: https://docs.google.com/spreadsheets/d/1xxHEd4dX4Yuwrhm48uebc-K-AVtkA7jFautui4jLw-A/edit#gid=0