Almost all my configs are gone after updating to V10.0.2 | MobiFlight | Page 1

analog dirge Jan 3, 2024, 12:09 AM

#

I just updated to version 10.0.2 on MobiFlight and all 3 of my nanos lost there config. What do I do?

#

ok update: still having the issue but now one of the displays on the nano's is fully lit up and i dont know why

#

i closed mobiflight and its still doing it

strong swan Jan 3, 2024, 7:34 AM

#

@analog dirge hey there! sorry to hear your experiencing trouble.

#

will they show as "compatible"?

#

please enable logging (debug) and share your log.txt file - you can find the file in the installation folder

#

%LocalAppData%\MobiFlight\MobiFlight Connector

strong swan Jan 3, 2024, 10:10 AM

#

@tame tangle please open a separate topic in #1028767888242376794

strong swan Jan 3, 2024, 10:28 AM

#

it's different, please open a separate thread

tame tangle Jan 3, 2024, 10:37 AM

#

I deleted it, because i reloaded a backupfile and this is ok so far.

analog dirge Jan 3, 2024, 8:11 PM

#

strong swan will they show as "compatible"?

yes they are still showing as compatible however when i first launched V10 it said all my nanos were orphaned.
also here is the log.txt

📎 log.txt

strong swan Jan 3, 2024, 9:37 PM

#

when they show as compatible, that means they are not recognized properly

#

your log file is very incomplete

#

probably you have to set the debug level to DEBUG

#

just try the following.

#

Go to %LocalAppData%\MobiFlight\MobiFlight Connector\Boards and drop the following file there:

📎 arduino_mega.board.json

analog dirge Jan 3, 2024, 9:39 PM

#

ok heres the log with degub level

📎 log.txt

analog dirge Jan 3, 2024, 9:40 PM

#

strong swan Go to `%LocalAppData%\MobiFlight\MobiFlight Connector\Boards` and drop the follo...

ok

strong swan Jan 3, 2024, 9:40 PM

#

stop

#

the log tells me that all your four boards are connected and "discovered" correctly

#

no need to change the file

analog dirge Jan 3, 2024, 9:41 PM

#

oh ok

strong swan Jan 3, 2024, 9:41 PM

#

so what's the problem now exactly, I am confused.

#

The boards should show correctly with their board names

#

you should see the names in the status bar, and also in the mobiFlight board settings

#

can you confirm that.

analog dirge Jan 3, 2024, 9:42 PM

#

yes there all in the MobiFlight Modules tab in settings with the correct names

#

the problem is when i updated the configs for all 3 of my nanos somehow vanished

strong swan Jan 3, 2024, 9:43 PM

#

what do you mean

analog dirge Jan 3, 2024, 9:44 PM

#

as you can see, the nanos no longer have anything attached to them

strong swan Jan 3, 2024, 9:44 PM

#

ok. yes.

#

can you click on one please

analog dirge Jan 3, 2024, 9:45 PM

#

strong swan Jan 3, 2024, 9:46 PM

#

did you ever reset the boards? Or did you just upgrade the firmware?

#

can you try running with 9.7.1 and see if that makes a difference.

#

?

analog dirge Jan 3, 2024, 9:46 PM

#

just upgrade the firmware, never reset them. it also said the nanos were orphaned when i first launched v10

analog dirge Jan 3, 2024, 9:46 PM

#

strong swan can you try running with 9.7.1 and see if that makes a difference.

sure

strong swan Jan 3, 2024, 9:46 PM

#

if that happens, that means, that the serial has changed.

#

@cinder heron I am supporting here

#

just looking at the log.txt file everything is looking normal

cinder heron Jan 3, 2024, 9:49 PM

#

Hmhm

strong swan Jan 3, 2024, 9:49 PM

#

@analog dirge it would be extremely helpful if you could download the 9.7.1 zip file. Extract it in a temp-folder

#

and then downgrade the firmware.

#

did you have 7-segment displays on your nano?

analog dirge Jan 3, 2024, 9:50 PM

#

i have 9.7.0 running right now, im currentley in the process of downgrading them

analog dirge Jan 3, 2024, 9:50 PM

#

strong swan did you have 7-segment displays on your nano?

yes

#

would i need 9.7.1 specifically?

strong swan Jan 3, 2024, 9:50 PM

#

https://github.com/MobiFlight/MobiFlight-Connector/releases/tag/9.7.1

