MobiFlight Community Support

Welcome to the forum for MobiFlight! Feel free to reach out to the community in case you have questions, issues or just want to share great ideas or details about your latest home cockpit project.

You like MobiFlight? Donate via PayPal and support the MobiFlight development. Thanks! 

icon
Avatar
mikeb1028
Posts: 29
Supporter
I setup LED display modules for COM1 and COM2 in X-Plane 11.

If the radio shows 121.255, the value passed by XPUIPC (similar to FSUIPC) shows 2125 (not the "5" on the right) - my display shows 121.250 and not the 121.255 on the simulator.

Has anyone modified this to show the correct frequency when there is a "5" or another number other than 0 as the last digit?

Thanks for the help!
Mike
2018-08-05 06:25
Avatar
paul_max
From: United Kingdom
Posts: 70
Supporter
Mike

At first glance it looks like a bug in XPUIPC.

Paul
2018-08-05 08:14
Avatar
StephanHo
From: EDDG, Germany
Posts: 1269
Supporter
Hi Mike,

no, it is not a mistake!

The FSX and also FSUIPC were designed and programmed more than 10 years ago. At that time there was the so-called 25 kHz grid in the frequency spectrum. Although this could not be displayed with 2 decimal places, but it was known that frequencies that ended with ###. # 2 or ###. # 7 as (invisible) 3rd place had a 5 (I have that as a student pilot still so learned).

At that time it was considered not so important to introduce a 3rd decimal place in the devices for these 2 digits.

Meanwhile, the 8.33kHz grid was introduced on all (real) aircraft. The frequencies today look like this:

120.000
120.008
120.017
120.025
120.033
120.042
120.050
120.058
120.067
120.075
120.083
120.092
120.100
etc.

This grid can no longer be displayed with 2 decimal places. Since XPUIPC is based on FSUIPC, even with the newer simulations this frequency grid can not be displayed. In order to remain backwards compatible, the new frequency grid has not been adopted because FSX-based simulations can not cope with it.

A pure X-Plane simulation or P3DV4 would be pretty straightforward, but if you work with F(X)SUIPC, the path would be blocked.

Even in the networks IVAO and VATSIM this frequency grid has not been adopted to my knowledge, because there would be a mess between FSX and newer simulators. If the new grid were agreed, the FSX participants would be excluded (not from flying, but from the frequency settings). So this step was not gone.

In that sense, it is neither a mistake of any software, but simply fails to develop it.
Grüße,
Stephan
2018-08-05 10:13
Avatar
mikeb1028
Posts: 29
Supporter
Thank you for the explanations and the help.

I kept wondering why, when I tune the COM radio and stop at a frequency ending with a "5" (eg. 120.285) the return from XPUIPC was not showing the last digit.

And with FSX users on VATSIM, I see why the network needs to comply with the older sim.

So, I will not need to find a way to configure the odd KHz frequencies!

Thanks again,
Mike
2018-08-06 05:52
Avatar
mikeb1028
Posts: 29
Supporter
I see a potential problem with this, at no fault of MobiFlight.

If I use an encoder to change the COM frequency and my display shows 120.280, the radio on the aircraft can still show 120.285 because it can tune to that but X/FSUIPC cannot display it. So what then? I'm relying on my LEDs to show the accurate frequency.

???
2018-08-06 18:56
Avatar
StephanHo
From: EDDG, Germany
Posts: 1269
Supporter
If you tune the 25kHz grid (the old one - standard one) with the encoder then the values from MF-> F(X)SUIPC will also only generate values of this grid
Grüße,
Stephan
2018-08-06 21:16
Avatar
mikeb1028
Posts: 29
Supporter
Ok Stephan. That sounds great. Thank you for the help!
2018-08-07 05:37
icon