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! 

05/03/2024 - This forum is read-only

The community support for MobiFlight has moved exclusively over to our Discord server. Register for free and enjoy more interactive functions like image and video upload, voice chat. More than 7,000 registered users around the world make it a great experience!

See you on our MobiFlight Community Discord server.

A HUGE Thank You to everyone who participated in the forum, especially obviously to Pizman and Stephan who did an outstanding job over so many years providing an incredible service to the MobiFlight community.

The forum is still providing a lot of good content, hence we keep this information accessible.

icon
Avatar
Endprodukt
Posts: 7
Hey there! New here, loving Mobiflight and got super fixed on building my panel.

Started by building throttles and now went onto working on a elevator trim. Everything got setup using a servo and an encoder - no problem...until I hooked up the
rest of my stuff (Basically Logitech/saitek Panels and two Arduinos that use the joystick.h for the throttle and the yoke).

Mobiflight starts crawling, takes minutes to load, no chances accessing the settings. As soon as I disconnect the other arduinos, I'm back in business.

The problem is I really need to use potentiometers so no workaround here.

I really really hope someone can help me out.

I tried reflashing the device, deleting all the mobiflight settings etc but nothing helped so far.

Best regards,

Olli
2020-09-30 21:27
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
Hi

Pretty sure your problem are the Arduinos that are used with Joystick.h sketch.
Mobiflight is based to detect all arduinos in the system and offer you to install the Mobiflight firmware. Thats Ok cause 95% of users not have other arduinos and enjoy this feature that MF find each arduiono itself.

In your case i recommend to disable the function " Auto Flash Firmware" . then Mobiflight simply ignore the Arduinos temporary.
NOTE: That means MF will also not flash firmware to exisiting or new MF Boards if there is a update . In your case its maybe needed to enable that tool if there was a update OR to install MF Firmware by hand ( Rightclick ins ettings tab) to all active board by hand,

Please report if this disbale of Update solve the problem!
Good Luck !
2020-10-01 01:23
Avatar
Endprodukt
Posts: 7
Thanks for getting back to me.

Deactivating the automatic firmware update is the first thing I did. Unfortunately that didn't help at all.

Mobi takes forever going through the three Arduinos and it's basically unusable after that.

There is no way I can give up on potentiometers. I'll be
Using them all over the cockpit.
2020-10-01 01:35
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
You not need to give up them. Mobiflight is basicly build to work "side by side" with other aplications and also other Arduinos that NOT use Mobiflight itself.
Pretty sure here we got a issue.... Maybe by sircumstance a identical identification or a never known "point of death"

If possible.... Please use the Logging Mode in MF..... Enable it in Typ DEBUG. Then Start Mobiflight and wait some time. So maybe Issue reports and errors are listed in that log while MF try to startup. Finaly save this file ( Log.txt in MF folder) to a other place and send it to us. ( most usefull via DISCORD to Sebastian, Stephan or Myself) .
We will have a look and with some luck we still see the problem in that log file !

Prepare do do some testings with a BETA Version if it´s needed !
Good Luck !
2020-10-01 01:41
Avatar
Endprodukt
Posts: 7
Awesome! Sure here to help!

I'll get the log files tomorrow and come to the discord. Thank you very very much!
2020-10-01 01:50
Avatar
Endprodukt
Posts: 7
Okay, so this is a bit embarrassing. The problem was the specific USB port that I was using. Now it's working fine.

The only "problem" left is that the trim wheel doesn't reflect the speed in the game. The encoder is already on 4 cycles but it's still nice too slow in msfs2020 (c 152).

I read somewhere that in other sims this is a per plane setting in a text file. Anybody tested this is fs2020?

Sorry for the drama. All is good now.
2020-10-02 15:12
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
Hi again.

So The USB/ Hardware Problem is fully solved if i understand correct.


About Encoder:

STOP:!! :scared: The Settings in the Device Upload Menue ( 1:1 , 1:2, 1:4 ) NOT relate to the speed of the Encoder. There exist different encoders ( resolution of detents and signals) ..... This setting must be done to make each encoder work correctly. If you use a wrong setting this will not increase turning speed. INSTEAD it will remove steps finaly !

If your encoder is to "slow" then your choosen Input "formula" is wrong. For example if trim goes from 0-1000 and your Encoder increase the Trim by one 360 turning just by 20 but in Sim the one turning increase already by 100 then you must change the Config.... So one detent increase the Trim not by 1..... it must increase by 5 to have the same effect.

Play with the used value.... And also tryout the On Fast Settings !
Good Luck !
2020-10-02 15:54
Avatar
Endprodukt
Posts: 7
But that's the problem. I can't find anything like that. I can only set the event id and the parameter.

Nevermind. Figured it out! Thank you very much
[Last edited by Endprodukt, 2020-10-02 18:09]
2020-10-02 17:55
Avatar
stvnrwd
Posts: 2
@Endprodukt - How did you fix it? I am experiencing the same issue.
2020-10-03 04:22
Avatar
StephanHo
Moderator
From: EDDG, Germany
Posts: 1867
Supporter
Hi,

try as follows:go into the menu -> EXTRAS -> SETTINGS -> MOBIFLIGHT MODULES

and look for the module the encoder is installed on. Click on the encoder and on the right side you can see the settings of the encoder.
Try the settings under TYPE:1, 2 or 4 detent(s)

That's what pizman means.

After changing the settings for the encoder upload it to the module, save the mfmc-file and restart the module.
This has to be repeated until the setings are so that you got a pulse for every detent.
Grüße,
Stephan (Time: UTC+2)
2020-10-03 10:18
Avatar
Endprodukt
Posts: 7
You have to use offset and use the parameter

Wheel up:
$+300

Wheel down:
$-300

Now with the number you need to play. It sets the range for one detent.

The fsuipc offset is 0BC0, size 2 (bit).
2020-10-04 11:04
icon