GitHub

Release 9.7.1 Release (Bugfix) · MobiFlight/MobiFlight-Connector

What's Changed
Bug Fixes 🐛

Handle exception when loading a config from a connected board by @DocMoebiuz in #1177
Update Pico board.json file to match firmware values by @neilenns in #1147
Prev...

#

yes. just to see if it works with the old version still... and there you can upload the old firmware too

analog dirge Jan 3, 2024, 9:52 PM

#

ok sure, and on the topic of the displays, they started doing this

#

even when mobiflight is closed

#

not sure if thats related

strong swan Jan 3, 2024, 9:52 PM

#

so you have max7219 on the nanos?

analog dirge Jan 3, 2024, 9:53 PM

#

yes, each one is on its own nano

strong swan Jan 3, 2024, 9:53 PM

#

that's the only device that is not compatible with a downgrade

#

😄

#

shoot!

#

ok... don't go back to 9.7.1

analog dirge Jan 3, 2024, 9:53 PM

#

ok

strong swan Jan 3, 2024, 9:53 PM

#

can you enable beta and update to the latest beta

#

it is in settings.

analog dirge Jan 3, 2024, 9:53 PM

#

in v10?

strong swan Jan 3, 2024, 9:53 PM

#

yes

analog dirge Jan 3, 2024, 9:54 PM

#

ok

#

ok im on the beta

#

10.0.2.2

#

there still showing no devices on the nanos

strong swan Jan 3, 2024, 10:01 PM

#

dang

analog dirge Jan 3, 2024, 10:02 PM

#

what would cause the serials to get changed?

safe dock Jan 3, 2024, 10:03 PM

#

sorry to barge in, I suppose @analog dirge does not have mfmc files saved with his device configurations? That he can just load again?

analog dirge Jan 3, 2024, 10:04 PM

#

do those get saved automaticaly or would i have to create those my self?

safe dock Jan 3, 2024, 10:04 PM

#

If Mobiflight reports the boards as empty is there really a chance the configs are still in the eeprom?

#

No. the mfmc file is just a backup of the EEPROM config with all the devices. You have to tell the Modules dialog you want to save it.

#

it is not necessary until sh*t happens

analog dirge Jan 3, 2024, 10:06 PM

#

ok

#

so

#

i have one .mfmc saved under the name "MobiFlight Nano"

#

should i try and load it under one of the nanos?

cinder heron Jan 3, 2024, 10:13 PM

#

I can upload a program which dumps the eeprom content. But I have to prepare the description, mainly how to make a serial connection to get the output.
I can not get it done this evening, will be tomorrow.

#

And I would like to test it before I upload it. Did it to long ago.

safe dock Jan 3, 2024, 10:14 PM

#

i have a sketch that prints the eeprom to serial, if that is what your are after

cinder heron Jan 3, 2024, 10:14 PM

#

Yes

safe dock Jan 3, 2024, 10:14 PM

#

hang on a sec

#

📎 eeprom_read.ino

#

this will read the eeprom and print to serial first as hex code and then as ascii code

cinder heron Jan 3, 2024, 10:16 PM

#

Once we see what is in the eeprom it can be decided if we can restore it.

#

Best would be to get it in ASCII format, not hex. Too late for me to check the code, sorry.

#

Have to leave now...

safe dock Jan 3, 2024, 10:17 PM

#

you get both

#

@analog dirge can you please try to load this sketch and run it in you nano... make sure to open the serial monitor set to 9600 baud rate.

#

it will just read the eeprom and dump it to serial. You should then select the output from serial monitor and save it to a txt file please.

#

frankly it is a lot to do, was the config a large number of devices?

analog dirge Jan 3, 2024, 10:19 PM

#

ok would this be done somewhere in MF?

analog dirge Jan 3, 2024, 10:20 PM

#

safe dock frankly it is a lot to do, was the config a large number of devices?

uhh it was most of the pins on 2 of the nanos

safe dock Jan 3, 2024, 10:20 PM

#

maybe it is easier to just re-create the devices.

#

no, the sketch goes to arduino IDE

analog dirge Jan 3, 2024, 10:21 PM

#

small issue, i cant access the nanos anymore without breaking my panel (bad design on my part)

analog dirge Jan 3, 2024, 10:21 PM

#

safe dock no, the sketch goes to arduino IDE

ok

