<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Welcome Jason,<br>
<br>
I'm in contact with a potential developer for the Fiat 500e
adaptation. I've informed him about your offer, maybe he'll contact
you or join in.<br>
<br>
Regarding reverse engineering of the Fiat protocol, it's of course a
great advantage being able to capture the original telematics
control communication.<br>
<br>
I'm not familiar with the Ross-Tech and AlfaOBD. You need an
interface able to continuously capture at the full bus speed, which
no ELM327 compatible is capable of.<br>
<br>
If the Ross-Tech or AlfaOBD also cannot do that, check for example
for an AGV4000, I've been using one of them for 500 kbit captures. A
simple Arduino with a standard 16 Mhz CAN module will also be able
to capture at full 500 kbit, for example using my Arduino CanLogger:
<a class="moz-txt-link-freetext" href="https://github.com/dexterbg/CanLogger">https://github.com/dexterbg/CanLogger</a><br>
<br>
<br>
Some general hints on the capturing:<br>
<br>
Activate time stamps on the capturing. Use separate trace files for
separate functions / groups. Follow a strict test protocol, so notes
& files can be mapped reliably.<br>
<br>
Begin with noting down the current dashboard readings, so the values
can be identified in the capture. Redo captures at different gauge
levels (i.e. SOC, odometer, temperatures, tire pressures etc.).<br>
<br>
Test one car function at a time, note the log timestamps of each
invocation and reaction.<br>
<br>
Begin with simple functions like pushing buttons, activating lights
etc., continue with pedals etc.<br>
<br>
When testing the telematics control functions, note down the
possible parameters (like temperature on climate control), then
invoke the function at some different settings for each parameter
(again, change one parameter at a time). You don't need to check all
values in range, just 2-3 strategic points.<br>
<br>
Do some live driving captures, best on a test track, with a simple
acceleration / speed profile.<br>
<br>
<br>
If the Fiat does not react to standard OBD requests, it may use
custom OBD addresses or the CANopen protocol. This can normally be
deducted from the captured CAN frames. You can also <br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 08.01.2018 um 16:07 schrieb Jason
Perkins:<br>
</div>
<blockquote type="cite"
cite="mid:CA+8Y7qKo2Z-mm1YnL8g7u8cEzcHk7heKJJKLP__Ag2m_ijH6Jg@mail.gmail.com">
<div dir="ltr">
<div dir="auto">OVMS team,</div>
<div dir="auto"><br>
</div>
<div dir="auto">As an owner of a Fiat 500e I was very interested
when I stumbled across this project on the TMC forums. <span
style="font-size:12.8px">The</span><span
style="font-size:12.8px"> </span><span class="gmail-il"
style="font-size:12.8px">Fiat</span><span
style="font-size:12.8px"> </span><span
style="font-size:12.8px">factory telematics system
deactivates 3 years from the original vehicle sale and is
non renewable. I think FCA wants to kill the whole system at
this point (it's been replaced with the corporate UConnect
system) so another solution would be ideal. </span></div>
<div style="font-size:12.8px"><br>
</div>
<div style="font-size:12.8px">I have a 2013 500e with
deactivated telematics, and our roommate has a 2014 with
working telematics. If any data could be captured from the car
with working telematics (branded as <span class="gmail-il">Fiat</span> Access)
to assist integrating OVMS I'd love to help. </div>
<div style="font-size:12.8px"><br>
</div>
<div style="font-size:12.8px">The <span class="gmail-il">Fiat</span> Access
telematics provides vehicle location, battery level, tire
pressure, setting the charge schedules, locking / unlocking
the car, and starting the climate control. I believe the
actual control unit was adapted from some kind of
remote-disablement system used in europe (the Fiat literature
calls this the Vehicle Tracking Module). </div>
<div style="font-size:12.8px"><br>
</div>
<div style="font-size:12.8px"><span style="font-size:12.8px">The </span><span
class="gmail-il" style="font-size:12.8px">Fiat</span><span
style="font-size:12.8px"> has a normal J1962 plug, but does
not have OBDII protocol support. Like the Kia Soul the
powertrain CAN on pin 6 / 14 and the body CAN on 1 / 9. </span><br>
</div>
<div style="font-size:12.8px"><span style="font-size:12.8px"><br>
</span></div>
<div style=""><span style="font-size:12.8px">There's no telling
how long the telematics will keep working on our
roommates '14, so doing a capture sooner than later would be
good. I'm open to any suggestions on how best to do this.
The car related diag tools I have on hand are: ELM327
Bluetooth, Ross-Tech VCDS (For VW / Audi Products), and
AlfaOBD (which can talk to most of the modules in the 500e -
but not the VTM :( ), and an adapter to swap the CAN wires
so a standard interface can get to the Body CAN. </span></div>
<div style=""><span style="font-size:12.8px"><br>
</span></div>
<div style=""><span style="font-size:12.8px">Thanks!</span></div>
<div style=""><span style="font-size:12.8px"><br>
</span></div>
<div style=""><span style="font-size:12.8px">-J</span></div>
<div dir="auto"><br>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a>
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="160">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</body>
</html>