Email sent again without the car photo (which exceeded the 1Mbyte file attachment limit)… From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org<mailto:kevin.sharpe@zerocarbonworld.org>> Date: Sunday, 14 April 2013 18:28 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Just to add a little more to Nikki's report… I've seen some odd behaviour with SOC… if you see the attached photo's you'll see STAT report SOC as 46% and then 50% even though the commands were sent within a minute of one another (approximately). You'll also see the app and car displayed 52% and 92m at the same time. I also note that the ODO reports 0.0 mil and I see no CAC in response to a STAT command. Is this expected behaviour with this firmware? Firmware version reported in the app is 2.3.1/TR/V2 All the best, [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Nikki Gordon-Bloomfield <nikki@littlecollie.com<mailto:nikki@littlecollie.com>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Sunday, 14 April 2013 17:24 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Just a head up: I flashed my Twizy firmware and it immediately started working. I flashed Kevin's firmware on his Roadster, and it took about 10 minutes to start working. Not sure why -- but thought you'd all appreciate the report. :) I've got a 35 mile round-trip tonight to Bath, and about 120 miles of work-related travel this week in the Twizy, so plenty of time to test it! Nikki Gordon-Bloomfield http://about.me/aminorjourney/bio email: nikki@littleCollie.com<mailto:nikki@littleCollie.com> tel: +44 7901 553308 On 14 Apr 2013, at 17:04, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: I've had GPS streaming enabled during the last days, and neither GPS nor GSM connectivity are good at the moment. May be related, as streaming means more data communication. But still that should not lead to RAM corruption. Am 14.04.2013 17:54, schrieb Michael Balzer: Mark, I've got the last but one version in my car, just lacking the new VEHICLE commands. I've got two open issues, the minor one being to raise the 12V auto acquisition time even more, as the faults have become better but it's not yet perfect. I'm trying 20 TAD now, as we don't need to be fast on that A/D conversion. But a major issue might have turned up: I've just had the second RAM corruption within three days. Effect: MP-0 c32,0,106,119,*-OVM-DebugCrash,2013-04-14 14:06:40,0,2.2.7/RT2.6.4/V2,0,0000,20 MP-0 c32,0,107,119,*-OVM-DebugCrash,2013-04-14 14:25:13,0,2.2.7/RT2.6.4/V2,80,0020,61 As there is no checkpoint 61, this means at least the debug variables have been overwritten, was the same with the first occurence (but other values). As the module behaves weird afterwards I suppose more variables have been corrupted. I've looked through the last changes several times, I'm pretty sure none could have introduced this kind of bug... if I'm the only one experiencing this, maybe I've got some hardware issue as well? I'll continue checking the source for possible buffer overruns... Regards, Michael Am 14.04.2013 16:29, schrieb Mark Webb-Johnson: I've just built from latest sources, v2.3.1. This is a release candidate, and I have 24 hours to test before i need to send it to China. It is in my car now, and seems ok. I'll do more testing tomorrow. I'd be grateful if others could grab it and put it in their cars to ensure there are no major problems. Regards, Mark. On 13 Apr, 2013, at 10:04 PM, Mark Webb-Johnson <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote: All seems ok. I've committed and pushed my changes (just the stp_ltf_h() function, and change to report cac as 999.99 to server). I've just flashed and it will go in my car tomorrow. Regards, Mark On 13 Apr, 2013, at 2:51 AM, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: Mark, I just checked in my latest changes. In net.c I added the pending send check also to the new net_notify_errorcode send, I think that should be correct, but please have a look. I saw the new stp_f() function, but I don't understand it's purpose yet. What's the difference to my stp_l2f() function? Btw: l2f = "long to float" -- I think "_f" should be reserved for an stp call with a real float type parameter, if we once really need one. Regards, Michael Am 12.04.2013 20:16, schrieb Michael Balzer: Nikki, yes, see attachment. I could not make out any possible source of that strange error I had yesterday (completely garbled data). I made a clean build with a freshly started MPLAB and got no errors up to now. May have been something completely different, not related to my last changes. Regards, Michael Am 12.04.2013 17:01, schrieb Nikki Gordon-Bloomfield: Michael, Any new firmware for me to test this weekend? Nikki. On 11 Apr 2013, at 18:33, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: I think I was a bit too fast on this, Nikki, don't use that version, it seems to have some new bug causing frequent crashes... :-( Regards, Michael Am 11.04.2013 19:22, schrieb Michael Balzer: Mark, Nikki, I'm currently trying to fix a last bug with the power statistics (the distance counter still went wrong), and I'm trying to get the 12V A/D conversion to work without these strange "peaks" by raising the automatic acquisition time. I will finish testing this ASAP or tell you in time before sunday. Nikki, I attached the latest version in case you'd like to test as well. Regards, Michael Am 11.04.2013 16:41, schrieb Mark Webb-Johnson: China is bugging me for final firmware for the next batch of hardware. I need to get them this early next week. I've committed what I need for the Tesla Roadster (and framework). Last outstanding small change to make is to send CAC as 999.99, rather than the current 99999, using Tom's new library function. Michael B & J: can you check Twizzy and Volt/Ampera, to see if everything is ok with current firmware or there is anything you need changed? I plan to cut release candidate for 2.3.1 on Sunday. Regards, Mark. _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Ignore my comment regarding CAC which I see now the car is on charge :-) [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org<mailto:kevin.sharpe@zerocarbonworld.org>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Sunday, 14 April 2013 18:32 To: "ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>" <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: [Ovmsdev] FW: Release Firmware Email sent again without the car photo (which exceeded the 1Mbyte file attachment limit)… From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org<mailto:kevin.sharpe@zerocarbonworld.org>> Date: Sunday, 14 April 2013 18:28 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Just to add a little more to Nikki's report… I've seen some odd behaviour with SOC… if you see the attached photo's you'll see STAT report SOC as 46% and then 50% even though the commands were sent within a minute of one another (approximately). You'll also see the app and car displayed 52% and 92m at the same time. I also note that the ODO reports 0.0 mil and I see no CAC in response to a STAT command. Is this expected behaviour with this firmware? Firmware version reported in the app is 2.3.1/TR/V2 All the best, [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Nikki Gordon-Bloomfield <nikki@littlecollie.com<mailto:nikki@littlecollie.com>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Sunday, 14 April 2013 17:24 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Just a head up: I flashed my Twizy firmware and it immediately started working. I flashed Kevin's firmware on his Roadster, and it took about 10 minutes to start working. Not sure why -- but thought you'd all appreciate the report. :) I've got a 35 mile round-trip tonight to Bath, and about 120 miles of work-related travel this week in the Twizy, so plenty of time to test it! Nikki Gordon-Bloomfield http://about.me/aminorjourney/bio email: nikki@littleCollie.com<mailto:nikki@littleCollie.com> tel: +44 7901 553308 On 14 Apr 2013, at 17:04, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: I've had GPS streaming enabled during the last days, and neither GPS nor GSM connectivity are good at the moment. May be related, as streaming means more data communication. But still that should not lead to RAM corruption. Am 14.04.2013 17:54, schrieb Michael Balzer: Mark, I've got the last but one version in my car, just lacking the new VEHICLE commands. I've got two open issues, the minor one being to raise the 12V auto acquisition time even more, as the faults have become better but it's not yet perfect. I'm trying 20 TAD now, as we don't need to be fast on that A/D conversion. But a major issue might have turned up: I've just had the second RAM corruption within three days. Effect: MP-0 c32,0,106,119,*-OVM-DebugCrash,2013-04-14 14:06:40,0,2.2.7/RT2.6.4/V2,0,0000,20 MP-0 c32,0,107,119,*-OVM-DebugCrash,2013-04-14 14:25:13,0,2.2.7/RT2.6.4/V2,80,0020,61 As there is no checkpoint 61, this means at least the debug variables have been overwritten, was the same with the first occurence (but other values). As the module behaves weird afterwards I suppose more variables have been corrupted. I've looked through the last changes several times, I'm pretty sure none could have introduced this kind of bug... if I'm the only one experiencing this, maybe I've got some hardware issue as well? I'll continue checking the source for possible buffer overruns... Regards, Michael Am 14.04.2013 16:29, schrieb Mark Webb-Johnson: I've just built from latest sources, v2.3.1. This is a release candidate, and I have 24 hours to test before i need to send it to China. It is in my car now, and seems ok. I'll do more testing tomorrow. I'd be grateful if others could grab it and put it in their cars to ensure there are no major problems. Regards, Mark. On 13 Apr, 2013, at 10:04 PM, Mark Webb-Johnson <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote: All seems ok. I've committed and pushed my changes (just the stp_ltf_h() function, and change to report cac as 999.99 to server). I've just flashed and it will go in my car tomorrow. Regards, Mark On 13 Apr, 2013, at 2:51 AM, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: Mark, I just checked in my latest changes. In net.c I added the pending send check also to the new net_notify_errorcode send, I think that should be correct, but please have a look. I saw the new stp_f() function, but I don't understand it's purpose yet. What's the difference to my stp_l2f() function? Btw: l2f = "long to float" -- I think "_f" should be reserved for an stp call with a real float type parameter, if we once really need one. Regards, Michael Am 12.04.2013 20:16, schrieb Michael Balzer: Nikki, yes, see attachment. I could not make out any possible source of that strange error I had yesterday (completely garbled data). I made a clean build with a freshly started MPLAB and got no errors up to now. May have been something completely different, not related to my last changes. Regards, Michael Am 12.04.2013 17:01, schrieb Nikki Gordon-Bloomfield: Michael, Any new firmware for me to test this weekend? Nikki. On 11 Apr 2013, at 18:33, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: I think I was a bit too fast on this, Nikki, don't use that version, it seems to have some new bug causing frequent crashes... :-( Regards, Michael Am 11.04.2013 19:22, schrieb Michael Balzer: Mark, Nikki, I'm currently trying to fix a last bug with the power statistics (the distance counter still went wrong), and I'm trying to get the 12V A/D conversion to work without these strange "peaks" by raising the automatic acquisition time. I will finish testing this ASAP or tell you in time before sunday. Nikki, I attached the latest version in case you'd like to test as well. Regards, Michael Am 11.04.2013 16:41, schrieb Mark Webb-Johnson: China is bugging me for final firmware for the next batch of hardware. I need to get them this early next week. I've committed what I need for the Tesla Roadster (and framework). Last outstanding small change to make is to send CAC as 999.99, rather than the current 99999, using Tom's new library function. Michael B & J: can you check Twizzy and Volt/Ampera, to see if everything is ok with current firmware or there is anything you need changed? I plan to cut release candidate for 2.3.1 on Sunday. Regards, Mark. _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Kevin, Thanks for the help testing. CAC is retrieved (a) car is turned on, (b) car is turned off, (c) charge is started - so your experience is expected. The odometer 0 miles is worrying. Is that still the case, or working now? Regards, Mark. On 15 Apr, 2013, at 3:50 AM, Kevin Sharpe ZCW wrote:
Ignore my comment regarding CAC which I see now the car is on charge :-)
Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org | www.zerocarbonworld.org | twitter.com/zerocarbonworld
Zero Carbon World is a UK Registered Charity #1141347 From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Sunday, 14 April 2013 18:32 To: "ovmsdev@lists.teslaclub.hk" <ovmsdev@lists.teslaclub.hk> Subject: [Ovmsdev] FW: Release Firmware
Email sent again without the car photo (which exceeded the 1Mbyte file attachment limit)…
From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org> Date: Sunday, 14 April 2013 18:28 To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] Release Firmware
Just to add a little more to Nikki's report…
I've seen some odd behaviour with SOC… if you see the attached photo's you'll see STAT report SOC as 46% and then 50% even though the commands were sent within a minute of one another (approximately). You'll also see the app and car displayed 52% and 92m at the same time.
I also note that the ODO reports 0.0 mil and I see no CAC in response to a STAT command. Is this expected behaviour with this firmware?
Firmware version reported in the app is 2.3.1/TR/V2
All the best, Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org | www.zerocarbonworld.org | twitter.com/zerocarbonworld
Zero Carbon World is a UK Registered Charity #1141347 From: Nikki Gordon-Bloomfield <nikki@littlecollie.com> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Sunday, 14 April 2013 17:24 To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] Release Firmware
Just a head up:
I flashed my Twizy firmware and it immediately started working.
I flashed Kevin's firmware on his Roadster, and it took about 10 minutes to start working.
Not sure why -- but thought you'd all appreciate the report. :)
I've got a 35 mile round-trip tonight to Bath, and about 120 miles of work-related travel this week in the Twizy, so plenty of time to test it!
Nikki Gordon-Bloomfield
http://about.me/aminorjourney/bio email: nikki@littleCollie.com tel: +44 7901 553308
On 14 Apr 2013, at 17:04, Michael Balzer <dexter@expeedo.de> wrote:
I've had GPS streaming enabled during the last days, and neither GPS nor GSM connectivity are good at the moment. May be related, as streaming means more data communication. But still that should not lead to RAM corruption.
Am 14.04.2013 17:54, schrieb Michael Balzer:
Mark,
I've got the last but one version in my car, just lacking the new VEHICLE commands.
I've got two open issues, the minor one being to raise the 12V auto acquisition time even more, as the faults have become better but it's not yet perfect. I'm trying 20 TAD now, as we don't need to be fast on that A/D conversion.
But a major issue might have turned up: I've just had the second RAM corruption within three days. Effect:
MP-0 c32,0,106,119,*-OVM-DebugCrash,2013-04-14 14:06:40,0,2.2.7/RT2.6.4/V2,0,0000,20 MP-0 c32,0,107,119,*-OVM-DebugCrash,2013-04-14 14:25:13,0,2.2.7/RT2.6.4/V2,80,0020,61
As there is no checkpoint 61, this means at least the debug variables have been overwritten, was the same with the first occurence (but other values).
As the module behaves weird afterwards I suppose more variables have been corrupted.
I've looked through the last changes several times, I'm pretty sure none could have introduced this kind of bug... if I'm the only one experiencing this, maybe I've got some hardware issue as well?
I'll continue checking the source for possible buffer overruns...
Regards, Michael
Am 14.04.2013 16:29, schrieb Mark Webb-Johnson:
I've just built from latest sources, v2.3.1. This is a release candidate, and I have 24 hours to test before i need to send it to China.
It is in my car now, and seems ok. I'll do more testing tomorrow.
I'd be grateful if others could grab it and put it in their cars to ensure there are no major problems.
Regards, Mark.
On 13 Apr, 2013, at 10:04 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
All seems ok.
I've committed and pushed my changes (just the stp_ltf_h() function, and change to report cac as 999.99 to server).
I've just flashed and it will go in my car tomorrow.
Regards, Mark
On 13 Apr, 2013, at 2:51 AM, Michael Balzer <dexter@expeedo.de> wrote:
Mark,
I just checked in my latest changes.
In net.c I added the pending send check also to the new net_notify_errorcode send, I think that should be correct, but please have a look.
I saw the new stp_f() function, but I don't understand it's purpose yet. What's the difference to my stp_l2f() function? Btw: l2f = "long to float" -- I think "_f" should be reserved for an stp call with a real float type parameter, if we once really need one.
Regards, Michael
Am 12.04.2013 20:16, schrieb Michael Balzer: > Nikki, > > yes, see attachment. > > I could not make out any possible source of that strange error I had yesterday (completely garbled data). > > I made a clean build with a freshly started MPLAB and got no errors up to now. > > May have been something completely different, not related to my last changes. > > Regards, > Michael > > > Am 12.04.2013 17:01, schrieb Nikki Gordon-Bloomfield: >> Michael, >> >> Any new firmware for me to test this weekend? >> >> Nikki. >> >> On 11 Apr 2013, at 18:33, Michael Balzer <dexter@expeedo.de> wrote: >> >>> I think I was a bit too fast on this, Nikki, don't use that version, it seems to have some new bug causing frequent crashes... :-( >>> >>> Regards, >>> Michael >>> >>> >>> Am 11.04.2013 19:22, schrieb Michael Balzer: >>>> Mark, Nikki, >>>> >>>> I'm currently trying to fix a last bug with the power statistics (the distance counter still went wrong), and I'm trying to get the 12V A/D conversion to work without these strange "peaks" by raising the automatic acquisition time. I will finish testing this ASAP or tell you in time before sunday. >>>> >>>> Nikki, I attached the latest version in case you'd like to test as well. >>>> >>>> Regards, >>>> Michael >>>> >>>> >>>> Am 11.04.2013 16:41, schrieb Mark Webb-Johnson: >>>>> China is bugging me for final firmware for the next batch of hardware. I need to get them this early next week. >>>>> >>>>> I've committed what I need for the Tesla Roadster (and framework). Last outstanding small change to make is to send CAC as 999.99, rather than the current 99999, using Tom's new library function. >>>>> >>>>> Michael B & J: can you check Twizzy and Volt/Ampera, to see if everything is ok with current firmware or there is anything you need changed? >>>>> >>>>> I plan to cut release candidate for 2.3.1 on Sunday. >>>>> >>>>> Regards, Mark. >>>>> >>>>> _______________________________________________ >>>>> OvmsDev mailing list >>>>> OvmsDev@lists.teslaclub.hk >>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >>>> >>>> >>>> >>>> _______________________________________________ >>>> OvmsDev mailing list >>>> OvmsDev@lists.teslaclub.hkhttp://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@lists.teslaclub.hk >>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >> >> >> >> _______________________________________________ >> OvmsDev mailing list >> OvmsDev@lists.teslaclub.hkhttp://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@lists.teslaclub.hkhttp://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@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hkhttp://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@lists.teslaclub.hkhttp://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@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Hi Mark, Thanks for the CAC explanation. I can confirm I do not see ODO change from 0.0 (see attached screen shot). Indeed, I have never seen ODO change and had assumed it was only working on the very latest firmware. I tried resetting the module using the app command and power cycling the hardware. All the best Kevin [cid:9C5B3064-2370-4C14-A8CA-A0D9AB96DC03] On 15 Apr 2013, at 01:50, "Mark Webb-Johnson" <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote: Kevin, Thanks for the help testing. CAC is retrieved (a) car is turned on, (b) car is turned off, (c) charge is started - so your experience is expected. The odometer 0 miles is worrying. Is that still the case, or working now? Regards, Mark. On 15 Apr, 2013, at 3:50 AM, Kevin Sharpe ZCW wrote: Ignore my comment regarding CAC which I see now the car is on charge :-) [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org<mailto:kevin.sharpe@zerocarbonworld.org>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Sunday, 14 April 2013 18:32 To: "ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>" <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: [Ovmsdev] FW: Release Firmware Email sent again without the car photo (which exceeded the 1Mbyte file attachment limit)… From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org<mailto:kevin.sharpe@zerocarbonworld.org>> Date: Sunday, 14 April 2013 18:28 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Just to add a little more to Nikki's report… I've seen some odd behaviour with SOC… if you see the attached photo's you'll see STAT report SOC as 46% and then 50% even though the commands were sent within a minute of one another (approximately). You'll also see the app and car displayed 52% and 92m at the same time. I also note that the ODO reports 0.0 mil and I see no CAC in response to a STAT command. Is this expected behaviour with this firmware? Firmware version reported in the app is 2.3.1/TR/V2 All the best, [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Nikki Gordon-Bloomfield <nikki@littlecollie.com<mailto:nikki@littlecollie.com>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Sunday, 14 April 2013 17:24 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Just a head up: I flashed my Twizy firmware and it immediately started working. I flashed Kevin's firmware on his Roadster, and it took about 10 minutes to start working. Not sure why -- but thought you'd all appreciate the report. :) I've got a 35 mile round-trip tonight to Bath, and about 120 miles of work-related travel this week in the Twizy, so plenty of time to test it! Nikki Gordon-Bloomfield http://about.me/aminorjourney/bio email: nikki@littleCollie.com<mailto:nikki@littleCollie.com> tel: +44 7901 553308 On 14 Apr 2013, at 17:04, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: I've had GPS streaming enabled during the last days, and neither GPS nor GSM connectivity are good at the moment. May be related, as streaming means more data communication. But still that should not lead to RAM corruption. Am 14.04.2013 17:54, schrieb Michael Balzer: Mark, I've got the last but one version in my car, just lacking the new VEHICLE commands. I've got two open issues, the minor one being to raise the 12V auto acquisition time even more, as the faults have become better but it's not yet perfect. I'm trying 20 TAD now, as we don't need to be fast on that A/D conversion. But a major issue might have turned up: I've just had the second RAM corruption within three days. Effect: MP-0 c32,0,106,119,*-OVM-DebugCrash,2013-04-14 14:06:40,0,2.2.7/RT2.6.4/V2,0,0000,20 MP-0 c32,0,107,119,*-OVM-DebugCrash,2013-04-14 14:25:13,0,2.2.7/RT2.6.4/V2,80,0020,61 As there is no checkpoint 61, this means at least the debug variables have been overwritten, was the same with the first occurence (but other values). As the module behaves weird afterwards I suppose more variables have been corrupted. I've looked through the last changes several times, I'm pretty sure none could have introduced this kind of bug... if I'm the only one experiencing this, maybe I've got some hardware issue as well? I'll continue checking the source for possible buffer overruns... Regards, Michael Am 14.04.2013 16:29, schrieb Mark Webb-Johnson: I've just built from latest sources, v2.3.1. This is a release candidate, and I have 24 hours to test before i need to send it to China. It is in my car now, and seems ok. I'll do more testing tomorrow. I'd be grateful if others could grab it and put it in their cars to ensure there are no major problems. Regards, Mark. On 13 Apr, 2013, at 10:04 PM, Mark Webb-Johnson <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote: All seems ok. I've committed and pushed my changes (just the stp_ltf_h() function, and change to report cac as 999.99 to server). I've just flashed and it will go in my car tomorrow. Regards, Mark On 13 Apr, 2013, at 2:51 AM, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: Mark, I just checked in my latest changes. In net.c I added the pending send check also to the new net_notify_errorcode send, I think that should be correct, but please have a look. I saw the new stp_f() function, but I don't understand it's purpose yet. What's the difference to my stp_l2f() function? Btw: l2f = "long to float" -- I think "_f" should be reserved for an stp call with a real float type parameter, if we once really need one. Regards, Michael Am 12.04.2013 20:16, schrieb Michael Balzer: Nikki, yes, see attachment. I could not make out any possible source of that strange error I had yesterday (completely garbled data). I made a clean build with a freshly started MPLAB and got no errors up to now. May have been something completely different, not related to my last changes. Regards, Michael Am 12.04.2013 17:01, schrieb Nikki Gordon-Bloomfield: Michael, Any new firmware for me to test this weekend? Nikki. On 11 Apr 2013, at 18:33, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: I think I was a bit too fast on this, Nikki, don't use that version, it seems to have some new bug causing frequent crashes... :-( Regards, Michael Am 11.04.2013 19:22, schrieb Michael Balzer: Mark, Nikki, I'm currently trying to fix a last bug with the power statistics (the distance counter still went wrong), and I'm trying to get the 12V A/D conversion to work without these strange "peaks" by raising the automatic acquisition time. I will finish testing this ASAP or tell you in time before sunday. Nikki, I attached the latest version in case you'd like to test as well. Regards, Michael Am 11.04.2013 16:41, schrieb Mark Webb-Johnson: China is bugging me for final firmware for the next batch of hardware. I need to get them this early next week. I've committed what I need for the Tesla Roadster (and framework). Last outstanding small change to make is to send CAC as 999.99, rather than the current 99999, using Tom's new library function. Michael B & J: can you check Twizzy and Volt/Ampera, to see if everything is ok with current firmware or there is anything you need changed? I plan to cut release candidate for 2.3.1 on Sunday. Regards, Mark. _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Kevin, This is strange, and worrying... I checked the logs for your car - it seems that your car has never reported odometer or trip != 0. Even with older firmware v2.2.2 it was always reporting 0 for both odometer and trip. I looked further back, and find the last record with a non-zero odometer reading seems to be back in January (that was firmware v1.3.5, but the odometer reported was 0 even with that firmware a day later). Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday), but a bunch are running v2.2.6 (the previous release) and all those show odometer correctly. I don't think this is anything to do with new firmware - instead it seems to be specific to your car. What is the actual odometer and trip reading in your car at the moment? Anything unusual about it (e.g. old vehicle firmware, etc)? Can you try cycling through the VDS screens next time you go for a drive? Just keep pressing the right-arrow button on the VDS until you cycle back to the main battery screen. Regards, Mark. On 15 Apr, 2013, at 1:34 PM, Kevin Sharpe ZCW wrote:
Hi Mark,
Thanks for the CAC explanation.
I can confirm I do not see ODO change from 0.0 (see attached screen shot). Indeed, I have never seen ODO change and had assumed it was only working on the very latest firmware.
I tried resetting the module using the app command and power cycling the hardware.
All the best
Kevin
On 15 Apr 2013, at 01:50, "Mark Webb-Johnson" <mark@webb-johnson.net> wrote:
Kevin,
Thanks for the help testing.
CAC is retrieved (a) car is turned on, (b) car is turned off, (c) charge is started - so your experience is expected.
The odometer 0 miles is worrying. Is that still the case, or working now?
Regards, Mark.
On 15 Apr, 2013, at 3:50 AM, Kevin Sharpe ZCW wrote:
Ignore my comment regarding CAC which I see now the car is on charge :-)
Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org | www.zerocarbonworld.org | twitter.com/zerocarbonworld
Zero Carbon World is a UK Registered Charity #1141347 From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Sunday, 14 April 2013 18:32 To: "ovmsdev@lists.teslaclub.hk" <ovmsdev@lists.teslaclub.hk> Subject: [Ovmsdev] FW: Release Firmware
Email sent again without the car photo (which exceeded the 1Mbyte file attachment limit)…
From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org> Date: Sunday, 14 April 2013 18:28 To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] Release Firmware
Just to add a little more to Nikki's report…
I've seen some odd behaviour with SOC… if you see the attached photo's you'll see STAT report SOC as 46% and then 50% even though the commands were sent within a minute of one another (approximately). You'll also see the app and car displayed 52% and 92m at the same time.
I also note that the ODO reports 0.0 mil and I see no CAC in response to a STAT command. Is this expected behaviour with this firmware?
Firmware version reported in the app is 2.3.1/TR/V2
All the best, Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org | www.zerocarbonworld.org | twitter.com/zerocarbonworld
Zero Carbon World is a UK Registered Charity #1141347 From: Nikki Gordon-Bloomfield <nikki@littlecollie.com> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Sunday, 14 April 2013 17:24 To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] Release Firmware
Just a head up:
I flashed my Twizy firmware and it immediately started working.
I flashed Kevin's firmware on his Roadster, and it took about 10 minutes to start working.
Not sure why -- but thought you'd all appreciate the report. :)
I've got a 35 mile round-trip tonight to Bath, and about 120 miles of work-related travel this week in the Twizy, so plenty of time to test it!
Nikki Gordon-Bloomfield
http://about.me/aminorjourney/bio email: nikki@littleCollie.com tel: +44 7901 553308
On 14 Apr 2013, at 17:04, Michael Balzer <dexter@expeedo.de> wrote:
I've had GPS streaming enabled during the last days, and neither GPS nor GSM connectivity are good at the moment. May be related, as streaming means more data communication. But still that should not lead to RAM corruption.
Am 14.04.2013 17:54, schrieb Michael Balzer:
Mark,
I've got the last but one version in my car, just lacking the new VEHICLE commands.
I've got two open issues, the minor one being to raise the 12V auto acquisition time even more, as the faults have become better but it's not yet perfect. I'm trying 20 TAD now, as we don't need to be fast on that A/D conversion.
But a major issue might have turned up: I've just had the second RAM corruption within three days. Effect:
MP-0 c32,0,106,119,*-OVM-DebugCrash,2013-04-14 14:06:40,0,2.2.7/RT2.6.4/V2,0,0000,20 MP-0 c32,0,107,119,*-OVM-DebugCrash,2013-04-14 14:25:13,0,2.2.7/RT2.6.4/V2,80,0020,61
As there is no checkpoint 61, this means at least the debug variables have been overwritten, was the same with the first occurence (but other values).
As the module behaves weird afterwards I suppose more variables have been corrupted.
I've looked through the last changes several times, I'm pretty sure none could have introduced this kind of bug... if I'm the only one experiencing this, maybe I've got some hardware issue as well?
I'll continue checking the source for possible buffer overruns...
Regards, Michael
Am 14.04.2013 16:29, schrieb Mark Webb-Johnson:
I've just built from latest sources, v2.3.1. This is a release candidate, and I have 24 hours to test before i need to send it to China.
It is in my car now, and seems ok. I'll do more testing tomorrow.
I'd be grateful if others could grab it and put it in their cars to ensure there are no major problems.
Regards, Mark.
On 13 Apr, 2013, at 10:04 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
> All seems ok. > > I've committed and pushed my changes (just the stp_ltf_h() function, and change to report cac as 999.99 to server). > > I've just flashed and it will go in my car tomorrow. > > Regards, Mark > > On 13 Apr, 2013, at 2:51 AM, Michael Balzer <dexter@expeedo.de> wrote: > >> Mark, >> >> I just checked in my latest changes. >> >> In net.c I added the pending send check also to the new net_notify_errorcode send, I think that should be correct, but please have a look. >> >> I saw the new stp_f() function, but I don't understand it's purpose yet. What's the difference to my stp_l2f() function? >> Btw: l2f = "long to float" -- I think "_f" should be reserved for an stp call with a real float type parameter, if we once really need one. >> >> Regards, >> Michael >> >> >> Am 12.04.2013 20:16, schrieb Michael Balzer: >>> Nikki, >>> >>> yes, see attachment. >>> >>> I could not make out any possible source of that strange error I had yesterday (completely garbled data). >>> >>> I made a clean build with a freshly started MPLAB and got no errors up to now. >>> >>> May have been something completely different, not related to my last changes. >>> >>> Regards, >>> Michael >>> >>> >>> Am 12.04.2013 17:01, schrieb Nikki Gordon-Bloomfield: >>>> Michael, >>>> >>>> Any new firmware for me to test this weekend? >>>> >>>> Nikki. >>>> >>>> On 11 Apr 2013, at 18:33, Michael Balzer <dexter@expeedo.de> wrote: >>>> >>>>> I think I was a bit too fast on this, Nikki, don't use that version, it seems to have some new bug causing frequent crashes... :-( >>>>> >>>>> Regards, >>>>> Michael >>>>> >>>>> >>>>> Am 11.04.2013 19:22, schrieb Michael Balzer: >>>>>> Mark, Nikki, >>>>>> >>>>>> I'm currently trying to fix a last bug with the power statistics (the distance counter still went wrong), and I'm trying to get the 12V A/D conversion to work without these strange "peaks" by raising the automatic acquisition time. I will finish testing this ASAP or tell you in time before sunday. >>>>>> >>>>>> Nikki, I attached the latest version in case you'd like to test as well. >>>>>> >>>>>> Regards, >>>>>> Michael >>>>>> >>>>>> >>>>>> Am 11.04.2013 16:41, schrieb Mark Webb-Johnson: >>>>>>> China is bugging me for final firmware for the next batch of hardware. I need to get them this early next week. >>>>>>> >>>>>>> I've committed what I need for the Tesla Roadster (and framework). Last outstanding small change to make is to send CAC as 999.99, rather than the current 99999, using Tom's new library function. >>>>>>> >>>>>>> Michael B & J: can you check Twizzy and Volt/Ampera, to see if everything is ok with current firmware or there is anything you need changed? >>>>>>> >>>>>>> I plan to cut release candidate for 2.3.1 on Sunday. >>>>>>> >>>>>>> Regards, Mark. >>>>>>> >>>>>>> _______________________________________________ >>>>>>> OvmsDev mailing list >>>>>>> OvmsDev@lists.teslaclub.hk >>>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> OvmsDev mailing list >>>>>> OvmsDev@lists.teslaclub.hkhttp://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@lists.teslaclub.hk >>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >>>> >>>> >>>> >>>> _______________________________________________ >>>> OvmsDev mailing list >>>> OvmsDev@lists.teslaclub.hkhttp://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@lists.teslaclub.hkhttp://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@lists.teslaclub.hk >> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > _______________________________________________ > OvmsDev mailing list > OvmsDev@lists.teslaclub.hk > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hkhttp://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@lists.teslaclub.hkhttp://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@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
I'm the one who flashed Kevin's firmware. Could I have missed something? Sent from my iPhone On 15 Apr 2013, at 07:03, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Kevin,
This is strange, and worrying...
I checked the logs for your car - it seems that your car has never reported odometer or trip != 0. Even with older firmware v2.2.2 it was always reporting 0 for both odometer and trip. I looked further back, and find the last record with a non-zero odometer reading seems to be back in January (that was firmware v1.3.5, but the odometer reported was 0 even with that firmware a day later).
Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday), but a bunch are running v2.2.6 (the previous release) and all those show odometer correctly. I don't think this is anything to do with new firmware - instead it seems to be specific to your car.
What is the actual odometer and trip reading in your car at the moment? Anything unusual about it (e.g. old vehicle firmware, etc)?
Can you try cycling through the VDS screens next time you go for a drive? Just keep pressing the right-arrow button on the VDS until you cycle back to the main battery screen.
Regards, Mark.
On 15 Apr, 2013, at 1:34 PM, Kevin Sharpe ZCW wrote:
Hi Mark,
Thanks for the CAC explanation.
I can confirm I do not see ODO change from 0.0 (see attached screen shot). Indeed, I have never seen ODO change and had assumed it was only working on the very latest firmware.
I tried resetting the module using the app command and power cycling the hardware.
All the best
Kevin
On 15 Apr 2013, at 01:50, "Mark Webb-Johnson" <mark@webb-johnson.net> wrote:
Kevin,
Thanks for the help testing.
CAC is retrieved (a) car is turned on, (b) car is turned off, (c) charge is started - so your experience is expected.
The odometer 0 miles is worrying. Is that still the case, or working now?
Regards, Mark.
On 15 Apr, 2013, at 3:50 AM, Kevin Sharpe ZCW wrote:
Ignore my comment regarding CAC which I see now the car is on charge :-)
Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org | www.zerocarbonworld.org | twitter.com/zerocarbonworld
Zero Carbon World is a UK Registered Charity #1141347 From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Sunday, 14 April 2013 18:32 To: "ovmsdev@lists.teslaclub.hk" <ovmsdev@lists.teslaclub.hk> Subject: [Ovmsdev] FW: Release Firmware
Email sent again without the car photo (which exceeded the 1Mbyte file attachment limit)…
From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org> Date: Sunday, 14 April 2013 18:28 To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] Release Firmware
Just to add a little more to Nikki's report…
I've seen some odd behaviour with SOC… if you see the attached photo's you'll see STAT report SOC as 46% and then 50% even though the commands were sent within a minute of one another (approximately). You'll also see the app and car displayed 52% and 92m at the same time.
I also note that the ODO reports 0.0 mil and I see no CAC in response to a STAT command. Is this expected behaviour with this firmware?
Firmware version reported in the app is 2.3.1/TR/V2
All the best, Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org | www.zerocarbonworld.org | twitter.com/zerocarbonworld
Zero Carbon World is a UK Registered Charity #1141347 From: Nikki Gordon-Bloomfield <nikki@littlecollie.com> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Sunday, 14 April 2013 17:24 To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] Release Firmware
Just a head up:
I flashed my Twizy firmware and it immediately started working.
I flashed Kevin's firmware on his Roadster, and it took about 10 minutes to start working.
Not sure why -- but thought you'd all appreciate the report. :)
I've got a 35 mile round-trip tonight to Bath, and about 120 miles of work-related travel this week in the Twizy, so plenty of time to test it!
Nikki Gordon-Bloomfield
http://about.me/aminorjourney/bio email: nikki@littleCollie.com tel: +44 7901 553308
On 14 Apr 2013, at 17:04, Michael Balzer <dexter@expeedo.de> wrote:
I've had GPS streaming enabled during the last days, and neither GPS nor GSM connectivity are good at the moment. May be related, as streaming means more data communication. But still that should not lead to RAM corruption.
Am 14.04.2013 17:54, schrieb Michael Balzer:
Mark,
I've got the last but one version in my car, just lacking the new VEHICLE commands.
I've got two open issues, the minor one being to raise the 12V auto acquisition time even more, as the faults have become better but it's not yet perfect. I'm trying 20 TAD now, as we don't need to be fast on that A/D conversion.
But a major issue might have turned up: I've just had the second RAM corruption within three days. Effect:
MP-0 c32,0,106,119,*-OVM-DebugCrash,2013-04-14 14:06:40,0,2.2.7/RT2.6.4/V2,0,0000,20 MP-0 c32,0,107,119,*-OVM-DebugCrash,2013-04-14 14:25:13,0,2.2.7/RT2.6.4/V2,80,0020,61
As there is no checkpoint 61, this means at least the debug variables have been overwritten, was the same with the first occurence (but other values).
As the module behaves weird afterwards I suppose more variables have been corrupted.
I've looked through the last changes several times, I'm pretty sure none could have introduced this kind of bug... if I'm the only one experiencing this, maybe I've got some hardware issue as well?
I'll continue checking the source for possible buffer overruns...
Regards,
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
I don't think so. Everything else looks ok. Just no odometer. Regards, Mark. On 15 Apr, 2013, at 2:11 PM, Nikki Gordon-Bloomfield wrote:
I'm the one who flashed Kevin's firmware. Could I have missed something?
Sent from my iPhone
On 15 Apr 2013, at 07:03, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Kevin,
This is strange, and worrying...
I checked the logs for your car - it seems that your car has never reported odometer or trip != 0. Even with older firmware v2.2.2 it was always reporting 0 for both odometer and trip. I looked further back, and find the last record with a non-zero odometer reading seems to be back in January (that was firmware v1.3.5, but the odometer reported was 0 even with that firmware a day later).
Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday), but a bunch are running v2.2.6 (the previous release) and all those show odometer correctly. I don't think this is anything to do with new firmware - instead it seems to be specific to your car.
What is the actual odometer and trip reading in your car at the moment? Anything unusual about it (e.g. old vehicle firmware, etc)?
Can you try cycling through the VDS screens next time you go for a drive? Just keep pressing the right-arrow button on the VDS until you cycle back to the main battery screen.
Regards, Mark.
On 15 Apr, 2013, at 1:34 PM, Kevin Sharpe ZCW wrote:
Hi Mark,
Thanks for the CAC explanation.
I can confirm I do not see ODO change from 0.0 (see attached screen shot). Indeed, I have never seen ODO change and had assumed it was only working on the very latest firmware.
I tried resetting the module using the app command and power cycling the hardware.
All the best
Kevin
On 15 Apr 2013, at 01:50, "Mark Webb-Johnson" <mark@webb-johnson.net> wrote:
Kevin,
Thanks for the help testing.
CAC is retrieved (a) car is turned on, (b) car is turned off, (c) charge is started - so your experience is expected.
The odometer 0 miles is worrying. Is that still the case, or working now?
Regards, Mark.
On 15 Apr, 2013, at 3:50 AM, Kevin Sharpe ZCW wrote:
Ignore my comment regarding CAC which I see now the car is on charge :-)
Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org | www.zerocarbonworld.org | twitter.com/zerocarbonworld
Zero Carbon World is a UK Registered Charity #1141347 From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Sunday, 14 April 2013 18:32 To: "ovmsdev@lists.teslaclub.hk" <ovmsdev@lists.teslaclub.hk> Subject: [Ovmsdev] FW: Release Firmware
Email sent again without the car photo (which exceeded the 1Mbyte file attachment limit)…
From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org> Date: Sunday, 14 April 2013 18:28 To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] Release Firmware
Just to add a little more to Nikki's report…
I've seen some odd behaviour with SOC… if you see the attached photo's you'll see STAT report SOC as 46% and then 50% even though the commands were sent within a minute of one another (approximately). You'll also see the app and car displayed 52% and 92m at the same time.
I also note that the ODO reports 0.0 mil and I see no CAC in response to a STAT command. Is this expected behaviour with this firmware?
Firmware version reported in the app is 2.3.1/TR/V2
All the best, Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org | www.zerocarbonworld.org | twitter.com/zerocarbonworld
Zero Carbon World is a UK Registered Charity #1141347 From: Nikki Gordon-Bloomfield <nikki@littlecollie.com> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Sunday, 14 April 2013 17:24 To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] Release Firmware
Just a head up:
I flashed my Twizy firmware and it immediately started working.
I flashed Kevin's firmware on his Roadster, and it took about 10 minutes to start working.
Not sure why -- but thought you'd all appreciate the report. :)
I've got a 35 mile round-trip tonight to Bath, and about 120 miles of work-related travel this week in the Twizy, so plenty of time to test it!
Nikki Gordon-Bloomfield
http://about.me/aminorjourney/bio email: nikki@littleCollie.com tel: +44 7901 553308
On 14 Apr 2013, at 17:04, Michael Balzer <dexter@expeedo.de> wrote:
I've had GPS streaming enabled during the last days, and neither GPS nor GSM connectivity are good at the moment. May be related, as streaming means more data communication. But still that should not lead to RAM corruption.
Am 14.04.2013 17:54, schrieb Michael Balzer: > Mark, > > I've got the last but one version in my car, just lacking the new VEHICLE commands. > > I've got two open issues, the minor one being to raise the 12V auto acquisition time even more, as the faults have become better but it's not yet perfect. I'm trying 20 TAD now, as we don't need to be fast on that A/D conversion. > > But a major issue might have turned up: I've just had the second RAM corruption within three days. Effect: > > MP-0 c32,0,106,119,*-OVM-DebugCrash,2013-04-14 14:06:40,0,2.2.7/RT2.6.4/V2,0,0000,20 > MP-0 c32,0,107,119,*-OVM-DebugCrash,2013-04-14 14:25:13,0,2.2.7/RT2.6.4/V2,80,0020,61 > > As there is no checkpoint 61, this means at least the debug variables have been overwritten, was the same with the first occurence (but other values). > > As the module behaves weird afterwards I suppose more variables have been corrupted. > > I've looked through the last changes several times, I'm pretty sure none could have introduced this kind of bug... if I'm the only one experiencing this, maybe I've got some hardware issue as well? > > I'll continue checking the source for possible buffer overruns... > > Regards,
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Hi Mark, Car firmware is version 4.6.5 40 I've had the car from new and I'm not aware of anything unusual about it. ODO - 40608 Trip - 121.3 I cycled through the VDS screens when stationary and it had no impact…. I'll try again when I drive the car later in the day. All the best, [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Mark Webb-Johnson <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Monday, 15 April 2013 07:03 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Kevin, This is strange, and worrying... I checked the logs for your car - it seems that your car has never reported odometer or trip != 0. Even with older firmware v2.2.2 it was always reporting 0 for both odometer and trip. I looked further back, and find the last record with a non-zero odometer reading seems to be back in January (that was firmware v1.3.5, but the odometer reported was 0 even with that firmware a day later). Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday), but a bunch are running v2.2.6 (the previous release) and all those show odometer correctly. I don't think this is anything to do with new firmware - instead it seems to be specific to your car. What is the actual odometer and trip reading in your car at the moment? Anything unusual about it (e.g. old vehicle firmware, etc)? Can you try cycling through the VDS screens next time you go for a drive? Just keep pressing the right-arrow button on the VDS until you cycle back to the main battery screen. Regards, Mark. On 15 Apr, 2013, at 1:34 PM, Kevin Sharpe ZCW wrote: Hi Mark, Thanks for the CAC explanation. I can confirm I do not see ODO change from 0.0 (see attached screen shot). Indeed, I have never seen ODO change and had assumed it was only working on the very latest firmware. I tried resetting the module using the app command and power cycling the hardware. All the best Kevin On 15 Apr 2013, at 01:50, "Mark Webb-Johnson" <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote: Kevin, Thanks for the help testing. CAC is retrieved (a) car is turned on, (b) car is turned off, (c) charge is started - so your experience is expected. The odometer 0 miles is worrying. Is that still the case, or working now? Regards, Mark. On 15 Apr, 2013, at 3:50 AM, Kevin Sharpe ZCW wrote: Ignore my comment regarding CAC which I see now the car is on charge :-) [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org<mailto:kevin.sharpe@zerocarbonworld.org>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Sunday, 14 April 2013 18:32 To: "ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>" <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: [Ovmsdev] FW: Release Firmware Email sent again without the car photo (which exceeded the 1Mbyte file attachment limit)… From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org<mailto:kevin.sharpe@zerocarbonworld.org>> Date: Sunday, 14 April 2013 18:28 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Just to add a little more to Nikki's report… I've seen some odd behaviour with SOC… if you see the attached photo's you'll see STAT report SOC as 46% and then 50% even though the commands were sent within a minute of one another (approximately). You'll also see the app and car displayed 52% and 92m at the same time. I also note that the ODO reports 0.0 mil and I see no CAC in response to a STAT command. Is this expected behaviour with this firmware? Firmware version reported in the app is 2.3.1/TR/V2 All the best, [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Nikki Gordon-Bloomfield <nikki@littlecollie.com<mailto:nikki@littlecollie.com>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Sunday, 14 April 2013 17:24 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Just a head up: I flashed my Twizy firmware and it immediately started working. I flashed Kevin's firmware on his Roadster, and it took about 10 minutes to start working. Not sure why -- but thought you'd all appreciate the report. :) I've got a 35 mile round-trip tonight to Bath, and about 120 miles of work-related travel this week in the Twizy, so plenty of time to test it! Nikki Gordon-Bloomfield http://about.me/aminorjourney/bio email: nikki@littleCollie.com<mailto:nikki@littleCollie.com> tel: +44 7901 553308 On 14 Apr 2013, at 17:04, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: I've had GPS streaming enabled during the last days, and neither GPS nor GSM connectivity are good at the moment. May be related, as streaming means more data communication. But still that should not lead to RAM corruption. Am 14.04.2013 17:54, schrieb Michael Balzer: Mark, I've got the last but one version in my car, just lacking the new VEHICLE commands. I've got two open issues, the minor one being to raise the 12V auto acquisition time even more, as the faults have become better but it's not yet perfect. I'm trying 20 TAD now, as we don't need to be fast on that A/D conversion. But a major issue might have turned up: I've just had the second RAM corruption within three days. Effect: MP-0 c32,0,106,119,*-OVM-DebugCrash,2013-04-14 14:06:40,0,2.2.7/RT2.6.4/V2,0,0000,20 MP-0 c32,0,107,119,*-OVM-DebugCrash,2013-04-14 14:25:13,0,2.2.7/RT2.6.4/V2,80,0020,61 As there is no checkpoint 61, this means at least the debug variables have been overwritten, was the same with the first occurence (but other values). As the module behaves weird afterwards I suppose more variables have been corrupted. I've looked through the last changes several times, I'm pretty sure none could have introduced this kind of bug... if I'm the only one experiencing this, maybe I've got some hardware issue as well? I'll continue checking the source for possible buffer overruns... Regards, Michael Am 14.04.2013 16:29, schrieb Mark Webb-Johnson: I've just built from latest sources, v2.3.1. This is a release candidate, and I have 24 hours to test before i need to send it to China. It is in my car now, and seems ok. I'll do more testing tomorrow. I'd be grateful if others could grab it and put it in their cars to ensure there are no major problems. Regards, Mark. On 13 Apr, 2013, at 10:04 PM, Mark Webb-Johnson <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote: All seems ok. I've committed and pushed my changes (just the stp_ltf_h() function, and change to report cac as 999.99 to server). I've just flashed and it will go in my car tomorrow. Regards, Mark On 13 Apr, 2013, at 2:51 AM, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: Mark, I just checked in my latest changes. In net.c I added the pending send check also to the new net_notify_errorcode send, I think that should be correct, but please have a look. I saw the new stp_f() function, but I don't understand it's purpose yet. What's the difference to my stp_l2f() function? Btw: l2f = "long to float" -- I think "_f" should be reserved for an stp call with a real float type parameter, if we once really need one. Regards, Michael Am 12.04.2013 20:16, schrieb Michael Balzer: Nikki, yes, see attachment. I could not make out any possible source of that strange error I had yesterday (completely garbled data). I made a clean build with a freshly started MPLAB and got no errors up to now. May have been something completely different, not related to my last changes. Regards, Michael Am 12.04.2013 17:01, schrieb Nikki Gordon-Bloomfield: Michael, Any new firmware for me to test this weekend? Nikki. On 11 Apr 2013, at 18:33, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: I think I was a bit too fast on this, Nikki, don't use that version, it seems to have some new bug causing frequent crashes... :-( Regards, Michael Am 11.04.2013 19:22, schrieb Michael Balzer: Mark, Nikki, I'm currently trying to fix a last bug with the power statistics (the distance counter still went wrong), and I'm trying to get the 12V A/D conversion to work without these strange "peaks" by raising the automatic acquisition time. I will finish testing this ASAP or tell you in time before sunday. Nikki, I attached the latest version in case you'd like to test as well. Regards, Michael Am 11.04.2013 16:41, schrieb Mark Webb-Johnson: China is bugging me for final firmware for the next batch of hardware. I need to get them this early next week. I've committed what I need for the Tesla Roadster (and framework). Last outstanding small change to make is to send CAC as 999.99, rather than the current 99999, using Tom's new library function. Michael B & J: can you check Twizzy and Volt/Ampera, to see if everything is ok with current firmware or there is anything you need changed? I plan to cut release candidate for 2.3.1 on Sunday. Regards, Mark. _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
WARNING – I had a VDS "communications fault" followed by "service request" on the VDS this morning (11am). I was cycling through the VDS trying to wake up the ODO and trip as suggested below. Now the OVMS hardware is cycling as follows; (1) Green & Red leds lit for ~ 10 seconds (2) Green led flashes 6 times (repeated 3 times) (3) Green led flashed 4 times (repeated 7 times) Repeat 1 to 3… I'll try a short drive to see if the OVMS recovers. [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Mark Webb-Johnson <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Monday, 15 April 2013 07:03 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Kevin, This is strange, and worrying... I checked the logs for your car - it seems that your car has never reported odometer or trip != 0. Even with older firmware v2.2.2 it was always reporting 0 for both odometer and trip. I looked further back, and find the last record with a non-zero odometer reading seems to be back in January (that was firmware v1.3.5, but the odometer reported was 0 even with that firmware a day later). Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday), but a bunch are running v2.2.6 (the previous release) and all those show odometer correctly. I don't think this is anything to do with new firmware - instead it seems to be specific to your car. What is the actual odometer and trip reading in your car at the moment? Anything unusual about it (e.g. old vehicle firmware, etc)? Can you try cycling through the VDS screens next time you go for a drive? Just keep pressing the right-arrow button on the VDS until you cycle back to the main battery screen. Regards, Mark. On 15 Apr, 2013, at 1:34 PM, Kevin Sharpe ZCW wrote: Hi Mark, Thanks for the CAC explanation. I can confirm I do not see ODO change from 0.0 (see attached screen shot). Indeed, I have never seen ODO change and had assumed it was only working on the very latest firmware. I tried resetting the module using the app command and power cycling the hardware. All the best Kevin On 15 Apr 2013, at 01:50, "Mark Webb-Johnson" <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote: Kevin, Thanks for the help testing. CAC is retrieved (a) car is turned on, (b) car is turned off, (c) charge is started - so your experience is expected. The odometer 0 miles is worrying. Is that still the case, or working now? Regards, Mark. On 15 Apr, 2013, at 3:50 AM, Kevin Sharpe ZCW wrote: Ignore my comment regarding CAC which I see now the car is on charge :-) [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org<mailto:kevin.sharpe@zerocarbonworld.org>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Sunday, 14 April 2013 18:32 To: "ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>" <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: [Ovmsdev] FW: Release Firmware Email sent again without the car photo (which exceeded the 1Mbyte file attachment limit)… From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org<mailto:kevin.sharpe@zerocarbonworld.org>> Date: Sunday, 14 April 2013 18:28 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Just to add a little more to Nikki's report… I've seen some odd behaviour with SOC… if you see the attached photo's you'll see STAT report SOC as 46% and then 50% even though the commands were sent within a minute of one another (approximately). You'll also see the app and car displayed 52% and 92m at the same time. I also note that the ODO reports 0.0 mil and I see no CAC in response to a STAT command. Is this expected behaviour with this firmware? Firmware version reported in the app is 2.3.1/TR/V2 All the best, [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Nikki Gordon-Bloomfield <nikki@littlecollie.com<mailto:nikki@littlecollie.com>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Sunday, 14 April 2013 17:24 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Just a head up: I flashed my Twizy firmware and it immediately started working. I flashed Kevin's firmware on his Roadster, and it took about 10 minutes to start working. Not sure why -- but thought you'd all appreciate the report. :) I've got a 35 mile round-trip tonight to Bath, and about 120 miles of work-related travel this week in the Twizy, so plenty of time to test it! Nikki Gordon-Bloomfield http://about.me/aminorjourney/bio email: nikki@littleCollie.com<mailto:nikki@littleCollie.com> tel: +44 7901 553308 On 14 Apr 2013, at 17:04, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: I've had GPS streaming enabled during the last days, and neither GPS nor GSM connectivity are good at the moment. May be related, as streaming means more data communication. But still that should not lead to RAM corruption. Am 14.04.2013 17:54, schrieb Michael Balzer: Mark, I've got the last but one version in my car, just lacking the new VEHICLE commands. I've got two open issues, the minor one being to raise the 12V auto acquisition time even more, as the faults have become better but it's not yet perfect. I'm trying 20 TAD now, as we don't need to be fast on that A/D conversion. But a major issue might have turned up: I've just had the second RAM corruption within three days. Effect: MP-0 c32,0,106,119,*-OVM-DebugCrash,2013-04-14 14:06:40,0,2.2.7/RT2.6.4/V2,0,0000,20 MP-0 c32,0,107,119,*-OVM-DebugCrash,2013-04-14 14:25:13,0,2.2.7/RT2.6.4/V2,80,0020,61 As there is no checkpoint 61, this means at least the debug variables have been overwritten, was the same with the first occurence (but other values). As the module behaves weird afterwards I suppose more variables have been corrupted. I've looked through the last changes several times, I'm pretty sure none could have introduced this kind of bug... if I'm the only one experiencing this, maybe I've got some hardware issue as well? I'll continue checking the source for possible buffer overruns... Regards, Michael Am 14.04.2013 16:29, schrieb Mark Webb-Johnson: I've just built from latest sources, v2.3.1. This is a release candidate, and I have 24 hours to test before i need to send it to China. It is in my car now, and seems ok. I'll do more testing tomorrow. I'd be grateful if others could grab it and put it in their cars to ensure there are no major problems. Regards, Mark. On 13 Apr, 2013, at 10:04 PM, Mark Webb-Johnson <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote: All seems ok. I've committed and pushed my changes (just the stp_ltf_h() function, and change to report cac as 999.99 to server). I've just flashed and it will go in my car tomorrow. Regards, Mark On 13 Apr, 2013, at 2:51 AM, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: Mark, I just checked in my latest changes. In net.c I added the pending send check also to the new net_notify_errorcode send, I think that should be correct, but please have a look. I saw the new stp_f() function, but I don't understand it's purpose yet. What's the difference to my stp_l2f() function? Btw: l2f = "long to float" -- I think "_f" should be reserved for an stp call with a real float type parameter, if we once really need one. Regards, Michael Am 12.04.2013 20:16, schrieb Michael Balzer: Nikki, yes, see attachment. I could not make out any possible source of that strange error I had yesterday (completely garbled data). I made a clean build with a freshly started MPLAB and got no errors up to now. May have been something completely different, not related to my last changes. Regards, Michael Am 12.04.2013 17:01, schrieb Nikki Gordon-Bloomfield: Michael, Any new firmware for me to test this weekend? Nikki. On 11 Apr 2013, at 18:33, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: I think I was a bit too fast on this, Nikki, don't use that version, it seems to have some new bug causing frequent crashes... :-( Regards, Michael Am 11.04.2013 19:22, schrieb Michael Balzer: Mark, Nikki, I'm currently trying to fix a last bug with the power statistics (the distance counter still went wrong), and I'm trying to get the 12V A/D conversion to work without these strange "peaks" by raising the automatic acquisition time. I will finish testing this ASAP or tell you in time before sunday. Nikki, I attached the latest version in case you'd like to test as well. Regards, Michael Am 11.04.2013 16:41, schrieb Mark Webb-Johnson: China is bugging me for final firmware for the next batch of hardware. I need to get them this early next week. I've committed what I need for the Tesla Roadster (and framework). Last outstanding small change to make is to send CAC as 999.99, rather than the current 99999, using Tom's new library function. Michael B & J: can you check Twizzy and Volt/Ampera, to see if everything is ok with current firmware or there is anything you need changed? I plan to cut release candidate for 2.3.1 on Sunday. Regards, Mark. _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Kevin,
WARNING – I had a VDS "communications fault" followed by "service request" on the VDS this morning (11am).
That is not good. You had a short on one of the CAN bus wires. Most likely a loose connection on the OVMS cable. I suggest you check the cable and make sure no stray wires.
Now the OVMS hardware is cycling as follows; (1) Green & Red leds lit for ~ 10 seconds (2) Green led flashes 6 times (repeated 3 times) (3) Green led flashed 4 times (repeated 7 times)
State 4 (which is the best you got to) is NET_LED_NETAPNOK - half way through initialising GPRS. It couldn't complete the GPRS initialisation successfully, so reset and tried again. This could be a problem with the GSM antenna - I suggest you double-check it is correctly attached and try to push the black antenna cable further into the gold plug (in case it has been pulled out). Regards, Mark. On 15 Apr, 2013, at 6:16 PM, Kevin Sharpe ZCW <kevin.sharpe@zerocarbonworld.org> wrote:
WARNING – I had a VDS "communications fault" followed by "service request" on the VDS this morning (11am).
I was cycling through the VDS trying to wake up the ODO and trip as suggested below.
Now the OVMS hardware is cycling as follows;
(1) Green & Red leds lit for ~ 10 seconds
(2) Green led flashes 6 times (repeated 3 times)
(3) Green led flashed 4 times (repeated 7 times)
Repeat 1 to 3…
I'll try a short drive to see if the OVMS recovers. Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org | www.zerocarbonworld.org | twitter.com/zerocarbonworld
Zero Carbon World is a UK Registered Charity #1141347 From: Mark Webb-Johnson <mark@webb-johnson.net> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Monday, 15 April 2013 07:03 To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] Release Firmware
Kevin,
This is strange, and worrying...
I checked the logs for your car - it seems that your car has never reported odometer or trip != 0. Even with older firmware v2.2.2 it was always reporting 0 for both odometer and trip. I looked further back, and find the last record with a non-zero odometer reading seems to be back in January (that was firmware v1.3.5, but the odometer reported was 0 even with that firmware a day later).
Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday), but a bunch are running v2.2.6 (the previous release) and all those show odometer correctly. I don't think this is anything to do with new firmware - instead it seems to be specific to your car.
What is the actual odometer and trip reading in your car at the moment? Anything unusual about it (e.g. old vehicle firmware, etc)?
Can you try cycling through the VDS screens next time you go for a drive? Just keep pressing the right-arrow button on the VDS until you cycle back to the main battery screen.
Regards, Mark.
On 15 Apr, 2013, at 1:34 PM, Kevin Sharpe ZCW wrote:
Hi Mark,
Thanks for the CAC explanation.
I can confirm I do not see ODO change from 0.0 (see attached screen shot). Indeed, I have never seen ODO change and had assumed it was only working on the very latest firmware.
I tried resetting the module using the app command and power cycling the hardware.
All the best
Kevin
On 15 Apr 2013, at 01:50, "Mark Webb-Johnson" <mark@webb-johnson.net> wrote:
Kevin,
Thanks for the help testing.
CAC is retrieved (a) car is turned on, (b) car is turned off, (c) charge is started - so your experience is expected.
The odometer 0 miles is worrying. Is that still the case, or working now?
Regards, Mark.
On 15 Apr, 2013, at 3:50 AM, Kevin Sharpe ZCW wrote:
Ignore my comment regarding CAC which I see now the car is on charge :-)
Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org | www.zerocarbonworld.org | twitter.com/zerocarbonworld
Zero Carbon World is a UK Registered Charity #1141347 From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Sunday, 14 April 2013 18:32 To: "ovmsdev@lists.teslaclub.hk" <ovmsdev@lists.teslaclub.hk> Subject: [Ovmsdev] FW: Release Firmware
Email sent again without the car photo (which exceeded the 1Mbyte file attachment limit)…
From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org> Date: Sunday, 14 April 2013 18:28 To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] Release Firmware
Just to add a little more to Nikki's report…
I've seen some odd behaviour with SOC… if you see the attached photo's you'll see STAT report SOC as 46% and then 50% even though the commands were sent within a minute of one another (approximately). You'll also see the app and car displayed 52% and 92m at the same time.
I also note that the ODO reports 0.0 mil and I see no CAC in response to a STAT command. Is this expected behaviour with this firmware?
Firmware version reported in the app is 2.3.1/TR/V2
All the best, Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org | www.zerocarbonworld.org | twitter.com/zerocarbonworld
Zero Carbon World is a UK Registered Charity #1141347 From: Nikki Gordon-Bloomfield <nikki@littlecollie.com> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Sunday, 14 April 2013 17:24 To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] Release Firmware
Just a head up:
I flashed my Twizy firmware and it immediately started working.
I flashed Kevin's firmware on his Roadster, and it took about 10 minutes to start working.
Not sure why -- but thought you'd all appreciate the report. :)
I've got a 35 mile round-trip tonight to Bath, and about 120 miles of work-related travel this week in the Twizy, so plenty of time to test it!
Nikki Gordon-Bloomfield
http://about.me/aminorjourney/bio email: nikki@littleCollie.com tel: +44 7901 553308
On 14 Apr 2013, at 17:04, Michael Balzer <dexter@expeedo.de> wrote:
I've had GPS streaming enabled during the last days, and neither GPS nor GSM connectivity are good at the moment. May be related, as streaming means more data communication. But still that should not lead to RAM corruption.
Am 14.04.2013 17:54, schrieb Michael Balzer:
Mark,
I've got the last but one version in my car, just lacking the new VEHICLE commands.
I've got two open issues, the minor one being to raise the 12V auto acquisition time even more, as the faults have become better but it's not yet perfect. I'm trying 20 TAD now, as we don't need to be fast on that A/D conversion.
But a major issue might have turned up: I've just had the second RAM corruption within three days. Effect:
MP-0 c32,0,106,119,*-OVM-DebugCrash,2013-04-14 14:06:40,0,2.2.7/RT2.6.4/V2,0,0000,20 MP-0 c32,0,107,119,*-OVM-DebugCrash,2013-04-14 14:25:13,0,2.2.7/RT2.6.4/V2,80,0020,61
As there is no checkpoint 61, this means at least the debug variables have been overwritten, was the same with the first occurence (but other values).
As the module behaves weird afterwards I suppose more variables have been corrupted.
I've looked through the last changes several times, I'm pretty sure none could have introduced this kind of bug... if I'm the only one experiencing this, maybe I've got some hardware issue as well?
I'll continue checking the source for possible buffer overruns...
Regards, Michael
Am 14.04.2013 16:29, schrieb Mark Webb-Johnson: > > I've just built from latest sources, v2.3.1. This is a release candidate, and I have 24 hours to test before i need to send it to China. > > It is in my car now, and seems ok. I'll do more testing tomorrow. > > I'd be grateful if others could grab it and put it in their cars to ensure there are no major problems. > > Regards, Mark. > > On 13 Apr, 2013, at 10:04 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: > >> All seems ok. >> >> I've committed and pushed my changes (just the stp_ltf_h() function, and change to report cac as 999.99 to server). >> >> I've just flashed and it will go in my car tomorrow. >> >> Regards, Mark >> >> On 13 Apr, 2013, at 2:51 AM, Michael Balzer <dexter@expeedo.de> wrote: >> >>> Mark, >>> >>> I just checked in my latest changes. >>> >>> In net.c I added the pending send check also to the new net_notify_errorcode send, I think that should be correct, but please have a look. >>> >>> I saw the new stp_f() function, but I don't understand it's purpose yet. What's the difference to my stp_l2f() function? >>> Btw: l2f = "long to float" -- I think "_f" should be reserved for an stp call with a real float type parameter, if we once really need one. >>> >>> Regards, >>> Michael >>> >>> >>> Am 12.04.2013 20:16, schrieb Michael Balzer: >>>> Nikki, >>>> >>>> yes, see attachment. >>>> >>>> I could not make out any possible source of that strange error I had yesterday (completely garbled data). >>>> >>>> I made a clean build with a freshly started MPLAB and got no errors up to now. >>>> >>>> May have been something completely different, not related to my last changes. >>>> >>>> Regards, >>>> Michael >>>> >>>> >>>> Am 12.04.2013 17:01, schrieb Nikki Gordon-Bloomfield: >>>>> Michael, >>>>> >>>>> Any new firmware for me to test this weekend? >>>>> >>>>> Nikki. >>>>> >>>>> On 11 Apr 2013, at 18:33, Michael Balzer <dexter@expeedo.de> wrote: >>>>> >>>>>> I think I was a bit too fast on this, Nikki, don't use that version, it seems to have some new bug causing frequent crashes... :-( >>>>>> >>>>>> Regards, >>>>>> Michael >>>>>> >>>>>> >>>>>> Am 11.04.2013 19:22, schrieb Michael Balzer: >>>>>>> Mark, Nikki, >>>>>>> >>>>>>> I'm currently trying to fix a last bug with the power statistics (the distance counter still went wrong), and I'm trying to get the 12V A/D conversion to work without these strange "peaks" by raising the automatic acquisition time. I will finish testing this ASAP or tell you in time before sunday. >>>>>>> >>>>>>> Nikki, I attached the latest version in case you'd like to test as well. >>>>>>> >>>>>>> Regards, >>>>>>> Michael >>>>>>> >>>>>>> >>>>>>> Am 11.04.2013 16:41, schrieb Mark Webb-Johnson: >>>>>>>> China is bugging me for final firmware for the next batch of hardware. I need to get them this early next week. >>>>>>>> >>>>>>>> I've committed what I need for the Tesla Roadster (and framework). Last outstanding small change to make is to send CAC as 999.99, rather than the current 99999, using Tom's new library function. >>>>>>>> >>>>>>>> Michael B & J: can you check Twizzy and Volt/Ampera, to see if everything is ok with current firmware or there is anything you need changed? >>>>>>>> >>>>>>>> I plan to cut release candidate for 2.3.1 on Sunday. >>>>>>>> >>>>>>>> Regards, Mark. >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> OvmsDev mailing list >>>>>>>> OvmsDev@lists.teslaclub.hk >>>>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> OvmsDev mailing list >>>>>>> OvmsDev@lists.teslaclub.hkhttp://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@lists.teslaclub.hk >>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> OvmsDev mailing list >>>>> OvmsDev@lists.teslaclub.hkhttp://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@lists.teslaclub.hkhttp://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@lists.teslaclub.hk >>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >> _______________________________________________ >> OvmsDev mailing list >> OvmsDev@lists.teslaclub.hk >> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > > > > _______________________________________________ > OvmsDev mailing list > OvmsDev@lists.teslaclub.hkhttp://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@lists.teslaclub.hkhttp://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@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Many thanks Mark. Nothing obviously wrong with any of the connections but I retightened them anyway and will keep an eye on it. All the best, [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Mark Webb-Johnson <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Monday, 15 April 2013 13:46 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Kevin, WARNING – I had a VDS "communications fault" followed by "service request" on the VDS this morning (11am). That is not good. You had a short on one of the CAN bus wires. Most likely a loose connection on the OVMS cable. I suggest you check the cable and make sure no stray wires. Now the OVMS hardware is cycling as follows; (1) Green & Red leds lit for ~ 10 seconds (2) Green led flashes 6 times (repeated 3 times) (3) Green led flashed 4 times (repeated 7 times) State 4 (which is the best you got to) is NET_LED_NETAPNOK - half way through initialising GPRS. It couldn't complete the GPRS initialisation successfully, so reset and tried again. This could be a problem with the GSM antenna - I suggest you double-check it is correctly attached and try to push the black antenna cable further into the gold plug (in case it has been pulled out). Regards, Mark. On 15 Apr, 2013, at 6:16 PM, Kevin Sharpe ZCW <kevin.sharpe@zerocarbonworld.org<mailto:kevin.sharpe@zerocarbonworld.org>> wrote: WARNING – I had a VDS "communications fault" followed by "service request" on the VDS this morning (11am). I was cycling through the VDS trying to wake up the ODO and trip as suggested below. Now the OVMS hardware is cycling as follows; (1) Green & Red leds lit for ~ 10 seconds (2) Green led flashes 6 times (repeated 3 times) (3) Green led flashed 4 times (repeated 7 times) Repeat 1 to 3… I'll try a short drive to see if the OVMS recovers. [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Mark Webb-Johnson <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Monday, 15 April 2013 07:03 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Kevin, This is strange, and worrying... I checked the logs for your car - it seems that your car has never reported odometer or trip != 0. Even with older firmware v2.2.2 it was always reporting 0 for both odometer and trip. I looked further back, and find the last record with a non-zero odometer reading seems to be back in January (that was firmware v1.3.5, but the odometer reported was 0 even with that firmware a day later). Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday), but a bunch are running v2.2.6 (the previous release) and all those show odometer correctly. I don't think this is anything to do with new firmware - instead it seems to be specific to your car. What is the actual odometer and trip reading in your car at the moment? Anything unusual about it (e.g. old vehicle firmware, etc)? Can you try cycling through the VDS screens next time you go for a drive? Just keep pressing the right-arrow button on the VDS until you cycle back to the main battery screen. Regards, Mark. On 15 Apr, 2013, at 1:34 PM, Kevin Sharpe ZCW wrote: Hi Mark, Thanks for the CAC explanation. I can confirm I do not see ODO change from 0.0 (see attached screen shot). Indeed, I have never seen ODO change and had assumed it was only working on the very latest firmware. I tried resetting the module using the app command and power cycling the hardware. All the best Kevin On 15 Apr 2013, at 01:50, "Mark Webb-Johnson" <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote: Kevin, Thanks for the help testing. CAC is retrieved (a) car is turned on, (b) car is turned off, (c) charge is started - so your experience is expected. The odometer 0 miles is worrying. Is that still the case, or working now? Regards, Mark. On 15 Apr, 2013, at 3:50 AM, Kevin Sharpe ZCW wrote: Ignore my comment regarding CAC which I see now the car is on charge :-) [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org<mailto:kevin.sharpe@zerocarbonworld.org>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Sunday, 14 April 2013 18:32 To: "ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>" <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: [Ovmsdev] FW: Release Firmware Email sent again without the car photo (which exceeded the 1Mbyte file attachment limit)… From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org<mailto:kevin.sharpe@zerocarbonworld.org>> Date: Sunday, 14 April 2013 18:28 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Just to add a little more to Nikki's report… I've seen some odd behaviour with SOC… if you see the attached photo's you'll see STAT report SOC as 46% and then 50% even though the commands were sent within a minute of one another (approximately). You'll also see the app and car displayed 52% and 92m at the same time. I also note that the ODO reports 0.0 mil and I see no CAC in response to a STAT command. Is this expected behaviour with this firmware? Firmware version reported in the app is 2.3.1/TR/V2 All the best, [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Nikki Gordon-Bloomfield <nikki@littlecollie.com<mailto:nikki@littlecollie.com>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Sunday, 14 April 2013 17:24 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Just a head up: I flashed my Twizy firmware and it immediately started working. I flashed Kevin's firmware on his Roadster, and it took about 10 minutes to start working. Not sure why -- but thought you'd all appreciate the report. :) I've got a 35 mile round-trip tonight to Bath, and about 120 miles of work-related travel this week in the Twizy, so plenty of time to test it! Nikki Gordon-Bloomfield http://about.me/aminorjourney/bio email: nikki@littleCollie.com<mailto:nikki@littleCollie.com> tel: +44 7901 553308 On 14 Apr 2013, at 17:04, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: I've had GPS streaming enabled during the last days, and neither GPS nor GSM connectivity are good at the moment. May be related, as streaming means more data communication. But still that should not lead to RAM corruption. Am 14.04.2013 17:54, schrieb Michael Balzer: Mark, I've got the last but one version in my car, just lacking the new VEHICLE commands. I've got two open issues, the minor one being to raise the 12V auto acquisition time even more, as the faults have become better but it's not yet perfect. I'm trying 20 TAD now, as we don't need to be fast on that A/D conversion. But a major issue might have turned up: I've just had the second RAM corruption within three days. Effect: MP-0 c32,0,106,119,*-OVM-DebugCrash,2013-04-14 14:06:40,0,2.2.7/RT2.6.4/V2,0,0000,20 MP-0 c32,0,107,119,*-OVM-DebugCrash,2013-04-14 14:25:13,0,2.2.7/RT2.6.4/V2,80,0020,61 As there is no checkpoint 61, this means at least the debug variables have been overwritten, was the same with the first occurence (but other values). As the module behaves weird afterwards I suppose more variables have been corrupted. I've looked through the last changes several times, I'm pretty sure none could have introduced this kind of bug... if I'm the only one experiencing this, maybe I've got some hardware issue as well? I'll continue checking the source for possible buffer overruns... Regards, Michael Am 14.04.2013 16:29, schrieb Mark Webb-Johnson: I've just built from latest sources, v2.3.1. This is a release candidate, and I have 24 hours to test before i need to send it to China. It is in my car now, and seems ok. I'll do more testing tomorrow. I'd be grateful if others could grab it and put it in their cars to ensure there are no major problems. Regards, Mark. On 13 Apr, 2013, at 10:04 PM, Mark Webb-Johnson <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote: All seems ok. I've committed and pushed my changes (just the stp_ltf_h() function, and change to report cac as 999.99 to server). I've just flashed and it will go in my car tomorrow. Regards, Mark On 13 Apr, 2013, at 2:51 AM, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: Mark, I just checked in my latest changes. In net.c I added the pending send check also to the new net_notify_errorcode send, I think that should be correct, but please have a look. I saw the new stp_f() function, but I don't understand it's purpose yet. What's the difference to my stp_l2f() function? Btw: l2f = "long to float" -- I think "_f" should be reserved for an stp call with a real float type parameter, if we once really need one. Regards, Michael Am 12.04.2013 20:16, schrieb Michael Balzer: Nikki, yes, see attachment. I could not make out any possible source of that strange error I had yesterday (completely garbled data). I made a clean build with a freshly started MPLAB and got no errors up to now. May have been something completely different, not related to my last changes. Regards, Michael Am 12.04.2013 17:01, schrieb Nikki Gordon-Bloomfield: Michael, Any new firmware for me to test this weekend? Nikki. On 11 Apr 2013, at 18:33, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: I think I was a bit too fast on this, Nikki, don't use that version, it seems to have some new bug causing frequent crashes... :-( Regards, Michael Am 11.04.2013 19:22, schrieb Michael Balzer: Mark, Nikki, I'm currently trying to fix a last bug with the power statistics (the distance counter still went wrong), and I'm trying to get the 12V A/D conversion to work without these strange "peaks" by raising the automatic acquisition time. I will finish testing this ASAP or tell you in time before sunday. Nikki, I attached the latest version in case you'd like to test as well. Regards, Michael Am 11.04.2013 16:41, schrieb Mark Webb-Johnson: China is bugging me for final firmware for the next batch of hardware. I need to get them this early next week. I've committed what I need for the Tesla Roadster (and framework). Last outstanding small change to make is to send CAC as 999.99, rather than the current 99999, using Tom's new library function. Michael B & J: can you check Twizzy and Volt/Ampera, to see if everything is ok with current firmware or there is anything you need changed? I plan to cut release candidate for 2.3.1 on Sunday. Regards, Mark. _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Hi Mark, Brief update… I was delayed by ~10 minutes before returning to drive the car… at this point the OVMS module was flashing just a single green led… looks like the unit is very slow to connect (same issue we had at Nikki's location yesterday). I drove the car for a few miles and tried cycling through the VDS screen but it had no impact on ODO reports following a stat command (still 0 miles). Also happy to report no more VDS comms issue reports. Here for the record are the current car figures; ODO - 40613 Trip - 126.5 I'll try and drive the car again later in the day. All the best, [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Mark Webb-Johnson <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Monday, 15 April 2013 07:03 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Kevin, This is strange, and worrying... I checked the logs for your car - it seems that your car has never reported odometer or trip != 0. Even with older firmware v2.2.2 it was always reporting 0 for both odometer and trip. I looked further back, and find the last record with a non-zero odometer reading seems to be back in January (that was firmware v1.3.5, but the odometer reported was 0 even with that firmware a day later). Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday), but a bunch are running v2.2.6 (the previous release) and all those show odometer correctly. I don't think this is anything to do with new firmware - instead it seems to be specific to your car. What is the actual odometer and trip reading in your car at the moment? Anything unusual about it (e.g. old vehicle firmware, etc)? Can you try cycling through the VDS screens next time you go for a drive? Just keep pressing the right-arrow button on the VDS until you cycle back to the main battery screen. Regards, Mark. On 15 Apr, 2013, at 1:34 PM, Kevin Sharpe ZCW wrote: Hi Mark, Thanks for the CAC explanation. I can confirm I do not see ODO change from 0.0 (see attached screen shot). Indeed, I have never seen ODO change and had assumed it was only working on the very latest firmware. I tried resetting the module using the app command and power cycling the hardware. All the best Kevin On 15 Apr 2013, at 01:50, "Mark Webb-Johnson" <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote: Kevin, Thanks for the help testing. CAC is retrieved (a) car is turned on, (b) car is turned off, (c) charge is started - so your experience is expected. The odometer 0 miles is worrying. Is that still the case, or working now? Regards, Mark. On 15 Apr, 2013, at 3:50 AM, Kevin Sharpe ZCW wrote: Ignore my comment regarding CAC which I see now the car is on charge :-) [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org<mailto:kevin.sharpe@zerocarbonworld.org>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Sunday, 14 April 2013 18:32 To: "ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>" <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: [Ovmsdev] FW: Release Firmware Email sent again without the car photo (which exceeded the 1Mbyte file attachment limit)… From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org<mailto:kevin.sharpe@zerocarbonworld.org>> Date: Sunday, 14 April 2013 18:28 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Just to add a little more to Nikki's report… I've seen some odd behaviour with SOC… if you see the attached photo's you'll see STAT report SOC as 46% and then 50% even though the commands were sent within a minute of one another (approximately). You'll also see the app and car displayed 52% and 92m at the same time. I also note that the ODO reports 0.0 mil and I see no CAC in response to a STAT command. Is this expected behaviour with this firmware? Firmware version reported in the app is 2.3.1/TR/V2 All the best, [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Nikki Gordon-Bloomfield <nikki@littlecollie.com<mailto:nikki@littlecollie.com>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Sunday, 14 April 2013 17:24 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Just a head up: I flashed my Twizy firmware and it immediately started working. I flashed Kevin's firmware on his Roadster, and it took about 10 minutes to start working. Not sure why -- but thought you'd all appreciate the report. :) I've got a 35 mile round-trip tonight to Bath, and about 120 miles of work-related travel this week in the Twizy, so plenty of time to test it! Nikki Gordon-Bloomfield http://about.me/aminorjourney/bio email: nikki@littleCollie.com<mailto:nikki@littleCollie.com> tel: +44 7901 553308 On 14 Apr 2013, at 17:04, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: I've had GPS streaming enabled during the last days, and neither GPS nor GSM connectivity are good at the moment. May be related, as streaming means more data communication. But still that should not lead to RAM corruption. Am 14.04.2013 17:54, schrieb Michael Balzer: Mark, I've got the last but one version in my car, just lacking the new VEHICLE commands. I've got two open issues, the minor one being to raise the 12V auto acquisition time even more, as the faults have become better but it's not yet perfect. I'm trying 20 TAD now, as we don't need to be fast on that A/D conversion. But a major issue might have turned up: I've just had the second RAM corruption within three days. Effect: MP-0 c32,0,106,119,*-OVM-DebugCrash,2013-04-14 14:06:40,0,2.2.7/RT2.6.4/V2,0,0000,20 MP-0 c32,0,107,119,*-OVM-DebugCrash,2013-04-14 14:25:13,0,2.2.7/RT2.6.4/V2,80,0020,61 As there is no checkpoint 61, this means at least the debug variables have been overwritten, was the same with the first occurence (but other values). As the module behaves weird afterwards I suppose more variables have been corrupted. I've looked through the last changes several times, I'm pretty sure none could have introduced this kind of bug... if I'm the only one experiencing this, maybe I've got some hardware issue as well? I'll continue checking the source for possible buffer overruns... Regards, Michael Am 14.04.2013 16:29, schrieb Mark Webb-Johnson: I've just built from latest sources, v2.3.1. This is a release candidate, and I have 24 hours to test before i need to send it to China. It is in my car now, and seems ok. I'll do more testing tomorrow. I'd be grateful if others could grab it and put it in their cars to ensure there are no major problems. Regards, Mark. On 13 Apr, 2013, at 10:04 PM, Mark Webb-Johnson <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote: All seems ok. I've committed and pushed my changes (just the stp_ltf_h() function, and change to report cac as 999.99 to server). I've just flashed and it will go in my car tomorrow. Regards, Mark On 13 Apr, 2013, at 2:51 AM, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: Mark, I just checked in my latest changes. In net.c I added the pending send check also to the new net_notify_errorcode send, I think that should be correct, but please have a look. I saw the new stp_f() function, but I don't understand it's purpose yet. What's the difference to my stp_l2f() function? Btw: l2f = "long to float" -- I think "_f" should be reserved for an stp call with a real float type parameter, if we once really need one. Regards, Michael Am 12.04.2013 20:16, schrieb Michael Balzer: Nikki, yes, see attachment. I could not make out any possible source of that strange error I had yesterday (completely garbled data). I made a clean build with a freshly started MPLAB and got no errors up to now. May have been something completely different, not related to my last changes. Regards, Michael Am 12.04.2013 17:01, schrieb Nikki Gordon-Bloomfield: Michael, Any new firmware for me to test this weekend? Nikki. On 11 Apr 2013, at 18:33, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: I think I was a bit too fast on this, Nikki, don't use that version, it seems to have some new bug causing frequent crashes... :-( Regards, Michael Am 11.04.2013 19:22, schrieb Michael Balzer: Mark, Nikki, I'm currently trying to fix a last bug with the power statistics (the distance counter still went wrong), and I'm trying to get the 12V A/D conversion to work without these strange "peaks" by raising the automatic acquisition time. I will finish testing this ASAP or tell you in time before sunday. Nikki, I attached the latest version in case you'd like to test as well. Regards, Michael Am 11.04.2013 16:41, schrieb Mark Webb-Johnson: China is bugging me for final firmware for the next batch of hardware. I need to get them this early next week. I've committed what I need for the Tesla Roadster (and framework). Last outstanding small change to make is to send CAC as 999.99, rather than the current 99999, using Tom's new library function. Michael B & J: can you check Twizzy and Volt/Ampera, to see if everything is ok with current firmware or there is anything you need changed? I plan to cut release candidate for 2.3.1 on Sunday. Regards, Mark. _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Still no difference. Perhaps the easiest is to wait for the current rush to die-down (v2.3.1 firmware to China factory) and then build you a custom firmware which will give us information on that odometer CAN bus message. Alternatively, if possible you could try your module in someone else's car or someone else's module in your car, to narrow it down. Regards, Mark. On 15 Apr, 2013, at 7:01 PM, Kevin Sharpe ZCW <kevin.sharpe@zerocarbonworld.org> wrote:
Hi Mark,
Brief update…
I was delayed by ~10 minutes before returning to drive the car… at this point the OVMS module was flashing just a single green led… looks like the unit is very slow to connect (same issue we had at Nikki's location yesterday).
I drove the car for a few miles and tried cycling through the VDS screen but it had no impact on ODO reports following a stat command (still 0 miles). Also happy to report no more VDS comms issue reports.
Here for the record are the current car figures;
ODO - 40613
Trip - 126.5
I'll try and drive the car again later in the day.
All the best, Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org | www.zerocarbonworld.org | twitter.com/zerocarbonworld
Zero Carbon World is a UK Registered Charity #1141347 From: Mark Webb-Johnson <mark@webb-johnson.net> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Monday, 15 April 2013 07:03 To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] Release Firmware
Kevin,
This is strange, and worrying...
I checked the logs for your car - it seems that your car has never reported odometer or trip != 0. Even with older firmware v2.2.2 it was always reporting 0 for both odometer and trip. I looked further back, and find the last record with a non-zero odometer reading seems to be back in January (that was firmware v1.3.5, but the odometer reported was 0 even with that firmware a day later).
Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday), but a bunch are running v2.2.6 (the previous release) and all those show odometer correctly. I don't think this is anything to do with new firmware - instead it seems to be specific to your car.
What is the actual odometer and trip reading in your car at the moment? Anything unusual about it (e.g. old vehicle firmware, etc)?
Can you try cycling through the VDS screens next time you go for a drive? Just keep pressing the right-arrow button on the VDS until you cycle back to the main battery screen.
Regards, Mark.
On 15 Apr, 2013, at 1:34 PM, Kevin Sharpe ZCW wrote:
Hi Mark,
Thanks for the CAC explanation.
I can confirm I do not see ODO change from 0.0 (see attached screen shot). Indeed, I have never seen ODO change and had assumed it was only working on the very latest firmware.
I tried resetting the module using the app command and power cycling the hardware.
All the best
Kevin
On 15 Apr 2013, at 01:50, "Mark Webb-Johnson" <mark@webb-johnson.net> wrote:
Kevin,
Thanks for the help testing.
CAC is retrieved (a) car is turned on, (b) car is turned off, (c) charge is started - so your experience is expected.
The odometer 0 miles is worrying. Is that still the case, or working now?
Regards, Mark.
On 15 Apr, 2013, at 3:50 AM, Kevin Sharpe ZCW wrote:
Ignore my comment regarding CAC which I see now the car is on charge :-)
Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org | www.zerocarbonworld.org | twitter.com/zerocarbonworld
Zero Carbon World is a UK Registered Charity #1141347 From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Sunday, 14 April 2013 18:32 To: "ovmsdev@lists.teslaclub.hk" <ovmsdev@lists.teslaclub.hk> Subject: [Ovmsdev] FW: Release Firmware
Email sent again without the car photo (which exceeded the 1Mbyte file attachment limit)…
From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org> Date: Sunday, 14 April 2013 18:28 To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] Release Firmware
Just to add a little more to Nikki's report…
I've seen some odd behaviour with SOC… if you see the attached photo's you'll see STAT report SOC as 46% and then 50% even though the commands were sent within a minute of one another (approximately). You'll also see the app and car displayed 52% and 92m at the same time.
I also note that the ODO reports 0.0 mil and I see no CAC in response to a STAT command. Is this expected behaviour with this firmware?
Firmware version reported in the app is 2.3.1/TR/V2
All the best, Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org | www.zerocarbonworld.org | twitter.com/zerocarbonworld
Zero Carbon World is a UK Registered Charity #1141347 From: Nikki Gordon-Bloomfield <nikki@littlecollie.com> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Sunday, 14 April 2013 17:24 To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] Release Firmware
Just a head up:
I flashed my Twizy firmware and it immediately started working.
I flashed Kevin's firmware on his Roadster, and it took about 10 minutes to start working.
Not sure why -- but thought you'd all appreciate the report. :)
I've got a 35 mile round-trip tonight to Bath, and about 120 miles of work-related travel this week in the Twizy, so plenty of time to test it!
Nikki Gordon-Bloomfield
http://about.me/aminorjourney/bio email: nikki@littleCollie.com tel: +44 7901 553308
On 14 Apr 2013, at 17:04, Michael Balzer <dexter@expeedo.de> wrote:
I've had GPS streaming enabled during the last days, and neither GPS nor GSM connectivity are good at the moment. May be related, as streaming means more data communication. But still that should not lead to RAM corruption.
Am 14.04.2013 17:54, schrieb Michael Balzer:
Mark,
I've got the last but one version in my car, just lacking the new VEHICLE commands.
I've got two open issues, the minor one being to raise the 12V auto acquisition time even more, as the faults have become better but it's not yet perfect. I'm trying 20 TAD now, as we don't need to be fast on that A/D conversion.
But a major issue might have turned up: I've just had the second RAM corruption within three days. Effect:
MP-0 c32,0,106,119,*-OVM-DebugCrash,2013-04-14 14:06:40,0,2.2.7/RT2.6.4/V2,0,0000,20 MP-0 c32,0,107,119,*-OVM-DebugCrash,2013-04-14 14:25:13,0,2.2.7/RT2.6.4/V2,80,0020,61
As there is no checkpoint 61, this means at least the debug variables have been overwritten, was the same with the first occurence (but other values).
As the module behaves weird afterwards I suppose more variables have been corrupted.
I've looked through the last changes several times, I'm pretty sure none could have introduced this kind of bug... if I'm the only one experiencing this, maybe I've got some hardware issue as well?
I'll continue checking the source for possible buffer overruns...
Regards, Michael
Am 14.04.2013 16:29, schrieb Mark Webb-Johnson: > > I've just built from latest sources, v2.3.1. This is a release candidate, and I have 24 hours to test before i need to send it to China. > > It is in my car now, and seems ok. I'll do more testing tomorrow. > > I'd be grateful if others could grab it and put it in their cars to ensure there are no major problems. > > Regards, Mark. > > On 13 Apr, 2013, at 10:04 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: > >> All seems ok. >> >> I've committed and pushed my changes (just the stp_ltf_h() function, and change to report cac as 999.99 to server). >> >> I've just flashed and it will go in my car tomorrow. >> >> Regards, Mark >> >> On 13 Apr, 2013, at 2:51 AM, Michael Balzer <dexter@expeedo.de> wrote: >> >>> Mark, >>> >>> I just checked in my latest changes. >>> >>> In net.c I added the pending send check also to the new net_notify_errorcode send, I think that should be correct, but please have a look. >>> >>> I saw the new stp_f() function, but I don't understand it's purpose yet. What's the difference to my stp_l2f() function? >>> Btw: l2f = "long to float" -- I think "_f" should be reserved for an stp call with a real float type parameter, if we once really need one. >>> >>> Regards, >>> Michael >>> >>> >>> Am 12.04.2013 20:16, schrieb Michael Balzer: >>>> Nikki, >>>> >>>> yes, see attachment. >>>> >>>> I could not make out any possible source of that strange error I had yesterday (completely garbled data). >>>> >>>> I made a clean build with a freshly started MPLAB and got no errors up to now. >>>> >>>> May have been something completely different, not related to my last changes. >>>> >>>> Regards, >>>> Michael >>>> >>>> >>>> Am 12.04.2013 17:01, schrieb Nikki Gordon-Bloomfield: >>>>> Michael, >>>>> >>>>> Any new firmware for me to test this weekend? >>>>> >>>>> Nikki. >>>>> >>>>> On 11 Apr 2013, at 18:33, Michael Balzer <dexter@expeedo.de> wrote: >>>>> >>>>>> I think I was a bit too fast on this, Nikki, don't use that version, it seems to have some new bug causing frequent crashes... :-( >>>>>> >>>>>> Regards, >>>>>> Michael >>>>>> >>>>>> >>>>>> Am 11.04.2013 19:22, schrieb Michael Balzer: >>>>>>> Mark, Nikki, >>>>>>> >>>>>>> I'm currently trying to fix a last bug with the power statistics (the distance counter still went wrong), and I'm trying to get the 12V A/D conversion to work without these strange "peaks" by raising the automatic acquisition time. I will finish testing this ASAP or tell you in time before sunday. >>>>>>> >>>>>>> Nikki, I attached the latest version in case you'd like to test as well. >>>>>>> >>>>>>> Regards, >>>>>>> Michael >>>>>>> >>>>>>> >>>>>>> Am 11.04.2013 16:41, schrieb Mark Webb-Johnson: >>>>>>>> China is bugging me for final firmware for the next batch of hardware. I need to get them this early next week. >>>>>>>> >>>>>>>> I've committed what I need for the Tesla Roadster (and framework). Last outstanding small change to make is to send CAC as 999.99, rather than the current 99999, using Tom's new library function. >>>>>>>> >>>>>>>> Michael B & J: can you check Twizzy and Volt/Ampera, to see if everything is ok with current firmware or there is anything you need changed? >>>>>>>> >>>>>>>> I plan to cut release candidate for 2.3.1 on Sunday. >>>>>>>> >>>>>>>> Regards, Mark. >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> OvmsDev mailing list >>>>>>>> OvmsDev@lists.teslaclub.hk >>>>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> OvmsDev mailing list >>>>>>> OvmsDev@lists.teslaclub.hkhttp://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@lists.teslaclub.hk >>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> OvmsDev mailing list >>>>> OvmsDev@lists.teslaclub.hkhttp://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@lists.teslaclub.hkhttp://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@lists.teslaclub.hk >>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >> _______________________________________________ >> OvmsDev mailing list >> OvmsDev@lists.teslaclub.hk >> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > > > > _______________________________________________ > OvmsDev mailing list > OvmsDev@lists.teslaclub.hkhttp://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@lists.teslaclub.hkhttp://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@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Hi Mark, Agreed, it makes sense to get the firmware deployed to the factory :-) When we have more OVMS hardware here then I'll test with another module and cable set. All the best, [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Mark Webb-Johnson <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Monday, 15 April 2013 13:51 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Still no difference. Perhaps the easiest is to wait for the current rush to die-down (v2.3.1 firmware to China factory) and then build you a custom firmware which will give us information on that odometer CAN bus message. Alternatively, if possible you could try your module in someone else's car or someone else's module in your car, to narrow it down. Regards, Mark. On 15 Apr, 2013, at 7:01 PM, Kevin Sharpe ZCW <kevin.sharpe@zerocarbonworld.org<mailto:kevin.sharpe@zerocarbonworld.org>> wrote: Hi Mark, Brief update… I was delayed by ~10 minutes before returning to drive the car… at this point the OVMS module was flashing just a single green led… looks like the unit is very slow to connect (same issue we had at Nikki's location yesterday). I drove the car for a few miles and tried cycling through the VDS screen but it had no impact on ODO reports following a stat command (still 0 miles). Also happy to report no more VDS comms issue reports. Here for the record are the current car figures; ODO - 40613 Trip - 126.5 I'll try and drive the car again later in the day. All the best, [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Mark Webb-Johnson <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Monday, 15 April 2013 07:03 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Kevin, This is strange, and worrying... I checked the logs for your car - it seems that your car has never reported odometer or trip != 0. Even with older firmware v2.2.2 it was always reporting 0 for both odometer and trip. I looked further back, and find the last record with a non-zero odometer reading seems to be back in January (that was firmware v1.3.5, but the odometer reported was 0 even with that firmware a day later). Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday), but a bunch are running v2.2.6 (the previous release) and all those show odometer correctly. I don't think this is anything to do with new firmware - instead it seems to be specific to your car. What is the actual odometer and trip reading in your car at the moment? Anything unusual about it (e.g. old vehicle firmware, etc)? Can you try cycling through the VDS screens next time you go for a drive? Just keep pressing the right-arrow button on the VDS until you cycle back to the main battery screen. Regards, Mark. On 15 Apr, 2013, at 1:34 PM, Kevin Sharpe ZCW wrote: Hi Mark, Thanks for the CAC explanation. I can confirm I do not see ODO change from 0.0 (see attached screen shot). Indeed, I have never seen ODO change and had assumed it was only working on the very latest firmware. I tried resetting the module using the app command and power cycling the hardware. All the best Kevin On 15 Apr 2013, at 01:50, "Mark Webb-Johnson" <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote: Kevin, Thanks for the help testing. CAC is retrieved (a) car is turned on, (b) car is turned off, (c) charge is started - so your experience is expected. The odometer 0 miles is worrying. Is that still the case, or working now? Regards, Mark. On 15 Apr, 2013, at 3:50 AM, Kevin Sharpe ZCW wrote: Ignore my comment regarding CAC which I see now the car is on charge :-) [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org<mailto:kevin.sharpe@zerocarbonworld.org>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Sunday, 14 April 2013 18:32 To: "ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>" <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: [Ovmsdev] FW: Release Firmware Email sent again without the car photo (which exceeded the 1Mbyte file attachment limit)… From: Kevin Sharpe <kevin.sharpe@zerocarbonworld.org<mailto:kevin.sharpe@zerocarbonworld.org>> Date: Sunday, 14 April 2013 18:28 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Just to add a little more to Nikki's report… I've seen some odd behaviour with SOC… if you see the attached photo's you'll see STAT report SOC as 46% and then 50% even though the commands were sent within a minute of one another (approximately). You'll also see the app and car displayed 52% and 92m at the same time. I also note that the ODO reports 0.0 mil and I see no CAC in response to a STAT command. Is this expected behaviour with this firmware? Firmware version reported in the app is 2.3.1/TR/V2 All the best, [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Nikki Gordon-Bloomfield <nikki@littlecollie.com<mailto:nikki@littlecollie.com>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Sunday, 14 April 2013 17:24 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] Release Firmware Just a head up: I flashed my Twizy firmware and it immediately started working. I flashed Kevin's firmware on his Roadster, and it took about 10 minutes to start working. Not sure why -- but thought you'd all appreciate the report. :) I've got a 35 mile round-trip tonight to Bath, and about 120 miles of work-related travel this week in the Twizy, so plenty of time to test it! Nikki Gordon-Bloomfield http://about.me/aminorjourney/bio email: nikki@littleCollie.com<mailto:nikki@littleCollie.com> tel: +44 7901 553308 On 14 Apr 2013, at 17:04, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: I've had GPS streaming enabled during the last days, and neither GPS nor GSM connectivity are good at the moment. May be related, as streaming means more data communication. But still that should not lead to RAM corruption. Am 14.04.2013 17:54, schrieb Michael Balzer: Mark, I've got the last but one version in my car, just lacking the new VEHICLE commands. I've got two open issues, the minor one being to raise the 12V auto acquisition time even more, as the faults have become better but it's not yet perfect. I'm trying 20 TAD now, as we don't need to be fast on that A/D conversion. But a major issue might have turned up: I've just had the second RAM corruption within three days. Effect: MP-0 c32,0,106,119,*-OVM-DebugCrash,2013-04-14 14:06:40,0,2.2.7/RT2.6.4/V2,0,0000,20 MP-0 c32,0,107,119,*-OVM-DebugCrash,2013-04-14 14:25:13,0,2.2.7/RT2.6.4/V2,80,0020,61 As there is no checkpoint 61, this means at least the debug variables have been overwritten, was the same with the first occurence (but other values). As the module behaves weird afterwards I suppose more variables have been corrupted. I've looked through the last changes several times, I'm pretty sure none could have introduced this kind of bug... if I'm the only one experiencing this, maybe I've got some hardware issue as well? I'll continue checking the source for possible buffer overruns... Regards, Michael Am 14.04.2013 16:29, schrieb Mark Webb-Johnson: I've just built from latest sources, v2.3.1. This is a release candidate, and I have 24 hours to test before i need to send it to China. It is in my car now, and seems ok. I'll do more testing tomorrow. I'd be grateful if others could grab it and put it in their cars to ensure there are no major problems. Regards, Mark. On 13 Apr, 2013, at 10:04 PM, Mark Webb-Johnson <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote: All seems ok. I've committed and pushed my changes (just the stp_ltf_h() function, and change to report cac as 999.99 to server). I've just flashed and it will go in my car tomorrow. Regards, Mark On 13 Apr, 2013, at 2:51 AM, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: Mark, I just checked in my latest changes. In net.c I added the pending send check also to the new net_notify_errorcode send, I think that should be correct, but please have a look. I saw the new stp_f() function, but I don't understand it's purpose yet. What's the difference to my stp_l2f() function? Btw: l2f = "long to float" -- I think "_f" should be reserved for an stp call with a real float type parameter, if we once really need one. Regards, Michael Am 12.04.2013 20:16, schrieb Michael Balzer: Nikki, yes, see attachment. I could not make out any possible source of that strange error I had yesterday (completely garbled data). I made a clean build with a freshly started MPLAB and got no errors up to now. May have been something completely different, not related to my last changes. Regards, Michael Am 12.04.2013 17:01, schrieb Nikki Gordon-Bloomfield: Michael, Any new firmware for me to test this weekend? Nikki. On 11 Apr 2013, at 18:33, Michael Balzer <dexter@expeedo.de<mailto:dexter@expeedo.de>> wrote: I think I was a bit too fast on this, Nikki, don't use that version, it seems to have some new bug causing frequent crashes... :-( Regards, Michael Am 11.04.2013 19:22, schrieb Michael Balzer: Mark, Nikki, I'm currently trying to fix a last bug with the power statistics (the distance counter still went wrong), and I'm trying to get the 12V A/D conversion to work without these strange "peaks" by raising the automatic acquisition time. I will finish testing this ASAP or tell you in time before sunday. Nikki, I attached the latest version in case you'd like to test as well. Regards, Michael Am 11.04.2013 16:41, schrieb Mark Webb-Johnson: China is bugging me for final firmware for the next batch of hardware. I need to get them this early next week. I've committed what I need for the Tesla Roadster (and framework). Last outstanding small change to make is to send CAC as 999.99, rather than the current 99999, using Tom's new library function. Michael B & J: can you check Twizzy and Volt/Ampera, to see if everything is ok with current firmware or there is anything you need changed? I plan to cut release candidate for 2.3.1 on Sunday. Regards, Mark. _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@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@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
on 4/14/13 11:03 PM, Mark Webb-Johnson wrote:
Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday)
I just put it in my v1.5 Roadster. It seems to be working fine (iPhone app updates, SMS stat command shows the expected values). I can post 2.3.1 on my firmware update page as soon as you're ready for that. For anyone who wants the firmware links: 2.3.1 for V1 hardware: https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V1_production.hex 2.3.1 for V2 hardware: https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V2_production.hex Tom
Hi Mark Just flashed my OVMS with your experimental github version 2.3.1 The App works fine, but the SMS shows some difference in comparison to what it looked like with the previous firmware: the ODO and the CAC values have different formats. ODO: I think it's in miles now and before it was km. CAC: now it's reported correctly with 3 digits - point - 2 digits. Piotr -----Ursprüngliche Nachricht----- Von: ovmsdev-bounces@lists.teslaclub.hk [mailto:ovmsdev-bounces@lists.teslaclub.hk] Im Auftrag von Tom Saxton Gesendet: Montag, 15. April 2013 18:02 An: OVMS Developers Betreff: Re: [Ovmsdev] Release Firmware on 4/14/13 11:03 PM, Mark Webb-Johnson wrote:
Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday)
I just put it in my v1.5 Roadster. It seems to be working fine (iPhone app updates, SMS stat command shows the expected values). I can post 2.3.1 on my firmware update page as soon as you're ready for that. For anyone who wants the firmware links: 2.3.1 for V1 hardware: https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V1_production.hex 2.3.1 for V2 hardware: https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V2_production.hex Tom _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Piotr, Thanks (and also to Pierre) for finding this. There was a bug in the SMS STAT code that always reported the odometer in miles - so only Km users noticed it. I just pushed a fix. It is not major, but still not nice. Anyway, I will build v1.3.2 tonight (with just this one fix) - nothing else obviously wrong so let's go with this version. Thanks to everyone for your help testing. Regards, Mark. On 16 Apr, 2013, at 2:54 AM, 911carrera4 wrote:
Hi Mark
Just flashed my OVMS with your experimental github version 2.3.1 The App works fine, but the SMS shows some difference in comparison to what it looked like with the previous firmware: the ODO and the CAC values have different formats. ODO: I think it's in miles now and before it was km. CAC: now it's reported correctly with 3 digits - point - 2 digits.
Piotr
-----Ursprüngliche Nachricht----- Von: ovmsdev-bounces@lists.teslaclub.hk [mailto:ovmsdev-bounces@lists.teslaclub.hk] Im Auftrag von Tom Saxton Gesendet: Montag, 15. April 2013 18:02 An: OVMS Developers Betreff: Re: [Ovmsdev] Release Firmware
on 4/14/13 11:03 PM, Mark Webb-Johnson wrote:
Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday)
I just put it in my v1.5 Roadster. It seems to be working fine (iPhone app updates, SMS stat command shows the expected values).
I can post 2.3.1 on my firmware update page as soon as you're ready for that.
For anyone who wants the firmware links:
2.3.1 for V1 hardware:
https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V1_production.hex
2.3.1 for V2 hardware:
https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V2_production.hex
Tom
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <IMG_2622.PNG>_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Tom, I think the SMS STAT odometer bug is serious enough to require a new build. The good news is that seems to be it, and the fix is simple. I'll build v1.3.2 tonight and that can be the one to announce and release. Regards, Mark. On 16 Apr, 2013, at 12:01 AM, Tom Saxton wrote:
on 4/14/13 11:03 PM, Mark Webb-Johnson wrote:
Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday)
I just put it in my v1.5 Roadster. It seems to be working fine (iPhone app updates, SMS stat command shows the expected values).
I can post 2.3.1 on my firmware update page as soon as you're ready for that.
For anyone who wants the firmware links:
2.3.1 for V1 hardware:
https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V1_production.hex
2.3.1 for V2 hardware:
https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V2_production.hex
Tom
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
I can't believe I missed that! Before sending you the diff, I switched my module to km and tested the status message. I verified that the ideal and estimated range changed values and displayed as expected, and that the odometer was shown in km, but didn't catch that it was still showing the value for miles. I saw Pierre's message just a few minutes ago and did a git pull to look at the code and couldn't see what was wrong. I was thinking it had to be a compiler bug. Then I saw your message that you had just fixed it, and looked back at the history to see what the bug was. I have the firmware update page ready to update. Tom on 4/15/13 5:34 PM, Mark Webb-Johnson wrote:
Tom,
I think the SMS STAT odometer bug is serious enough to require a new build. The good news is that seems to be it, and the fix is simple.
I'll build v1.3.2 tonight and that can be the one to announce and release.
Regards, Mark.
On 16 Apr, 2013, at 12:01 AM, Tom Saxton wrote:
on 4/14/13 11:03 PM, Mark Webb-Johnson wrote:
Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday)
I just put it in my v1.5 Roadster. It seems to be working fine (iPhone app updates, SMS stat command shows the expected values).
I can post 2.3.1 on my firmware update page as soon as you're ready for that.
For anyone who wants the firmware links:
2.3.1 for V1 hardware:
https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V1_production.hex
2.3.1 for V2 hardware:
https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V2_production.hex
Tom
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
mark, this mornig me and karin got two new alerts we didn't use to get with the previous versions of firmware Piotr Von meinem iPhone gesendet Am 16.04.2013 um 03:09 schrieb Tom Saxton <tom@idleloop.com>:
I can't believe I missed that! Before sending you the diff, I switched my module to km and tested the status message. I verified that the ideal and estimated range changed values and displayed as expected, and that the odometer was shown in km, but didn't catch that it was still showing the value for miles.
I saw Pierre's message just a few minutes ago and did a git pull to look at the code and couldn't see what was wrong. I was thinking it had to be a compiler bug. Then I saw your message that you had just fixed it, and looked back at the history to see what the bug was.
I have the firmware update page ready to update.
Tom
on 4/15/13 5:34 PM, Mark Webb-Johnson wrote:
Tom,
I think the SMS STAT odometer bug is serious enough to require a new build. The good news is that seems to be it, and the fix is simple.
I'll build v1.3.2 tonight and that can be the one to announce and release.
Regards, Mark.
On 16 Apr, 2013, at 12:01 AM, Tom Saxton wrote:
on 4/14/13 11:03 PM, Mark Webb-Johnson wrote:
Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday)
I just put it in my v1.5 Roadster. It seems to be working fine (iPhone app updates, SMS stat command shows the expected values).
I can post 2.3.1 on my firmware update page as soon as you're ready for that.
For anyone who wants the firmware links:
2.3.1 for V1 hardware:
https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V1_production.hex
2.3.1 for V2 hardware:
https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V2_production.hex
Tom
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Yes, that is a new feature - the VDS alerts are relayed as PUSH notifications to the smartphone. Useful to give more information on charge interrupted alerts, as well as other vehicle problems. The alert from SILVERARROW (1174) is new. Do you know what error message the car was saying at the time (it would be a pop-up window on the VDS)? Regards, Mark. On 16 Apr, 2013, at 3:05 PM, 911carrera4 wrote:
mark, this mornig me and karin got two new alerts we didn't use to get with the previous versions of firmware<image.png>
<image.png>
Piotr Von meinem iPhone gesendet
Am 16.04.2013 um 03:09 schrieb Tom Saxton <tom@idleloop.com>:
I can't believe I missed that! Before sending you the diff, I switched my module to km and tested the status message. I verified that the ideal and estimated range changed values and displayed as expected, and that the odometer was shown in km, but didn't catch that it was still showing the value for miles.
I saw Pierre's message just a few minutes ago and did a git pull to look at the code and couldn't see what was wrong. I was thinking it had to be a compiler bug. Then I saw your message that you had just fixed it, and looked back at the history to see what the bug was.
I have the firmware update page ready to update.
Tom
on 4/15/13 5:34 PM, Mark Webb-Johnson wrote:
Tom,
I think the SMS STAT odometer bug is serious enough to require a new build. The good news is that seems to be it, and the fix is simple.
I'll build v1.3.2 tonight and that can be the one to announce and release.
Regards, Mark.
On 16 Apr, 2013, at 12:01 AM, Tom Saxton wrote:
on 4/14/13 11:03 PM, Mark Webb-Johnson wrote:
Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday)
I just put it in my v1.5 Roadster. It seems to be working fine (iPhone app updates, SMS stat command shows the expected values).
I can post 2.3.1 on my firmware update page as soon as you're ready for that.
For anyone who wants the firmware links:
2.3.1 for V1 hardware:
https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V1_production.hex
2.3.1 for V2 hardware:
https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V2_production.hex
Tom
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
no, there was no alert on the SILVERARROW VSD screen. Von meinem iPhone gesendet Am 16.04.2013 um 09:10 schrieb Mark Webb-Johnson <mark@webb-johnson.net>:
Yes, that is a new feature - the VDS alerts are relayed as PUSH notifications to the smartphone. Useful to give more information on charge interrupted alerts, as well as other vehicle problems.
The alert from SILVERARROW (1174) is new. Do you know what error message the car was saying at the time (it would be a pop-up window on the VDS)?
Regards, Mark.
On 16 Apr, 2013, at 3:05 PM, 911carrera4 wrote:
mark, this mornig me and karin got two new alerts we didn't use to get with the previous versions of firmware<image.png>
<image.png>
Piotr Von meinem iPhone gesendet
Am 16.04.2013 um 03:09 schrieb Tom Saxton <tom@idleloop.com>:
I can't believe I missed that! Before sending you the diff, I switched my module to km and tested the status message. I verified that the ideal and estimated range changed values and displayed as expected, and that the odometer was shown in km, but didn't catch that it was still showing the value for miles.
I saw Pierre's message just a few minutes ago and did a git pull to look at the code and couldn't see what was wrong. I was thinking it had to be a compiler bug. Then I saw your message that you had just fixed it, and looked back at the history to see what the bug was.
I have the firmware update page ready to update.
Tom
on 4/15/13 5:34 PM, Mark Webb-Johnson wrote:
Tom,
I think the SMS STAT odometer bug is serious enough to require a new build. The good news is that seems to be it, and the fix is simple.
I'll build v1.3.2 tonight and that can be the one to announce and release.
Regards, Mark.
On 16 Apr, 2013, at 12:01 AM, Tom Saxton wrote:
on 4/14/13 11:03 PM, Mark Webb-Johnson wrote:
Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday)
I just put it in my v1.5 Roadster. It seems to be working fine (iPhone app updates, SMS stat command shows the expected values).
I can post 2.3.1 on my firmware update page as soon as you're ready for that.
For anyone who wants the firmware links:
2.3.1 for V1 hardware:
https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V1_production.hex
2.3.1 for V2 hardware:
https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V2_production.hex
Tom
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
The message occurred at: 2013-04-16 00:56:15.341898 -0400 info main: #22 C SILVERARROW rx msg P ETR2N,1174,16384 (time zone -0400 = 4 hours west of GMT) Alert #1174 is close to the other alerts for driving (such as unsafe gear shift, tow mode not available, etc), but the time seems very early in the morning. +0100 would be just before 6am! Regards, Mark. On 16 Apr, 2013, at 3:26 PM, 911carrera4 wrote:
no, there was no alert on the SILVERARROW VSD screen.
Von meinem iPhone gesendet
Am 16.04.2013 um 09:10 schrieb Mark Webb-Johnson <mark@webb-johnson.net>:
Yes, that is a new feature - the VDS alerts are relayed as PUSH notifications to the smartphone. Useful to give more information on charge interrupted alerts, as well as other vehicle problems.
The alert from SILVERARROW (1174) is new. Do you know what error message the car was saying at the time (it would be a pop-up window on the VDS)?
Regards, Mark.
On 16 Apr, 2013, at 3:05 PM, 911carrera4 wrote:
mark, this mornig me and karin got two new alerts we didn't use to get with the previous versions of firmware<image.png>
<image.png>
Piotr Von meinem iPhone gesendet
Am 16.04.2013 um 03:09 schrieb Tom Saxton <tom@idleloop.com>:
I can't believe I missed that! Before sending you the diff, I switched my module to km and tested the status message. I verified that the ideal and estimated range changed values and displayed as expected, and that the odometer was shown in km, but didn't catch that it was still showing the value for miles.
I saw Pierre's message just a few minutes ago and did a git pull to look at the code and couldn't see what was wrong. I was thinking it had to be a compiler bug. Then I saw your message that you had just fixed it, and looked back at the history to see what the bug was.
I have the firmware update page ready to update.
Tom
on 4/15/13 5:34 PM, Mark Webb-Johnson wrote:
Tom,
I think the SMS STAT odometer bug is serious enough to require a new build. The good news is that seems to be it, and the fix is simple.
I'll build v1.3.2 tonight and that can be the one to announce and release.
Regards, Mark.
On 16 Apr, 2013, at 12:01 AM, Tom Saxton wrote:
on 4/14/13 11:03 PM, Mark Webb-Johnson wrote:
> Seems to be that you and I are the only Tesla Roadsters on tmc server that > are > running v2.3.1 yet (not surprising, as only pre-released yesterday)
I just put it in my v1.5 Roadster. It seems to be working fine (iPhone app updates, SMS stat command shows the expected values).
I can post 2.3.1 on my firmware update page as soon as you're ready for that.
For anyone who wants the firmware links:
2.3.1 for V1 hardware:
https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V1_production.hex
2.3.1 for V2 hardware:
https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V2_production.hex
Tom
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
The alert arrived at about 6:55 am, while I was leaving for office (I've disconnected the power wire with on tesla port - not on the wall plug. Von meinem iPhone gesendet Am 16.04.2013 um 09:58 schrieb Mark Webb-Johnson <mark@webb-johnson.net>:
The message occurred at:
2013-04-16 00:56:15.341898 -0400 info main: #22 C SILVERARROW rx msg P ETR2N,1174,16384 (time zone -0400 = 4 hours west of GMT)
Alert #1174 is close to the other alerts for driving (such as unsafe gear shift, tow mode not available, etc), but the time seems very early in the morning. +0100 would be just before 6am!
Regards, Mark.
On 16 Apr, 2013, at 3:26 PM, 911carrera4 wrote:
no, there was no alert on the SILVERARROW VSD screen.
Von meinem iPhone gesendet
Am 16.04.2013 um 09:10 schrieb Mark Webb-Johnson <mark@webb-johnson.net>:
Yes, that is a new feature - the VDS alerts are relayed as PUSH notifications to the smartphone. Useful to give more information on charge interrupted alerts, as well as other vehicle problems.
The alert from SILVERARROW (1174) is new. Do you know what error message the car was saying at the time (it would be a pop-up window on the VDS)?
Regards, Mark.
On 16 Apr, 2013, at 3:05 PM, 911carrera4 wrote:
mark, this mornig me and karin got two new alerts we didn't use to get with the previous versions of firmware<image.png>
<image.png>
Piotr Von meinem iPhone gesendet
Am 16.04.2013 um 03:09 schrieb Tom Saxton <tom@idleloop.com>:
I can't believe I missed that! Before sending you the diff, I switched my module to km and tested the status message. I verified that the ideal and estimated range changed values and displayed as expected, and that the odometer was shown in km, but didn't catch that it was still showing the value for miles.
I saw Pierre's message just a few minutes ago and did a git pull to look at the code and couldn't see what was wrong. I was thinking it had to be a compiler bug. Then I saw your message that you had just fixed it, and looked back at the history to see what the bug was.
I have the firmware update page ready to update.
Tom
on 4/15/13 5:34 PM, Mark Webb-Johnson wrote:
Tom,
I think the SMS STAT odometer bug is serious enough to require a new build. The good news is that seems to be it, and the fix is simple.
I'll build v1.3.2 tonight and that can be the one to announce and release.
Regards, Mark.
On 16 Apr, 2013, at 12:01 AM, Tom Saxton wrote:
> on 4/14/13 11:03 PM, Mark Webb-Johnson wrote: > >> Seems to be that you and I are the only Tesla Roadsters on tmc server that >> are >> running v2.3.1 yet (not surprising, as only pre-released yesterday) > > I just put it in my v1.5 Roadster. It seems to be working fine (iPhone app > updates, SMS stat command shows the expected values). > > I can post 2.3.1 on my firmware update page as soon as you're ready for > that. > > For anyone who wants the firmware links: > > 2.3.1 for V1 hardware: > > https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ > firmware/V1_production.hex > > 2.3.1 for V2 hardware: > > https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ > firmware/V2_production.hex > > Tom > > > _______________________________________________ > OvmsDev mailing list > OvmsDev@lists.teslaclub.hk > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Mark I've installed the new 2.3.2 firmware. Everything works stable and the ODO Values are more or less okay. Is there one new alert? 882 (00000004) - Before starting, charge port door must be closed. How can I disable the push messages ? Feature 14: VALUE? Piotr Von: ovmsdev-bounces@lists.teslaclub.hk [mailto:ovmsdev-bounces@lists.teslaclub.hk] Im Auftrag von Mark Webb-Johnson Gesendet: Dienstag, 16. April 2013 09:59 An: OVMS Developers Betreff: Re: [Ovmsdev] Release Firmware The message occurred at: 2013-04-16 00:56:15.341898 -0400 info main: #22 C SILVERARROW rx msg P ETR2N,1174,16384 (time zone -0400 = 4 hours west of GMT) Alert #1174 is close to the other alerts for driving (such as unsafe gear shift, tow mode not available, etc), but the time seems very early in the morning. +0100 would be just before 6am! Regards, Mark. On 16 Apr, 2013, at 3:26 PM, 911carrera4 wrote: no, there was no alert on the SILVERARROW VSD screen. Von meinem iPhone gesendet Am 16.04.2013 um 09:10 schrieb Mark Webb-Johnson <mark@webb-johnson.net>: Yes, that is a new feature - the VDS alerts are relayed as PUSH notifications to the smartphone. Useful to give more information on charge interrupted alerts, as well as other vehicle problems. The alert from SILVERARROW (1174) is new. Do you know what error message the car was saying at the time (it would be a pop-up window on the VDS)? Regards, Mark. On 16 Apr, 2013, at 3:05 PM, 911carrera4 wrote: mark, this mornig me and karin got two new alerts we didn't use to get with the previous versions of firmware<image.png> <image.png> Piotr Von meinem iPhone gesendet Am 16.04.2013 um 03:09 schrieb Tom Saxton <tom@idleloop.com>: I can't believe I missed that! Before sending you the diff, I switched my module to km and tested the status message. I verified that the ideal and estimated range changed values and displayed as expected, and that the odometer was shown in km, but didn't catch that it was still showing the value for miles. I saw Pierre's message just a few minutes ago and did a git pull to look at the code and couldn't see what was wrong. I was thinking it had to be a compiler bug. Then I saw your message that you had just fixed it, and looked back at the history to see what the bug was. I have the firmware update page ready to update. Tom on 4/15/13 5:34 PM, Mark Webb-Johnson wrote: Tom, I think the SMS STAT odometer bug is serious enough to require a new build. The good news is that seems to be it, and the fix is simple. I'll build v1.3.2 tonight and that can be the one to announce and release. Regards, Mark. On 16 Apr, 2013, at 12:01 AM, Tom Saxton wrote: on 4/14/13 11:03 PM, Mark Webb-Johnson wrote: Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday) I just put it in my v1.5 Roadster. It seems to be working fine (iPhone app updates, SMS stat command shows the expected values). I can post 2.3.1 on my firmware update page as soon as you're ready for that. For anyone who wants the firmware links: 2.3.1 for V1 hardware: https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V1_production.hex 2.3.1 for V2 hardware: https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V2_production.hex Tom _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
I‘ve installed the new 2.3.2 firmware. Everything works stable and the ODO Values are more or less okay.
Fantastic - thanks for helping to test this.
Is there one new alert? 882 (00000004) - Before starting, charge port door must be closed.
Added to my collection :-)
How can I disable the push messages ? Feature 14: VALUE?
Yes, car bits feature 14, add 8 to the value (bit #3) to suppress vehicle alerts via push notification. Regards, Mark. On 17 Apr, 2013, at 2:28 AM, 911carrera4 wrote:
Mark
I‘ve installed the new 2.3.2 firmware. Everything works stable and the ODO Values are more or less okay. Is there one new alert? 882 (00000004) - Before starting, charge port door must be closed.
How can I disable the push messages ? Feature 14: VALUE?
Piotr
Von: ovmsdev-bounces@lists.teslaclub.hk [mailto:ovmsdev-bounces@lists.teslaclub.hk] Im Auftrag von Mark Webb-Johnson Gesendet: Dienstag, 16. April 2013 09:59 An: OVMS Developers Betreff: Re: [Ovmsdev] Release Firmware
The message occurred at:
2013-04-16 00:56:15.341898 -0400 info main: #22 C SILVERARROW rx msg P ETR2N,1174,16384 (time zone -0400 = 4 hours west of GMT)
Alert #1174 is close to the other alerts for driving (such as unsafe gear shift, tow mode not available, etc), but the time seems very early in the morning. +0100 would be just before 6am!
Regards, Mark.
On 16 Apr, 2013, at 3:26 PM, 911carrera4 wrote:
no, there was no alert on the SILVERARROW VSD screen.
Von meinem iPhone gesendet
Am 16.04.2013 um 09:10 schrieb Mark Webb-Johnson <mark@webb-johnson.net>:
Yes, that is a new feature - the VDS alerts are relayed as PUSH notifications to the smartphone. Useful to give more information on charge interrupted alerts, as well as other vehicle problems.
The alert from SILVERARROW (1174) is new. Do you know what error message the car was saying at the time (it would be a pop-up window on the VDS)?
Regards, Mark.
On 16 Apr, 2013, at 3:05 PM, 911carrera4 wrote:
mark, this mornig me and karin got two new alerts we didn't use to get with the previous versions of firmware<image.png>
<image.png>
Piotr Von meinem iPhone gesendet
Am 16.04.2013 um 03:09 schrieb Tom Saxton <tom@idleloop.com>:
I can't believe I missed that! Before sending you the diff, I switched my module to km and tested the status message. I verified that the ideal and estimated range changed values and displayed as expected, and that the odometer was shown in km, but didn't catch that it was still showing the value for miles.
I saw Pierre's message just a few minutes ago and did a git pull to look at the code and couldn't see what was wrong. I was thinking it had to be a compiler bug. Then I saw your message that you had just fixed it, and looked back at the history to see what the bug was.
I have the firmware update page ready to update.
Tom
on 4/15/13 5:34 PM, Mark Webb-Johnson wrote:
Tom,
I think the SMS STAT odometer bug is serious enough to require a new build. The good news is that seems to be it, and the fix is simple.
I'll build v1.3.2 tonight and that can be the one to announce and release.
Regards, Mark.
On 16 Apr, 2013, at 12:01 AM, Tom Saxton wrote:
on 4/14/13 11:03 PM, Mark Webb-Johnson wrote:
Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday)
I just put it in my v1.5 Roadster. It seems to be working fine (iPhone app updates, SMS stat command shows the expected values).
I can post 2.3.1 on my firmware update page as soon as you're ready for that.
For anyone who wants the firmware links:
2.3.1 for V1 hardware:
https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V1_production.hex
2.3.1 for V2 hardware:
https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V2_production.hex
Tom
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OK, attempt #2. Firmware v2.3.2 is now pushed to github. The SMS bug is fixed. I also added (last minute) a car bits setting to suppress vehicle alerts (for those that don't want them). I still have to update the documentation, but the firmware is there and ready to go. Once Tom has is firmware update page with v2.3.2, I'll announce it. Regards, Mark. P.S. Still not happy with KM/Miles conversion. It seems wrong - I can't get it to agree with the car (Tesla Roadster), but then again I can't get different bits of the Tesla Roadster to agree with themselves either. Anyway, as Michael pointed out it should really be converted at vehicle module level to whatever the owner chooses and not stored as miles. But, that will need changes to the Apps and protocol so will have to wait. On 16 Apr, 2013, at 8:34 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Tom,
I think the SMS STAT odometer bug is serious enough to require a new build. The good news is that seems to be it, and the fix is simple.
I'll build v1.3.2 tonight and that can be the one to announce and release.
Regards, Mark.
On 16 Apr, 2013, at 12:01 AM, Tom Saxton wrote:
on 4/14/13 11:03 PM, Mark Webb-Johnson wrote:
Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday)
I just put it in my v1.5 Roadster. It seems to be working fine (iPhone app updates, SMS stat command shows the expected values).
I can post 2.3.1 on my firmware update page as soon as you're ready for that.
For anyone who wants the firmware links:
2.3.1 for V1 hardware:
https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V1_production.hex
2.3.1 for V2 hardware:
https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/v2.3.1/vehicle/ firmware/V2_production.hex
Tom
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
on 4/16/13 5:32 AM, Mark Webb-Johnson wrote:
Once Tom has his firmware update page with v2.3.2, I'll announce it.
It's up. http://www.idleloop.com/tesla/ovms/ I have a "coming soon" placeholder for the release notes, which I'll update when that's ready. Tom
participants (5)
-
911carrera4 -
Kevin Sharpe ZCW -
Mark Webb-Johnson -
Nikki Gordon-Bloomfield -
Tom Saxton