'411 Transients

[Jim Blackwood]

Anyone here know how to tune transients in the '411 ecm? I've been using HPT and it may be a bit lacking in that area.

Jim

[Fast355]

WAG for me tuning my P59 for my L31 style 383 with s marine manifold.

Best thing I can say is mine mostly needed Throttle Stomp Compensation although it did nee aome additional boil time and impact factor. Make sure that each cell increases in value to the next cell.

[Jim Blackwood]

WAG for me tuning my P59 for my L31 style 383 with s marine manifold.

Best thing I can say is mine mostly needed Throttle Stomp Compensation although it did nee aome additional boil time and impact factor. Make sure that each cell increases in value to the next cell.


Thanks for that, I guess I will have to sort out where to find this throttle stomp compensation. Been using the HPT VCM Editor and I have never seen anything like that in that app. Can I assume you are using a different app to do your tuning (and what one would that be?)

Jim

[Fast355]

Thanks for that, I guess I will have to sort out where to find this throttle stomp compensation. Been using the HPT VCM Editor and I have never seen anything like that in that app. Can I assume you are using a different app to do your tuning (and what one would that be?)

Jim

TunerProRT and an XDF exported from Universal Patcher.

[Jim Blackwood]

Great! I already have that on my laptop, and just installed the latest version. Just have to learn how to use it again. I hope to load my latest tune from HPT and go from there. I'll check out the help files.

Jim

[Jim Blackwood]

Anybody got a good link to set up the OBD Link LX101?
Jim

[kur4o]

It is bluetooth, Just connect enter pin code and it will be assigned a comport.

Than open Universal patcher->utilities->logger->settings tab->select device and comport->connect

If all is good you will see connection to obdlink and to pcm.

Than you can configure the logging parameters in profile tab.->Add pids that will be logged->start logging button->You will see data on log tab.

[Jim Blackwood]

It seems my OBD Link has lost it's mind. Blue light flashes but it doesn't seem to send out a signal. Neither my laptop or phone can detect it. Not exactly a robust bluetooth connection there. So... looks like I need to buy a new one but I'm seeing some bad reviews on it with connectivity issues. Anyone current on this care to comment?

Jim

[kur4o]

DOes it have some form of hard reset button, or some button needs to be pressed while pairing.

[Jim Blackwood]

Yeah I did that and the blue led starts flashing fast to indicate it is trying to connect but it never shows up. I'm pretty sure it is FUBAR at this point. These have gotten pretty expensive, I would think there would be something better by now what with all the ones on the market but so far the ones I have looked at all seem to have close to 10% unfavorable ratings, mostly for connectivity issues and I don't really think one in 5 purchasers are clueless about pairing bluetooth. Also I don't believe bluetooth as a comm method is quite that bad.

Of course, last time I went around and around over this connectivity issue was back when they changed the chip in the preferred physical cable and they all were then bad. I still have one of those around here somewhere if I haven't thrown it out. At that point I bought the LX and it worked so I stopped looking at it.

BUT, I have no problem at this point with using a cable if I can find one that is affordable and reliable. For that matter all this was a big part of the reason I migrated to HPT. I think I did have one glitch with their hardware but we got it sorted without anyone going nuclear. But as it turns out, they can't help me with the transient tuning so we're back here.

My buddy Scott tells me there is a BT unit that a couple of the guys developed specifically for tuning, Was maybe an American working with an Australian, does that ring a bell? But honestly I'd be perfectly happy with a cable if it works.

Jim

[kur4o]

If you want the best around, a chines clone MDI unit is quite capable, A little expensive and bulkier but is the most versatile. Have wifi, lan and usb.

Next option is lsdroid home brew cables, You can look at them here. The gt is what you need, it supposedly supports tech2win and have j2534 support as a bonus.

https://obdxpro.com/shop/

Than a cheap old usb version of obdlink devices will do the job too.

[Jim Blackwood]

