Owie chip standalone
-
@lia You'd want to hit up the ow discord (and ping Adoah) for answers on that to be sure. But I want to tentatively say it'd still be dependent on the BMS, as it's essentially a piggyback, and modifying the signal from the BMS.
-
@lia Unfortunately, the Owie and JW chip only changes the bms signal to the controller, it cannot be used as a stand alone sub for a OW bms. I'm not sure what's happening with your XPint project, but the Owie can pair any Pint bms to any Pint controller. It works because I've tried it and have installed an Owie in my Pint controller box permanently.
-
@lemur Assumed that might have been the case. I'll try pickup a BMS from somewhere at some point. I have an XR BMS still from Dax but I want to use that for the accompanying 4209 controller... when I get around to giving it a body >.>
-
@lia I tried an Xr bms with an Owie to try to pair to a Pint controller, but that doesn't work. Only same platform, Pint to Pint, XR to XR.
I did reflash a 4208 bms to be a Pint bms and that works with an Owie. I've since reflashed that bms back to a 4208. -
@lia I finally got my hands on a friend's 4212 Xr with code 16, turned out to be a harness problem.
Anyhow, I got to test Owie 1.3.0 which has the magic number "428448455" hard code for the bms number and it works to pair the 4212 controller to my 4208 bms.
Thanks to "datboig" on discord for the hard work!
https://github.com/lolwheel/Owie/releases/tag/v1.3.0 -
@lemur Oh Future Motion, you could have at least used "3735928559" for your magic code.
-
@biell Does it mean "unknown error code"?
-
@lemur "4289449455" is "0xFFABCDEF" in hexidecimal. Cute, but "3735928559" is "0xDEADBEEF" in hexidecimal. A value with a storied history.
-
@biell lmao
XR's got what plants crave!
-
This post is deleted!
