Hello, I wanted to set up the new ATC panel. I did a firmware update and now everything is gone. I can no longer select the panel in the functions. I can only do a firmware update, but I can't upload any configuration. Can someone help me so that I can use it for the Microsoft A320? The program connected with the flight simulator and I was able to see all the variables it read from the aircraft. It recognized the A320 neo V2. Unfortunately, nothing lights up at all and basically nothing works. Please help me.😕
#Help new Rowsfire A105 RMP+ATC Panel
1 messages · Page 1 of 1 (latest)
Did you install the driver for CH340 serial com chip?
It appears the firmware is gone. Try reloading the fimware. AFAIK, Rowsfire units use Arduino Nanos as their microcontroller, so select Nano type.
Also, you have loaded a Mobiflight profile for the Fenix A320. That will never work with the Microsoft A320 neo v2.
You need a specific profile for that aircraft.
Hello, thank you for your reply. No, I haven't installed the CH340 driver yet. I tried installing the Nano driver, but unfortunately, it didn't work. The Mega 2560 worked. Unfortunately, I can't establish a connection or create a configuration. This is all new to me. However, I did access a variables menu where I could select all the variables for the A320 Neo. I don't know how to create and upload this configuration, though. No LEDs are lit, and I can't select the controller. I somehow deleted the controller, and now the controller type isn't even available for selection. It only says "compatible.
This is not very hard, but it does take some learning. I can only suggest you start at the beginning
https://docs.mobiflight.com/getting-started/
How to start using MobiFlight with flight simulators
A Nano board, won't work with the Mega firmware. You would most likely get an error when loading the hex file.
If it shows as compatible, you can try again loading the Nano firmware.
If that fails, please go to device manager lpt and serial ports and post a screenshot of that window
it should show the Nano serial com port as a CH340 device
I've installed the diver. What's the next step to test and configure my device so that it no longer displays "config" and I can upload a configuration?
It is a mega 2560 board i look inside.
Good to know. I don't have any Rowsfire panels. If you are sure it is Mega 2560, then select that in the firmware upload selection menu.
I performed the firmware update, but there was no change. Mobiflight also cannot establish an automatic connection at startup. This message always appears when starting the program.
It recognizes that a compatible module is connected, but it can't do anything with it.
Mobifight can only establish connection if the firmware has been previously uploaded to the device
Right click on the Compatible board and a menu should open
Does uploading the firmware end successfully?
should show a message box like this
These are the only options available. yes the uploading was successfully.
Select Mega 2560
i did
activate logging in debug level and retry the upload
and it still shows up as Compatible?
same before
did you use the ch340 driver provided by Rowsfire?
no
there are some Arduino chinese clones that have counterfeit ch340 chips. I can't know what your board has, but you could try installing the ch340 driver dated 2019 instead of the default driver installed by Windows for the CH340
the new driver versions don't work with the counterfeit ch340
It worked at first, but I must have done something wrong, and now it doesn't work anymore. Initially, it recognized the board and everything worked. I don't think it's the port because I've already updated the driver twice. I acquired it legitimately; I don't think it's a clone. What else can I do if the chip no longer has the original software?
I am not saying you didn't buy this panel legitimately. FYI, all arduino boards using ch340 are cheaper clones made in China. The original design does not use these ch340 chips.
I myself have a few clones that have the counterfeit chips and require the driver dated 2019.
Maybe someone with this panel can shed some light.
Also you can't hurt anything by trying the 2019 driver. You can always undo it later if it makes no difference.
It worked fine from the factory. I think I accidentally changed or reset something, and now I don't know what the chip needs to be reprogrammed.