ECU/PCM clone process & pricing

[\/\/0j0]

I was having errors similar to that. I used a 12v power supply that offered a more robust current supply and it seemed to help. The other thing that helped tremendously was replacing the failing hard drive in the windows laptop I was using with a SSD. If the computer can't ingest the data stream that is being sent to it fast enough, it can cause corrupt files. I wonder if this might be the case with your virtualized windows machine on older Mac hardware

Sponsored

 

[DailyDrivenTJ]

I was having errors similar to that. I used a 12v power supply that offered a more robust current supply and it seemed to help. The other thing that helped tremendously was replacing the failing hard drive in the windows laptop I was using with a SSD. If the computer can't ingest the data stream that is being sent to it fast enough, it can cause corrupt files. I wonder if this might be the case with your virtualized windows machine on older Mac hardware

I have another machine coming in the next few days. My MBP already has SSD. Ordered a government surplus tough laptop with windows and SSD to keep it in the garage. I will try it again and see if the read process goes properly. Will report back in a few days.

 

[Firehawkcpo]

I got it setup with Virtualbox that I am running a virtual machine running Win7 off of my old MacBook Pro.

I should be able to share this image and you would be able to do the whole process off of a Mac or at least a 2013 MacBook Pro. Since it is a virtual machine there is no real worries with virus or malware.

I am practicing on the new ECU and when I read and save the file at the end I get the following pop up.

Once the binary is saved it pops up check sum error. Any thoughts?

Did you uncheck the box to verify the checksum?

 

[\/\/0j0]

I have another machine coming in the next few days. My MBP already has SSD. Ordered a government surplus tough laptop with windows and SSD to keep it in the garage. I will try it again and see if the read process goes properly. Will report back in a few days.

I didn't mean to imply an SSD was necessary. In my case, I was dealing with an older laptop with hardware that couldn't keep up due to a failing drive. A virtualized operating system can be resource intensive, especially in handling data between the host hardware and virtual OS. Not saying this is the issue but may be a variable worth investigating. Sounds like you're on the right track with garage computer running a native OS. At least that way you've minimized variables to start troubleshooting if you have issues with the new rig.

 

[DailyDrivenTJ]

Did you uncheck the box to verify the checksum?

I did and when I do, I do not get the error as it shouldn't.

So here is a question for yall, are you guys unchecking the verify option? Also if you do, do you get the same error as I am seeing?

I didn't mean to imply an SSD was necessary. In my case, I was dealing with an older laptop with hardware that couldn't keep up due to a failing drive. A virtualized operating system can be resource intensive, especially in handling data between the host hardware and virtual OS. Not saying this is the issue but may be a variable worth investigating. Sounds like you're on the right track with garage computer running a native OS. At least that way you've minimized variables to start troubleshooting if you have issues with the new rig.

I know you didn't mean that SSD is required.

I am not sure if the it is virtual machine is causing the problem. I am wondering if it is just how the software is. Trying to confirm if the others were having similar issue.

Having said that I am posting this from my garage laptop.

 

[DailyDrivenTJ]

Here is a update and I would like to ask some of you who have backed up their original ECM for help.

I tried this on the native Windows machine and I am getting the same error when I tried to read the ECM.

Interestingly, the virtual machine did not need to power cycle the Scanmatik but the native Windows machine needs the power disconnect and reconnect right before the read operation.

Can someone just try the read with verification option on for me?

Thank you.

 

[Firehawkcpo]

Here is a update and I would like to ask some of you who have backed up their original ECM for help.

I tried this on the native Windows machine and I am getting the same error when I tried to read the ECM.

Interestingly, the virtual machine did not need to power cycle the Scanmatik but the native Windows machine needs the power disconnect and reconnect right before the read operation.

Can someone just try the read with verification option on for me?

Thank you.

When the power prompt came up I selected no and power cycled manually to get scanmatik to read the pcm. Hope this helps. The kit I have has 2 power cables, one label is battery, the other is 12v. I found to read is 12v and to write is battery or vice versa (bad memory). I did not need to do the CRC check.

 

[DailyDrivenTJ]

When the power prompt came up I selected no and power cycled manually to get scanmatik to read the pcm. Hope this helps. The kit I have has 2 power cables, one label is battery, the other is 12v. I found to read is 12v and to write is battery or vice versa (bad memory). I did not need to do the CRC check.

I did not realize there is difference in 12v and battery distinction. I will try that tomorrow.

Thank you!

 

[DailyDrivenTJ]

Working on this right now and it seems like the binary in the new PCM is what is causing the checksum error. Hooked it up to the PCM on the vehicle and read the binary and checksum is correct.

Writing the backed up binary into the new PCM as we speak.

 

[DailyDrivenTJ]

So it is done!

Ended up doing this on a MacOS running virtual machine on Windows7 image.

This seemed to work better than Windows 10 machine as I did not have to powercycle the programmer to initiate read/write operation.

Also the checksum error only occurred while reading the blank PCM "Flash" Binary. When reading the PCM on the truck, checksum was error free.

No red light with new cloned PCM. Now did you all remove the original PCM completely install the tuned the PCM?

I am going to drive up one day to Vancouver, BC to get the PCM programmed and drive back.

 

[dgeist]

Just installed my tuned ECU today. Before installing, I popped it on the flash tool (same as I had done with my factory original to copy and backup that tune in the first place) and I was unable to read the ECU. No specific errors came up, just a timeout...

Has anyone else had issues reading an ECU (with the procedures discussed here) post-tune?

 

[Gregj]

Yes, the “repaired” ECU won’t read, I just got a “completed unsuccessfully” message. @rharr had a theory about it.
Gregj

 

[dgeist]

Yes, the “repaired” ECU won’t read, I just got a “completed unsuccessfully” message.

WTH, man! How are we supposed to make a backup (in the same way that we made a backup of the factory ECU image) in case THAT one gets overwritten. Isn't that kinda the point of being able to save ECU flash images? I'm calling my congressman...oh, wait.

 

[DailyDrivenTJ]

@dgeist Which tune did you go with by whom?

I am curious to which tune y'all went with.

 

[Firehawkcpo]

@dgeist Which tune did you go with by whom?

I am curious to which tune y'all went with.

I went with the tow tune because I plan to tow the buggies.

Sponsored