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
jeff_d
Posts: 15
Supporter
I have several propwash dual rotaries. All but one of them have been working fine. Any time I connect the problem child to a set of pins on my Sparkfun clone those pins stop working for any rotary. If I switch the pins back to buttons they seem to work fine. Switching to rotary pins to buttons I can see correct output behavior for the rotary:
16:16:28.875 -> 7,Pin8,1;
16:16:29.015 -> 7,Pin9,1;
16:16:33.234 -> 7,Pin8,0;
16:16:33.281 -> 7,Pin9,0;
----
16:16:36.469 -> 7,Pin9,1;
16:16:36.656 -> 7,Pin8,1;
16:16:38.015 -> 7,Pin9,0;
16:16:38.109 -> 7,Pin8,0;
I get no output when in rotary mode for those pins

Once the two pins get into this state no other rotary works on them and updating the FW doesn't seem to fix it. I've checked the wires multiple times and having found any ground issues or anything like that. Is it something in the rotary that can causes this or is there an issue in the FW that isn't handling something correctly? My current config:

<?xml version="1.0" encoding="utf-8"?>
<Config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<ModuleName>LowerNav</ModuleName>
<PowerSavingTime>600</PowerSavingTime>
<Encoder Name="DR_L_S" PinLeft="1" PinRight="0" EncoderType="2" />
<Encoder Name="DR_L_B" PinLeft="3" PinRight="2" EncoderType="2" />
<Button Name="DR_L_P" Pin="6" />
<Encoder Name="SR_TRIM" PinLeft="10" PinRight="16" EncoderType="1" />
<Button Name="SR_TRIM_P" Pin="14" />
<Encoder Name="DR_R_B" PinLeft="5" PinRight="4" EncoderType="2" />
<Encoder Name="DR_R_S" PinLeft="9" PinRight="8" EncoderType="2" /> <-------- this is the one that has issues.
<Button Name="DR_R_P" Pin="7" />
<Button Name="U_15" Pin="15" />
<Button Name="U_19" Pin="19" />
<Button Name="BTN_RED_U" Pin="20" />
</Config>

Originally the rotary was on pins 6/7 and then moved it to 8/9 with the same result. I did order a MEGA 2560 "Pro" (smaller clone) board to see if that makes any difference.
2021-04-21 05:54
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
Hi

I not know if my Idea is the solution for your Problem..... But basicly you have a Bigger Misstake here.....

iconQuote:

<?xml version="1.0" encoding="utf-8"?>
<Config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<ModuleName>LowerNav</ModuleName>
<PowerSavingTime>600</PowerSavingTime>
<Encoder Name="DR_L_S" PinLeft="1" PinRight="0" EncoderType="2" />
<Encoder Name="DR_L_B" PinLeft="3" PinRight="2" EncoderType="2" />
<Button Name="DR_L_P" Pin="6" />
<Encoder Name="SR_TRIM" PinLeft="10" PinRight="16" EncoderType="1" />
........
</Config>



HOW do you set the Encoder DR_L_S to Pins 0 and 1 ???
This should be permitted in the UI. Pins 0 and 1 are INOP and should be not possible to choose in Settings/Device Create Process.

So... At first. Solve this.... Set your Encoders to regulary Pins ( not 0,1) and then test again.
May the fact, there are devices on Pin 0,1 occure in this issue.

If this not help please report again !
Good Luck !
2021-04-21 14:07
Avatar
jeff_d
Posts: 15
Supporter
Thanks for the response. I know I'm working off the book here since I'm using a clone board. 0/1 on my board can be used as digital input. I'm hacking around the UI by editing the file directly (please don't fix). The FW seems to be happy to use these values and it does work for that. https://golem.hu/article/pro-micro-pinout/

I did solve the issue I'm having. I think I had maybe an intermittent connection issue to the rotator. After re-soldering everything it now seems to be working as expected. I'm able to use all of the pins accept A0 and A3. I also just order a Meg so I'll be switching to that for my bigger panel.
2021-04-22 00:53
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
Hi again

Not get scarred. We will not blocking you.
If you rework (hack) the system by editing the mfmc file or by editing the MF source Code..... Thats your personal decision.

Just note......

For the future.... If you get in trouble, then at first build a test System within the official recomendations.
If the issue also occure in a "standard" System then we will support you..... Cause thats our Job !
BUT
If the build work fine in a regular setup but occure in issues with your "personal reworks".... Then not ask for help!

I hope you understand....
Its like a DVD Player.... If you open the case and solder a diode yourself on the PCB then the garantee is lost and the customer support will no longer help you !

At last.... I personaly high recommend to not use Micro Pro Boards..... Megas work fine ( And Mega Pro Minis) . If you like a "smooth" life then use the Megas. You not need to use Pin 0,1 in case you got 68 full working Pins ..... Much more as a micro..... So.... No trouble, More Pins, Simply use Megas !
Good Luck !
2021-04-22 19:44
Avatar
jeff_d
Posts: 15
Supporter
Yes the Mega pro showed up yesterday and I integrated it into my pit. Seems to be working much better and the extra pins are nice. I just had some of the Micros sitting around and wanted to see if they would work. Some of my button boxes are very small and a Mega (even the smaller pro) is just to big.
2021-04-22 21:01
icon