I'll be updating mine in a few min... William On Sun, Sep 2, 2012 at 8:36 PM, Mark Webb-Johnson <mark@webb-johnson.net>wrote:

Tom,

Thanks. Looks good. 4 cars updated to v1.3.1 overnight and all seem to be reporting in ok.

I should have the production V2 modules in my hands today or tomorrow, and will send pictures of them with the pickit plugged in. I only have a pickit3, but it looks similar enough.

To avoid confusion between V1 and V2, probably best to just include a picture of the two modules. They look so completely different, that should avoid any mistakes. We really don't want people to be flashing the wrong firmware to the wrong modules. In particular, for V2 devices, they will accept V1 firmware but a few things won't work properly (like the GSM/GPRS switch). I've been trying to work out how to pickup the processor ID so I can check at startup and refuse to run if the wrong firmware is flashed, but still not solved.

Regards, Mark

On 3 Sep, 2012, at 12:25 AM, Tom Saxton wrote:

...

I've updated my OVMS Firmware Update Guide.

http://www.idleloop.com/tesla/ovms/

I need a photo of the PICkit2 programmer plugged into the V2 board correctly to add to the page. Also, I'd like to know what device string appears in the PICkit2 programmer software when connected to a V2 board.

I'll wait until it's officially released to post my install page update onto TMC, or Mark you can just link to it when you post the release.

Tom

on 9/1/12 11:45 PM, Mark Webb-Johnson wrote:

...

Car firmware 1.3.1 is in GitHub now. I built all variants to .hex files, and source is there for the adventurous. Tom: can you help setup end-user instructions of this?

All outstanding car issues recorded on github have been resolved and closed with this version.

It has been running in my car for a few days, and seems fine. I did a few different charge-interruption tests, and they all alert as expected.

I'm gonna wait a few days to allow you guys some time to try it out and report any issues (hopefully none). I'll then announce it as generally available. Due to the enhanced modem control, linear connection backup algorithm, bug fixes, and new improved notification algorithm, this will be a recommended update for all users.

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

As of late, I haven't been getting the charge finished notifications. The app says that the charge is complete, but OVMS waits for me to unplug the car before it sends any notifications. (those stopped sometime within the last two weeks.) BTW this is a Roadster 2.5 non-sport. William On Mon, Sep 3, 2012 at 12:03 AM, Mark Webb-Johnson <mark@webb-johnson.net>wrote:

Thanks William, I see 5 now.

Most helpful thing people on this list can do to help out this week is deploy this firmware to their car and help test it for stability. I am most interested in:

1. If the car is in an area of poor / no cellular coverage, then drives out to an area of good coverage, does OVMS connection re-establish? In particular, if you previously saw a situation where you had to unplug-then-plugin the module to hard-reset it, does that still happen? If realise that this will take longer to know, as it was very rare.

2. If you interrupt charges in various ways, do you get SMS/PUSH notifications if the charge stopping?

3. If charges complete normally, in various ways, do you get false SMS/PUSH notifications?

4. Any weird numbers, or other problems, with Motor Temperature - particularly in very hot or very cold areas?

5. Any weird numbers, or other problems, with ideal/estimated ranges - particularly when the battery is very full, very empty or when changing between standard and range modes?

Thanks, Mark.

On 3 Sep, 2012, at 11:29 AM, William Petefish wrote:

I'll be updating mine in a few min...

William

On Sun, Sep 2, 2012 at 8:36 PM, Mark Webb-Johnson <mark@webb-johnson.net>wrote:

...

Tom,

Thanks. Looks good. 4 cars updated to v1.3.1 overnight and all seem to be reporting in ok.

I should have the production V2 modules in my hands today or tomorrow, and will send pictures of them with the pickit plugged in. I only have a pickit3, but it looks similar enough.

To avoid confusion between V1 and V2, probably best to just include a picture of the two modules. They look so completely different, that should avoid any mistakes. We really don't want people to be flashing the wrong firmware to the wrong modules. In particular, for V2 devices, they will accept V1 firmware but a few things won't work properly (like the GSM/GPRS switch). I've been trying to work out how to pickup the processor ID so I can check at startup and refuse to run if the wrong firmware is flashed, but still not solved.

Regards, Mark

On 3 Sep, 2012, at 12:25 AM, Tom Saxton wrote:

...

I've updated my OVMS Firmware Update Guide.

http://www.idleloop.com/tesla/ovms/

I need a photo of the PICkit2 programmer plugged into the V2 board correctly to add to the page. Also, I'd like to know what device string appears in the PICkit2 programmer software when connected to a V2 board.

I'll wait until it's officially released to post my install page update onto TMC, or Mark you can just link to it when you post the release.

Tom

on 9/1/12 11:45 PM, Mark Webb-Johnson wrote:

