[CANNOT REPRODUCE] AA Tacan Y Channel

It seems that the Y Channel for Air to Air Tacan doesn't work right.

If I set the Tacan channel to for example a tanker, in the ME to the Y channel, in game the Tacan responds with the only the X channel selected.

Actual functionality works fine with X, but I should expect it to only work with Y channel. Setting Y channel on the UFC gives nothing.

I second this bug. I've noticed it for a while but never reported it. I always set Tanker to Y channel, but no TACAN info shows unless I switch to X channel even though the freq. is set to Y in the ME.

Third

But only In the Persian Gulf Terrain

Just select X channel and you can see the distance....

In principle it can't happen(while T/R frequences are right,but the codes don't match),so defintely a bug.

I think it’s a sim wide bug. Doesn’t work for Hornet and Hog either.

Sent from my iPhone using Tapatalk Pro

It seems that the Y Channel for Air to Air Tacan doesn't work right.

 

If I set the Tacan channel to for example a tanker, in the ME to the Y channel, in game the Tacan responds with the only the X channel selected.

 

Actual functionality works fine with X, but I should expect it to only work with Y channel. Setting Y channel on the UFC gives nothing.

Same here in current OB 2.5.3.24984

Track file as requested.

tacanXY.trk

Not just a PG issue. Does the same thing in multiplayer in Nevada.

track with 5*Y and 1*X AA stations

For AA tacan:

I don't understand why we must set the UFC X for Y stations for bearing and RANGE,

why only bearing displayed if we set to Y in UFC.

I don't understand why X stations display BEARING only when we set UFC to Y.

tacanXY_discwalker_noscript_6stations.trk

You are welcome for the tracks. You still need more?

The misunderstanding is complete.

Watch the Arco's tacan: Y4 string:"AY4" (A10C replaced with KC135)

Only working when the UFC is set to X4!!

Tested with 2.5.4.26479ob

I hided other VALID AA tacans at mission start.

X11 string "X11" is working on UFC mode X11

What is the purpose of selecting Y chanel in mission editor advanced waypoint actions if only all

working in UFC X mode??

I not complained about multiplayer feature: 63 chanel offset AA tacan distance measuring

2,5,4,26479_AAtacanYnro4_noscript2.trk

No valid A/A TCN bearing was entered. This is also only supported for multiplayer.

Sorry Wags but I don't understand your answer (in context).

Other than that, we also have this problem (sometimes, not always) in our MP missions.

I have a few observations, although they might be slightly off-topic here.

What I noticed is that when I set a tanker to channel 70X (for example), this happens:

- on T/R 70X, there is nothing

- on A/A 70X, I have bearing and range

- on T/R 70Y, I have bearing

- on A/A 70Y, I have bearing

So I get the bearing signal but the range interrogation doesn't work.

I am unsure as to how exactly A/A TACAN works, so the following is speculation, but would explain what I observed.

This is what I have found are the TACAN frequencies (two for each channel, one for interrogation, one for reply).

Manual of Regulations and Procedures for Federal Radio Frequency Management, chapter 4c

Note that for Y channels, 70Y and 7Y, the two same frequencies are used; this is not the case for 70X and 7X.

For A/A TACAN to work, 70X and 7X must use the same two frequencies for interrogation-reply. I assume that in this A/A mode, 70X uses the same frequencies as 7X, namely 1031 and 968. So the TACAN is expecting interrogation on 968 and replying/broadcasting in 1031.

In this case we have the following:

- in T/R 70X we are 1094 (int) and 1157 (reply), so no signal

- in A/A 70X we are 968 (int) and 1031 (reply), so interrogation works and we receive the bearing signal

- in 70 Y we are 1094 (int) and 1031 (reply), so we get the bearing signal but interrogation (and therefore range) doesn't work.

This is the only way I could make logical sense of my observations; assuming it isn't a bug, of course. I must admit I have not tried with setting tankers to Y mode.

My guess this is something Mission Editor related.

In some mission I have Y channel working , in some Y selected but X working.

In some mission I have Y channel working , in some Y selected but X working.

Same here

In our mission it is the same.

1 tanker with TCN 31Y A/A and bearing, the other with TCN 41Y A/A and bearing.

When Y channel selected in the F18, no HUD info and only bearing information is available on the DDI.

When changing it to the X channel in the F18, while tankers are setup as Y, HUD info is displayed and TCN bearing and distance is available on DDI.

Didn't test this with other planes.

Same Problem in one of my missions (where i realized it)

Tanker set to 26Y - Tacan only receives bearing

I didn't test it with X

Y does not provide DME, only X does.

Hi, I want to add to this as I have found that at least on caucasus when you have set a tanker as takan X you only find it in game with Y

Flew a mission to day in the Caucuses (476th ded server) and tanker was supposed to be on 51Y. Only came up on 51X.

Same here. The tanker is set to 44Y, but I have to tune TACAN to 44X, otherwise I only get the bearing and no DME.

We tried it again at the Weekend, it doesn't seem to be a F-18 problem only, the A-10 didn't receive a distance, too. TACAN was set to 26Y.

Set up tanker mission via mission editor last night (before the OpenBeta update to 2.5.4.28090), used default TACAN of 1X and it didn't work--got spinning TACAN in T/R.

Punched in 1Y and it seemed to work fine. Will try with new update to OpenBeta.

I had the same problem when I created a tanker mission in the PG, worked fine with X not with Y