OVMS for Mitsubishi i-Miev, Citroen C-Zero and Peugeot iOn

[jjlink]

Way cool! John, will you bring your iMiEV to tomorrow's EAASV meeting (they'll be demo'ing an i3)?

Yes, I think I can make it to the EAASV.org meeting tomorrow. :idea:

 

[TestO]

Grate to see that more people is using the OVMS on there i-Miev's :mrgreen:

Please report back if you experience any bug or issues.

Could someone check if the speed is reported correctly in the OVMS app when driving?

 

[jjlink]

Grate to see that more people is using the OVMS on there i-Miev's :mrgreen:

Please report back if you experience any bug or issues.

Could someone check if the speed is reported correctly in the OVMS app when driving?

The speed is not reading correctly. I just took a short drive and it appeared to be reading like 2x my actual speed.

Do you know how to pull the data from the OVMS server? I started messing around with Perl; but i'm missing the Crypt library, etc.

 

[TestO]

Grate to see that more people is using the OVMS on there i-Miev's :mrgreen:

Please report back if you experience any bug or issues.

Could someone check if the speed is reported correctly in the OVMS app when driving?

The speed is not reading correctly. I just took a short drive and it appeared to be reading like 2x my actual speed.

Do you know how to pull the data from the OVMS server? I started messing around with Perl; but i'm missing the Crypt library, etc.

Thanks,
I was expecting that the speed had the same issue as ODO for cars configured to display miles. The i-Miev is reporting in Km on the CAN bus for Km and Miles configured cars.
It's great if you could help testing a new version of the code? I can make a new .hex file and send you a PM.

 

[jjlink]

FYI - I figured how to pull the data logs for my car from the OVMS server using cURL. The log file is returned in JSON format. I converted to a CSV file (using Windows Powershell 4) for use in Excel.

Here is a sample of some if the data looks like at the beginning of a charge cycle starting at 22% SOC:

#65 C rx msg S 22,M,212,6,charging,standard,20,8,13,0,0,0,3,1,0,0,0,-1,0.00,-1,-1,0,0,-1,0,0,-1 39661 1/20/2014 14:06
#65 C rx msg S 22,M,210,14,charging,standard,20,8,13,0,0,0,3,1,0,0,0,-1,0.00,-1,-1,0,0,-1,0,0,-1 39699 1/20/2014 14:07
#65 C rx msg S 23,M,209,14,charging,standard,21,9,13,3,0,0,3,1,0,0,0,-1,0.00,-1,-1,0,0,-1,0,0,-1 39785 1/20/2014 14:10
#65 C rx msg S 26,M,209,14,charging,standard,24,11,13,13,0,0,3,1,0,0,0,-1,0.00,-1,-1,0,0,-1,0,0,-1 40159 1/20/2014 14:19
#65 C rx msg S 29,M,208,14,charging,standard,26,12,13,23,0,1,3,1,0,0,0,-1,0.00,-1,-1,0,0,-1,0,0,-1 40546 1/20/2014 14:29
#65 C rx msg S 32,M,209,14,charging,standard,29,14,13,33,0,1,3,1,0,0,0,-1,0.00,-1,-1,0,0,-1,0,0,-1 40946 1/20/2014 14:39
#65 C rx msg S 35,M,209,14,charging,standard,32,16,13,43,0,2,3,1,0,0,0,-1,0.00,-1,-1,0,0,-1,0,0,-1 41516 1/20/2014 14:49
#65 C rx msg S 38,M,210,14,charging,standard,35,18,13,53,0,2,3,1,0,0,0,-1,0.00,-1,-1,0,0,-1,0,0,-1 42103 1/20/2014 14:59
#65 C rx msg S 41,M,209,14,charging,standard,38,20,13,63,0,3,3,1,0,0,0,-1,0.00,-1,-1,0,0,-1,0,0,-1 42525 1/20/2014 15:09
#65 C rx msg S 44,M,209,14,charging,standard,40,22,13,73,0,3,3,1,0,0,0,-1,0.00,-1,-1,0,0,-1,0,0,-1 42875 1/20/2014 15:19
#65 C rx msg S 47,M,209,14,charging,standard,43,24,13,83,0,4,3,1,0,0,0,-1,0.00,-1,-1,0,0,-1,0,0,-1 43261 1/20/2014 15:29
#65 C rx msg S 50,M,209,14,charging,standard,46,26,13,93,0,4,3,1,0,0,0,-1,0.00,-1,-1,0,0,-1,0,0,-1 43620 1/20/2014 15:39
#65 C rx msg S 51,M,209,14,charging,standard,47,27,13,98,0,4,3,1,0,0,0,-1,0.00,-1,-1,0,0,-1,0,0,-1 43846 1/20/2014 15:44

 