safe dock Jan 3, 2024, 10:21 PM

#

no wiring needs to be changed

#

you just need access to the usb port connected to your PC, and running arduino IDE, instead of Mobiflight Connector

#

even if there are remnants of the config there, it would be useful as it will most likely say which pins are used for what

analog dirge Jan 3, 2024, 10:23 PM

#

yea thats another problem, i dont know whats connected to what pin

safe dock Jan 3, 2024, 10:23 PM

#

so if recreating the devices is difficult because you can't see the wiring connections anymore, then this is another way.

analog dirge Jan 3, 2024, 10:23 PM

#

so if it tells me that it would be great

safe dock Jan 3, 2024, 10:24 PM

#

so, I suggest you open arduino IDE and load the sketch

#

I would disconnect all boards

analog dirge Jan 3, 2024, 10:24 PM

#

ok so i have it in the IDE and its compiled, should i upload it to one of the nanos?

safe dock Jan 3, 2024, 10:24 PM

#

just leave the target nano connected

analog dirge Jan 3, 2024, 10:24 PM

#

ok

safe dock Jan 3, 2024, 10:24 PM

#

do you have serial monitor open and set to 9600 baud?\

#

if you are sure your target board is correct in IDE, go for it..

analog dirge Jan 3, 2024, 10:26 PM

#

no it keeps saying COM5 isn't available, how should i change it to the correct COM

#

its been a wile since ive used the IDE

safe dock Jan 3, 2024, 10:28 PM

#

close Mobiflight

analog dirge Jan 3, 2024, 10:28 PM

#

its closed

safe dock Jan 3, 2024, 10:28 PM

#

reboot

analog dirge Jan 3, 2024, 10:29 PM

#

ok one second

safe dock Jan 3, 2024, 10:29 PM

#

do you have Cura?

#

that is one known app to capture the serial ports

analog dirge Jan 3, 2024, 10:30 PM

#

No I don’t

#

I can download it once my computers back up

safe dock Jan 3, 2024, 10:33 PM

#

no, I didn't mean for you to load Cura if you don't have it

#

I am saying Cura is known to cause interference because it captures and does not release the serial ports, thus preventing other apps from using them

analog dirge Jan 3, 2024, 10:34 PM

#

ohh

#

my fault

#

ok so its either com9 or com4

safe dock Jan 3, 2024, 10:35 PM

#

rebooting your pc should give you a clean slate on serial ports use

analog dirge Jan 3, 2024, 10:36 PM

#

ok yea its 9

safe dock Jan 3, 2024, 10:36 PM

#

I suggest only having the target nano connected.

#

so there is no confusion

analog dirge Jan 3, 2024, 10:36 PM

#

yea all the others are disconnected

safe dock Jan 3, 2024, 10:36 PM

#

make sure to select the proper type of board in the IDE

analog dirge Jan 3, 2024, 10:37 PM

#

yea board and processor are correct

#

im going to upload it now, i have the serial port open on 9600 baud

#

avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x31 avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x37 avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0x2c avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0x4f avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0x4b avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0x3b avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0x0d avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0x0a avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0x0a avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x0a

#

fire

#

an error

#

it failed to upload

#

the serial monitor gave me ⸮

safe dock Jan 3, 2024, 10:41 PM

#

dang... try to load the blink sketch

#

loading sketches does not erase the eeprom

#

hopefully blink will go through

analog dirge Jan 3, 2024, 10:42 PM

#

ok its uploading

#

avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x31 avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x37 avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0x2c avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0x4f avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0x4b avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0x3b avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0x0d avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0x0a avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0x0a avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x0a Problem uploading to board. See https://support.arduino.cc/hc/en-us/sections/360003198300 for suggestions.

#

failed again

safe dock Jan 3, 2024, 10:43 PM

#

Is there no error message other than what you show?

#

I remember there is a way to turn avrdude output to verbose in the IDE options

analog dirge Jan 3, 2024, 10:47 PM

#

yea thats the only one im getting

safe dock Jan 3, 2024, 10:47 PM

#

ohhhh are you sure you are NOT USING pins 0 and 1 in the Nano

#

those are not allowed

analog dirge Jan 3, 2024, 10:47 PM

#

uhh

#

i probably am

safe dock Jan 3, 2024, 10:48 PM

#

because serial communications use those pins

#

so, please disconnect whatever is on those pins

analog dirge Jan 3, 2024, 10:49 PM

#

uhh, i cant

#

i would need to break my pannel

#

well

safe dock Jan 3, 2024, 10:49 PM

#

you have to correct this anyway

analog dirge Jan 3, 2024, 10:49 PM

#

not break but take it apart in a way its not meant to

safe dock Jan 3, 2024, 10:49 PM

#

you could not have been using the arduino Nano with devices connected to pins 0 and 1.

#

and still be able to upload firmware to those boards

#

it doesn't work that way

analog dirge Jan 3, 2024, 10:50 PM

#

ok but then why was it working in MF before?

safe dock Jan 3, 2024, 10:51 PM

#

maybe you uploaded the firmware before connecting devices to those pins, I don't know

#

the MF user interface also does not allow you to assign devices to those pins

#

so, I don't know what you did

#

or maybe you are mistaken and did not use those pins

analog dirge Jan 3, 2024, 10:52 PM

#

ok, ill try and see what i can do about that. but i was able to upload to one of the other nanos having issues

safe dock Jan 3, 2024, 10:53 PM

#

can't you just peek inside the panel and see if there is anything connected to those pins?

analog dirge Jan 3, 2024, 10:54 PM

#

i designed it pretty bad, it was my first panel tbf

safe dock Jan 3, 2024, 10:54 PM

#

you can't configure devices to those pins, so I am confident you are most likely mistaken about using pins 0 and 1.

analog dirge Jan 3, 2024, 10:54 PM

#

i can do it, just not rn

#

i got this out of one of my nanos

safe dock Jan 3, 2024, 10:57 PM

#

ok

#

is that one of the faulty nanos?

analog dirge Jan 3, 2024, 10:57 PM

#

yes

safe dock Jan 3, 2024, 10:58 PM

#

I am not an eeprom format expert, but I think it is corrupted

#

copy that to a text file and post it here

analog dirge Jan 3, 2024, 10:59 PM

#

thats nice,

#

ill do that

#

i also got it out of the other nano

#

2/3

safe dock Jan 3, 2024, 10:59 PM

#

ok

#

good

#

what was causing the upload to fail?

analog dirge Jan 3, 2024, 11:00 PM

#

no not the one failing to upload

#

i have 3 nanos

#

2 of them uploaded

#

the 1 didnt

safe dock Jan 3, 2024, 11:01 PM

#

ok, there is always the possibility that the Nano bootloader got corrupted and that is why it is not responding.

analog dirge Jan 3, 2024, 11:02 PM

#

hmm ok, also for whatever reason its not leting me copy the things off the resource monitor so unless i can export it somewhere the best i can do is a screen shot

safe dock Jan 3, 2024, 11:02 PM

#

you may need to reload the bootloader which implies connecting through the ICMP pins.

#

I think Ralf just needs to see the state of the EEPROM

#

screenshots might be ok

analog dirge Jan 3, 2024, 11:03 PM

#

ok

#

in that case heres the other nano

safe dock Jan 3, 2024, 11:06 PM

#

that one doesn't look corrupted but if I am counting correctly, I only see seven devices which is hardly worth the trouble of trying to save instead of recreating.

analog dirge Jan 3, 2024, 11:07 PM

#

yea thats the one with a small amount, 2 of the devices was me actually testing mobiflight for the first time, there just left over. i can recreate that one no problem. just not sure what number is the corresponding pin for the input

safe dock Jan 3, 2024, 11:09 PM

#

you can create an all button config for all pins

#

in Mobiflight

#

then as you press the buttons or encoders in the panel, you can see which pins are triggered in the Mobiflight log.

analog dirge Jan 3, 2024, 11:11 PM

#

ok ill try it

safe dock Jan 3, 2024, 11:17 PM

#

or if you prefer to wait for Ralf and see if he has another solution.

#

Please save your devices to a mfmc file from now on.

#

If you had that file, you can just factory reset the board, reload the firmware and reload the devices.

analog dirge Jan 3, 2024, 11:21 PM

#

ok i will def save them lol

#

i just finished setting up one of the nanos

#

all the buttons are working as they should now

#

so

#

now its just the other 2

analog dirge Jan 3, 2024, 11:23 PM

#

analog dirge i got this out of one of my nanos

im going to see if i can get anything out of this one

strong swan Jan 3, 2024, 11:24 PM

#

that would be very helpful

#

