Re: [Ovmsdev] little problem/feature needed/debug
William,
Is it repeatable?
ie; plug in, stop charge. wait 5 minutes until coolant pump turns off, then try start charge from the app.
Also, are other commands working (like lock/unlock)?
After setting the feature for write-enabled CAN bus, you need to restart the module. If not, none of the commands will work. If at least one of the commands is working, then that is fine.
Regards, Mark.
P.S. Not wishing to hijack this thread, but since you are in the USA - could you test the lock/unlock commands for us on your US car? Supposedly, the US cars don't have an immobiliser so that the UNLOCK command will disable the alarm and allow the car to be driven. Please try and let us know.
On 17 Feb 2012, at 2:35 PM, William Petefish wrote:
Mark,
Yes, I did and to no avail. I had purposefully let the car sit until it went into power save mode and tried again, no joy.
Might it have something to do with the new FW on the roadster? (4.6.4 I think is the FW that is on mine.) My roadster is a 2.5.
William
On Fri, Feb 17, 2012 at 12:29 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: William:
Current (1.2.0-rc3) code is:
void can_tx_setchargecurrent(unsigned char current) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x05; TXB0D1 = 0x02; TXB0D2 = 0x00; TXB0D3 = 0x00; TXB0D4 = current; TXB0D5 = 0x00; TXB0D6 = 0x00; TXB0D7 = 0x00; TXB0DLC = 0b00001000; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done
can_tx_wakeup(); // Also, wakeup the car if necessary }
void can_tx_wakeup(void) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x0a; TXB0DLC = 0b00000001; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done }
That should work. Pre-rc3, I used to see this, but since rc3 it has been ok for me.
Maybe the bus was busy and lost the wakeup message? Did you try sending any other commands, or repeating the start charge command?
What is the version of your car (2.x or 1.5?).
Regards, Mark.
P.S. There is also a specific command C,18 that calls the CAN wakeup function. Not sure if the Android App supports it or not.
On 17 Feb 2012, at 2:22 PM, William Petefish wrote:
Mark,
Feature Needed: Wake Up command.
I tried to send the start charge command from my android phone and it wouldn't start to charge or change charging mode, etc. without being woken up by opening/closing the doors/trunk/remote/etc.
I am using the latest release (1.20) and the Android app.
William
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Mark,
Yes, fully repeatable, reproducible, and verifiable.
When not woken up first, none of the commands work.
I will restart the module and try further.
It will disarm the alarm and allow it to be driven.
William
P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)
On Fri, Feb 17, 2012 at 12:51 AM, Mark Webb-Johnson <mark@webb-johnson.net>wrote:
William,
Is it repeatable?
ie; plug in, stop charge. wait 5 minutes until coolant pump turns off, then try start charge from the app.
Also, are other commands working (like lock/unlock)?
After setting the feature for write-enabled CAN bus, you need to restart the module. If not, none of the commands will work. If at least one of the commands is working, then that is fine.
Regards, Mark.
P.S. Not wishing to hijack this thread, but since you are in the USA - could you test the lock/unlock commands for us on your US car? Supposedly, the US cars don't have an immobiliser so that the UNLOCK command will disable the alarm and allow the car to be driven. Please try and let us know.
On 17 Feb 2012, at 2:35 PM, William Petefish wrote:
Mark,
Yes, I did and to no avail. I had purposefully let the car sit until it went into power save mode and tried again, no joy.
Might it have something to do with the new FW on the roadster? (4.6.4 I think is the FW that is on mine.) My roadster is a 2.5.
William
On Fri, Feb 17, 2012 at 12:29 AM, Mark Webb-Johnson <mark@webb-johnson.net
wrote:
William:
Current (1.2.0-rc3) code is:
void can_tx_setchargecurrent(unsigned char current) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x05; TXB0D1 = 0x02; TXB0D2 = 0x00; TXB0D3 = 0x00; TXB0D4 = current; TXB0D5 = 0x00; TXB0D6 = 0x00; TXB0D7 = 0x00; TXB0DLC = 0b00001000; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done
can_tx_wakeup(); // Also, wakeup the car if necessary }
void can_tx_wakeup(void) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x0a; TXB0DLC = 0b00000001; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done }
That should work. Pre-rc3, I used to see this, but since rc3 it has been ok for me.
Maybe the bus was busy and lost the wakeup message? Did you try sending any other commands, or repeating the start charge command?
What is the version of your car (2.x or 1.5?).
Regards, Mark.
P.S. There is also a specific command C,18 that calls the CAN wakeup function. Not sure if the Android App supports it or not.
On 17 Feb 2012, at 2:22 PM, William Petefish wrote:
Mark,
Feature Needed: Wake Up command.
I tried to send the start charge command from my android phone and it wouldn't start to charge or change charging mode, etc. without being woken up by opening/closing the doors/trunk/remote/etc.
I am using the latest release (1.20) and the Android app.
William
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, fully repeatable, reproducible, and verifiable.
Sonny (if you are listening): Does the Android App have a 'wakeup' command function (C,18)? If so, it would be useful to try that to ensure it works.
It will disarm the alarm and allow it to be driven.
Scary, very scary. The Non-US cars have immobilisers so the command will unlock the doors but the alarm will still go off when you open them and the car can't be driven.
Regards, Mark.
P.S. Thanks for the help testing. Most appreciated, and what we need most at the moment.
On 17 Feb 2012, at 2:59 PM, William Petefish wrote:
Mark,
Yes, fully repeatable, reproducible, and verifiable.
When not woken up first, none of the commands work.
I will restart the module and try further.
It will disarm the alarm and allow it to be driven.
William
P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)
On Fri, Feb 17, 2012 at 12:51 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: William,
Is it repeatable?
ie; plug in, stop charge. wait 5 minutes until coolant pump turns off, then try start charge from the app.
Also, are other commands working (like lock/unlock)?
After setting the feature for write-enabled CAN bus, you need to restart the module. If not, none of the commands will work. If at least one of the commands is working, then that is fine.
Regards, Mark.
P.S. Not wishing to hijack this thread, but since you are in the USA - could you test the lock/unlock commands for us on your US car? Supposedly, the US cars don't have an immobiliser so that the UNLOCK command will disable the alarm and allow the car to be driven. Please try and let us know.
On 17 Feb 2012, at 2:35 PM, William Petefish wrote:
Mark,
Yes, I did and to no avail. I had purposefully let the car sit until it went into power save mode and tried again, no joy.
Might it have something to do with the new FW on the roadster? (4.6.4 I think is the FW that is on mine.) My roadster is a 2.5.
William
On Fri, Feb 17, 2012 at 12:29 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: William:
Current (1.2.0-rc3) code is:
void can_tx_setchargecurrent(unsigned char current) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x05; TXB0D1 = 0x02; TXB0D2 = 0x00; TXB0D3 = 0x00; TXB0D4 = current; TXB0D5 = 0x00; TXB0D6 = 0x00; TXB0D7 = 0x00; TXB0DLC = 0b00001000; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done
can_tx_wakeup(); // Also, wakeup the car if necessary }
void can_tx_wakeup(void) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x0a; TXB0DLC = 0b00000001; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done }
That should work. Pre-rc3, I used to see this, but since rc3 it has been ok for me.
Maybe the bus was busy and lost the wakeup message? Did you try sending any other commands, or repeating the start charge command?
What is the version of your car (2.x or 1.5?).
Regards, Mark.
P.S. There is also a specific command C,18 that calls the CAN wakeup function. Not sure if the Android App supports it or not.
On 17 Feb 2012, at 2:22 PM, William Petefish wrote:
Mark,
Feature Needed: Wake Up command.
I tried to send the start charge command from my android phone and it wouldn't start to charge or change charging mode, etc. without being woken up by opening/closing the doors/trunk/remote/etc.
I am using the latest release (1.20) and the Android app.
William
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
P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)
Is this Android App?
If so, Sonny (again): modes are 0=standard, 1=storage,3=range,4=performance
P.S. What happened to mode 2? Did there used to be a mystery fifth mode?
On 17 Feb 2012, at 2:59 PM, William Petefish wrote:
Mark,
Yes, fully repeatable, reproducible, and verifiable.
When not woken up first, none of the commands work.
I will restart the module and try further.
It will disarm the alarm and allow it to be driven.
William
P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)
On Fri, Feb 17, 2012 at 12:51 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: William,
Is it repeatable?
ie; plug in, stop charge. wait 5 minutes until coolant pump turns off, then try start charge from the app.
Also, are other commands working (like lock/unlock)?
After setting the feature for write-enabled CAN bus, you need to restart the module. If not, none of the commands will work. If at least one of the commands is working, then that is fine.
Regards, Mark.
P.S. Not wishing to hijack this thread, but since you are in the USA - could you test the lock/unlock commands for us on your US car? Supposedly, the US cars don't have an immobiliser so that the UNLOCK command will disable the alarm and allow the car to be driven. Please try and let us know.
On 17 Feb 2012, at 2:35 PM, William Petefish wrote:
Mark,
Yes, I did and to no avail. I had purposefully let the car sit until it went into power save mode and tried again, no joy.
Might it have something to do with the new FW on the roadster? (4.6.4 I think is the FW that is on mine.) My roadster is a 2.5.
William
On Fri, Feb 17, 2012 at 12:29 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: William:
Current (1.2.0-rc3) code is:
void can_tx_setchargecurrent(unsigned char current) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x05; TXB0D1 = 0x02; TXB0D2 = 0x00; TXB0D3 = 0x00; TXB0D4 = current; TXB0D5 = 0x00; TXB0D6 = 0x00; TXB0D7 = 0x00; TXB0DLC = 0b00001000; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done
can_tx_wakeup(); // Also, wakeup the car if necessary }
void can_tx_wakeup(void) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x0a; TXB0DLC = 0b00000001; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done }
That should work. Pre-rc3, I used to see this, but since rc3 it has been ok for me.
Maybe the bus was busy and lost the wakeup message? Did you try sending any other commands, or repeating the start charge command?
What is the version of your car (2.x or 1.5?).
Regards, Mark.
P.S. There is also a specific command C,18 that calls the CAN wakeup function. Not sure if the Android App supports it or not.
On 17 Feb 2012, at 2:22 PM, William Petefish wrote:
Mark,
Feature Needed: Wake Up command.
I tried to send the start charge command from my android phone and it wouldn't start to charge or change charging mode, etc. without being woken up by opening/closing the doors/trunk/remote/etc.
I am using the latest release (1.20) and the Android app.
William
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 can confirm that switching between charge modes does not work 100%. I tried switching to range mode, and then start charging from the app.
The battery indicator in the car changes, i.e. the top of the battery is visible. Range does not change, also charge mode visible on the VDS does not change (still standard charging)
On the (Android) app , it's shows the same. After i stopped the charging, i received a SMS that does not start with Range - or Standard - just "Charging Stopped, ideal range ..etc"
Tonight i'll try to send the commands manually on the CAN bus, to see if i see any difference in behaviour.
Btw, i do receive a "Hello World" push message on my android phone, but not on the Ipad. I'm not using any testflight version anymore, but the one from the appstore.
Btw2, when a charge is stopped, i used to receive a push message + SMS, this somehow does not work anymore for me. I only receive the SMS
Btw3, the car powers up fine, and starts charging, even if left unused (but connected) for over a day.
-Michael
Op 17-2-2012 8:06, Mark Webb-Johnson schreef:
P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)
Is this Android App?
If so, Sonny (again): modes are 0=standard, 1=storage,3=range,4=performance
P.S. What happened to mode 2? Did there used to be a mystery fifth mode?
On 17 Feb 2012, at 2:59 PM, William Petefish wrote:
Mark,
Yes, fully repeatable, reproducible, and verifiable.
When not woken up first, none of the commands work.
I will restart the module and try further.
It will disarm the alarm and allow it to be driven.
William
P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)
On Fri, Feb 17, 2012 at 12:51 AM, Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>> wrote:
William, Is it repeatable? ie; plug in, stop charge. wait 5 minutes until coolant pump turns off, then try start charge from the app. Also, are other commands working (like lock/unlock)? After setting the feature for write-enabled CAN bus, you need to restart the module. If not, none of the commands will work. If at least one of the commands is working, then that is fine. Regards, Mark. P.S. Not wishing to hijack this thread, but since you are in the USA - could you test the lock/unlock commands for us on your US car? Supposedly, the US cars don't have an immobiliser so that the UNLOCK command will disable the alarm and allow the car to be driven. Please try and let us know. On 17 Feb 2012, at 2:35 PM, William Petefish wrote:Mark, Yes, I did and to no avail. I had purposefully let the car sit until it went into power save mode and tried again, no joy. Might it have something to do with the new FW on the roadster? (4.6.4 I think is the FW that is on mine.) My roadster is a 2.5. William On Fri, Feb 17, 2012 at 12:29 AM, Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>> wrote: William: Current (1.2.0-rc3) code is: void can_tx_setchargecurrent(unsigned char current) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x05; TXB0D1 = 0x02; TXB0D2 = 0x00; TXB0D3 = 0x00; TXB0D4 = current; TXB0D5 = 0x00; TXB0D6 = 0x00; TXB0D7 = 0x00; TXB0DLC = 0b00001000; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done can_tx_wakeup(); // Also, wakeup the car if necessary } void can_tx_wakeup(void) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x0a; TXB0DLC = 0b00000001; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done } That should work. Pre-rc3, I used to see this, but since rc3 it has been ok for me. Maybe the bus was busy and lost the wakeup message? Did you try sending any other commands, or repeating the start charge command? What is the version of your car (2.x or 1.5?). Regards, Mark. P.S. There is also a specific command C,18 that calls the CAN wakeup function. Not sure if the Android App supports it or not. On 17 Feb 2012, at 2:22 PM, William Petefish wrote:Mark, Feature Needed: Wake Up command. I tried to send the start charge command from my android phone and it wouldn't start to charge or change charging mode, etc. without being woken up by opening/closing the doors/trunk/remote/etc. I am using the latest release (1.20) and the Android app. William_______________________________________________ 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 http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
-- Stegen Electronics Kwartslaan 95 3162 RD Rhoon The Netherlands
Tel: +31 10-5016960 www.stegen.com
Michael,
I tried issuing the commands manually on the can bus and can switch modes shown on the VDS.
N.B. There is a bug in the Android App on the marketplace - it gets the mode numbers wrong (I guess 0..3 not 0,1,3,4).
I'm implementing this in the iPhone App tonight, so should be able to test later.
Regards, Mark.
On 17 Feb, 2012, at 9:11 PM, Michael Stegen wrote:
I can confirm that switching between charge modes does not work 100%. I tried switching to range mode, and then start charging from the app.
The battery indicator in the car changes, i.e. the top of the battery is visible. Range does not change, also charge mode visible on the VDS does not change (still standard charging)
On the (Android) app , it's shows the same. After i stopped the charging, i received a SMS that does not start with Range - or Standard - just "Charging Stopped, ideal range ..etc"
Tonight i'll try to send the commands manually on the CAN bus, to see if i see any difference in behaviour.
Btw, i do receive a "Hello World" push message on my android phone, but not on the Ipad. I'm not using any testflight version anymore, but the one from the appstore.
Btw2, when a charge is stopped, i used to receive a push message + SMS, this somehow does not work anymore for me. I only receive the SMS
Btw3, the car powers up fine, and starts charging, even if left unused (but connected) for over a day.
-Michael
Op 17-2-2012 8:06, Mark Webb-Johnson schreef:
P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)
Is this Android App?
If so, Sonny (again): modes are 0=standard, 1=storage,3=range,4=performance
P.S. What happened to mode 2? Did there used to be a mystery fifth mode?
On 17 Feb 2012, at 2:59 PM, William Petefish wrote:
Mark,
Yes, fully repeatable, reproducible, and verifiable.
When not woken up first, none of the commands work.
I will restart the module and try further.
It will disarm the alarm and allow it to be driven.
William
P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)
On Fri, Feb 17, 2012 at 12:51 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: William,
Is it repeatable?
ie; plug in, stop charge. wait 5 minutes until coolant pump turns off, then try start charge from the app.
Also, are other commands working (like lock/unlock)?
After setting the feature for write-enabled CAN bus, you need to restart the module. If not, none of the commands will work. If at least one of the commands is working, then that is fine.
Regards, Mark.
P.S. Not wishing to hijack this thread, but since you are in the USA - could you test the lock/unlock commands for us on your US car? Supposedly, the US cars don't have an immobiliser so that the UNLOCK command will disable the alarm and allow the car to be driven. Please try and let us know.
On 17 Feb 2012, at 2:35 PM, William Petefish wrote:
Mark,
Yes, I did and to no avail. I had purposefully let the car sit until it went into power save mode and tried again, no joy.
Might it have something to do with the new FW on the roadster? (4.6.4 I think is the FW that is on mine.) My roadster is a 2.5.
William
On Fri, Feb 17, 2012 at 12:29 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: William:
Current (1.2.0-rc3) code is:
void can_tx_setchargecurrent(unsigned char current) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x05; TXB0D1 = 0x02; TXB0D2 = 0x00; TXB0D3 = 0x00; TXB0D4 = current; TXB0D5 = 0x00; TXB0D6 = 0x00; TXB0D7 = 0x00; TXB0DLC = 0b00001000; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done
can_tx_wakeup(); // Also, wakeup the car if necessary }
void can_tx_wakeup(void) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x0a; TXB0DLC = 0b00000001; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done }
That should work. Pre-rc3, I used to see this, but since rc3 it has been ok for me.
Maybe the bus was busy and lost the wakeup message? Did you try sending any other commands, or repeating the start charge command?
What is the version of your car (2.x or 1.5?).
Regards, Mark.
P.S. There is also a specific command C,18 that calls the CAN wakeup function. Not sure if the Android App supports it or not.
On 17 Feb 2012, at 2:22 PM, William Petefish wrote:
Mark,
Feature Needed: Wake Up command.
I tried to send the start charge command from my android phone and it wouldn't start to charge or change charging mode, etc. without being woken up by opening/closing the doors/trunk/remote/etc.
I am using the latest release (1.20) and the Android app.
William
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
-- Stegen Electronics Kwartslaan 95 3162 RD Rhoon The Netherlands
Tel: +31 10-5016960 www.stegen.com
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
P.S. Some ideas of where we are going (not perfect, but getting there):
http://www.youtube.com/watch?v=v1oGXYngI3c http://www.youtube.com/watch?v=-SL_ZTxv1B0& [note the small bug in the stop and start charge - I need to fix in the car firmware (this weekend)] [but, I think you get the idea]
I did a usability test on my 5 year old daughter. Telling her to stop the charge she tried tapping the plug (without success) then slid it to the left and successfully stopped the charge. She had no training, but has done it on the car a few times.
I should have the last of these done this weekend.
Regards, Mark.
On 17 Feb, 2012, at 9:35 PM, Mark Webb-Johnson wrote:
Michael,
I tried issuing the commands manually on the can bus and can switch modes shown on the VDS.
N.B. There is a bug in the Android App on the marketplace - it gets the mode numbers wrong (I guess 0..3 not 0,1,3,4).
I'm implementing this in the iPhone App tonight, so should be able to test later.
Regards, Mark.
On 17 Feb, 2012, at 9:11 PM, Michael Stegen wrote:
I can confirm that switching between charge modes does not work 100%. I tried switching to range mode, and then start charging from the app.
The battery indicator in the car changes, i.e. the top of the battery is visible. Range does not change, also charge mode visible on the VDS does not change (still standard charging)
On the (Android) app , it's shows the same. After i stopped the charging, i received a SMS that does not start with Range - or Standard - just "Charging Stopped, ideal range ..etc"
Tonight i'll try to send the commands manually on the CAN bus, to see if i see any difference in behaviour.
Btw, i do receive a "Hello World" push message on my android phone, but not on the Ipad. I'm not using any testflight version anymore, but the one from the appstore.
Btw2, when a charge is stopped, i used to receive a push message + SMS, this somehow does not work anymore for me. I only receive the SMS
Btw3, the car powers up fine, and starts charging, even if left unused (but connected) for over a day.
-Michael
Op 17-2-2012 8:06, Mark Webb-Johnson schreef:
P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)
Is this Android App?
If so, Sonny (again): modes are 0=standard, 1=storage,3=range,4=performance
P.S. What happened to mode 2? Did there used to be a mystery fifth mode?
On 17 Feb 2012, at 2:59 PM, William Petefish wrote:
Mark,
Yes, fully repeatable, reproducible, and verifiable.
When not woken up first, none of the commands work.
I will restart the module and try further.
It will disarm the alarm and allow it to be driven.
William
P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)
On Fri, Feb 17, 2012 at 12:51 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: William,
Is it repeatable?
ie; plug in, stop charge. wait 5 minutes until coolant pump turns off, then try start charge from the app.
Also, are other commands working (like lock/unlock)?
After setting the feature for write-enabled CAN bus, you need to restart the module. If not, none of the commands will work. If at least one of the commands is working, then that is fine.
Regards, Mark.
P.S. Not wishing to hijack this thread, but since you are in the USA - could you test the lock/unlock commands for us on your US car? Supposedly, the US cars don't have an immobiliser so that the UNLOCK command will disable the alarm and allow the car to be driven. Please try and let us know.
On 17 Feb 2012, at 2:35 PM, William Petefish wrote:
Mark,
Yes, I did and to no avail. I had purposefully let the car sit until it went into power save mode and tried again, no joy.
Might it have something to do with the new FW on the roadster? (4.6.4 I think is the FW that is on mine.) My roadster is a 2.5.
William
On Fri, Feb 17, 2012 at 12:29 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: William:
Current (1.2.0-rc3) code is:
void can_tx_setchargecurrent(unsigned char current) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x05; TXB0D1 = 0x02; TXB0D2 = 0x00; TXB0D3 = 0x00; TXB0D4 = current; TXB0D5 = 0x00; TXB0D6 = 0x00; TXB0D7 = 0x00; TXB0DLC = 0b00001000; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done
can_tx_wakeup(); // Also, wakeup the car if necessary }
void can_tx_wakeup(void) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x0a; TXB0DLC = 0b00000001; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done }
That should work. Pre-rc3, I used to see this, but since rc3 it has been ok for me.
Maybe the bus was busy and lost the wakeup message? Did you try sending any other commands, or repeating the start charge command?
What is the version of your car (2.x or 1.5?).
Regards, Mark.
P.S. There is also a specific command C,18 that calls the CAN wakeup function. Not sure if the Android App supports it or not.
On 17 Feb 2012, at 2:22 PM, William Petefish wrote:
Mark,
Feature Needed: Wake Up command.
I tried to send the start charge command from my android phone and it wouldn't start to charge or change charging mode, etc. without being woken up by opening/closing the doors/trunk/remote/etc.
I am using the latest release (1.20) and the Android app.
William
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
-- Stegen Electronics Kwartslaan 95 3162 RD Rhoon The Netherlands
Tel: +31 10-5016960 www.stegen.com
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
Michael,
I just tried from the iPhone App I'm working on, and all seems ok.
Car was not charging, standard mode with limit 13A on a 70A HPC. I sent a charge mode command to RANGE mode, and car switched to range mode, started charging at 13A and reported charging,range. I sent a charge mode command to STANDARD mode, and car switched to standard mode, while charge continued at 13A and reported as charging,standard. I sent a charge limit command to 32A, then car sent back limit 32A and within a few seconds increased the current at the car to 32amp. I sent a charge limit command to 70A, then car sent back limit 70amp and within a few seconds increased the current at the car to 70amp.
Sonny says he has fixed the Android App charge mode and the version in the market should be ok now. Can you try that?
If the new version has not yet been released, perhaps selecting performance mode will enter range mode (assuming 3=2 and 4=3)?
Regards, Mark.
On 17 Feb, 2012, at 9:35 PM, Mark Webb-Johnson wrote:
Michael,
I tried issuing the commands manually on the can bus and can switch modes shown on the VDS.
N.B. There is a bug in the Android App on the marketplace - it gets the mode numbers wrong (I guess 0..3 not 0,1,3,4).
I'm implementing this in the iPhone App tonight, so should be able to test later.
Regards, Mark.
On 17 Feb, 2012, at 9:11 PM, Michael Stegen wrote:
I can confirm that switching between charge modes does not work 100%. I tried switching to range mode, and then start charging from the app.
The battery indicator in the car changes, i.e. the top of the battery is visible. Range does not change, also charge mode visible on the VDS does not change (still standard charging)
On the (Android) app , it's shows the same. After i stopped the charging, i received a SMS that does not start with Range - or Standard - just "Charging Stopped, ideal range ..etc"
Tonight i'll try to send the commands manually on the CAN bus, to see if i see any difference in behaviour.
Btw, i do receive a "Hello World" push message on my android phone, but not on the Ipad. I'm not using any testflight version anymore, but the one from the appstore.
Btw2, when a charge is stopped, i used to receive a push message + SMS, this somehow does not work anymore for me. I only receive the SMS
Btw3, the car powers up fine, and starts charging, even if left unused (but connected) for over a day.
-Michael
Op 17-2-2012 8:06, Mark Webb-Johnson schreef:
P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)
Is this Android App?
If so, Sonny (again): modes are 0=standard, 1=storage,3=range,4=performance
P.S. What happened to mode 2? Did there used to be a mystery fifth mode?
On 17 Feb 2012, at 2:59 PM, William Petefish wrote:
Mark,
Yes, fully repeatable, reproducible, and verifiable.
When not woken up first, none of the commands work.
I will restart the module and try further.
It will disarm the alarm and allow it to be driven.
William
P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)
On Fri, Feb 17, 2012 at 12:51 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: William,
Is it repeatable?
ie; plug in, stop charge. wait 5 minutes until coolant pump turns off, then try start charge from the app.
Also, are other commands working (like lock/unlock)?
After setting the feature for write-enabled CAN bus, you need to restart the module. If not, none of the commands will work. If at least one of the commands is working, then that is fine.
Regards, Mark.
P.S. Not wishing to hijack this thread, but since you are in the USA - could you test the lock/unlock commands for us on your US car? Supposedly, the US cars don't have an immobiliser so that the UNLOCK command will disable the alarm and allow the car to be driven. Please try and let us know.
On 17 Feb 2012, at 2:35 PM, William Petefish wrote:
Mark,
Yes, I did and to no avail. I had purposefully let the car sit until it went into power save mode and tried again, no joy.
Might it have something to do with the new FW on the roadster? (4.6.4 I think is the FW that is on mine.) My roadster is a 2.5.
William
On Fri, Feb 17, 2012 at 12:29 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: William:
Current (1.2.0-rc3) code is:
void can_tx_setchargecurrent(unsigned char current) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x05; TXB0D1 = 0x02; TXB0D2 = 0x00; TXB0D3 = 0x00; TXB0D4 = current; TXB0D5 = 0x00; TXB0D6 = 0x00; TXB0D7 = 0x00; TXB0DLC = 0b00001000; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done
can_tx_wakeup(); // Also, wakeup the car if necessary }
void can_tx_wakeup(void) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x0a; TXB0DLC = 0b00000001; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done }
That should work. Pre-rc3, I used to see this, but since rc3 it has been ok for me.
Maybe the bus was busy and lost the wakeup message? Did you try sending any other commands, or repeating the start charge command?
What is the version of your car (2.x or 1.5?).
Regards, Mark.
P.S. There is also a specific command C,18 that calls the CAN wakeup function. Not sure if the Android App supports it or not.
On 17 Feb 2012, at 2:22 PM, William Petefish wrote:
Mark,
Feature Needed: Wake Up command.
I tried to send the start charge command from my android phone and it wouldn't start to charge or change charging mode, etc. without being woken up by opening/closing the doors/trunk/remote/etc.
I am using the latest release (1.20) and the Android app.
William
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
-- Stegen Electronics Kwartslaan 95 3162 RD Rhoon The Netherlands
Tel: +31 10-5016960 www.stegen.com
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Mark,
Will Do. Waiting on it now. I'll run a test after I get out of my first class.
William
On Fri, Feb 17, 2012 at 8:25 AM, Mark Webb-Johnson <mark@webb-johnson.net>wrote:
Michael,
I just tried from the iPhone App I'm working on, and all seems ok.
- Car was not charging, standard mode with limit 13A on a 70A HPC.
- I sent a charge mode command to RANGE mode, and car switched to range mode, started charging at 13A and reported charging,range.
- I sent a charge mode command to STANDARD mode, and car switched to standard mode, while charge continued at 13A and reported as charging,standard.
- I sent a charge limit command to 32A, then car sent back limit 32A and within a few seconds increased the current at the car to 32amp.
- I sent a charge limit command to 70A, then car sent back limit 70amp and within a few seconds increased the current at the car to 70amp.
Sonny says he has fixed the Android App charge mode and the version in the market should be ok now. Can you try that?
If the new version has not yet been released, perhaps selecting performance mode will enter range mode (assuming 3=2 and 4=3)?
Regards, Mark.
On 17 Feb, 2012, at 9:35 PM, Mark Webb-Johnson wrote:
Michael,
I tried issuing the commands manually on the can bus and can switch modes shown on the VDS.
N.B. There is a bug in the Android App on the marketplace - it gets the mode numbers wrong (I guess 0..3 not 0,1,3,4).
I'm implementing this in the iPhone App tonight, so should be able to test later.
Regards, Mark.
On 17 Feb, 2012, at 9:11 PM, Michael Stegen wrote:
I can confirm that switching between charge modes does not work 100%. I tried switching to range mode, and then start charging from the app.
The battery indicator in the car changes, i.e. the top of the battery is visible. Range does not change, also charge mode visible on the VDS does not change (still standard charging)
On the (Android) app , it's shows the same. After i stopped the charging, i received a SMS that does not start with Range - or Standard - just "Charging Stopped, ideal range ..etc"
Tonight i'll try to send the commands manually on the CAN bus, to see if i see any difference in behaviour.
Btw, i do receive a "Hello World" push message on my android phone, but not on the Ipad. I'm not using any testflight version anymore, but the one from the appstore.
Btw2, when a charge is stopped, i used to receive a push message + SMS, this somehow does not work anymore for me. I only receive the SMS
Btw3, the car powers up fine, and starts charging, even if left unused (but connected) for over a day.
-Michael
Op 17-2-2012 8:06, Mark Webb-Johnson schreef:
P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)
Is this Android App?
If so, Sonny (again): modes are 0=standard, 1=storage,3=range,4=performance
P.S. What happened to mode 2? Did there used to be a mystery fifth mode?
On 17 Feb 2012, at 2:59 PM, William Petefish wrote:
Mark,
Yes, fully repeatable, reproducible, and verifiable.
When not woken up first, none of the commands work.
I will restart the module and try further.
It will disarm the alarm and allow it to be driven.
William
P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)
On Fri, Feb 17, 2012 at 12:51 AM, Mark Webb-Johnson <mark@webb-johnson.net
wrote:
William,
Is it repeatable?
ie; plug in, stop charge. wait 5 minutes until coolant pump turns off, then try start charge from the app.
Also, are other commands working (like lock/unlock)?
After setting the feature for write-enabled CAN bus, you need to restart the module. If not, none of the commands will work. If at least one of the commands is working, then that is fine.
Regards, Mark.
P.S. Not wishing to hijack this thread, but since you are in the USA - could you test the lock/unlock commands for us on your US car? Supposedly, the US cars don't have an immobiliser so that the UNLOCK command will disable the alarm and allow the car to be driven. Please try and let us know.
On 17 Feb 2012, at 2:35 PM, William Petefish wrote:
Mark,
Yes, I did and to no avail. I had purposefully let the car sit until it went into power save mode and tried again, no joy.
Might it have something to do with the new FW on the roadster? (4.6.4 I think is the FW that is on mine.) My roadster is a 2.5.
William
On Fri, Feb 17, 2012 at 12:29 AM, Mark Webb-Johnson < mark@webb-johnson.net> wrote:
William:
Current (1.2.0-rc3) code is:
void can_tx_setchargecurrent(unsigned char current) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x05; TXB0D1 = 0x02; TXB0D2 = 0x00; TXB0D3 = 0x00; TXB0D4 = current; TXB0D5 = 0x00; TXB0D6 = 0x00; TXB0D7 = 0x00; TXB0DLC = 0b00001000; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done
can_tx_wakeup(); // Also, wakeup the car if necessary }
void can_tx_wakeup(void) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x0a; TXB0DLC = 0b00000001; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done }
That should work. Pre-rc3, I used to see this, but since rc3 it has been ok for me.
Maybe the bus was busy and lost the wakeup message? Did you try sending any other commands, or repeating the start charge command?
What is the version of your car (2.x or 1.5?).
Regards, Mark.
P.S. There is also a specific command C,18 that calls the CAN wakeup function. Not sure if the Android App supports it or not.
On 17 Feb 2012, at 2:22 PM, William Petefish wrote:
Mark,
Feature Needed: Wake Up command.
I tried to send the start charge command from my android phone and it wouldn't start to charge or change charging mode, etc. without being woken up by opening/closing the doors/trunk/remote/etc.
I am using the latest release (1.20) and the Android app.
William
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 listOvmsDev@lists.teslaclub.hkhttp://lists.teslaclub.hk/mailman/listinfo/ovmsdev
-- Stegen Electronics Kwartslaan 95 3162 RD Rhoon The Netherlands
Tel: +31 10-5016960www.stegen.com
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
Problem confirmed still. Module doesn't seem to be responding even after the reboot request.
Another popped up, pin entry in app limited to 2 characters.
William On Feb 17, 2012 8:34 AM, "William Petefish" <william.petefish@gmail.com> wrote:
Mark,
Will Do. Waiting on it now. I'll run a test after I get out of my first class.
William
On Fri, Feb 17, 2012 at 8:25 AM, Mark Webb-Johnson <mark@webb-johnson.net>wrote:
Michael,
I just tried from the iPhone App I'm working on, and all seems ok.
- Car was not charging, standard mode with limit 13A on a 70A HPC.
- I sent a charge mode command to RANGE mode, and car switched to range mode, started charging at 13A and reported charging,range.
- I sent a charge mode command to STANDARD mode, and car switched to standard mode, while charge continued at 13A and reported as charging,standard.
- I sent a charge limit command to 32A, then car sent back limit 32A and within a few seconds increased the current at the car to 32amp.
- I sent a charge limit command to 70A, then car sent back limit 70amp and within a few seconds increased the current at the car to 70amp.
Sonny says he has fixed the Android App charge mode and the version in the market should be ok now. Can you try that?
If the new version has not yet been released, perhaps selecting performance mode will enter range mode (assuming 3=2 and 4=3)?
Regards, Mark.
On 17 Feb, 2012, at 9:35 PM, Mark Webb-Johnson wrote:
Michael,
I tried issuing the commands manually on the can bus and can switch modes shown on the VDS.
N.B. There is a bug in the Android App on the marketplace - it gets the mode numbers wrong (I guess 0..3 not 0,1,3,4).
I'm implementing this in the iPhone App tonight, so should be able to test later.
Regards, Mark.
On 17 Feb, 2012, at 9:11 PM, Michael Stegen wrote:
I can confirm that switching between charge modes does not work 100%. I tried switching to range mode, and then start charging from the app.
The battery indicator in the car changes, i.e. the top of the battery is visible. Range does not change, also charge mode visible on the VDS does not change (still standard charging)
On the (Android) app , it's shows the same. After i stopped the charging, i received a SMS that does not start with Range - or Standard - just "Charging Stopped, ideal range ..etc"
Tonight i'll try to send the commands manually on the CAN bus, to see if i see any difference in behaviour.
Btw, i do receive a "Hello World" push message on my android phone, but not on the Ipad. I'm not using any testflight version anymore, but the one from the appstore.
Btw2, when a charge is stopped, i used to receive a push message + SMS, this somehow does not work anymore for me. I only receive the SMS
Btw3, the car powers up fine, and starts charging, even if left unused (but connected) for over a day.
-Michael
Op 17-2-2012 8:06, Mark Webb-Johnson schreef:
P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)
Is this Android App?
If so, Sonny (again): modes are 0=standard, 1=storage,3=range,4=performance
P.S. What happened to mode 2? Did there used to be a mystery fifth mode?
On 17 Feb 2012, at 2:59 PM, William Petefish wrote:
Mark,
Yes, fully repeatable, reproducible, and verifiable.
When not woken up first, none of the commands work.
I will restart the module and try further.
It will disarm the alarm and allow it to be driven.
William
P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)
On Fri, Feb 17, 2012 at 12:51 AM, Mark Webb-Johnson < mark@webb-johnson.net> wrote:
William,
Is it repeatable?
ie; plug in, stop charge. wait 5 minutes until coolant pump turns off, then try start charge from the app.
Also, are other commands working (like lock/unlock)?
After setting the feature for write-enabled CAN bus, you need to restart the module. If not, none of the commands will work. If at least one of the commands is working, then that is fine.
Regards, Mark.
P.S. Not wishing to hijack this thread, but since you are in the USA - could you test the lock/unlock commands for us on your US car? Supposedly, the US cars don't have an immobiliser so that the UNLOCK command will disable the alarm and allow the car to be driven. Please try and let us know.
On 17 Feb 2012, at 2:35 PM, William Petefish wrote:
Mark,
Yes, I did and to no avail. I had purposefully let the car sit until it went into power save mode and tried again, no joy.
Might it have something to do with the new FW on the roadster? (4.6.4 I think is the FW that is on mine.) My roadster is a 2.5.
William
On Fri, Feb 17, 2012 at 12:29 AM, Mark Webb-Johnson < mark@webb-johnson.net> wrote:
William:
Current (1.2.0-rc3) code is:
void can_tx_setchargecurrent(unsigned char current) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x05; TXB0D1 = 0x02; TXB0D2 = 0x00; TXB0D3 = 0x00; TXB0D4 = current; TXB0D5 = 0x00; TXB0D6 = 0x00; TXB0D7 = 0x00; TXB0DLC = 0b00001000; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done
can_tx_wakeup(); // Also, wakeup the car if necessary }
void can_tx_wakeup(void) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x0a; TXB0DLC = 0b00000001; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done }
That should work. Pre-rc3, I used to see this, but since rc3 it has been ok for me.
Maybe the bus was busy and lost the wakeup message? Did you try sending any other commands, or repeating the start charge command?
What is the version of your car (2.x or 1.5?).
Regards, Mark.
P.S. There is also a specific command C,18 that calls the CAN wakeup function. Not sure if the Android App supports it or not.
On 17 Feb 2012, at 2:22 PM, William Petefish wrote:
Mark,
Feature Needed: Wake Up command.
I tried to send the start charge command from my android phone and it wouldn't start to charge or change charging mode, etc. without being woken up by opening/closing the doors/trunk/remote/etc.
I am using the latest release (1.20) and the Android app.
William
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 listOvmsDev@lists.teslaclub.hkhttp://lists.teslaclub.hk/mailman/listinfo/ovmsdev
-- Stegen Electronics Kwartslaan 95 3162 RD Rhoon The Netherlands
Tel: +31 10-5016960www.stegen.com
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
Hard reset performed. Module working again.
Pin entry still limited to 2 characters.
William On Feb 17, 2012 10:05 AM, "William Petefish" <william.petefish@gmail.com> wrote:
Problem confirmed still. Module doesn't seem to be responding even after the reboot request.
Another popped up, pin entry in app limited to 2 characters.
William On Feb 17, 2012 8:34 AM, "William Petefish" <william.petefish@gmail.com> wrote:
Mark,
Will Do. Waiting on it now. I'll run a test after I get out of my first class.
William
On Fri, Feb 17, 2012 at 8:25 AM, Mark Webb-Johnson <mark@webb-johnson.net
wrote:
Michael,
I just tried from the iPhone App I'm working on, and all seems ok.
- Car was not charging, standard mode with limit 13A on a 70A HPC.
- I sent a charge mode command to RANGE mode, and car switched to range mode, started charging at 13A and reported charging,range.
- I sent a charge mode command to STANDARD mode, and car switched to standard mode, while charge continued at 13A and reported as charging,standard.
- I sent a charge limit command to 32A, then car sent back limit 32A and within a few seconds increased the current at the car to 32amp.
- I sent a charge limit command to 70A, then car sent back limit 70amp and within a few seconds increased the current at the car to 70amp.
Sonny says he has fixed the Android App charge mode and the version in the market should be ok now. Can you try that?
If the new version has not yet been released, perhaps selecting performance mode will enter range mode (assuming 3=2 and 4=3)?
Regards, Mark.
On 17 Feb, 2012, at 9:35 PM, Mark Webb-Johnson wrote:
Michael,
I tried issuing the commands manually on the can bus and can switch modes shown on the VDS.
N.B. There is a bug in the Android App on the marketplace - it gets the mode numbers wrong (I guess 0..3 not 0,1,3,4).
I'm implementing this in the iPhone App tonight, so should be able to test later.
Regards, Mark.
On 17 Feb, 2012, at 9:11 PM, Michael Stegen wrote:
I can confirm that switching between charge modes does not work 100%. I tried switching to range mode, and then start charging from the app.
The battery indicator in the car changes, i.e. the top of the battery is visible. Range does not change, also charge mode visible on the VDS does not change (still standard charging)
On the (Android) app , it's shows the same. After i stopped the charging, i received a SMS that does not start with Range - or Standard - just "Charging Stopped, ideal range ..etc"
Tonight i'll try to send the commands manually on the CAN bus, to see if i see any difference in behaviour.
Btw, i do receive a "Hello World" push message on my android phone, but not on the Ipad. I'm not using any testflight version anymore, but the one from the appstore.
Btw2, when a charge is stopped, i used to receive a push message + SMS, this somehow does not work anymore for me. I only receive the SMS
Btw3, the car powers up fine, and starts charging, even if left unused (but connected) for over a day.
-Michael
Op 17-2-2012 8:06, Mark Webb-Johnson schreef:
P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)
Is this Android App?
If so, Sonny (again): modes are 0=standard, 1=storage,3=range,4=performance
P.S. What happened to mode 2? Did there used to be a mystery fifth mode?
On 17 Feb 2012, at 2:59 PM, William Petefish wrote:
Mark,
Yes, fully repeatable, reproducible, and verifiable.
When not woken up first, none of the commands work.
I will restart the module and try further.
It will disarm the alarm and allow it to be driven.
William
P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)
On Fri, Feb 17, 2012 at 12:51 AM, Mark Webb-Johnson < mark@webb-johnson.net> wrote:
William,
Is it repeatable?
ie; plug in, stop charge. wait 5 minutes until coolant pump turns off, then try start charge from the app.
Also, are other commands working (like lock/unlock)?
After setting the feature for write-enabled CAN bus, you need to restart the module. If not, none of the commands will work. If at least one of the commands is working, then that is fine.
Regards, Mark.
P.S. Not wishing to hijack this thread, but since you are in the USA
could you test the lock/unlock commands for us on your US car? Supposedly, the US cars don't have an immobiliser so that the UNLOCK command will disable the alarm and allow the car to be driven. Please try and let us know.
On 17 Feb 2012, at 2:35 PM, William Petefish wrote:
Mark,
Yes, I did and to no avail. I had purposefully let the car sit until it went into power save mode and tried again, no joy.
Might it have something to do with the new FW on the roadster? (4.6.4 I think is the FW that is on mine.) My roadster is a 2.5.
William
On Fri, Feb 17, 2012 at 12:29 AM, Mark Webb-Johnson < mark@webb-johnson.net> wrote:
William:
Current (1.2.0-rc3) code is:
void can_tx_setchargecurrent(unsigned char current) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x05; TXB0D1 = 0x02; TXB0D2 = 0x00; TXB0D3 = 0x00; TXB0D4 = current; TXB0D5 = 0x00; TXB0D6 = 0x00; TXB0D7 = 0x00; TXB0DLC = 0b00001000; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done
can_tx_wakeup(); // Also, wakeup the car if necessary }
void can_tx_wakeup(void) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x0a; TXB0DLC = 0b00000001; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done }
That should work. Pre-rc3, I used to see this, but since rc3 it has been ok for me.
Maybe the bus was busy and lost the wakeup message? Did you try sending any other commands, or repeating the start charge command?
What is the version of your car (2.x or 1.5?).
Regards, Mark.
P.S. There is also a specific command C,18 that calls the CAN wakeup function. Not sure if the Android App supports it or not.
On 17 Feb 2012, at 2:22 PM, William Petefish wrote:
Mark,
Feature Needed: Wake Up command.
I tried to send the start charge command from my android phone and it wouldn't start to charge or change charging mode, etc. without being woken up by opening/closing the doors/trunk/remote/etc.
I am using the latest release (1.20) and the Android app.
William
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 listOvmsDev@lists.teslaclub.hkhttp://lists.teslaclub.hk/mailman/listinfo/ovmsdev
-- Stegen Electronics Kwartslaan 95 3162 RD Rhoon The Netherlands
Tel: +31 10-5016960www.stegen.com
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
Sonny, Mark, others,
Thanks, the new update fixed the charge mode issues.
Some bugs:
I'm seeing the same two digit PIN limit now.
Also, setting the Charge current, causes a forced close of the app.
(might be related to the beta ICS version i have on my phone right now)
The app also shows SMS/Paranoid Mode Password. Aren't those two different params? The app shows the SMS password "OVMS"
Somehow the notification mode setting is displayed as SMS only, instead of "SMS, IP" I changed it in the app, rebooted the module, but it doesn't stick. (at first i tought it did, but now it's back to "SMS" only)
Regards, Michael
Op 17-2-2012 17:16, William Petefish schreef:
Hard reset performed. Module working again.
Pin entry still limited to 2 characters.
William
On Feb 17, 2012 10:05 AM, "William Petefish" <william.petefish@gmail.com <mailto:william.petefish@gmail.com>> wrote:
Problem confirmed still. Module doesn't seem to be responding even after the reboot request. Another popped up, pin entry in app limited to 2 characters. William On Feb 17, 2012 8:34 AM, "William Petefish" <william.petefish@gmail.com <mailto:william.petefish@gmail.com>> wrote: Mark, Will Do. Waiting on it now. I'll run a test after I get out of my first class. William On Fri, Feb 17, 2012 at 8:25 AM, Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>> wrote: Michael, I just tried from the iPhone App I'm working on, and all seems ok. * Car was not charging, standard mode with limit 13A on a 70A HPC. * I sent a charge mode command to RANGE mode, and car switched to range mode, started charging at 13A and reported charging,range. * I sent a charge mode command to STANDARD mode, and car switched to standard mode, while charge continued at 13A and reported as charging,standard. * I sent a charge limit command to 32A, then car sent back limit 32A and within a few seconds increased the current at the car to 32amp. * I sent a charge limit command to 70A, then car sent back limit 70amp and within a few seconds increased the current at the car to 70amp. Sonny says he has fixed the Android App charge mode and the version in the market should be ok now. Can you try that? If the new version has not yet been released, perhaps selecting performance mode will enter range mode (assuming 3=2 and 4=3)? Regards, Mark. On 17 Feb, 2012, at 9:35 PM, Mark Webb-Johnson wrote:Michael, I tried issuing the commands manually on the can bus and can switch modes shown on the VDS. N.B. There is a bug in the Android App on the marketplace - it gets the mode numbers wrong (I guess 0..3 not 0,1,3,4). I'm implementing this in the iPhone App tonight, so should be able to test later. Regards, Mark. On 17 Feb, 2012, at 9:11 PM, Michael Stegen wrote:I can confirm that switching between charge modes does not work 100%. I tried switching to range mode, and then start charging from the app. The battery indicator in the car changes, i.e. the top of the battery is visible. Range does not change, also charge mode visible on the VDS does not change (still standard charging) On the (Android) app , it's shows the same. After i stopped the charging, i received a SMS that does not start with Range - or Standard - just "Charging Stopped, ideal range ..etc" Tonight i'll try to send the commands manually on the CAN bus, to see if i see any difference in behaviour. Btw, i do receive a "Hello World" push message on my android phone, but not on the Ipad. I'm not using any testflight version anymore, but the one from the appstore. Btw2, when a charge is stopped, i used to receive a push message + SMS, this somehow does not work anymore for me. I only receive the SMS Btw3, the car powers up fine, and starts charging, even if left unused (but connected) for over a day. -Michael Op 17-2-2012 8:06, Mark Webb-Johnson schreef:P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)Is this Android App? If so, Sonny (again): modes are 0=standard, 1=storage,3=range,4=performance P.S. What happened to mode 2? Did there used to be a mystery fifth mode? On 17 Feb 2012, at 2:59 PM, William Petefish wrote:Mark, Yes, fully repeatable, reproducible, and verifiable. When not woken up first, none of the commands work. I will restart the module and try further. It will disarm the alarm and allow it to be driven. William P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.) On Fri, Feb 17, 2012 at 12:51 AM, Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>> wrote: William, Is it repeatable? ie; plug in, stop charge. wait 5 minutes until coolant pump turns off, then try start charge from the app. Also, are other commands working (like lock/unlock)? After setting the feature for write-enabled CAN bus, you need to restart the module. If not, none of the commands will work. If at least one of the commands is working, then that is fine. Regards, Mark. P.S. Not wishing to hijack this thread, but since you are in the USA - could you test the lock/unlock commands for us on your US car? Supposedly, the US cars don't have an immobiliser so that the UNLOCK command will disable the alarm and allow the car to be driven. Please try and let us know. On 17 Feb 2012, at 2:35 PM, William Petefish wrote:Mark, Yes, I did and to no avail. I had purposefully let the car sit until it went into power save mode and tried again, no joy. Might it have something to do with the new FW on the roadster? (4.6.4 I think is the FW that is on mine.) My roadster is a 2.5. William On Fri, Feb 17, 2012 at 12:29 AM, Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>> wrote: William: Current (1.2.0-rc3) code is: void can_tx_setchargecurrent(unsigned char current) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x05; TXB0D1 = 0x02; TXB0D2 = 0x00; TXB0D3 = 0x00; TXB0D4 = current; TXB0D5 = 0x00; TXB0D6 = 0x00; TXB0D7 = 0x00; TXB0DLC = 0b00001000; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done can_tx_wakeup(); // Also, wakeup the car if necessary } void can_tx_wakeup(void) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x0a; TXB0DLC = 0b00000001; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done } That should work. Pre-rc3, I used to see this, but since rc3 it has been ok for me. Maybe the bus was busy and lost the wakeup message? Did you try sending any other commands, or repeating the start charge command? What is the version of your car (2.x or 1.5?). Regards, Mark. P.S. There is also a specific command C,18 that calls the CAN wakeup function. Not sure if the Android App supports it or not. On 17 Feb 2012, at 2:22 PM, William Petefish wrote:> Mark, > > Feature Needed: Wake Up command. > > I tried to send the start charge command > from my android phone and it wouldn't start > to charge or change charging mode, etc. > without being woken up by opening/closing > the doors/trunk/remote/etc. > > I am using the latest release (1.20) and the > Android app. > > William
_______________________________________________ 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-- Stegen Electronics Kwartslaan 95 3162 RD Rhoon The Netherlands Tel:+31 10-5016960 <tel:%2B31%2010-5016960> www.stegen.com <http://www.stegen.com/> _______________________________________________ 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 http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
-- Stegen Electronics Kwartslaan 95 3162 RD Rhoon The Netherlands
Tel: +31 10-5016960 www.stegen.com
Everyone,
Thanks for the reports. Here are some updates for the Android app in the market:
The PIN and current entry bugs are fixed. Sorry about the new bugs.
Screen rotation for the first two tabs are disabled for now because horizontal screens are getting too crowded on phones. I'm working on a new custom horizontal layout. Rotation will be enabled soon.
A new 4x1 home screen widget has been added to the latest version. Please note that it will only show up in the add widgets list when the app is installed inside phone memory (not SD card). This seems to be an Android restriction.
The widget is highly experimental and will be improved over upcoming updates. The way the app works now is that it closes the server TCP connection when it goes to background. As such, the widget's data can refresh only when the main app is opened. While I want to keep the TCP shutdown behavior, in the next version, at least the parking meter will remain live all the time.
The app has been over 5MB in size for some time. 90%+ of that goes to the very nice car layout graphics (one for each roadster color). As a low priority task, I'm going to make the app download the car images the first time you use them. This will make app updates speedy and conserve some bandwidth for limited data plans.
Michael, can you check the TCP log in the Android app to see if SMS,IP is sent after you tap commit? And when you tap refresh, does SMS,IP show up in the TCP log, under [RX] prefix? Thanks.
Sonny On Feb 18, 2012 6:01 AM, "Michael Stegen" <michael@stegen.com> wrote:
Sonny, Mark, others,
Thanks, the new update fixed the charge mode issues.
Some bugs:
I'm seeing the same two digit PIN limit now.
Also, setting the Charge current, causes a forced close of the app. (might be related to the beta ICS version i have on my phone right now)
The app also shows SMS/Paranoid Mode Password. Aren't those two different params? The app shows the SMS password "OVMS"
Somehow the notification mode setting is displayed as SMS only, instead of "SMS, IP" I changed it in the app, rebooted the module, but it doesn't stick. (at first i tought it did, but now it's back to "SMS" only)
Regards, Michael
Op 17-2-2012 17:16, William Petefish schreef:
Hard reset performed. Module working again.
Pin entry still limited to 2 characters.
William On Feb 17, 2012 10:05 AM, "William Petefish" <william.petefish@gmail.com> wrote:
Problem confirmed still. Module doesn't seem to be responding even after the reboot request.
Another popped up, pin entry in app limited to 2 characters.
William On Feb 17, 2012 8:34 AM, "William Petefish" <william.petefish@gmail.com> wrote:
Mark,
Will Do. Waiting on it now. I'll run a test after I get out of my first class.
William
On Fri, Feb 17, 2012 at 8:25 AM, Mark Webb-Johnson < mark@webb-johnson.net> wrote:
Michael,
I just tried from the iPhone App I'm working on, and all seems ok.
- Car was not charging, standard mode with limit 13A on a 70A HPC.
- I sent a charge mode command to RANGE mode, and car switched to range mode, started charging at 13A and reported charging,range.
- I sent a charge mode command to STANDARD mode, and car switched to standard mode, while charge continued at 13A and reported as charging,standard.
- I sent a charge limit command to 32A, then car sent back limit 32A and within a few seconds increased the current at the car to 32amp.
- I sent a charge limit command to 70A, then car sent back limit 70amp and within a few seconds increased the current at the car to 70amp.
Sonny says he has fixed the Android App charge mode and the version in the market should be ok now. Can you try that?
If the new version has not yet been released, perhaps selecting performance mode will enter range mode (assuming 3=2 and 4=3)?
Regards, Mark.
On 17 Feb, 2012, at 9:35 PM, Mark Webb-Johnson wrote:
Michael,
I tried issuing the commands manually on the can bus and can switch modes shown on the VDS.
N.B. There is a bug in the Android App on the marketplace - it gets the mode numbers wrong (I guess 0..3 not 0,1,3,4).
I'm implementing this in the iPhone App tonight, so should be able to test later.
Regards, Mark.
On 17 Feb, 2012, at 9:11 PM, Michael Stegen wrote:
I can confirm that switching between charge modes does not work 100%. I tried switching to range mode, and then start charging from the app.
The battery indicator in the car changes, i.e. the top of the battery is visible. Range does not change, also charge mode visible on the VDS does not change (still standard charging)
On the (Android) app , it's shows the same. After i stopped the charging, i received a SMS that does not start with Range - or Standard - just "Charging Stopped, ideal range ..etc"
Tonight i'll try to send the commands manually on the CAN bus, to see if i see any difference in behaviour.
Btw, i do receive a "Hello World" push message on my android phone, but not on the Ipad. I'm not using any testflight version anymore, but the one from the appstore.
Btw2, when a charge is stopped, i used to receive a push message + SMS, this somehow does not work anymore for me. I only receive the SMS
Btw3, the car powers up fine, and starts charging, even if left unused (but connected) for over a day.
-Michael
Op 17-2-2012 8:06, Mark Webb-Johnson schreef:
P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)
Is this Android App?
If so, Sonny (again): modes are 0=standard, 1=storage,3=range,4=performance
P.S. What happened to mode 2? Did there used to be a mystery fifth mode?
On 17 Feb 2012, at 2:59 PM, William Petefish wrote:
Mark,
Yes, fully repeatable, reproducible, and verifiable.
When not woken up first, none of the commands work.
I will restart the module and try further.
It will disarm the alarm and allow it to be driven.
William
P.S. Could someone fix the display so it reads Range Mode instead of Standard Mode when switched from standard to range? (Much appreciated.)
On Fri, Feb 17, 2012 at 12:51 AM, Mark Webb-Johnson < mark@webb-johnson.net> wrote:
William,
Is it repeatable?
ie; plug in, stop charge. wait 5 minutes until coolant pump turns off, then try start charge from the app.
Also, are other commands working (like lock/unlock)?
After setting the feature for write-enabled CAN bus, you need to restart the module. If not, none of the commands will work. If at least one of the commands is working, then that is fine.
Regards, Mark.
P.S. Not wishing to hijack this thread, but since you are in the USA
could you test the lock/unlock commands for us on your US car? Supposedly, the US cars don't have an immobiliser so that the UNLOCK command will disable the alarm and allow the car to be driven. Please try and let us know.
On 17 Feb 2012, at 2:35 PM, William Petefish wrote:
Mark,
Yes, I did and to no avail. I had purposefully let the car sit until it went into power save mode and tried again, no joy.
Might it have something to do with the new FW on the roadster? (4.6.4 I think is the FW that is on mine.) My roadster is a 2.5.
William
On Fri, Feb 17, 2012 at 12:29 AM, Mark Webb-Johnson < mark@webb-johnson.net> wrote:
William:
Current (1.2.0-rc3) code is:
void can_tx_setchargecurrent(unsigned char current) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x05; TXB0D1 = 0x02; TXB0D2 = 0x00; TXB0D3 = 0x00; TXB0D4 = current; TXB0D5 = 0x00; TXB0D6 = 0x00; TXB0D7 = 0x00; TXB0DLC = 0b00001000; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done
can_tx_wakeup(); // Also, wakeup the car if necessary }
void can_tx_wakeup(void) { while (TXB0CONbits.TXREQ) {} // Loop until TX is done TXB0CON = 0; TXB0SIDL = 0b01000000; // Setup 0x102 TXB0SIDH = 0b00100000; // Setup 0x102 TXB0D0 = 0x0a; TXB0DLC = 0b00000001; // data length (8) TXB0CON = 0b00001000; // mark for transmission while (TXB0CONbits.TXREQ) {} // Loop until TX is done }
That should work. Pre-rc3, I used to see this, but since rc3 it has been ok for me.
Maybe the bus was busy and lost the wakeup message? Did you try sending any other commands, or repeating the start charge command?
What is the version of your car (2.x or 1.5?).
Regards, Mark.
P.S. There is also a specific command C,18 that calls the CAN wakeup function. Not sure if the Android App supports it or not.
On 17 Feb 2012, at 2:22 PM, William Petefish wrote:
Mark,
Feature Needed: Wake Up command.
I tried to send the start charge command from my android phone and it wouldn't start to charge or change charging mode, etc. without being woken up by opening/closing the doors/trunk/remote/etc.
I am using the latest release (1.20) and the Android app.
William
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 listOvmsDev@lists.teslaclub.hkhttp://lists.teslaclub.hk/mailman/listinfo/ovmsdev
-- Stegen Electronics Kwartslaan 95 3162 RD Rhoon The Netherlands
Tel: +31 10-5016960www.stegen.com
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 listOvmsDev@lists.teslaclub.hkhttp://lists.teslaclub.hk/mailman/listinfo/ovmsdev
-- Stegen Electronics Kwartslaan 95 3162 RD Rhoon The Netherlands
Tel: +31 10-5016960www.stegen.com
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Sonny,
This sounds cool. Could you post some screen-shots for us Android-deprived Apple fan-boys?
On 18 Feb, 2012, at 11:07 AM, Sonny <email@sonnychen.com> wrote:
A new 4x1 home screen widget has been added to the latest version. Please note that it will only show up in the add widgets list when the app is installed inside phone memory (not SD card). This seems to be an Android restriction.
The widget is highly experimental and will be improved over upcoming updates. The way the app works now is that it closes the server TCP connection when it goes to background. As such, the widget's data can refresh only when the main app is opened. While I want to keep the TCP shutdown behavior, in the next version, at least the parking meter will remain live all the time.
Mark,
Sure, screenshot attached. It's slightly more updated than the version on the Market but still very rough.
The parking meter updates live in this version (next Market update). It is a chronometer (an Android control) that updates every second and displays the current parked time based on the last known data received by the main app. The UI is refreshed only when the device is awake.
Sonny
Sonny, Mark,
Thanks for the update.
Yes i see that it's sent: [TX] C4,3,SMS,IP
When refreshing the data i can see that it still set to SMS,IP [RX] c3,0,3,32,SMS,IP But no push messages, only SMS
- Rebooted the module, still displayed as SMS,IP
- Rebooted phone, and it's back to SMS only. Refreshing the data shows SMS,IP in the TCP log. (app does not change, still SMS only)
I tried setting it to IP only, rebooted the phone + module, Now i do receive IP messages (only).
Mark, can you see in your server logs if these push messages have been sent out?
Ref the Charge Current, you can not set it higher that the pilot signal allows.
-Michael
Op 18-2-2012 4:07, Sonny schreef:
Everyone,
Thanks for the reports. Here are some updates for the Android app in the market:
The PIN and current entry bugs are fixed. Sorry about the new bugs.
Screen rotation for the first two tabs are disabled for now because horizontal screens are getting too crowded on phones. I'm working on a new custom horizontal layout. Rotation will be enabled soon.
A new 4x1 home screen widget has been added to the latest version. Please note that it will only show up in the add widgets list when the app is installed inside phone memory (not SD card). This seems to be an Android restriction.
The widget is highly experimental and will be improved over upcoming updates. The way the app works now is that it closes the server TCP connection when it goes to background. As such, the widget's data can refresh only when the main app is opened. While I want to keep the TCP shutdown behavior, in the next version, at least the parking meter will remain live all the time.
The app has been over 5MB in size for some time. 90%+ of that goes to the very nice car layout graphics (one for each roadster color). As a low priority task, I'm going to make the app download the car images the first time you use them. This will make app updates speedy and conserve some bandwidth for limited data plans.
Michael, can you check the TCP log in the Android app to see if SMS,IP is sent after you tap commit? And when you tap refresh, does SMS,IP show up in the TCP log, under [RX] prefix? Thanks.
Sonny
participants (4)
-
Mark Webb-Johnson -
Michael Stegen -
Sonny -
William Petefish