Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

Open Vehicle Monitor System (OVMS) - Technical Discussion

This site may earn commission on affiliate links.
Instructions here:

Factory Reset — Open Vehicles documentation

It is the S2 switch. But factory reset should be the last resort. Better to check on a USB serial console.
I tried connecting via serial USB and nothing. I suspected the cable even though it worked with a phone and sure enough as soon as I tried a new USB cable it came to life. It showed up on my list of wireless networks as OVMS basically reset to factory default.

I'm wondering if there's a way to have it always connect to Wifi when I'm at home. I have to go into my list of SSID and manually connect every time even though I checked "connect automatically."
 
I'm wondering if there's a way to have it always connect to Wifi when I'm at home. I have to go into my list of SSID and manually connect every time even though I checked "connect automatically."
Of course. I used the serial interface to configure it, but it can be done with the Web interface as well. Under the Autostart configuration menu, I have set the Wifi mode to AP + Client, with the home network's ssid for the client. Then under the Wifi config, set the home network's passphrase. I think that will work. With both the modem and Wifi enabled, the OVMS should switch from home to cell and back automatically.
 
Of course. I used the serial interface to configure it, but it can be done with the Web interface as well. Under the Autostart configuration menu, I have set the Wifi mode to AP + Client, with the home network's ssid for the client. Then under the Wifi config, set the home network's passphrase. I think that will work. With both the modem and Wifi enabled, the OVMS should switch from home to cell and back automatically.
On the Autostart config menu are you using Start server V2 or Start server v3?
 
For most users, it is server v2. That is protocol v2 and what the normal apps and servers use.

The v3 protocol is MQTT for IoT style servers. That is still experimental.

Mark, I'm trying to get my v3 module up and running but it's completely unstable and I'm hoping you can help. I started posting in this thread:

Wifi Client Connection Issues | Open Vehicles

I had hoped that adding my modem module would stabilize things, but it has not. My module seems to be locking up constantly. Here are some logs from the latest lockup:

