pcmhacking.net

Dylan wrote:Can you recomemnd a good elm device? Post a link up to one you would buy?

Ahhh, ill have a search through fleabay from something that looks somewhat reliable.
I buy direct from manufacture so I bypass the "dodgy" china salesmen, although at a minimum bulk purchase of 150pieces its not suitable for the average joe.

*Edit
Scrolling through the ebay listings and feedback, its all the same chinese shiz. Its more of a "pick and hope" type situation.
But, generally/hopefully, you should be safer with elms that are more than $12aud + shipping. When you start buying cables at $3-6.. thats when parts and manufacturing starts gettign really dodgy and they will be older versions or will work intermittently, so steer clear of "Ebay Specials". Iv bought a few off ebay.. umm from the names I remember.. tomtop was a bit iffy (ebay special king), mallzon (something like that) has a few dead units out of 20 and werent all the same version. Just scroll through their feedback and look for any elm cables issues.

As for bluetooth devices.. they are literally a HC-05 bluetooth module mashed with an ELM327 chip.. which are not 100% compatible.. well.. it needs a middle man to process the messages between devices appropriately hence changing the baud rate freaks then out! But again, I would steer clear of "Ebay Specials".

For speed and reliability, purchase one of the $15 from an Australia seller, and harass them (yes I do mean it!) to make sure the unit is working and is the correct version prior to being sent. Should have it within a few days instead of a few weeks from china!

Dylan wrote:Can you recomemnd a good elm device? Post a link up to one you would buy?

BuyInCoins_au ensured me that it is v1.5 and all cables have been tested and working. This could just be all words. But, has a huge backing of purchases with minor previous issues. Make sure to choose the usb version:
http://www.ebay.com.au/itm/USB-Bluetoot ... 2c78e2abd1

I have a obdlink mx Bluetooth device which doesn't seem to work on this software, but it does on your old obd2logger v023.

[07:57:05:181] Attempting to Connect to Comport...
[07:57:05:196] Searching for Device...
[07:57:10:397] Problem with comport: COM3 at baud: 9600
[07:57:15:554] Problem with comport: COM3 at baud: 38400
[07:57:19:663] Testing Comport: COM3 at Baudrate: 57600
[07:57:20:726] Testing Comport: COM3 at Baudrate: 115200
[07:57:21:007] ELM Device Successfully Found!
[07:57:21:007] Requesting Fast 115200 Baud..
[07:57:21:023] ELM Device Accepted New Baud Timeout
[07:57:21:054] ELM Device Accepted Baud Change Command, Checking Communications..
[07:57:21:273] ELM Device Sent ID frame..Responing with CR
[07:57:21:288] ELM Device Accepted Baud Change Command!
[07:57:21:288] Disabling Echo...
[07:57:21:304] Echo Disabled Successfully!
[07:57:21:304] Disabling LineFeed...
[07:57:21:304] LineFeed Disabled Successfully!
[07:57:21:304] Enabling Headers...
[07:57:21:320] Headers Enabled Successfully!
[07:57:21:320] Allowing Long Frames...
[07:57:21:335] Long Messages Enabled!
[07:57:21:335] Setting Timeout...
[07:57:21:335] Timeout Set Successfully!
[07:57:21:335] Setting VPW Protocol...
[07:57:21:351] Protocol Set Successfully!
[07:57:21:351] Setting VPW Headers...
[07:57:21:351] Custom VPW Headers Set: 6C10F1
[07:57:21:351] Checking Input Voltage..
[07:57:21:366] Voltage Found!
[07:57:21:366] Connection Established!
[07:58:18:604] Getting Device Information...
[07:58:18:635] ELM Device Successfully Found!
[07:58:18:635] Checking Input Voltage..
[07:58:18:651] Voltage Found!
[07:58:23:198] Requesting Protocol..
[07:58:23:229] Protocol Found: SAE J1850 VPW
[07:58:23:245] Requesting Protocol Number..
[07:58:23:245] Protocol Number Found: 2
[07:58:23:245] Read Completed!
[07:58:25:448] Setting VPW Headers...
[07:58:25:495] Requesting VIN..
[07:58:25:526] VIN Part1: 6C F1 10 7C 01 00 36 47 31 59 4B C2
[07:58:25:604] VIN Part2: 6C F1 10 7C 02 34 32 46 33 43 4C 12
[07:58:25:667] VIN Part3: 6C F1 10 7C 03 39 32 32 35 39 30 9A
[07:58:25:714] VIN Read Completed!
[07:58:25:714] Reading OSID..
[07:58:25:745] OSID: 6C F1 10 7C 0A 00 13 AF 15 E3
[07:58:25:807] OSID Read Completed!
[07:58:25:807] Reading PCM#...
[07:58:25:839] PCM#: 6C F1 10 7C 04 00 F7 81 C2 52
[07:58:25:885] PCM# Read Completed!
[07:58:35:573] Closed Comport!

Tre-Cool wrote:I have a obdlink mx Bluetooth device which doesn't seem to work on this software, but it does on your old obd2logger v023.

[07:57:05:181] Attempting to Connect to Comport...
[07:57:05:196] Searching for Device...
[07:57:10:397] Problem with comport: COM3 at baud: 9600
[07:57:15:554] Problem with comport: COM3 at baud: 38400
[07:57:19:663] Testing Comport: COM3 at Baudrate: 57600
[07:57:20:726] Testing Comport: COM3 at Baudrate: 115200
[07:57:21:007] ELM Device Successfully Found!
[07:57:21:007] Requesting Fast 115200 Baud..
[07:57:21:023] ELM Device Accepted New Baud Timeout
[07:57:21:054] ELM Device Accepted Baud Change Command, Checking Communications..
[07:57:21:273] ELM Device Sent ID frame..Responing with CR
[07:57:21:288] ELM Device Accepted Baud Change Command!
[07:57:21:288] Disabling Echo...
[07:57:21:304] Echo Disabled Successfully!
[07:57:21:304] Disabling LineFeed...
[07:57:21:304] LineFeed Disabled Successfully!
[07:57:21:304] Enabling Headers...
[07:57:21:320] Headers Enabled Successfully!
[07:57:21:320] Allowing Long Frames...
[07:57:21:335] Long Messages Enabled!
[07:57:21:335] Setting Timeout...
[07:57:21:335] Timeout Set Successfully!
[07:57:21:335] Setting VPW Protocol...
[07:57:21:351] Protocol Set Successfully!
[07:57:21:351] Setting VPW Headers...
[07:57:21:351] Custom VPW Headers Set: 6C10F1
[07:57:21:351] Checking Input Voltage..
[07:57:21:366] Voltage Found!
[07:57:21:366] Connection Established!
[07:58:18:604] Getting Device Information...
[07:58:18:635] ELM Device Successfully Found!
[07:58:18:635] Checking Input Voltage..
[07:58:18:651] Voltage Found!
[07:58:23:198] Requesting Protocol..
[07:58:23:229] Protocol Found: SAE J1850 VPW
[07:58:23:245] Requesting Protocol Number..
[07:58:23:245] Protocol Number Found: 2
[07:58:23:245] Read Completed!
[07:58:25:448] Setting VPW Headers...
[07:58:25:495] Requesting VIN..
[07:58:25:526] VIN Part1: 6C F1 10 7C 01 00 36 47 31 59 4B C2
[07:58:25:604] VIN Part2: 6C F1 10 7C 02 34 32 46 33 43 4C 12
[07:58:25:667] VIN Part3: 6C F1 10 7C 03 39 32 32 35 39 30 9A
[07:58:25:714] VIN Read Completed!
[07:58:25:714] Reading OSID..
[07:58:25:745] OSID: 6C F1 10 7C 0A 00 13 AF 15 E3
[07:58:25:807] OSID Read Completed!
[07:58:25:807] Reading PCM#...
[07:58:25:839] PCM#: 6C F1 10 7C 04 00 F7 81 C2 52
[07:58:25:885] PCM# Read Completed!
[07:58:35:573] Closed Comport!

Yeah it does alot more than the above now, it reads out the faults, freeze data and supported PIDs before saying "connected". You can bypass this process by unticking "read engine info on start up". Can you post a log using the current software to see where it going wrong?

Im not home yet, but when I tested it this morning I unticked all the box's and it just sat there.

I had to kill the program in the end. It seems to be talking on some level as the Bluetooth link is active.

my pcm is on a bench harness too, so no other comms will be getting in the way.

Alright no worries, sounds like a major glitch so would definately like to see what's happening to fix it up!

Tazzi wrote:Alright no worries, sounds like a major glitch so would definately like to see what's happening to fix it up!

im home now and forgot that I left it connecting.. so 10hrs later and no connection. lol

anything I can provide to help sort it out?

same problem even with an elm 1.3 cable I use to get ls1 seed keys with the planethax tool.

[18:24:31:161] Attempting to Connect to Comport...
[18:24:31:177] Searching for Device...
[18:24:31:239] Testing Comport: COM5 at Baudrate: 9600
[18:24:31:474] ELM Device Successfully Found!
[18:24:31:489] Requesting Fast 115200 Baud..
[18:24:31:521] ELM Device Accepted New Baud Timeout
[18:24:31:552] ELM Device Accepted Baud Change Command, Checking Communications..
[18:24:31:802] ELM Device Sent ID frame..Responing with CR
[18:24:31:817] ELM Device Accepted Baud Change Command!
[18:24:31:817] Disabling Echo...
[18:24:31:833] Echo Disabled Successfully!
[18:24:31:833] Disabling LineFeed...
[18:24:31:849] LineFeed Disabled Successfully!
[18:24:31:849] Enabling Headers...
[18:24:31:864] Headers Enabled Successfully!
[18:24:31:864] Allowing Long Frames...
[18:24:31:880] Long Messages Enabled!
[18:24:31:880] Setting Timeout...
[18:24:31:896] Timeout Set Successfully!
[18:24:31:896] Setting VPW Protocol...
[18:24:31:911] Protocol Set Successfully!
[18:24:31:911] Setting VPW Headers...
[18:24:31:927] Custom VPW Headers Set: 6C10F1
[18:24:31:927] Checking Input Voltage..
[18:24:31:942] Voltage Found!
[18:24:31:942] Connection Established!

again from the old obdlogger software

Tre-Cool wrote:

Tazzi wrote:Alright no worries, sounds like a major glitch so would definately like to see what's happening to fix it up!

im home now and forgot that I left it connecting.. so 10hrs later and no connection. lol

anything I can provide to help sort it out?

What does it say in the console log tab? It should indicate where its stuck.

Very curious with it though.. thought I had timeouts in send/receive functions as a failsafe.. so somethings gone wrong there.

Tazzi wrote:

Tre-Cool wrote:

Tazzi wrote:Alright no worries, sounds like a major glitch so would definately like to see what's happening to fix it up!

im home now and forgot that I left it connecting.. so 10hrs later and no connection. lol

anything I can provide to help sort it out?

What does it say in the console log tab? It should indicate where its stuck

Stuck at searching for device on both.

update- seems if u leave the reset device to default settings it freezes up. but is working for both cables now

Hmmm.... not sure why it freezes up? I think its because of the way bluetooth works.. its "slower" as Iv found with testing. The "auto detect" runs through each comport really quickly to identify if it is valid. It also runs through all main baud rates.. which might be why it froze up?