XR Error 16 (repaired)
-
@samuraipunch No compiling needed, copy and paste the 1.3.0 firmware bin in the esp8266 flash tool.
bin-https://github.com/lolwheel/Owie/releases/tag/v1.3.0
tool-https://www.espressif.com/en/support/download/other-tools?keys=&field_type_tid[]=14 -
@lemur Oh wow, that's new... I knew originally that you had to build/compile it to flash it... Maybe something changed with the licensing/github to allow it to be ready to flash, or they decided to just ship it ready to flash. Haven't really been paying attention to OWIE since i left the OW discord.
-
@samuraipunch I guess what I care about is error 16. Can I trust owie to not randomly throw me onto my face on the concrete?
-
@swinefeaster I'd say yes, it's the better and less expensive option... But that's assuming you really don't have harness damage... If you do it doesn't really matter which option you go with.
Although if it's straight dropping you and the board is off when it does, it'd suggest that the error 16 is really a stop-gap in saying something else is going wrong, like your BMS could be dying. As OWIE and FFM are piggy backs and modifying the signal to the controller, and with them the signal is manipulated enough to trigger the error, where sans chip the signal is still on the "ok" side. Not saying that your BMS is dying, but that the chips are manipulating the signal, so there could be some component overall that's failing or resulting in an out of spec signal/value when processed resulting in the error 16.
It's one of the reasons why you may hear of "i left board charging for a really long time and now it's dead" stories. Board charging = board on... so it's non riding electrical component wear time.
-
@samuraipunch said in XR Error 16 (repaired):
Not saying that your BMS is dying
im not qualified but i am opinionated, n i think this is a sound conclusion. power is failing randomly n the bms provides it, correct? neither owie, nor ffm could solve that particular issue, which also describes his problem to a tee: intermittent power loss.
-
@notsure Very possible, I could be wrong on this, where you could "zombie" an XR to work without a BMS, but if it was doable it was on 4208 or earlier... but one of the things we may be overlooking is that it's also a more recent board that needs a chip... Who's to say that maybe it's an issue of chip installation, and a wire/solder joint to the chip and plug isn't bad... And that during riding vibrations are enough to cause an interruption at the chip.
Although I've always been of the mindset of "battery mod = no use app, and no updating app"... Which is why the app i have installed on my phone is for a pre-group ride and pre-achievement version... Who's to say what "bug fixes" are being released to combat battery mods via the app. Even though it's not a "firmware", board behavior can be adjusted and influenced by the app. So with the app open, it's very possible that some data is being sent to the app from the board, and the app interprets something in that data stream as a behavior FM doesn't approve of, and tells the board it's time to throw an error; resulting in yeeting the rider.
-
@samuraipunch said in XR Error 16 (repaired):
So with the app open, it's very possible that some data is being sent to the app from the board, and the app interprets something in that data stream as a behavior FM doesn't approve of, and tells the board it's time to throw an error; resulting in yeeting the rider.
their management may lack scruples, but theyre not the mob lol. an application layer diagnostic that communicates with the firmware without the user being aware n resulting in injury would be a huge liability. huge! their lawyers would quit.
-
@notsure .... right... like QC and GT are synonomous... I can't even type that in the same phrase without dying of laughter! :D
-
@samuraipunch Unfortunately, no XR model can work without a bms, only the V1, and Plus can be "zombied".
-
@lia said in XR Error 16 (repaired):
I second removing the chip since you've proven the likely intermittent culprits so far
so.... two test rides so far. one very careful ride and one less careful ride, no issues. on the first ride, last night, i rode it down to 1%. what was really odd is that once at 1% (i wanted to test pushback at battery depletion) it took 20 min and about 2 miles of running around my street in circles to get it to actually throw up the need juice warning.
is this normal? or some kind of battery calibration now that the ffm chip is gone?
i also notice that the mile range indicator works too, so the ffm chip was definitely affecting that even at stock.
-
@swinefeaster Usually the percentage should straighten out after a couple of recharges.