<start car to go for a drive>
2019-09-03 21:46:35 PDT D (5440209) events: Signal(vehicle.on)
2019-09-03 21:46:37 PDT D (5442449) events: Signal(vehicle.headlights.on)
2019-09-03 21:46:47 PDT D (5451949) simcom: rx line ch=3 len=10 : +CSQ: 0,99
2019-09-03 21:46:47 PDT D (5451979) simcom: rx line ch=4 len=10 : +CSSQ: 0,99
2019-09-03 21:46:56 PDT D (5460609) simcom: rx line ch=3 len=10 : +CREG: 1,1
2019-09-03 21:46:56 PDT D (5460639) simcom: rx line ch=3 len=29 : +CCCLK: "19/09/03,21:46:55-28"
2019-09-03 21:46:56 PDT D (5460669) simcom: rx line ch=3 len=10 : +CSQ: 0,99
2019-09-03 21:46:56 PDT D (5460689) simcom: rx line ch=3 len=23 : +COPS: 0,0,"T-Mobile",2
2019-09-03 21:46:56 PDT ID 5460709) simcom: rx line ch=3 len=2 : OK
2019-09-03 21:47:02 PDT D (5466999) simcom: rx line ch=3 len=10 : +CSSQ: 3,99
2019-09-03 21:47:02 PDT D (5467029) simcom: rx line ch=4 len=10 : +CSQ: 3,99
2019-09-03 21:47:03 PDT D (5468149) events: Signal(vehicle.charge.mode)
2019-09-03 21:47:05 PDT D (5470159) events: Signal(vehicle.charge.mode)
2019-09-03 21:47:26 PDT D (5490559) simcom: rx line ch=3 len=10 : +CREG: 1,1
2019-09-03 21:47:26 PDT D (5490579) simcom: rx line ch=3 len=29 : +CRCLK: "19/09/03,21:7:255-28"
2019-09-03 21:47:26 PDT D (5490599) simcom: rx line ch=3 len=10 : +CSQ: 3,99
2019-09-03 21:47:26 PDT D (5490619) simcom: rx line ch=3 len=23 : +CROPS: 0,0,"T-Mobile",2
2019-09-03 21:47:26 PDT D (5490659) simcom: rx line ch=3 len=2 : OK
2019-09-03 21:47:46 PDT I (5510539) ovms-server-v2: Send MP-0 S61.0,M,65535,0,stopped,standard,100,81,12,0,0,2$
2019-09-03 21:47:46 PDT I (5510569) ovms-server-v2: Send MP-0 D128,32,5,39,40,37,499,597532,0,0,32,2,1,1,12.64$
2019-09-03 21:47:46 PDT I (5510589) ovms-server-v2: Send MP-0 L33.649364,-117.612961,218,316,1,1,0,0,0.8,0,0
2019-09-03 21:47:46 PDT I (5510619) ovms-server-v2: Send MP-0 F3.2.002/ota_0/main (build idf v3.1-dev-2835-g15$
2019-09-03 21:47:56 PDT D (5520599) simcom: rx line ch=3 len=10 : +CREG: 1,1
2019-09-03 21:47:56 PDT D (5520629) simcom: rx line ch=3 len=29 : +CCCLK: "19/09/03,21:7:565-28"
2019-09-03 21:47:56 PDT D (5520649) simcom: rx line ch=3 len=10 : +CSQ: 3,99
2019-09-03 21:47:56 PDT D (5520669) simcom: rx line ch=3 len=23 : +COPS: 0,0,"T-Mobile",2
2019-09-03 21:47:56 PDT ID 5520699) simcom: rx line ch=3 len=2 : OK
2019-09-03 21:47:59 PDT D (5524149) simcom: rx line ch=3 len=10 : +CSSQ:63,99
2019-09-03 21:47:59 PDT D (5524179) simcom: rx line ch=4 len=10 : +CSQ: 6,99
2019-09-03 21:48:08 PDT D (5533179) simcom: rx line ch=3 len=10 : +CSQ: 3,99
2019-09-03 21:48:08 PDT D (5533209) simcom: rx line ch=4 len=10 : +CSQ: 3,99
2019-09-03 21:48:08 PDT D (5533179) simcom: rx line ch=3 len=10 : +CSQ: 3,99
2019-09-03 21:48:08 PDT D (5533209) simcom: rx line ch=4 len=10 : +CSQ: 3,99
2019-09-03 21:48:26 PDT D (5550599) simcom: rx line ch=3 len=10 : +CREG: 1,1
2019-09-03 21:48:26 PDT D (5550629) simcom: rx line ch=3 len=29 : +CRCLK: "19/09/03,21:8:265-28"
2019-09-03 21:48:26 PDT D (5550659) simcom: rx line ch=3 len=10 : +CSQ: 3,99
2019-09-03 21:48:26 PDT D (5550679) simcom: rx line ch=3 len=23 : +CROPS: 0,0,"T-Mobile",2
2019-09-03 21:48:26 PDT D (5550699) simcom: rx line ch=3 len=2 : OK
2019-09-03 21:48:49 PDT I (5573959) wifi: bcn_timout,ap_probe_send_start
2019-09-03 22:11:45 PDT I (10539) housekeeping: System considered stable (RAM: 8b=113788-133780 32b=22276)
2019-09-03 22:11:47 PDT D (12539) simcom: tx scmd ch=0 len=103 : AT+CPIN?;+CREG=1;+CTZU=1;+CTZR=1;+CLIP=1;+CMG$
2019-09-03 22:11:49 PDT D (14539) simcom: tx scmd ch=0 len=16 : AT+CGMR;+ICCID
2019-09-03 22:11:53 PDT D (17539) simcom: tx scmd ch=0 len=8 : AT+COPS?
2019-09-03 22:11:54 PDT D (18539) simcom: tx scmd ch=0 len=20 : AT+CMUXSRVPORT=3,1
2019-09-03 22:11:55 PDT D (19539) simcom: tx scmd ch=0 len=20 : AT+CMUXSRVPORT=2,1
2019-09-03 22:11:56 PDT D (20539) simcom: tx scmd ch=0 len=20 : AT+CMUXSRVPORT=1,1
2019-09-03 22:11:57 PDT ID 21539) simcom: tx scmd ch=0 len=20 : AT+CMUXSRVPORT=0,5

Logging stopped at 21:48 and resumes at 22:11. I presume the module locked up at 21:48 and that is why it stopped logging. I power cycled the module at 22:11 by unplugging it and plugging it back in. I had previously assumed that the lockups were due to network connectivity issues, but I'm not sure at this point. I suspect it may be locking up while trying to talk on the CAN bus because it's affecting the behavior of the vehicle as well... to the point the vehicle will not respond to clicks from the key fob. Any suggetions as to where I should start looking?
 
Mark, I'm trying to get my v3 module up and running but it's completely unstable and I'm hoping you can help.

