openinverter forum

arber333 wrote: ↑Thu Sep 29, 2022 2:31 pm Hm... no i tries that already and it just stoped charging. No tapering of current... this is why i wanted to setup tapering.

Do you think i should setup greater difference? As in 390V for charge and 394V for max?

That should work better. I believe the max is also so the EVSE knows how high the pack can go to ensure compatibility (2.0 supports 1000v ish).

Nope that doesnt work. Today a lot of evse on my way to Split just stopped charging when reached 390V battery voltage. I havent observed any throttling of the amps.
Perhaps we could add another voltage parameter to form a knee where CV would start? Since Umax is never reached Ut means evse stops, maybe Ucv would directly vary request until Imin? Isaac could you try to change the code since you know what you are doing?

Tnx

Currently awaiting recovery tried multiple chargers and now too empty to continue, getting recovery home instead of desired destination so I'm not stuck again

Charging starts then immediately stops with no apparent reason.

Bigpie wrote: ↑Sat Oct 08, 2022 1:07 pm Current awaiting recovery tried multiple chargers and now too empty to continue, getting recovery home instead of desired destination so I'm not stuck again

Charging starts then immediately stops with no apparent reason.

Dang! I was good with Chademo stations all the way to Split.
The same happens to me at Delta chargers. I suspect bad CAN bus termination. I am thinking of taking VCU board 60R resistor out and extending chademo twisted pair. Then i qould fit one 60R resistor into the end connector. Maybe i could then more easily connect to this line for listening...
But this would mean i have to take apart everything... maybe now that i have to refit my battery i can also do this job.

I'm not sure what the problem could be, it was communicating properly from what I can tell with the log file, the current request ramps up then it just stops at 4 amps.

Bigpie wrote: ↑Sat Oct 08, 2022 1:24 pm I'm not sure what the problem could be, it was communicating properly from what I can tell with the log file, the current request ramps up then it just stops at 4 amps.

Does it report error code in charger display?
What if your ISA reports positive current? It happened to me before. EVSE would start but then stopped as if ISA would report system is driving...
I have made some changes to my code and it works good at least on most chargers.
I added option to reverse voltage and current sensing.
I also inserted Nissan leaf instructions and IDs for V2X.
You could reflash your DUE board with my changed code

Man that sucks Is this problem on chargers you've used before? I've been meaning to post about this, I had modify your board so there is a voltage divider on in2. in1 and in2 are connected to contactors/ pins 2 and 10 directly. I then just had out2 on my bms cutout. I think the circontrol station near me must need to see a load on pins 2 and 10.

My in2 has an external pull up no voltage divider' it gets pulled to ground.

Didnt have can logging with me unfortunately.

Was the same BP units that I've used else where, same goes for the instavolts. Not used these specific ones.

Will go to my local BP tomorrow with can logging and get some messages.

The inputs and outs are working, the contactors closed, the current request starts ramping up, the supplied current starts to ramp then the charger errors out.

Still an issue today so grabbed a log

Looks like the voltage seen goes up to ~340v but doesn't drop back below 20v before staring the charge.

Looks like I've blown an input pin, IN2 is being constantly pulled to ground, the contactors are closing too early. Need to redesign to add input protection I guess.

Bigpie wrote: ↑Tue Oct 11, 2022 8:12 am Looks like I've blown an input pin, IN2 is being constantly pulled to ground, the contactors are closing too early. Need to redesign to add input protection I guess.

How is that possible. Isnt it pulled low? A transient on the EVSE line?
Could be that a small 3V6 zener diode would save your problem. You connect upper side to your pin and the other to GND .
I would have to think on that for my VCU too...

Not entirely sure, transients or ESD? Zener going on and hoping Might have to carry around a gas soldering iron to quickly change to another pin

Bigpie wrote: ↑Tue Oct 11, 2022 9:01 am Not entirely sure, transients or ESD? Zener going on and hoping Might have to carry around a gas soldering iron to quickly change to another pin

