March 2012 - OvmsDev - Open Vehicles

Re: [Ovmsdev] Digital Speedometer
by Mark Webb-Johnson 14 Mar '12

14 Mar '12

Piotr, I think there are 2 reasons you get the occasional amps display: When we use the modem, there is a delay loop, and we don't do the periodic speedo message transmission while in that loop. This is, at worst, once every minute or so. Occasionally, the car is going to win. At aggressive factor 5, I find it acceptable. The AMPS display is pretty rare. This can never be 100% perfect (unless we can find some way to suppress the car messages, which I doubt). Regards, Mark. P.S. Soapbox: this does show how easy it is to do. Tesla could do this _very_ easily in their firmware and that would be perfect. On 14 Mar, 2012, at 6:32 PM, 911carrera4(a)bluewin.ch wrote: > Hi Mark > > i've been usingthe speedo for 2 weeks. No problems. Only that > sometimes (for 1 second or so) it showed the amps insetead of the speed. > > Piotr > > ----Ursprüngliche > Nachricht---- > Von: mark(a)webb-johnson.net > Datum: 14.03.2012 10:10 > An: "ovmsdev(a)lists.teslaclub.hk"<ovmsdev@lists. > teslaclub.hk> > Betreff: [Ovmsdev] Digital Speedometer > > > A while ago, I had to turn off the digital speedometer in my car > as I had some issues that I wanted to be sure it wasn't causing. It turned out to be completely unrelated and caused by > a faulty PEM. Since replacement of the PEM, things have been perfect. > > I've now been running the digital speedo on > (setting 5) for the past 3 weeks and it had been flawless. > > Is anyone else running this feature? If so, have you seen > any issues and what is your opinion? Anyone else brave enough |-) > > Regards, Mark > > _______________________________________________ > OvmsDev mailing list > OvmsDev(a)lists.teslaclub.hk > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > > >

1 0

Digital Speedometer
by Mark Webb-Johnson 14 Mar '12

14 Mar '12

A while ago, I had to turn off the digital speedometer in my car as I had some issues that I wanted to be sure it wasn't causing. It turned out to be completely unrelated and caused by a faulty PEM. Since replacement of the PEM, things have been perfect. I've now been running the digital speedo on (setting 5) for the past 3 weeks and it had been flawless. Is anyone else running this feature? If so, have you seen any issues and what is your opinion? Anyone else brave enough |-) Regards, Mark

1 0

Car firmware version
by Mark Webb-Johnson 13 Mar '12

13 Mar '12

Guys, We've received a few questions recently about whether the car firmware needs to be updated or not, and basically, what version of firmware am I running? It is fairly easy to add a small feature to the server that when the car sends it the firmware version, and the version is < 1.2.0, it sends a PUSH notification to the Apps of that car saying (a) the version of firmware in the car, (b) a reminder that the firmware needs to be updated to v1.2.0 or later. We could limit this to once every week or so (or until the server is restarted). This seems like a good idea, as everyone should really be updating to v1.2.0 to get the full functionality. We could also do something similar if the user connects to the wrong server (ie; their account says TMC server, but they connect to WWW openvehicles.com server). Any objections? Regards, Mark.

2 1

v1.2
by Mark Webb-Johnson 13 Mar '12

13 Mar '12

I've just committed some revisions to the user guide for OVMS in the Tesla Roadster and updated it to v1.2. This completes the v1.2 work, and I have formally branched v1.2 on github so we have a stable reference point in future. You can download the new user guide direct from github at: https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/O… The guide contains instructions for installing the module in the car, as well as initial setup for access. It has been updated to match the features in the v1.2 car firmware, and latest GSM/GPRS hardware switch on the car module. Thanks to everyone involved in development, testing and just using the v1.2 firmware and OVMS. This, quite simply, would not have been possible without you all. Now, onwards to v1.3 and beyond ;-) Let's get social. Regards, Mark.

1 0

