[Ovmsdev] 1.3.1

Wed Sep 5 11:16:25 HKT 2012

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 at 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 at gmail.com> wrote:
>> 
>>> Thanks for the clarification.
>>> 
>>> William
>>> 
>>> On Sep 3, 2012 9:22 PM, "Mark Webb-Johnson" <mark at 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 at 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 at 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 at 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 at 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 at lists.teslaclub.hk
>>>>>> >> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>>>> >>
>>>>>> >
>>>>>> >
>>>>>> > _______________________________________________
>>>>>> > OvmsDev mailing list
>>>>>> > OvmsDev at lists.teslaclub.hk
>>>>>> > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>>>> 
>>>>>> _______________________________________________
>>>>>> OvmsDev mailing list
>>>>>> OvmsDev at lists.teslaclub.hk
>>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>>>> 
>>>>>> _______________________________________________
>>>>>> OvmsDev mailing list
>>>>>> OvmsDev at lists.teslaclub.hk
>>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> OvmsDev mailing list
>>>>> OvmsDev at lists.teslaclub.hk
>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> OvmsDev mailing list
>>>>> OvmsDev at lists.teslaclub.hk
>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>> 
>>>> 
>>>> _______________________________________________
>>>> OvmsDev mailing list
>>>> OvmsDev at lists.teslaclub.hk
>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>> 
>>>> _______________________________________________
>>>> OvmsDev mailing list
>>>> OvmsDev at lists.teslaclub.hk
>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>> 
>>> 
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.teslaclub.hk
>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>> 
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.teslaclub.hk
>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
> 
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20120904/01ac1cc1/attachment.htm>