29 posts / 0 new
Last post
alillebakk
OVMS v3 KIA E-Niro - Stability issues reading from car

Hi.
I installed a OVMS v3 in my KIA E-Niro, and it is great! But I have stability issues for the data read from the car OBD-II port.
I got stable readings for X hours, but suddenly it stops reporting SOC, Voltage etc. Then i need to power cycle and everything is back to normal.
During the time where OVMS do not read OBD-II data, it still reports GPS speed etc, so it seems to be a bug related to OBD-II data.

I have tested both latest delevoper release and stable release but both have same issue.

While waiting for a new release who hopefully solve this, would it be possible to script a "hourly reboot" of the device ?

Thanks in advance!

Regards
Andre

markwj
markwj's picture
At the time of the fault, and

At the time of the fault, and with vehicle on, can you get us:

can can1 status
(wait 10 seconds)
can can1 status
vehicle status
server v2 status

If you are running the latest development firmware, a can dump of can1 would be helpful (again at the time of the problem). Just 1 minute or so, in crtd format.

alillebakk
Any idea?

Hi @markwj do you have any idea how to solve this?

alillebakk
With wehicle stopped, and plugged into wall charger and charging

OVMS# can can1 status
CAN: can1
Mode: Active
Speed: 500000
DBC: none
Interrupts: 5604
Rx pkt: 2817
Rx err: 0
Rx ovrflw: 0
Tx pkt: 10196
Tx delays: 0
Tx err: 128
Tx ovrflw: 0
Wdg Resets: 0
Wdg Timer: 8 sec(s)
Err flags: 0x0004c40a
OVMS# can can1 status
CAN: can1
Mode: Active
Speed: 500000
DBC: none
Interrupts: 5604
Rx pkt: 2817
Rx err: 0
Rx ovrflw: 0
Tx pkt: 10199
Tx delays: 0
Tx err: 128
Tx ovrflw: 0
Wdg Resets: 0
Wdg Timer: 2 sec(s)
Err flags: 0x0004c40a
OVMS# server v2 status
State: Connected
OVMS V2 login successful, and crypto channel established
OVMS# vehicle status
Vehicle module loaded and running

Vehicle status from OVMS webconsole status page :

Not charging
SOC: 68.0%
Ideal range: 287km
Est. range: 309km
ODO: 8538.0km
CAC: 108.8Ah
SOH: 100%
Currently at 62.748356,7.252410 (with good GPS lock)
There are 1 location(s) defined
Active locations: Lillebakk Office

alillebakk
With wehicle started, and disconnected from wall charger:

OVMS# can can1 status
CAN: can1
Mode: Active
Speed: 500000
DBC: none
Interrupts: 0
Rx pkt: 0
Rx err: 0
Rx ovrflw: 0
Tx pkt: 1
Tx delays: 20
Tx err: 0
Tx ovrflw: 22
Wdg Resets: 0
Wdg Timer: 4 sec(s)
Err flags: 0x00000000
OVMS# can can1 status
CAN: can1
Mode: Active
Speed: 500000
DBC: none
Interrupts: 0
Rx pkt: 0
Rx err: 0
Rx ovrflw: 0
Tx pkt: 1
Tx delays: 20
Tx err: 0
Tx ovrflw: 24
Wdg Resets: 0
Wdg Timer: 4 sec(s)
Err flags: 0x00000000
OVMS# vehicle status
Vehicle module loaded and running
OVMS# server v2 status
State: Connected
OVMS V2 login successful, and crypto channel established

Vehicle status from OVMS webconsole status page :

Not charging
SOC: -
Ideal range: 440km
Est. range: 455km
CAC: 160.0Ah
Currently at 62.748192,7.252820 (with good GPS lock)
There are 1 location(s) defined
Active locations: Lillebakk Office

alillebakk
With wehicle started, after power cylcle of OVMS

OVMS# can can1 status
CAN: can1
Mode: Active
Speed: 500000
DBC: none
Interrupts: 416
Rx pkt: 298
Rx err: 0
Rx ovrflw: 0
Tx pkt: 118
Tx delays: 0
Tx err: 0
Tx ovrflw: 0
Wdg Resets: 0
Wdg Timer: 0 sec(s)
Err flags: 0x00000000
OVMS# can can1 status
CAN: can1
Mode: Active
Speed: 500000
DBC: none
Interrupts: 468
Rx pkt: 334
Rx err: 0
Rx ovrflw: 0
Tx pkt: 134
Tx delays: 0
Tx err: 0
Tx ovrflw: 0
Wdg Resets: 0
Wdg Timer: 0 sec(s)
Err flags: 0x00000000
OVMS# vehicle status
Vehicle module loaded and running
OVMS# server v2 status
State: Connected
OVMS V2 login successful, and crypto channel established

