MobiFlight Community Support

Hello:

breaking my head again....help appreciated!

This is what I want to config (short version):

1 encoder:
Turn: change Mhz NAV1
Press: change from Mhz to kHz
Turn: change kHz
Press: change from kHz to MHz
etc etc.

So: turning make the value change: pressing the encoder changes Mhz or kHz.

What does work:
Mhz change with encoder
Khz change with encoder
The on_press switch of the encoder (tested with an other function than this)

What does not work:
changing the function of kHz <-> Mhz by pressing the encoder

When I look at MobiFlight the FSUIPC values I see that the mem location I use always is 0, it never changes:

The config:

1): I coupled the button of the encoder to mem location 0xCC60. As value I use a toggle function with each press.




2): I defined an output which uses the same mem location as defined in the input. There is no precondition defined.



Now...I know I need to do more (i.e. define preconditions for the Mhz and kHz change_inputs) but: to make this a shorter story:it does not work.

The problem is that in the output tab where I defined the MEM_NAv1_toggle location the FSUIPC value should change from 0 to 1 and back to 0 and so on with each press on the rotary encoder.

This does not happen: the value always stays on 0. The encoder switch itself is perfect: I temperarely defined it as a nav active-stdby swap and that works fine so physically the switch is perfect.

Now...as a test I did this on the settings of the input_memory location:




I hard_coded the value as 1 on press and 0 on releas (no picture from that but I did).

Checked the output and...it stays the same:0

also I changed both, on press and release to 1: same

Changed it to value 55 on press and release: same.

So: my problem_conclusion is that I am not able to communicate with this address.

Also tried other adresses in the CCxx range but same problem.



Any thoughts?
Thanks!

Hi

At first. THANK YOU! That is a perfect and nice request. All Information are listed. I see what you do and still try. If everybody would request same way, my life woud be more easy! Just note: If you make those requests via DISCORD you not need to difficult Upload the Pics... There you can simply copy paste your screenshots more easy.

*****

About Request.

Your issue is just a wrong Offset
Hopefuly this misstake was not located to myself.... E.g. I gave you a wrong guide by a typing Error in a other Topic!

YOU use the Offset CC60 .... Thats Wrong. The whole Area of Cxxx 4096 Bytes is for the Waether System and mostly is not allowed to Written and not free!

The Correct Offset Area for Custom Config use is 66C0 !!!

******

Last Note: I see you named the Config "Mem Nav 1 Toggle" ..... Looks to me you plan for a Readout Config for each of the Encoders ( Nav1, com1 Nav 2 Com 2 and so on)
THIS is not needed..... You will never controll 2 systems same time. So it´s not needed that every system got it´s own Mhz/Khz logic individual.

Best solution.... You use ONE Offset ( e.g. 66C0) for ALL Mhz/Khz Toggles ! Sure... Each Encoder got a own Button.... So you need 4 Input Configs. BUT All 4 configs will write the same Custom Offset. (Just duplicate that Input config 4 times and only change the device to the other encoder Push buttons)
Finaly all Encoder Configs ( Whatever Com1, Nav1 and so on) will use as precondition the same "mem" Config.

Result: If you turn the COM1 and you like to swap then you press the Com 1 Encoder Button. Mhz change to Khz. In same moment all other Encoders also change.... But thats no matter cause you use only COM1 a.t.m.
This will save you lots of configs and lots of individual preconditions.... Cause now all work same way.

Aaah!! Thank You Pizman!!

I just changed it to 66C0 and..BANG!!! WORKING!!

I do have an other question now:

1) What mem_locations are now available for personal use?? (can't see it in the FSUIPC list and I do need some more)

2) Is there a possibility (in MF??) to directly monitor the input and output status of the MEGA?
In case something does not work it would be a great help to see what is going on at the pins of the MEGA, sepecially the input pins.

3) total different question but: Analogue inputs A0..A15 : they can be used as digital inputs I assume but can they within MF also act as digital output? What pinnumber they start (A0=54, A1=55 etc, correct?)


I see what you meen by 1 location for the Mega or Kilo hz.... Worst case is I need 4 memory places: Com1/2 and Nav 1/2....
You are right, so may-be I try to make it that you can press whatever encoder -> makes the memLocation chage -> change k or Mhz.

So...only 1 location but multiple physical encoders which can toggle this. And..may-be a control_led so I can see if it is M or K what is changing....

Discord...thank you for the advice....uploading pic's no problem and may_be other people can learn from these postings as well (I learn from other ones )

Again, thank you very much for your help!

Hi again.

1. Just check the FSUIPC List.... On 66C0 there is written.....

66C0 64 Free for general use, for example in button or keys
programming

4200 256 Free for general use, for example in button or keys
programming.

Note: Also non used AddOns are for free.... So if you have no PMDG and your AddOn not use that area then also all PMDG Offset are free.

2. Not directly. you can not see if a Pin is ON or OFF. But you got other tools.
With the TEST Function in Output Config Display Tabs you can check the LED and Displays.
With the Logging Mode ( Debug) you can observe Inputs.... everytime you Press or Release a Button there is a notification there.
BUT You can NOT directly ask if e.g. A Switch is currently ON or OFF.... You just cann see a "change" if it happen.

3. Correct. A0 = 54 and so on.

Thanks Pizman for your information....learning more every time

Now....everything is fine and understood, only can not get the switches visable as you describe:

"With the Logging Mode ( Debug) you can observe Inputs."

I assume this is within FSUIPC and not within MF?? (could find nothing in MF, the LED's/outputs I can test in MF, that's great.)

What I did in FSUIPC: Logging --> enable 'Log Buttons & Keys' -> Open console -> console log

I can see the console and I see a lot of information when starting MSFS and, when everything is settled, I can see on the console when I press a key on my keyboard but NOT when a MobiFlight defined key is pressed or toggled, nothing is going on at the console.

Now...may-be when I enable Events in the console I can see events when a key is pressed but I can watch that in MF as well: it's when kays are not working that you want to know first if the hardware is ok by monitoring the inputs on a direct level.


So...do you refer to somewhere else to look or should I enable something else in the logging option of FSUIPC?

Thanks!

I assume this is within FSUIPC and not within MF??

WRONG ! It´s inside MF.

Go to Settings..... Enable "Logging Mode" by click the checkbox. Then choose from Dropdown DEBUG

Then below the MF Conncetor Window ( Input or Output Tab) you see a "new" area. There the logging is shown.

Great!

Thank you for your explanation.

Works perfect...and MF still has a lot of 'secrets' for me

Thank you