...

Car firmware 1.3.1 is in GitHub now. I built all variants to .hex files, and source is there for the adventurous. Tom: can you help setup end-user instructions of this?

All outstanding car issues recorded on github have been resolved and closed with this version.

It has been running in my car for a few days, and seems fine. I did a few different charge-interruption tests, and they all alert as expected.

I'm gonna wait a few days to allow you guys some time to try it out and report any issues (hopefully none). I'll then announce it as generally available. Due to the enhanced modem control, linear connection backup algorithm, bug fixes, and new improved notification algorithm, this will be a recommended update for all users.

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

SMS and IP are selected. I'll try unplugging while charging tonight. William On Sep 3, 2012 7:03 PM, "Mark Webb-Johnson" <mark@webb-johnson.net> wrote:

William,

I suggest you check the 'features' and 'parameters' set on the phone. Make sure notifications are enabled. In particular, the notification method should be "SMSIP" (or SMS or IP alone).

To test a charge alert, plug the car in and start a charge. Make sure the App is showing the charge in progress (it takes about a minute for the car to start the charge). Then, on the car itself, slide the plug switch to off (or interrupt by circuit breaker if you want to be more abrupt). That will interrupt the charge, and generate a 'stopped' charge state 100% of the time. You should then get a notification however you've configured it.

Stopping the charge from the cellphone apps or sms messages should not generate an alert. If the charge completes normally, it will end in 'done' state and that should also not generate an alert.

If someone cars to try, the extension cord detected error message in the car should now result in charge stopped notifications. You won't get the detailed reason message, but you should get the alert.

Regards, Mark.

On 4 Sep, 2012, at 3:42 AM, William Petefish wrote:

As of late, I haven't been getting the charge finished notifications. The app says that the charge is complete, but OVMS waits for me to unplug the car before it sends any notifications. (those stopped sometime within the last two weeks.)

BTW this is a Roadster 2.5 non-sport.

William

On Mon, Sep 3, 2012 at 12:03 AM, Mark Webb-Johnson <mark@webb-johnson.net>wrote:

...

Thanks William, I see 5 now.

Most helpful thing people on this list can do to help out this week is deploy this firmware to their car and help test it for stability. I am most interested in:

1. If the car is in an area of poor / no cellular coverage, then drives out to an area of good coverage, does OVMS connection re-establish? In particular, if you previously saw a situation where you had to unplug-then-plugin the module to hard-reset it, does that still happen? If realise that this will take longer to know, as it was very rare.

2. If you interrupt charges in various ways, do you get SMS/PUSH notifications if the charge stopping?

3. If charges complete normally, in various ways, do you get false SMS/PUSH notifications?

4. Any weird numbers, or other problems, with Motor Temperature - particularly in very hot or very cold areas?

5. Any weird numbers, or other problems, with ideal/estimated ranges - particularly when the battery is very full, very empty or when changing between standard and range modes?

Thanks, Mark.

On 3 Sep, 2012, at 11:29 AM, William Petefish wrote:

I'll be updating mine in a few min...

William

On Sun, Sep 2, 2012 at 8:36 PM, Mark Webb-Johnson <mark@webb-johnson.net>wrote:

...

Tom,

Thanks. Looks good. 4 cars updated to v1.3.1 overnight and all seem to be reporting in ok.

I should have the production V2 modules in my hands today or tomorrow, and will send pictures of them with the pickit plugged in. I only have a pickit3, but it looks similar enough.

To avoid confusion between V1 and V2, probably best to just include a picture of the two modules. They look so completely different, that should avoid any mistakes. We really don't want people to be flashing the wrong firmware to the wrong modules. In particular, for V2 devices, they will accept V1 firmware but a few things won't work properly (like the GSM/GPRS switch). I've been trying to work out how to pickup the processor ID so I can check at startup and refuse to run if the wrong firmware is flashed, but still not solved.

Regards, Mark

On 3 Sep, 2012, at 12:25 AM, Tom Saxton wrote:

...

I've updated my OVMS Firmware Update Guide.

http://www.idleloop.com/tesla/ovms/

I need a photo of the PICkit2 programmer plugged into the V2 board correctly to add to the page. Also, I'd like to know what device string appears in the PICkit2 programmer software when connected to a V2 board.

I'll wait until it's officially released to post my install page update onto TMC, or Mark you can just link to it when you post the release.

Tom

on 9/1/12 11:45 PM, Mark Webb-Johnson wrote:

...

Car firmware 1.3.1 is in GitHub now. I built all variants to .hex files, and source is there for the adventurous. Tom: can you help setup end-user instructions of this?

All outstanding car issues recorded on github have been resolved and closed with this version.

It has been running in my car for a few days, and seems fine. I did a few different charge-interruption tests, and they all alert as expected.

