[Ovmsdev] Twizy release 3.0.2

Sun Jan 19 09:44:15 HKT 2014

OK, just pushed the change to extended mode compilation.

I had a to make a small change to vehicle_twizy for the production build (where the CFG define is not set).

The change to temperatures (8 to 16 bit) has also been made.

I also added some code to call the vehicle idle poll and 1/10th second ticker functions from within the 100ms utils.c delay. The issue here is that the 100ms delay may be called from within the functions, so there is a guard against recursion. Hopefully this didn’t break anything.

I’m going for a drive soon, with this code in place. If there are no problems, I’ll build an official 2.6.2 .hex for wider testing.

Regards, Mark.

On 18 Jan, 2014, at 10:14 pm, Michael Balzer <dexter at expeedo.de> wrote:

> I implemented an "offline" cfg reset method -- which btw unfortunately could also be used by any thieve... well, maybe not quite "any" though ;-)
> 
> 
> Am 18.01.2014 13:55, schrieb Mark Webb-Johnson:
>> Sounds like it might be cool to hook this into the valet msg. Valet ON is save limit then set speed limit to 10kph. Valet off is restore limit. Lock/Unlock could be similar.
>> 
>> I would just be a little concerned if gsm connectivity was lost after lock/valet. Without connectivity, you couldn't unlock and it would be a real slow drive to the next cell tower :-)
>> 
>> Mark
>> 
>> On 18 Jan, 2014, at 8:14 pm, Michael Balzer <dexter at expeedo.de> wrote:
>> 
>>> Nikki,
>>> 
>>> nice ideas.
>>> 
>>> You can reduce available power simply by a CFG DRIVE command, i.e. "CFG DRIVE 10" will reduce available power to 10%.
>>> 
>>> To completely disable it, "CFG DRIVE 0" should also work -- haven't tried that yet.
>>> 
>>> Another option if valet mode still needs the power (i.e. hills): "CFG SPEED 10" will reduce maximum speed to 10 kph.
>>> 
>>> Regards,
>>> Michael
>>> 
>>> 
>>> Am 18.01.2014 11:57, schrieb Nikki Gordon-Bloomfield:
>>>> Michael,
>>>> 
>>>> Great work! 
>>>> 
>>>> I wonder if there would be a way to use this as a valet mode option? Really reduce motor settings etc? 
>>>> 
>>>> Yes, its no Tesla, but more might be useful for some.
>>>> 
>>>> Also, could this be used to make the twizy more secure? 
>>>> 
>>>> I know it has an immobilizer but no locks on the doors, making it perhaps a target for thieves?
>>>> 
>>>> Could OVMS he used to lock down a twizy with really poor parameters?
>>>> 
>>>> In other words, if someone does defeat the lock and turn it on, this could event them from moving the car?
>>>> 
>>>> On 18 Jan 2014 08:27, "Michael Balzer" <dexter at expeedo.de> wrote:
>>>> Thanks :-)
>>>> 
>>>> There should also be a visible change in crash history records, my crash count with the new version is still 0.
>>>> 
>>>> The extended mode also has been running 100% fine during the last days, so I can also check in some more Twizy & CANopen functionality later on :-)
>>>> 
>>>> Btw, I read about the Mia also using a SEVCON Gen4. So if there's a Mia OVMS development going on somewhere: the Twizy tuning commands should be easily portable, should just need to be adapted to the other defaults.
>>>> 
>>>> Regards,
>>>> Michael
>>>> 
>>>> 
>>>> 
>>>> Am 18.01.2014 03:46, schrieb Mark Webb-Johnson:
>>>> Wow, just wow!
>>>> 
>>>> I’ve been running this (2.6.x code, with Michael’s interrupt handling enhancements, and a switch to extended mode compilation) in my car and the difference is amazing.
>>>> 
>>>> The best indicator I have of interrupt performance is the digital speedo in the Tesla Roadster. That relies on picking up the transmission of a single CAN bus message, then following it up very quickly with a sequence of 3 override CAN bus messages. Previously it was ok, but now (with the new Interrupt code) it seems much much smoother.
>>>> 
>>>> Well done, Michael! Great contribution.
>>>> 
>>>> I’ll be fixing up the compiler warnings (just a difference in ‘static’ vs ‘auto’ storage mode in extended mode) and then will commit the switch to extended mode to the repository as 2.6.2. I should get this done today.
>>>> 
>>>> Regards, Mark.
>>>> 
>>>> On 15 Jan, 2014, at 6:19 am, Michael Balzer <dexter at expeedo.de> wrote:
>>>> 
>>>> Mark,
>>>> 
>>>> I now also have compiled in extended mode (got no choice). I only get some warnings about static function args, not sure if they need to be static, doesn't seem so.
>>>> 
>>>> First tests have been completely fine in both diag and live mode, so I'll use the extended mode firmware during the next days to see if anything goes wrong.
>>>> 
>>>> Regards,
>>>> Michael
>>>> 
>>>> 
>>>> Am 08.01.2014 14:18, schrieb Mark Webb-Johnson:
>>>> Not sure if we can use extended mode or not - if we can, it will give us a lot of breathing room. If I enable extended mode, everything compiles just fine (all configs). Supposedly the PIC18F2685 supports the C-optimised extended instruction set.
>>>> 
>>>> Regards, Mark.
>>>> 
>>>> -- 
>>>> Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
>>>> Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
>>>> <dexter.vcf>_______________________________________________
>>>> 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
>>>> 
>>>> -- 
>>>> Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
>>>> Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
>>>> 
>>>> 
>>>> _______________________________________________
>>>> 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
>>> 
>>> -- 
>>> Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
>>> Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
>>> <dexter.vcf>
>>> _______________________________________________
>>> 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
> 
> -- 
> Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
> Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
> <dexter.vcf>_______________________________________________
> 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/20140119/f2dfe096/attachment.htm>