we don't understand why this happened and the information from the eeprom might give us a hint

#

both dumps are ok

#

they show a problem

analog dirge Jan 3, 2024, 11:27 PM

#

oh whats the problem?

strong swan Jan 3, 2024, 11:28 PM

#

i will have to take a look at the firmware code together with Ralf - the serial number and the device configuration information overlap in the first dump

#

so how many are still not recognized correctly?

#

can you please keep one of them bricked? so that we might be able to test something and recover most of the info?

#

i understand you want to use your cockpit again. Maybe you have a spare nano and can swap it out

analog dirge Jan 3, 2024, 11:31 PM

#

i did just buy 2 new nanos, i can try sawpping them. i would need to take my panel appart first

analog dirge Jan 3, 2024, 11:31 PM

#

strong swan so how many are still not recognized correctly?

one nano wont let me upload the sketch, however they all show up in mobiflight

#

one of them i just finished remaking the config for, one is still empty and the other i cant run the sketch

#

i can leave the empty one empty if you would like

strong swan Jan 3, 2024, 11:37 PM

#

can you dump the eeprom from the one that still shows empty?

#

or is that the first dump

strong swan Jan 3, 2024, 11:38 PM

#

analog dirge i got this out of one of my nanos

i mean this one

analog dirge Jan 3, 2024, 11:38 PM

#

analog dirge i got this out of one of my nanos

this one still shows empty and the other one wont let me upload the sketch

analog dirge Jan 3, 2024, 11:38 PM

#

strong swan i mean this one

isnt that the eeprom?

strong swan Jan 3, 2024, 11:40 PM

#

if that's the eeprom dump from the one where you have not recreated the config yet - perfect

#

i just wanted the confirmation

analog dirge Jan 3, 2024, 11:42 PM

#

yea no problem, i was finnaly able to get the back off the panel so if you would like i can try swapping the nano that wont upload with a brand new one

safe dock Jan 3, 2024, 11:48 PM

#

strong swan if that's the eeprom dump from the one where you have not recreated the config y...

I can confirm the same type of corruption, where the device config data invaded the board name and serial number area of the EEPROM, happened to me once about a month ago.

#

I just cleared the EEPROM, reloaded the firmware and reloaded the config.

#

I am guessing Mobiflight only writes config data when uploading a config to a board, so somehow the starting address is not correctly set.

#

from my adventures exploring the EEPROM, it seems to me the starting address for the device config is a fixed offset (decimal +60), so the firmware knows where it needs to start writing. How can this be somehow lost?

strong swan Jan 3, 2024, 11:58 PM

#

there was a short period when we tried to use the microcontroller info for the serial

#

it turned out the IDs were not unique

#

we changed it back to the old style - i wonder if it has to do something with that.

#

the offsets in the eeprom where name, serial and config are starting haven't changed in years

#

i will do some digging tomorrow with Ralf

cinder heron Jan 4, 2024, 5:38 AM

#

OK, it seems that the EEPROM is not corrupted and I know what happens. But for know I don't know why this happens.
On detection for new boards, which is done in the serial generation function, 0x00 is written to the first Byte of the Config within the EEPROM. This avoids sending multiple 0xFF which is the original content of an EEPROM. It seems that exactly that happens. As it is very seldom I guess it happens when coming from the UniqueID.
We habe two different ways:

Setting up a sketch which writes a "1" to the first location of the config
Rebuild the config from the ASCII dump. It might be easier, but then I need the ASCII dump like in the screenshots from all 3 affected Nanos. And not as a screenshot but as copy and paste into a .txt file.

#

@analog dirge As I understood you have still two Nanos w/o the config, one of them the dump sketch is running and the other one not.
I guess the difference is the old and new bootloader. This has to be choosen in the Arduino IDE.
Which of the screen shots is the missing config?

cinder heron Jan 4, 2024, 7:27 AM

#

@analog dirge This is the config from the screenshot. Is it correct that "only" 4 Buttons are configured?

📎 MobiFlight_Nano1.mfmc

#

Now we have to dump the EEPROM content from the missing one.

#

The Nano clones (or an old original one) can be shipped with an old bootloader.
This can be choosen as per screenshot:

#

If you already tried this, switch to ATmega328P (w/o (Old Bootloader))

#

But first you have to choose the Nano Board, but I guess you already did this.

#

