AvinoxRide Update 📲 v1.4.0

[Seleuco]

Could you please share the outcome?


Did you spot anything? E.g., is it easy to accidently damage that cable during factory installation?

To be honest, after reading all the feedback here on the forum and in other groups, I am really not keen on having the dealer drop the motor and dismantle the bike for nothing.

I've decided to cancel tomorrow's workshop appointment and give it about a week. I want to see if they finally admit it's a software issue and a 'magic' firmware patch suddenly appears.

I am also still waiting for Amflow Support to get back to me regarding the display logs I uploaded for their engineering team. I'd much rather wait for their official log analysis before letting anyone touch the hardware or mess with the Y-cable. I'll keep you guys updated if they tell me something new about the logs

 

[beutelfuchs]

understandable. Thank you.

 

[richy]

Note this is NOT related to this update, but wanted to point out i had one of the errors mentioned in here 6 weeks ago, first ride after applying an older update.

Happened mid ride and didn't feel like the power was restricted, just showed 0 battery but all else functioned until I got home - 'fixed' with the classic off and on trick, and never had it show again.

Was going to take it in to LBS but glad i didn't as it was clearly a bug or something.

 

[Seleuco]

Note this is NOT related to this update, but wanted to point out i had one of the errors mentioned in here 6 weeks ago, first ride after applying an older update.

Happened mid ride and didn't feel like the power was restricted, just showed 0 battery but all else functioned until I got home - 'fixed' with the classic off and on trick, and never had it show again.

Was going to take it in to LBS but glad i didn't as it was clearly a bug or something.

View attachment 187340

That is exactly what happened to me!

That 'lost communication/0 battery' issue was the very first error I got mid-rid after applying last firmware update. The difference is that in my case, after doing the classic 'off and on' trick to fix it, that is exactly when the 0x27030021 'unofficial battery' error started popping up randomly and completely locking the motor.

 

[beutelfuchs]

If I'd have to guess I'd assume they have some CAN communication error states which they are not handling well yet.

 

[Seleuco]

If I'd have to guess I'd assume they have some CAN communication error states which they are not handling well yet.

Whether that's the actual technical root cause or not, we can only guess. But what is completely unacceptable is the absolute lack of official communication from Amflow/DJI.

It is bad enough that they keep us users in the dark, but they haven't even notified their own dealers! The local bike shops have no idea what is going on with this firmware update. They are basically left to deal with frustrated customers on their own, while Amflow Support officially tells them to waste time on useless hardware replacements (like dropping motors to swap cables).

If they messed up an update, they need to own it, be transparent, and send an official service bulletin to the shops immediately so everyone is on the same page

 

[beutelfuchs]

Agree. The fact that they have not done so could point to that only a small number of users are affected atm. Probably only the new motor generation., a subset of those bikes, only people why looked for the last updates and applied them. For some of those the error disappeared after the 2nd update. Some are just re-starting the bike and move on...

So, time and more reports will hopefully force them to take it seriousely.

 

[Pyr0]

Unfortunately, I didn't have time after work last night.
Hopefully this evening

 

[Mlok]

If this is clearly a software bug because they screwed up trying to block third-party extenders, why are they officially instructing us to check or replace the Y-cable? Replacing that cable means dropping the whole motor, which is a massive amount of unnecessary labor and a huge hassle for the dealers!

This is indeed a block on non-original batteries.
I have Rotwild R.EX 900. It has not original, but Rotwild battery (but officialy with Avinox support). After update (friday) I ended up with errors: "Communication Error Between Motor and Battery" and "Non-Official Bike Battery".
I immediately reported it to my Rotwild dealer and directly to Rotwild's customer support.. My Rotwild dealer already had information (email) from Rotwild since Friday morning. Unfortunately, he didn't read it before I had already performed the update.
Rotwild has been working with Avinox on the repair since Friday.
Yesterday I received an email from Rotwild saying that Avinox had been resolved the problem.
Yesterday Avinox released a new version of the app AVINOX app 1.4.1(6178), but only available via direct link for manual instalation. Probably it is a version only for install update for Rotwild without checking the battery charge (standard update is not possible with battery under 10% and with this error comunication with battery it shows 0% battery).
I haven't had a chance yet to see if the problem is really fixed, because I'm on vacation—I left on Saturday and brought my older e-bike with the Brose motor.
So far, I've only successfully installed the new version of the app; I won't be able to try the motor firmware update until I get back from vacation.
The FW repair was quick, but unfortunately it happened right before I was about to leave for vacation.

 

[John_likes_bikes]

These might be small, one-off cases but there have been issues with updates in the past. I think I've learned that unless an update is significant there's really no need to perform one. At least immediately after release.

 

[Seleuco]

