- OvmsDev - Open Vehicles

Re: [Ovmsdev] OvmsDev Digest, Vol 32, Issue 5
by Aatheus 24 Sep '14

24 Sep '14

On 09/24/2014 09:00 PM, ovmsdev-request(a)lists.teslaclub.hk wrote: > Message: 4 > Date: Thu, 25 Sep 2014 09:51:47 +0800 > From: Mark Webb-Johnson <mark(a)webb-johnson.net> > Subject: Re: [Ovmsdev] CFG commands on RT_Production > To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> > Message-ID: <DB4A9580-13F5-4343-A098-CB5463C2A3D9(a)webb-johnson.net> > Content-Type: text/plain; charset=us-ascii > > Jeff, > > It should be sufficient, for the Nissan Leaf, to use the V2_EXPERIMENTAL build and select NL and the vehicle type. > > You also need to make sure you've got the new style Nissan Leaf OBDII cable (with the EV bus CAN pins, not the CAR CAN bus). > > Regards, Mark. Mark, I tried recompiling because I see that the V2_EXPERIMENTAL firmware is from 7 months ago, but the vehice_nissanleaf.c was last modified in July. I had to exclude all of the other vehicles from the build, or I got the "cannot fit" linker error. I did not know about the custom LEAF ODBII cable. Was it recently added to the Fasttech site? I could have sworn that it wasn't there a month ago. Thanks, -Jeff

2 1

Re: [Ovmsdev] CFG commands on RT_Production
by Aatheus 24 Sep '14

24 Sep '14

Thank you for posting this info! I was able to get the experimental Nissan Leaf code to compile and (sort of) do useful things now. The configuration that I had to use was V2_EXPERIMENTAL. I cloned it to be V2_EXPERIMENTAL_LEAF. I set these flags: OVMS_CAR_NONE OVMS_HW_V2 OVMS_DIAGMODULE OVMS_INTERNALGPS OVMS_NISSANLEAF OVMS_LOGGINGMODULE OVMS_POLLER OVMS_ODBII OVMS_TRACK I also excluded acc.c and all of the other vehicle source files except for these: vehicle_nissanleaf.c vehicle_none.c vehicle_odbii.c vehicle_track.c vehicle.c Now the hex file builds and the OVMS v2 module is able to give me a different inaccurate battery percentage (0% instead of 80%). Progress? :) -Jeff Orr Message: 2 Date: Mon, 22 Sep 2014 20:02:47 +0200 From: Michael Balzer <dexter(a)expeedo.de> Subject: Re: [Ovmsdev] CFG commands on RT_Production To: ovmsdev(a)lists.teslaclub.hk Message-ID: <54206447.5010806(a)expeedo.de> Content-Type: text/plain; charset="windows-1252"; Format="flowed" (snip) To compile yourself you need to define these (and only these) compiler flags: OVMS_CAR_NONE OVMS_CAR_RENAULTTWIZY OVMS_HW_V2 OVMS_DIAGMODULE OVMS_INTERNALGPS OVMS_TWIZY_BATTMON OVMS_TWIZY_CFG ...and you need to manually exclude source files "acc.c", "logging.c" and all other "vehicle*.c" from the build, because otherwise... (snip)

2 1

OVMS not connecting
by Jack West 08 Sep '14

08 Sep '14

My module has been on the fritz for about two weeks after working for a long time. Red led flashes 8 times. "GPRS Network initialization failed". I have tried unplugging the module to reboot. My phone plan still has a balance. The blue led is slowly flashing. I replaced the cable a few months ago when I thought the unit was acting flakey and that seemed to help for a while, ie the module stayed connected more reliably. What should my next step be in troubleshooting? Thanks, Jack

1 0

SIM Card recommendation for Sweden
by Nikolay Shishkov 01 Sep '14

01 Sep '14

Hi, For those of you in Sweden and looking for a working SIM card solution for the OVMS module - I have been using the Telenor M2M prepaid cards with very good success. I got mine from http://www.m2mbutiken.se/ . They should be available at other places too... Nikolay

1 0

Leaf EV CAN messages
by Jeremy Whaling 21 Aug '14

21 Aug '14

