openinverter forum

johu wrote: ↑Tue Mar 05, 2024 7:35 am Yes I will work on the software again, currently focusing on ccs.


What's the purpose of this sentence? Another translater bug?

Ok maybe leave a quick note if text is translated so it's not taken too literal

I wrote that it is probably not difficult to save my Can cards in the new firmware version.This is a useful option for everyone)))

Hey Johu,
any recommendations on a suitable wire-to-board connector for the 17pincell tap connection?
I've looked on JLCPCB and LCSC but neither seem to have something suitable to my inexperienced eyes. what is the max voltage rating required? do they need to be 400V rated or not?
failing a wire-to-board connection, what is the recommended alternative? I'm going to get JLCPCB to solder the boards up completely rather than mess up the boards with my sloppy soldering!
thanks

The max voltage per board is about 70V so I don't think that is any constraint. I used some sort of Molex connector. Couldn't really find that at JLC but there should be some sort 0.1 inch available.
I don't recommend wire-to-board because you don't want 17 live wires dangling about when disconnected

johu wrote: ↑Sun Apr 28, 2024 8:46 pm The max voltage per board is about 70V so I don't think that is any constraint. I used some sort of Molex connector. Couldn't really find that at JLC but there should be some sort 0.1 inch available.
I don't recommend wire-to-board because you don't want 17 live wires dangling about when disconnected

Ok I may have misunderstood what wire to board is, I was thinking it would be a connector from the battery harness to the PCB. Yes I'm struggling to find something for the 17 pin option on JLC but will look at molex options.

Leo M wrote: ↑Tue Mar 05, 2024 9:09 am I wrote that it is probably not difficult to save my Can cards in the new firmware version.This is a useful option for everyone

Check it out: https://github.com/jsphuebner/FlyingAdc ... 330e883082

There is now separate maps for internal and external use. That way you can map your own messages without disturbing operation. Of course the already used CAN Ids mustn't be reused in the user map.

johu wrote: ↑Thu May 02, 2024 1:15 pm Check it out: https://github.com/jsphuebner/FlyingAdc ... 330e883082

There is now separate maps for internal and external use. That way you can map your own messages without disturbing operation. Of course the already used CAN Ids mustn't be reused in the user map.

and when will there be a release?

Dont we love it when the reaction to an announcement is yet another request You're welcome...

I've added a workflow that builds binaries on every commit https://github.com/jsphuebner/FlyingAdcBms/actions

johu wrote: ↑Thu May 02, 2024 7:12 pm Dont we love it when the reaction to an announcement is yet another request You're welcome...

I've added a workflow that builds binaries on every commit https://github.com/jsphuebner/FlyingAdcBms/actions

I see you have made additional can cards after all, it's very cool. Will there be bin, hex files? Otherwise, there is no lunix at hand for checking now

The plan is, that the bin and hex files are available at the link https://github.com/jsphuebner/FlyingAdcBms/actions
How does this work? Johu configured a "continuous integration job" to the github. This job automatically builds the software and stores the results. Each run is listed on the linked page, the most recent is on top of the list. Selecting the intended job and scrolling down the page to the chapter "Artifacts", there are the zipped bin and hex files.

Отлично! Спасибо Ёханес!