[Ovmsdev] OVMS update

Julien Banchet jaxx at jaxx.org
Wed Dec 14 16:47:54 HKT 2016

Hi Mark,

Many Thanks for the update, I honestly can't wait as every single point of
features are great!

Just a couple of questions:
- Do you forsee a data envelope  to have on the mobile provider ? (payload
* rythme might go up) I suppose most of the things can(/will) be
configurable on the backend/provisionning side ("discard this"/"limit these
to once an hour"...)
- Will the backend be rewritten? I suppose it will have to, as this is
nothing alike before... What language will it be based on? Honestly, I have
loved Perl in the past, and even though I'm far from being Python fluent,
the latter might be a better pick in terms of adoption.

Again, Thanks !


On Wed, Dec 14, 2016 at 2:00 AM, Mark Webb-Johnson <mark at openvehicles.com>

> A short update on OVMS.
> We are working hard on OVMS v3. The development environment for the
> microcontroller we chose for v3 has finally stabilised to a point where we
> can rely on it. There will be a new revision of hardware silicon around the
> end of 2017Q1 and we'll most likely try to time the first production
> releases of OVMS v3 to use that as soon as it is available. But, the good
> news is that we have the production development environments available now,
> and the CAN driver (although early beta) is working well. All the
> components are finally in place and usable. This has caused us delays in
> our plans, but we are confident that our choice of microcontroller was the
> right one. This will give us a great platform for the future and most
> importantly allow us to keep costs down without being constrained by
> RAM/Flash memory storage (as was the case for the v2 PIC18 platform).
> Bluetooth and Wifi support are a bonus. Work on the firmware for OVMS v3 is
> ongoing, and we're hoping to release this to the open source team any day
> now. Some highlights of the coming features for OVMS v3 include:
>    - Use of the industry standard MQTT protocol, for easier third party
>    integration (in particular to IOT and home automation systems)
>    - Event driven model for scripting events in the car (such as
>    geofencing, homelink, charge settings, etc)
>    - 3G
>    - Wifi
>    - Bluetooth
>    - SD-CARD support
>    - Reduced power consumption, and low-power sleep modes
>    - Dramatically more RAM and FLASH memory, to overcome limits of PIC18
>    architecture used by OVMS v2
>    - Firmware updates via SD-CARD and USB, without any special
>    programming tools
>    - Over-The-Air (OTA) firmware updates via wifi and/or 3G
>    - Expansion slot and port for extra functionality
> In the meantime, we continue to support OVMS v2. The hardware is still
> available on fasttech site, but we are over half way through what we think
> will be the very last batch.
> In other news, we have partnered with hologram.io to provide a cellular
> network for OVMS users (both v2 and v3). Early feedback from our users has
> been fantastic, and this is now running in a bunch of OVMS cars. Use of
> this is entirely optional, and the cost-effectiveness will depend on where
> you are in the world and what other cellular options you have. We're not
> forcing you to use Hologram; just making it easy for you to choose them if
> you want. OVMS v3 will come with hologram.io SIMs included as standard
> (but easily replaced if you choose not to use it). For OVMS v2 users in
> USA, with the imminent shutdown of the AT&T 2G network, we recommend
> Hologram.IO now. You can get SIMs from Hologram directly at
> https://hologram.io/store/, and Tom has penned an excellent write-up of
> how to switch to Hologram at https://www.idleloop.com/
> tesla/ovms/hologram.php.
> Regards, Mark.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20161214/e14fb226/attachment.htm>

More information about the OvmsDev mailing list