Hi All- Over the last few days a few of us on the mynissanleaf forum have been working on getting the TCU (telematics module) CAN messages for the various modes of operation (remote CC, status, charge). Here's what we know now: To wake up the VCM (Main controller), the TCU sends a msgID of 68C on the EV CAN bus with one byte of 00. On 2013 and newer models wake up solely on the CAN message. For 2011 or 2012 models the TCU will bring a logic line high that connects to the VCM briefly as well to wake it up. Page 64 of the "AV" section of the 2012 service manual shows the pinout of the TCU. You will need to splice into Pin 11 (light green? wire) on the large connector going to the TCU and make an appropriate circuit to pull it high briefly when the OVMS module sends the 68C message. When doing non "remote charge" testing you might be able to hit the charge override button (which uses another line to wake the VCM) then send 68C. I think that might work for testing. :-) Once the VCM is awake it looks to the TCU status message to see what's up. The status message has a msgID of 56E and the first byte determines the status (the 6 other bytes are FF). The 56E message repeats every 100ms whenever the EV CAN bus is active. The various modes are: hex binary state 46 01000110 status 86 10000110 idle 4E 01001110 cc on 56 01010110 cc off 66 01100111 remote charge That's all we have so far. Haven't tried pulling the TCU yet and duplicating it's messages but I'm reasonably confident this is all there is to it as far as remote activation. For more info, see this Google Doc with the Leaf's CAN message info here <https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy…> For the latest developments Leaf CAN wise, check out the thread on MNL here <http://www.mynissanleaf.com/viewtopic.php?f=44&t=4131&start=390> Take care, Jeremy

3 5

Re: [Ovmsdev] Fwd: CFG PRE: ERROR
by Michael Balzer 16 Aug '14

16 Aug '14

Hi Lionel, nice words, you're welcome :-) Regards, Michael Am 16.08.2014 20:27, schrieb Lionel Saint Denis: > > Hi Michael, > > Thank you for your quick support. > I found the solution by myself but thank you. > > Congratulations to you and the whole team. Your product changed my life. > > Cordially > > Le 16 août 2014 19:21, Michael Balzer <dexter(a)expeedo.de> a écrit : > > Hi Trig, > > for safety reasons, pre-operative mode is only allowed if the > Twizy is not in "GO" state (and not moving and not in D/R gear). > > So turn on the Twizy but do not switch to "GO", then you can use > "CFG PRE" and macro commands needing the pre-op mode. > > Reason for this is to avoid the risk of some delayed SMS switching > your Twizy to pre-op while you're on the road. > > Regards, > Michael > -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

1 0

tmc.openvehicles.com
by Nigel Jones 14 Aug '14

14 Aug '14

I have OVMS installed in my leaf which is up & configured with SMS access. I've also setup the GPRS connection and configured the server as 64.111.70.40 with password MODPASS I can login to http://www.openvehicles.com/ as user 624 with username OPENUSER and pass OPENPASS . I have one car registered with vehicle id VEHICLE In the android ovms app I fill in the parameters as Vehicle Id: $VEHICLE Vehicle Label: leaf OVMS Server Password: $OPENPASS OVMS Module Password $MODPASS server: tmc.openvehicles.com Where have I gone wrong as I keep getting an error to check ovms server address or vehicle id/password Thanks Nigel. -- ---- Nigel Jones

2 1

OVMS provisioning not working to US?
by Aatheus 08 Aug '14

08 Aug '14

I am exciting. I have gotten the OVMS server up and running on my personal box, and the OVMS v2 module is actively logging data to it! I am able to pull data from the Android app, and it's (mostly) correct. Very exciting when it works at last! I would love to contribute some messages from my 2014 LEAF's CAN bus to help with getting the SoC display working and other controls working. Which brings me to my question. Is the provisioning server at http://www.openvehicles.com/user restricted to EU numbers only? I tried my +1408xxxyyyy and my 1408xxxyyyy numbers, and even after 24 hours, no SMS messages were ever delivered. I ended up having to manually input the server IP, shared secret, APN and other info over serial connection. I even tried sending messages to my cell phone #, and also no SMS even after 24 hours. Very odd. Thanks, -Jeff Orr

1 0

Twizy release 3.4.0
by Michael Balzer 07 Aug '14

07 Aug '14

https://github.com/openvehicles/Open-Vehicle-Monitoring-System/commit/efe84… - Automatic recuperation level adjustment from BMS max power reading - SEVCON auto-login retries on switch-on - Power map debug output optimized - CFG POWER now allows power_low param up to 139% (same level as high=130%) - Send power statistics only if 25+ Wh used - Collect power (/current) min/max values per GPS section - Preop mode safety check in configmode() to protect against delayed SMS - Accel/decel stats now based on running average of speed changes - Client scripts now generate CSV header lines Note: had to exclude Tesla Roadster specific CAN data from diag module to get space. If other cars need these, a new preprocessor switch can be introduced. - Bugfix: RT-PWR-Log speed/accel stats output fixed for 0 distances (charge/onoff) - Now checking for carbits vehicle alert & (new) info suppression (info suppression applies to trip reports) Framework: - Added car bits flag FEATURE_CB_SVINFOS (0x10): 1 = suppress vehicle informational notifies (currently only used on Twizy) Regards, Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

2 2

Re: [Ovmsdev] OvmsDev Digest, Vol 31, Issue 1
by Aatheus 01 Aug '14

01 Aug '14

Mark, Fair point on the diag port being more of a 'power user' input. Regarding the SIM card, I was not able to get the card to register on the AT&T or T-mobile networks using my unlocked quad band phone. The registration timed out. It may in fact be my SIM. And no, the GSM lock is not set on the module. I was able to get some output using the 'diag' command. The signal strength bounces between 0 and 24 every few minutes. Also, the VIN is reported is random characters, plus part of the SIM's serial. This is on a 2014 LEAF S trim (US). Thanks, -Jeff On 08/01/2014 09:00 PM, ovmsdev-request(a)lists.teslaclub.hk wrote: > ------------------------------ > > Message: 2 > Date: Fri, 01 Aug 2014 10:54:52 +0200 > From: Michael Balzer <dexter(a)expeedo.de> > Subject: Re: [Ovmsdev] OvmsDev Digest, Vol 30, Issue 12 > To: ovmsdev(a)lists.teslaclub.hk > Message-ID: <53DB55DC.9070706(a)expeedo.de> > Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" > > Jeff, > > I think the diag port is not something a normal user should be > confronted with. The OVMS setup and troubleshooting is already quite > complex for a simple user. If you're able to use a serial port, you're > able to find and read the tech docs -- just my 2 cents. > > Now for your trace: is a GSM lock configured (parameter #13)? If so, try > without. > > Also, does the SIM work correctly in a mobile phone? > > Regards, > Michael > > > Am 01.08.2014 06:46, schrieb Aatheus: >> Mark, >> >> Thank you for the info. Can the serial port parameters get added to the >> helpme page? The info is not findable anywhere on the page. I did find >> it in the development PDF, but it was hard to find! >> >> I managed to get serial access to the OVMS board, and it looks like the >> data call is repeatedly failing. I verified that my GeoSIM card has $15 >> balance on it. Is my SIM card screwed up? I activated the SIM on the >> GeoSIM site, and I think it's set up ok. >> >> RDY >> >> +CFUN: 1 >> >> +CPIN: READY >> >> +PACSP: 1 >> >> +CREG: 0 >> >> +CREG: 2 >> >> Call Ready >> >> GPS Ready >> AT >> >> OK >> AT+CGPSPWR=1;+CGPSRST=0;+CSMINS? >> >> +CSMINS: 0,1 >> >> OK >> AT+CCID;+CPBF="O-";+CPIN? >> >> (SERIAL OBSCURED) >> >> +CPIN: READY >> >> OK >> AT+IPR?;+CREG=1;+CLIP=1;+CMGF=1;+CNMI=2,2;+CSDH=1;+CIPSPRT=0;+CIPQSEND=1;+CLTS=1;E0 >> >> +IPR: 9600 >> >> OK >> >> ERROR >> >> +CREG: 3 >> >> +CREG: 0 >> >> OK >> >> +CSMINS: 0,1 >> >> OK >> >> (SERIAL OBSCURED) >> +CPIN: READY >> >> OK >> >> +IPR: 9600 >> >> OK >> >> ERROR >> >> +CREG: 3 >> >> OK >> >> +CSMINS: 0,1 >> >> OK >> >> (SERIAL OBSCURED) >> >> +CPIN: READY >> >> OK >> >> +IPR: 9600 >> >> OK >> >> ERROR >> >> >> >> _______________________________________________ >> OvmsDev mailing list >> OvmsDev(a)lists.teslaclub.hk >> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

1 0