Hm... In my new V6 version i have plenty of 10K pulled up inputs so i might just choose a new wire and reconnect .
But that is how i was dealing with burned IGBTs in 2016! Each year a different set replaced until i used desat drivers which solved the issue for good.
Hope for the best aint a tactic! I strongly suggest you add a zener or TVS protection on each input so it cant be overloaded easily.

EDIT: look at me preaching while i dont actually have zeners mounted....any day now.

Ordered an updated pcb with zener diodes and some other fixes. All working again on a new pin . Only thought ive had is somehow the pin went to output?

arber333 wrote: ↑Sat Oct 08, 2022 1:20 pmI am thinking of taking VCU board 60R resistor out and extending chademo twisted pair. Then i qould fit one 60R resistor into the end connector.

CAN should be terminated by one 120 ohm resistor on each end - not the 60 ohm. One is in the CHAdeMO station, the second should be on the CHAdeMO controller.

im working on installing chademo in my brat. i have an stm32 board "isa fc vcu v2" from damien, seeing the issues people have had with them, and all the little developments, i started a wiki page after gathering all the info from this thread.

https://openinverter.org/wiki/Chademo

dump info into it if you can.
regardless of board/software

I've rebuilt my HVJB and hopefully addressed the issues I had, but likely won't be able to test until sometime next spring when I've finished replacing axles in the car. I'll report back then on whether the changes worked, and what they were.

@arber333 did you ever get anywhere with the tapering?

Bigpie wrote: ↑Fri Jan 13, 2023 1:55 pm @arber333 did you ever get anywhere with the tapering?

Nope, i tried from the code but it just ignores me.
I could try to set different amps... will try tomorrow.

Yesterday i removed the box from under the car and set it up for testing from the trunk.

1. i removed ACDC converter and connected 12V directly from the car. There were issues on some EVSE when they declared isolation problem.

2. I tried to rewire my CAN bus lines. Strangely when i switched wires CAN L/H on some EVSE (Delta) i got "CAN no communication" error and on some (ABB) it charged correctly. Go figure...

Can anyone share their own details on how they formed CAN bus twisted pair from Chademo socket to Leaf(chademo) VCU? Do you have any data on how OEM twist their wires? I try to keep to some convention and i usualy twist my wires from left to right looking at a right hand perspective - thumb up.

re stm boards: im not getting any prams on the web interface.... supposed to use the generic open inverter interface correct?

Not used the STM32 board, but usual thing to try it hookup TTL to USB and look at the serial output instead of the esp8266. If it's just printing endless 2F2F2F... it's not running the firmware successfully

hmm just noticed the STM32 gets quite warm once the board is powerd on

Bratitude wrote: ↑Fri Jan 27, 2023 8:32 pm re stm boards: im not getting any prams on the web interface.... supposed to use the generic open inverter interface correct?

I too have the ISA FC VCU V2 and just got some blinking leds, esp8266 wifi hotspot is working, but no params.

I used st-link to send this to the board.

https://github.com/damienmaguire/Chadem ... hademo.hex

On the esp8266 web page I found I have SWD error when I try to update firmware that way.

And after reading through this thread "again" I see I have some BSP75N that I need to change to the NCV8402 too huh..? Damn I just ordered stuff from mouser anyone got spare 3 in EU?

JaniK wrote: ↑Thu Feb 23, 2023 7:48 pm

I too have the ISA FC VCU V2 and just got some blinking leds, esp8266 wifi hotspot is working, but no params.

I used st-link to send this to the board.

https://github.com/damienmaguire/Chadem ... hademo.hex

On the esp8266 web page I found I have SWD error when I try to update firmware that way.

And after reading through this thread "again" I see I have some BSP75N that I need to change to the NCV8402 too huh..? Damn I just ordered stuff from mouser anyone got spare 3 in EU?

where is it saying the swd error?

is your stm32 getting warm once the board is powered on?