Re: [EVDL] Nissan Leaf key: $300! Yikes

2018-10-14 Thread Tom Parker via EV

On 14/10/18 10:12, EVDL Administrator via EV wrote:


On 14 Oct 2018 at 7:57, Tom Parker via EV wrote:


My 2016 Leaf has remote charge port opening -- the key fob has a 3rd
button, if you hold it down for about 2 seconds, the door opens.

Darned if I can see the point of this.  How hard could it be to open the
charging port door with your left hand, when you're standing there with the
charging connector in your right hand?  (Or vice versa.)

Maybe I'm missing something, but it seems like I'd be more trouble to get
the keys out and find the right button.  And then you have to hold it down
for a while.  Nuisance.


Like the other Tom, I don't use it very often but it is useful if you 
forget to open the charge port before getting out of the car and the 
keys are handy. If the keys are buried in a bag I find it 's easier to 
bring the bag to the car and open the door and press the button to open 
the charge port rather than find the keys and press the button on the key.



OTOH, inside release fuel filler doors make sense.  They help prevent fuel
theft.  But with an EV, who's gonna steal your electrons?


Agreed, there isn't a major need to lock the charge port, except perhaps 
to reduce the vandalism attack surface. Other cars do it better than the 
Leaf, for example the i3 charge port opens when you push it, but it 
still locks with the car which may or may not be necessary.


___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)



Re: [EVDL] Nissan Leaf key: $300! Yikes

2018-10-13 Thread Tom Parker via EV

On 14/10/18 07:46, Cor van de Water via EV wrote:


I meant on the key fob. For the 2011 and 2012 there is only a dash handle
to open the door latch.
The 2013+ has an electric latch opener, so theoretically it can be opened
remotely, but the functions on the wireless interface are severely limited.
Cor.


My 2016 Leaf has remote charge port opening -- the key fob has a 3rd 
button, if you hold it down for about 2 seconds, the door opens.


___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)



Re: [EVDL] Leaf battery pack overheating due to depth of discharge.

2017-06-21 Thread Tom Parker via EV
Lawrence, 

Is this a 30kWh leaf? 

We've seen that they will accept charge much faster than the 24kWh leaves, 
maintaining 50kW for most of the charge to 80%. This will put a lot more I^2R 
heating into the battery than charging slower. The 24kWh cars average under 
25kW for a charge to 80%.

How hot is 5 and 9 bars?

On Jun 22, 2017 9:45 AM, Lawrence Rhodes via EV wrote: > > After driving 135 
miles down to 13% charging back up to 85% caused the pack to go from 6 bars to 
9.  Today the plan is to try to stay above 50%.  So far so good.  The pack 
hasn't exceeded 6 bars. This is in hotter temperature than yesterday.  So 
ambient temperature doesn't seem a big factor. It is large depth of discharge 
then a fast charge.  Now in Santa Barbara.  Going to Rancho Jarupa near 
Riverside.  Lawrence Rhodes > > Sent from my MetroPCS 4G LTE Android device > 
On Jun 21, 2017 1:05 PM, via EV wrote: > > > > Send EV mailing list submissions 
to > > ev@lists.evdl.org > > > > To subscribe or unsubscribe via the World Wide 
Web, visit > > http://lists.evdl.org/listinfo.cgi/ev-evdl.org > > or, via 
email, send a message with subject or body 'help' to > > 
ev-requ...@lists.evdl.org > > > > You can reach the person managing the list at 
> > ev-ow...@lists.evdl.org > > > > When replying, please edit your Subject 
line so it is more specific > > than "Re: Contents of EV digest..." > > > > > > 
Also, please be careful not to append the entire digest to your reply. Many 
mail systems do this by default. Trim or delete the digest text from the bottom 
of your message, and quote only the parts to which you're replying. > > > > > > 
> > Today's Topics: > > > >    1. EVLN: EV-newswire posts for 20170621 
(brucedp5 via EV) > > > > > > 
-- > > > > 
Message: 1 > > Date: Wed, 21 Jun 2017 05:52:57 -0700 (PDT) > > From: brucedp5 
via EV > > To: ev@lists.evdl.org > > Subject: [EVDL] EVLN: EV-newswire posts 
for 20170621 > > Message-ID: <1498049577620-4687111.p...@n4.nabble.com> > > 
Content-Type: text/plain; charset=UTF-8 > > > > > > > > 
http://electric-vehicle-discussion-list.413529.n4.nabble.com/EVLN-How-Lotus-Evora-EV-performs-flat-out-on-the-track-r-125mi-ts-172mph-v-td4687110.html
 > > EVLN: How Lotus Evora EV performs flat-out on the track r:125mi ts:172mph 