Thanks. Since both you and Scott endorsed the obdxpro I ordered the GT. Personally I think the expense is a bit much but if it allows me to tune out the transients it will be worth it. I'm hoping the premium product will get a little more attention in terms of quality control, and being able to use it with newer systems could turn out to justify the extra cost also. Watched Lowbuck LS' vid on the vt with pcmhammer and that brought back old memories. I'll upgrade the version, I'm on ver. 14 if that tells you anything. Also taking a look at universalpatcher. I don't know yet what it is useful for but Scott recommended it so I'm looking. Should be here in a few days.

Jim

[kur4o]

WIth universal patcher you can tune, datalog and analyze logged data, and much more.

You need to poke around a bit to get what it does and where it is located.

For simple tuning, get a ls1 bin and open it from file->open bin
Change mode->file->mode->advanced to get more features available.

in utilities tab there is more tools that will open in new windows.

[Jim Blackwood]

Thanks. I'll look into it. I have a pretty good tune currently, it's evolved a pretty long ways from the basic generic gen-IV file but I need to get those pesky transients under control. Not bad when it's warm but when cold gear changes take a delicate touch.

Jim

[Jim Blackwood]

Sorry to take so long getting back to this, my hard drive crashed and I had to basically start over and it's taken me awhile to find this thread. Present status is that I do have the OBDXPRO in hand, I have PCMHammer v21 installed and it does recognize the obdxpro. I have the Universal Patcher (downloaded yesterday) also installed but I remember seeing something about loading a file before using it, I'm looking for that reference.

I still haven't managed to download the bin file using PCMHammer. There might be a power issue of some sort, if I connect to my simulator with the battery charger on it interferes with my touch pad and makes cursor movement almost impossibly erratic due to latency. But on the battery only it seems to behave more normally. However I haven't gotten it to properly connect to the ECM yet either on the simulator or the car. Bound to be something I'm doing wrong but I haven't run across the detailed sequence of user inputs for doing that download so at this point I am mostly guessing and trying to remember how it's supposed to be done. I suppose at some point I will figure it out again and say, "Well of course.." but I'm not there yet.

So that's the update, in case anyone was interested.

Jim

[kur4o]

Hooking a charger is real bad ides, regulated filtered power supply is much better.
You need to select device as serial with comport.

[Jim Blackwood]

When I open PCH with the OBDX plugged in it tells me it found the OBDX on com3, serial port is selected, and it says the device is initialized and ready. However, Test doesn't work, access to com3 denied. Then it says it found ATZ but failed to switch to DVI protocol or reset DVI or initiate the OBDX. It's been a couple years since I did this and I can't remember what I'm doing wrong.

Jim

[kur4o]

Which obdx device do you have.

You can try to get latest drivers from their website, and upgrade firmware if there is any.

ANother test will be to get it working with universal patcher logger.
utiliies->logger->settings tab->select device->connect

[Jim Blackwood]

The OBDXPro GT.
About the battery charger, I have a 12v battery in the simulator. I switch on the battery charger to charge it up. I can switch on either or both so it's easy to run on just the battery and charge it afterwards. I expected the battery to be a reasonably effective filter but apparently not.

I just downloaded and installed the software from the OBDXProGT page, seemed odd that there were about 4 or so install cycles but I went through the complete process. Tried to connect with both PCH and Universal Patcher, on com3 with a usb cable and then on com4 and com5 with bluetooth. No joy. PCH did say it found ATZ then failed to switch to DVI. UP just gave me a connection failed.

Jim

[kur4o]

Can you test with j2534 device selection, in patcher and hammer.

[Jim Blackwood]

In logger it says "32534 client: Device initialization fail.
IN PCH if I say OK without running test it tells me an update for the OBDX Pro scantool is required so I went to the update download site and downloaded and installed every update that looked like it could be related to the GT then went back to PCH and got the exact same result. Trying Test brings up the same dialog which happens right after it loaded DLL. On com3 (usb) it fails to switch DVI, on com4 (BT) access to com4 is denied, on com5 it times out.

