AJKS

Paul,

Im just about to start mucking around with the necassary ADC for dealing with an external temp sensor. Mine will be configured for a Autometer sensor if thats at all useful to you.

adam

edited to add:
Oops. I just remembered that you dont have the source code so my ADC code wont be much use to you.

adam

[Edited by AJKS - 5/21/2003 4:23:38 AM]

AndrewC

Paul,

I am currently tinkering with temp sensors again, and will have some code to support both thermocouples and an oil temp sensor, probably the Greengauges/Caerbont/Smiths one ('cos it's cheap).

Mickey,

I haven't had a reply from my last 2 emails to you?

Andrew...

StickyMicky

last email was the one were u said u were collecting parts for the kits, ive had none scince then

greasemonkey

Just thought I'd bring this one back to the top, and at the same time ask if anyone was having any luck mapping the dumps of the MY99/00 era ECU's...

Scooby New

iTrader: (2)

Any news on a MY99/MY00 version???

greasemonkey

Going to have a crack at mapping the 99/00 ECU's output myself, unless someone else manages it in the meantime.

Will keep Andrew up to date with whatever I find out, so with a bit of luck (and some spare time), your wish, Cinderella, will come true

ozzy

I was very interested in this when Andrew first spoke of it and even more disappointed he when he didn't have time to take it further.

Would've had a go myself if I knew anything about electronics.

AFAIK, the only people to have cracked this are the PSI folk, but haven't heard of any DIY'ers.

Stefan

dnb

AFAIK no DIYers have done the MY99. It's still on the list of things to do for me to look at, but I've been working on pre97 things - at the moment a laptop based deltadash style utility that's very nearly finished.

steve_nairn_sti

dnb,

if you get the chance, could you mail me when you have that nailed please.

I'd be more than interested in going for that if you start producing them!

Cheers

dnb

will do. I know I keep saying it, but it won't be long!

StickyMicky

ohh i rember this post

well i finaly got my kit sorted out and wired up and its mint!

although that reminds me, maplins still havnet sent me my led for the shift light yet grrrrr

Paul_M

Sticky what kind of LED are you using for the shift light, just a bog-standard one? I have a normal 5mm red LED in the corner of the box but it's pretty useless there - you need to be looking at the box to see it and at 6500RPM with the boot down that's the last place you want to be looking .

I'm thinking of rigging up a Defi warning light or something like that although it's way overpriced for what it is IMO. Maybe just stick a blue LED somewhere prominent since they're very eye catching.

Finally what do all the figures mean in the logs? Here's a sample of a few lines from mine:

4240,176,53,105,138,34,80,135,49,20,147,36,37,40,1 ,119,133,128,94,120,133,216,22,

4604,176,53,106,139,34,79,134,49,21,148,36,35,40,1 ,127,133,128,94,117,133,216,22,

4970,176,52,106,139,34,79,134,49,20,148,35,1,40,1, 133,133,128,94,116,133,216,22,

5336,175,53,106,139,34,79,134,49,19,148,35,34,40,1 ,126,133,128,94,116,133,216,22,

I know the first value is some kind of time increment but the rest I've no idea! I've added a blank line between each to make it easier to read.

Well happy with mine, hoping to get it mounted somewhere more permanent soon though (DIN hole?) so I don't need to keep hiding the box for fear of tea-leafs taking a fancy to it!

StickyMicky

ooo a blast from the past post
well my led was actualy deliverd a few days ago as the one i was after was on back oder (for like over a month )

i tried it and had no joy, i tested it and it doesnt work
cant be botherd to order another one now lol, not even worth sending it back, next time im in town ill pick one up there, the one i orderd was a super brite clear to green one, i think it was 5mm

not sure on the data logs and i never use mine for logging
i normally use mine to monitor boost preasure, afr, maf values and knock correction, had a problems with the car a few weeks back while i was away down south and it was pretty reasuring to skip through the displays and check exactly what was up with the car, turned out it wasnt boosting properlly due to sum new red hose i had added while at a show, easy to sort out

StickyMicky

actualy sumthing iw as going to mail andrew c about is the afr readings, from memory he said it should be about 850 under load

mines normaly 815 but ive seen 835 a few times, does a lower reading mean its running leaner or richer?

Paul_M

Lower is leaner, it's best to correspond the readings with boost cos it should get richer the higher boost is to keep temps down. 850mV corresponds to around 12.5:1 and should be at least this much if you're at or near 1 bar. 870mV is around 11.5:1 which is maybe what you'd want if the boost goes over 1 bar held.

Remember though that the lambda isn't particularly accurate at these readings (narrowband) and also that it's very temperature dependant so it's best to run off-boost for a while so the lambda can cool in the lower EGTs then give it a good run and check the readings before it gets too hot again.

StickyMicky

ok thanks, my car holds 1.1 bar so im asume that its running a touch lean?

induction mods are limited to a pannel filter
center decat exhaust
and thats about it, bar the samco hoses and stuff

AndrewC

Hi guys, glad to see you making good use of the monitors.

I'll try to get the logging parameters and conversions on my website this weekend.

I haven't forgotten about it, just haven't had the time.

The first column is time in ms, watch out for it resetting though!

