|
pellajl |
|
||
|
Has anyone used GLM Software's ODB 2007 application?
www.glmsoftware.com It looks very interesting and it is developed in Melbourne. Regards John |
||
Top | |
Lukeyson |
|
|||
|
We know about it. Graham McKechnie has at least had a good read of this thread and knows about us too.
I know that it's OBD2 J1979 software, so it doesn't have custom manufacturer stuff in it. I haven't actually seen it myself to give you my impression of it. But I do know that he's customised it for the obdpro tool, as well as being ELM compatible. Lukeyson |
|||
Top | |
rodgej2382 |
|
||
|
ya know that ptdiag (pass thru diagnostics) someone was talkin about up top.. well i have it. so if anyone needs it contact me
|
||
Top | |
Lukeyson |
|
|||
|
You've got at least one PM I would imagine.....just in case you only hit this page publicly and don't logon to check your PMs.
Lukeyson |
|||
Top | |
pellajl |
|
||
|
This DTC library may be useful to some. Not sure if you have seen it.
http://www.auteltech.com/DTC_Library_V1.10.rar Regards John |
||
Top | |
pellajl |
|
||
|
A couple of weeks ago I ordered one of those Chinese ELM327 cheapies from eBay. In total, I paid approximately $30 including postage. The unit is a no name brand with a USB interface.
I had a expectation that this units was inferior in quality and performance. (Didn’t matter, it was a $30 experiment!!). To cut a long story short, I downloaded OBD 2007 from GLM Software and installed the trial activation key. I had some drama connecting and once connected, I didn’t really know how to drive the application effectively so I sort assistance from Graham McKechnie. I sent Graham a couple log files and we exchanged a few emails. I was had issues connecting and with connection speeds. At this point, I wasn’t sure whether it was my laptop, the Chinese clone or some other obscure issue. Since I lived in Melbourne, Graham suggested we meet and we could test both vehicles (Ford BA XR8 MkII – 2005 and Mazda 6 MPS 2005. Graham had never worked with a Chinese clone before and suggested we meet to do some tests. This was good because I knew that Graham’s laptop worked. Graham also brought along a Scantool ELMscan USB and ODBPro unit as reference points for the test. Graham was able to connect to both vehicles with his software and ELM units. The Falcon reported support for PIDs # 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0C, 0x0D, 0x0E, 0x0F, 0x10, 0x11, 0x14, 0x15 and 0x18. (I have a question about PIDs 0x10 & 0x11 later on). The Mazda reported support for twice as many PIDs. I won’t list them here though. Both vehicles reported support for ISO 15765-4 (CAN 11/500). We had our baseline, now came the Chinese clone’s turn….. We connected up the clone and it identifies itself as an ELM327 v1.2a unit. (Yeah right!). We put the clone through its paces and from memory it was reading somewhere between 5 and 10 PID/sec. The interface speed was set at 9600. So the next was to try to push the clone until it broke essentially by pushing the interface speed higher and higher. Before we did that, we dismantled the unit to see if there were any jumpers so we could set the default interface speed to 38400. No jumper! Oh well, I thought to myself, we are stuck with 9600. The build quality was excellent and the PCB is housed in a strong aluminium box. Not to be deterred, we set the software to select it’s own speed and the software connected at 500000. See line 81 of the log file below. Started the engine and the data just poured in without fault. The software was reading between 19 and 20 pids / sec. We even set the ELM327 time out value to 25ms, still couldn’t break the clone. Conclusion, if you want a cheap ELM327 clone that works very well, just get one of these: http://cgi.ebay..com.hk/ws/eBayISAPI.dl ... 9&tc=photo Graham was a great help. Thanks Graham…… I have a question in relation to PIDs 0x10 (Air Flow Rate from Mass Airflow Sensor) and 0x11 (Absolute Throttle Position). The Falcon reports 0x10 and 0x11 as supported PIDs but no data is ever received from the ECU. The Mazda supports the same PIDs and yet, data is received from the ECU. This eliminates the software and in the clone interface unit. Has anyone else got or seen the same issue in BA Falcons? Regards John 1 Connection: Saturday, 30 August 2008 12:15:24 PM 2 OBD 2007 PC Ver: 1.0.13.96 15:24.625 3 Com Port : COM4 15:24.625 4 Baud Rate: 9600 15:24.625 5 Current Units: Metric 15:24.625 6 Country: Australia 15:24.625 7 SENT ATZ 15:24.625 8 SENT RESET 15:24.640 9 ATZ - a*** 15:25.562 10 ELM327 v1.2a - a*** 15:25.562 11 SENT ATSP0 15:25.562 12 SENT SET PROTOCOL 15:25.562 13 ATSP0 - a*** 15:25.625 14 OK - a*** 15:25.625 15 SENT ATE0 15:25.625 16 SENT ECHO OFF 15:25.625 17 ATE0 - a*** 15:25.671 18 OK - a*** 15:25.671 19 SENT ATL0 15:25.671 20 SENT LINE FEED OFF 15:25.671 21 OK - a*** 15:25.703 22 SENT ATST06 15:25.703 23 SENT SET TIMEOUT 15:25.703 24 OK - a*** 15:25.750 25 SENT ATRV 15:25.750 26 SENT READ VOLTAGE 15:25.750 27 14.1V - a*** 15:25.796 28 SENT AT@1 15:25.796 29 SENT READ MANUFACTURER 15:25.796 30 OBDII to RS232 Interpreter - a*** 15:25.859 31 0100 15:25.859 32 SENT READ PIDS_0x20 15:25.859 33 SEARCHING... - a*** 15:26.125 34 41 00 BF 9F B9 10 15:26.125 35 READING PIDS_0x20 15:26.125 36 011C 15:26.125 37 SENT READ OBDREQUIREMENTS 15:26.125 38 NO DATA - a*** 15:26.187 39 0113 15:26.187 40 READING O2 SENSOR LOCATION 15:26.187 41 NO DATA - a*** 15:26.234 42 0600 15:26.234 43 SENT READ ONBOARD TIDS 0x20 15:26.234 44 46 00 00 00 00 00 15:26.312 45 READING ONBOARDMONITORING TIDS 0x20 15:26.312 46 0900 15:26.312 47 NO DATA - a*** 15:26.375 48 08000000000000 15:26.375 49 48 00 00 00 00 00 15:26.453 50 READING ONBOARDMONITORINGTEST TIDS 0x20 15:26.453 51 SENT ATDP 15:26.453 52 SENT DESCRIBE PROTOCOL 15:26.453 53 AUTO, ISO 15765-4 (CAN 11/500) - a*** 15:26.515 54 SENT ATDPN 15:26.515 55 SENT DESCRIBE PROTOCOL BY NUMBER 15:26.515 56 A6 15:26.546 57 0101 15:26.546 58 SENT SERVICE 01 - PID 01 WHILE INITIALIZING 15:26.546 59 NO DATA - a*** 15:26.609 60 020000 15:26.609 61 SENT READ FREEZEFRAMEPIDS_0x20 15:26.609 62 NO DATA - a*** 15:26.671 63 050001 15:26.671 64 SENT READ TIDS_0x20 15:26.671 65 NO DATA - a*** 15:26.734 66 READ STOPPED AUTOMATICALLY 15:26.734 67 SENT ATH1 15:26.734 68 SENT HEADERS ON 15:26.734 69 OK - a*** 15:26.765 70 SET HEADERS ON COMPLETE 15:26.765 71 0100 15:26.765 72 NO DATA 15:26.828 73 SENT ATH0 15:26.828 74 SENT HEADERS OFF 15:26.828 75 OK - a*** 15:26.859 76 SET HEADERS OFF COMPLETE 15:26.859 77 READ ECU INFO FOR CRA COMPLETE 15:26.859 78 SENT ATBRT0F 15:26.859 79 OK - a*** 15:26.890 80 SENT ATBRD08 15:26.890 81 BAUD CHANGED TO 500000 15:26.921 82 OK - a*** 15:26.921 83 SENT 15:27.000 84 SENT CR ACK FOR NEW BAUDRATE 15:27.000 85 ELM327 v1.2a - a*** 15:27.000 86 BAUD CHANGE SUCCESSFULL 15:27.031 87 OK - a*** 15:27.031 88 BAUD CHANGE COMPLETED - READ STOPPED 15:27.031 |
||
Top | |
Lukeyson |
|
|||
|
So you are John? It's coming together for me now. Graham mentioned the success you had dynamically changing the baud rate on the chinese clone. I think auMatt had only ever tried the AT PP 0C method for setting the baud on boot which didn't appear to be supported.
And you're right, I've not receive data on 0x10 and 0x11 from a BA either. The BF sends out 0x11 but not 0x10. However, I think most of my data-gathering scans have been Key On Engine Off for J1979 stuff. I looked at a few Mode 22 scans (since the J1979 Mode01 stuff is replicated in the base PIDS of Mode22) and it looks like it's the same there too. Luke |
|||
Top | |
pellajl |
|
||
|
Yes Luke it's me......
It is a little disappointing that the BA doesn't output at the 0x10 information. Without this information, it is impossible to log fuel consumption performance. I can't believe the Ford dealers don't have access to this information though their WDS tool. Do you know if they do? If they do, there must be a command that enables /disbles the data streams. Have you ventured down this path? Regards |
||
Top | |
aumatt |
|
|||
|
My chinese clone switches to 500k using GLM software. I think I will be purchasing a copy, looks like great software.
Matt
_________________ 2004 Harvest Green XR6
|
|||
Top | |
Lukeyson |
|
|||
|
220900 is MAP pressure sensor, Volts, 2 Bytes, Div 1024
220914, 0915 and 0916 are the 3 Accelerator Position Sensors, Volts, 2 Bytes, Div 1024 220917 and 220918 are the 2 Throttle Position Sensors, Volts, 2 Bytes, Div 1024 22091a ETC Desired, 2 Bytes, Degrees, Div 512 22091b is Accelerator Pedal Position, 1 Byte, Integer, As is 22093c ETC Actual, 2 Bytes, Degrees, Div 512 220945 Another MAP sensor, kPA, as is (Is this Boosted only?) 22114a is Intake Air Temp, 1 Byte, Voltage, Scaling depends on the car, I think it will be Mult 15625 then Div 1000000 Of interest to you though may be this one: 221410, Fuel Pulse Width, 2 Bytes, Seconds, Mult 8 then Div 1000000 Lukeyson |
|||
Top | |
Lukeyson |
|
|||
|
I've just located a bunch of PCM Codes for the DSC enabled LPG I6 Falcon in the BFIII/FG range.
It appears that the internal code name for DSC enabled LPG is 'Wombat'. Luke |
|||
Top | |
data_mine |
|
|||
|
wombat = unkillable ???
_________________ 1998 DL LTD in Sparkling Burgundy, daily, 302W, stereo, slow |
|||
Top | |
Lukeyson |
|
|||
|
Ahh. Unkillable. For some reason when I first looked at it I thought you said Unlikeable....
Lukeyson |
|||
Top | |
aumatt |
|
|||
|
Im still waiting for some wrecked FG's to turn up so I can start hacking some new stuff
_________________ 2004 Harvest Green XR6
|
|||
Top | |
data_mine |
|
|||
|
Should be fun.
_________________ 1998 DL LTD in Sparkling Burgundy, daily, 302W, stereo, slow |
|||
Top | |
Who is online |
---|
Users browsing this forum: No registered users and 20 guests |