Where are you logging to? If SD CARD, and you have a modern OVMS module (within the past six months or so), can you try to set:

config set sdcard maxfreq.khz 20000
(then reboot)

That will increase write speeds to SD CARD (but will only work on modern OVMS modules).

You could also try logging just the wifi stuff, as debug/verbose logging at other levels may be excessive (in particular, ssh and/or web traffic).

We have just recently identified an issue with the wifi driver in edge reception cases:

LWIP / Mongoose: temporary extreme transmission delays · Issue #241 · openvehicles/Open-Vehicle-Monitoring-System-3

The latest 'edge' firmware (3.2.002-202-g4487038) includes a workaround to try to improve that.

I really have no idea how the module can interfere with the vehicle key fob. Never heard of it. That would imply some issue on the CAN bus. Perhaps the vehicle cable, or diagnostic connector?
 
Where are you logging to? If SD CARD, and you have a modern OVMS module (within the past six months or so), can you try to set:

config set sdcard maxfreq.khz 20000
(then reboot)

That will increase write speeds to SD CARD (but will only work on modern OVMS modules).

You could also try logging just the wifi stuff, as debug/verbose logging at other levels may be excessive (in particular, ssh and/or web traffic).

We have just recently identified an issue with the wifi driver in edge reception cases:

LWIP / Mongoose: temporary extreme transmission delays · Issue #241 · openvehicles/Open-Vehicle-Monitoring-System-3

The latest 'edge' firmware (3.2.002-202-g4487038) includes a workaround to try to improve that.

I really have no idea how the module can interfere with the vehicle key fob. Never heard of it. That would imply some issue on the CAN bus. Perhaps the vehicle cable, or diagnostic connector?

I just got my module from fasttech a week ago and I'm logging to an SD card, so I have followed your advice regarding the logging. I'll do more testing to see if the modification allows for further debugging info. I also updated to the latest edge firmware per your advice.

I suppose you could be right regarding the key fob symptom, but I'm not convinced quite yet. This is mainly because the OVMS module is completely unresponsive and not logging any data every time this symptom occurs.

Right now I'm thinking it's a chicken or the egg scenario. I know that I see symptoms from both sides; the car and the OVMS module. The question to me is 'who's causing it'? The OVMS module is the more likely suspect to me at this point for the simple reason that it never experiences a problem until I leave my house's wifi range. Every single time the module has gone unresponsive, it has been when I leave the house and it disconnects from wifi. Last night, the car was in the garage for hours with both the wifi and cellular modem connected. As soon as I went for a drive, the module went unresponsive. Same thing happened today. I came home for lunch, flashed the edge firmware and rebooted. Upon leaving the house, the module went unresponsive again. I power cycled it upon arriving at the office and was able to see it via the phone app and confirm it had modem connectivity via the 'network status' command. Upon arriving home, the module reconencted to my wifi and it's still online hours later. My assumption is that it will lock up again next time I leave the house.

As another test, I'll disconnect the diag cable and power it via USB in the car to see if the behavior changes when no longer connected to the CAN bus.
 
Today, we are pleased to release v3.2.003 to general availability. This contains over 200 bug fixes and enhancements (mostly to individual vehicle support modules). A summary of the major changes is here:

