Michael,
I'll first need cmd codes for...
DEBUG RANGE CA For vehicle specific cmds you wrote earlier we could just use arbitrary codes 200+, can I still do so or do you want to directly assign standard codes for some of them?
I think we can say everything in the range 200-255 is private, per vehicle module. Allocate them as you require.
...plus a new common code for "ALERT", if you agree on routing the net_msg_alert() function through the dispatcher as well to allow vehicle control over this.
Can you explain more what you require here? Regards, Mark. On 19 Nov, 2012, at 3:32 AM, Michael Balzer <dexter@expeedo.de> wrote:
Am 18.11.2012 13:38, schrieb Mark Webb-Johnson:
I've just pushed my last set of changes. It seems ok from my end now. The code runs and sms commands function as expected. I've added a capabilities message that is sent car->server->apps and will be useful to tailor the app functions to what the car can do.
As everything so far seems to be working pretty well, I'll next add the msg cmd handlers for my commands, to see how that fits.
I'll first need cmd codes for...
DEBUG RANGE CA
...plus a new common code for "ALERT", if you agree on routing the net_msg_alert() function through the dispatcher as well to allow vehicle control over this.
For vehicle specific cmds you wrote earlier we could just use arbitrary codes 200+, can I still do so or do you want to directly assign standard codes for some of them?
...if some cmd later becomes standard, we can just add that code to the dispatcher switch: case 7: // standard cmd: DEBUG case 200: // obsolete specific cmd: DEBUG do_alert(...); ...at least if the arguments match the standard :-)
Regards, Michael
-- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26 <dexter.vcf>_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev