EFIDynoTuning Forum

i dont see any .cf4 files on cvaf1. i do see them on fbgio.

there is the chance i am looking right over them.

Picked a SCT SF3 (X3) 3015 yesterday. I figured it would be married but I could use it to learn data logging with SCT livelink. Turns out it was unmarried so that is a plus.
I downloaded livelink2 from SCT and did some data logs to test with. Ordered a 1394 cable to make a pigtail for external inputs.

Does anyone have any helpful tips for using the the unit and data logging with it?

Maybe some firmware files?

Happy new years yall

Merry Christmas to everyone on the forum

Be safe and enjoy your time with your family

Something I have found to find these types of issues is to check the relay sockets for proper drag. Easy way to do it would be to cut terminals off a relay and hold them with a small pair of pliers or solder to something rigid that will allow you to insert and pull back out. I have found when relays fail and get hot, the clamping force of the socket to the relay terminal drops off and you can get intermittent loss of connection and also arcing on the socket and on the contacts inside the relay. What I would recommend is replacing all your relays (all of them) with good quality relays and check the terminals for proper drag so that you know they are making proper contact with the new relays.
Intermittent issues will drive you nuts trying to find. Relays are cheaper than a tow.

65536 bytes or 0x1000 bytes

I took the bin decipha posted, put your vin and pats key in, and converted with custom ecm 's bank swap tool. I then compared it to the one you posted. Hex editor shows no differences. Makes me think that maybe there is an issue with the tool. Try converting manually the bin manually and do a bin compare and see if the code is there. Info on the bank swapping process is in the "eec disassembly" write up.

Are you using tool from custom ecm solutions to swap the banks?

You are not going to be able to pull the bin using vxdiag and forscan. I know some people like them, but I would not trust a vxdiag product to read and write to an ecm. Most vxdiag devices try to act like some other type of diagnostic interface. I own the blue and black vxdiag interface. Very glitchy doing the job it is designed for (gm stuff)
Depending on what you are trying to do, you may have an easier time with a commercial product such as HP tuners or SCT. I haven't used SCT in about 15 yrs and that was on eec v stuff. I am a current user of HP tuners product. The learning curve is not as steep as it would be for you to figure out the diy method.
For example

with a commercial product
-buy interface/software combo
-license the PCM you are wanting to calibrate
-read, make changes, and write!

With diy stuff

-obtain the software to read write your PCM
-obtain compatible hardware to read write your PCM that is compatible with the software you are using
-figure out if there is a definition file (xdf) publically available for your strategy and obtain
-figure out if definition file is complete enough to make the necessary changes to your strategy. (This is also an issue with commercial products)
-then read, make changes and write. (Hopefully the software you have corrects the checksum)

Maybe someone else can chime in and give an opinion on current sct products that would be compatible with your vehicle.

None the less welcome to the world of "tuning" and good luck with your project.

Do you have any reference sources? Would like to read up on this.
The writing has been on the wall for a while. The dealer I work for hasn't had much inventory for over 2 yrs.