OBD MPGuino gauge

[Keeper]

Hello
I have uncommented line 201
# define ELM
and comment lines: 210, 217, 228
/ / # define ISO_9141
/ / # define ISORequestByteDelay 5
/ / # define ISORequestDelay 55

The compiler shows the error:
obduino_code.cpp: In function 'boolean get_pid (byte, char *, long int *)':
obduino_code: 1786: error: 'ECUconnection' was not declared in this scope
obduino_code.cpp: In function 'void config_menu ()':
obduino_code: 3440: error: 'str' was not declared in this scope
obduino_code.cpp: In function 'void needBacklight (boolean)':
obduino_code: 4284: error: 'ECUconnection' was not declared in this scope
obduino_code.cpp: In function 'void loop ()':
obduino_code: 4626: error: 'ECUconnection' was not declared in this scope
obduino_code: 4727: error: 'ISO_InitStep' was not declared in this scope
obduino_code.cpp: In function 'void get_engine_on_time (char *)':
obduino_code: 5132: error: 'ECUconnection' was not declared in this scope


This code is taken from the site Google

If you cancel the changes - there are no errors.
If possible, tell me how to configure to work with the ELM.
Thank you.

[eimix]

what version did you used?

if using obduino32K (rev198) - try commenting "#define useECUState" line 218

if using obduino32K_graphic - (rev200) had error, fixed in rev201
you have to comment "#define useECUState" too.

I see in code many comments that ELM should be tested - so it needs more tests and some debuging and fixing, good luck.

[Keeper]

OK.
Compiling passed without errors. (obduino32K_graphic, rev 201)
21.03.2012 ordered ArdinoMega1280
Waiting until the fly. This is about 3 weeks.
I'll be a tester ELM

[Bix]

My car's OBD2 (Toyota corolla 2002 aus) has pins 6 and 14 populated, which by diagrams is supposed to be locations for CAN high and CAN low. Its also got pin 7 populated supposedly for the K line - I have not seen any mention of CANbus on corollas.

Is there any way of telling what these pins actually are? Ive got a scope I can hook up to it.

[toc]

Is there any way of telling what these pins actually are? Ive got a scope I can hook up to it.

You can check that they are actually "CAN" pins by getting your multimeter out and checking what voltage you get from Pin 6 to 4/5 (ground), and PIN 14 to ground

CAN will be a balanced 2.5V line (so it'll go 2.5/2.6 on one side and 2.4 the other).

The K-Line pin could be there for either - Obsolete or for other ECUs.

An ELM327 scanner could help determine which protocol is in use.

[Bix]

Hmm getting about 11 volts from both those pins. Guess its not can then.

[Bix]

Hooked it up to a ELM scanner, none of the programs could detect the protocol...

I connected the K line to an oscilloscope and got a constant 12v out, no evidence of a digital signal on any of the pins on the connector. Do I have a dud OBD or what...

[toc]

I connected the K line to an oscilloscope and got a constant 12v out, no evidence of a digital signal on any of the pins on the connector. Do I have a dud OBD or what...

OK - that's strange, the ELM should at the least generate some signals on the K-Line in Auto mode.

The line does actually idle high too.. do you have enough resolution on your oscilloscope to see what might be minor changes?
What software did you use to command the ELM whilst the oscilloscope was attached?

(There won't be any change on those pins without a scan tool communicating).

[Bix]

What software did you use to command the ELM whilst the oscilloscope was attached?

EasyOBDII. It read the port, read the scantool, done something with the bus but then got stalled trying to communicating giving an error of the car not being on. The car was on all times tested, and the engine was turned on for a few tests as well, with the same outcome.

do you have enough resolution on your oscilloscope to see what might be minor changes?

50 MHz, should be plenty.

(There won't be any change on those pins without a scan tool communicating).

Oh ok, I assumed it would send something even without it being initialised.

I tried the scantool on a holden Astra 2004, worked like a charm so its definitely not something wrong with the scantool.

[backsidesnap]

to whom may have an answer for me:
I have a mpguino and previously had it connected. It worked for like six months or so then crapped out like three years ago. I thought it was the wiring so I found new places and ran new wires to the correct places and still dice when I try and turn it on. My situation is that I know that DCB is wayyy backlogged and dont want to bug him so if some on could help me in the form of telling me where to buy the connectors to try and diagnose the guino myself, or...... this feed is so damn long I cant imagine sorting through the whole thing at this point. thanks