Hi Mark,

I was thinking about the faster processor being a factor also.  But it might be more related to the two amp-setting commands being issued when I'm not already charging.  That seemed to be incorrect procedure on my part, if I am reading what you asked as a verification.  The #278 error was in the logs twice, with the same time stamp, and aligned with the start of the charging.  Though I wonder why your time stamps are so different from mine?  Best alignment in time would be the final command for range mode at 10 amps.  My errors are 3 seconds after that, which is probably about right, in which case, why do I have 2 errors?

Greg

04/06/2018 19:26:51 - 04/06/2018 19:33:27 (00:06:36) Charge  83% ->  84%                                           240V  24A of 40A  0.5 kWh   0.0 Ah    0.0 Ah                        
04/06/2018 19:34:48 - 04/06/2018 19:35:12 (00:00:24) Drive   84% ->  84%   0.0 mi   0.0 mph   5.5 mph   46657.7 mi                   0.0 kWh   0.0 Ah    0.0 Ah           
04/06/2018 19:35:13 - 04/06/2018 19:44:48 (00:09:35) Charge  84% ->  84%                                           242V  24A of 40A  0.9 kWh   0.0 Ah    0.0 Ah                        
201804070245.tar Transient section: odometer: 44744.0 to 46657.0 (1913.0 mi), 55.6 hours of driving, 290.9 hours of charging, over 218.1 days

Approximate CAC: 139.63 Ah as of 04/06/2018 04:47:23
greg@server:~/projects/tesla/VehicleLogs/5YJRE1A16A1000834> wine ~/bin/VMSParser.exe -p 201804070245.tar | grep 'code 278'
04/06/2018 19:34:48 | 1523068488 | ERR  | error code 278 8 bytes
04/06/2018 19:34:48 | 1523068488 | ERR  | error code 278 5 bytes
greg@server:~/projects/tesla/VehicleLogs/5YJRE1A16A1000834>


Mark Webb-Johnson wrote:

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



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