[Ovmsdev] 1.3.1

[Mark Webb-Johnson]

Brian,

Just make sure you've got an account on openvehicles.com - I'm assuming everyone there, who created an account after we sold out v1, wants a module and will be inviting in account registration order.

I don't think quantity will be a problem (like it was before). The only reason I'm making 20 first is to have a test production run then give it a few weeks before bringing in the next 100. These are now being 100% made by the factories, so much quicker to get stock,

Regards, Mark

On 15 Aug, 2012, at 10:24 PM, Brian Town <brian_town at hotmail.com> wrote:

> Mark,
> 
> Thanks for the update, especially related to the v2 hardware.  Is there a queue yet for the v2 hardware (beyond the initial 20 which are reserved)?  I'd like to get a place in line if there is!
> 
> Thanks,
> Brian
> 
> > From: mark at webb-johnson.net
> > Date: Wed, 15 Aug 2012 22:17:12 +0800
> > To: OvmsDev at lists.teslaclub.hk
> > Subject: [Ovmsdev] 1.3.1
> > 
> > 
> > Guys,
> > 
> > I'm back on the firmware (after a break doing v2 basic hardware and summer holidays away from my roadster - driving a horrible borrowed Honda Jazz - not fun).
> > 
> > I've just committed a bunch of changes to github on the way towards 1.3.1 firmware.
> > 
> > The purpose of this next firmware version is to address a couple of niggly bugs, try to improve reliability of the GPRS and GSM connections (including adding linear-backoff timers for certain states like server unreachable and vehicleid/password incorrect), add support for timed charge control, and add support for the new v2 base hardware.
> > 
> > I hope to have the code for this done within the next few days (about 75% of it got committed tonight), aiming for a release (after testing) around the end of this month.
> > 
> > The v2 base hardware is done and with the factory. I'm doing a first test run of 20 modules (pretty much all of which have been reserved), followed by a second run of 100. I'm really sorry this has taken so long, but there were some issues with getting the prototypes working (our end as well as the factory / board fabricator). It is looking good now, and I'm expecting to receive the first batch within the next 10 days. The modules themselves are looking really good, and the cable arrangement is very flexible and reliable.
> > 
> > As the new v2 base hardware processor has more flash memory, and some other functions (such as A/D converter for reading +12V voltage level), I've decided to split the firmware as a compile time build environment variable. This means we can build both sets of firmware from the same sources, but take advantage of v2 hardware features where available. The v2 hardware features are really for cars other than the Tesla Roadster, so no need for Roadster users to upgrade, and we'll continue to support both versions.
> > 
> > If there are any ideas for 'little' things to go in 1.3.1, please let me know. It would be nice to try to capture the CAN bus message for alarm sounding, but I'm not sure if I'll have time to do it. I'll try. If anyone else has time, let me know. I think all we need is to be able to pickup that message and relay it on as an SMS/IP PUSH alert.
> > 
> > Regards, Mark.
> > 
> > _______________________________________________
> > OvmsDev mailing list
> > OvmsDev at lists.teslaclub.hk
> > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20120815/361c3083/attachment.htm>