OVMS kits have started arriving, and are being connected to cars. Approximately 1/3rd of the first batch of modules have already been installed and are connected to OVMS servers, with more coming online every day. The feedback you early users are providing is extremely helpful to the project, to smooth the way for future users, and is most appreciated.
1] Firmware Update
Of those who have already installed their OVMS v3 modules, approximately half are still running the old factory firmware (now more than a month out of date). As this is early beta firmware, it is important that you keep the module up-to-date with the latest firmware (to take advantage of fixes and improvements as they are released, and avoid running into problems already fixed).
Today, we are pleased to release v3.1.004:
Firmware: 3.1.004/ota_0/main (build idf v3.1-dev-454-gdaef4b5c Apr 17 2018 08:35:59) OTA release providing minor improvements and fixes. - Tesla Model S: Add support for v.bat.soc, v.pos.speed and park/drive status metrics - Tesla Roadster: Fixes for charge/drive mode on v1.x and v2.x cars - SD CARD: Provide configurable sdcard parameters: sdcard [maxfreq.khz] = 16000 Maximum frequency (in kHz) of SD CARD bus sdcard [automount] = yes Automatically mount SD CARD on insertion - Boot: store & send crash debug info (*-OVM-DebugCrash records) - OTA: Support for configurable release tag and server URL ota [tag] = main ota [server] = api.openvehicles.com/firmware/ota - Wifi: Increase scan responsiveness (60 seconds -> 10, on first scan) - Factory reset by SD file "factoryreset.txt" or pushing SW2 for 10 seconds Note: SW2 method needs removing any SD card inserted. - Wifi: fallback to AP mode net "OVMS" password "OVMSinit" after factory reset - Miscellaneous bug fixes and enhancements
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.
Early production users have run into some common problems, which we summarise below in a mini-FAQ:
* The 'metric list m.net.mdm.iccid’ is not showing my modem, and my modem is not connecting.
To minimise power consumption, OVMS v3 will by default keep all peripheral devices turned off unless you enable them. In the case of the modem, you can enable it at startup by the web interface ‘Autostart’ configuration clicking the “Start modem” option. You can also do this from the command line with ‘config auto modem yes’.
* I’ve messed things up, and need to reset the settings back to factory defaults.
If you are running the latest v3.1.004 firmware, you can simply remove any SD CARD then press and hold the BOOT button for 10 seconds. Alternatively, make a file ‘factoryreset.txt’ on the root of the SD CARD and insert it.
If you are running older firmware, you will need to connect a serial console (via USB) and use the ‘module factory reset’ command. Instructions are in the User Guide.
* It is not connecting. How do I find out what is going on?
The following commands show useful status information:
server v2 status
* What WiFi configuration is recommended?
The most flexible seems to be “Scanning Client” mode. Enter SSIDs and passwords for all the WiFi networks you have access to (including your phone hotspot if you have it), and enable Scanning Client mode. The OVMS module will then connect to WiFi whenever it gets in range of any of those networks. That will then give the module cheap fast Internet (without cellular data charges), the ability to do OTA firmware updates over WiFi, and a simple way for any laptop/phone/tablet on the same WiFi network to connect to the module to configure/monitor.
While Access Point mode is useful at times (especially for initial setup), it offers no Internet connectivity. Access Point + Client mode can only use one single SSID and is limited in that the channel for the SSID must be the same as the channel for the Access Point (only 1 radio in the module). In general, Scanning Client mode is much simpler and more useful for the majority of cases.
3] Help/Support links
To simplify getting started, a Hologram SIM has been included with the modem in every OVMS v3.1 kit. Hologram have also kindly provided a coupon code “OVMS” that can be used to get US$5 credit; this can be used for both existing as well as new Hologram customers. You can simply enter that coupon code at checkout (when purchasing data credits, etc).
When activating your Hologram SIM, you’ll need to enter the ICCID written on the SIM itself. You can also get that electronically (without having to open up the package) from the web or terminal shells, so long as the modem is powered up, with the following command:
OVMS# metric list m.net.mdm.iccid
Please remember that this first production batch is intended for experienced OVMS v2 users and v3 developers, and note:
* Firmware is not complete, and should be considered beta.
* Functionality is approximately equivalent to basic OVMS v2 firmware, but some advanced features (such as ACC, SMS control, etc) are not available yet.
* Firmware is far in advance of v2 in other aspects (such as built in web server, metrics, console, tcp/ip support, diagnostics, geofencing, scripting, etc).
* Firmware can be updated either Over The Air (OTA), by Micro SD card, or over USB interface.
* Vehicle support currently includes: Kia Soul EV, Nissan Leaf, Renault Twizy, and Tesla Roadster.
If you do experience a problem, or need assistance, please start by talking to other OVMS v3.1 users/developers in your area. If you still can't solve the issue, then login to the www.openvehicles.com website and open a support ticket or forum topic. Software issues can be reported directly to the project GitHub issue tracker here:
Thank you for your support of the project.