Recent content by TestO

Have some logs i did when developed the OVMS i-Miev puggin. In the excel file there is one log where i start preheating, one from normal charging and one where i just push the button on the remote to activate the remote and get error on the remote. As you can see from the summary page, there...

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...

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...

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.

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.

Great work with the CanIon app. And great to hear that you and Martin has found the CAN message to get the VIN. I would like to implement this into the OVMS as well. So we will appreciate if you will share how to get the VIN form the CAN-bus. Thomas

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.

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?

I believe I've located and fixed this bug in the code now. Could you check if the speed is reported correctly in the app? I assume the same issue also applies for the speed.

No new features, just bug fixes. Good to hear that it's working. The location is always wrong in the app after a restart of the OMVS module until the OVMS server is updated with correct position.

Hi, Have a updated FW under testing now. Have fixed issues where we got false 12V alerts and false quick charge detection. If anyone is interested I can send you the updated FW for testing before i push it to GitHub.

A good start is to read this: https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OVMS_UserGuide_TeslaRoadster.pdf?raw=true The document is for Tesla, but the setup of the module is the same. This kit from ZCW will work...

The OVMS does now also support i-Miev. More info on OVMS: http://www.openvehicles.com/ It is first developed for Tesla Roadster, but the software is open source and adapted to work with several EV. It can be purchased from here...

Have started looking into adding OVMS support for our i-Miev's. http://www.openvehicles.com/ To be able to add support we need at least discover CAN messages to determine if the car is On/Off and if the car is charging or not. Hopefully several of you are interested in OVMS support for our...

Was googling for information regarding i-Miev CAN and find this information regarding i-Miev CAN Gateway. http://www.pref.nagasaki.jp/ev/ev&its/120614/navi/gateway_gaiyou.pdf Here we can see some message transmission intervals - that is a big clue and should help us narrow things down while...