PDA

View Full Version : Startrek



wrinx
15-06-12, 23:43
Anyone tried it...?

wrinx

wrinx
16-06-12, 00:06
Oh...and where's the Q4's diag port?

wrinx

Steve Webb
16-06-12, 08:31
Anyone tried it...?

wrinx

Original or next gen?

Seriously, is this the PC based diagnostic? Got a link?

Not sure where the diag port would be, but given the electrics in the rest of the car, its probably somewhere dirty, hot and next to a sharp edge to cut at least one of the wires.

AlfaJack
16-06-12, 09:12
I think there is a plug by the ecu.

wrinx
16-06-12, 10:02
Confirmed as working for Q4s, you'll need a couple of cables to communicate.

Main page: http://www.nailed-barnacle.co.uk/coupe/startrek/startrek.html
Specific to Q4: http://www.nailed-barnacle.co.uk/coupe/startrek/startrek409.zip

wrinx

wrinx
16-06-12, 10:04
I think there is a plug by the ecu.

Ahh, yes, was groping down there a week ago and recall there being a three pin plug hanging around.

wrinx

wrinx
16-06-12, 10:09
This is a simple guide to what's needed...

http://www.fiatforum.com/punto-guides/238280-reading-spi-ecu-data-logging.html

wrinx

Steve Webb
16-06-12, 10:12
Looks interesting, is there a diagram of the cable needed?

Scratch that, just spotted your other links.

wrinx
16-06-12, 10:15
See the Fiat thread for pics of the cables. I'd check the Q4 before buying the three pin one...but I'm pretty sure it's the same.

Edit: mine only has one red fly lead but it's fine. The black lead is just an earth but the middle pin of the connector is also an earth.

wrinx

wrinx
16-06-12, 10:28
Codes will be something like this...

Error.....Binary.....Fault
128...10000000.....80
64.....01000000.... 40
32.....00100000.....20
16.....00010000.....10
8.......00001000......8
4..............0100.....4
2..............0010.....2
1..............0001.....1

Fault can then be read from here, checking which column it came from:

http://i54.photobucket.com/albums/g118/wrinx/Q4/Error_Codes.jpg

wrinx

Steve Webb
16-06-12, 10:31
Hmm, I've got a selection of old Alfa connectors, by the looks of the 2 cables needed, you should be able to put the cable together using an old serial plug and an Alfa connector.

Time for some digging.

mpampis_
16-06-12, 14:06
I tried it. It was working for 1 day. After that never works. I don't know, maybe the cables are fault. I bought them for 15 Euros from china

Steve Webb
16-06-12, 17:39
Was it the connector near to the ECU that you plugged the cable into?

wrinx
16-06-12, 21:59
Woohoo....works like a charm!

I'll post some pics later but there's plenty of error code for me to analyse! :lol:

Including a couple of "255" which isn't in the list :oops:

wrinx

wrinx
16-06-12, 22:00
Was it the connector near to the ECU that you plugged the cable into?

Yes :)

wrinx

wrinx
16-06-12, 23:24
Well....that's confused me!

Got the following codes:

Column 1………….1, 3
Column 2…………..4, 12, 64 (off)
Column 3…………..64, 255

Bear in mind 3, 12 and 255 aren't in the list I'm guessing they're the product of two errors together...???

So they translate to:

Column 1 (input)
1 - TPS)
3 - Assuming 1&2 means TPS and MAP (3 was constantly there whilst running, 1 only when cranking)

Column 2 (output)
4 - Coil pack 2
12 - Assuming 4&8 means Coil pack 2 and Idle stepper motor (4 occurred during revving and 8 occurred during idling)
64 - fuel pump (ignoring as ignition was cut)

Column 3 (functionality)
64 - not used!
255 - no flamin' idea!

Does that make sense to anyone? :lol:

I think I've got a few errors :roll:

wrinx