I'm gonna wait a few days to allow you guys some time to try it out and report any issues (hopefully none). I'll then announce it as generally available. Due to the enhanced modem control, linear connection backup algorithm, bug fixes, and new improved notification algorithm, this will be a recommended update for all users.

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

_______________________________________________ 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

William, It isn't supposed to notify you when a charge completes normally, only when it is interrupted. For example: SOC at 90%, plug it in and let charge complete normally -> No notification SOC at 90%, plug it in, but when SOC reaches 92% unplug to interrupt the charge -> Notification will be raised Is that what you mean? Regards, Mark. On 4 Sep, 2012, at 10:17 AM, William Petefish wrote:

Unplugging works, but it doesn't notify you when a charge is completed. Only after unplugging does it send any messages.

William

On Sep 3, 2012 7:46 PM, "William Petefish" <william.petefish@gmail.com> wrote: SMS and IP are selected. I'll try unplugging while charging tonight.

William

On Sep 3, 2012 7:03 PM, "Mark Webb-Johnson" <mark@webb-johnson.net> wrote: William,

I suggest you check the 'features' and 'parameters' set on the phone. Make sure notifications are enabled. In particular, the notification method should be "SMSIP" (or SMS or IP alone).

To test a charge alert, plug the car in and start a charge. Make sure the App is showing the charge in progress (it takes about a minute for the car to start the charge). Then, on the car itself, slide the plug switch to off (or interrupt by circuit breaker if you want to be more abrupt). That will interrupt the charge, and generate a 'stopped' charge state 100% of the time. You should then get a notification however you've configured it.

Stopping the charge from the cellphone apps or sms messages should not generate an alert. If the charge completes normally, it will end in 'done' state and that should also not generate an alert.

If someone cars to try, the extension cord detected error message in the car should now result in charge stopped notifications. You won't get the detailed reason message, but you should get the alert.

Regards, Mark.

On 4 Sep, 2012, at 3:42 AM, William Petefish wrote:

...

As of late, I haven't been getting the charge finished notifications. The app says that the charge is complete, but OVMS waits for me to unplug the car before it sends any notifications. (those stopped sometime within the last two weeks.)

BTW this is a Roadster 2.5 non-sport.

William

On Mon, Sep 3, 2012 at 12:03 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: Thanks William, I see 5 now.

Most helpful thing people on this list can do to help out this week is deploy this firmware to their car and help test it for stability. I am most interested in:

If the car is in an area of poor / no cellular coverage, then drives out to an area of good coverage, does OVMS connection re-establish? In particular, if you previously saw a situation where you had to unplug-then-plugin the module to hard-reset it, does that still happen? If realise that this will take longer to know, as it was very rare.

If you interrupt charges in various ways, do you get SMS/PUSH notifications if the charge stopping?

If charges complete normally, in various ways, do you get false SMS/PUSH notifications?

Any weird numbers, or other problems, with Motor Temperature - particularly in very hot or very cold areas?

Any weird numbers, or other problems, with ideal/estimated ranges - particularly when the battery is very full, very empty or when changing between standard and range modes?

Thanks, Mark.

On 3 Sep, 2012, at 11:29 AM, William Petefish wrote:

...

I'll be updating mine in a few min...

William

On Sun, Sep 2, 2012 at 8:36 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: Tom,

Thanks. Looks good. 4 cars updated to v1.3.1 overnight and all seem to be reporting in ok.

I should have the production V2 modules in my hands today or tomorrow, and will send pictures of them with the pickit plugged in. I only have a pickit3, but it looks similar enough.

To avoid confusion between V1 and V2, probably best to just include a picture of the two modules. They look so completely different, that should avoid any mistakes. We really don't want people to be flashing the wrong firmware to the wrong modules. In particular, for V2 devices, they will accept V1 firmware but a few things won't work properly (like the GSM/GPRS switch). I've been trying to work out how to pickup the processor ID so I can check at startup and refuse to run if the wrong firmware is flashed, but still not solved.

Regards, Mark

On 3 Sep, 2012, at 12:25 AM, Tom Saxton wrote:

...

I've updated my OVMS Firmware Update Guide.

http://www.idleloop.com/tesla/ovms/

I need a photo of the PICkit2 programmer plugged into the V2 board correctly to add to the page. Also, I'd like to know what device string appears in the PICkit2 programmer software when connected to a V2 board.

I'll wait until it's officially released to post my install page update onto TMC, or Mark you can just link to it when you post the release.

Tom

on 9/1/12 11:45 PM, Mark Webb-Johnson wrote:

...

Car firmware 1.3.1 is in GitHub now. I built all variants to .hex files, and source is there for the adventurous. Tom: can you help setup end-user instructions of this?

