Not another EAS question

Sorry Lads n lasses but I'm afraid it is.
Trying to get the RSW EAS Reset suite to communicate with my 1998 P.38 DSE I'm getting some strange figures in the return column. I managed somehow to reset the system but can't get a good idle . Tried different Com Ports and 2 different laptops, one Vista and one Windows 10. Getting 20 E2 20 62 E0 E2 A0 70 74. still trying to fathom how to post a screenshot. ( what chance do I have with Unlock suite?)
Any advice, comments etc most welcome
Cheers
Pete

The forum is broke at the mo.
Difficult to post pics for many so probably not your fault.

If the laptop is Win10, press "Windows Key + Shift + S", and then select the section of your screen. Then simply Paste into the forum thread.

Most EAS Unlock comms issues are wrong windows drivers for the Serial cable, unless it's a real one with no USB converter. Make sure the Com Port is set to 9600 baud.
You can also try changing the delay slightly in the software..

Latest Update.
I fiddled with com ports and drivers and at last nice healthy FFs in the RX column.
I think the problem might've been too high a number com port and maybe the wrong driver. Wouldn't swear to it because computers are still black magic to me. If they had pulleys and grease nipples I might have a chance of understanding them.
Thanks for the assistance.
Pete
Thinking it might be time for an L322 so I'll be back

Spridget said:

Latest Update.
I fiddled with com ports and drivers and at last nice healthy FFs in the RX column.
I think the problem might've been too high a number com port and maybe the wrong driver. Wouldn't swear to it because computers are still black magic to me. If they had pulleys and grease nipples I might have a chance of understanding them.
Thanks for the assistance.
Pete
Thinking it might be time for an L322 so I'll be back

Click to expand...

If you are struggling with P38 diagnostics, I don't fancy your chances with the L322
Vista is often a problem communicating with the RSW software, Win 10 less so, but with either preloading the correct USB to serial driver is imperative. If you plug the hardware in before loading the driver, Win will use a generic driver that doesn't have the RTS/DTS protocol needed.

I've had this car for 16 years now and managed to survive all the usual P38 traumas without having to resort to a visit to the professionals. I'm hoping, maybe naively that the L322 will be similar. Maybe be able to reset EAS and suchlike with an icarsoft or similar?
When I decided to change my Classic for the P38 I heard all the horror stories and was told to avoid them like the plague and keep the Classic. Wondering now if I should keep the P38 for another 16years or take the plunge.

Spridget said:

I've had this car for 16 years now and managed to survive all the usual P38 traumas without having to resort to a visit to the professionals. I'm hoping, maybe naively that the L322 will be similar. Maybe be able to reset EAS and suchlike with an icarsoft or similar?an be an a
When I decided to change my Classic for the P38 I heard all the horror stories and was told to avoid them like the plague and keep the Classic. Wondering now if I should keep the P38 for another 16years or take the plunge.

Click to expand...

Th electronics in the L322 can be an absolute nightmare compared to the relatively simple P38. Having experienced the problems a friend had with one, I wouldn't have an L322 as a gift except perhaps to sell it.
Nanocom is the best diagnostic tool for the P38 and the free EAS software from RSW for the EAS.

Ok, I've gone off the L322 idea so old Reggie the P38 Rangie is safe for the minute. Still fiddling with the RSW unlock suite and still strange happenings. My Heights according to the RSW are: NSF 185, OSF 159, NSR 191, OSR 105. Yet the OSR is actually 10 mm higher than the others. Looks like a duff OSR sensor? Also the unlock suite seems to lose the return signal and sometimes freezes so I have to shut the computer down and start again.
Thanks for your patience

Spridget said:

Ok, I've gone off the L322 idea so old Reggie the P38 Rangie is safe for the minute. Still fiddling with the RSW unlock suite and still strange happenings. My Heights according to the RSW are: NSF 185, OSF 159, NSR 191, OSR 105. Yet the OSR is actually 10 mm higher than the others. Looks like a duff OSR sensor? Also the unlock suite seems to lose the return signal and sometimes freezes so I have to shut the computer down and start again.
Thanks for your patience

Click to expand...

Are those figures from the heights tab in the EAS software or the get heights in the calibration tab?

If those number are real, then either car is reaching for the sky, or the sensors are very wrong. Could also be duff values if RSW is not communicating properly.

Expected value ranges:

Suspect it's the latter. The readings are from the heights tag. The car is sitting more or less where it always is on the standard height with just the OSR a touch higher, hardly noticeable without the use of a tape measure. I tried to get a set of readings at all heights but kept losing the return signal. Readings from the Calibration tag, last time I got a decent reading for OSR were 90,100 120. didn't record access mode.
I've been promised an old laptop with a DB9 Serial port so if it materialises we'll see what it says.
Thanks for the replies.
Pete

Personally I would make up some calibration blocks from dowel (see Technical Section) and take the readings for each height. Average the reading across each axle and program them in.

Grrrrrr said:

Personally I would make up some calibration blocks from dowel (see Technical Section) and take the readings for each height. Average the reading across each axle and program them in.

Click to expand...

That equals a lot of hard work moving the car up and down to get the different height dowels in. Much easier with a measuring stick, adjust the 4 corners to the required height, read the heights and enter in the calibration tab, start at wade height and repeat for each level.

Grrrrrr said:

Personally I would make up some calibration blocks from dowel (see Technical Section) and take the readings for each height. Average the reading across each axle and program them in.

Click to expand...

Datatek said:

That equals a lot of hard work moving the car up and down to get the different height dowels in. Much easier with a measuring stick, adjust the 4 corners to the required height, read the heights and enter in the calibration tab, start at wade height and repeat for each level.

Click to expand...

tried both of these methods and the stick referencing is a good way using the info on the nanocom. The dowels do help to base line everything as a starting point.

I would be deliriously happy if I could just get the computers to stop sulking and talk to each other in a civilised manner. Tried again today after reloading drivers and checking OBD connections. I get good idle for about 20 seconds then the RX column goes all to rat's s&!t.
I have a Grandson who professes to know about these things and I will be interrogating him tomorrow as soon as the turkey and tinsel bit is done. Also the promise of an old laptop with Windows XP is pending.
Merry Xmas everyone.

Datatek said:

That equals a lot of hard work moving the car up and down to get the different height dowels in. Much easier with a measuring stick, adjust the 4 corners to the required height, read the heights and enter in the calibration tab, start at wade height and repeat for each level.

Click to expand...

Didn't take me long although I did have a helper. Took a photo of yhe readings at each height with the dowels in.

At last I managed to get a consistent good idle. As suggested in this post the problem seems to have been drivers. I disabled the automatic Windows update and downloaded the driver that came with the unlock suite. Did this several times before but for some reason it works now. Tweaked the OSR Height and it's spot on now.
Thanks for the help

Spridget said:

View attachment 280482
At last I managed to get a consistent good idle. As suggested in this post the problem seems to have been drivers. I disabled the automatic Windows update and downloaded the driver that came with the unlock suite. Did this several times before but for some reason it works now. Tweaked the OSR Height and it's spot on now.
Thanks for the help

Click to expand...

Good result

looking at the readings they are a bit out you should have either side within one or two bits so its time to get adjusting

brianp38dse said:

looking at the readings they are a bit out you should have either side within one or two bits so its time to get adjusting

Click to expand...

As far as I know, 5 bits across the axle is permissible