Page 42 of 109

Re: ELM327 Software Development

Posted: Fri Sep 05, 2014 6:30 pm
by Tazzi
Yeah tech2 can do that. Done by going into the instrument cluster -> options -> transmission. Or something like that.

Re: ELM327 Software Development

Posted: Tue Sep 09, 2014 6:58 pm
by Tazzi
Did a little bit of work on the obd2 app today. The autoconnect feature should work great. I actually noticed a couple of my bluetooth comports popping up as "4i,6i" ect so it even accommodates for any unavailable ports. :thumbup:
And initiating the 115200 baud should work much better now. Some ELM clones dont actually accept the commands, so this feature must be turned off!
Image

Should hopefully fixup anyone having issues with connecting or monitoring all data.
And, currently Im only working on the VPW protocol as I only have access to a ls1 pcm!

Re: ELM327 Software Development

Posted: Tue Sep 09, 2014 9:28 pm
by Tazzi
forgot to add the app :lol:

Re: ELM327 Software Development

Posted: Wed Sep 10, 2014 12:09 am
by Tazzi
Few little errors in the recent one I added.. forgot to add the header updater to automatically do all header changes between requesting vin, faults ect. Will update with latest version soon, just adding a few last things.

Also, the engine data reading looks to be sitting at around 45-60pids/s. :thumbup:
Could probably increase that with some threading of the control updates.. and it will probably severely diminish if I dont thread the gauge updates too. Currently it only reads engine temp and coolant temp. But the "custom send" function works correctly now too so custom sends can be done from there.


If anyone is having issues with connecting, please post up any issues! Iv tried it on 4 lappys here and seems to be running strong!. But not all ELM devices are the same or support the same commands, so be good to be able to add some sort of feature/bypass for those. :thumbup:

Heres the faults that the app pulls from a PCM on bench:

Code: Select all

[22:02:32:362]   Manufacture defined: P1  0125
[22:02:32:372]   Manufacture defined: P1  0225
[22:02:32:386]   Manufacture defined: P1  0325
[22:02:32:398]   Manufacture defined: P1  0725
[22:02:32:411]   Manufacture defined: P1  0825
[22:02:32:423]   Manufacture defined: P1  1201
[22:02:32:439]   Manufacture defined: P1  1325
[22:02:32:449]   Manufacture defined: P1  1701
[22:02:32:462]   Manufacture defined: P1  1825
[22:02:32:475]   Manufacture defined: P1  2125
[22:02:32:487]   Manufacture defined: P1  2225
[22:02:32:500]   Manufacture defined: P1  2301
[22:02:32:513]   Manufacture defined: P1  2525
[22:02:32:525]   Manufacture defined: P1  3125
[22:02:32:537]   Manufacture defined: P1  3225
[22:02:32:549]   Manufacture defined: P1  3425
[22:02:32:562]   Manufacture defined: P1  5125
[22:02:32:575]   Manufacture defined: P1  5225
[22:02:32:587]   Manufacture defined: P1  5425
[22:02:32:599]   Manufacture defined: P1  7125
[22:02:32:612]   Manufacture defined: P1  7225
[22:02:32:625]   Manufacture defined: P1  7425
[22:02:32:636]   Manufacture defined: P1  7525
[22:02:32:649]   SAE defined: P2  3025
[22:02:32:660]   Jointly defined: P3  2525
[22:02:32:673]   Jointly defined: P3  2725
[22:02:32:685]   Jointly defined: P3  3225
[22:02:32:697]   Jointly defined: P3  3525
[22:02:32:710]   Jointly defined: P3  3625
[22:02:32:721]   Jointly defined: P3  4125
[22:02:32:733]   Jointly defined: P3  4225
[22:02:32:746]   Jointly defined: P3  4325
[22:02:32:758]   Jointly defined: P3  5101
[22:02:32:770]   Jointly defined: P3  5201
[22:02:32:783]   Jointly defined: P3  5301
[22:02:32:795]   Jointly defined: P3  5401
[22:02:32:808]   Jointly defined: P3  5501
[22:02:32:820]   Jointly defined: P3  5601
[22:02:32:835]   Jointly defined: P3  5701
[22:02:32:848]   Jointly defined: P3  5801
[22:02:32:867]   Chassis Codes - SAE defined: C0  4325
[22:02:32:875]   Chassis Codes - SAE defined: C0  8125
[22:02:32:885]   Manufacturer defined: C1  0025
Image

Re: ELM327 Software Development

Posted: Wed Sep 10, 2014 12:36 pm
by Tazzi
Ahh... now Im confused whether I read that right?

