I have connected an ovms 3 module in the car. I turned on the 12 volt option in the software to prevent the battery from running down. After about 1 day the module shuts down because the battery voltage is too low. This is not a problem. However when the battery is charged and thus the voltage is higher than 12 volts the module does not turn on. A hard reset (unplugging the ODBII connector and plugging it back in) solves the problem temporarily. Until the voltage is too low again. How can I ensure that the module automatically starts up again when the voltage is sufficient?
You need to replace the 12v battery.
Once you "kill" a lead-acid car battery, it's never the same again. If the resting voltage is <12v, you are wasting your time. The module issues are caused by the battery issues, not the other way around.
It's a brand new car.
I know the risk if the resting voltage is too low.
That's why I enabled this option in the software.
The powerconsumption is too high.
no need, but the module need to start up automatticaly when the voltage is above 12 volt.
I haven't used the power management module before, but the original author doesn't seem to respond, so I've had a look at the implementation.
I've found an issue with the final shutdown actually not working as documented. The module would simply shut off for 60 seconds, then do a full boot again. This would happen in a loop until either power was restored or the battery had been depleted so deeply it wouldn't provide enough power for normal module operation. I assume that's where your module got stuck.
So that sleep/reboot loop actually would not save your battery but rather cause a faster depletion and finally a deep discharge.
The fix is in "edge" on my server now (3.2.017-2-gd8028d5d) and should be available on openvehicles.com within 24 hours.
Please leave a feedback if this solves your issue.
That seems to be good news.
Many thanks in advance.
I tried to update.
ota status shows that 3.2.017 is available.
but nothing happens with the command ota flash http
now running the latest version
After the update, the module is live.
But I can't see information in the app. No battery and tire pressure for example in the status page.
After any update, you may need to switch on the car to get metrics data.
Yes, I did, but it didn't work.
in the previous firmware it was indeed needed.
now it doensn't solve this issue.
What do you mean by "the module is live"? Does it connect to the server, just not read data from the car? I.e. can you send commands from the App?
I mean the antenne icon in the app is green and shows 'live'.
I can send commands to the module and receive answers.
ota status for example.
I have thwe wifi only version.
That means the module does not get data from the car, which points to an issue with the CAN bus or connector. Check the status for the CAN buses your vehicle type uses ("can canX status") for errors, try rebooting.
I did a reset and added the car model again.
Now it works.
I will check of the main problem is solved now and let you know.
If your car model configuration was lost, that's indicating your configuration partition may have been corrupted by one of your brown-outs.
That would manifest as not keeping configuration settings over reboots. If that is the case, you need to do a factory reset as documented in the manual:
All issues are solved now.
Next issue, car information doesn't update anymore.
The command ota status shows the latest firmware.
But no reaction when I enter ' can can1 status' or 'can can0 status'.
Any Idea how to solve this?
Reboot and disconnect and connect the module from the car didn't solve it.
Check if you have the same issue with the web interface. If you do, check all your configuration -- see above. If not, you've got some server connection issue. Check the log for hints.
I did a module reset and new installation.
Everything worked again.
For a few days....
Friday I connected my car to the charger.
I didn't disconnect it, but today, Sunday the OVMS lost connection.
Unreachable via Wifi.
I disconnect and connect the connector and now it works again.
But I don't know why it is instable.
It's impossible to read the log when the problem occurs.
Any idea how the solve this issue?
It serms to be difficult.
What do you mean exactly by it's impossible to read the log? The log is currently the only option I see to debug your issue.
Logging is volatile by default.
Did you enable file (persistent) logging to an SD card?
I added an sd card in the module for logging. But when inserting, it fell into the box, but not in the sd sleeve.
Then I opened the box to remove the card and found one small screw loose. I bougt the version without gsm module.
But the screws for mounting this module were included and sreweed in the bracked. Factory didn't tigtened enough. I think this is the reason. Now I inserted the sd card and enabled logging, but it's working prpoerly.