Paul_M

No worries... started that reply before you posted yours so you'll probably be able to get better components/prices.

As for the .bin file... not sure really! I've always compiled to hex when doing PIC stuff . Not sure if I need to convert it to hex first, I really haven't a clue with Atmel tools

Paul_M

BTW... (another reply to myself )

Might be an idea if you're using a bigger display to stay within the confines of a DIN space. Not sure if you have double-DIN over there but UK cars are single-DIN so I might convert to a double-DIN dash and use the space below to mount the display.

DIN blanking plates can be picked up for buttons and can be butchered as required. It would look factory and is an ideal place to put the unit if it grows much since I'm going to put the current 2x16 one where the ashtray goes but a bigger one won't fit there.

AJKS

Hmm, seen them before at that size. Ultimately I would like a 20x4 large font one with backlighting - but they're pricy!

see:
http://www.densitron.com/ (UK BASED)
http://www.eio.com/lcdprodt.htm
http://www.displaytec.com/Pages/Alphamumeric/Alphanumeric_Displays.htm

for other lcd stuff.

Adam

AJKS

Actually Im planning to have mine in 2 pieces: 1 box for the electronics (tucked away under the dash) and another slimline unit containing the display and buttons - which I will mount just above the gauges in direct viewing when on the track otherwise place it on the steering wheel stem (I may just use vecro pads for mounting - not too sure yet). I may even mount the buttons separately for easier access to them (hmm, where can I get one of those F1 style steering wheels from?!)

Adam

Paul_M

Interesting idea with the movable display and remote buttons. Still think I'd like my display to be fixed and look factory, but the buttons could be placed somewhere more accessible.

My dad has a Vectra (I know ) which has a trip computer display next to the dash and the buttons for that are on the end of the wiper stalk so you change the dispay with your right hand without taking it off the steering wheel - works a treat

I'll have a look at those display pages. I assume the ones you're after all comply with the same protocol?

AJKS

Yeh, the hitachi HD44780 is pretty much the industry standard - as long as you get one which is based on that (its actually the PCB driving the LCD - the 2 are normally sold as a integrated 'package') you can basically plug and play. Bascom is so simple to use to drive a LCD. I expect this to be a major effort, but with a high level language such as bascom life is simple - I never want to see assembler code ever again.

In Oz we have single DIN stereos on the pre bug eye WRX with the extra space acting as a empty bin - same as the UK, etc. I just want to be able to keep an eye on the data the whole time (especially lap times, temps and pressures).

adam

Adam

Paul_M

UK Cars don't have an empty bin as standard, there are some switches above the stereo and the hole isn't big enough for double-DIN. You have to change the console, as can be seen here. That's a LHD model but all the Euro cars are the same.

I still think it's probably the best way to integrate it if a bigger display is being used, as I'd prefer it nice and neat myself. Quite an easy job by the looks of it.

AndrewC

Hello all,

Sorry for not posting on here recently, been busy with other things, I'm just going to post a few bits of info, but will try to put more on my website as soon as I can.

1. There is (and always has been) an ATMega8 link on the hardware page to the Atmel (AVRFreaks is run by Atmel) overview page which has a pinout and a link the latest datasheet and app notes, I did this as I trust Atmel to maintain the info rather than me having to do it.

2. I cocked up with the switches, I originally used push-to-break, but changed to push-to-make and didn't change everything properly, I will upload a new parts list with each part referenced to the DT107 where applicable, I have a nasty feeling that the first binary I posted was built for push-to-break but I have changed that.

3. I will add pinout details for the RS232 connector, although this is shown on the PCB schematics on the DT107 page linked from my hardware page.

4. Current backlit LCD character displays are expensive, I went for the 2x16 as this was meant to be a cheap project, to me the display is only a small part of the device, the logging is equally as important. In the next few months I will be developing a version using a graphics LCD which is far more versatile and cost effective than large character displays. That version will also have on board logging which can be later downloaded via RS232, this will still use the DT107 and M8 chip.

5. The demo version of Bascom-AVR whilst limiting compilation to object code of less than 2K will allow programming of any size binary, I will add some instructions on how to do this.

6. Due to time contraints I don't think I am going to develop the monitor for MY99/00 ECUs.

I don't monitor this thread every day but I do try to answer my emails.

Andrew...

PS. Adam, I agree with your reasoning re. the Tx/Rx lines and will change my definitions.

AJKS

Cheers Andrew - and thanks heaps for all your effort. The TX/RX is always a bit confusing...

Aftermarket ECUs and the Select Monitor/protocol:
Does anyone know whether the aftermarket WRX ECU's are also Subaru Select Monitor compatible (ie respond to the Subaru diagnostic port commands)?

