Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

numericprofile /radio profil wrong frequencies

Featured Replies

AAO 3.00 b53 SD 6.1.0.18521 Lorby AAO Integration 18.01

Good day , thank you for the "numericprofiles" I downloaded from https://www.axisandohs.com/.
I use from the "radio profile" to set the radio frequencies on the FlyByWire A320 and other aircraft ( default B747) and I have observed the following.
With frequencies with the decimal fractions .015, .035, .055 , .065 , .085 it does not work. For example, 118.015 when set to Standby or Active results in 118.010. At 118.035, 118.030 is set and so on.
If I enter the frequency directly via mouse clicks on the radio panel it works, so it's not the aircraft.
I suspect that the dec2b16 function is not working properly in converting these numbers, but I don't know enough about this function to be able to really judge. Can someone help me?
Thanks Stefan

regards
Stefan Liebe

  • Commercial Member
On 4/19/2023 at 8:42 AM, Stefan01 said:

If I enter the frequency directly via mouse clicks on the radio panel it works, so it's not the aircraft.

...but the aircraft is free to use any other type of frequency encoding logic which can be completely unrelated to the MSFS SDK or to what the example SD profile does. 

Not sure, but if I remember this correctly, the default K-events (which have been chosen for compatibility with the legacy sims FSX and P3D) cannot process the values with the required precision. K-Events cannot process floating point numbers at all, so they must be converted to integers and then BCD encoded - and at that point the K-event fails. 

I think that for these aircraft you would have to find another way to input frequencies, maybe by writing it directly into the variables that the plane is using.

The SD profiles on the AAO website are just examples of how to use the AAO WebAPI - feel free to adapt them any way you wish.

Edited by Lorby_SI

LORBY-SI

  • Author

I found a workaround for the malfunction after all. I have extended the radio profile by 2 buttons.
One has the key down event K: COM_RADIO_FRACT_DEC
and the other has the Key Down Event K: COM_RADIO_FRACT_INC.
So I can set the faulty standby frequency correctly.
Thanks again for the Profile Cheers Stefan

regards
Stefan Liebe

  • Commercial Member

If you are entering frequencies with three fraction digits, change the Key Down events S: code to the following in the StreamDeck actions. Be mindful that this only works in MSFS - I've added an extra profile for the radios in MSFS to the download.

 

COM1 active:
(L:MyFreq, String) stod 1000000 * (>K:COM_RADIO_SET_HZ) '' (>L:MyFreq, String)

COM2 active:
(L:MyFreq, String) stod 1000000 * (>K:COM2_RADIO_SET_HZ) '' (>L:MyFreq, String)

COM1 stby:
(L:MyFreq, String) stod 1000000 * (>K:COM_STBY_RADIO_SET_HZ) '' (>L:MyFreq, String)

COM2 stby:
(L:MyFreq, String) stod 1000000 * (>K:COM2_STBY_RADIO_SET_HZ) '' (>L:MyFreq, String)

 

Edited by Lorby_SI

LORBY-SI

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.