ElectricMotorcycleForum.com

Chiming in with the same message. The resistance of these batteries are in the milliohm range.
Every bit of preparation matters.
Do the work of making sure the voltage is as close to the monolith as possible at connection.

Like Specter said, i think the reason why you won't get a lot of response on this topic is that it is quite dangerous if you don't know what you're doing. The existing packs are potted, so repairing them isn't really an option. recreating with newer tech is the only point where it's possible to do something, but the requirements to get there is quite high.
I am about to embark on a project close to what Specter did, but my battery will have a system voltage of 495 volts. the problem of arcing and killing you increase quite a lot at this level, but then again, i AM certified.
That said, trying to build a pack that will be in movement and able to handle this level of vibration and shock? eh.. it's not the first battery build i would try to do.. :/

Thank you Specter.

I take it you're referring to the 100% section i wrote about.
It's actually not the mA's left to cram into the batteries that is the issue there. It's the way it behaves. ..And since i am a sucker for a good UX, i tend to drill down into those kind of issues..
The charge mode works in 3 (4) modes; bulk, absorption, float and complete. Keywords well familiar in the world of solar.
At the top, the charging process tapers off naturally, and as it stands right now, it never goes from "bulk" stage to any other stage, meaning it's the BMS taking care of it all. I prefer to have better control. The BMS is the fallback protective device (in my eyes at least).
I have been noodling some ideas i will test out whenever i am back at the computer at home to change this. I want to make this controller into something that both works as on-the-go and as a set-it-and-forget-it type of system for when it's at home.

Today i got to test it on a Easee chargerobot, and that gave me a new list of bugs to tackle, so.. yeah.. fun times!

Thanks
I have been to Haugesund. It's far away from where i am, but a very nice (yet windy) city.

Apart from what i wrote in the Readme on the github page, i haven't written much documentation apart from what is commented in the code.

There was no need to do I2C or UART on this.. The link i have is for transferring DC Power and CAN bus data.. There's also a few pins in reserve for some future plans i have.
I was aiming for a connector setup because i am still developing the PCB, and i know i would want to extend its functionality from DC+CAN bus to also do EVSE charge pilot signal processing. - and then be able to just do a swap-out type of upgrade. keeping it easy for the user to choose/upgrade..

Hi

So, first off, all homage to skonk's amazing work in this thread: https://www.electricmotorcycleforum.com/boards/index.php?topic=13489.0
It is the springboard that sent me down the rabbithole of building upon his work.
I had several reasons for doing so..
- Hardware - that arduino + 3 layers would never fit my bike within the range of the bike's cable connector.
- More web control
- added support for HomeAssistant

What i made is exactly what i sought out to create.
DISCLAIMER: I used and still use Claude AI as i am NOT as proficient a coder as i would've loved to be. I do however have experience as a project manager and a product developer as well as being an electrical engineer.
I mentioned in the thread i referenced above that i had already made something there. I ended up discarding that one and restarting from (almost) scratch.
So.. I took the header files from skonk's project and restarted a new arduino project using a LilyGo T2-CAN unit as it is both 2 isolated CAN bus transceivers as well as a beefier processing unit.
In addition it handles 12-24VDC input, so i could skip one of the PSU's from that project, keeping this even more lean.

Anyway.. I am _almost_ ready to post my new version. it has taken the better part of my life these past few weeks, but it's finally functioning well enough that I'm doing cosmetic fixes..
So.. Here's some screenshots for you:
First iteration i made.. Quite heavily dependent on AI (but i did like the lowkey design of it):



This one kinda reveals i'm not a native english speaking user.. 





Still..
I went back to the design board rather than relying on adaptations of others.
I wrote myself an overview of functionality, and began building the thing from scratch. (+ those previously mentioned header files)
I built it section by section and bugfixed them as i did before continuing onto the next "module".
It is not "perfect" yet.. But what i have now, supports 1,2,3 and 4 chargers (because i had already controls at home to decide how many chargers to energize)
I made it possible to read the different CAN addresses Elcon chargers have, so it would be possible to get data from all 3, before i figured out they are all set up with the same ID.. As such, it's currently set up to just take the static setting in the screenshots instead and i made that a setting to adjust from HA so i can tie that in to possible automations from HA.
I wanted both coarse and fine adjustment control of the chargespeeds, so the slider seen below adjusts on a per 100w increment. Btw, the slider adjusts to the number of chargers you tell it is available.

And so for the people that think AI just ruins everything:
I have security audited this app and tightened controls and functions to a fairly high level. I know nothing is airtight, but security is not without thought here.

Some screenshots:





Oh, and also.. This platform handles OTA updates so i don't have to go out in the garage with the laptop every time i had to upload a new version (and there were A LOT of versions) as well as doing logging to the web so i could look at debug pointers. stuff i can clean up before publishing..

Next on my roadmap is designing a companion pcb for the bike/psu part for those that don't have the tools to build their own.
I'd also like to make a pilot signal pcb/module so it conforms to that part too, but that would require a lot of designing, so it's not first on my list..

Because i wanted more.
And i wanted hardware that took up less space. this way it is contained onto 2 pcb's.

nice

thank you! 

This thread should be in the unofficial manual because it seriously saved me trying to figure out how to assemble the throttle again.
Thank you @Demoni, that video was a godsend!