Jack, Tom, One good thing - when/if you switch from v1 to v2 you don't have to re-do the antenna! The connectors are the same. You will just need the module and the Tesla Roadster cable. The situation with v1 + ACC now is very very tight. It is ok, but at some point it is going to be feature-limited. Regards, Mark. On 29 Aug, 2013, at 1:50 PM, Jack West <jackduncanwest@gmail.com> wrote:
I'm with Tom. Time to upgrade! I look forward to hacking the V1 hardware that will be freed up.
Jack
On Aug 28, 2013, at 9:27 PM, Tom Saxton <tom@idleloop.com> wrote:
I want all the features, ACC and logging, and room to hack in my own stuff. I'm also looking forward to being able to do DIAG mode without totally disassembling the device. Plus, v2 looks cooler. :-)
Tom
On 8/28/13 6:10 PM, "Mark Webb-Johnson" <mark@webb-johnson.net> wrote:
Tom, I sent out a subsequent eMail last night - I managed to shoe-horn ACC into v1 firmware (at the expense of DIAG mode):
The good news is that by doing some juggling around, I've managed to shoe-horn ACC into the V1_Production code for v1 hardware modules. We've got 3,614bytes of flash and 504bytes of RAM free to play with! The sad news is that this is at the expense of DIAG mode. Anyway, if developers really need that, they can build a custom firmware for it anyway, so not too bad. I may be able to bring it back for v1 hardware at a later stage, if we can reduce code-size elsewhere.
That said, the v2 hardware is so much better than v1 :-)
Regards, Mark.
On 29 Aug, 2013, at 5:17 AM, Tom Saxton <tom@idleloop.com> wrote:
Well, I guess that means it's time to order a V2 OVMSŠ
I'm looking forward to all the new features!
Tom
On 8/27/13 7:05 AM, "Mark Webb-Johnson" <mark@webb-johnson.net> wrote:
I've just pushed to github the code for v2.5.2. This includes a workable ACC module, as well as a bunch of bug fixes. It also includes a re-working of the cooldown feature in the Tesla Roadster, based on many a hot evening spent in my car with a CAN USB adaptor and laptop.
For the Tesla Roadster, I managed to find two new id#100 messages related to HVAC - 0x87 and 0x9A. This is now used by the cooldown feature to track HVAC usage and try to make it work better.
HVAC HVAC message 0x87 and 0x9A are enabled with: 102 06 D0 07 00 00 80 00 08 and disabled with: 102 06 10 27 00 10 00 00 00
HVAC#1 B1=0x87 B2=Toutside (outside temperature, celcius) B3=Tmaxbrick (ESS temperature, celcius) B4=Tcoolant (coolant temperature, celcius) B5=Requested cooling % B6=Received cooling % B7= LSB \ Compressor RPM B8= MSB /
HVAC#2 B1=0x9A B2=? B3=? B4=? B5=? B6=? [ seems to be refrigerent pressure (scaled with ~/4) but not certain ] B7=TcabinOutlet (celcius) B8=? [ seems to be outside temperature (celcius) ]
The build configs are restructured, as previously announced.
Currently, I haven't been able to fit either LOGGING or ACC in the V1 module firmware - it is just too big. I'll keep working on this, as it would be good to get at least ACC in that firmware.
One caveat: this is largely untested and probably very buggy - which is why I haven't done binary builds yet. I'll test and debug over the next couple of days and then release binaries when I've got something working well.
Regards, Mark.
_______________________________________________ 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