I can see this:

2018-04-07 10:34:26.617392 +0800 info  main: #59 A ROADSTER_834 rx msg C 15,15
2018-04-07 10:34:40.025887 +0800 info  main: #59 A ROADSTER_834 rx msg C 15,24
2018-04-07 10:34:45.481678 +0800 info  main: #59 A ROADSTER_834 rx msg C 16,3,10

That seems to be changing charge current to 15A, then 24A, then a change to range mode at 10A.

Response from the car (for the last one) was:

2018-04-07 10:34:45.682460 +0800 info  main: #150 C ROADSTER_834 rx msg c 16,0
2018-04-07 10:34:46.924401 +0800 info  main: #150 C ROADSTER_834 rx msg S 96.0,K,1,0,prepare,standard,264,264,10,0,0,100,5,13,0,0,0,0,0.00,0,0,0,0,0,0,0,0,0,0,0,0,0.00,0.00,0

That results in two commands to the car (CommandSetChargeMode, CommandSetChargeCurrent).
 
Maybe the commands are sent too quickly? There wasn’t a deIay in ovms v2, but the processor in v3 is much faster. Probably safest to add a small delay - I’ll add 50ms into the server v2 code. No idea if this is causing the issue, but it shouldn't hurt.

Regards, Mark.

On 7 Apr 2018, at 2:31 PM, Greg D. <gregd2350@gmail.com> wrote:

Oh, and if it will help track things down, the error was at 04/06/2018
19:34:48, local time (UTC-7).

Thanks,

Greg


Greg D. wrote:
Hi folks,

To the Roadster owners among us...  I just tried switching my 2.0
Roadster from Standard to Range mode charging, and there was an unusual
"pop", similar to the car or OpenEVSE contactors engaging, but louder,
followed by all the fans going off and a "Power Train Service Required"
error on the display.  Tapping away the message, the car started
charging in Range mode as normal...  Odd, and rather unnerving, given
that I'm heading out on a trip shortly.  I'll pull the logs when I return.

This was my first experience using the OVMS system to control charging.
I don't want to try it again.

Has anyone else tried doing this?

Greg


_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev