######### EDIT #######
CONCLUSION: It seems that my module crashes when booting most of the time when just on OBD2. That's the reason why I thought it was not working. The issue is related with celluar enabled as it boots fine without cellular.
I'm new to OVMS.
- I got a used module and did a factory reset and configured the module
- Setup a ovms server v2+v3 (need to add an update to the installation documentation on freebsd jails in the future)
- Sending v3 messages to the mqtt server will create the correct live entries on abetterrouteplanner
All works fine.
The only trouble I have is, that the module won't start up when connected to OBD2 .
When I connect it to USB first and then connect it to the OBD2 port it works fine. After that first usb connection it works fine from the OBD2 port allone. Shouldn't it start just when I connect it to the OBD2 port ? Other OBD2 dongles start up fine with just OBD2. I also have a testsetup at home where I connect OBD2 dongles to 12v power and they work, only OVMS requires me to connect usb for startup first.
Is that intended ?
Looks I'm too quick to jump to conclusions. I put it up and now it works after some time waiting. It takes much longer on obd than on usb.
That's not normal. You should try to get some clues from monitoring the boot process via USB.
Thanx for your advice. I will try to do that, even though I don't understand how that can help me with the obd2 problem.
Maybe I have a broken module ? I have weird files in the on /store directory when I got to editor and load files I see 8 files:
date: 19-Dec-1921 05:46
I updated to the newest version but the files are still there.
That means you need to do a factory reset, as your /store partition bas been corrupted.
That's a known issue, can happen under unknown circumstances, possibly related to brown outs during file writes.
Simply do a factory reset and restore your latest backup.
Exactly what I came to the conclusion. And after a factory reset those files vanished. Thank you for your help @dexter.