[Ovmsdev] little problem/feature needed/debug

[William Petefish]

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>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
> > 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
>> 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/20120217/6804dcfa/attachment.htm>