Hi,

Strange.

My VIN is 1G1R96E49CU116489 Read from the papers

The calc for the VIN is 1.514.4e1 (c Notation, dot means concat).

With this your Reading Look ok.

Will try later the New Code later.

Bye

Michael

Von unterwegs gesendet

Am 26.12.2012 um 14:52 schrieb Mark Webb-Johnson <mark@webb-johnson.net>:

Michael,

OK. I found some old logs you sent me before and these show:

7.628 R11 4E9 E1 80 00 04 6C 00 

7.637 R11 514 47 31 52 39 36 45 34 39

8.647 R11 4F1 41 A1 01 A1 00 36 08 88

The 514 looks fine. But, both 4E9 and 4F1 look wrong. In particular, the 4F1 has '41 A1 01 A1 00' - which is what we are seeing for your VIN.

But, id #4E1 has:

8.694 R11 4E1 43 55 31 31 36 34 38 39

If the VIN was in 4E1 and 514, that would give us:

8.694 R11 4E1 43 55 31 31 36 34 38 39

7.637 R11 514 47 31 52 39 36 45 34 39

Or, CU116489G1R96E49 for your car.

For RScott, his logs show:

41966.094 R11 4E1 42 55 31 30 32 36 38 39

41966.110 R11 514 47 31 52 44 36 45 34 36

Or, BU102389G1RD6E36 for his car.

Is that correct?

Reading back through the old eMails, I find this from RScott:

The VIN can be constructed by taking the number "1" and converting the CAN IDs 4E9 and 514 to ASCII.  So with "4E1 4255313032363839" and "514 4731524436453436", you would end up with 42 55 31 30 32 36 38 39 47 31 52 44 36 45 34 36, where 42 is ASCII for B, 55 is U, etc.

So, I think the whole 4E9 was just  a typo, as 4E1 is what is mentioned later in the same sentence.

I've committed the code with 4E1 into github now. It works ok on my simulator, and hopefully should be ok in your car now.

Can you try?

Regards, Mark.

On 26 Dec, 2012, at 9:12 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

Michael,

I've put this up on my test bench, set to VA vehicle type, and setting my simulator to 500Kbps CAN speed, then transmitting the following three messages once a second:

ID#206 A0 10 00 00 00 00 00 00

ID#4F1 42 55 31 30 32 36 38 39

ID#514 47 31 52 44 D6 45 34 36

Then, with the module in SETUP mode, I get:

S MODULE?

# Module:

 VehicleID:TESTCAR

 VehicleType:VA

 Units:K

 Notifications:IP

DIAG

# DIAG

# Firmware: 2.1.1/VA/V2

#  SWITCH:   1

#  12V Line: 14.0 V

#  Signal:   0

#  VIN:      BU102689G1RD6E46 (VA)

#  SOC:      64% (0 ideal, 0 est miles)

That all looks ok. 

The message from your car is:

GERMANVOLT rx msg F 2.1.1/V2,A??,24,0,VA,E-Plus

00000040  20 6d 73 67 20 46 20 32  2e 31 2e 31 2f 56 32 2c  | msg F 2.1.1/V2,|
00000050  41 a1 01 a1 2c 32 31 2c  30 2c 56 41 2c 45 2d 50  |A...,21,0,VA,E-P|
00000060  6c 75 73 0a                                       |lus.|

Your VIN is showing up as 41,A1,01,A1 - as you say: wrong.

But, the firmware version and car type look ok. Not sure why they would not show up in the App. Perhaps the corrupt VIN# is messing up interpretation of that message? Perhaps the high bit on the A1 is messing it up.

Not sure what is going on in your car itself. Can you check any captures you have for the exact id#4F1 and id#514 messages you have, and let me know?

Regards, Mark.

On 21 Dec, 2012, at 9:33 PM, mikeljo@mac.com wrote:

Hi,

thanks.

Works. Get the correct infos from my car.

Implement the SOC calculation from my previous mail.

- GPS ok

- SOC ok

BUT:

- no VIN

- No Car Type

- no car firmware

Here some Pics from the App:

<IMG_1075.PNG>

<IMG_1076.PNG>

<IMG_1077.PNG>

<IMG_1078.PNG>

The App is the 1.3.2 compiled from the git. This is NOT the one from the Store!?

BTW: You see the GSM Signal is -113dBm. When one door is open i got -87dBm. Heavy attenuation.

I think i must mount the antenna outside the car. GPS is ok.

Bye

michael

Am 21.12.2012 um 02:19 schrieb Mark Webb-Johnson <mark@webb-johnson.net>:

Michael,

Parameter #14 (PARAM_VEHICLETYPE) holds the selected vehicle type. This can be set either from the smartphone apps, or via the SMS MODULE command.

Regards, Mark.

On 21 Dec, 2012, at 4:31 AM, mikeljo@mac.com wrote:

Hi,

i checked it out. It compiles without error.
But i think i missed something: how to switch between the cars? I know you do something, but couldn't find the howto.
I found the ROM Parameter "VA" in "vehicle.c", but how to put this in the ROM?
SMS Command?

Sorry.

Bye
Michael


Am 20.12.2012 um 15:08 schrieb Mark Webb-Johnson <mark@webb-johnson.net>:

Michael J:

The following commit should fix this:

* 269cd4f (HEAD, origin/master, origin/HEAD, master) Ampera VIN 4E9->4F1

Can you check the code now in master head, and see if it has everything you need. It builds and compiles on v2 hardware, but you'll need to change the compiler flags to get it building on v1 (just change TESLAROADSTER to VOLTAMPERA).

What was the end result of the SOC range changes? Any ideas on the solution?

Regards, Mark.

On 6 Nov, 2012, at 5:28 AM, mikeljo@mac.com wrote:

Hi mark,

do you think at the VIN?

1 +  514 + 4F1

_______________________________________________
OvmsDev mailing list
OvmsDev@lists.teslaclub.hk
http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________
OvmsDev mailing list
OvmsDev@lists.teslaclub.hk
http://lists.teslaclub.hk/mailman/listinfo/ovmsdev