- OvmsDev - Open Vehicles

Firmware enhancements -> 1.2.0-rc4
by Mark Webb-Johnson 18 Feb '12

18 Feb '12

I'm planning to work on the car firmware this weekend, hopefully making a 1.2.0-rc4 with the following changes: Fix net_puts_rom, net_puts_ram handling of empty strings. Treat HEATING state as car charging (force charging bit high). Refuse to start charge if charge port not open. Refuse to stop charge if car not charging. Tidy up car_charging and stopped charging alerts. Implement a command 16 to set charge mode and current in the same message. Change logic for commands 10,11,12 and 15 to NOT send battery status message immediately. Change can.c to detect changes in battery status and send that as an immediate status update (this and [6] should improve the UI in the Apps so that when you start/stop a charge, etc, the UI gets updated cleaner). Triple-check notifications for charge stopped vs done. Try to report charge and trip stats to server (if time allows). I'll also double-check the charge mode and limit commands from the prototype iPhone App, and fix anything I find wrong. To help people's testing, given the Android problems, I'm committing my work-in-progress iPhone App to git now. You should be able to use it in the iPhone simulator (or build and run on your phone if you've paid your dues to Apple). Some notes: When the car is plugged in, a graphical representation will appear on the Battery screen. Slide right to charge, left to stop. Note: the UI on updates from the car is not perfect here, and will need the above rc4 firmware fix to be cleaner. Note: the function works, it is just the UI updates that are counter-intuitive (stop charge - ok, stopped, no charging, no stopped!) Tapping on the battery will bring up an screen to allow you to change charge mode and current limit. Note: At the moment, only change one at a time - if you change both only the mode will be set correctly. Firmware support rc4 is required to get this working better. Note; Set higher currents than is permitted by the plug has been UNTESTED. Hopefully the car will handle this gracefully, but please don't do this until I've had a chance to check the behavior. If you are brave/dumb enough to try this, please let me know the result. On the Car screen, tapping on the lock will allow you to lock/unlock the car. The PIN requested is the vehicle pin. Note: Non-US cars have immobilisers fitted. Even if you unlock the car with the App, the alarm will still be enabled and the car can't be driven until you unlock with the key fob. US cars don't have this issue (but are much easier to steal ;-) On the Car screen, tapping on the valet will allow you to enable/disable valet mode. The PIN requested is the vehicle pin. Note: This is cool. Give the car to the valet, walk away and enable valet mode from your phone - no more having to enter the PIN while the guy looks over your shoulder. On the Car screen, tapping on the engine compartment will prompt you if you want to wake up the car. Note; A sleeping car has no water pump (rear-right of the car) noise. An awake car has this noise of water rushing through pipes. Most of the stuff on Cars/i/Control no longer works (as it has been moved away). Sorry, but the iPad version has not yet been done. I'm getting the iPhone stuff working first, then will copy it over. It is a work-in-progress, and may be buggy. Live with it. Enjoy, Mark

2 7

Re: [Ovmsdev] Test RC4
by Mark Webb-Johnson 18 Feb '12

18 Feb '12

Jack, I think this was too quick - the server didn't log any of this. Without an App connected, the car only reports every 10 minutes. With an App, every minute or immediately if the charge state or substate changes. Can you try again, but this time with an App connected. All I really need is (a) start charge, (b) wait for heating to start and for the App to show it (perhaps a minute or two), (c) VDS STOP the charge, (d) let me know the time. What I'm looking for is the by-request state when the charge is stopped and the car goes back to preparing-to-charge state. Another one that many be useful would be to see the transition out of heating into charging. For that, we'd need (a) start charging, (b) wait for heating to start, (c) wait or heating to end, (d) wait for charging to start, (e) let me know the time. Again, with an App connected for as much of the time as possible (or at least connect with the App whenever you see a state change). Thanks, Mark. P.S. I have a log from Michael, that may help. I'll look through it now. On 19 Feb, 2012, at 12:03 PM, Jack West wrote: > Test time. (HK) Action > 11:54. Open charge port, connect cable, slide pilot on, heating begins (7amps) > 11:55. VDS 'stop' > 11:56. VDS 'start' > 11:57. Slide pilot off > > Jack

1 0

Re: [Ovmsdev] little problem/feature needed/debug
by Sonny Chen 18 Feb '12

18 Feb '12

Michael, The bug that that causes the app settings to show SMS only even when a refresh RX is SMS,IP is fixed. But it doesn't explain why some of the push messages are missing. I'll do some tests and get back to you. Sonny

1 0

Can.c logic
by Jack West 18 Feb '12

18 Feb '12

Mark, One possibility that might explain what I saw: In heating substate the car does not turn on b4 of B2 in 0x96. Therefore logic does not see the car as charging when in the heating state so flags are not set, etc. I'll look into this in more detail tonight. Jack

3 12

Re: [Ovmsdev] little problem/feature needed/debug
by Mark Webb-Johnson 18 Feb '12

18 Feb '12

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(a)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(a)lists.teslaclub.hk > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > >

4 15

little problem/feature needed/debug
by William Petefish 16 Feb '12

16 Feb '12

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

2 1

Apple PUSH Notifications Sounds
by Mark Webb-Johnson 16 Feb '12

16 Feb '12

Guys, When we send a PUSH notification to the Apple devices, we play a 'default' sound. It seems that this is not configurable on the phone, and only one (boring) system default sound can be used for all alerts. There is an alternative. We can store a sound file in the App itself, and the phone can use that file for the alert. To do this, we need (a) the sound file, and (b) to specify the sound file (rather than 'default') when sending the alert. Does anyone want to have a go at this? Apple has a document on the format of the file (Linear PCM, MA4 (IMA/ADPCM), µLaw or aLaw format, < 30 seconds in length): Apple; Preparing Custom Alert Sounds Only free sounds, please - nothing copyright or commercially restricted. Remember the alert would normally be for a charging issue. Regards, Mark. P.S. What is the sound of a Tesla Coil alerting? The contractors opening in the car (ground fault)?

1 0

Re: [Ovmsdev] PUSH notifications
by Mark Webb-Johnson 16 Feb '12

16 Feb '12

Jack, Thanks for the feedback. > I sent the hello world message to our car and received push notifications on both my iPad and iPhone. Excellent. I also made a change to the APNS PUSH server code, and it should now be beeping for you. You can turn it off in Settings/Notifications if you don't like it. > The only odd thing was my iPad was in landscape and the notification came in on the side. I'm using the 202 server. Not my problem ;-) Thanks, Mark. P.S. Now PUSH is back working for me (it seemed to be just a developer build problem, and testflight builds are ok), I can get back to testing the Stop charge notification. I don't get cellular signal (or SMS messages) at home - which suggests either the antenna and cellular modem in the car are fantastic to keep getting signal even in the garage, or the iPhone 4S reception sucks - take your pick. On 17 Feb 2012, at 11:47 AM, Jack West wrote: > Mark, > > I sent the hello world message to our car and received push notifications on both my iPad and iPhone. The only odd thing was my iPad was in landscape and the notification came in on the side. I'm using the 202 server. > > Jack > > On Feb 16, 2012, at 3:52 PM, Mark Webb-Johnson <mark(a)webb-johnson.net> wrote: > >> >> I found an issue with the developer build of push notifications under iOS. It was not a code problem - just the wrong certificate specified for code signing. I also found that the PUSH certificates were not installed on the production tmc.openvehicles.com server (64.111.70.40). >> >> So, two questions: >> >> For those of you using the iOS TestFlight release against www.openvehicles.com server, do PUSH notifications work for you? Do you get a notification of charge complete/done when you are not running the App? A simple way to test is to send an SMS to your car "HELLO WORLD" - you should get a PUSH notification back with the content of the unrecognised SMS. Can you test this, and let me know if it is ok? >> >> For those you using the iOS TestFlight release against tmc.openvehicles.com, can you test PUSH notifications now, to see if they work? A simple way to test is to send an SMS to your car "HELLO WORLD" - you should get a PUSH notification back with the content of the unrecognised SMS. Can you test this, and let me know if it is ok? >> >> >> We're getting ready for production now, and need to cross the T's and dot the I's. >> >> Regards, Mark. >> >> _______________________________________________ >> OvmsDev mailing list >> OvmsDev(a)lists.teslaclub.hk >> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

1 0

PUSH notifications
by Mark Webb-Johnson 16 Feb '12

16 Feb '12

I found an issue with the developer build of push notifications under iOS. It was not a code problem - just the wrong certificate specified for code signing. I also found that the PUSH certificates were not installed on the production tmc.openvehicles.com server (64.111.70.40). So, two questions: For those of you using the iOS TestFlight release against www.openvehicles.com server, do PUSH notifications work for you? Do you get a notification of charge complete/done when you are not running the App? A simple way to test is to send an SMS to your car "HELLO WORLD" - you should get a PUSH notification back with the content of the unrecognised SMS. Can you test this, and let me know if it is ok? For those you using the iOS TestFlight release against tmc.openvehicles.com, can you test PUSH notifications now, to see if they work? A simple way to test is to send an SMS to your car "HELLO WORLD" - you should get a PUSH notification back with the content of the unrecognised SMS. Can you test this, and let me know if it is ok? We're getting ready for production now, and need to cross the T's and dot the I's. Regards, Mark.

1 0

Re: [Ovmsdev] 1.2.0-rc3
by Mark Webb-Johnson 14 Feb '12

14 Feb '12

Michael, I'll check the PUSH on 202.52.42.80. The iOS Simulator doesn't work with PUSH notifications. It is an Apple restriction. The PUSH notifications only work with physical devices. Regards, Mark. P.S. Yes, the new GUI looks amazing - thanks to Felix B, not me ;-) > From: "Michael Gerber gerber energie systeme" <michael.gerber(a)gerber.tv> > Subject: AW: [Ovmsdev] 1.2.0-rc3 tire pressure monitoring system > Date: 14 February, 2012 3:49:07 PM GMT+08:00 > To: <ovmsdev-bounces(a)lists.teslaclub.hk> > > > Mark, > > Thanks - moved yesterday evening to dev (202.52.42.80) server – works fine – but sill no push messages > I also tried the iOS Code released on Github with the Xcode iOS simulator – also no push > > The new GUI looks fantastic!!! > > All the best > Michael > > Von: ovmsdev-bounces(a)lists.teslaclub.hk [mailto:ovmsdev-bounces@lists.teslaclub.hk] Im Auftrag von Mark Webb-Johnson > Gesendet: Dienstag, 14. Februar 2012 03:44 > An: OVMS Developers > Betreff: Re: [Ovmsdev] 1.2.0-rc3 tire pressure monitoring system > > Michael, > > Thanks for the feedback. > >> - my EU 2.5 Roadster Sport have no tire pressure monitoring system installed, the iOS App shows invalid temp an pressure values > > Seems to be an invalid tpms record (dating back to 2012-02-08 15:35:58). I have cleared it. > > > - Not able to receive any PUSH Messages via the iOS App, maybe a configuration or server (64.111.70.40) issue … > > Yes, that server has not been provisioned for PUSH yet. The main 202.52.42.80 server should be ok (and I think you've switched to that one). > > > - I enabled the CAN write Feature by sending “FEATURE 15 1” SMS command – but how to check if it’s enabled? > > > The Android App on the store supports this today. The iOS App is a little behind (but will look better when done) - I should have a testflight release later this week. > > Regards, Mark. > > On 14 Feb 2012, at 12:39 AM, Michael Gerber gerber energie systeme wrote: > > > Hi all, > > yesterday I flashed the new 1.2.0-rc3 firmware, while testing I found some issues: > > - my EU 2.5 Roadster Sport have no tire pressure monitoring system installed, the iOS App shows invalid temp an pressure values > > <image001.jpg> > > - Not able to receive any PUSH Messages via the iOS App, maybe a configuration or server (64.111.70.40) issue … > > - I enabled the CAN write Feature by sending “FEATURE 15 1” SMS command – but how to check if it’s enabled? > > But hey – great work! > > mit sonnigen grüßen vom kaiserstuhl, with sunny regards > > Michael Gerber > Geschäftsführer > > <image003.jpg> > > > gerber energie systeme gmbh > Coulonger str. 8 > > 79346 Endingen, Germany > > Telefon: +49 (0) 7642 92118-22 > Telefax: +49 (0) 7642 92118-18 > > Mail michael.gerber(a)gerber.tv > http://www.gerber.tv/ > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > This message may contain confidential or privileged > information and is intended only for the use of the > addressee named above. If you are not the intended > recipient of this message, you are hereby notified > that you must not use, copy, disclose or take any > action based on this message or information herein. > If you have received this message by error, please > advise the sender immediately and delete this message. > Thank you for your cooperation. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > _______________________________________________ > OvmsDev mailing list > OvmsDev(a)lists.teslaclub.hk > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > > >

1 0