Code: Select all

[10:28:00:958]   Found Fault: 6C F1 10 59 01 01 25 F9 
[10:28:00:970]   Found Fault: 6C F1 10 59 01 02 25 2D 
[10:28:00:982]   Found Fault: 6C F1 10 59 01 03 25 61 
[10:28:00:995]   Found Fault: 6C F1 10 59 01 07 25 4C 
[10:28:01:007]   Found Fault: 6C F1 10 59 01 08 25 EF 
[10:28:01:020]   Found Fault: 6C F1 10 59 01 12 01 6A 
So looking at the first fault: 6C F1 10 59 01 01 25 F9
Is the fault code P0125?

Is byte 5 (start at 1)the byte that designates P1,P2,C1 ect. Or is that the upper nibble of byte 6, and the fault is the lower nibble of byte 6 plus byte 7?

As seen in this log dump, not sure what byte 5 is exactly designating, is it identifying a specific component?

Code: Select all

[10:28:00:958]   Found Fault: 6C F1 10 59 01 01 25 F9 
[10:28:00:970]   Found Fault: 6C F1 10 59 01 02 25 2D 
[10:28:00:982]   Found Fault: 6C F1 10 59 01 03 25 61 
[10:28:00:995]   Found Fault: 6C F1 10 59 01 07 25 4C 
[10:28:01:007]   Found Fault: 6C F1 10 59 01 08 25 EF 
[10:28:01:020]   Found Fault: 6C F1 10 59 01 12 01 6A 
[10:28:01:032]   Found Fault: 6C F1 10 59 01 13 25 D5 
[10:28:01:044]   Found Fault: 6C F1 10 59 01 17 01 0B 
[10:28:01:057]   Found Fault: 6C F1 10 59 01 18 25 5B 
[10:28:01:070]   Found Fault: 6C F1 10 59 01 21 25 8C 
[10:28:01:082]   Found Fault: 6C F1 10 59 01 22 25 58 
[10:28:01:094]   Found Fault: 6C F1 10 59 01 23 01 E7 
[10:28:01:107]   Found Fault: 6C F1 10 59 01 25 25 A1 
[10:28:01:119]   Found Fault: 6C F1 10 59 01 31 25 38 
[10:28:01:132]   Found Fault: 6C F1 10 59 01 32 25 EC 
[10:28:01:144]   Found Fault: 6C F1 10 59 01 34 25 59 
[10:28:01:157]   Found Fault: 6C F1 10 59 01 51 25 A7 
[10:28:01:169]   Found Fault: 6C F1 10 59 01 52 25 73 
[10:28:01:181]   Found Fault: 6C F1 10 59 01 54 25 C6 
[10:28:01:194]   Found Fault: 6C F1 10 59 01 71 25 D2 
[10:28:01:206]   Found Fault: 6C F1 10 59 01 72 25 06 
[10:28:01:219]   Found Fault: 6C F1 10 59 01 74 25 B3 
[10:28:01:231]   Found Fault: 6C F1 10 59 01 75 25 FF 
[10:28:01:243]   Found Fault: 6C F1 10 59 02 30 25 F8 
[10:28:01:256]   Found Fault: 6C F1 10 59 03 25 25 A2 
[10:28:01:268]   Found Fault: 6C F1 10 59 03 27 25 3A 
[10:28:01:281]   Found Fault: 6C F1 10 59 03 32 25 EF 
[10:28:01:293]   Found Fault: 6C F1 10 59 03 35 25 16 
[10:28:01:306]   Found Fault: 6C F1 10 59 03 36 25 C2 
[10:28:01:318]   Found Fault: 6C F1 10 59 03 41 25 10 
[10:28:01:330]   Found Fault: 6C F1 10 59 03 42 25 C4 
[10:28:01:343]   Found Fault: 6C F1 10 59 03 43 25 88 
[10:28:01:355]   Found Fault: 6C F1 10 59 03 51 01 57 
[10:28:01:368]   Found Fault: 6C F1 10 59 03 52 01 83 
[10:28:01:380]   Found Fault: 6C F1 10 59 03 53 01 CF 
[10:28:01:392]   Found Fault: 6C F1 10 59 03 54 01 36 
[10:28:01:405]   Found Fault: 6C F1 10 59 03 55 01 7A 
[10:28:01:419]   Found Fault: 6C F1 10 59 03 56 01 AE 
[10:28:01:431]   Found Fault: 6C F1 10 59 03 57 01 E2 
[10:28:01:443]   Found Fault: 6C F1 10 59 03 58 01 41 
[10:28:01:456]   Found Fault: 6C F1 10 59 04 43 25 02 
[10:28:01:468]   Found Fault: 6C F1 10 59 04 81 25 B9 
[10:28:01:481]   Found Fault: 6C F1 10 59 05 00 25 B3 

