[Ovmsdev] little problem/feature needed/debug
Michael Stegen
michael at stegen.com
Sat Feb 18 06:01:57 HKT 2012
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 at gmail.com <mailto:william.petefish at 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 at gmail.com <mailto:william.petefish at 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 at webb-johnson.net <mailto:mark at 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 at webb-johnson.net <mailto:mark at 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 at webb-johnson.net
>>>>>> <mailto:mark at 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 at lists.teslaclub.hk
>>>>>> <mailto:OvmsDev at lists.teslaclub.hk>
>>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> OvmsDev mailing list
>>>>> OvmsDev at lists.teslaclub.hk
>>>>> <mailto:OvmsDev at lists.teslaclub.hk>
>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> OvmsDev mailing list
>>>>> OvmsDev at lists.teslaclub.hk
>>>>> <mailto:OvmsDev at lists.teslaclub.hk>
>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> OvmsDev mailing list
>>>> OvmsDev at lists.teslaclub.hk <mailto:OvmsDev at 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 at lists.teslaclub.hk
>>> <mailto:OvmsDev at lists.teslaclub.hk>
>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>
>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk <mailto: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
--
Stegen Electronics
Kwartslaan 95
3162 RD Rhoon
The Netherlands
Tel: +31 10-5016960
www.stegen.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20120217/dbdfd72d/attachment.htm>
More information about the OvmsDev
mailing list