Jump to content

Recommended Posts

Posted

So we can edit the AN_ARN128_config.lua file to change the AWLS channels.

 

The format looks like:

 

-- User Modifiable channels (20 channels max)

-- Data explanation sheet. Any value outside valid parameters will invalidate entry.

-- awls_channels[channel_number]["mapID"] = World map where the ILS station is located

-- World Map IDs

-- 1 == Caucasus

-- 2 == Nevada (Not Applicable)

-- 3 == Normandy

-- 4 == Persian Gulf

-- awls_channels[channel_number]["name"] = Airport name (alphanumeric)

-- awls_channels[channel_number]["runway"] = Runway number (alhpanumeric)

-- awls_channels[channel_number]["ils_freq"] = ILS frequency in Mhz. Range 108.0 - 112.0 Mhz

-- awls_channels[channel_number]["tacan_ch"] = Airport TACAN channel (if exists). 0 if the airport does not have a TACAN

-- awls_channels[channel_number]["tacan_xymod"] = Airport TACAN channel mode: 0 == X, 1 == Y.

-- awls_channels[channel_number]["ils_gs"] = ILS glideslope in degrees. Valid values 2.0 to 6.0 in 0.1 increments

-- awls_channels[channel_number]["ils_az_os"] = ILS Azimuth offset from RWY. Value is in feet (integer). Range: +/- 310 feet in 1 feet increment

-- awls_channels[channel_number]["ils_el_os"] = ILS Elevation offset from RWY. Valie is in feet (integer). Range +/1 31 feet in 1 feet increment

 

for example:

 

awls_channels[33] = {}

awls_channels[33]["mapID"] = 4

awls_channels[33]["name"] = "KHASAB"

awls_channels[33]["runway"] = "19"

awls_channels[33]["ils_freq"] = 110.30

awls_channels[33]["tacan_ch"] = 84

awls_channels[33]["tacan_xymod"] = 0

awls_channels[33]["ils_gs"] = 3.0

awls_channels[33]["ils_az_os"] = 0

awls_channels[33]["ils_el_os"] = 0

 

As far as I can tell, only the channels with the mapID relevant to the map in question are loaded in game (i.e., on Persian Gulf you don't see the Caucasus channels, so even though Khasab above is 33 there are only about 12 in total for PG).

 

I was trying to add Syria. Any idea what should I put for line2 (mapID)? Is there a global list of mapIDs (aside for the ones given in the format instructions), or do we need to wait for RAZBAM to add this manually?

 

awls_channels[38] = {}

awls_channels[38]["mapID"] = <---------------------------- What goes here???

awls_channels[38]["name"] = "BEIRUT-RAFIC"

awls_channels[38]["runway"] = "03"

awls_channels[38]["ils_freq"] = 110.70

awls_channels[38]["tacan_ch"] = 0

awls_channels[38]["tacan_xymod"] = 0

awls_channels[38]["ils_gs"] = 3.0

awls_channels[38]["ils_az_os"] = 0

awls_channels[38]["ils_el_os"] = 0

 

 

 

  • 1 year later...
Posted (edited)

Hey Shiroka, sorry to necro this but did you get anywhere? I tried plugging in 5 in the hope that "5 is the Syria MAPID for the TACAN (AN_AR118_config.lua) so maybe it'll work for the AWLS," but no joy. Couldn't spot any clues on various Discords, I've asked in RAZBAM's AV-8B channel, will let you know if / when I get anything back.

 

EDIT 03/06/22: Alpha Juliet on the Discord says he's going to report it upwards, keep them fingers crossed!

Edited by ZuluThreeZero
News
  • 1 month later...
Posted (edited)
On 6/2/2022 at 11:07 PM, ZuluThreeZero said:

Hey Shiroka, sorry to necro this but did you get anywhere? ...

EDIT 03/06/22: Alpha Juliet on the Discord says he's going to report it upwards, keep them fingers crossed!

The AWLS Channels were updated on the 22nd June to support Syria, Mariana Islands and South Atlantic.

There's a lot good with the ability to edit the AWLS fields (via the ODU) to support the Portable TACAN Beacon which can be added to airfields that don't have a "native" TACAN.

Testing in Open Beta, Incirlik RWY 05 AWLS-ILS worked flawlessly (zero wind),

Screen_220731_174731.jpg

... unfortunately Bassel Al-Assad RWY 17R did not, and the AV-8B failed to detect Localiser or Glide Slope (the portable TACAN did work).

Screen_220731_181431.jpg

The A-10C had no such issues when testing the ILS and Portable TACAN on Bassel Al-Assad's RWY 17R final.

Screen_220731_175749.jpg

The AV-8B's behaviour at Bassel Al-Assad is similar to what is seen when testing AWLS in Nevada, so perhaps there might be a clue there to get AWLS working in Nevada ?

Tested DCS Open Beta 2.7.16.28157

Edited by Ramsay
  • Like 1

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

Posted

interesting news that the AWLS works with the mobile TACAN. No we only need a AWLS frequency for Mother and I'm happy.

Posted (edited)
14 hours ago, Kappa said:

Please, explain how to setup a mobile tacan as AWLS

TL;DR:

You can't set a mobile tacan beacon to transmit AWLS-ILS for the Harrier.

You can only use a map's ILS beacons and the frequencies entered into AN_ARN128_config.lua

However you can use the Harrier's ODU to setup the AWLS to use a portable tacan for DME i.e. where an airfield lacks a default TACAN.

Detail:

Here, when landing at Incirlik RWY 05 AWLS-ILS, I haven't programmed AWLS Channel 07 for Bassel Al-Assad's portable tacan that's using 10X, so the kneeboard shows AWLS channel 07 TACAN as blank.

Screen_220731_174731.jpg

In the other screenshot, I've entered the portable TACAN's channel 10X using the AWLS ODU options, and AWLS DME works. TACAN 10X is associated with AWLS Channel 07, Bassel Al-Assad in the kneeboard.

Screen_220731_181431.jpg

Unfortunately the ILS part (localiser/glide slope) - didn't work when I tested Bassel Al-Assad using the Harrier.

Comment

IRL AWLS is a microwave landing system and used with an associated TACAN beacon.

Edited by Ramsay
  • Thanks 1

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...