> > (v) > > Watch a Lotus Evora With a Tesla's Electric Motor Set Silent Lap 
Times ... > > All of that power and instant electric torque make for a 
seriously quick > > track car, as the guys from Speed Academy find out ... > > 
> > 
http://electric-vehicle-discussion-list.413529.n4.nabble.com/EVLN-1-3k-Boosted-e-skateboards-sell-past-their-voluntary-pack-recall-r-7mi-ts-22mph-td4687109.html
 > > EVLN: $1.3k Boosted e-skateboards sell past their voluntary pack recall > 
> r:7mi ts:22mph > > Boosted electric skateboard maker seeks a reboot > > ... 
(redesigned packs keep water out and from short-circuiting their bms, > > 
preventing overheating) ... > > > > 
http://electric-vehicle-discussion-list.413529.n4.nabble.com/EVLN-Lyft-s-murky-plan-gt-an-auton-Bolt-EV-fleet-charged-w-renewable-electricity-td4687108.html
 > > EVLN: Lyft's murky plan> an auton (Bolt) EV fleet charged w/ renewable > > 
electricity > > Lyft just unveiled an aggressive plan to reduce its carbon 
emissions ... > > The ride-hailing service said all of its electric, autonomous 
vehicles will > > only use electricity generated by clean energy sources, 
starting ...  in > > Boston later this year ... > > > > + > > 
http://electric-vehicle-discussion-list.413529.n4.nabble.com/A-2nd-L2-WSU-Pullman-WA-gt-not-the-dual-L3-DC-EVSE-that-is-needed-td4687106.html
 > > A 2nd L2 @WSU Pullman-WA> (not the dual L3 DC EVSE that is needed) > > 
Electric car charging station to be installed in Pullman > > Palouse already 
has one electric car charging station but this fall a 2nd > > one is going in 
... 'We do know there are more EVs being purchased every > > day' ... > > > > 
http://electric-vehicle-discussion-list.413529.n4.nabble.com/EVangel-Lough-is-holding-court-like-xXx-in-Issaquah-WA-td4687107.html
 > > EVangel Lough is holding court like xXx in Issaquah-WA > > Batteries 
included! Seattle Electric Vehicle Association leads the charge > > On a sunny 
day in May, Steven Lough is holding court among the gathered ? > > > > > > > > 
> > http://evdl.org/evln/ > > For all EVLN EV-newswire posts > > > > > > 
{brucedp.neocities.org} > > > > -- > > View this message in context: 
http://electric-vehicle-discussion-list.413529.n4.nabble.com/EVLN-EV-newswire-posts-for-20170621-tp4687111.html
 > > Sent from the Electric Vehicle Discussion List mailing list archive at 
Nabble.com. > > > > > > -- > > > > Subject: Digest 
Footer > > > > ___ > > 
EV@lists.evdl.org > > For general EVDL support, see http://evdl.org/help/ > > 
http://lists.evdl.org/listinfo.cgi/ev-evdl.org > > > > > > 

Re: [EVDL] Nissan Leaf CAN Bus Man in the Middle

2017-03-14 Thread Tom Parker via EV

On 14/03/17 07:07, Bill Dube via EV wrote:


Outstanding work Tom.
Not many folks have the ability (or patience) to tackle this job, but 
a lot of us will use this. Makes the Leaf battery module so much more 
useful as a functional unit.


To be clear my contribution so far is only

* writing a simple tool to explore how the system behaves when messages 
are modified
* writing a configuration file for kayak and a wireshark dissector to 
decode some of the can bus messages
* finding the car mostly works when the battery can send messages to it 
and it cannot send messages to the battery
* discovering which signals the leaf instrument cluster is using for the 
capacity, temperature and state of charge displays


The work to decipher enough of the Leaf BMS to use it outside the car 
was done by others.

___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Read EVAngel's EV News at http://evdl.org/evln/
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)



Re: [EVDL] Nissan Leaf CAN Bus Man in the Middle

2017-03-12 Thread Tom Parker via EV

On 13/03/17 04:39, Jay Summet via EV wrote:
The next time I use a Leaf pack on an EV I want to be able to just 
plug it in "unmodified" and make use of the existing BMS and CAN 
interface, it's good to know that people are making good progress on 
the "auto" side of this.


The BMS is already understood mostly enough to use in a conversion. 
While it evidently logs an error when the car is missing, it's quite 
happy to tell you the battery current, voltage, remaining capacity and 
cell voltage levels. There are some more signals that would be a good 
idea to follow but I don't know if anyone has identified them:


* High voltage discharge permit signal
* System main relay ON permit signal
* Insulation resistance signal
* Li-ion battery dischargeable power signal

___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Read EVAngel's EV News at http://evdl.org/evln/
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)



[EVDL] Nissan Leaf CAN Bus Man in the Middle

2017-03-12 Thread Tom Parker via EV
I wrote a man in the middle for the leaf battery communication. It uses 
can4python and Kayak's kcd format to describe the signals. It probably 
only works on Linux. Source code is here 
https://carrott.org/git/leaf-can-utils.git


It decodes all the messages received on one interface (from the battery) 
into signals, lets me change their values, and then re-encodes them back 
into the can bus format, recalculates the new checksum when necessary 
and sends them out the other interface (to the car).


Yesterday I spent some time testing it on a Gen 1 leaf at 
https://bluecars.nz


We cut the can bus wires inside the battery box, just after they go 
through the water proof connector to the outside and connected about 1 
metre of thin figure 8 wire to each side of the cut. This let us access 
the bus on the car and the bus on the battery while the battery was 
plugged in under the car. It's possible to get enough slack in the 
internal battery loom to feed the connector all the way through the 
machined hole and make room for some extra wires to pass through.


With the two pairs connected together, the car behaved normally, going 
into ready and spinning the wheels.


The BMS module terminates the bus so we connected a termination resistor 
to the car side of the cut and used termination on the CAN interface 
talking to the battery. We plugged the other end of the man in the 
middle to the OBD2 port and didn't use termination.


The MitM just worked.

The car is very tolerant of errors on the CAN bus. You can stop the 
battery messages and it goes into turtle mode and all the battery info 
disappears off the instrument cluster. When you re-start the battery 
messages it goes back to normal mode and the battery info reappears. 
Start-up is quite critical, if you don't let the battery send it's start 
up messages the car doesn't go into ready mode. The car never shut down 
or went into a permanent turtle mode while I was messing with data on 
the bus -- it always went back to normal mode if I restored the 
unmodified messages flow from the BMS. I modified the data in nearly 
every field to see what would happen.


The car will go into ready and turn the wheels even when it cannot send 
messages to the battery. This means the startup sequence doesn't involve 
a car to battery handshake, even if the car is expecting some startup 
messages from the battery within a time window. The "check engine" light 
comes on and it does record some DTCs:
* P3180 (EVC-249) VCM detects an error signal that is received from LBC 
via CAN communication for 0.02 seconds or more.
* P3183 (EVC-250) After a lapse of 0.3 seconds from M/C RELAY ON, the 
following state remains for 2.8 seconds or more: LBC's calculation 
result to the VCM-set example question is incorrect.


My MitM only works in one direction (from the battery to the car) and it 
turns out my CAN bus setup wouldn't let two programs play together, so 
when I started a CAN repeater (candump -b) to copy data from the car to 
the battery I got corrupted frames and no buffer space errors. I'm going 
to make the MitM work in both directions to resolve this.


If you play a different car's battery messages into this car, it does 
not go into ready. I didn't spend much time on this and I didn't write 
code to start the BMS messages at the right time, I just started playing 
the recording of a running BMS and switched the car on. One experiment 
that I should have tried was to start the car with it's real battery and 
then switch to messages recorded from a different car. There are some 
new DTCs when you try to start a the car while playing messages recorded 
from another car including


* P3102 Li-ion Battery ID Registration must be performed if the Li-ion 
battery controller or VCM is replaced.


The next experiment is to swap in a BMS module from another car.

I figured out some more of the BMS protocol by messing with the data and 
seeing how the car reacted.


The Fuel Gauge display on the instrument cluster is powered by the GIDs 
signal (the first 10 bits of 0x5BC), not the state of charge signal 
(first 10 bits of 0x55B). I guess it knows how many GIDS is "full" 
because the battery will have fewer gids and still read full as it ages.


