Problem with FMC920 Version FW FMB.Ver.04.00.00.Rev.05.e (WARNING @ 333:AXL is not initialized!)

Hi everyone, I’m having a problem with my FMC920. It currently has firmware version FMB.Ver.04.00.00.Rev.05.e installed, and it has stopped working after a month for no reason. The device powers on and connects normally to the PC, but it doesn’t display battery charge data, IO, Accelerometer, or A-inputs, and it doesn’t report to the platform. SMS commands don’t work.

Checking the logs, I find this message:

WARNING @ 333: AXL is not initialized!

I read that the same thing happened to another user, and also that that firmware version is no longer available on the Teltonika website, but it’s also not possible to downgrade to a previous version on 04 devices!

I need help, please. No one has answered any questions about how to solve it.

1 Like

Hi,

Good day, how many devices are affected by this issue?
Do you have contact with your sales manager or access of Helpdesk? Please contact your sales manager and add the device logs, IMEI, number of devices, configuration file. etc

Best Regards
Maynard C

@francofazi1

Kindly try to update the firmware of your device to 04.00.00.rev.09

Here is the link: Teltonika Drive

Best Regards
Maynard C

I’ve already contacted my provider but haven’t received a response yet. I tried updating to version FMB.Ver.04.00.00.Rev.09_ID1.e but I get the following error:

Do you think you have another firmware version to try? Is there any way to go back to a previous firmware version?

Hi @francofazi1

Do you have contact with the teltonika support?
It should be updated remotely using the flashtool.

Best Regards
Maynard C

I’ve only been contacted via WhatsApp by a representative in Chile, the closest to Argentina, and they haven’t provided a solution. How can I contact Teltonika support? Can you help me with that? My number is

+5493525620862

Hello,

How many FMC920 units have encountered this issue?
If it is not possible to do the remote flashing you can return the device to us via RMA process

If there are no solutions provided by your sales manager please contact through our official website. https://teltonika-gps.com/ and click on the “Contact Us” button. When you will click, please fill the form and submit it.

Best Regards
Maynard C

Hi,

I raised the same issue in a separate topic and after almost a month I still haven’t received a solution. The provider has not yet provided a solution to this problem.

I tried to test with the version you provided here, but unfortunately I got the exact same error.

According to my last check, more than thirty devices with this version have encountered this problem, and the number of these devices is increasing every day.

Hi @bmehrabani

Please contact your sales manager for the RMA request, or create an HD ticket.

Best Regards
Maynard C

Yes, I had read your problem on this forum, and that’s what made me think it was a general issue and not just with my device. Honestly, I’m discouraged that you haven’t found a solution after more than a month. It makes me think I’m on a path with no solution other than RMA.

I’ve also tried changing settings for GPRS validation, connection attempts, and other things my provider suggested. I also tried updating the firmware versions through my provider’s Photo Web (a version prior to and a version later than the one with the problem) and was unsuccessful. I don’t understand why @Maynard can’t tell me what the problem is here.

1 Like

@francofazi1 @bmehrabani

Good day, it can only be fixed by flashing the firmware 04.00.00.Rev.09_ID1.e
It can be done remotely, you can check with your sales manager to request for the support.

Another option is to send the device via RMA.

Best Regards
Maynard C

Hi @Maynard ,

Devices installed on cars and moving on the roads. The possibility of coordinating for a specific time for remote flashing seems impossible.

Do you have a schedule for the release of the new and official version 4 on the website? So that we can manage and solve this issue ourselves according to local conditions.

Hello @bmehrabani

Currently, the only solution is to flash the device and update the firmware to 04.00.00.Rev.09_ID1.e or via RMA.

If you have devices that are currently working with the firmware 04.00.00.Rev.05, please update it to 04.00.00.Rev.09_ID1.e to avoid these kinds of issues.

Best Regards
Maynard C