[jjlink]

Grate to see that more people is using the OVMS on there i-Miev's :mrgreen:

Please report back if you experience any bug or issues.

Could someone check if the speed is reported correctly in the OVMS app when driving?

Bugs or issues:

A couple of times when charging was complete the OVMS box notified me three times in the same minute.


OVMS by JJLINK, on Flickr

 

[PV1]

For the first time today I got a notification that charging started. I charged the car, then got the notification when I preheated the car.

 

[jjlink]

For the first time today I got a notification that charging started. I charged the car, then got the notification when I preheated the car.

What did the notification look like? Maybe you are running 2.6.2 that was uploaded in the last 5 days?

V2_experimental.hex 2.6.2 firmware .hex builds 5 days ago

I loaded whatever version was on github on Jan 14th.

From GitHub - It looks like they just fixed an issue that could effect the i-MiEV, Citroen C-Zero and Peugeot iOn:

Call vehicle_fn_poll0() in OVMS_POLLER, if no poll list defined

 

[TestO]

For the first time today I got a notification that charging started. I charged the car, then got the notification when I preheated the car.

What did the notification look like? Maybe you are running 2.6.2 that was uploaded in the last 5 days?

V2_experimental.hex 2.6.2 firmware .hex builds 5 days ago

I loaded whatever version was on github on Jan 14th.

From GitHub - It looks like they just fixed an issue that could effect the i-MiEV, Citroen C-Zero and Peugeot iOn:

Call vehicle_fn_poll0() in OVMS_POLLER, if no poll list defined

The V2_experimental.hex 2.6.2 firmware .hex from GutHub is not working.
Mark fixed a bug in the 2.6.2 yesterday and I have compiled a new version that i'm testing now.
It's look good so far. Have also fixed the Miles vs Km issues and added reading of VIN.

 

[jjlink]

For the first time today I got a notification that charging started. I charged the car, then got the notification when I preheated the car.

What did the notification look like? Maybe you are running 2.6.2 that was uploaded in the last 5 days?

V2_experimental.hex 2.6.2 firmware .hex builds 5 days ago

I loaded whatever version was on github on Jan 14th.

From GitHub - It looks like they just fixed an issue that could effect the i-MiEV, Citroen C-Zero and Peugeot iOn:

Call vehicle_fn_poll0() in OVMS_POLLER, if no poll list defined

The V2_experimental.hex 2.6.2 firmware .hex from GutHub is not working.
Mark fixed a bug in the 2.6.2 yesterday and I have compiled a new version that i'm testing now.
It's look good so far. Have also fixed the Miles vs Km issues and added reading of VIN.

OK, let us know when its safe to try it.

Thanks

 

[PV1]

I loaded my firmware before the new year, 2.5.5 I believe. I'm also having issues with the app not getting updated. This started yesterday. Also, when I got home yesterday, my car freaked out and gave me RBS (Regen Brake System), EV warning, ASC active, and ASC off lights and the car gave me ready dings twice. Check out the thread "i-MiEV Crashed".

Also, as shown here, I'm now getting temperatures, which I didn't have before. I haven't updated the module since I installed it and loaded the experimental firmware back in December.
https://www.dropbox.com/s/a551qbnocyxk0je/Screenshot_2014-01-24-14-47-11.png

Here's the new notification:
https://www.dropbox.com/s/qe4tj4f5jqjpxyn/Screenshot_2014-01-24-14-47-25.png

Here's the lights. It acted like the module fuzzed the CAN bus. I've noticed similar behavior when opening the OBDLink app, which attempts to talk to the car with various protocols. I'll verify tonight.
https://www.dropbox.com/s/q36delnjw1w78ry/20140123_165148.jpg

After restarting the car, the lights were off.

 

[TestO]

I don't know when Mark is going to compile a new version. If you want I can send you the version I'm testing.
Had been great to have someone else testing the new code. Especially the format conversion for cars configured for miles.

 

[TestO]

