pcmhacking.net

Posted: **Tue Sep 24, 2013 1:13 pm**

when you look at the number of different circuit boards and layouts in the chinese cables i would assume some will require differing solutions.some have 2 crystals some one and other componants.and some will be real elms

Posted: **Tue Sep 24, 2013 3:54 pm**

Not being a computer wizkid like most of you blokes I have been doing a bit of discovery learning. With the com port it's set at 9600 but when I use OBDwiz it links to the ELM unit at 115200. I am wondering if OBD2logger needs to have the ability to set the baud rate to 115200 to allow it to link the the ELM.

Posted: **Tue Sep 24, 2013 5:11 pm**

antus wrote:Im not sure you can rely on the interface running at the same speed by default - i think that may also be the problem with the elm adx. You might need to try 9600, 38400, 57600 and 115200 and try and init it at each speed or something like that and run at the speed you get an answer with.

ohh... I didnt realise that! Ill try adding 57600 and 115200, might be a trial and error type thing to see if it responds. Guess I could try and loop through to try them all out until it gets a response.
Iv based it off the elm datasheet, says to set up at 38400.

delcowizzid wrote:when you look at the number of different circuit boards and layouts in the chinese cables i would assume some will require differing solutions.some have 2 crystals some one and other componants.and some will be real elms

Mm.. I figured they would all at least abide to the basic elm327 requirements as detailed in the fact sheet.

Charlescrown wrote:Not being a computer wizkid like most of you blokes I have been doing a bit of discovery learning. With the com port it's set at 9600 but when I use OBDwiz it links to the ELM unit at 115200. I am wondering if OBD2logger needs to have the ability to set the baud rate to 115200 to allow it to link the the ELM.

Cheers Charles, By the sounds of it, I need to add a few more baud rates to test out... Im betting that it will work at 115200!.

Im beginning to see why some software doesnt work with clones/other circuit boards, need to consider the different setups.

Will update soon!.

*Edit
Attached is new version. Including baud rates of 57600 and 115200.
Try selecting 115200 and see if it connects, Im wondering if the device prefers the higher bauds.

Posted: **Tue Sep 24, 2013 9:15 pm**

Was getting a bit cluttered, Added column list on left for navigation.

Still waiting on some good news on anything working!

Posted: **Tue Sep 24, 2013 9:38 pm**

It seems to connect at 38400 on my v1.5 clone.

[21:06:20:703] Attempting to Connect to Comport...
[21:06:20:876] Searching for Device...
[21:06:21:694] ELM Device Successfully Found!
[21:06:21:696] Checking ELM Status..
[21:06:21:697] ELM is Idle
[21:06:21:698] Disabling Echo...
[21:06:21:704] Echo Disabled Successfully!
[21:06:21:704] Checking ELM Status..
[21:06:21:705] ELM is Idle
[21:06:21:705] Disabling LineFeed...
[21:06:21:712] LineFeed Disabled Successfully!
[21:06:21:712] Checking ELM Status..
[21:06:21:713] ELM is Idle
[21:06:21:713] Enabling Headers...
[21:06:21:720] Headers Enabled Successfully!
[21:06:21:721] Checking ELM Status..
[21:06:21:722] ELM is Idle
[21:06:21:722] Setting Headers...
[21:06:21:730] Custom Headers Set: 686AF1
[21:06:21:731] Checking ELM Status..
[21:06:21:731] ELM is Idle
[21:06:21:732] Checking Input Voltage..
[21:06:21:745] Voltage Found!
[21:06:21:745] Checking ELM Status..
[21:06:21:746] ELM is Idle
[21:06:21:746] Connection Established!
[21:06:24:717] Getting Device Information...
[21:06:25:516] ELM Device Successfully Found!
[21:06:25:516] Checking ELM Status..
[21:06:25:517] ELM is Idle
[21:06:25:517] Disabling Echo...
[21:06:25:524] Echo Disabled Successfully!
[21:06:25:524] Checking ELM Status..
[21:06:25:525] ELM is Idle
[21:06:25:526] Disabling LineFeed...
[21:06:25:532] LineFeed Disabled Successfully!
[21:06:25:537] Checking ELM Status..
[21:06:25:538] ELM is Idle
[21:06:25:538] Enabling Headers...
[21:06:25:554] Headers Enabled Successfully!
[21:06:25:554] Checking ELM Status..
[21:06:25:555] ELM is Idle
[21:06:25:555] Setting Headers...
[21:06:25:563] Custom Headers Set: 686AF1
[21:06:25:564] Checking ELM Status..
[21:06:25:564] ELM is Idle
[21:06:25:565] Checking Input Voltage..
[21:06:25:577] Voltage Found!
[21:06:25:579] Checking ELM Status..
[21:06:25:580] ELM is Idle
[21:06:25:580] Connection Established!
[21:06:31:230] Getting Protocol...
[21:06:31:232] Requesting Protocol..
[21:06:31:248] Protocol Found: AUTO, ISO 15765-4 (CAN 11/500)
[21:06:31:249] Checking ELM Status..
[21:06:31:250] ELM is Idle
[21:06:31:251] Requesting Coolant Temp: 01 05..
[21:06:31:258] Protocol Number Found: A6
[21:06:31:259] Checking ELM Status..
[21:06:31:260] ELM is Idle
[21:06:31:260] Read Completed!

No luck reading engine data (timeouts) or DTCs (nothing happens) though.

I dont think the detected protocol can be right, its on my VPW pcm test bench, and the ecu is powered up.

Posted: **Tue Sep 24, 2013 9:46 pm**

Cheers for that! Good to see its semi working.. I can see Iv made a couple errors, which Ill fix up.. just stupid textbox updates by the look of it.. right at the end there. Should have send Requesting protocol number.. not coolant temp lol.