mpampis_
17-06-12, 09:08
When I tried it the only error I had it was the EEPROM. I guess because of the different checksum. I can't iuderstand why after the first day I bought the cables they never work again. The blue vagcom is lighting when I connect it to 3pin adaptor

Steve Webb
17-06-12, 09:24
Does that make sense to anyone? :lol:
wrinx

Fraid not, I guess I need to get hold of the cables and have a go myself, it looks useful to say the least.




I think I've got a few errors :roll:
wrinx

Well it would be even more worrying if you didn't have any!

wrinx
17-06-12, 10:11
When I tried it the only error I had it was the EEPROM. I guess because of the different checksum. I can't iuderstand why after the first day I bought the cables they never work again. The blue vagcom is lighting when I connect it to 3pin adaptor

It could the that the cable has failed...mine came from Sander and were expensive but hopefully good quality!

wrinx

wrinx
17-06-12, 10:13
Fraid not, I guess I need to get hold of the cables and have a go myself, it looks useful to say the least.

Very useful indeed...and also simple, despite what I've written!

But it's hard to write so it makes sense to anyone unless they've tried it out.

Neil (the author) has replied to my email and it does look like you can get multiple errors so a 3 could be 1&2 combined. He's going to look at my log file and get back to me.

Helpful chap :cool:

wrinx

alfa155chris
17-06-12, 11:00
Hope you get it sorted soon steve

Steve Webb
17-06-12, 11:19
It could the that the cable has failed...mine came from Sander and were expensive but hopefully good quality!

wrinx

Whats the deal with the external power croc-clips on some VAG cables? Reference voltage or something else?

wrinx
17-06-12, 12:37
Do you mean the three pin connectors with fly lead? If so, it needs a 12v power source to work.

That's then plugged into the standard KKL lead which has the USB to your laptop.

wrinx

Steve Webb
17-06-12, 12:44
Well....that's confused me!

Got the following codes:

Column 1………….1, 3
Column 2…………..4, 12, 64 (off)
Column 3…………..64, 255

Bear in mind 3, 12 and 255 aren't in the list I'm guessing they're the product of two errors together...???

So they translate to:

Column 1 (input)
1 - TPS)
3 - Assuming 1&2 means TPS and MAP (3 was constantly there whilst running, 1 only when cranking)

Column 2 (output)
4 - Coil pack 2
12 - Assuming 4&8 means Coil pack 2 and Idle stepper motor (4 occurred during revving and 8 occurred during idling)
64 - fuel pump (ignoring as ignition was cut)

Column 3 (functionality)
64 - not used!
255 - no flamin' idea!

Does that make sense to anyone? :lol:

I think I've got a few errors :roll:

wrinx

Now I've woke up a little more and taken another look at this, It looks to me as though some of the confusion comes from them using some sort of bastardised binary.

Bin / bastard bin
1/1
2/2
4/4
8/8
16/10
32/20
64/40
128/80

I'd say you were right with your assumptions for columns 1&2

As for the third column, your 64 error would be 40 and not used as you say.

The 255 error would come from errors from everything (1+2+4+....+128) and I'd say that was just a glitch in the logging, or the car about to explode. :hyper:

wrinx
17-06-12, 12:59
Iirc one of the two 255 errors was in the third column so I'm tempted to ignore it anyway :lol:

wrinx

mpampis_
17-06-12, 19:00
Was it the connector near to the ECU that you plugged the cable into?

Sorry Steve I didn't understand what you mean? The 3pin adapter is about 15cm long so it is near the ecu and I "steal" power for a cable I found near there with 12volt

Steve Webb
01-07-12, 13:54
Well the cables turned up this week, so if I get a few minutes later on this afternoon, I'll man up and plug the laptop in. See just how many faults the car has.

Anyone like to take a guess as to how bad it will be?

wrinx
01-07-12, 18:13
Can't see you beating mine ;)

wrinx

