I cannot answer that, as it highly depends on so many other factors, Alot of people have had very little issues with reliability in all sorts of installations.
The OE Tesla installation utilizes unshielded twisted cables.
I cannot answer that, as it highly depends on so many other factors, Alot of people have had very little issues with reliability in all sorts of installations.
Is the charged speced to be at 500kbps like the CAB300 sensor? Please turn on canbus debugging to see if the charger is sending any messages on the bus.
So you can see the information from the current sensor at 500kbps? So you know the canbus net work is good?
Of course not, tried the BMS can bus connected to the charger and only the charger, with can sensor disconnected. (bus was terminated)
I do not know how this charger gets its "12V" ground so that might be causing issue. Have you provided the Charger AC power, on the other larger 3kw and 6.6kw as soon as you give it AC power it spits out canbus messages.
I'll borrowed an oscillioscope, so I'll see more... thank you anyway.tom91 wrote: ↑Tue Jun 07, 2022 11:17 amI do not know how this charger gets its "12V" ground so that might be causing issue. Have you provided the Charger AC power, on the other larger 3kw and 6.6kw as soon as you give it AC power it spits out canbus messages.
Possible routes to come to a conclusion:
- Incorrect wiring to charger - try swapping high and low, figure out 12v ground
- Try different canbus speeds, check simpbms canbus works with a known working can devices
arturk wrote: ↑Tue Sep 07, 2021 7:51 pmAwesome, thanks a lot Tom!tom91 wrote: ↑Tue Sep 07, 2021 5:25 pm I have now create new firmware rolling nearly all the changes upto SimpCharge Support into the BMWPhev firmware. This means the IVTS shunts board casting on ids 0x521, 0x522, 0x523 are supported.
firmware found: https://github.com/Tom-evnut/BMWPhevBMS
Please remember to check and redo all settings as this is a major revision. Please feedback any bugs found.
I will report back if I run into any issues.
Karim, Thank you for pointing this out a coding error slipped in. I was calling for the wrong canbus message structure in this version. rxBuf instead of inMsg.buf
I did check the serial debug and there were a bunch of 0s. i can't say i paid a ton of attention to it so far