iOS App v1.2.0
by Mark Webb-Johnson 12 Mar '12

12 Mar '12

http://itunes.apple.com/us/app/open-vehicle/id490098531 The iOS App v1.2.0 has been approved by Apple, and should appear on the iTunes App stores around the world within the next few hours. Those users with the app already installed will be prompted to update. This version includes full support for the v1.2.0 car firmware and functions such as starting/stopping charge, changing charge mode and current, lock/unlock car, valet mode on/off, features, parameters, etc. It also includes new graphics and a more polished look-and-feel (with thanks to Felix for all his hard work on this). Please note that you should ensure you are running car firmware v1.2.0, or later, to get the full functionality of this, as well as the latest Android, App. Regards, Mark.

3 3

Transport Evolved
by Mark Webb-Johnson 10 Mar '12

10 Mar '12

Join Nikki Gordon-Bloomfield from Green Car Reports, Michael Thwaite from TeslaMotorsClub, and guest Mark Webb-Johnson from the Open Vehicle Monitoring System project as they discuss the week’s news in the world of electric cars, including the latest from the Geneva Motor Show, The Open Vehicle Monitoring System and much more.. http://www.transportevolved.com/transport-evolved-episode-92-the-anti-brick

1 0

Module stops working after couple of days
by Wido den Hollander 08 Mar '12

08 Mar '12

Hi, About a week ago I was able to install the module and get my own server up and running. Everything seemed to work fine from the beginning, but after about 36 hours the module died. First I thought my prepaid SIM-card had ran out of credits, but that was not the case. A manual reboot of the module was needed and it started working again. Yesterday I opened the app and saw "Last update 8 hours ago" Again, a reboot of the module was enough. I checked the LED's and the first time GREEN was solid ON and RED was flashing slowly, that is normal. The second time the GREEN LED was off and only the RED one was blinking. I don't think it's a problem of GSM reception, the module even worked without the antenna while lying on the floor of the car. GSM reception is however very good here in the neighborhood, no high buildings and it's a very dense network. It's also weird that the module doesn't come back online. If it was a short disruption it could be a connection problem, but being offline for 8 hours is long. Has anyone seen this behavior? Thanks, Wido

3 14

Re: [Ovmsdev] 0% SOC Reported in v1.5 Roadster
by Mark Webb-Johnson 07 Mar '12

07 Mar '12

Jack, Tom, Yep, Jack is right. It is feature #14. 0x0e. I seem to have get hexed. P.S. Tom's problem has been narrowed down to a faulty PIC board. The soldering seems ok, so probably the CAN bus driver chip. The module doesn't work in a 2.x roadster either. We're sending him a new board (I'm going to QC one tonight).. On 7 Mar 2012, at 3:34 PM, Jack West wrote: > Tom, > > Carbits is actually feature 14 and would need set to be set to 1 for a 2008 Roadster. > > Feature 15 set to 1 is to enable writing to the CAN bus. Set to 0 is 'listen' only. > You only need to do this once. > > So > SMS > FEATURE 15 1 (allows you to do all the fun stuff) > FEATURE 14 1 (because you have a 2008) > > That should do it (once you get the unit working). If you are using the new iPhone app you can do it from the Cars/I/Control tab. > > I don't think Feature 12 is anything yet. > > Jack > > > > On Mar 6, 2012, at 3:45 PM, Mark Webb-Johnson <mark(a)webb-johnson.net> wrote: > >> Tom, >> >> Scott451's original (ground breaking) post is at: >> >> http://www.teslamotorsclub.com/showthread.php/4388-iPhone-app/page2?p=49456… >> >> He talks there about the 2008 roadster, and confirms 1MHz bus speed. >> >> Your confirmation of the wales gps location and 0 SOC means the module is definitely not getting any can bus messages. >> >> It is either a faulty board, or some other incompatibility. >> >> Can you ask Cathy (she is your hardware support, right?) to check the continuity on connections on the MCP2551P and pins #23 and #24 on the PIC CPU? >> >> Do you know anyone close by with a 2.x roadster that you could plug the module in, to rule out 1.5 vs 2.x incompatibility? >> >> Regards, Mark. >> >> On 7 Mar 2012, at 1:35 AM, Tom Saxton wrote: >> >>> I did the "FEATURE 12 1" SMS command, but got no response. Are those >>> commands documented somewhere, or is it a "read the code" deal? (It is cool >>> to be able to read the code.) >>> >>> I get the same "not charging" status with the charge port door open. >>> >>> When I do a GPS command, I get back a link to 52.042460,-3.944089 which I >>> assume is the default position in Wales. >>> >>> So, it seems the OVMS module isn't getting any of these CAN messages. Is >>> there a way to tell if the board is getting any messages at all? >>> >>> With Cathy's help, I checked continuity and all four pins going to the MCU >>> board. They all check out, as do the four twin wires to the other connector. >>> >>> When plugged in, after the start up sequence, I get a solid green LED on >>> each board and a blinking blue LED on the modem board. >>> >>> Finally, I'm sure my diag port is functional as it has been working with my >>> Tattler (although the Tattler is going through some brain surgery right now >>> so I can't confirm that it's working today). >>> >>> BTW, I notice the generated GPS link takes you to a static map that can't be >>> scaled or panned. This makes it impossible to tell where the pin is if you >>> don't recognize any features in the static map. >>> >>> I like using a simpler link that gets you a fully functional map: >>> >>> http://maps.google.com/maps?q=52.042460,-3.944089 >>> >>> Also, I'm also not a big fan of the Tesla logo for the pin, but I have an >>> unusual history with the company that may be coloring my attitude on that. >>> >>> Tom >>> >>> on 3/5/12 5:38 PM, Mark Webb-Johnson wrote: >>> >>>> Tom, >>>> >>>> Good to have you aboard. >>>> >>>> We haven't been able to test the module on 1.5 cars (which is why we're only >>>> shipping to end-users with 2.x cars). The problem we've had is that all the >>>> developers involved have 2.x cars. >>>> >>>> That said, the module _should_ work in a 1.5 car. Scott451 did the original >>>> bus decodes on a 1.5 car, and while there are some differences, he did >>>> document the messages (but we haven't been able to verify this as we have with >>>> the 2.x cars). >>>> >>>> First, some trivia: >>>> >>>> Our current master document on CAN bus messages is at: >>>> https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/vehicl… >>>> ar%20Module/canbus_notes.txt >>>> and that includes all of Scott451's published work, plus our own additions. >>>> >>>> The SOC message is on the CAN bus - message ID#100, B1=0x80. There is >>>> supposedly no difference between the 1.5 and 2.x models for this message. >>>> >>>> To get the charging messages correctly, you will need to set the CARBITS >>>> feature to a 2008 model roadster. An SMS command: >>>> FEATURE 15 1 >>>> should enable bit#1 of the carbits, and permanently record this as a 2008 >>>> roadster. >>>> >>>> The "Not charging" just means the charge port door is closed (or bit#2 of B2 >>>> on id#100 B1=0x96 is zero). The SOC and Ideal range being zero is similar zero >>>> (default) values. >>>> >>>> So, either none of these messages are getting from the CAN bus to the module, >>>> or the messages are completely different on a 1.5 car. I suspect the former. >>>> >>>> Can you try: >>>> a) A "GPS" SMS command - do you get a location in Wales (default), or the true >>>> location? >>>> b) Open the charge port door, and repeat the "STAT" command - do you get a >>>> charging reply? >>>> and let us know the result? >>>> >>>> The problem could also just be a faulty module (we had some factory soldering >>>> issues with early modules), so please verify the soldering looks good, and >>>> trace continuity test, particularly on the CAN bus side? Or, a loose >>>> connection on the CAN bus cables (two pins CAN-L and CAN-H), so can you check >>>> that with a continuity tester? If you have the opportunity, you could try it >>>> in a 2.x roadster. >>>> >>>> There is a wiring schematic at: >>>> >>>> https://github.com/markwj/Open-Vehicle-Monitoring-System/raw/master/vehicle… >>>> r%20Module/OVMS_V5a.png >>>> >>>> My guess for this problem is a loose/broken cable on the CAN bus side - >>>> somewhere between the DIAG connector and the telco-style jacks connecting to >>>> the PIC motherboard. >>>> >>>> It would be really helpful if you could help us test this and iron out any >>>> wrinkles for the 1.5 cars. We've had some enquiries from 1.5 end-users, but >>>> have told them to hold-off for the moment until we can verify things work in a >>>> 1.5 car. >>>> >>>> Regards, Mark. >>>> >>>> On 6 Mar 2012, at 8:39 AM, Tom Saxton wrote: >>>> >>>>> I just got the OVMS board plugged into our v1.5 Roadster. I haven't jumped >>>>> through the hoops to get a data plan on my SIM card yet, so I'm just using >>>>> SMS. >>>>> >>>>> I registered my phone and changed my password. Those commands worked as >>>>> expected. I then did a STAT and got back: >>>>> >>>>> Not charging >>>>> Ideal Range: 0 Km >>>>> SOC 0% >>>>> >>>>> It's true that it's not charging, but the car is actually at 96% and 185 >>>>> ideal miles. >>>>> >>>>> What should I do next? >>>>> >>>>> Tom >>>>> >>>>> >>>>> _______________________________________________ >>>>> OvmsDev mailing list >>>>> OvmsDev(a)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

