- OvmsDev - Open Vehicles

Re: [Ovmsdev] The meaning of life and universe
by Gianluca Magalotti 22 Oct '14

22 Oct '14

And with this feeling we can look at the sky! :-) Gianluca Magalotti ITIL® 2011 Foundation Certified Cobit 5 Foundation Certified email: gianluca(a)magalotti.net Mob: +39 3474 3474 25 Linkedin: http://www.linkedin.com/in/gianlucamagalotti/ > Il giorno 22/ott/2014, alle ore 15:37, ovmsdev-request(a)lists.teslaclub.hk ha scritto: > > I think that is about 0.39 seconds a day, but we have solved the answer to life the universe and everything.

1 0

Forums
by Mark Webb-Johnson 21 Oct '14

21 Oct '14

Just a short note to say that I've had to take the forums on www.openvehicles.com offline. A few reasons: Most of the questions there were support questions, and the questions weren't getting answered. The forums were almost never used - just one or two posts a week. The forum module itself has very few features and no notification capability. Too many spammers signing up for accounts so that they can write forums posts about how much their sister is earning per hour. Bottom line is that it was just wasting too much time, and that is time better spent on the project itself. I've kept the old content for the moment - just disabled it for everyone except administrators. Regards, Mark.

1 0

Re: [Ovmsdev] [Open-Vehicle-Monitoring-System] First implemention of net_fnbits NET_FN_CARTIME (1a97b92)
by Mark Webb-Johnson 21 Oct '14

21 Oct '14

My thinking is that losing 1 ms every second or so means 1,000 seconds (16 minutes) to lose 1 second. As we poll the GSM modem for clock once every 60 seconds that should be fine and we should maintain accuracy. The GSM modem includes a real-time clock, so even if it loses GSM connectivity it should still keep good time. P.S. There is a simple slight improvement I thought about last night. I use a 16bit unsigned integer to count milliseconds, adding 105 to it every 104.8576ms timer interrupt, and taking off 1,000ms every time it gets >1,000. Leading to an inaccuracy of 0.1424ms every timer tick. I could simply count 50ms instead, adding 5243 every timer tick of equivalent 5242.88 50ms chunks, and then taking off 50,000 every time if gets >50,000. That would lead to an inaccuracy of 0.12ms every timer tick. We could also mess around with the timer functions to try to get something more divisible into 1ms. But, with the GSM polling, I just don't think it will be necessary. Regards, Mark. On 21 Oct, 2014, at 2:55 pm, Gianluca <notifications(a)github.com> wrote: > After quick math every 7 interrupts you "loose" one ms. Maybe you could count interrupts and adjust ms count. To be more precise every 44 adjustments you should skip the increment. Let's say is a gregorian solution :) > > — > Reply to this email directly or view it on GitHub. >

1 1

Re: [Ovmsdev] Open Charge Map
by Christopher Cook 16 Oct '14

16 Oct '14

Actually, on that topic (almost) - we should discuss how OVMS users might checkin (or even auto-checkin) to OCM. That would help us track which locations people are using and the quality of their experience there. Are there any recent thoughts on this from the OVMS side? Currently there are no third party apps writing to the OCM API. Doing so currently requires at least authentication (via the web UI) - this is also the method used by the OCM mobile apps. There is the possibility of a quicker/simple login to OCM via third party apps by way of a security code emailed to the user (who would either be new to OCM or an existing user). Not massively secure (there are holes in the approach) but it would make it easy for third party apps to quickly authenticate. Alternatively we can provide URLs which OVMS users would open in a browser/webview which go on to use the standard mobile app or site. This is the easiest for OVMS apps to implement. Depends on what integration people would like to see? Chris J-C Saint-Pô <jcsaintpo(a)gmail.com> wrote: >_______________________________________________ >OvmsDev mailing list >OvmsDev(a)lists.teslaclub.hk >http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

9 47

Re: [Ovmsdev] [Open-Vehicle-Monitoring-System] SMS Response (#135)
by Tom Saxton 10 Oct '14

10 Oct '14

I saw this recently when working on configuring a V1 module running OVMS version 2.6.5/TR (the version on my firmware update page, http://www.idleloop.com/tesla/ovms/) This command: GPRS MOBILEDATA - returned: GPRS: APN:MOBILEDATA User: Password: GSM:AT&T GPRS: OK Server: Connected OAT +CIPSHUT Also, this command: SERVER 54.243.136.230 PASSWORD - returned: Server IP:54.243.136.230 Password:PASSWORD Paranoid:AT+CIPSHUT I haven't tried it with a current build, or with a V2 unit. Tom On 10/9/14, 10:51 AM, "Gianluca" <notifications(a)github.com> wrote: >Some OVMS users are experiencing strange responses to SMS configuration. >Last row of every SMS like MODULE, SERVER and GPRS is missing the last >character and some AT command is appended instead. >For Instance. a MODULE SMS command would return >Module: >... >... >Notifications:SMAT+###### (with ##### replaced by some AT command string). >instead of >Notifications:SMS >It Sounds to me like a not properly null terminated string but I've been >not able to recreate the problem. Users state it disappear after >reflashing or moving GPRS/GSM switch (but I'm not sure about it). > >Reply to this email directly or view it on GitHub ><https://github.com/openvehicles/Open-Vehicle-Monitoring-System/issues/135 >>. >{"@context":"http://schema.org","@type":"EmailMessage","description":"View > this Issue on >GitHub","action":{"@type":"ViewAction","url":"https://github.com/openvehic >les/Open-Vehicle-Monitoring-System/issues/135","name":"View Issue"}}

1 0

Re: [Ovmsdev] Twizy Trip sms report
by Gianluca Magalotti 04 Oct '14

04 Oct '14

Thankyou Michael. I just sow the 3.3.1 changelog yesterday night and made a post on the Italian forum. And yes, manual is missing the feature (the tesla manual appendix reports feature 10 as n/a). Btw can we provide a single documentation for installation and basic commands? Il 04/ott/2014 06:00 <ovmsdev-request(a)lists.teslaclub.hk> ha scritto: > 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. Twizy Trip sms report (Gianluca Magalotti) > 2. Re: Twizy Trip sms report (Michael Balzer) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 3 Oct 2014 08:04:59 +0200 > From: Gianluca Magalotti <gianluca(a)magalotti.net> > Subject: [Ovmsdev] Twizy Trip sms report > To: "ovmsdev(a)lists.teslaclub.hk" <ovmsdev(a)lists.teslaclub.hk> > Message-ID: <D0BF5758-CC97-4A77-9D00-32896B97FBAE(a)magalotti.net> > Content-Type: text/plain; charset=utf-8 > > Some Italian users are asking if there is any way to disable SMS reporting > trip stats. In fact SMS in Italy are often paid (even 20 ?cents per > message). > If this would not possible could be implemented in a future version? > > > Thanks > Gianluca > > ------------------------------ > > Message: 2 > Date: Fri, 03 Oct 2014 21:33:46 +0200 > From: Michael Balzer <dexter(a)expeedo.de> > Subject: Re: [Ovmsdev] Twizy Trip sms report > To: ovmsdev(a)lists.teslaclub.hk > Message-ID: <542EFA1A.6050501(a)expeedo.de> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Gianluca, > > have you seen... > > Twizy update V3.3.1: > > - Bugfix: RT-PWR-Log speed/accel stats output fixed for 0 distances > (charge/onoff) > - Now checking for carbits vehicle alert & (new) info suppression > (info suppression applies to trip reports) > > Framework: > - Added car bits flag FEATURE_CB_SVINFOS (0x10): 1 = suppress vehicle > informational notifies (currently only used on Twizy) > > ...? > > Quite possibly missed including a note on this in the manual... > > Regards, > Michael > > > Am 03.10.2014 um 08:04 schrieb Gianluca Magalotti: > > Some Italian users are asking if there is any way to disable SMS > reporting trip stats. In fact SMS in Italy are often paid (even 20 ?cents > per message). > > If this would not possible could be implemented in a future version? > > > > > > Thanks > > Gianluca > > _______________________________________________ > > 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 > >

2 1

Twizy Trip sms report
by Gianluca Magalotti 03 Oct '14

03 Oct '14

Some Italian users are asking if there is any way to disable SMS reporting trip stats. In fact SMS in Italy are often paid (even 20 €cents per message). If this would not possible could be implemented in a future version? Thanks Gianluca

2 1

MBED v3 announcement
by phil hochstetler 01 Oct '14

01 Oct '14

Given the recent discussion about mbed, this announcement about mbed v3.0 seems timely: https://developer.mbed.org/blog/entry/Announcing-our-plans-for-mbed-v30/ Phil H.

1 0

Twizy release 3.5.0
by Michael Balzer 30 Sep '14

30 Sep '14

Hi everyone, just checked in Twizy release 3.5.0: https://github.com/openvehicles/Open-Vehicle-Monitoring-System/commit/b6d21… This release adds a kickdown function to the Twizy to make eco profiles more usable. If using a profile with reduced drive level, a kickdown will temporarily raise the level to 100%. See manual for details. Regards, Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

3 4

CFG commands on RT_Production
by Julien NOZAIS 26 Sep '14

26 Sep '14

Hello everybody, my name is Julien, I am a soon-to-be CS engineer from France. I am working on an internship project that requires to modify the Renault Twizy's internal parameters via the CAN bus. I am very interested in the work done by the OVMS developers on that topic. In the past few weeks I have learned quite a lot about Twizy's SEVCON through the documentation and also by browsing through the OVMS car module's source code. Thanks a lot for all the documentation and advice you provide! I have some questions that I hope you guys can answer to (TL;DR below). MSG commands My current situation is that I have upgraded my OVMS module to 2.6.5 firmware with the .hex file provided on GitHub. I have also successfully connected to the module via SMS commands and Android App. Most of the basic commands that I tried worked. I say 'most', because I have set the #15 'write' bit to '1' and cleared the #14 bit as well. However, I don't seem to be able to send CFG commands via SMS (such as CFG SPEED <speed> for example) in the way that the twizy manual describes it. All I get are push notifications forwarding my SMS to the app. Is there something I'm missing? :( Compilation issues On an other topic, I have installed MPLABX and acquired the C18 compiler thanks to someone hosting it on a personal website (note: it's nowhere to be found in the microchip archive and static links sourcing it on the website are all dead at the moment). I have tried to compile the V2_RT_Production from the last source available on GitHub. However I ran into compilation errors in vehicle_twicy.c, caused by what I assumed were missing '#define' directives (i.e 'OVMS_TWIZY_BATTMON' & 'OVMS_TWIZY_CFG'). I didn't see them referenced anywhere but in the version comments at the start of the file: > - Twizy battery monitor compiler switch: OVMS_TWIZY_BATTMON So I added these two, but I don't know if they were supposed to be left out. Incidentally, I ran into a new compilation error: > Error - section '.romdata_net_msg.o' can not fit the section. Section '.romdata_net_msg.o' length=0x000000a8 Which as I understand is an issue relative to the length of the file being too large to pass compilation. I'm fairly new to PIC programming, so I may have misinterpreted some of these compilation errors. I imagine there is a lot of work in progress on the code so maybe the version I pulled was not a stable one ? Any remark or advice is most welcome! DIAG communication Probably noob error: I tried connecting through the DIAG port with minicom. I set minicom to 9600 Bds / 8N1, as specified in the developers documentation, but had no success. I think that I'm closed since since I received data, but it was just gibberish encoding errors. Since these errors are often caused by a wrong baud setting, I tried different baud values without success. I hope somebody can point out something that I could have missed. I have read the manual, but, well... you never know. TL;DR - Can I send SMS CFG commands to Twizy 2.6.5 firmware? - Is there any specific advice on how to get started on OVMS source and compile it for the Twizy? - Communication with DIAG port on minicom only speaks gibberish although I have (supposedly) correct settings. Could I have missed something? Anyway, I hope I'm not bothering you with all my questions. Sorry for the long e-mail. I look forward to reading from you ! Julien Nozais

2 5