Im very curious as I have an Apexi PowerFC at home waiting to be fitted and tuned - but I dont want to do that until I have got this little project finished first. I really hope its not going to be a wasted effort if the PowerFC is not compatible...!!!

Adam

ozzy

Oh no ..................

Can anyone pick up the ball from Andrew? There's still loads of interest (inc. me) for those cars.

Andrew,

Would the hardware be the same with just the decodes for the ECU output being different?

Stefan

parso_rex

Adam,
let me/us know what displays you discover I'm particulalry interesested in a totally seperate display purely for anti theft reasons. I have been told by a couple of guys here to look for the ones with the extended temp module purely for operation in a hot environment don't kow if that is of any relevance.

Andrew, thats a pity about the 99/00 development but you've done an amazing amount of work so far on the 98. I simply don't know how anyone finds the time for a non commercial product. Will there be any chance of putting up any relevant addresses for the 99/00 on your site as thats what I'm playing with now : )
Oh yeah thanks for making me get back into some very basic programming its been a long while but worth it.....

Regards Mark


http://home.iprimus.com.au/surfleague/index.htm

Paul_M

I'm getting close... finally got the chip programmed after a bit of playing around with the Bascom software. The programmer you need to select is "Sample Electronics AVR" this one will work with the Kanda port. My Mega-8 is now downloaded and verified.

Just need to connect 4 wires into the car's OBD socket tomorrow, hopefully it's not pi55ing down Then fingers crossed I'll get some diagnostics

Nice work once again, looking forward to this in action!

AJKS

Mark,

Ill let you know what LCD I choose (and where I get it from) - might be a couple of weeks though. Re the heat; yeh, I am definitely trying to find ones that should be ok inside a car all day - especially considering some of the hot days we've been having this summer (even Melbourne!!:35degC plus) - probably doesnt apply to the UK fellas though!

Adam

Paul_M

Hmm a bit of stumbling on the "testbench" stage! Do you have to jumper pins 1 and 2 of JP2 to allow the output of the voltage regulator to be connected? I'd imagine so but want to be sure.

Also I'm using a 78L05ACZ regulator, which is a 0.1A in a TO92 package (like a small transistor). It seems the simmstick is designed for this type of regulator, but Andrew's design uses a 78M05CV which is a 0.5A in a P1d package (bigger). Is the extra current required, I'd guess so for the display but how do you get it to fit onto the holes in the PCB?

bruce

iTrader: (5)

I added the link to JP2 1-2 to get the 5v from the regulator to the IC's, Andrew also suggested that I add a link at JP4 1-2 so that the board can be used as a programmer. I added flying leads to connect my regulator.

AndrewC

Paul,

If you're driving the LCD backlight from the DT107, a 0.1A reg is not not enough, 0.5 is better but you may still need a heatsink depending on how enclosed it is, it is not a bad idea to drive the LCD from a different regulator for noise reasons although if you're not using the ADCs this isn't really an issue.

I am going to upload a new binary today, I suggest you use this one.

Temp measurements are good, I actually have another unit, very similar to the scoobymonitor but running different code, which displays various temps, I am currently using LM335Zs and a oil temp sender, when I get the time (or someone else does it) I would like to use K-type thermocouples.

Andrew...

Paul_M

Cheers mate, will get the code updated and the regulator swapped out. Still waiting on my 0.5A reglator from Maplin though cos they were out of stock when I ordered .

Only worry I have is the wiring - the 4 core cable you listed is very thin, its rated current is 0.25A per core. Will the device draw any more than 0.25A and can the select monitor port provide that current OK?

Finally any chance of an idiot's guide to what colour wire goes to what pin in the OBD connector? I've used the same wire colours you did (red +12V, blue GND, green TxD, yellow RxD) but the stuff about TxD and RxD has me confused, and I'm not sure whether blue goes to chassis GND or signal GND. This is the one part I don't wanna stuff up or it's bye bye ECU . I have the OBD-II connector under the steering wheel BTW.

AJKS

Paul,

I can answer that for you.

ODB Pin16 = ECU +12V -> ECU Monitor PWR In (RED)
ODB Pin4 = ECU CHS GND -> ECU Monitor GND (BLUE)
ODB Pin12 = ECU RXD (0V) -> ECU Monitor TXD (5V) (GREEN)
ODB Pin13 = ECU TXD (5V)-> ECU Monitor RXD (OV) (YELLOW)

The RXD/TXD voltages will be for when the Selector Monitor is NOT plugged in.