Re: ELM327 Software Development

Posted: Wed Sep 10, 2014 12:49 pm
by Tazzi
Updated the fault code lookup.. seems to make more sense now... still dont know what byte 5 is doing

Code: Select all

Fault Log
[10:44:42:814]   Powertrain Code - SAE defined: P0125
[10:44:42:825]   Powertrain Code - SAE defined: P0225
[10:44:42:837]   Powertrain Code - SAE defined: P0325
[10:44:42:849]   Powertrain Code - SAE defined: P0725
[10:44:42:863]   Powertrain Code - SAE defined: P0825
[10:44:42:876]   Manufacture defined: P1201
[10:44:42:887]   Manufacture defined: P1325
[10:44:42:902]   Manufacture defined: P1701
[10:44:42:915]   Manufacture defined: P1825
[10:44:42:927]   SAE defined: P2125
[10:44:42:940]   SAE defined: P2225
[10:44:42:952]   SAE defined: P2301
[10:44:42:965]   SAE defined: P2525
[10:44:42:979]   Jointly defined: P3125
[10:44:42:991]   Jointly defined: P3225
[10:44:43:001]   Jointly defined: P3425
[10:44:43:015]   Manufacturer defined: C1125
[10:44:43:026]   Manufacturer defined: C1225
[10:44:43:039]   Manufacturer defined: C1425
[10:44:43:052]   Reserved for Future: C3125
[10:44:43:065]   Reserved for Future: C3225
[10:44:43:077]   Reserved for Future: C3425
[10:44:43:090]   Reserved for Future: C3525
[10:44:43:102]   Jointly defined: P3025
[10:44:43:115]   SAE defined: P2525
[10:44:43:127]   SAE defined: P2725
[10:44:43:140]   Jointly defined: P3225
[10:44:43:153]   Jointly defined: P3525
[10:44:43:174]   Jointly defined: P3625
[10:44:43:184]   Chassis Codes - SAE defined: C0125
[10:44:43:192]   Chassis Codes - SAE defined: C0225
[10:44:43:200]   Chassis Codes - SAE defined: C0325
[10:44:43:212]   Manufacturer defined: C1101
[10:44:43:225]   Manufacturer defined: C1201
[10:44:43:236]   Manufacturer defined: C1301
[10:44:43:248]   Manufacturer defined: C1401
[10:44:43:261]   Manufacturer defined: C1501
[10:44:43:273]   Manufacturer defined: C1601
[10:44:43:285]   Manufacturer defined: C1701
[10:44:43:298]   Manufacturer defined: C1801
[10:44:43:310]   Chassis Codes - SAE defined: C0325
[10:44:43:323]   Body Codes - SAE defined: B0125
[10:44:43:335]   Powertrain Code - SAE defined: P0025

Re: ELM327 Software Development

Posted: Wed Sep 10, 2014 4:00 pm
by Tazzi
Updated with some better fault code listing. Now looking to add in a quick websearch for the fault code rather than hard coding 100's of faults. :thumbup:
And to add some proper functionality to the engine data section, maybe a list of PIDs that can be chosen to display in the gauges? Or just a huge list of textboxs of information?.. Will figure it out as I go I guess. Maybe display more regularly viewed info in the boxes and the gauges can be changed frequently
update3.PNG
update3.PNG (49.6 KiB) Viewed 4465 times

Re: ELM327 Software Development

Posted: Wed Sep 10, 2014 4:10 pm
by delcowizzid
looking good mate ill have a test on the weekend with my elm and a VT LS1

Re: ELM327 Software Development

Posted: Wed Sep 10, 2014 6:09 pm
by Tazzi
Cheers, delcowizzid.
Will probably be a good 6+ versions more by then.

Implemented seed/key finder now. Im thinking we can speed things up a bit using a relay as well to do a full power cycle.
So do a full power cycle ~0.5seconds.. therefore 2 attempts/second = 120/min = 7200/hr = 172800/day
Or, we would hit max value of 0xFFFF after about 9ish hours.
Well.. in theory that would work. Wont know till we try.. hopefully there isnt any big capacitors that hold power for a long time.

Re: ELM327 Software Development

Posted: Wed Sep 10, 2014 6:11 pm
by yoda69
Very nice work, will have to have a play with it over the weekend when I get home.
Keep up the good work!!!
:driving: