200 tvr cerbera speed 6 diagnostic pc software
Discussion
i have a 4.2 and tried to connect my laptop up yesterday but was unsuccessful. i bought a usb to serial adaptor and a straight wired male to female serial rs232 lead from maplins. when hooked up it just said no ecu connected or comms error. i remember some time ago reading a thread about all of the settings etc for the port ie baud rate and the like but seem to be unable to search far enough back in time to find it. can anyone help????
also lambda sensors, is there any difference between the £68 ones from the website linked of the cerbera parts list or the £130 tvr ones?
also lambda sensors, is there any difference between the £68 ones from the website linked of the cerbera parts list or the £130 tvr ones?
tur8o said:
i have a 4.2 and tried to connect my laptop up yesterday but was unsuccessful. i bought a usb to serial adaptor and a straight wired male to female serial rs232 lead from maplins. when hooked up it just said no ecu connected or comms error. i remember some time ago reading a thread about all of the settings etc for the port ie baud rate and the like but seem to be unable to search far enough back in time to find it. can anyone help????
also lambda sensors, is there any difference between the £68 ones from the website linked of the cerbera parts list or the £130 tvr ones?
I'm not exactly sure what the settings are, but my old XP Laptop - with a serial port works - with all the default settings. also lambda sensors, is there any difference between the £68 ones from the website linked of the cerbera parts list or the £130 tvr ones?
Connect everything up. Press the Start to kick in the Ignition. Remember if you dont connect anything within 30 seconds, the immobiler will kick in, and the connection between the ECU and Diags will be broken. So always ensure that the Immobilier hasn't kicked in.
I always have to do the following each time I use the Diags.
1. Connect everything up
2. Start up the Diags
3. Ignore the error message that the ECU is not connected,
2. Right Click My Computer > Manage
3. Go to Device Manager
4. In the RH Pane go to Ports (com1 LPT), and expand it
5. Right Click on Com1, and select Uninstall - ignore the warnings
6. Right click on Ports and select 'Scan for Hardware Changes'
Now go back to the Diags and select the Reconnect to ECU.
I use a USB to serial for mine. I just ensured the USB serial came up as Com1. You may have to go into device manager/ports in windows (assuming XP) and change the port numbering around so this happens. After that I had no problems.
Oh and make sure the immobiliser is off, i.e. press the key fob after turning the ignition on.
Oh and make sure the immobiliser is off, i.e. press the key fob after turning the ignition on.
The serial port needs to be set to be COM1 on the laptop. The software is hard coded to default to that port.
ETA I have a vague recollection of finding a key combination that would switch the software to use COM2 but I cant find any record of it. Someone else may be able to help there.
ETA I have a vague recollection of finding a key combination that would switch the software to use COM2 but I cant find any record of it. Someone else may be able to help there.
Edited by Tanguero on Tuesday 12th March 20:48
aide said:
Tanguero said:
ETA I have a vague recollection of finding a key combination that would switch the software to use COM2
That's extremely interesting!Can anybody shed light on this?
With the software running first press the F5 key to disconnect the coms then press the F10 key and you get a menu that lets you chose between COM1 and COM2.
Reset everything then run it for a bit. Air temp fault will be logged if it has been started with the air temperature sensor unplugged. Battery volts could be anything but may well go away if its running properly. If its still showing a lambda fault after a run then I would address that before worrying about the other faults. Things like AFR and adaptives will be all over the place if the lambda sensor is playing up.
Don't necessarily assume its a sensor fault though. On my car I had persistent problems with water getting into the lambda sensor connectors and giving all sorts of strangeness. Solved eventually by putting properly waterproof connectors on the lambda sensors and harness.
Don't necessarily assume its a sensor fault though. On my car I had persistent problems with water getting into the lambda sensor connectors and giving all sorts of strangeness. Solved eventually by putting properly waterproof connectors on the lambda sensors and harness.
Dragging up the past!!
I have exactly these codes on mine.
What was the outcome. I predicted 123 running rich. Plugged in today.
Lambda 1 dormant. %s on 123 up in the 30s. Afr was red. But yet the software said the lambda1 was ok
I don't think it is. Will check wiring.
Where are we buying lambdas from these days??
I have exactly these codes on mine.
What was the outcome. I predicted 123 running rich. Plugged in today.
Lambda 1 dormant. %s on 123 up in the 30s. Afr was red. But yet the software said the lambda1 was ok
I don't think it is. Will check wiring.
Where are we buying lambdas from these days??
wurzlegummage said:
Dragging up the past!!
I have exactly these codes on mine.
What was the outcome. I predicted 123 running rich. Plugged in today.
Lambda 1 dormant. %s on 123 up in the 30s. Afr was red. But yet the software said the lambda1 was ok
I don't think it is. Will check wiring.
Where are we buying lambdas from these days??
If the software says the lambda sensor is ok but the value from is pegged and has a bad AFR then it could very well mean that the sensor itself is ok and it genuinely is detecting a rich condition that is severe enough to hold the output value steady.I have exactly these codes on mine.
What was the outcome. I predicted 123 running rich. Plugged in today.
Lambda 1 dormant. %s on 123 up in the 30s. Afr was red. But yet the software said the lambda1 was ok
I don't think it is. Will check wiring.
Where are we buying lambdas from these days??
Looking for some advice on how to connect my laptop to the ECU as it feels like I have now read every post and every article about connecting my Cerbera 4.2 ECU to my laptop and still to no avail. The sorry saga so far.
We are all mac, so bought an old laptop with a Windows XP operating system, and downloaded the old version of the diagnostics software (yellow car), connected initially with a diagnostics cable male to USB with a serial converter, but I was continually getting the unable to open serial port error. I have been through all of the instructions re changing the serial port, still nothing.
I then tried downloading the new software (blue car), same issue, unable to open serial port 1, it is definitely set to serial port one, I thought perhaps it could be the cable, so sourced a new cable with a male (9 pin) direct to usb and tried that. No difference, it still seems impossible to locate the ECU on the computer, despite following the full procedure with the ignition on and immobiliser off etc and even with the engine running there is nothing.
I then downloaded the newer Varley software, but am still unable to make any contact between the ECU and the laptop.
I have now tried a combination of different laptops, cables and software, but I am still unable to get anything to recognise any output from my ECU.
… any ideas welcomed
We are all mac, so bought an old laptop with a Windows XP operating system, and downloaded the old version of the diagnostics software (yellow car), connected initially with a diagnostics cable male to USB with a serial converter, but I was continually getting the unable to open serial port error. I have been through all of the instructions re changing the serial port, still nothing.
I then tried downloading the new software (blue car), same issue, unable to open serial port 1, it is definitely set to serial port one, I thought perhaps it could be the cable, so sourced a new cable with a male (9 pin) direct to usb and tried that. No difference, it still seems impossible to locate the ECU on the computer, despite following the full procedure with the ignition on and immobiliser off etc and even with the engine running there is nothing.
I then downloaded the newer Varley software, but am still unable to make any contact between the ECU and the laptop.
I have now tried a combination of different laptops, cables and software, but I am still unable to get anything to recognise any output from my ECU.
… any ideas welcomed
This could help:
http://www.pistonheads.com/gassing/topic.asp?h=0&a...
or maybe this:
www.pistonheads.com/gassing/topic.asp?h=0&f=15...
http://www.pistonheads.com/gassing/topic.asp?h=0&a...
or maybe this:
www.pistonheads.com/gassing/topic.asp?h=0&f=15...
Gassing Station | Cerbera | Top of Page | What's New | My Stuff