mpampis_
01-07-12, 18:45
If the car is ok you will have only EPROM fault because of checksum as mine

Steve Webb
01-07-12, 19:08
Well that was interesting, both with the ignition on, and when the car is running I only get the EPROM error lit.
I had to grab the battery from the Land Rover before starting as it looks like the battery on the car is pretty much dead, despite being left on a battery conditioner.
When looking through the log though, I got error 4 in the second error column, which from the list means an error in coil pack 2. Nothing in column 3.
I would have expected error 4 in column 3, for a ROM error due to an Evocars chip.

Don't know about you but it seems as though the logging is placing errors in the wrong column. Or have I got that wrong?

Anyway here is the CSV log file. The voltage is low as I know my alternator is on its last legs.

wrinx
01-07-12, 19:30
Sounds about right from what little experience I've got...the Eprom error will be the chip.

Coil pack...I plan to replace mine but I've a horrible feeling it'll still show an error, perhaps the error could down to a bad earth, only time will tell.

wrinx

Steve Webb
05-07-12, 13:40
One thing I forgot, I don't seem to get full deflection from the throttle. On the graphical display the throttle goes from 0 - 90 but I only ever saw a max of 72. Is that the same for you wrinx?

wrinx
05-07-12, 18:04
No idea, I've only really idled the car; is this seen before turning the engine on?

wrinx

Steve Webb
05-07-12, 18:44
Yep, you can do it with just the ignition on and without the engine running, which is helpful when you are testing with the car sat in the garage.

mpampis_
06-07-12, 07:12
One thing I forgot, I don't seem to get full deflection from the throttle. On the graphical display the throttle goes from 0 - 90 but I only ever saw a max of 72. Is that the same for you wrinx?

The max I had on mine it was 80% but even 72 doesn't matters. The only job that is doing is to recognize the ecu tha the throttle body is closed or more than a half to enrich the gas mixture at wot

Steve Webb
07-07-12, 21:52
The max I had on mine it was 80% but even 72 doesn't matters. The only job that is doing is to recognize the ecu tha the throttle body is closed or more than a half to enrich the gas mixture at wot

Cheers for that, thought I was only getting 3/4 throttle travel.

mpampis_
08-07-12, 09:10
Just be sure that on idle it is about 0.28- 0.3 volt. Better somewhere in the middle like 0.29 so you will see abou 78% at WOT in startrek

Steve Webb
08-07-12, 11:19
Is that going to be affected by my worn out alternator? I'm not seeing 13.8v when the engine is running.

mpampis_
08-07-12, 13:22
I really don't know Steve. I have 13.7 volt and I am seeing that because of the gauge I have after removing the battery to the trunk and new cables

Lukajda
22-12-12, 18:46
Hey guys,

i would like to ask if you have some experience with troubleshooting in startrek software. We are not able to connect to our ECU.

First we bought cable with not genuine FTDI chip, what was obviosly mistake and we bought new one with FT232BM chip, that should work also with other programs. But... After self instalation of drivers i´m able to see my port in startrek software. That looks fine. After chosing ECU in startrek to "16V turbo" program just freeze (or react really slowly). This happens even if it is or not connected to ECU.

So these scenarios are possible, i think:
- USB to KKL cable isn´t properly instaled and set up
- Startrek isn´t compatible with chip FT232BM
- Our ECU could take some damage when rebuilding car (welding and so on...)

My questions are:

1) What should be right setup of COM port in windows device manager?
- Bits per seconds, how many data bits, advanced setup,...
2) Does Startrek usualy "freeze" when ECU isn´t connected?

I´m trying find what´s wrong

Thanks for inputs! I appreciate it...

wrinx
05-01-13, 00:13
Lukajda - I seem to remember something about installing the cable driver TWICE for this to work...check the instructions for Startrek again in case I got it wrong.

You might want to try the other bit of software...it's easier to use imho as Startrek takes some working out.

wrinx