Andrew...

dnb

I'll make a guess at the conversion being as follows:

1st number is a time in milliseconds.

The rest (going from left to right) are the raw sensor values in the order presented in the parameter table on www.scoobymonitor.co.uk. Simply use the conversion shown in the right hand columns.

Just make an Excel sheet to do the conversions.

dnb

pointless error fixing post

JonDBM

Greasemonkey,

I would be very interested in MY99 decodes if / when you get around to doing them. Do you know the communications protocol for MY99? If I knew that I could start doing it myself as I have all the bits at my disposal at work.

Jon.

Graz

Likewise, I would be interested in how you get diagnostics out of MY99/00. I could understand this one, do lots of stuff with serial interfaces at work, but it's no good to me as I have a MY00.

I'm lead to believe that the MY99/00 ECU uses O.B.D.II protocol, but I'm not so sure that's what SECS / Delta Dash use to communicate as I'm sure I read somewhere that it doesn't update fast enough? Maybe some proprietry Subaru comms protocol is also available or you can switch the ODB.II protocol into a high speed mode? Still i'm just guessing. Then there is the small matter of interpreting the info... would it still be in the form of a memory dump like this version?

ozzy

AFAIK, the MY99/00 uses the Subaru Select Monitor protocol and not ODBII.

The hardware available for the MY97/98 that Andrew developed remains the same, you just need to know the addresses of all the maps and sensor values in the later ECU.

Stefan

Graz

Hmm....

If this is true could you not just spy on say Delta Dash, using a PC to monitor tx and rx on the serial interface. Ask it to read a specific parameter from the ECU and the watch to see which memory locations it accesses, what the values are and then translate this to what Delta Dash reads.

DD may grab the entire memory dump each time but only display the bits you ask for, in which case it is educated guess work trying to work out what memory location relates to what...

Graz

Also if this is true why don't they do a SECS version for older cars. If the same serial interface is used and the memory decode is in the public domain it would be very easy for them to produce a version for pre 99 ECUs.

Confused...

Graz

Found some info here as to why DD doesn't work with pre MY99 cars. Apparently the protocol / interface is different, but it isn't OBD-II even though the ECU supports it.

greasemonkey

Graz, Ozzy, John (and others), yes, you could use a sniffer to monitor a DeltaDash or Select Monitor session, but that would be cheating (and in any case, I don't have a DD).

I've been up against a brick wall trying to get any reply from the ECU through pins 12 and 13, as per the older cars. Zilch, no matter what combination of baud rate/framing/command format I try.

I've found a snippet of info that implies the comm happens on a half-duplex basis through pin 7. This pin should be ISO style OBD, but I'm not sure yet whether the protocol used on the 99/00's is ODB, Subaru, or something in between.

I've been too busy to actually try it as yet, but with a bit of luck this'll happen over the weekend, as I've got the bits to build an opto-isolated level converter, just need the time to put it together and experiment.

As/when I find something, I'll post the details up here.

[Edited by greasemonkey - 7/25/2003 4:25:58 PM]

JonDBM

I was under the impression that the hardware AndrewC developed would not just plug straight into MY99/00 otherwise I would have done it by now! I thought it used a different protocol that no-one but DD or SECS seem to know. Of course, I could be completely wrong.

Jon.

ozzy

My understanding is Andrews hardware can be used to plug into a MY99/00. The problem is the coding on Andrew's Atmel chip is for the MY97/98 protocol. This is different to the MY99/00 cars. It's not a different version of OBDII, it's just a newer version of Subaru's select protocol with all the ECU area's being completely different.

You could build Andrew's device, plug it in but it won't work coz the programming's all wrong.

Stefan

Paul_M

If it were OBD-II it would work on all the ECUs that support that protocol because it's a standard designed to be accessible by all manufacturers of reading equipment (to break the monopoly of car manufacturers on fault reading equipment).

Unfortunately a lot of the classic shape don't use OBD-II and anyway it's a lot slower and provides less information than select protocol. So all the stuff we have available for Subaru uses select protocol, which changes between ECU versions.

Anyway I don't have a clue about the actual protocols itself so I'm just glad that others have cracked it and made it available to the rest of the community.

Back to the shift light thing, I decided to order a 10mm super-bright red LED which I can place right on the steering column shroud to make it slight more visible . Will take some pics when it's done.

Also the logging parameters, I'm pretty sure they aren't in the order the list is given in the scoobymonitor page cos looking at my log it just doesn't fit properly - for example the coolant temp is going up and down continually when in reality it starts low and builds up to around 90deg where it settles and stays within a few deg. Other things just don't match up so I'll wait for the info to be posted.

greasemonkey

Stef, if my information is correct, Andrew's hardware won't work on a 99/00 without modification, even with the appropriate code, as the information is carried on a different pin in the DLC plug, and its electrical properties are different.

If the comm is indeed done on pin 7, instead of 12/13, you'll need an intermediate interface to handle the single pin Tx/Rx, and also to convert the 0-12v voltage swing to TTL.

This is all a big "if" though. Am building the interface now, so more later hopefully!

[Edited by greasemonkey - 7/25/2003 6:44:44 PM]