Setting GBU Laser Codes below 1511 on the Ground

[Darkdiz]

When going to the F8 (Groundcrew) / F8 GBU Laser Codes menu to have the groundcrew change your laser codes to something other than default, the second digit only goes to 5, it SHOULD go to 1 to allow anything below 1511, all of which are available in the mission editor. In the manual, it clearly states valid laser codes are 1111 to 1788, but anything below 1511 cannot be set.

Is this by design, or something that needs to be looked at?

[Vakarian]

From what I've seen, that's realistic. Bombs we have in DCS can use laser codes that have following scheme:

1. 1
2. 5-7
3. 1-8
4. 1-8

So from 1511 - 1788 can be set, those are the limits and that's how it should be. Linking F-16 subforum, but you can see there the diagram of what codes are actually settable on the bomb itself.

 

[Ramsay]

7 hours ago, Darkdiz said:

Is this by design, or something that needs to be looked at?

This is by design, the bombs have physical dials set by the ground crew i.e. the 2nd digit can't be set less than "5"

https://forum.dcs.world/topic/244040-gbu-laser-codes-since-update/?do=findComment&comment=4405162

 

Edited January 15, 2024 by Ramsay

[Darkdiz]

Ok, so the bombs cant be set by the ground crew to anything under 1511. Why then, as it clearly states in the manual (for the F15E anyway) that valid laser codes are 1111 to 1788. I can also set 1111 (for example) in the mission editor, it shows correctly on the kneeboard, and for the GBU54, I can set 1111 on the smart weapons page. It seems there is a disconnect here, it SHOULD be available on the bomb itself, especially if I can set in in the ME, and through the smart weapons SENSOR page.

My buddy tested 1111 on the A-10, he reported it worked fine.

[Darkdiz]

Just tested a GBU24 with 1111 set via the ME. Worked fine. Tested GBU54 set with 111 on the sm wpn page, worked fine (default was 1688, which is what came up on the sm wpn sensor page initially). I think there is a disconnect here, if it works in ME, it SHOULD be available via the ground crew, as IRL, they would be the ones physically changing the bomb's physical code.

[Ramsay]

2 minutes ago, Darkdiz said:

I think there is a disconnect here,

Agreed.

3 minutes ago, Darkdiz said:

if it works in ME, it SHOULD be available via the ground crew,

NO, the mission editor allows invalid laser codes, this is not a reason NOT model a RL physical limitation.

8 minutes ago, Darkdiz said:

IRL, they would be the ones physically changing the bomb's physical code.

IRL GBU-10, GBU-12, GBU-16, etc. cannot be set to 1111, etc.

GBU-58 may differ as it has an umbilical connection to the aircraft and it's code can be changed whilst in flight.

The "allowable" operational laser codes are decided on by joint "standards" committees to prevent conflicts between different services/users, hence why certain weapons/designators have a limited range of settings.

So the GBU-58 in practice, may be limited to the same range of codes as the GBU-12, etc series.

[Darkdiz]

Interesting that the GBU24 worked with 1111 set in the 15 via the ME, as well as the 54. I purposely set the 54 to something other than 1111 in the ME, and changed it in flight to 1111, launched it to an "area" then terminally guided it to a point near the original coords

[Tholozor]

The guidance control unit code select panel on GBU-24 should permit the first digit being 1 or 2 (the second basically never used), and the three remaining digits can be 1-8, so 1111 is a valid code for Paveway III, but not Paveway II.

Edited January 24, 2024 by Tholozor