All outstanding car issues recorded on github have been resolved and closed with this version.

It has been running in my car for a few days, and seems fine. I did a few different charge-interruption tests, and they all alert as expected.

I'm gonna wait a few days to allow you guys some time to try it out and report any issues (hopefully none). I'll then announce it as generally available. Due to the enhanced modem control, linear connection backup algorithm, bug fixes, and new improved notification algorithm, this will be a recommended update for all users.

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

_______________________________________________ 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

After updating firmware to 1.3.1 (experimental) I interrupted a charge before completion and did not receive any notifications. I double checked OVMS settings (SMSIP) and phone notification center (OVMS notifications 'ON'). I'm using IOS and compiled the source from Github. I'll try to repeat the test when my wife brings the car back on Thursday. I live in an area with poor cell coverage and so far OVMS has not shown any problems with connectivity. Jack On Sep 3, 2012, at 6:23 PM, William Petefish <william.petefish@gmail.com> wrote:

Thanks for the clarification.

William

On Sep 3, 2012 9:22 PM, "Mark Webb-Johnson" <mark@webb-johnson.net> wrote:

William,

It isn't supposed to notify you when a charge completes normally, only when it is interrupted.

For example:

SOC at 90%, plug it in and let charge complete normally -> No notification SOC at 90%, plug it in, but when SOC reaches 92% unplug to interrupt the charge -> Notification will be raised

Is that what you mean?

Regards, Mark.

On 4 Sep, 2012, at 10:17 AM, William Petefish wrote:

...

Unplugging works, but it doesn't notify you when a charge is completed. Only after unplugging does it send any messages.

William

On Sep 3, 2012 7:46 PM, "William Petefish" <william.petefish@gmail.com> wrote: SMS and IP are selected. I'll try unplugging while charging tonight.

William

On Sep 3, 2012 7:03 PM, "Mark Webb-Johnson" <mark@webb-johnson.net> wrote: William,

I suggest you check the 'features' and 'parameters' set on the phone. Make sure notifications are enabled. In particular, the notification method should be "SMSIP" (or SMS or IP alone).

To test a charge alert, plug the car in and start a charge. Make sure the App is showing the charge in progress (it takes about a minute for the car to start the charge). Then, on the car itself, slide the plug switch to off (or interrupt by circuit breaker if you want to be more abrupt). That will interrupt the charge, and generate a 'stopped' charge state 100% of the time. You should then get a notification however you've configured it.

Stopping the charge from the cellphone apps or sms messages should not generate an alert. If the charge completes normally, it will end in 'done' state and that should also not generate an alert.

If someone cars to try, the extension cord detected error message in the car should now result in charge stopped notifications. You won't get the detailed reason message, but you should get the alert.

Regards, Mark.

On 4 Sep, 2012, at 3:42 AM, William Petefish wrote:

...

As of late, I haven't been getting the charge finished notifications. The app says that the charge is complete, but OVMS waits for me to unplug the car before it sends any notifications. (those stopped sometime within the last two weeks.)

BTW this is a Roadster 2.5 non-sport.

William

On Mon, Sep 3, 2012 at 12:03 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: Thanks William, I see 5 now.

Most helpful thing people on this list can do to help out this week is deploy this firmware to their car and help test it for stability. I am most interested in:

If the car is in an area of poor / no cellular coverage, then drives out to an area of good coverage, does OVMS connection re-establish? In particular, if you previously saw a situation where you had to unplug-then-plugin the module to hard-reset it, does that still happen? If realise that this will take longer to know, as it was very rare.

If you interrupt charges in various ways, do you get SMS/PUSH notifications if the charge stopping?

If charges complete normally, in various ways, do you get false SMS/PUSH notifications?

Any weird numbers, or other problems, with Motor Temperature - particularly in very hot or very cold areas?

Any weird numbers, or other problems, with ideal/estimated ranges - particularly when the battery is very full, very empty or when changing between standard and range modes?

Thanks, Mark.

On 3 Sep, 2012, at 11:29 AM, William Petefish wrote:

...

I'll be updating mine in a few min...

William

On Sun, Sep 2, 2012 at 8:36 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: Tom,

Thanks. Looks good. 4 cars updated to v1.3.1 overnight and all seem to be reporting in ok.

I should have the production V2 modules in my hands today or tomorrow, and will send pictures of them with the pickit plugged in. I only have a pickit3, but it looks similar enough.

To avoid confusion between V1 and V2, probably best to just include a picture of the two modules. They look so completely different, that should avoid any mistakes. We really don't want people to be flashing the wrong firmware to the wrong modules. In particular, for V2 devices, they will accept V1 firmware but a few things won't work properly (like the GSM/GPRS switch). I've been trying to work out how to pickup the processor ID so I can check at startup and refuse to run if the wrong firmware is flashed, but still not solved.