This is indeed a block on non-original batteries.
I have Rotwild R.EX 900. It has not original, but Rotwild battery (but officialy with Avinox support). After update (friday) I ended up with errors: "Communication Error Between Motor and Battery" and "Non-Official Bike Battery".
I immediately reported it to my Rotwild dealer and directly to Rotwild's customer support.. My Rotwild dealer already had information (email) from Rotwild since Friday morning. Unfortunately, he didn't read it before I had already performed the update.
Rotwild has been working with Avinox on the repair since Friday.
Yesterday I received an email from Rotwild saying that Avinox had been resolved the problem.
Yesterday Avinox released a new version of the app AVINOX app 1.4.1(6178), but only available via direct link for manual instalation. Probably it is a version only for install update for Rotwild without checking the battery charge (standard update is not possible with battery under 10% and with this error comunication with battery it shows 0% battery).
I haven't had a chance yet to see if the problem is really fixed, because I'm on vacation—I left on Saturday and brought my older e-bike with the Brose motor.
So far, I've only successfully installed the new version of the app; I won't be able to try the motor firmware update until I get back from vacation.
The FW repair was quick, but unfortunately it happened right before I was about to leave for vacation.

Thanks for sharing this! It actually explains a lot about what DJI was trying to do with this update, but our case with the Amflow bikes is slightly different.

Since we are using the original Avinox batteries, we don't get that permanent 0% battery bug. Our bikes do read the battery charge correctly most of the time, but the system just randomly triggers the "Non-Official Battery" error and cuts the power. Because our screens still show the actual battery percentage, we wouldn't even need that special 1.4.1 app to bypass the 10% update restriction. We can update normally through the standard app.

The real problem for us Amflow owners is that there is simply no firmware fix available for us yet. The latest firmware update with the supposed "bug fixes" did absolutely nothing to solve this issue for us. It seems DJI quickly patched the communication protocol for the Rotwild batteries, but they left their own Amflow bikes dealing with this over-sensitive CAN bus error. We are still stuck waiting for a real firmware fix!

 

[mikeywilcox]

The latest firmware update with the supposed "bug fixes" did absolutely nothing to solve this issue for us.

I totally support community complains on Amflow support but i can’t agree with your statement. They fixed dead SIM connectivity at least. Still waiting for battery fix and corrupted recorded tracks.

 

[Seleuco]

I totally support community complains on Amflow support but i can’t agree with your statement. They fixed dead SIM connectivity at least. Still waiting for battery fix and corrupted recorded tracks.

Ah, you misunderstood my point! I wasn't talking about the SIM at all since that doesn't really affect me.

When I said the update 'did absolutely nothing', I meant specifically regarding the random 'unofficial battery' error, which is the main issue we are trying to figure out in this thread. I am glad they at least fixed the SIM connectivity for you guys, but man, what a complete disaster of an update overall. Let's hope they release the actual battery fix soon.

 

[Seleuco]

Hey everyone,

I just read an article from a Czech e-bike blog that absolutely nails this whole mess and completely confirms our CAN bus timeout theories.

Honestly, the timing of this is so hilariously bad that I’m starting to think an undercover Bosch engineer infiltrated DJI’s software team just to hit the "deploy update" button right before Eurobike.

Here is a quick summary of what the guy points out:

• The Eurobike PR Nightmare: Eurobike literally starts today. DJI was planning a massive show to crown the Avinox as the new king of e-MTBs. Instead, their software department is probably sweating blood right now trying to patch this so their demo bikes don't throw a 0x27030021 error in front of all the journalists.
• The Amflow Irony: He points out the ultimate joke: Amflow is DJI's own in-house baby, yet we are the ones getting screwed the most. The author actually rides a Crussis bike with an Avinox motor, did the update, and is riding with zero errors. DJI basically crippled their own flagship fleet while third-party frames are fine.
• "Drone Paranoia" Confirmed: He confirms exactly what we suspected. DJI brought their strict drone DRM into the e-bike world to block third-party extenders. They made the CAN bus communication so hypersensitive that any micro-delay—whether on boot-up or taking a hit on the trail—makes the system panic and cut the power. A premium motor paralyzed by overzealous code.
• Voodoo Workarounds: He lists the same temporary fixes we’ve been doing: unpairing/repairing the app to force a new server authorization, and the "5-minute rule" (leaving the bike off for 5 mins to completely drain the capacitors and force a clean BMS handshake on the next boot).

At least the Eurobike panic means they are definitely rushing a real hotfix right now to save face. Let's hope they drop it soon so our dealers can stop tearing our motors apart looking for ghost cable issues!

Když aktualizace nepozná vlastní baterii: Avinox si uřízl ostudu těsně před Eurobikem - avinox.cz

Dnes oficiálně startuje největší cyklistický svátek roku – veletrh Eurobike. DJI tam má s Avinoxem políčeno na obří show a...

www.avinox.cz

 

[John_likes_bikes]

Are the issues with the latest update mostly/only with Amflows? Anyone with another frame having issues? I'm holding off updating my Crestline.

 

[beutelfuchs]

I had it on the new Forbidden Druid after the first update. After the second update I had it one more time and since then I can't reproduce it anymore.