1 0

GPS SMS Response
by Tom Saxton 07 Mar '12

07 Mar '12

I notice that the SMS response to the GPS yields a gigantic link to a static map that can't be zoomed or panned. This makes it very difficult to figure out where the car is if you don't happen to recognize any of the features shown in the map. I prefer a simpler link that takes you to a fully functional map: http://maps.google.com/maps?q=52.042460,-3.944089 Also, I'm also not a big fan of the Tesla logo for the pin, but I have an unusual history with the company that may be coloring my attitude on that. Tom

4 3

Re: [Ovmsdev] 0% SOC Reported in v1.5 Roadster
by Mark Webb-Johnson 07 Mar '12

07 Mar '12

Tom, Scott451's original (ground breaking) post is at: http://www.teslamotorsclub.com/showthread.php/4388-iPhone-app/page2?p=49456… He talks there about the 2008 roadster, and confirms 1MHz bus speed. Your confirmation of the wales gps location and 0 SOC means the module is definitely not getting any can bus messages. It is either a faulty board, or some other incompatibility. Can you ask Cathy (she is your hardware support, right?) to check the continuity on connections on the MCP2551P and pins #23 and #24 on the PIC CPU? Do you know anyone close by with a 2.x roadster that you could plug the module in, to rule out 1.5 vs 2.x incompatibility? Regards, Mark. On 7 Mar 2012, at 1:35 AM, Tom Saxton wrote: > I did the "FEATURE 12 1" SMS command, but got no response. Are those > commands documented somewhere, or is it a "read the code" deal? (It is cool > to be able to read the code.) > > I get the same "not charging" status with the charge port door open. > > When I do a GPS command, I get back a link to 52.042460,-3.944089 which I > assume is the default position in Wales. > > So, it seems the OVMS module isn't getting any of these CAN messages. Is > there a way to tell if the board is getting any messages at all? > > With Cathy's help, I checked continuity and all four pins going to the MCU > board. They all check out, as do the four twin wires to the other connector. > > When plugged in, after the start up sequence, I get a solid green LED on > each board and a blinking blue LED on the modem board. > > Finally, I'm sure my diag port is functional as it has been working with my > Tattler (although the Tattler is going through some brain surgery right now > so I can't confirm that it's working today). > > BTW, I notice the generated GPS link takes you to a static map that can't be > scaled or panned. This makes it impossible to tell where the pin is if you > don't recognize any features in the static map. > > I like using a simpler link that gets you a fully functional map: > > http://maps.google.com/maps?q=52.042460,-3.944089 > > Also, I'm also not a big fan of the Tesla logo for the pin, but I have an > unusual history with the company that may be coloring my attitude on that. > > Tom > > on 3/5/12 5:38 PM, Mark Webb-Johnson wrote: > >> Tom, >> >> Good to have you aboard. >> >> We haven't been able to test the module on 1.5 cars (which is why we're only >> shipping to end-users with 2.x cars). The problem we've had is that all the >> developers involved have 2.x cars. >> >> That said, the module _should_ work in a 1.5 car. Scott451 did the original >> bus decodes on a 1.5 car, and while there are some differences, he did >> document the messages (but we haven't been able to verify this as we have with >> the 2.x cars). >> >> First, some trivia: >> >> Our current master document on CAN bus messages is at: >> https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/vehicl… >> ar%20Module/canbus_notes.txt >> and that includes all of Scott451's published work, plus our own additions. >> >> The SOC message is on the CAN bus - message ID#100, B1=0x80. There is >> supposedly no difference between the 1.5 and 2.x models for this message. >> >> To get the charging messages correctly, you will need to set the CARBITS >> feature to a 2008 model roadster. An SMS command: >> FEATURE 15 1 >> should enable bit#1 of the carbits, and permanently record this as a 2008 >> roadster. >> >> The "Not charging" just means the charge port door is closed (or bit#2 of B2 >> on id#100 B1=0x96 is zero). The SOC and Ideal range being zero is similar zero >> (default) values. >> >> So, either none of these messages are getting from the CAN bus to the module, >> or the messages are completely different on a 1.5 car. I suspect the former. >> >> Can you try: >> a) A "GPS" SMS command - do you get a location in Wales (default), or the true >> location? >> b) Open the charge port door, and repeat the "STAT" command - do you get a >> charging reply? >> and let us know the result? >> >> The problem could also just be a faulty module (we had some factory soldering >> issues with early modules), so please verify the soldering looks good, and >> trace continuity test, particularly on the CAN bus side? Or, a loose >> connection on the CAN bus cables (two pins CAN-L and CAN-H), so can you check >> that with a continuity tester? If you have the opportunity, you could try it >> in a 2.x roadster. >> >> There is a wiring schematic at: >> >> https://github.com/markwj/Open-Vehicle-Monitoring-System/raw/master/vehicle… >> r%20Module/OVMS_V5a.png >> >> My guess for this problem is a loose/broken cable on the CAN bus side - >> somewhere between the DIAG connector and the telco-style jacks connecting to >> the PIC motherboard. >> >> It would be really helpful if you could help us test this and iron out any >> wrinkles for the 1.5 cars. We've had some enquiries from 1.5 end-users, but >> have told them to hold-off for the moment until we can verify things work in a >> 1.5 car. >> >> Regards, Mark. >> >> On 6 Mar 2012, at 8:39 AM, Tom Saxton wrote: >> >>> I just got the OVMS board plugged into our v1.5 Roadster. I haven't jumped >>> through the hoops to get a data plan on my SIM card yet, so I'm just using >>> SMS. >>> >>> I registered my phone and changed my password. Those commands worked as >>> expected. I then did a STAT and got back: >>> >>> Not charging >>> Ideal Range: 0 Km >>> SOC 0% >>> >>> It's true that it's not charging, but the car is actually at 96% and 185 >>> ideal miles. >>> >>> What should I do next? >>> >>> Tom >>> >>> >>> _______________________________________________ >>> OvmsDev mailing list >>> OvmsDev(a)lists.teslaclub.hk >>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >> > >

1 0