RMP and 8.33 khz spacing

[dkreiskott]

Hi JL,

I don't know if I found a problem with the RMP.
Since P3Dv5 the 8.33 khz spacing for the frequencies is supported.

I have now adjusted some addon airports based on the Navigraph charts for the frequencies. Thereby the following problem occurred.
EDDL Ground has the frequency 121.600. This was changed to 121.605. So I have also stored 121.605 for Ground in the AFCAD.

I can turn in this frequency at the Skalarki RMP, however, this is not recognized in the simulator.

I use an additional ATC tool (Voxatc) which supports 8.33khz. So I am asked to turn in the frequency 121.605 for Dusseldorf Ground. But even if I do this, the ATC software does not react, because this frequency cannot be recognized.

As it looks to me, the 8.33 khz spacing is not supported here.

[bbruechmann]

Dieter, there is an option to be set in the Aircraft options of the FMGSServer. Called "VHF radio spacing"

[dkreiskott]

Hi Bernd,

thanks for your tip.
But it is set to 8.33 khz. I think, this setting doesn't work.

I have tested with the ATC Windows from P3d.
If I select the line for "EDDL Ground 121.605" in P3D then my ATC programm act with this Frequency, but not with the RMP.

[dkreiskott]

I don't know if it helps. But since FSUIPC v6 there ar new Offsets for frequencys in 8.33 khz space

05C4 Active COM1 frequency in Hz (32 bit int)
05C8 Active COM2 frequency in Hz (32 bit int)
05CC Standby active COM1 frequency in Hz (32 bit int)
05D0 Standby COM2 frequency in Hz (32 bit int)

The old Offsets befor are in 4 digit BCD format.

[dkreiskott]

Hi Jean Luc,

today I do some test with frequencies on EDDL.
I change the ground frequencies from 121.600 to .605, .610, .615, .625, .630, .635
Only .600 and .625 are working. I think the rest is in 25 khz steps too.
The FMGS Server option is set to 8.33 khz.
I have tested with the software panel too, same behavier. It is not a hardware problem from skalarki RMP.
See the previous post from me, I think this is the problem.
An answer from you is appreciated.

[jeehell]

It's been a long since I last used FSUIPC to set anything in the sim...
I have no idea why it would not work. I will make some tests one day, but this is not really top priority.

[dkreiskott]

Hi JL,

thanks for your answer.
How do you read or set the frequencies from/to the simulator?
If I can help, let me know.

[bbruechmann]

JL, in the installation guide of FMGS it´s mentioned

 Master FSX/P3D PC,
 FMGS Server and AP/FBW,
 Sounds module,
 Intercom,
 FSUIPC support,
 Other hardware support (CPFlight, FDS, Skalarki, CockpitSonic, OpenCockpits,…).
This will be the core of the FMGS system.

But if you don´t use FSUIPC would that mean this is all done via simconnect? And why is FSUIPC part of the core?

[dkreiskott]

Hi Bernd,

I think JL uses the FSUIPC offsets. Since other programs react to the frequencies turned in, this must actually be passed on to the simulator via FSUIPC.
And exactly there is the problem of the new offsets for the 6 digit frequencies. I suspect that JL still fills the old 16 bit BCD offsets.
So you can see the 8.33 khz values on the RMP, but the simulator doesn't get them.
For me a big problem, since the Airports AFCAD are updated.

[dkreiskott]

]Today I read the offsets from FSUIPC. Obviously the active frequency is not always filled or read correctly.
The standby frequency is not used at all in 32 bits.
I took two screenshots of the RMP and the offsets.

rmp2.PNG[/attachment [attachment=1]rmp.PNG

[Buford]

I tested it with P3Dv5.3/vPilot for online flying with VATSIM. It does not really work. I can tune to the correct frequencies with my Skalarki RMP, but the third decimal digit is transmitted to vPilot as "0", regardeless what is tuned. For example:
118.005 is transmitted as 118.000
118.010 is transmitted as 118.010
118.015 is transmitted as 118.010
118.030 is transmitted as 118.030
118.035 is transmitted as 118.030
118.040 is transmitted as 118.040
and so on.
I think that matches with Dieter´s supposition that JeeHell uses the old 16 bit offset only while the 32bit offset would be needed to transmit the third decimal.
VATSIM Germany, Dutch VACC and VAT UK, thus Germany, the Netherlands and the UK will begin to use the 8.33 kHz scheme in a 3 month test phase from September this year, one can expect that whole VATSIM will do the same in near future. So there really will be a need to find a solution to be able to fly online furtheron. World Flight Team JeeHell will already have a problem with that, as World Flight 2023 will take place in the beginning of November, thus in the test phase, and three flights will lead through the affected airspaces.

[dkreiskott]

But I'm glad I'm not the only one having this problem.
I have a Navigraph subscription and cannot use the frequencies on the current charts. If VATSIM and others change over now, that will be a bigger problem.
I think that Jean Luc should react much faster to this. Especially since we can already define quite clearly where the problem lies. Adjusting the offsets for the frequencies can't be such a big programming effort now. The basic function is already there. And the server has the option of switching to 8.33 khz. Then the correct values must also be passed.
At least that's my humble opinion, although I really appreciate Jean Luc's work.

[smagnut]

This would be painful - no more beeing able to fly and communicate on VATSIM.
Lets hope that this is an easy and quick fix.

Thanks to Jean Luc for this brilliant piece of free software!

Best regards
Micha

[jeehell]

there will be a fix, and no it's not because of FSUIPC, I do not use it except for hardware inputs...

[Capt. PERO]

there will be a fix, and no it's not because of FSUIPC, I do not use it except for hardware inputs...

Thanks Jean-Luc!

[Buford]

there will be a fix, and no it's not because of FSUIPC, I do not use it except for hardware inputs...

THX a lot!

[smagnut]

there will be a fix, and no it's not because of FSUIPC, I do not use it except for hardware inputs...

Great, many thanks!

Best regards
Micha

[dkreiskott]

Hi all,

I would like to add something to the problem, because I noticed it in the last few days.

In Cologne the current ATIS frequency is 112.150
In Krakow it is 112.800
In Manchester it is 113.550

To give three examples. However, it is not possible to turn in frequencies below 118.000 in the RMP at all.
I assume that we have a problem in the Jeehell software as well as with the RMP of Skalarki.

It would be great if one of you with Skalarki hardware could check this.

[jeehell]

This is getting tiring. the ATIS frequencies you mention are in VOR range. To hear them in real life, you'd tune your VOR receiver to that frequency and use the VOR ID channel to listen to it. And for Koln at least there is a second ATIS freq 132.130.

[dkreiskott]

Hi JL,

yes, I have set the freq of Cologne to 132.130 in the AFCAD.
I understand your comment for VOR, but why are the Navigraph Charts give us frequencies in this space for other Airports?
Is this an error from Navigraph or are these frequencies really so now?
I'm confused.

[jeehell]

Because navigraph charts are real charts (Jeppesen's) so they have the real frequencies?

[Capt. PERO]

VATSIM Germany, VATUK and Dutch vACC startet using 8.33 khz spacing yesterday.
https://board.vatsim-germany.org/thread ... off.70925/

[dkreiskott]

Hi JL,

yesterday I tested the 8.33 Khz frequencies with different airports. It works fine for me.
Thanks for the adjustment.