Dont (necessarily) trust me about the ECU Monitor TXD/RXD lines. I haven't built Andrew's kit so I cant guarantee this. BUT (from looking at his code) just ensure that (what I have called: ECU Monitor TXD) is connected to PORTD.2. I am sure pin12=ECU RXD and pin13=ECU TXD though.

Dont worry, the ECU wont blow up if you muck up the TXD/RXD connection. Trust me - I was doing this for over a month!!

If you are unsure, turn your car on, provide power and GND to the ECU monitor but DONT plug in the TXD/RXD lines. Now measure voltages present at all 4 TXD/RXD's and check against those I've listed above.

Adam


[Edited by AJKS - 1/15/2003 1:02:41 PM]

Paul_M

Thanks Adam. Unfortunately we have a thunderstorm up this neck of the woods at the moment so installation into the car will have to wait .

Just hope Maplin get their finger outta their *** and get my 0.5A regulator pretty soon!

buzzerboyroy

ok
i am a maintainence eletrician and you have all lost me!!!!!!!!!!!

just a few simple questions,


is this project ever going to cover the 99/00 model????

why is there a difference???

shurely it cant be that difficult????

i long for one of these monitors in my car,i even have friends that are extreemly interested in it.

Paul_M

There's a difference because MY97/98 and MY99> have different ECUs so the locations of all the required data are different. Similarly you can't get an Ecutek remap for a MY97/98 only MY99> models so it's swings and roundabouts!

It depends on whether someone with the time and knowledge develops it for MY99>. Failing that I'd suggest the commercial offering from www.psi3.co.uk which is currently shipping for MY99/00 cars.

buzzerboyroy

aahhhhh
now i know
many thanks paul,i hope someone can do it!!!!!
i will keep looking on here for futher info

cheers
roy

AndrewC

Decoding the newer ECUs isn't that hard as long as you've got the time and the patience to do it, I sadly, have limited amounts of both

Anyone with access to the relevant ECU and a little electronics/systems engineering knowledge could do it, a select monitor and a logic analyser is also useful.

Andrew...

buzzerboyroy

i wish i could help!!!!
i can get hold of the new type select monitor but thats about it,
sorry.

abradley

TTL to RS232 converter... I know making it is half the fun, but I want to 'cut to the chase' of decoding that ECU!

Would http://www.bb-elec.com/product.asp?sku=232LPTTL&dept_id=161 do the job?

Adam

AJKS

Hmm dont know. But a RS-232 circuit to build (for ecu comms) can be found here:

http://lillith.sk.tsukuba.ac.jp/~kas...r/subarusm.pdf

(you can use an Atmel chip if you dont want to use a PIC)

adam

abradley

Now I have my cable (though I still have to confirm this is
working!), I'm looking at writing some Java code to help me with the address decodes. I'm using the comm.jar package on Windows 2000 to allow me to hit the serial port, and wonder if 1953-8-E-1 is the COM port setup I should be targeting?

I've had to de-compile, modify, and recreate the comm.jar file (in
order to include the 1953 baud in the list of 'valid' baud rates -
otherwise the application throws a Java exception).

After compiling the application and running it, issuing the "MODE
COM1" returns BAUD 1953 8 Data bits etc etc so setting the COM port to this rate through Java _seems_ to be working!

I did try and connect the cable to the car and used a 3rd party
application - RS232 Hex Com Tool (trial at http://www.viddata.com)
- that has the ability to connect at non-standard baud rates.

The port opens successfully, and it would seem I received some kind of response from the car. A periodic "00" and some almost random data - noise? - when disconnecting the cable.

Running the Java application returns similiar results.

Any ideas?

Paul_M

Sorry that lot means nothing to me

I'd just like to confirm what adam wrote earlier regarding wiring connections to OBD-II port:

These are spot-on, my monitor is working a treat although it's proving to be quite a danger with me trying to watch my boost levels and IDC with the foot to the floor in 4th . Time to get the laptop into the car and logging set up.

Many thanks to Andrew for both designing the monitor and making it available to all, and also for loads of individual help in getting mine going. Thanks also to the other contributors in this thread, I reckon with all the knowledgable peeps chipping in there's loads more potential for this device yet.

cswminty

Adam - i am very interested in this indeed but iv'e got an APEXi power FC unit ready to be fitted and tuned. Just wondered if you had managed to test the two bits of kit together yet ???

Chris.

ScoobyDuck

iTrader: (1)

if the Apexi is only controlling the boost solenoid, the ScoobyMonitor would still be able to log the results that the ECU see from it's sensors.

However, if it's one that sits inbetween the sensors & ECU & fools the ecu, then the only data you would get would be the fooled response from the Apexi. so that wouldnt be of much use for fueling etc - but the ScoobyMonitor would still be able to monitor alot more!

Steve