Technical 6F/16F Cinque/Sei ECU Reader Project
- Thread starter Jamieboy
- Start date
Currently reading:
Technical 6F/16F Cinque/Sei ECU Reader Project
CinqSporting97
New member
Tommi,
I have written some software in C# with a nice user interface that already reads the sensor values and trouble codes. I also intend to implement Active Diagnostics so you can activate the various actuators, etc to test their operation.
At the minute its a bit rough around the edges, but I certainly intend to post it up so everyone can benefit from it.
I'll keep you all posted.
I have written some software in C# with a nice user interface that already reads the sensor values and trouble codes. I also intend to implement Active Diagnostics so you can activate the various actuators, etc to test their operation.
At the minute its a bit rough around the edges, but I certainly intend to post it up so everyone can benefit from it.
I'll keep you all posted.
Uno driver
New member
- Joined
- Dec 16, 2007
- Messages
- 284
- Points
- 49
Straight from battery (use aligator clip)
Thanks! Somehow connecting something to my computer that is hooked up directly to a car battery on the other side does not appeal to me, but I will have to get pass through it
I was thinking also from the ECU 5A fuse socket. This is practically the same as battery, would that be with voltage regulated to 12V? I could make a nice gizmo to put in between the fuse socket and the fuse itself. Also put an additional small fuse for the interface, not sure how big this should be though...
Cheers,
Woj
Uno driver
New member
- Joined
- Dec 16, 2007
- Messages
- 284
- Points
- 49
You can fit a small fuse (or resistor) between aligator clip and ecu reader, but i don't think it's necessary as it only powers two pull-up resistors. Current is very low, max 0,03A.
G'day, folks; dragging this one up again...
Some of you will know of the barnacle widget and the star-trek software for coupes; what you may not know is that I have a version of star-trek for the Punto MK1 55 (forced upon me because daughter's car was overheating and didn't have a temperature gauge - it's a shame you have to hack the ECU to find out how warm the water is!).
I need to make a small modification to the code to use with my current interface of choice: one of the VAG OBD adaptors cluttering up ebay and identified as '409.1 KKL' - big blue chunky USB to OBDII thing. I pick up the K, L, power, and ground lines and take them out to a flying lead and the AMP connector for the ECU. That done, I'll post a link to a download. (All free, of course; GNU LGPL license terms.
I've seen some interesting stuff on here (I had to learn enough italian to translate the docs!) and (damn!) some of my own early not-quite-working-properly adaptors.
I'm currently working on dropping down a level - I've just written a console version of startrek for the coupe, because it simplifies the program structure immensely. It's also easy to translate to another ecu, because you can do it linearly rather than messing around with the <insert swearword here> windows event handler API. Next on the list is for the coupe 20v/vt, which uses the Bosch M2.10.4 with its completely incompatible protocol - but which opens up things like the Punto GT which is very similar. Rather than a one-size-fits-all approach, for development, I'm working on one prog per ECU.
I should stress that I'm up to my ears with lots of other stuff going on, but if there's interest in a punto/sei/quint version of the console app, I'll be happy to bop one out. Shouldn't take long...
Useful hints if you're rolling your own:
1) full details for construction and software of the MK1 widget here: there's everything you need to build one (it'll work on veroboard) but you may need to sort out a different display as the one I used then is like rocking horse droppings. If so, the display driver code is in one chunk.
2) the connector you need for Fiats - at least, all the ones I've come across - is this one: farnell part number 150678 (the picture is wrong!) and you'll also need the pins: part number 151040
3) Any USB adaptor using the FTDI chipset will work at 7812 baud; most others don't. However, *no* USB-serial adaptor will work at 5 baud. You can bit bang the output from Windows using the SetCommBreak and ClearCommBreak functions.
4) Timing in windows is a pain in the proverbial. Easiest way I've found is to ignore the timer (though I do it that way in the Punto Startrek) and just use SleepEx() - you need to include windows.h even if doing a console app. Delay is in milliseconds, so five baud is easy, as is the delay between the trigger bytes to initialise.
5) If you have a *genuine* PC-compatible (i.e. a 16550 or close equivalent) it will actually work at 5 baud. But you'd probably have to do it by talking to the chip directly in dos mode; I don't think the driver will accept it directly.
Hope this helps,
Neil
Some of you will know of the barnacle widget and the star-trek software for coupes; what you may not know is that I have a version of star-trek for the Punto MK1 55 (forced upon me because daughter's car was overheating and didn't have a temperature gauge - it's a shame you have to hack the ECU to find out how warm the water is!).
I need to make a small modification to the code to use with my current interface of choice: one of the VAG OBD adaptors cluttering up ebay and identified as '409.1 KKL' - big blue chunky USB to OBDII thing. I pick up the K, L, power, and ground lines and take them out to a flying lead and the AMP connector for the ECU. That done, I'll post a link to a download. (All free, of course; GNU LGPL license terms.
I've seen some interesting stuff on here (I had to learn enough italian to translate the docs!) and (damn!) some of my own early not-quite-working-properly adaptors.
I'm currently working on dropping down a level - I've just written a console version of startrek for the coupe, because it simplifies the program structure immensely. It's also easy to translate to another ecu, because you can do it linearly rather than messing around with the <insert swearword here> windows event handler API. Next on the list is for the coupe 20v/vt, which uses the Bosch M2.10.4 with its completely incompatible protocol - but which opens up things like the Punto GT which is very similar. Rather than a one-size-fits-all approach, for development, I'm working on one prog per ECU.
I should stress that I'm up to my ears with lots of other stuff going on, but if there's interest in a punto/sei/quint version of the console app, I'll be happy to bop one out. Shouldn't take long...
Useful hints if you're rolling your own:
1) full details for construction and software of the MK1 widget here: there's everything you need to build one (it'll work on veroboard) but you may need to sort out a different display as the one I used then is like rocking horse droppings. If so, the display driver code is in one chunk.
2) the connector you need for Fiats - at least, all the ones I've come across - is this one: farnell part number 150678 (the picture is wrong!) and you'll also need the pins: part number 151040
3) Any USB adaptor using the FTDI chipset will work at 7812 baud; most others don't. However, *no* USB-serial adaptor will work at 5 baud. You can bit bang the output from Windows using the SetCommBreak and ClearCommBreak functions.
4) Timing in windows is a pain in the proverbial. Easiest way I've found is to ignore the timer (though I do it that way in the Punto Startrek) and just use SleepEx() - you need to include windows.h even if doing a console app. Delay is in milliseconds, so five baud is easy, as is the delay between the trigger bytes to initialise.
5) If you have a *genuine* PC-compatible (i.e. a 16550 or close equivalent) it will actually work at 5 baud. But you'd probably have to do it by talking to the chip directly in dos mode; I don't think the driver will accept it directly.
Hope this helps,
Neil
Hi there,
I made the cable, too dark to connect it to the car. I connected it just to the com port, the ecu plug unconnected. The diag program in cable test mode just echoes the data send to the cable. Is this correct, or did I mess something up?
Cheers,
Woj
I made the cable, too dark to connect it to the car. I connected it just to the com port, the ecu plug unconnected. The diag program in cable test mode just echoes the data send to the cable. Is this correct, or did I mess something up?
Cheers,
Woj
I'm tempted to make one of these for the hell of it, seems simple enough
but...
Does anyone know if a PL2023 based USB <-> serial adapter (adaptor?) would work, as DX sell a couple based on this chipset for a couple of quid.
but...
Does anyone know if a PL2023 based USB <-> serial adapter (adaptor?) would work, as DX sell a couple based on this chipset for a couple of quid.
Ah, well they are only $2.99 (search for 24512) and it's something that would probably be handy at some point anyway, so I might try it
Could be awquard trying to test it with the desktop system tho, to make sure the cable is ok and it's not a problem with the laptop or serial adaptor...
Could be awquard trying to test it with the desktop system tho, to make sure the cable is ok and it's not a problem with the laptop or serial adaptor...
nedge2k
Member
I'm after the same info, took mine to a "friendly" garage to get it code read, they tried both Launch and Snap-on readers on it, neither worked. I don't wanna take it to Fiat but I need to find out why my 1.2 16v is returning 25mpg!
Does anyone know if the ELM323 cables are compatible and if any "off the shelf" software will work? Like Uniscan?
I'm an IT/Web guy by trade working for an engine specialist so none of the stuff in this thread really goes over my head but i'm not an experienced software dev so modding the source to work with the 18FD ain't summin I can do
nedge2k
Member
Right, screw it, I've bought a VagCom lead and I'm gonna have a go at 18FD interrogation! Watch this (or some other more relevant) space
Does anyone know where the 16F documentation originated? Did the source have anything for the 18FD protocol too?
Does anyone know where the 16F documentation originated? Did the source have anything for the 18FD protocol too?
Last edited:
I'm talking to Nedge about getting the IAW18F working in the console version StarTrek. I have a working IAW16F graphical StarTrek but I'd like to get it working with the console mode version too.
I have data for the 16F and 18F.
Neil
I have data for the 16F and 18F.
Neil
