Universalpatcher with Logger & Analyzer
-
Boostedforlife
- Posts: 60
- Joined: Sat May 22, 2021 4:39 am
Re: Universalpatcher with Logger & Analyzer
I will mess around this evening after work. I want the soark control for my cammed (228/232 .585 112 lsa) 5.3 to find the best advance for vacuum. So only at idle I would never try to run a motor lock in a fixed ignition time. But I do understand the risks if it. I know it's in the 20-30 range but it will be cool to see how it works.
Re: Universalpatcher with Logger & Analyzer
I have used it on older pcms, and it works pretty good. Spark advance control is on every gm pcm from 1990+, and the logic is the same. Just need to find the scaling from hex to degress.
I think we can map other unknow functions as afr and some other interesting stuff. End of injection target is really great for tuning, but not sure it is supported.
I think we can map other unknow functions as afr and some other interesting stuff. End of injection target is really great for tuning, but not sure it is supported.
-
Boostedforlife
- Posts: 60
- Joined: Sat May 22, 2021 4:39 am
Re: Universalpatcher with Logger & Analyzer
Okay got a chance to enter the examples you gave and not change at all I tried the slider and entering raw hex numbers but no change. But I did mess with the injector pulse,had the logger and at idle seen the timing drop to -11 when it tried to die. If you use the pedal it will come back. So I change the first byte to 10 and it will stay solid at 20 at idle only but I think that is what my timing is set to in all the tables for timing did matter if I made this byte 10,20,30,40,etc but if it's 02,03 ,04, all the way to 0a(01 did nothing) it seems to call max retard set in the tune. Mine is -11
The example is 6c 10 f0 ae 02 10 00 00 00 00 00= timing locked at idle only, 20 degrees.
Example 6c 10 f0 ae 02 02 00 00 00 00 00 locked at - 11
The example is 6c 10 f0 ae 02 10 00 00 00 00 00= timing locked at idle only, 20 degrees.
Example 6c 10 f0 ae 02 02 00 00 00 00 00 locked at - 11
Re: Universalpatcher with Logger & Analyzer
6c 10 f0 ae 02 10 00 00 00 00 00
disables spark advance idle correction.
10 f0 ae 02 02 00 00 00 00 00
is idle speed correction. used with byte 3 to set idle position.
Timing control does check for some conditions. I will try to test some stuff too, and add more commands to list.
disables spark advance idle correction.
10 f0 ae 02 02 00 00 00 00 00
is idle speed correction. used with byte 3 to set idle position.
Timing control does check for some conditions. I will try to test some stuff too, and add more commands to list.
-
Boostedforlife
- Posts: 60
- Joined: Sat May 22, 2021 4:39 am
Re: Universalpatcher with Logger & Analyzer
I'll change my names in my list but definatly seems to be what they are doing. Byte three is 6c 10 f0 ae 02 02 00 xx 00 00 00 correct?
Both Fan relays confirmed to be the same as your list.
Both Fan relays confirmed to be the same as your list.
Re: Universalpatcher with Logger & Analyzer
Added some more commands, ripped from scan tool.
For spark control I think $80 = 0degrees, below is retard above is advance, You can give it a try with $80 as starting point.
On some pcms 3 in hex equals 1 degree, but here scaling can differ,
For spark control I think $80 = 0degrees, below is retard above is advance, You can give it a try with $80 as starting point.
On some pcms 3 in hex equals 1 degree, but here scaling can differ,
- Attachments
-
- MODE_AE_COMMANDS.txt
- (3.89 KiB) Downloaded 48 times
-
Boostedforlife
- Posts: 60
- Joined: Sat May 22, 2021 4:39 am
Re: Universalpatcher with Logger & Analyzer
So I see that the scan tools send 6c 10 f1 and we send f0 what's the difference? And i have not had much time to play with the timing stuff but I'm itching to try it again.
I think 6c is quieting the bus 10 is module(pcm) ae is mode and the rest is data. Just wondering. Lol I'm still learning and would like to know why there is a difference.
In torque app if you send mode 22 pid say 1113 and end with 01 the communication is faster so the hex address is 22111301. Some pids don't respond without it and some will but the response Is faster on first load I think this is just how torque handles the commands but thought it was intersing. Definitely what to get a spliter and second obd device and see what's really going on.
I think 6c is quieting the bus 10 is module(pcm) ae is mode and the rest is data. Just wondering. Lol I'm still learning and would like to know why there is a difference.
In torque app if you send mode 22 pid say 1113 and end with 01 the communication is faster so the hex address is 22111301. Some pids don't respond without it and some will but the response Is faster on first load I think this is just how torque handles the commands but thought it was intersing. Definitely what to get a spliter and second obd device and see what's really going on.
Re: Universalpatcher with Logger & Analyzer
6c=priority
f0 or f1 it doesn`t matter, this is the tool ID and can vary from f0-fd
Last byte of pid request does have some meaning, and without it mode 22 is not working.
Anyway mode 22 logging is way slower than DPID mode.
To see actual communication on bus you can goto universal patcher vpw console tab and mark log to screen, It will show all data on bus that is running in the background.
f0 or f1 it doesn`t matter, this is the tool ID and can vary from f0-fd
Last byte of pid request does have some meaning, and without it mode 22 is not working.
Anyway mode 22 logging is way slower than DPID mode.
To see actual communication on bus you can goto universal patcher vpw console tab and mark log to screen, It will show all data on bus that is running in the background.