Incidentally, the laptop does not beep when the GT is plugged in, if that means anything. My desktop PC does though. Guess I could try the install there but it won't help me much on tuning the car. Though I suppose I could always bring in the ECM and put it on the simulator. Do my logging with HPT.

Jim

[kur4o]

The update might not have completed successfully.

Here is some other user with similar issue fix.


Well finally got it sorted. Firmware wasn't loading by clicking on the download even though it was telling me it was ready. Went into my computer/ program files and found it there so tried from there and it's working finally. Thanks everyone for your help and Tazzie you're a genius

[Jim Blackwood]

OK, did that. Found the updater and it did a firmware update and then confirmed that it was up to date.
Logger now appears to connect on J2534 (Device initiation complete) but not on com3 or BT. No improvement from PCH.

Jim

[kur4o]

Can you try pcm hammer with j-device selected, and post debug log.

You can test logger if it have actual communication in dtc tab when connected, test some random buttons.

[Jim Blackwood]

J2534 on PCH, log below. Finally getting somewhere I think:
--------------------------------------------------------------------
[09:55:02:408] PCM Hammer 021
[09:55:02:408] Monday, April 08 2024 @09:55:02:40
[09:55:02:408] Initializing J2534 Device
[09:55:02:408] Loaded DLL
[09:55:05:587] Connected to the device.
[09:55:05:591] Battery Voltage is: 12.685
[09:55:12:952] VIN: 1G1FP31S61N240478
[09:55:12:983] OS ID: 1253002
[09:55:12:983] Hardware Type: P01_P59
[09:55:13:014] Calibration ID: 12206911
[09:55:13:049] Hardware ID: 9386530
[09:55:13:120] Serial Number: 2EB2K9S62010
[09:55:13:158] Broad Cast Code: DJZX
[09:55:13:182] MEC: 0
[09:55:29:689] Will save to C:\Users\Jim\OneDrive\Desktop\MG\300 Iron Head\2024\PCM Hammer\C test.bin
[09:55:32:959] Querying operating system of current PCM.
[09:55:32:991] OSID: 1253002
[09:55:33:062] Unlock succeeded.
[09:55:33:081] Attempting switch to VPW 4x
[09:55:33:100] Module 0x10 (engine controller) has agreed to enter high-speed mode.
[09:55:37:674] Kernel upload 22% complete.
[09:55:38:114] Kernel upload 48% complete.
[09:55:38:579] Kernel upload 74% complete.
[09:55:39:012] Kernel upload 100% complete.
[09:55:39:267] Kernel Version: 01030501
[09:55:39:271] kernel uploaded to PCM succesfully. Requesting data...
[09:55:39:291] Flash chip: Intel 28F400B, 512kb
[09:55:39:295] Read complete.
[09:55:39:302] All read-request messages succeeded on the first try. You have an excellent connection to the PCM.
[09:55:39:302] We're not sure how much retrying is normal for a read operation on a 0kb PCM.
[09:55:39:316] Please help by sharing your results in the PCM Hammer thread at pcmhacking.net.
[09:55:39:322] Starting verification...
[09:55:39:334] Calculating CRCs from file.
[09:55:39:334] Initializing CRC algorithm on PCM, this will take a minute...
[09:55:39:382] Requesting CRCs from PCM.
[09:55:39:402] Range File CRC PCM CRC Verdict Purpose
[09:55:39:402] 060000-07FFFF not needed not needed n/a OperatingSystem
[09:55:39:413] 040000-05FFFF not needed not needed n/a OperatingSystem
[09:55:39:413] 020000-03FFFF not needed not needed n/a OperatingSystem
[09:55:39:433] 008000-01FFFF not needed not needed n/a Calibration
[09:55:39:433] 006000-007FFF not needed not needed n/a Parameter
[09:55:39:459] 004000-005FFF not needed not needed n/a Parameter
[09:55:39:470] 000000-003FFF not needed not needed n/a Boot
[09:55:39:480] The contents of the file match the contents of the PCM.
[09:55:39:502] Clearing trouble codes.
[09:55:40:603] Clearing trouble codes.
[09:55:41:687] Elapsed time 00:00:08.6197110
[09:55:41:698] Saving contents to C:\Users\Jim\OneDrive\Desktop\MG\300 Iron Head\2024\PCM Hammer\C test.bin
---------------------------------------------------------------------------------
This is the my first good read with the OBDX Pro GT.
----------------------------------------------------------------------------------

