EAS - Yes but I'm being thick

This site contains affiliate links for which LandyZone may be compensated if you make a purchase.
R

Ragingrover

Member
Posts
53
Location
Ragingrover
Hi guys....

So I got the software and leads. Followed instructions, plugged it in, all well, got Tx and Rx feedback so comms should be healthy.
Got a shed load of fault codes which I'm not sure how to read, its the volume of them though ! If I "Reset" EAS nothing happens at all, no waning lights, no display messages and no surprise no rise in suspension.
So its read / writing but nothing else.

Help !

Karl
 
Last edited:
Update, was not looking closely enough. Although I'm getting comms feedback its a constant stream of 50s / 80s / starts with 200's so its a comms thing ?
How the heck do I start sorting this one ???
 
Using a process of iteration....start by changing the comms settings, baud rate etc until you get a steady idle.

Watch the vids by RSW for some base settings and work from there....if still no comms, start looking at the OBD socket itself, they do corrode internally!!
 
EASunlock was made for windows XP you may have major problems linking it to anything else. Also the main problem is the USB driver if your computer does not have a serial port which it was designed to work off and you are using a serial to USB adaptor. Can be a bloody nightmare to get working.
 
Saint.V8 said:
Using a process of iteration....start by changing the comms settings, baud rate etc until you get a steady idle.

Watch the vids by RSW for some base settings and work from there....if still no comms, start looking at the OBD socket itself, they do corrode internally!!
Click to expand...

Tried different ports and different baud / sample / refresh rates....Still nothing. I've pulled and inserted the plug a few times to clear the contact tracks on socket......

This bloomin project car is turning into a right pain !!! What did I expect eh ?? LOL
 
wammers said:
EASunlock was made for windows XP you may have major problems linking it to anything else. Also the main problem is the USB driver if your computer does not have a serial port which it was designed to work off and you are using a serial to USB adaptor. Can be a bloody nightmare to get working.
Click to expand...
The RSW software existd before XP and it works fine up to and including Win 7 with a good USB to serial adaptor.
OP, forget the list of FF's etc, you need a green "Good Idle" for it to work.
Almost certainly you have a problem with the USB to serial adaptor if you are using one. Did you load the correct USB driver before you started?

Where did you get the cable? Does it use an adaptor?
 
Datatek said:
The RSW software existd before XP and it works fine up to and including Win 7 with a good USB to serial adaptor.
OP, forget the list of FF's etc, you need a green "Good Idle" for it to work.
Almost certainly you have a problem with the USB to serial adaptor if you are using one. Did you load the correct USB driver before you started?

Where did you get the cable? Does it use an adaptor?
Click to expand...

I got it from P38Spare on Ebay. I chose that specifically as listing stated better than average USB adapter.

The suggestion has been made about the driver so I'll try that next.
 
Ragingrover said:
I got it from P38Spare on Ebay. I chose that specifically as listing stated better than average USB adapter.

The suggestion has been made about the driver so I'll try that next.
Click to expand...
Paid through the nose then.
You HAVE to install the driver before you plug the adaptor in or Windows will install a driver that it thinks suitable but never is. If you plugged in before you installed the correct driver, you have a problem, you need to remove the defective driver and then install the correct drive or it will always default to the driver Windows installed..
Which version of Windows are you using?
 
Datatek said:
The RSW software existd before XP and it works fine up to and including Win 7 with a good USB to serial adaptor.
OP, forget the list of FF's etc, you need a green "Good Idle" for it to work.
Almost certainly you have a problem with the USB to serial adaptor if you are using one. Did you load the correct USB driver before you started?

Where did you get the cable? Does it use an adaptor?
Click to expand...

Funny that as XP came out in 2001 and Netframework needed to run EASunlock in 2002. :);)
 
Datatek said:
This is the first release of the .NET Framework, released on 13 February 2002 and available for Windows 98, ME, NT 4.0, 2000,
Click to expand...

Yes so EASunlock could not run on any system prior to 2002. Retrospective yes but not before NET framework. XP was the system in use when EASunlock was developed, as far as i am aware Microsoft did the interface programming for Storie Wilson i believe. Well that's what he says anyway should i not believe him? :);)
 
wammers said:
Yes so EASunlock could not run on any system prior to 2002. Retrospective yes but not before NET framework. XP was the system in use when EASunlock was developed, as far as i am aware Microsoft did the interface programming for Storie Wilson i believe. Well that's what he says anyway should i not believe him? :);)
Click to expand...
No comment on that, my information is different.
 
Datatek said:
Paid through the nose then.
You HAVE to install the driver before you plug the adaptor in or Windows will install a driver that it thinks suitable but never is. If you plugged in before you installed the correct driver, you have a problem, you need to remove the defective driver and then install the correct drive or it will always default to the driver Windows installed..
Which version of Windows are you using?
Click to expand...

Did that, still no joy. I'm assuming that if there was no voltage to the ECU I'd get nothing Rx ?As opposed to the junk Rx I'm currently getting.
 
Ragingrover said:
Did that, still no joy. I'm assuming that if there was no voltage to the ECU I'd get nothing Rx ?As opposed to the junk Rx I'm currently getting.
Click to expand...

If you have bad comms you usually get a list of every possible fault code. Same valve listed as shut and open at same time is a sure sign of bad comms. You never actually get a valve stuck shut open or closed. It just means an action has been requested and nothing has happened so the ECU thinks the valve is open or closed.
 
Last edited:
wammers said:
If you have bad comms you usually get a list of every possible fault code. Same valve listed as shut and open at same time is a sure sign of bad comms. You never actually get a valve stuck shut open or closed. It just means an action has been requested and nothing has happened so the ECU thinks the valve is open or closed.
Click to expand...

Spot on, thats exactly what seems to be happening, every possible fault code in it comes up ! LOL
Still not sure where to go with this next...apart from the pub !
 
Saint.V8 said:
have you done as I suggested and checked the obd socket ??
Click to expand...
As best I can yes, I've diconnected and reinserted the plug a good few times to try and clean the contact points. I'll take the panel off that retains the socket next and try to get a better look.
Although its pouring it down out side so that won't be for some time, bugger !
 
I'm giving up and going to the pub !! I've tried everything that I can find out about and still no joy. Might have to admit defeat and get a local specialist out here :¬(
 
You must log in or register to reply here.

Similar threads

8v_chris
P38A EAS & Nanocom - not talking to each other!
2
Replies
28
Views
3K
8v_chris
8v_chris
R
Classic Classic EAS Diagnostics Help Near Nottingham
2
Replies
20
Views
2K
RAW111111
R
Paul Coddington
EAS question
2
Replies
22
Views
2K
Scotiawhiskers
Scotiawhiskers
F
P38A 97 P38 Gems - EAS issue which seems to have expanded
2 3 4
Replies
79
Views
5K
Grrrrrr
Grrrrrr
J
P38 eas problem (typical)
2
Replies
23
Views
2K
Grrrrrr
Grrrrrr
Back
Top