Vehicle status from OVMS webconsole status page :

Not charging
SOC: 68.0%
Ideal range: 287km
Est. range: 309km
ODO: 8538.0km
CAC: 108.8Ah
SOH: 100%
Currently at 62.748356,7.252410 (with good GPS lock)
There are 1 location(s) defined
Active locations: Lillebakk Office

alillebakk
With vehicle plugged in charger, after power cylcle of OVMS

OVMS# can can1 status
CAN: can1
Mode: Active
Speed: 500000
DBC: none
Interrupts: 2474
Rx pkt: 1795
Rx err: 0
Rx ovrflw: 0
Tx pkt: 679
Tx delays: 0
Tx err: 0
Tx ovrflw: 0
Wdg Resets: 0
Wdg Timer: 3 sec(s)
Err flags: 0x00000000
OVMS# can can1 status
CAN: can1
Mode: Active
Speed: 500000
DBC: none
Interrupts: 2551
Rx pkt: 1851
Rx err: 0
Rx ovrflw: 0
Tx pkt: 700
Tx delays: 0
Tx err: 0
Tx ovrflw: 0
Wdg Resets: 0
Wdg Timer: 0 sec(s)
Err flags: 0x00000000
OVMS# vehicle status
Vehicle module loaded and running
OVMS# server v2 status
State: Connected
OVMS V2 login successful, and crypto channel established

Vehicle status from OVMS webconsole status page :

Standard - Charging
232.0V/31.9A
Full: 163 mins
0%: 163 mins
0km: 163 mins
SOC: 68.0%
Ideal range: 287km
Est. range: 309km
ODO: 8538.0km
CAC: 108.8Ah

markwj
markwj's picture
If the fault occurs, can you

If the fault occurs, can you try a:

can can1 status
can can1 stop
can can1 start active 500000
can can1 status

and see if that resolves it? If it does, then we can try to find out more about the actual status of the can bus at the time of the issue. The error flags 0x0004c40a seem to indicate a bus fault.

alillebakk
Test did work.

two can1 status with 10 sec interval before stop,start procedure. and two can1 status with 10 sec interval aftert stop,start procedure.

OVMS# can can1 status
CAN: can1
Mode: Active
Speed: 500000
DBC: none
Interrupts: 11991
Rx pkt: 7396
Rx err: 0
Rx ovrflw: 0
Tx pkt: 12976
Tx delays: 0
Tx err: 128
Tx ovrflw: 0
Wdg Resets: 0
Wdg Timer: 3 sec(s)
Err flags: 0x0004c400
OVMS# can can1 status
CAN: can1
Mode: Active
Speed: 500000
DBC: none
Interrupts: 11991
Rx pkt: 7396
Rx err: 0
Rx ovrflw: 0
Tx pkt: 12981
Tx delays: 0
Tx err: 128
Tx ovrflw: 0
Wdg Resets: 0
Wdg Timer: 4 sec(s)
Err flags: 0x0004c400
OVMS# can can1 status
CAN: can1
Mode: Active
Speed: 500000
DBC: none
Interrupts: 11991
Rx pkt: 7396
Rx err: 0
Rx ovrflw: 0
Tx pkt: 12985
Tx delays: 0
Tx err: 128
Tx ovrflw: 0
Wdg Resets: 0
Wdg Timer: 5 sec(s)
Err flags: 0x0004c400
OVMS# can can1 status
CAN: can1
Mode: Active
Speed: 500000
DBC: none
Interrupts: 11991
Rx pkt: 7396
Rx err: 0
Rx ovrflw: 0
Tx pkt: 12985
Tx delays: 0
Tx err: 128
Tx ovrflw: 0
Wdg Resets: 0
Wdg Timer: 6 sec(s)
Err flags: 0x0004c400
OVMS# can can1 stop
Can bus can1 stopped
OVMS# can can1 start active 500000
Can bus can1 started in mode active at speed 500000bps
OVMS# can can1 status
CAN: can1
Mode: Active
Speed: 500000
DBC: none
Interrupts: 0
Rx pkt: 0
Rx err: 0
Rx ovrflw: 0
Tx pkt: 1
Tx delays: 1
Tx err: 0
Tx ovrflw: 0
Wdg Resets: 0
Wdg Timer: 2 sec(s)
Err flags: 0x00000000
OVMS# can can1 status
CAN: can1
Mode: Active
Speed: 500000
DBC: none
Interrupts: 0
Rx pkt: 0
Rx err: 0
Rx ovrflw: 0
Tx pkt: 1
Tx delays: 5
Tx err: 0
Tx ovrflw: 0
Wdg Resets: 0
Wdg Timer: 5 sec(s)
Err flags: 0x00000000