Results for serial connections to follow:
--------------------------------------------
Com3 usb:
[10:03:24:294] PCM Hammer 021
[10:03:24:310] Monday, April 08 2024 @10:03:24:31
[10:03:24:636] Thanks for using PCM Hammer.
[10:03:24:994] Device Found: OBDX Pro GT
[10:03:25:079] Device Successfully Initialized and Ready

Re-Initialized:
[10:05:38:875] PCM Hammer 021
[10:05:38:876] Monday, April 08 2024 @10:05:38:87
[10:05:39:539] Device Found: ATZ
[10:05:39:544] Failed to switch to DVI protocol
[10:05:39:546] Unable to reset DVI device.
[10:05:39:546] Unable to initialize OBDX Pro on COM3

Test results in Unhandled Exception, access to com3 denied.
[09:40:44:866] PCM Hammer 021
[09:40:44:882] Monday, April 08 2024 @09:40:44:88
[09:40:45:215] Thanks for using PCM Hammer.
[09:40:45:587] Device Found: OBDX Pro GT
[09:40:45:650] Device Successfully Initialized and Ready
[09:41:37:916] VIN query failed: Timeout

[09:52:29:082] PCM Hammer 021
[09:52:29:082] Monday, April 08 2024 @09:52:29:08
[09:52:29:757] Device Found: ATZ
[09:52:29:757] Failed to switch to DVI protocol
[09:52:29:757] Unable to reset DVI device.
[09:52:29:773] Unable to initialize OBDX Pro on COM3

BT:
[09:42:58:443] PCM Hammer 021
[09:42:58:457] Monday, April 08 2024 @09:42:58:45
[09:42:58:457] Unable to initialize OBDX Pro on COM4

BT:
[09:44:27:768] PCM Hammer 021
[09:44:27:768] Monday, April 08 2024 @09:44:27:76
[09:44:44:059] Unable to initialize OBDX Pro on COM5

Logger:

Connecting (VPW)...
J2534 client initializing...
Initializing J2534 Device
J2534 client: Device initialization complete.
Connected to the device, ID: 1
Battery Voltage is: 12.947
Timeout requesting OS
Versions: Firmware: 01.00, DLL: 1.4.8834.14573, Api: 04.04
Connected protocol: J1850VPW Speed: ISO14230
Removing all filters
Device initialization complete.
Filtering parameters by OS:
Start logging...
No profile configured
Disconnecting...J2534 Server Quits
Clearing functional address table (primary protocol)
Disconnecting primary protocol
[Done]
Connecting (VPW)...
J2534 client initializing...
Initializing J2534 Device
J2534 client: Device initialization complete.
Connected to the device, ID: 1
Battery Voltage is: 12.721
Versions: Firmware: 01.00, DLL: 1.4.8834.14573, Api: 04.04
Connected protocol: J1850VPW Speed: ISO14230
Removing all filters
Device initialization complete.
Device in use
Done

Attempting to connect to Logger with BT:

Connecting (VPW)...
J2534 client initializing...
Initializing J2534 Device
J2534 client: Device initialization fail.
Unable to connect to the device: 34
J2534 server: Device initialization failed
J2534 Server Quits


I do not have any parameters set for logging so I'm not getting any readings. yet.


Jim