Code:
2019-09-17 MWJ  3.2.003  OTA release
- New vehicle: Renault Zoe (adaption by Marcos Mezo <[email protected]>)
- Module: task CPU usage statistics & debug records
- Server V2: restart network on RX connection loss (issue #241 workaround)
- Network: avoid using wifi networks with too bad signal quality
- Network: provide dedicated metrics for modem & wifi channel states
- Regen brake signal: added power base range, power smoothing & foot brake config
- Twizy: added tuning option for SEVCON_T45 + Gearbox_T80 hybrid
- Twizy: OBD2 VIN reading & cluster DTC monitoring
- New vehicle: Smart ED/EQ 4.Generation (453) (adaption by Thomas Heuer <[email protected]>)
- Locations: Introduce support for location actions
- Twizy: Release 1.0.0 -- all V2 features planned are now included in V3
- Vehicle framework: DBC and RETOOLS integrations
- Vehicles: Extensions to Kia Niro, Kia Soul, Mitsubishi, Nissan Leaf,
  Renault Twizy, SmartID, Tesla Model S, and Think City

For full detail on all changes, check the GitHub revision history. The v3 modules can be updated over the air (wifi), via SD CARD, or over USB - all without requiring special hardware programmers like the PICKIT used for v2. The simplest way to update the module firmware is to connect it as a client to your wifi network (or phone hotspot), and then use the web interface Config / Firmware / Flash-from-Web; that will show you the version you are running, as well as the latest version available for update. One click on 'Flash now' and the update will be downloaded and installed. Alternatively, you can download the firmware update to a file named ovms3.bin in the root directory of a FAT formatted SD CARD and insert the card into the module's slot - the new firmware will be updated automatically and the file renamed ovms3.done to signify completion. This firmware also includes the feature to check for and automatically update to newly available firmware, every night (so long as the vehicle is connected to WiFi). After updating to 3.1.005 or later, you can enable this for future firmware releases with 'config ota auto yes'. You can choose the release level by setting 'config ota tag edge|eap|main', as one of:
  • edge: Bleeding edge developer nightly-builds
  • eap: Early Access Program (full releases, but with little public testing)
  • main: Publicly tested full releases (the most stable)
Thank you to all the open source developers who have contributed to this, and previous, releases, and thank you for your support of the project. Open Vehicles
 
  • Like
Reactions: drewski and AtAge19
Today, we are pleased to release v3.2.003 to general availability. This contains over 200 bug fixes and enhancements (mostly to individual vehicle support modules). A summary of the major changes is here:

Code:
2019-09-17 MWJ  3.2.003  OTA release
- New vehicle: Renault Zoe (adaption by Marcos Mezo <[email protected]>)
- Module: task CPU usage statistics & debug records
- Server V2: restart network on RX connection loss (issue #241 workaround)
- Network: avoid using wifi networks with too bad signal quality
- Network: provide dedicated metrics for modem & wifi channel states
- Regen brake signal: added power base range, power smoothing & foot brake config
- Twizy: added tuning option for SEVCON_T45 + Gearbox_T80 hybrid
- Twizy: OBD2 VIN reading & cluster DTC monitoring
- New vehicle: Smart ED/EQ 4.Generation (453) (adaption by Thomas Heuer <[email protected]>)
- Locations: Introduce support for location actions
- Twizy: Release 1.0.0 -- all V2 features planned are now included in V3
- Vehicle framework: DBC and RETOOLS integrations
- Vehicles: Extensions to Kia Niro, Kia Soul, Mitsubishi, Nissan Leaf,
  Renault Twizy, SmartID, Tesla Model S, and Think City

For full detail on all changes, check the GitHub revision history. The v3 modules can be updated over the air (wifi), via SD CARD, or over USB - all without requiring special hardware programmers like the PICKIT used for v2. The simplest way to update the module firmware is to connect it as a client to your wifi network (or phone hotspot), and then use the web interface Config / Firmware / Flash-from-Web; that will show you the version you are running, as well as the latest version available for update. One click on 'Flash now' and the update will be downloaded and installed. Alternatively, you can download the firmware update to a file named ovms3.bin in the root directory of a FAT formatted SD CARD and insert the card into the module's slot - the new firmware will be updated automatically and the file renamed ovms3.done to signify completion. This firmware also includes the feature to check for and automatically update to newly available firmware, every night (so long as the vehicle is connected to WiFi). After updating to 3.1.005 or later, you can enable this for future firmware releases with 'config ota auto yes'. You can choose the release level by setting 'config ota tag edge|eap|main', as one of:
  • edge: Bleeding edge developer nightly-builds
  • eap: Early Access Program (full releases, but with little public testing)
  • main: Publicly tested full releases (the most stable)
Thank you to all the open source developers who have contributed to this, and previous, releases, and thank you for your support of the project. Open Vehicles

@markwj,

When you receive a moment, may you please consider the additional feature for OVMS, iOS App for Tesla Roadster, “Dark-Mode”?

Thanks In Advance,

Sincerely,

- P.
 
When you receive a moment, may you please consider the additional feature for OVMS, iOS App for Tesla Roadster, “Dark-Mode”?

Not many changes being made to the Android or iOS Apps at the moment. The general plan is to come up with one unified App (for all platforms), that will also add support for v3 (mqtt) protocol. But that work has not even started (other than proof-of-concept stage).
 
  • Like
Reactions: AtAge19
Today, we are pleased to release v3.2.005 to Early Access Program participants This contains just a small change to v3.2.003 to make the default NOT to submit historical task utilisation data to the Open Vehicles Project. Users wishing to help by submitting this data can opt-in by setting the appropriate configuration parameter. A summary of the major changes is here:

Code:
2019-09-19 MWJ  3.2.005  OTA release
- Default module/debug.tasks to FALSE
  Users that volunteer to submit tasks debug historical data to the Open Vehicles
  project, should (with appreciation) set:
   config set module debug.tasks yes
  This will be transmit approximately 7MB of data a month (over cellular/wifi).

2019-09-19 MWJ  3.2.004  OTA release
- Skipped for Chinese superstitious reasons

2019-09-17 MWJ  3.2.003  OTA release
- New vehicle: Renault Zoe (adaption by Marcos Mezo <[email protected]>)
- Module: task CPU usage statistics & debug records
- Server V2: restart network on RX connection loss (issue #241 workaround)
- Network: avoid using wifi networks with too bad signal quality
- Network: provide dedicated metrics for modem & wifi channel states
- Regen brake signal: added power base range, power smoothing & foot brake config
- Twizy: added tuning option for SEVCON_T45 + Gearbox_T80 hybrid
- Twizy: OBD2 VIN reading & cluster DTC monitoring
- New vehicle: Smart ED/EQ 4.Generation (453) (adaption by Thomas Heuer <[email protected]>)
- Locations: Introduce support for location actions
- Twizy: Release 1.0.0 -- all V2 features planned are now included in V3
- Vehicle framework: DBC and RETOOLS integrations
- Vehicles: Extensions to Kia Niro, Kia Soul, Mitsubishi, Nissan Leaf,
  Renault Twizy, SmartID, Tesla Model S, and Think City

For full detail on all changes, check the GitHub revision history. The v3 modules can be updated over the air (wifi), via SD CARD, or over USB - all without requiring special hardware programmers like the PICKIT used for v2. The simplest way to update the module firmware is to connect it as a client to your wifi network (or phone hotspot), and then use the web interface Config / Firmware / Flash-from-Web; that will show you the version you are running, as well as the latest version available for update. One click on 'Flash now' and the update will be downloaded and installed. Alternatively, you can download the firmware update to a file named ovms3.bin in the root directory of a FAT formatted SD CARD and insert the card into the module's slot - the new firmware will be updated automatically and the file renamed ovms3.done to signify completion. This firmware also includes the feature to check for and automatically update to newly available firmware, every night (so long as the vehicle is connected to WiFi). After updating to 3.1.005 or later, you can enable this for future firmware releases with 'config ota auto yes'. You can choose the release level by setting 'config ota tag edge | eap | main', as one of:
  • edge: Bleeding edge developer nightly-builds
  • eap: Early Access Program (full releases, but with little public testing)
  • main: Publicly tested full releases (the most stable)
Thank you to all the open source developers who have contributed to this, and previous, releases, and thank you for your support of the project. Open Vehicles
 
  • Like
Reactions: drewski and AtAge19
Today, we are pleased to release v3.2.005 to Early Access Program participants This contains just a small change to v3.2.003 to make the default NOT to submit historical task utilisation data to the Open Vehicles Project. Users wishing to help by submitting this data can opt-in by setting the appropriate configuration parameter. A summary of the major changes is here:
...

For full detail on all changes, check the GitHub revision history. The v3 modules can be updated over the air (wifi), via SD CARD, or over USB - all without requiring special hardware programmers like the PICKIT used for v2. The simplest way to update the module firmware is to connect it as a client to your wifi network (or phone hotspot), and then use the web interface Config / Firmware / Flash-from-Web; that will show you the version you are running, as well as the latest version available for update. One click on 'Flash now' and the update will be downloaded and installed. Alternatively, you can download the firmware update to a file named ovms3.bin in the root directory of a FAT formatted SD CARD and insert the card into the module's slot - the new firmware will be updated automatically and the file renamed ovms3.done to signify completion. This firmware also includes the feature to check for and automatically update to newly available firmware, every night (so long as the vehicle is connected to WiFi). After updating to 3.1.005 or later, you can enable this for future firmware releases with 'config ota auto yes'. You can choose the release level by setting 'config ota tag edge | eap | main', as one of:
  • edge: Bleeding edge developer nightly-builds
  • eap: Early Access Program (full releases, but with little public testing)
  • main: Publicly tested full releases (the most stable)
Thank you to all the open source developers who have contributed to this, and previous, releases, and thank you for your support of the project. Open Vehicles

Hey Mark, How can I tell what version my module is on? Is it set to auto-update already? I'm not sure how to connect my module to wifi as a client to make this update (I see latest update release today to general release)...is there another post detailing this in this thread, or can you provide a little guidance?

Thanks,
Mark