MobiFlight Community Support

I just installed n Mega 2560 Pro Mini (which is compatible with M which I will use for my Throttle. Throttle is wired to the board and now connected to my pc. In Mobiflight I add the board and named it Throttle Board. The board's green light is steady telling me it is connected. I right click on the board to update firmware. I get an error "There was a problem uploading the firmware for the board(s) . Throttle Board (COM4)". My Arduino 2650 Mega is on COM3 which I use for my Auto Panel.

I ignore the update thinking is was a glitch and programmed Parking Brake by adding Parking Brake under Throttle Board Module and update module.
Then add Parking Brake (Input) and assign pin 2 as per Throttle Board and click edit.
On press TAB
Action Type FSUIPC-Offset
Load Preset: Controls-Bark Parking
Offset: 0x0BC8
Value type: Int
Bytes: 2
Mask: 0xFFFF
Set Value: 0

This is board
https://make.net.za/product/mega2560-pro/?utm_source=Google%20Shopping&utm_campaign=General%20Product%20Feed&utm_medium=cpc&utm_term=242&gclid=EAIaIQobChMIxIeCnIqq9wIVC5NmAh1MZQd0EAQYASABEgI5NvD_BwE

But no reaction from the throttle when tested in B737 default on the ground.
I look at the log and saw this
ExitCode1 =>Something went wrong when flashing with command "Arduino\hardware\tools\avr\bin\avrdude', C"Arduino\hardware\tools\avr\etc\avrdude.config patmega2560 -cwiring -P\\.\COM4-b115200 -D -Uflash:w:"C\Users\....
I have no clue what this means
Is COM4 the problem?

Your report confusing me....

You say :

I ignore the update thinking is was a glitch and programmed Parking Brake by adding Parking Brake under Throttle Board Module and update module.
Then add Parking Brake (Input) and assign pin 2 as per Throttle Board and click edit.

If you be able to create a device on that Board and update it, then the board is already detected and firmware is on it. Else you would not see it in MF and not be able to upload something.

Best way to test something.... Enable Logging Mode.... Typ Debug.

Then when you press your button you will see if MF detect it or not by check if there is a logging line for every press or release.

***
If yes.... then simply your used Offset/Preset is wrong.
If No.... There is a problem with the Board. Here i recommend a EEPROM Clear and a fresh flashing of Firmware.

I did the logging with debug when I press a button on my throttle MF does not respond in debug window.

How I do EEPROM Clear and a fresh flashing of Firmware or do I just press the reset button on the board. Is this really necessary as the board is brand new with now previous configurations.

Simply gpoogle for a detailed Guide.

Basically you open the Arduino IDE Software.
There you upload the prededined Sketch "EEPROM CLEAR" to the Board and run it.
Then Board is empty and be able to get flashed by MF again.

So EEPROM Clear it....
Shortly Disconnect/Reconnect it.
And then Start MF.
If all is OK MF will tell you there is a new Mega detected and ask if you like to flash MF Firmware on it.
Agree and all should be fine.

DID EEPROM CLEAR STILL THE SAME PROBLEM. CHANGE TO SPARE ARDUINO MEGA 2560 AND WORKS
MEGA 2560 MINI PRO PROBLEM IS THAT IT CAN'T UPDATE FIRMWARE

First: pls don't use only capital letters, this means yelling....

To your problem: have you tried with another cable and another USB-Port?

There are some mystique things going on in Windows with USB....believe me....

I agree to Kai.....

Also a important fact can be the Chip.
Maybe the ProMicro is a CH340 instead of the standard ones.
So get sure you install also correct Drivers in windows for the used Arduino.
Simply google for "CH340 Arduino Drivers" to find a download Link !

Kai, first sorry for the capital letters, was not my intension to yell, I do apologize. I did change to another usb port. Not the cable as I only have one micro USB cable.

Pizman, yes it is a CH340, and did find a link for the driver and will download and revert back.

Thanks for the feedback guys.

Ok, this what's happening thus far.

I downloaded CH340 driver install it and Windows told me that the best driver of the device is already installed. Problem still exists on Mega 2560 mini pro. What is strange though that one limit switch is working but none of the others not even the LED for parking brake.

So I switch to my spare Arduino 2560 Mega again (firmware is updated), now the Parking Brake LED when testing is working and again only one limit switch. I even configure throttle1 encoder but all so no feedback from logging/debug.

So this is really strange as I follow the correct procedure when doing the configurations. Maybe I miss something. I check the wiring of the throttle and no wire is loose from the switches terminals. All so no loose connections on the Arduino

What I do not understand is why will 2 configurations work (LED & one limit switch) but not the others. Can the serial be a problem as it is just a few "yyyyyyyyyyyyy" no letters and numbers like my 1st Arduino on COM3.

Do I need to calibrate the throttle if so where do I start as window 10 only pick up COM5 (Arduino 2560 Mega) under Devices and Printers no gaming control.

Your reports are confusing....

You say the board is shown as "Unknown".
On a Unknown Board you can not create Devices.
Otherwise you tell us you have devices ( One LED one Switch) on that Board.
Means it was detected already , casue you could not create them without detect it.

Also confusing.... You always talk about your "Throttle".
If you have only 2 Devices ( 1 Switch and one LED) how do you want to calibrate something? there is no Poti on it.
If otherwise Poti already there... Are they created in MF as devices ?

Next you say you search for the Device in "Gamecontrollers" .
There are HID Devices (Joysrticks).
If your system is a HID Gamecontroller ( With axis, Potis and so on) then it can not be a Mobiflight Board anymore.

I think you mix up a lot of stuff !

************
Solution:
Give us much more details WHAT we talk about here.
Or
More easy . Contakt us on Discord. By talk together its more easy to figure this out !