Once you uploaded the screenshot I can create the config file.
Better would be to mark the output with the mouse, copy it and paste it here

#

This part is from interest, everything until the special characters appear

cinder heron Jan 4, 2024, 9:01 AM

#

This is the config from the second Nano, not sure if you have already restored him.

📎 MobiFlight_Nano2.mfmc

#

And what I have written above I am not sure anymore. It seems that something other has happend to the EEPROM, but can't figured it out...

cinder heron Jan 4, 2024, 10:12 AM

#

@analog dirge Sorry, one more question. Which was the last version from the connector you have used before updating to the new version. Or do you in which month you did the last update?

analog dirge Jan 4, 2024, 11:52 AM

#

cinder heron <@726517030853017651> Sorry, one more question. Which was the last version from ...

The last version I used before updating to v10 I believe was 9.7.1 and I updated around 20 minutes before I originally made the post

analog dirge Jan 4, 2024, 11:53 AM

#

cinder heron This is the config from the second Nano, not sure if you have already restored h...

This one I did restore using the EEPROM

analog dirge Jan 4, 2024, 11:54 AM

#

cinder heron <@726517030853017651> This is the config from the screenshot. Is it correct that...

There are 4 buttons however there’s also a 7 segment display connected as well as 2 rotary encoders

analog dirge Jan 4, 2024, 11:57 AM

#

cinder heron But first you have to choose the Nano Board, but I guess you already did this.

I can do this when I get home, on my way to school rn lol. I’ll ping you when I have it or if I’m still having trouble

cinder heron Jan 4, 2024, 12:20 PM

#

analog dirge The last version I used before updating to v10 I believe was 9.7.1 and I updated...

I mean before this update. But 9.7.1 helps too!

analog dirge Jan 4, 2024, 2:07 PM

#

If you mean before 9.7.1 then it was 9.6.0

#

Sorry if I’m misunderstanding you

analog dirge Jan 5, 2024, 1:50 AM

#

@cinder heron hey i was able to get the EEPROM off the last nano. you were right, i needed to use the old bootloader

📎 EEPROM.txt

cinder heron Jan 5, 2024, 7:33 AM

#

analog dirge <@818484383606243342> hey i was able to get the EEPROM off the last nano. you we...

Attached id the config file for Nano3.

📎 MobiFlight_Nano3.mfmc

#

For the Nano 2 it seems that there are two additional Buttons, but I am not sure:

Button 3 but I can't see on which Pin
2)Button 1 on Pin 10
The EEPROM content is very strange, never seen this before and we have no clou how this could happen.
The only chance is to rerun the eeprom dump if you haven't already uploaded the new config. Maybe something went wrong while printing the content.

analog dirge Jan 5, 2024, 8:22 PM

#

cinder heron Attached id the config file for Nano3.

thanks!

analog dirge Jan 5, 2024, 8:22 PM

#

cinder heron For the Nano 2 it seems that there are two additional Buttons, but I am not sure...

ok ill try re-dumping nano 2

#

i havent uploaded anything to it yet

#

0 == #MobiFlight Nano2Button 3:1. 32 == 10.Button 1: SN-4FE-F44.2.3 64 == .4.15.1.HDG and SPEED:8.5.6.1.SP 96 == D:8.7.8.1.HDG:1.9.SPD Select:1.1 128 == 0.HDG Select:1.11.SPD Managed:1. 160 == 12.HDG Managed:⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮

#

this is what i got out of the second dump from nano 2

#

you know what interesting, nano 3 is showing up as compatable now. i wonder if thats because the sketch is on it instead of the mobiflight firmware

#

just tested, the nano 3 config works :D

cinder heron Jan 6, 2024, 12:43 PM

#

analog dirge `0 == #MobiFlight Nano2Button 3:1. 32 == 10.Button 1: SN-4FE-F44.2.3 64 == .4.15...

It's the same as before, so I can't do more as I have provided/sayed (two more buttons as in the config I have uploaded) before.
Sorry for this!

analog dirge Jan 6, 2024, 12:54 PM

#

That’s alright, I could just trial and error it until something works lol

analog dirge Jan 6, 2024, 5:16 PM

#

hey it works!

#

thank you guys so much for helping me with this

#

all 3 nanos are working again

cinder heron Jan 6, 2024, 5:39 PM

#

analog dirge all 3 nanos are working again

Glad to hear this

#Almost all my configs are gone after updating to V10.0.2