Regards, Mark

On 3 Sep, 2012, at 12:25 AM, Tom Saxton wrote:

...

I've updated my OVMS Firmware Update Guide.

http://www.idleloop.com/tesla/ovms/

I need a photo of the PICkit2 programmer plugged into the V2 board correctly to add to the page. Also, I'd like to know what device string appears in the PICkit2 programmer software when connected to a V2 board.

I'll wait until it's officially released to post my install page update onto TMC, or Mark you can just link to it when you post the release.

Tom

on 9/1/12 11:45 PM, Mark Webb-Johnson wrote:

...

Car firmware 1.3.1 is in GitHub now. I built all variants to .hex files, and source is there for the adventurous. Tom: can you help setup end-user instructions of this?

All outstanding car issues recorded on github have been resolved and closed with this version.

It has been running in my car for a few days, and seems fine. I did a few different charge-interruption tests, and they all alert as expected.

I'm gonna wait a few days to allow you guys some time to try it out and report any issues (hopefully none). I'll then announce it as generally available. Due to the enhanced modem control, linear connection backup algorithm, bug fixes, and new improved notification algorithm, this will be a recommended update for all users.

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

_______________________________________________ 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

Ooopps. Looked right at it but missed the fact that it wasn't caps. On Sep 4, 2012, at 4:46 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

Jack,

I think your problem may be the notification parameter you have is 'smsip'. Can you try putting it in upper-case 'SMSIP'?

Regards, Mark.

On 5 Sep, 2012, at 12:57 AM, Jack West wrote:

...

After updating firmware to 1.3.1 (experimental) I interrupted a charge before completion and did not receive any notifications. I double checked OVMS settings (SMSIP) and phone notification center (OVMS notifications 'ON'). I'm using IOS and compiled the source from Github.

I'll try to repeat the test when my wife brings the car back on Thursday. I live in an area with poor cell coverage and so far OVMS has not shown any problems with connectivity.

Jack

On Sep 3, 2012, at 6:23 PM, William Petefish <william.petefish@gmail.com> wrote:

...

Thanks for the clarification.

William

On Sep 3, 2012 9:22 PM, "Mark Webb-Johnson" <mark@webb-johnson.net> wrote:

William,

It isn't supposed to notify you when a charge completes normally, only when it is interrupted.

For example:

SOC at 90%, plug it in and let charge complete normally -> No notification SOC at 90%, plug it in, but when SOC reaches 92% unplug to interrupt the charge -> Notification will be raised

Is that what you mean?

Regards, Mark.

On 4 Sep, 2012, at 10:17 AM, William Petefish wrote:

...

Unplugging works, but it doesn't notify you when a charge is completed. Only after unplugging does it send any messages.

William

On Sep 3, 2012 7:46 PM, "William Petefish" <william.petefish@gmail.com> wrote: SMS and IP are selected. I'll try unplugging while charging tonight.

William

On Sep 3, 2012 7:03 PM, "Mark Webb-Johnson" <mark@webb-johnson.net> wrote: William,

I suggest you check the 'features' and 'parameters' set on the phone. Make sure notifications are enabled. In particular, the notification method should be "SMSIP" (or SMS or IP alone).

To test a charge alert, plug the car in and start a charge. Make sure the App is showing the charge in progress (it takes about a minute for the car to start the charge). Then, on the car itself, slide the plug switch to off (or interrupt by circuit breaker if you want to be more abrupt). That will interrupt the charge, and generate a 'stopped' charge state 100% of the time. You should then get a notification however you've configured it.

Stopping the charge from the cellphone apps or sms messages should not generate an alert. If the charge completes normally, it will end in 'done' state and that should also not generate an alert.

If someone cars to try, the extension cord detected error message in the car should now result in charge stopped notifications. You won't get the detailed reason message, but you should get the alert.

Regards, Mark.

On 4 Sep, 2012, at 3:42 AM, William Petefish wrote:

...

As of late, I haven't been getting the charge finished notifications. The app says that the charge is complete, but OVMS waits for me to unplug the car before it sends any notifications. (those stopped sometime within the last two weeks.)

BTW this is a Roadster 2.5 non-sport.

William

On Mon, Sep 3, 2012 at 12:03 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: Thanks William, I see 5 now.

Most helpful thing people on this list can do to help out this week is deploy this firmware to their car and help test it for stability. I am most interested in:

If the car is in an area of poor / no cellular coverage, then drives out to an area of good coverage, does OVMS connection re-establish? In particular, if you previously saw a situation where you had to unplug-then-plugin the module to hard-reset it, does that still happen? If realise that this will take longer to know, as it was very rare.

If you interrupt charges in various ways, do you get SMS/PUSH notifications if the charge stopping?

If charges complete normally, in various ways, do you get false SMS/PUSH notifications?

Any weird numbers, or other problems, with Motor Temperature - particularly in very hot or very cold areas?

Any weird numbers, or other problems, with ideal/estimated ranges - particularly when the battery is very full, very empty or when changing between standard and range modes?

Thanks, Mark.

On 3 Sep, 2012, at 11:29 AM, William Petefish wrote:

...

I'll be updating mine in a few min...

William

On Sun, Sep 2, 2012 at 8:36 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: Tom,

Thanks. Looks good. 4 cars updated to v1.3.1 overnight and all seem to be reporting in ok.

I should have the production V2 modules in my hands today or tomorrow, and will send pictures of them with the pickit plugged in. I only have a pickit3, but it looks similar enough.

To avoid confusion between V1 and V2, probably best to just include a picture of the two modules. They look so completely different, that should avoid any mistakes. We really don't want people to be flashing the wrong firmware to the wrong modules. In particular, for V2 devices, they will accept V1 firmware but a few things won't work properly (like the GSM/GPRS switch). I've been trying to work out how to pickup the processor ID so I can check at startup and refuse to run if the wrong firmware is flashed, but still not solved.

Regards, Mark

On 3 Sep, 2012, at 12:25 AM, Tom Saxton wrote:

> I've updated my OVMS Firmware Update Guide. > > http://www.idleloop.com/tesla/ovms/ > > I need a photo of the PICkit2 programmer plugged into the V2 board correctly > to add to the page. Also, I'd like to know what device string appears in the > PICkit2 programmer software when connected to a V2 board. > > I'll wait until it's officially released to post my install page update onto > TMC, or Mark you can just link to it when you post the release. > > Tom > > on 9/1/12 11:45 PM, Mark Webb-Johnson wrote: > >> Car firmware 1.3.1 is in GitHub now. I built all variants to .hex files, and >> source is there for the adventurous. Tom: can you help setup end-user >> instructions of this? >> >> All outstanding car issues recorded on github have been resolved and closed >> with this version. >> >> It has been running in my car for a few days, and seems fine. I did a few >> different charge-interruption tests, and they all alert as expected. >> >> I'm gonna wait a few days to allow you guys some time to try it out and report >> any issues (hopefully none). I'll then announce it as generally available. Due >> to the enhanced modem control, linear connection backup algorithm, bug fixes, >> and new improved notification algorithm, this will be a recommended update for >> all users. >> >> 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

_______________________________________________ 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

Jack, Strange, mine did the same (at roughly the same time). Mine still hasn't recovered, but is in good coverage area now. Without resetting, I'm going to put a serial console on it when I get home tonight. Hopefully I can see what is going on then. Regards, Mark. On 17 Sep, 2012, at 1:40 PM, Jack West wrote:

I lost connectivity today with the car in our garage. We live in a poor cell coverage area and this is not that unusual. However, later today I drove into the city where coverage is excellent and OVMS did not reconnect. After hard reset OVMS was able to connect. If there is any other information I can supply, please let me know. I updated firmware to 1.3.5 a couple days ago.

Jack

On Sep 2, 2012, at 9:03 PM, Mark Webb-Johnson <mark@webb-johnson.net>

...

If the car is in an area of poor / no cellular coverage, then drives out to an area of good coverage, does OVMS connection re-establish? In particular, if you previously saw a situation where you had to unplug-then-plugin the module to hard-reset it, does that still happen? If realise that this will take longer to know, as it was very rare.

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

Mark, I think it was a series of four fairly fast green led blinks, red led off, that repeated maybe 5 or 6 times and ending with a solid red and green. Then the entire sequence would repeat. OVMS was down about 7 hours total with the last hour or two being in good cell coverage area before I did the hard reset. Jack On Sep 17, 2012, at 3:50 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

Jack,

Do you remember what code the lights were flashing?

I checked mine, and it was bizarre. Green LED was flashing 1 (GPRS up and connected), and red LED was off (no errors found). But, when I connected a PC to the DIAG port (thanks to v2 hardware I can do this now when the box is running), the modem responded just fine but there was no comms between the modem and the PIC. As the LEDs were flashing, the PIC was definitely running. It seems that the RS232 port was just dead on the PIC side. A hardware reset brought it back alive.

I guess I'll have to add a timer to the NET driver code for data last received on the modem port. If nothing is received in a few minutes, then time to reset everything.

Regards, Mark.

On 17 Sep, 2012, at 1:49 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

...

Jack,

Strange, mine did the same (at roughly the same time). Mine still hasn't recovered, but is in good coverage area now.

Without resetting, I'm going to put a serial console on it when I get home tonight. Hopefully I can see what is going on then.

Regards, Mark.

On 17 Sep, 2012, at 1:40 PM, Jack West wrote:

...

I lost connectivity today with the car in our garage. We live in a poor cell coverage area and this is not that unusual. However, later today I drove into the city where coverage is excellent and OVMS did not reconnect. After hard reset OVMS was able to connect. If there is any other information I can supply, please let me know. I updated firmware to 1.3.5 a couple days ago.

Jack

On Sep 2, 2012, at 9:03 PM, Mark Webb-Johnson <mark@webb-johnson.net>

...

If the car is in an area of poor / no cellular coverage, then drives out to an area of good coverage, does OVMS connection re-establish? In particular, if you previously saw a situation where you had to unplug-then-plugin the module to hard-reset it, does that still happen? If realise that this will take longer to know, as it was very rare.

_______________________________________________ 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 seen this as well. I suspect somehow the code is getting into a loop and the watchdog timer is firing to reset the module. As the experimental speedo setting is volatile, it will be 'lost' on reset. The watchdog timer should be 8 seconds, so it would have to be a pretty bad loop for this to occur. It could also be a stack overflow. I'll try to track down the problem by looking at the changes. To try to narrow down the version it happened at, does anyone else using the digital speedo see this problem and if so what version are you using? If you don't see the problem, and are using digital speedo and a version >1.2.7 then please also let me know. Regards, Mark. On 20 Sep, 2012, at 1:10 AM, 911carrera4 wrote:

Dear all In the last 2 days my digital speedo seems to reset itself for a reason I don’t understand. The OVMS has always been under power and is sending data. It seemed to happen after I parked my car in a garage where the GPS signal can’t be received. I tried to reproduce the problem but couldn’t do it. It happened the first time after firmware update to 1.3.5/V1 experimental. I could re-activate the feature via application without any problems.

Question: does anyone of you has the same problem?

Piotr

Von: ovmsdev-bounces@lists.teslaclub.hk [mailto:ovmsdev-bounces@lists.teslaclub.hk] Im Auftrag von Jack West Gesendet: Montag, 17. September 2012 16:50 An: OVMS Developers Betreff: Re: [Ovmsdev] 1.3.1

Mark, I think it was a series of four fairly fast green led blinks, red led off, that repeated maybe 5 or 6 times and ending with a solid red and green. Then the entire sequence would repeat. OVMS was down about 7 hours total with the last hour or two being in good cell coverage area before I did the hard reset.

Jack

On Sep 17, 2012, at 3:50 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

Jack,

Do you remember what code the lights were flashing?

I checked mine, and it was bizarre. Green LED was flashing 1 (GPRS up and connected), and red LED was off (no errors found). But, when I connected a PC to the DIAG port (thanks to v2 hardware I can do this now when the box is running), the modem responded just fine but there was no comms between the modem and the PIC. As the LEDs were flashing, the PIC was definitely running. It seems that the RS232 port was just dead on the PIC side. A hardware reset brought it back alive.

I guess I'll have to add a timer to the NET driver code for data last received on the modem port. If nothing is received in a few minutes, then time to reset everything.

Regards, Mark.

On 17 Sep, 2012, at 1:49 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

Jack,

Strange, mine did the same (at roughly the same time). Mine still hasn't recovered, but is in good coverage area now.

Without resetting, I'm going to put a serial console on it when I get home tonight. Hopefully I can see what is going on then.

Regards, Mark.

On 17 Sep, 2012, at 1:40 PM, Jack West wrote:

I lost connectivity today with the car in our garage. We live in a poor cell coverage area and this is not that unusual. However, later today I drove into the city where coverage is excellent and OVMS did not reconnect. After hard reset OVMS was able to connect. If there is any other information I can supply, please let me know. I updated firmware to 1.3.5 a couple days ago.

Jack

On Sep 2, 2012, at 9:03 PM, Mark Webb-Johnson <mark@webb-johnson.net> If the car is in an area of poor / no cellular coverage, then drives out to an area of good coverage, does OVMS connection re-establish? In particular, if you previously saw a situation where you had to unplug-then-plugin the module to hard-reset it, does that still happen? If realise that this will take longer to know, as it was very rare.

_______________________________________________ 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, Today my wife drove our car from our house (poor coverage) to a town about 60 miles away (good coverage). I used the app to check her SOC when she was there and though the app indicated "live", the data showed she hadn't left home yet. I reset OVMS by the app and soon after was getting proper data. It seems strange that the app would be showing "live", yet the data be incorrect and also still be able to be reset. This was approximately 5PM local time if you care to look at the logs. Let me know if there is any other info you need. As I did the reset remotely, I do not know what codes the LEDs were showing but this situation might be repeatable as it has now happened (at least I think it was the same thing) on the last two trips from our house into the city. Best, Jack On Sep 17, 2012, at 3:50 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