I havent added anything to the dtc buttons so that wont work haha. Needed to check if I could actually pull any data from the car first (engine data stuff)

And As for the engine data.. yeah, Im unsure on whats exactly output, Not sure if the header needs to be directed at the pcm(10 instead of 6A) to get info back of not.

Antus, yeah just noticed the protocol that it picked up... that definately doesnt look right!. The Protocol is set to automatic.. so might have to manually set it.. maybe thats why it didnt pick up the request to the pcm?

Posted: **Tue Sep 24, 2013 10:08 pm**

Oky Doky, fixed up my little textbox mistake.

And have now made it set the protocol to SP2, which is VPW.

Hoooopefully that will be enough to get engine data this time.. otherwise will need to start just displaying everything on the port after requesting to know exactly what is sent back.

Posted: **Wed Sep 25, 2013 8:28 am**

Still no good here. I only get timeouts with all baud rates on PC and laptop. When I look into devices it identifies the ELM and says it's working. I will try it connected to a car this arvo and see if it responds. I do know that all the software I have needs that connection to work.

Posted: **Wed Sep 25, 2013 8:53 am**

[08:16:42:107] Attempting to Connect to Comport...
[08:16:42:332] Searching for Device...
[08:16:43:150] ELM Device Successfully Found!
[08:16:43:157] Checking ELM Status..
[08:16:43:159] ELM is Idle
[08:16:43:165] Disabling Echo...
[08:16:43:171] Echo Disabled Successfully!
[08:16:43:171] Checking ELM Status..
[08:16:43:171] ELM is Idle
[08:16:43:171] Disabling LineFeed...
[08:16:43:177] LineFeed Disabled Successfully!
[08:16:43:178] Checking ELM Status..
[08:16:43:178] ELM is Idle
[08:16:43:178] Enabling Headers...
[08:16:43:184] Headers Enabled Successfully!
[08:16:43:185] Checking ELM Status..
[08:16:43:185] ELM is Idle
[08:16:43:185] Setting Headers...
[08:16:43:193] Custom Headers Set: 686AF1
[08:16:43:193] Checking ELM Status..
[08:16:43:194] ELM is Idle
[08:16:43:194] Setting Protocol...
[08:16:43:201] Protocol Set Successfully!
[08:16:43:201] Checking ELM Status..
[08:16:43:224] ELM is Idle
[08:16:43:224] Checking Input Voltage..
[08:16:43:242] Voltage Found!
[08:16:43:243] Checking ELM Status..
[08:16:43:244] ELM is Idle
[08:16:43:245] Connection Established!
[08:16:47:294] Getting Device Information...
[08:16:48:093] ELM Device Successfully Found!
[08:16:48:094] Checking ELM Status..
[08:16:48:094] ELM is Idle
[08:16:48:095] Disabling Echo...
[08:16:48:101] Echo Disabled Successfully!
[08:16:48:102] Checking ELM Status..
[08:16:48:102] ELM is Idle
[08:16:48:103] Disabling LineFeed...
[08:16:48:109] LineFeed Disabled Successfully!
[08:16:48:110] Checking ELM Status..
[08:16:48:110] ELM is Idle
[08:16:48:111] Enabling Headers...
[08:16:48:117] Headers Enabled Successfully!
[08:16:48:117] Checking ELM Status..
[08:16:48:118] ELM is Idle
[08:16:48:119] Setting Headers...
[08:16:48:126] Custom Headers Set: 686AF1
[08:16:48:127] Checking ELM Status..
[08:16:48:128] ELM is Idle
[08:16:48:128] Setting Protocol...
[08:16:48:135] Protocol Set Successfully!
[08:16:48:135] Checking ELM Status..
[08:16:48:136] ELM is Idle
[08:16:48:136] Checking Input Voltage..
[08:16:48:149] Voltage Found!
[08:16:48:150] Checking ELM Status..
[08:16:48:151] ELM is Idle
[08:16:48:151] Connection Established!
[08:16:56:601] Requesting Protocol..
[08:16:56:610] Protocol Found: SAE J1850 VPW
[08:16:56:611] Checking ELM Status..
[08:16:56:612] ELM is Idle
[08:16:56:613] Requesting Protocol Number..
[08:16:56:619] Protocol Number Found: 2
[08:16:56:620] Checking ELM Status..
[08:16:56:621] ELM is Idle
[08:16:56:622] Read Completed!

but no engine data comes back.

Posted: **Wed Sep 25, 2013 10:00 am**

antus wrote:but no engine data comes back.

hmm... Im at a loss then.

With headers turned on, and echo off. The response will contain the header 686AF1 then data, 41 0C XX XX XX XX ect.
In my receiving function, I look to check that the received messaged doesn't match the sent (echo), and that the sent frame isn't any of these : NO DATA, SEARCHING...,?, >, or nothing.

Might try putting a message on each to see if one of these is being picked up.. If the elms not happy with the command, it would have sent back a '?'. If told told to get info, it is meant to say "SEARCHING", which Iv made it look for that and display that elm is searching.

So if neither of those are occurring.. maybe Im sending it wrong? Its being sent as "01 0C" for engine RPM data.. Fairly certain it said it didnt matter if there was spaces or not, as they have done in there examples.

Alight, will update the headers, lets have them pointed directly at the pcm (10) instead of 6A. And will display if any of the other parameters ar found (?,>, Searching ect).

pcmhacking.net

Software On ELM Street - OBD2 Software Development

Re: ELM327 Software Development

Re: ELM327 Software Development

Re: ELM327 Software Development

Re: ELM327 Software Development

Re: ELM327 Software Development

Re: ELM327 Software Development

Re: ELM327 Software Development

Re: ELM327 Software Development

Re: ELM327 Software Development

Re: ELM327 Software Development