- OvmsDev - Open Vehicles

Pickit 3
by Paul Churchley 10 Jan '14

10 Jan '14

Thanks to all who offered advice/help. I have now ordered a Pickit 3 programmer from RS Components - GBP31 That will arrive Monday so I have allocated some time Tuesday to get the first one up and running. I am doing the Ampera first. Paul

1 0

Re: [Ovmsdev] Getting OVMS next week
by Denis KRAUTH 09 Jan '14

09 Jan '14

If you find the Day to trigger the preheating on the Ampera, you will entrer in the hall of fame :-) Denis. Paul Churchley <paul(a)churchley.org> a écrit : >_______________________________________________ >OvmsDev mailing list >OvmsDev(a)lists.teslaclub.hk >http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

1 0

Getting OVMS next week
by Paul Churchley 09 Jan '14

09 Jan '14

I have ordered an OVMS kit for my 2011 Mk1 Leaf and also my 2012 Vauxhall Ampera. Once I get them up and running I shall be looking to see how I might help with development. Any suggestions please? :-) I have gone with GeoSIM on both. I will need a programmer to update the firmware... can I get one in the UK? My particular interest with OVMS is interfacing to other charge station databases such as OCM. I might be able to provide a testing server too (Windows or Linux) if that might help. Paul

5 12

Re: [Ovmsdev] OvmsDev Digest, Vol 24, Issue 17
by Nacho 08 Jan '14

08 Jan '14

An interesting move from Google Android http://www.openautoalliance.net/#about Best regards Dr. Eng. Ignacio González Alonso. On Wed, Jan 8, 2014 at 2:19 PM, <ovmsdev-request(a)lists.teslaclub.hk> wrote: > Send OvmsDev mailing list submissions to > ovmsdev(a)lists.teslaclub.hk > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > or, via email, send a message with subject or body 'help' to > ovmsdev-request(a)lists.teslaclub.hk > > You can reach the person managing the list at > ovmsdev-owner(a)lists.teslaclub.hk > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of OvmsDev digest..." > > > Today's Topics: > > 1. Re: Twizy release 3.0.2 (Michael Balzer) > 2. Re: Twizy release 3.0.2 (Mark Webb-Johnson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 08 Jan 2014 14:11:12 +0100 > From: Michael Balzer <dexter(a)expeedo.de> > Subject: Re: [Ovmsdev] Twizy release 3.0.2 > To: ovmsdev(a)lists.teslaclub.hk > Message-ID: <52CD4E70.6090608(a)expeedo.de> > Content-Type: text/plain; charset="iso-8859-15"; Format="flowed" > > Mark, > > can't look at the config right now, but if V2_* > contain everything, I think that will be too much > on both ROM and RAM size now. > > I had a similar problem with V2_RT before > disabling logging and acc. > > Maybe you can get it to build if you disable the > Twizy battery monitor and the new cfg command. > > Regards, > Michael > > > > Am 08.01.2014 13:50, schrieb Mark Webb-Johnson: > > Michael, > > > > I added the OVMS_POLLER as necessary, and > > committed that code. But, not getting much luck > > compiling this. > > > > The single vehicle configs (V1, V2_TR and V2_RT) > > compile ok. > > > > But, V2_EXPERIMENTAL gives the following error: > > > > Error - section 'MATH_DATA' can not fit the > > section. Section 'MATH_DATA' length=0x00000014 > > > > > > and V2_PRODUCTION gives: > > > > Error - section '.tmpdata' can not fit the > > section. Section '.tmpdata' length=0x00000024 > > > > > > I'm not sure why it is complaining about > > .tmpdata, when it should now be using > > high_isr_tmpdata for the code. > > > > I'll keep looking, but I'm not sure if this > > approach will be so easy... > > > > Regards, Mark. > > > > On 8 Jan, 2014, at 8:08 am, Mark Webb-Johnson > > <mark(a)webb-johnson.net > > <mailto:mark@webb-johnson.net>> wrote: > > > >> Michael, > >> > >> Nice. I'll have a play with it this weekend. > >> > >> Regards, Mark. > >> > >> P.S. I was aware (recently) of the ISR stuff, > >> but didn't realise the fix was so (relatively) > >> easy. Thanks for handling this. > >> > >> On 5 Jan, 2014, at 9:22 am, Michael Balzer > >> <dexter(a)expeedo.de <mailto:dexter@expeedo.de>> > >> wrote: > >> > >>> Hi everyone, > >>> > >>> I have integrated the latest Twizy release > >>> 3.0.2 with framework version 2.6.1 and pushed > >>> it into the main repository. > >>> > >>> Please note: > >>> > >>> > >>> 1) I had to introduce a new preprocessor flag > >>> for the vehicle polling system: OVMS_POLLER > >>> > >>> The Twizy firmware will just barely compile > >>> with it enabled, but not work (poll0() will > >>> not be called). Anyway it doesn't need the > >>> polling system, so I disabled it instead of > >>> changing something. > >>> > >>> You'll need to add the flag to your build > >>> configurations if you use the polling. > >>> > >>> > >>> 2) I have included a major stability > >>> improvement for the interrupt codes. With > >>> deeper nesting and stack usage, my crashes > >>> multiplied. On checking everything I stumbled > >>> across the info, that calling functions is > >>> among the worst things to do inside an ISR. > >>> The compiler needs to save the complete > >>> context including all temporary data on the > >>> stack, which is both very time consuming and > >>> can use a lot of stack space. > >>> > >>> There's a good info on this topic on the web: > >>> http://www.xargs.com/pic/c18-isr-optim.pdf > >>> > >>> I've implemented a separate tmpdata section > >>> for both low and high priority ISRs based on > >>> this info and had not a single crash since > >>> then. Also no CAN data has been lost since the > >>> change and the module has become rock steady > >>> on the GSM and GPS connection. > >>> > >>> The downside is, it needs some additional RAM > >>> for the ISR tmpdata sections. As both the ISR > >>> main/entry functions and all called functions > >>> need to use the separate tmpdata section, I > >>> changed all vehicle modules accordingly. > >>> Please check if everything still works. > >>> > >>> > >>> With acc and logging disabled and all Twizy > >>> features activated I now get... > >>> > >>> RAM Used: 3152 (0xC50) Free: 176 (0xB0) > >>> Flash Used: 97756 (0x17DDC) Free: 548 (0x224) > >>> > >>> So I'm approaching the final frontier... but > >>> in another way as expected, I always thought > >>> RAM is my problem... > >>> > >>> Regards, > >>> Michael > >>> > >>> > >>> > >>> Am 31.12.2013 13:39, schrieb Michael Balzer: > >>>> Hi everyone, > >>>> > >>>> sorry for dropping behind/off last months, > >>>> lots of work. > >>>> > >>>> I've not been able to catch up on the > >>>> framework advances yet, but nevertheless > >>>> wanted to announce a major Twizy update I'm > >>>> currently working on. > >>>> > >>>> This update enables access to the SEVCON > >>>> controller configuration of the Twizy. > >>>> > >>>> Low level commands allow read and write > >>>> access to all SDOs. Macro commands allow to > >>>> easily change common settings like maximum > >>>> speed, maximum torque, power and recuperation > >>>> levels and drive profile characteristics. > >>>> > >>>> There is a potential benefit for other > >>>> vehicles from this development: I've done a > >>>> basic CANopen SDO protocol implementation for > >>>> this. The implementation is specific to the > >>>> Twizy only because it's limited to addressing > >>>> just node #1 and currently only supports > >>>> expedited SDO transfers, not segmented. The > >>>> node id could easily be made variable, and > >>>> segmented transfers should be not much of a > >>>> problem. It still is nowhere near a complete > >>>> CANopen protocol implementation, but allows > >>>> SDO reading and writing. Tell me if this > >>>> sounds useful for other vehicles. > >>>> > >>>> As I've not yet integrated your latest work, > >>>> I've pushed this into my Github repository > >>>> first: > >>>> > >>>> https://github.com/dexterbg/Open-Vehicle-Monitoring-System > >>>> > >>>> > >>>> I'll also wait for some more user feedback > >>>> before going on, and I also want to implement > >>>> support for the Twizy 45 before merging this in. > >>>> > >>>> Just wanted to let you know in case you > >>>> wonder about rising OVMS hardware sales > >>>> lately ;-) > >>>> > >>>> Oh, and I wish you all a happy new year! > >>>> > >>>> Regards, > >>>> Michael > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> OvmsDev mailing list > >>>> OvmsDev(a)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(a)lists.teslaclub.hk > >>> <mailto:OvmsDev@lists.teslaclub.hk> > >>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > >> > >> _______________________________________________ > >> OvmsDev mailing list > >> OvmsDev(a)lists.teslaclub.hk > >> <mailto:OvmsDev@lists.teslaclub.hk> > >> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > > > > > > > > _______________________________________________ > > OvmsDev mailing list > > OvmsDev(a)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 > >

1 0

OVMS 101 hangout!
by Nikki Gordon-Bloomfield 08 Jan '14

08 Jan '14

Folks, We've had the responses and it seems like Saturday, January 4 is the best time and 5pm GMT is the best time for the hangout! I'm assuming those of you in different timezones are more than happy doing the required math(s) to ensure you're around at the right time! Here's my outline of the event. Please step up to the plate and 'sign up' to present different parts of the event. I'm not expecting any one person to run the 'complete' section, as I'm happy to be the host/compare. But I need to know who I'm talking with mostly in that section. *Part one: What is OVMS?* *- *One of us, I'm suggesting Mark, should do a practical overview of OVMS, what it does, and why it's needed, as well as the cars it currently works with. Ideally, some screen shots and/or live demonstrations would be good. It's also really important to tell people how it differs from OEM's telematics, and how/why people may want to use it instead of them. *Part two: How do I get OVMS?* *- Basic *walkthrough on how to get hold of OVMS kit, along with 'what you'll need' for each main car. Talk about the various websites you can visit to buy the hardware, and recommendations for SIM cards. It's important in this section to differentiate between those who want to develop/write for OVMS, and those who just want to plug in and forget. *Part three: How do I set it up? * -- This should be a walk through from downloading the iOS and/or Android apps to plugging the final setup into the car's ODBII port. Perhaps we could split this into further sections: - What will you need - How to open up the kit - How to put the SIM card in - First connection - etc etc. *Part Four: Using and understanding the app. * Since this is partly different for each vehicle, we'd benefit from having some Tesla, Twizy and Volt specific sections here. But open to thoughts. *Part Five: Questions* We can either have a formal Q&A at the end of the hangout, or we could answer them throughout. My aim is to only allow those who have already volunteered (and those who have extra stuff to add now) in on the actually video side of the hangout. Everyone else will be able to watch. If we meet on Saturday ten minutes before the hangout is due to start, this should all be possible without too many problems. I will of course, need everyone's google ID so I can invite them in. Nikki.

5 10

Model S Can Bus Specs
by Oliver Weidmann 08 Jan '14

08 Jan '14

A good new year to everyone on this mailing list. I finally found some time to play with my Model S and search for bus wires. Well here are some details: The bus connector is located underneath the touch screen (grab the storage shelf hole and pull STRAIGHT down). The connector is the same as in the Roadster. When reading the bus be sure to attach CAN HIGH, CAN LOW and CAN GROUND (you can use normal GND, see image). If you don't use CAN GROUND, the car will get confused. The Roadster doesn't care if you use CAN GROUND, but Model S seems to be a bit sensitive on this topic. Also be careful with the +12V pin. If you produce a short your instrument panel screen will eventually go black as they seem to share the same fuse (which is the 5A fuse #49 in fuse box #2). Ok, once all wires are in place and the car is still running, it's time to read some data. Bus speed is 500 Kbit/s (vs. 1Mbit/s in the Roadster). A fist quick look at the data showed me the following: ID 2C8 looks like the actual charge settings. 67 32 = min Standard 67 5A = max Standard 67 63 = one tick before max Range 27 64 = max Range Obviously the second bit bit represents the percentage of the charge settings (32h=50dec=50%, 64h=100dec=100%). It seems to be a readout only variable, as sending messages to ID 2C8 didn't change the charge settings. Maybe this is the first step for OVMS for Model S? Well, we'll have to see ;) regards Oliver --- Diese E-Mail ist frei von Viren und Malware, denn der avast! Antivirus Schutz ist aktiv. http://www.avast.com

2 4

Showing Km while unit set to miles
by Thomas Bergo 06 Jan '14

06 Jan '14

Hi, A OVMS user on the i-Miev forum in US with a i-Miev have experienced the following issue: *In the notifications, I have my units set to miles, though the Odometer reading is still in Km. Range readings are correct.* He are using the v2.5.5 FW downloaded from Mark's GitHub repository. Anyone else experienced this?

3 3

Re: [Ovmsdev] OVMS 101 hangout!
by Denis KRAUTH 03 Jan '14

03 Jan '14

Hi everybody, If it can be of any help, I wrote a complete tutorial (in french) for the Ampera/Volt here : http://www.amperiste.fr/forums/viewtopic.php?f=39&t=1115 Denis. Paul Churchley <paul(a)churchley.org> a écrit : >_______________________________________________ >OvmsDev mailing list >OvmsDev(a)lists.teslaclub.hk >http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

1 0

Re: [Ovmsdev] OVMS 101 hangout!
by Bennett Leeds 02 Jan '14

02 Jan '14

>From my experience helping people to get OVMS running, I think we should make sure the following are covered: 1) Confirming the position of the GPRS slide switch. 2) Explaining the differences between the vehicleID, 2 usernames, and 4 different passwords that need to be entered. (Bet you can't name all 4 passwords off the top of your head!) 3) Use of the OVMS provisioning web page. 4) Understanding the OVMS module's LED status blink codes. 5) Understanding the different antenna statuses on the smartphone apps. Have we identified any cars that have OVMS hardware installed but not yet provisioned, so that we can run through at least one example? Do we have the ability to show input/output from SMS on a smartphone or to stream what the smartphone app is showing? - Bennett On Wed, Jan 1, 2014 at 8:30 AM, <ovmsdev-request(a)lists.teslaclub.hk> wrote: > Send OvmsDev mailing list submissions to > ovmsdev(a)lists.teslaclub.hk > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > or, via email, send a message with subject or body 'help' to > ovmsdev-request(a)lists.teslaclub.hk > > You can reach the person managing the list at > ovmsdev-owner(a)lists.teslaclub.hk > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of OvmsDev digest..." > > > Today's Topics: > > 1. OVMS 101 hangout! (Nikki Gordon-Bloomfield) > 2. Re: OVMS 101 hangout! (Paul Churchley) > 3. Paul Churchley added you to his circles and invited you to > join Google+ (Google+) > 4. Re: OVMS 101 hangout! (J-C Saint-P?) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 1 Jan 2014 12:40:30 +0000 > From: Nikki Gordon-Bloomfield <Nikki(a)littlecollie.com> > Subject: [Ovmsdev] OVMS 101 hangout! > To: ovmsdev(a)lists.teslaclub.hk > Message-ID: > <CAOWoTn94PZjYeRmd9j+YBQm89uFWDWh_HUO7DaDw= > Nu42Vgahw(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Folks, > > We've had the responses and it seems like Saturday, January 4 is the best > time and 5pm GMT is the best time for the hangout! I'm assuming those of > you in different timezones are more than happy doing the required math(s) > to ensure you're around at the right time! > > Here's my outline of the event. Please step up to the plate and 'sign up' > to present different parts of the event. I'm not expecting any one person > to run the 'complete' section, as I'm happy to be the host/compare. But I > need to know who I'm talking with mostly in that section. > > > *Part one: What is OVMS?* > > *- *One of us, I'm suggesting Mark, should do a practical overview of OVMS, > what it does, and why it's needed, as well as the cars it currently works > with. Ideally, some screen shots and/or live demonstrations would be good. > It's also really important to tell people how it differs from OEM's > telematics, and how/why people may want to use it instead of them. > > *Part two: How do I get OVMS?* > > *- Basic *walkthrough on how to get hold of OVMS kit, along with 'what > you'll need' for each main car. Talk about the various websites you can > visit to buy the hardware, and recommendations for SIM cards. It's > important in this section to differentiate between those who want to > develop/write for OVMS, and those who just want to plug in and forget. > > *Part three: How do I set it up? * > > -- This should be a walk through from downloading the iOS and/or Android > apps to plugging the final setup into the car's ODBII port. > > Perhaps we could split this into further sections: > > - What will you need > - How to open up the kit > - How to put the SIM card in > - First connection > - etc etc. > > *Part Four: Using and understanding the app. * > > Since this is partly different for each vehicle, we'd benefit from having > some Tesla, Twizy and Volt specific sections here. But open to thoughts. > > *Part Five: Questions* > > We can either have a formal Q&A at the end of the hangout, or we could > answer them throughout. My aim is to only allow those who have already > volunteered (and those who have extra stuff to add now) in on the actually > video side of the hangout. Everyone else will be able to watch. > > > If we meet on Saturday ten minutes before the hangout is due to start, this > should all be possible without too many problems. I will of course, need > everyone's google ID so I can invite them in. > > Nikki. >

2 1

Paul Churchley added you to his circles and invited you to join Google+
by Google+ 01 Jan '14

01 Jan '14

Paul Churchley added you to his circles and invited you to join Google+. Click here to get started with Google+: https://plus.google.com/_/notifications/ngemlink?&emid=CLiVqqmC3bsCFUW4cgod… Google+ makes sharing on the web more like sharing in real life. ------------------------ You have received this message because Paul Churchley invited ovmsdev(a)lists.teslaclub.hk to join Google+. Click here to unsubscribe from these emails: https://plus.google.com/_/notifications/ngemlink?&emid=CLiVqqmC3bsCFUW4cgod…

1 0