Jack,

Do you remember what code the lights were flashing?

I checked mine, and it was bizarre. Green LED was flashing 1 (GPRS up and connected), and red LED was off (no errors found). But, when I connected a PC to the DIAG port (thanks to v2 hardware I can do this now when the box is running), the modem responded just fine but there was no comms between the modem and the PIC. As the LEDs were flashing, the PIC was definitely running. It seems that the RS232 port was just dead on the PIC side. A hardware reset brought it back alive.

I guess I'll have to add a timer to the NET driver code for data last received on the modem port. If nothing is received in a few minutes, then time to reset everything.

Regards, Mark.

On 17 Sep, 2012, at 1:49 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

...

Jack,

Strange, mine did the same (at roughly the same time). Mine still hasn't recovered, but is in good coverage area now.

Without resetting, I'm going to put a serial console on it when I get home tonight. Hopefully I can see what is going on then.

Regards, Mark.

On 17 Sep, 2012, at 1:40 PM, Jack West wrote:

...

I lost connectivity today with the car in our garage. We live in a poor cell coverage area and this is not that unusual. However, later today I drove into the city where coverage is excellent and OVMS did not reconnect. After hard reset OVMS was able to connect. If there is any other information I can supply, please let me know. I updated firmware to 1.3.5 a couple days ago.

Jack

On Sep 2, 2012, at 9:03 PM, Mark Webb-Johnson <mark@webb-johnson.net>

...

If the car is in an area of poor / no cellular coverage, then drives out to an area of good coverage, does OVMS connection re-establish? In particular, if you previously saw a situation where you had to unplug-then-plugin the module to hard-reset it, does that still happen? If realise that this will take longer to know, as it was very rare.

_______________________________________________ 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

Will do. On Oct 1, 2012, at 5:33 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

Jack,

Not good. Looking at the logs, the car was online and reporting, but the data from the CAN bus was 'stuck'. The reset of the module restarted it.

I don't think it is hardware/cabling, but it might be worth ensuring everything is tightly connected.

If it happens again, can you try to send a can-bus command (something like wake up car, etc), to see what happens, and let me know the exact time you sent that command?

Regards, Mark.

On 1 Oct, 2012, at 3:16 PM, Jack West <jackduncanwest@gmail.com> wrote:

...

Mark,

Today my wife drove our car from our house (poor coverage) to a town about 60 miles away (good coverage). I used the app to check her SOC when she was there and though the app indicated "live", the data showed she hadn't left home yet. I reset OVMS by the app and soon after was getting proper data. It seems strange that the app would be showing "live", yet the data be incorrect and also still be able to be reset. This was approximately 5PM local time if you care to look at the logs.

Let me know if there is any other info you need. As I did the reset remotely, I do not know what codes the LEDs were showing but this situation might be repeatable as it has now happened (at least I think it was the same thing) on the last two trips from our house into the city.

Best, Jack

On Sep 17, 2012, at 3:50 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

...

Jack,

Do you remember what code the lights were flashing?

I checked mine, and it was bizarre. Green LED was flashing 1 (GPRS up and connected), and red LED was off (no errors found). But, when I connected a PC to the DIAG port (thanks to v2 hardware I can do this now when the box is running), the modem responded just fine but there was no comms between the modem and the PIC. As the LEDs were flashing, the PIC was definitely running. It seems that the RS232 port was just dead on the PIC side. A hardware reset brought it back alive.

I guess I'll have to add a timer to the NET driver code for data last received on the modem port. If nothing is received in a few minutes, then time to reset everything.

Regards, Mark.

On 17 Sep, 2012, at 1:49 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

...

Jack,

Strange, mine did the same (at roughly the same time). Mine still hasn't recovered, but is in good coverage area now.

Without resetting, I'm going to put a serial console on it when I get home tonight. Hopefully I can see what is going on then.

Regards, Mark.

On 17 Sep, 2012, at 1:40 PM, Jack West wrote:

...

I lost connectivity today with the car in our garage. We live in a poor cell coverage area and this is not that unusual. However, later today I drove into the city where coverage is excellent and OVMS did not reconnect. After hard reset OVMS was able to connect. If there is any other information I can supply, please let me know. I updated firmware to 1.3.5 a couple days ago.

Jack

On Sep 2, 2012, at 9:03 PM, Mark Webb-Johnson <mark@webb-johnson.net>

...

If the car is in an area of poor / no cellular coverage, then drives out to an area of good coverage, does OVMS connection re-establish? In particular, if you previously saw a situation where you had to unplug-then-plugin the module to hard-reset it, does that still happen? If realise that this will take longer to know, as it was very rare.

_______________________________________________ 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