Universalpatcher with Logger & Analyzer

[hjtrbo]

kur4o, the tip you gave with tablelist xml naming is excellent. Rename xml to the os number and place into the tuner folder. When a corresponding bin is opened, the xml is automatically opened.

Question, is there a limitation with obeying row major when importing from xdf? There is a discrepancy as shown below. I manually correct using the tablelist editor as a work around.

And another question, is there support for TunerPro 'Minor Stride'. Or do we need to define each table individually?

pt4BWr5.png (104.95 KiB) Viewed 3722 times

2yoJ90u.png (45.13 KiB) Viewed 3722 times

[kur4o]

I looked at the screenshot and found the issue.

The table is a 2d array and have 2 extra bytes infront of each 2d array.

00 11 [F3 A2 F3 A2 F3 A2 F3 A2 F3 A2 F3 A2 F3 A2 F3 A2 F3
A2 F3 A2 F3 A2 F3 A2 F3 A2 F3 A2 F3 A2 F3 A2 F3
A2] 00 11 (00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00) 00 00 00 00 00 00 00
00 00 00 00 00) 00 11 [F3 A2 F3 A2 F3 A2 F3 A2 F3
A2 F3 A2 F3 A2 F3 A2 F3 A2 F3 A2 F3 A2 F3 A2 F3
A2 F3 A2 F3 A2 F3 A2 F3 A2] 00 11 [07 27 07 27 07
27 07 27 07 27 07 27 07 27 07 27 07 27 07 27 07
27 07 27 07 27 07 27 07 27 07 27 07 27] 00 11....

00 11 is added infront of each table, and specify the size of table.
It is not possible to configure as is, as a 3d table.
Looks like tunerpro added some new features to deal with it[not currently supported by import].
In universal patcher you can use multitable settings to define such arrays.

The row major is usually imported correctly, maybe that major/minor stride settings gives an issue with row major import. I think it will be very easy to add support since we already have much better arrays encoded.

Here is some example you can look at.
I rename some of the table to give you an idea how it works.

You ca use . and [] to define the arrays.
The idea is to have different tables defined->displayed as a single table.

The naming must follow strict rules to work usually a . and [] should be used only for arrays and no other places in the table name.

15296 TCC WOT Apply/Release Speed - Pattern B - [1st][Apply]
15296 TCC WOT Apply/Release Speed - Pattern B - [1st][Release]
15296 TCC WOT Apply/Release Speed - Pattern B - [2nd][Apply]
15296 TCC WOT Apply/Release Speed - Pattern B - [2nd][Release]
15296 TCC WOT Apply/Release Speed - Pattern B - [3rd][Apply]
15296 TCC WOT Apply/Release Speed - Pattern B - [3rd][Release]
15296 TCC WOT Apply/Release Speed - Pattern B - [4th][Apply]
15296 TCC WOT Apply/Release Speed - Pattern B - [4th][Release]
15296 TCC WOT Apply/Release Speed - Pattern B - [5th]
15296 TCC WOT Apply/Release Speed - Pattern B - [6th]

Will be displayed in a single 4d table

[hjtrbo]

I will have a play. Thank you kur4o

[kur4o]

Latest version is now on github

V22.11 now can autofix the extra checksums found on most of the newer Gm engine controllers.

Lots of xml files are updated and some other added, so a full download of zip folder will be needed for the new functionality to work correctly.

There is a also a new bruteforce tool for testing various checksums, for advanced users only.

[Boostedforlife]

Figure this is the best place to ask this. I've been searching the internet for vpw commands and have learned a little, diffently understanat j-1850 protocol better but I'm looking for info on how scan tools do bidirectional controls? Any one have commands to turn on off fans, lock timing, adjust afr, and lock trans in diffent gears and lock converteer. Or how one would go about figuring out how this us done.

Os is the 7603. Also in the logger I've made changes to the paramater.Standard file but after I do it will not load to the logger.

The pid I'm trying to define is 1113. The on,off boolean doesn't work for this switch, it displays the selected gear. The way its works is 1=park:2=reversue:4= neutral:8=4th:16=3rd:32=2nd:64=1st. I also think I have 1112 figured out it's a little different set up but need to figure out if logger can do this. I do know this works in torque app.

[kur4o]

bidirectional works like that. While logging you inject some custom messages that contains command for control.

There is some initial version that can do that with some basic commands, but it is not well tested and needs more work.

You can give it a try, There is some sample file attached.

In logger->tools->send control commands

load the attached file. You can than open editor and see the configuration. I have much more defined list if you want to make the files better and do some testing.

Pid reconfig should work, but not sure how. You`d better test first if your pcm support the pid. DTCtab->>query pids

I think a better pid editor is needed. Current one is a little confusing.

[Boostedforlife]

I figure it was a command message and just have not found any info on what commands but this is what I'm looking for I'll test it out and will do any testing you want.

The logger is different then pcmlogger I thought I could edit the xml file and be set. But the profile is set up different.

But thank you I'll give it a try and let you know how it works. Just will be nice to see some commands to get eyes on how it works.

[kur4o]

I have some better list but this one is confirmed for sure[ripped from t2].
mode ae
with 3 submodes
01
02
03

are used.
Than there is 6 bytes of data. usually bit encoded. 1bit enables control second byte commands on/off

or if there is solenoid one bit enables control second byte specify values.

The main commands are similar across all vpw pcms, with slight differences.

[Boostedforlife]

Played around with the command controls and it worked great I edited in ac clutch and injector pulse and got the feel for the layout and how it works. I would take the better list if you are willing to share and will test and find out what works and doesn't and posted it up here to share at least for the 7603 os.

[kur4o]

That is great. I managed to dig out the old file. Here it is. There is checksum added on some of the commands, you can ignore it. use only the 6 bytes of data after mode/submode.

Also finally figured spark control through some complete disassembly I was given by some nice people.

mode ae submode 02
byte3
[bit2[$04] 0=advance
1=retard
bit3[$08] 1=absolute
0=relative
bit4[$10] 1=enable spark control
0=disable spark control]

byte5= spark variable. We need to figure conversion of this variable

Some example will be

add +xx degrees of spark, using $12 in hex, but in actual spark degrees it is converted, so we need to figure scale factor

advance by $12 in hex
6c 10 f0 ae 02 00 00 10 00 12 00

retard by $12 in hex

6c 10 f0 ae 02 00 00 14 00 12 00

Absolute spark is dangerous, and don`t advice anyone using it.