0x5BC bits 36-39 (ie the high nibble of the 5th byte) somehow effects 
the Fuel Gauge, lower numbers mean more bars, all other things being the 
same. Maybe this is used to calculate how many GIDs each bar is worth? I 
haven't explored this.


The battery capacity gauge (the bars outside the fuel gauge) is 
controlled by a muxed field, when 0x5BC bits 32-35 (ie the low nibble of 
the 5th byte) is 0x3, 0x5BC bits 16-19 (ie the low nibble of the 3rd 
byte) contains the capacity bars. I haven't yet used the mux field 
support in the kcd format to express this -- can4python doesn't support 
it so I had to hand code it. The cluster does not remember the capacity 
-- changing this value directly manipulates the number of bars 
displayed, the 

Re: [EVDL] Anyone interested in 2015 Leaf drivetrain or interior/exterior/suspension parts?

2017-01-27 Thread Tom Parker via EV

On 27/01/17 13:36, Collin Kidder via EV wrote:


Any logs anyone could send me from a Leaf would be great. But, I might
be on to something. Byte 4 (the fifth byte if you start counting at 0)
is always a constant value for a given car. It stays the same across
all 0x5C0 frames, it stays the same whether driving or charging. Every
vehicle I've got a capture from has a unique byte here that never
changes with any captures from that car no matter what else the car is
doing. Pretty much all of the rest of the bytes change as you charge
or discharge. I think what might be happening is that this byte is a
sort of identifier that the rest of the system uses to see whether the
pack is the same one it last knew. 256 unique values might not seem
like a lot but that means that your odds of getting a pack with the
same byte as your old pack is 1/256 or less than 0.5% - not so likely.
One way to test this would be to set up a man in the middle
configuration and then change that byte and see if it makes the car
puke. Or, take a car with a replaced pack and try to change the
reported byte from the new LBC to the reported byte from the old LBC
and see if the car then wants to work better.


I don't see a constant here. With the exception of one capture, each 
capture from my car has a single value in byte 4 but it is decreasing 
(except once when it went down and up) slowly over the last year or so 
for which I have data:


Each line represents one capture and has the following format
byte_number value_in_hex:count_in_decimal

4 84:7
4 84:12
4 84:14
4 84:80
4 84:252
4 84:128
4 84:10
4 84:14
4 82:1607
4 82:40
4 82:22
4 82:91
4 80:40
4 80:4332
4 7e:14
4 7e:53
4 7c:531 fe:1
4 7c:36
4 7c:19
4 7c:6
4 7a:72
4 7c:8
4 7c:22
4 7c:8
4 7c:28
4 7c:30
4 7c:1
4 7a:40
4 7a:165
4 7a:38
4 7a:54

The exception was captured during remote climate control, and I have 531 
frames with 7c with one frame containing fe about 2/3 of the way through 
the capture:


1572272017-01-07 08:38:05.031301LBC 0x5c016STD: 
0x05c0   c0 72 74 00 7c d4 00 00
1575332017-01-07 08:38:05.531215LBC 0x5c016STD: 
0x05c0   00 fe fe 00 fe fc 00 00
1572272017-01-07 08:38:05.031301LBC 0x5c016STD: 
0x05c0   c0 72 74 00 7c d4 00 00

I have 2 short captures made on the same day from a Gen 2 and there it 
alternates between two values:


4 ba:5 c0:2
4 ba:8 c0:4
___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Read EVAngel's EV News at http://evdl.org/evln/
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)



Re: [EVDL] Anyone interested in 2015 Leaf drivetrain or interior/exterior/suspension parts?

2017-01-26 Thread Tom Parker via EV

On 27/01/17 07:29, Cor van de Water via EV wrote:

Also, the LBC validation happens without disconnecting the aux battery.
I know for sure as I never disconnect the 12V battery and when I swapped
my pack for a complete replacement pack from Washington State, the
yellow light on the dash came on and my Leaf was in Limp mode while I
only disconnected the (non-energized, due to the contactors in the pack)
HV lines and the control bus.
Just wheeling the original pack back under my Leaf and swapping the
connectors removed the Limp mode, so I know for a fact that the Leaf
validates the battery upon pressing the power button while the aux
battery is connected continuously, so it seems that you were looking at
the wrong thing.
Probably a trace of the EV bus as soon as the power button is depressed
(when a *lot* of communication is happening) will tell the story.
You may start the trace as soon as the brake is pressed.


Thank you for this information Cor!

I have many captures of my car's startup on the EV Bus and unless my 
hardware misses the important frames, I don't see anything special at 
startup. 0x603 is sent once, is the first frame sent and always with 
payload 00. A number of frames are sent with lots of bits set which 
later contain valid data - for example the first couple of frames from 
the LBC:


1 2017-01-26 21:47:24.907267CAN16STD: 
0x0603   00
8 2017-01-26 21:47:24.993307VCM Info   16STD: 
0x01f2   08 64 00 00 00 01 01 06
652017-01-26 21:47:25.139218LBC Battery V/A16STD: 
0x01db   7f e0 ff c6 00 00 00 de
662017-01-26 21:47:25.140191LBC 0x1dc  16STD: 
0x01dc   ff ff ff ff 1f ff fc 6b

And I can see the VCM go through it's startup sequence (in 0x1f2 byte 
5). However all the frames other than 0x603 are sent more than once per 
second.


I'll capture startup from some more cars, identify which bytes are 
different and use a man in the middle to selectively tamper with those 
bytes and see what causes the car to reject the battery. Hopefully there 
aren't too many differences! Carl at https://bluecars.nz/ has a leaf 
system on the bench, so establishing the man in the middle won't be too 
hard.

___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Read EVAngel's EV News at http://evdl.org/evln/
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)



Re: [EVDL] Anyone interested in 2015 Leaf drivetrain or interior/exterior/suspension parts?

2017-01-26 Thread Tom Parker via EV

On 27/01/17 07:06, Cor van de Water via EV wrote:

Did you grab communication from *both* CAN buses?
The Leaf's Battery Controller (LBC) communicates via the VCM which is
connected to both the EV CAN bus and the normal CAN bus, to the
Combination Meter, which is supposed to hold the key that is paired to
the LBC. So some communication spills over from one CAN bus to the
other. Both are available on the OBD (Data Link) connector. Without a
dump from both, it is hard to tell what would disable/enable the Leaf
since only half the communication can be seen.
I'm only capturing the EV CAN bus -- I'm interested in how the BMS is 
authenticated by the rest of the car, so that transaction must pass 
through the EV bus to get to the BMS. Unless it isn't done on the CAN 
bus at all, but that seems unlikely?

___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Read EVAngel's EV News at http://evdl.org/evln/
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)



Re: [EVDL] Anyone interested in 2015 Leaf drivetrain or interior/exterior/suspension parts?

2017-01-26 Thread Tom Parker via EV

On 24/01/17 23:25, Tom Parker via EV wrote:

On my car, there is only one frame that isn't repeated continuously 
after startup (0x603 is sent once, with a single byte payload which is 
00 in my captures).


I'll try disconnecting the 12v battery tomorrow and see if anything 
different happens at when it's connected, or during the first startup.


I removed the 12V battery and there was no activity on the EV CAN bus 
when it was reconnected. There were also no new messages when I turned 
the car on, and other than 0x603, they all streamed continuously. I 
waited quite a long time (10 minutes maybe) before reconnecting the battery.


I guess this means the BMS authentication is in the repeating messages, 
or it is triggered by some other event than disconnecting the 12V 
battery, or you can have the 12V battery disconnected for a very long 
time without breaking the BMS authentication.

___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Read EVAngel's EV News at http://evdl.org/evln/
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)



Re: [EVDL] Anyone interested in 2015 Leaf drivetrain or interior/exterior/suspension parts?

2017-01-24 Thread Tom Parker via EV

On 24/01/17 04:07, Ed Blackmond via EV wrote:


I am interested in learning how to reset the capacity gauge. Cor replaced the 
battery cells in my 2011 Leaf about 2000 miles ago. LeafSpy now reports about 
62.5AH, but the capacity gauge on the dash hasn't budged. I get over 265 GIDs 
on a full charge and the car has range equal to what it was when new.  The 
state of charge gauge works fine and the distance to empty number is as 
inaccurate as ever.




When you say the capacity gauge, do you mean the outer column of battery 
bars? IE you car still has the number of bars remaining that your old 
battery had before it was replaced?


You kept the original BMS, right? Do you know if the BMS is reporting 
healthy data and the instrument cluster is ignoring it, or if the BMS is 
reporting the old data? Obviously the BMS is reporting Ah & GIDs values 
that match the battery, but perhaps those values don't drive the 
instrument display? What about the SOH?

___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Read EVAngel's EV News at http://evdl.org/evln/
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)



Re: [EVDL] Anyone interested in 2015 Leaf drivetrain or interior/exterior/suspension parts?

2017-01-23 Thread Tom Parker via EV

On 23/01/17 10:52, Cor van de Water via EV wrote:

I sent you a separate email with an idea to avoid a fake Leaf pack and still 
keep the BMS happy and report SoC.


Is anyone trying to reverse engineer the handshake between the Leaf BMS 
and the rest of the car?


As I understand it, the Leaf BMS is quite happy to work on it's own but 
some other part car authenticates the BMS and is not happy if the BMS is 
swapped. A friend tried swapping the whole battery including the BMS he 
says the car was not happy, it worked but only in Turtle mode, 
regardless of state of charge.


Has anyone identified the CAN bus messages that contain the 
authentication handshake? I've been collecting information at 
https://carrott.org/emini/Nissan_Leaf_OVMS#Leaf_Can_Bus but I haven't 
seen information about the BMS authentication.


Could you put a man in the middle between the BMS and the rest of the 
car which allows the original BMS board to authenticate, but replaces 
all the battery status messages with "everything is fine"? Obviously the 
man in the middle would need to talk to the BMS on the new battery 
(either another Nissan or a whole new BMS or whatever) and tell the car 
everything is not fine if the new battery is in trouble.

___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Read EVAngel's EV News at http://evdl.org/evln/
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)



Re: [EVDL] Recent Model EV Conversion - CAN and accesories to work..

2017-01-03 Thread Tom Parker via EV

On 04/01/17 04:50, Collin Kidder via EV wrote:


I don't think that generic sales pitches are acceptable on this list
but since it is topically relevant I'd like to quickly mention that I
am involved in the creation of many pieces of hardware and software to
aid in these things.

CANDue: http://store.evtv.me/proddetail.php?prod=EVTVDue2=23
SavvyCAN: http://www.savvycan.com


Along these lines, the audio from 
https://xi.hope.net/schedule.html#-2016-car-hacking-tools- is worth a 
listen and gives links to http://opengarages.org/index.php/Tools (which 
includes Colin's SavvyCAN) and other resources.


More advanced, https://media.ccc.de/v/33c3-8131-dieselgate_a_year_later 
shows how to glitch a VW ECU to bypass the flash read-protect and 
retrieve a firmware image (also the technical Dieselgate information is 
interesting but off topic). Going from a firmware image to an emulated 
ECU is probably the hard way to make a modern car work without it's ICE.


___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Read EVAngel's EV News at http://evdl.org/evln/
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)



Re: [EVDL] Japanese leaf charging cable

2016-05-03 Thread Tom Parker via EV

On 05/03/2016 08:28 AM, George Tyler via EV wrote:

Hi, here in NZ many people are importing used Nissan Leaf's from Japan.
Japan has different voltage and frequency to the supply here, leaf charging
cable: 200V 60hz, NZ voltage 230V 50Hz. There is a small transformer in the
cable that has to be changed, but opening the cable means that it has to be
re-certified. Does anyone know what the charging cable electronics does?
The cable has an EVSE embedded in it. This basically tells the car how 
much current is available and only turns on the power if a car is 
actually present. In the EVSE supplied with the Gen 1 cars the power 
supply for the circuit inside the EVSE has a mains step down transformer 
not for more than 200v. This transformer will saturate on 240V and get 
very hot. The dealer forgot to do the replacement on our car and it 
failed after about 6 weeks being plugged in continuously. They replaced 
it with one that had been modified. I think you may also have to replace 
some over-voltage protection too.


What is the certification you're worried by? I'm not aware of needing a 
certification to plug something in in New Zealand.


The EVSE supplied with the Gen 2 cars is smaller, I don't know if that 
one needs modification or not.


If you don't want to modify the Nissan EVSE you might look at 
https://bluecars.nz/bc-shop/ in Auckland. Carl has an 8-10-16A 
selectable EVSE with a 16A caravan plug & a caravan to "normal" 10A 3 
pin plug adapter (with 10A circuit breaker and RCD). He also has a fixed 
8A EVSE.

___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Read EVAngel's EV News at http://evdl.org/evln/
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)