I loaded my firmware before the new year, 2.5.5 I believe. I'm also having issues with the app not getting updated. This started yesterday. Also, when I got home yesterday, my car freaked out and gave me RBS (Regen Brake System), EV warning, ASC active, and ASC off lights and the car gave me ready dings twice. Check out the thread "i-MiEV Crashed".

Also, as shown here, I'm now getting temperatures, which I didn't have before. I haven't updated the module since I installed it and loaded the experimental firmware back in December.
https://www.dropbox.com/s/a551qbnocyxk0je/Screenshot_2014-01-24-14-47-11.png

Here's the new notification:
https://www.dropbox.com/s/qe4tj4f5jqjpxyn/Screenshot_2014-01-24-14-47-25.png

Here's the lights. It acted like the module fuzzed the CAN bus. I've noticed similar behavior when opening the OBDLink app, which attempts to talk to the car with various protocols. I'll verify tonight.
https://www.dropbox.com/s/q36delnjw1w78ry/20140123_165148.jpg

After restarting the car, the lights were off.

The strange temperature is a known bug. Earlier versions didn't support negative motor temperature values. Since the i-Miev is report the temperatures in Celsius you will see this at freezing temperatures.
This will be fixed in the new version.

I have also had the error light issue twice with an older version. Haven't seen this issue with the later versions of the code. I believe this is related to a SW crash and a restart of the module. The newest version looks more stabile and also more responsive.

 

[PV1]

OK. That's along the lines of what I was thinking that caused it.

What's weird is that I've never had temperatures before.

Let me know when the latest firmware will be available.

 

[PV1]

I fuzzed the CAN bus with an app. I got the same lights to come on, but without the other fanfare. Is it possible that a dead short of the CAN bus for less than half a second would act like turning the key off then right back on? With the car in READY, turning the key off, then right back on without going to START will result in the car going to 'auto-READY'.

 

[martinwinlow]

Hi,

I am trying to get my Peugeot Ion (Mitsubishi i-Miev) working with my OVMS module using a GeoSim. I have configured it and can get SMS responses and an accurate GPS location report. However, in response to a STAT? SMS I am still only getting:

xx:xx:xx
Not charging
SOC: 0%

I also get:-

Module:
VehicleIDmy correct vehicle ID)
VehicleType:MI
Units:M
Notifications:SMSIP

… to a MODULE? request.

In response to VERSION…

OVMS Firmware version:
2.6.2//V2

Anyone got any clues? MW

 

[PV1]

Have you loaded the experimental firmware from GIThub?

 

[TestO]

Have tested the 2.6.2 OMVS FW with the latest MI code for a week. So far it look to OK
The latest MI code is pushed to GitHub : https://github.com/openvehicles/Open-Vehicle-Monitoring-System

For those of you not able to build form source yourself, you can download the HEX file from here: https://dl.dropboxusercontent.com/u/7144634/OVMS.X.production.hex.020214.zip

Please report if you experience any bugs.

 

[martinwinlow]

Thanks for the replies.

After I reset the OVMS module (by unplugging the ODB connector and reconnecting it) in response to STAT? I got
00:55:26 (time since last reset?)
Not charging (it isn't)
SOC: 0% (it should be near 100%)
ODO: 7,319.0 mi (its only done about 4 and a bit K miles - is this kms? I'll check in the morning)

"Have you loaded the experimental firmware from GIThub?"… Er, thought so but I've just had a look back there and can't find anything that looks remotely like a source file (or hex for that matter). It is not wildly obvious where I should be looking…

The hex file I used to flash my OVMS module was called 'OVMS i-Miev compatible HEX code - vehicle_mitsubishi.hex' and I downloaded it on 19Jan2014, if that helps.

I'll try this hex file tomorrow suggested by TestO…

https://dl.dropboxusercontent.com/u/7144634/OVMS.X.production.hex.020214.zip

… but it would be interesting to see the source code too. Bed time.

MW

 

[jjlink]

Have tested the 2.6.2 OMVS FW with the latest MI code for a week. So far it look to OK
The latest MI code is pushed to GitHub : https://github.com/openvehicles/Open-Vehicle-Monitoring-System

For those of you not able to build form source yourself, you can download the HEX file from here: https://dl.dropboxusercontent.com/u/7144634/OVMS.X.production.hex.020214.zip

Please report if you experience any bugs.

OK, its up and running on my box now.

i-MiEV: OVMS Firmware version: 2.6.2/MI/V2

Thanks