markwj
markwj's picture
Ok. thanks. This is most

Ok. thanks. This is most likely the same issue with the can driver we have seen elsewhere. Errors on the bus cause the driver to lockup and need a restart. We are working on it.

alillebakk
Periodic restart

Is IT possible to script a hourly reboot or similar as a temporary fix until problem is solved?

timopen
This is caused by the TX

This is caused by the TX errors.
For each TX error there is a error counter in esp CAN bus that increases by 8 and for each successful TX it decreases by 1.
When the counter reaches 128 there is a warning flag raised (TX WARNING) and when it reaches 255 the bus is shut down.
The only remedy when it's shut down is a hard reboot.
I found out that there was 2 CAN bus pollings in Pollstate 0 (off) that interfered with each other, I moved them apart a bit time wise, then there were no more TX errors.
This change is now in a pull request.

juanheredia
Hi, I can confirm that this

Hi, I can confirm that this is happening to me. Using a Hyundai Kona 39,2kWh. Specially after charging the car.

Everytime I finish to charge up the car (at home or in a public place), what I do is: power can1 off, then after 30 seconds, power can1 on. 

I'm sure that doing what you say will have the same beheavior.  

Ningaloo
Reboot

I have the same problem, no data form the OBD-II port after x hours. Then i have to reconnect the OBD-II plug. Is there a easier way to power cycle?

rroca
pls update on any progress on this stability issue

Just bought my device for my new e-Niro, nice project, promising and excited! But experiencing this stability issue.

It's nearly unusable except for the GPS location on the road unless you manually disconnect/connect the cable just before you want to request the readings (i.e. when going to charge in a public station and you want to follow-up the progress remotely).

Please keep update on any progress for this.

Thanks!

tillathenun
tillathenun's picture
Just to say “me too”.

I’ve recorded a video for my YouTube channel about setting up OVMS for the e-Niro but I’m hesitating publishing until this is fixed.

glynhudson
possible fix

There has been a possible fix submitted for this issue, it's currently in pull-request. Hopefully it will be merged into the 'edge; firmware release soon

https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/267

tillathenun
tillathenun's picture
Thanks, Glyn - good to hear!

Thanks, Glyn - good to hear!

DeNiro
Please publish Mr EV.

Hi Andrew, I'm a great fan of your YT postings about the e-Niro (waiting for report on "the Trip to Italy" by the way). Would really appreciate a video from you on this OVMS-topic as I'm looking for a way to monitor temperature and SoC in the e-niro.

markwj
markwj's picture
This has now been accepted

This has now been accepted and merged. It is available in the EDGE releases now.

alillebakk
Working release

I can confirm that this new release has solved the problem on my side. Stable readings the whole week now without restarts! Thank you!

markwj
markwj's picture
Glad to hear it. Thanks for

Glad to hear it. Thanks for the feedback.

Borrem
3.2.005 still stopping

Hi. Just upgraded my unit to the latest fw, but it still freeze up the obd when it’s parked w/o charger on.
Any ideas?

Tobahc
Latest developer release or

Latest developer release or stable release?
Release number?

rroca
I'm stable at 3.2.006

got from OTA eap (early access program)

Tobahc
@rroca

@rroca
So no freezing system with 3.2.006?

rroca
No.

That update came OTA last saturday, and no freezing/need to reboot since then,
Also with the previous EDGE firm release, I ran stable with it for a month.

Tobahc
@Borrem

Sounds great!

@Borrem
What is your experience? Do you also have a stable system now with this latest fw-version?

Borrem
Installed .006 EAP yesterday,

Installed .006 EAP yesterday, and so far so good! Looks stable now, tested both with and without charger. Also managed to unlook car using app. :-)
Any possibility to remote start the heater/cooler in the future?

Log in or register to post comments