PeteS160

Already have one that's about done for the 1mb with the 12587603 OS that does 4l60,4l80, manual trans, flex fuel, DBC or DBW and has support for 3 bar map with custom OS's. Last I checked the tables for the extended MAP range was still being worked on but the rest of the Xdf was done. It's also suitable for use in a number of stock vehicles with segment swaps so it plays nice with Bcm's, Clusters, Abs etc.

The OS will work with most 1/2, 3/4 and 1 ton trucks, 3/4 and 1 ton vans. It also works with the 2003 and some 2004 corvettes as well as the Trailblazer/Envoys in 04.

The OS is also compatible with pcm's from 2003 to early 2006.

Scott68B

iTrader: (1)

Wow, this is so cool! I need to get a compatible BT device real soon!

Thank you for all your work!

Scott68B

iTrader: (1)

Are we better waiting until ODBLink has the 1x stuff in place before buying or is it possible to update the firmware?

poorboy

this thread is huge where do i start? ok so i joined ls1tech today just so i can hopefully learn something from this. im a little behind the times here in rural mn. ive owned an old chevy pickup for quite a few years now and i have dreamt of dropping a newer 6.0 in it for the longest time. all the years my project has been on hold i shouldve been doing my homework. here we are in 2018 and i picked up a deal off craigslist and i finally got my dream motor a gen iii 6.0 out of a 2004 denali. embarrassed to say this is my first efi swap and its really sent my head spinning. i have been picking up books and hitting the forums for a couple months just trying to wrap my brain around the emense amount of directions i can go with this build. It feels like destiny that i come across this thread in my reading from last night. all the crap ive been trying to weigh out like do i go standalone vs do i teach myself to rework a simple old stock pcm. All i can say is kudos to pete and his drive to take a great idea and push the limits of innovation with the technology we are blindly engulfed with today and making it work. This thread has answered so many questions that were going through my mind in my quest of why and how has the market gotten us here today. I thrive to improvise and i believe thats what hotrodding is all about. I will be shadowing this closely and next time i chime in i promise it will be more brief and to the point!

PeteS160

There's no reason to run out and buy one tomorrow, app's still got a little work before I release it and even then it's still READ ONLY for the time being until I can collect data from a larger pool of people using it.

It's very unlikely they would alter the hardware design if that was necessary to get 4x mode to work, I'm not saying it isn't possible but it'd be VERY unlikely that's something they'd be willing to do.

They have said in the past that 4x mode support should be possible with changes to the firmware (that is user update-able) but they have never actually tried it since it would require writing it into the firmware. There really isn't any reason the hardware shouldn't be able to support it unless it came down to something like the speed of the internal clock being too slow but that's not likely to be an issue.

PeteS160

I do need to find some time and update the original post since it's pretty old at this point...your not the only one that's said something about that so I apologize.

Now as for your swap, you've found a forum that has a LOT of knowledgeable people on here that I'm sure can help to answer any questions you might have as you prepare for the swap or while your working on. Searching the forum...even if your using google to search this forum will help to answer a lot of questions you might have and your likely going to find at least a couple of threads that have been posted here over the years that should answer most if not all your questions about the swap. Of course not every possible scenario can be found by searching and when you run into there I'm sure you'll find someone here that can help you.

And let me be the first to say..... welcome to the forum

Scott68B

iTrader: (1)

Well, a friend gave us an Amazon gift card so my wife and I split it and I ended up getting an OBDLink Lx. Should be here next week. I'll be testing your little read only app on my Samsung Galaxy Tab A.

PeteS160

Great news, an open source flash kernel is being written for use with my Android app & for use with the Pcm Hammer. It's going to be an all in one kernel that does both read and write. Writing a kernel is even harder then developing software to use it so they must also be tested and debugged just like normal programs would be.

Well there's a catch 22.....to develop the write aspect of the kernel it needs to be tested so changes can be made and it can be optimized. The issue is my App is read only, just like the Pcm Hammer.

Well.....my app was read only

Scott68B

iTrader: (1)

Wow! It's really happening, isn't it?

PeteS160

Yes.... Android read and write is really gonna happen

MudDuck514

Pete,
Were you ever able to get the USB feature working with your App?
I'd rather NOT have to buy multiple versions of the AllPro Adapter!
Mike

PeteS160

I do not have USB working and it's probably not going to either for a very long time. I'm going to point out again.....since I've pointed this out before the Allpro USB will not work. It's designed a bit different then the other devices.

At this point in time the only 2 devices I'm really focusing on are the Obdlink Lx and Mx.

MudDuck514

Pete,

Thanks for the reply.
I asked because I THOUGHT I read on here that you were TRYING to get it working but were a bit stuck on how to do so.
Looks like I'll plan on getting one of the board versions with the big connector that mates to a pre-made OBD2 cable. (I have one).
That way I can get an HC-06 BT Module for it.

Mike

PeteS160

It's been one year, 1 month and 8 days ago since I started working on this and while it's by no means complete I have a 512k/1mb "read only" version of LS Droid ready for use. This also includes the ability to change the vin number on the 512k and 1mb pcm's. It will also change the serial number on the 512K pcm's....1mb pcm's are still a ways out.

There have been a number of users from this form that have been doing some testing for me and after a great deal of work it appears all the noticeable bugs and random crashes have been worked out now. There are still some things that exhibit odd behavior if your looking for problems but all and all it's stable and reliable.

Step one - Turn the key/switched 12 volts on
Step two - connect the Obdlink Lx/Mx to the DLC
Step three - Start the app, connect to the device
Step four - Press id pcm
Step five - Read the pcms file or change the vin/serial number

If you are going to change the vin/serial you will need to press and hold the change button next to the item you want to alter.

When you read the pcm the file will be saved to the main storage directory on your device, this varies from phone to phone.

******Note - this version of Ls Droid will ONLY work with the Obdlink Lx/Mx

You can download this with instructions from
https://github.com/Loud160/LS_Droid

Or just the app directly from
https://drive.google.com/open?id=102...Tak_8nhIoMxWlE

truckdoug

iTrader: (26)

Hell yeah Pete! I know you've put a ton of hours into this he last 12 months.

Thank you a ton for advancing the cause! I owe you many cold beverages if we ever meet up.

PeteS160

I'm just doing what I can to help others

kpeters59

Any idea whether the new ScanTool OBDLink MX+ is a good choice for a new purchase intending on using it for this and your other projects?

I've had an MX since they were new and need a 2nd unit since I have 2 LSx vehicles now.

They sent me a promo that goes like this:


OBDLink MX+ is the newest addition to the OBDLink family that is even faster, more reliable, more feature-rich than its predecessors - and it simply BLOWS AWAY the competition.

Priced at $99.95, this all-new, professional-grade scan tool works with iOS devices and comes with a free enhanced diagnostics add-on for Ford, Mazda, Nissan, Toyota and GM owners.

It seems like they built what you told them they needed...

I still want the faster firmware for my old MX, ScanTool, if you're listening!

--KP

gofastwclass

iTrader: (2)

Thanks a ton!

PeteS160

So I've been playing with the flash side of things and the guy I'm working with from Gearhead EFI that's been developing a write kernel for LS Droid and the Pcm Hammer was able to make a crazy twisted off the wall idea I had into something unlike anything else done before.

Just so we're all on the same page I'm currently working on a full flash (OS +Cal) for the 0411 Pcm.

Now just about every one reading this has either experienced a bricked pcm or likely knows someone who has had a pcm brick while being flashed. If your flashing a new OS you know the damages involved and the obvious things that you NEVER want to do while flashing.......well what if I told you every thing you think you know about flashing and what's going to damage the PCM during a flash was wrong?

Reason flash fails #1> In a stock vehicle, lets say a 2002 F body.....2002 Silverado...it doesn't really matter what it's in. There are other modules on the data bus that must also be controlled and kept quite while your flashing a PCM or all hell breaks loose and will result in anything from the program refusing to flash the PCM if it can't quite all the modules or a flash failing mid write. So we need the tool/program running the flash to keep control of these modules while the PCM is being programmed.

Reason flash fails #2>If the tool falls off or gets unplugged while flashing the PCM your in BIG trouble. The program will have no idea where it was at when the tool lost commutation with the pcm. If your only writing calibration data you can probably still recover the pcm but if your flashing the OS as well then your in BIG trouble and will likely now have a pcm that's as useful as a paper weight.

Reason flash fails#3>If you turn the key off...or switch off your bench harness while the pcm is being flashing it has the same effect as unplugging the tool. When you turn it back on you will likely have a paper weight.

When you look at ANY of the above scenarios you can see it's actually rather easy to damage a pcm while it's being flashed. What you may not have expected is that all 3 of these can be prevented with code written into the flash kernel.

Lets pretend we are mid flash doing an OS swap....
First lets unplug the tool from the pcm. We've just established that with out the tool the data bus will "wake up" and all the modules will start talking again.
Next lets close the program we are using to flash with
To make sure we wreck the pcm lets turn the ignition switch off and go watch some TV for a couple of hours while we think about how bad this pcm is gonna be bricked.......or is it?

**************************Sample log of this in action, the data bus was being monitored externally to log what took place with out with out the tool being used connected to the bus.
--> 12 03 AD 00 6D 10 F0 36 00 xx xx FF xx xx B4 78 8E 8C 6C 00 01 38 3D 78 8E 70 FF FA 34 38 9F FE 20 02 90 6E FF FA 3A 38 8E 92 48 C5 22 3C FF FF D8 00 B2 85 6F 04 42 45 60 1C 2C 3C 00 00 28 00 BC 85 6F 0E DA 86 6B 06 4C 47 50 05 60 08 42 85 60 04 3A 3C 08 00 24 7C 00 01 1A 48 F8 12 59 40 B0 45 65 00 00 E8 31 C2 8E 70 36 38 8E 92 38 39 00 01 19 58 B6 44 6C 04 26 04 60 0A 38 39 00 01 19 56 B6 44 6E F2 4A 43 6D 42 B6 79 00 01 19 52 6C 04 42 43 60 7E 4A 38 8E 53 67 18 96 79 00 01 19 52 69 06 0C 43 D8 00 6C 02 26 01 C7 F9 00 01 19 5A 60 54 96 79 00 01 19 52 69 06 0C 43 D8 00 6C 02 26 01 C7 F9 00 01 19 5E 60 3C B6 79 00 01 19 54 6E BE 4A 38 8E 53 67 18 96 79 00 01 19 54 69 06 0C 43 D8 00 6C 02 26 01 C7 F9 00 01 19 5C 60 16 96 79 00 01 19 54 69 06 0C 43 D8 00 6C 02 26 01 C7 F9 00 01 19 60 6A 06 06 83 00 00 0F FF E0 83 E8 83 D6 78 8E 96 68 04 6B 10 60 14 0C 43 28 00 6E 08 0C 43 D8 00 6D 08 60 08 36 3C 28 00 60 02 26 01 38 39 00 01 19 64 B6 44 6C 04 26 04 60 0A 38 39 00 01 19 62 B6 44 6E F2 08 38 00 05 8E CA 66 18 4A 38 8E 53 66 30 4A 38 8E 54 66 2A 2A 03 4A 45 6C 02 44 45 4A 45 63 1E 4A 43 6F 0E 96 79 00 01 19 66 0C 43 7F FF 63 0E 60 0A D6 79 00 01 19 66 4A 43 6F 02 42 43 31 C3 8E 96 36 38 8E 94 D6 78 8E 96 68 0C 6A 06 36 3C 7F FF 60 04 36 3C 80 00 38 39 00 01 19 6A B6 44 6C 04 26 04 60 14 30 39 00 01 19 68 42 85 3A 00 22 03 48 C1 B2 85 6F 02 26 00 31 C3 8E 98 08 38 00 04 9C 2C 66 08 08 38 00 03 9C 2C 67 08 08 38 00 07 9C 2D 67 06 11 F8 98 0C 8E E4 08 38 00 07 8E CA 67 06 11 FC 00 07 8E E4 30 38 96 3A 36 00 42 44 18 38 8E E4 C8 FC 00 2A 45 F0 49 B0 00 01 21 8E 42 44 3A 3C A0 00 BA 43 63 04 E6 4B 60 04 36 3C 14 00 F8 12 31 40 31 C3 8E E2 36 38 85 80 0C 43 0D 00 64 04 26 04 60 06 E2 4B 04 43 06 80 24 7C 00 01 1A 1E F8 12 31 40 3C 03 34 38 A7 80 D4 4C C5 FC 00 05 85 FC 00 06 24 7C 00 01 1A 28 F8 12 21 40 4A 78 95 3E 66 06 36 3C 08 00 60 1A 42 83 36 38 95 40 E1 83 E7 83 86 F8 95 3E 69 06 0C 43 10 00 63 04 36 3C 10 00 32 38 8E E2 D2 78 95 3A 68 0C 6A 06 32 3C 7F
******************We don't get a response from the PCM because we've plug pulled the tool in the middle of it sending data to the pcm so this is only a partial data block that's been written.************

The Pcm hasn't received any response from the tool or seen any new data for 1.5 seconds and now PUT'S IT SELF in control of the data bus since there is no tool controlling the bus anymore.
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F

Ok the PCM has control of the data bus so it might be able to recover from this......NOPE we want a paper weight.....

So lets turn off the key.......
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F

You should be scratching your head at this point....
We've turned the key off and removed the flash tool so the pcm should have shut down......NOPE.....the Pcm isn't giving up on this flash and it will keep the bus active and in control. Do note that if you actually waited several hours your battery would likely be dead by that point.

Ok lets turn the key back on......well the pcm never stopped talking so we see more of the same thing.
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F
--> 05 00 8C FE 10 3F

Now lets take control of the data bus again....we restart the app and send.....
--> 05 00 6C FE F0 3F <<Sent by tool/program
--> 05 00 6C F0 10 3F <Pcm Answers
--> 05 00 6C 10 F0 34<Sent by tool/program
--> 07 00 6C F0 10 74 00 44<Pcm responds
**Now we send the first 1000 bytes of the bin file we want to flash**
--> 07 00 6C F0 10 76 00 78 <PCM Erasing block
--> 07 00 6C F0 10 76 00 78 <PCM Erasing block
--> 07 00 6C F0 10 76 00 78 <PCM Erasing block
--> 07 00 6C F0 10 76 00 78 <PCM Erasing block
--> 07 00 6C F0 10 76 00 73 <Blocks are now erased and the PCM can be written like this is a fresh start and nothing ever happened that shouldn't have.
--> 05 00 8C FE 10 3F < The Pcm will go back to bus control until the App starts sending the data to be written.

This may look really boring or you may not understand what all of this means so let me summarize this. The only legitimate reason why a pcm should ever be bricked is because the batter voltage drops too low to keep the pcm powered on or you were to physically disconnect ALL power from the pcm....not something that's going to happen accidentally. There is absolutely ZERO reason a pcm should ever be bricked during a flash. It's really sad that a couple of nobody's came up with this idea and was able to make it work in with just a couple of weeks worth of development and people have been bricking Pcm's for years only due to the way the flash kernels were written.

joecar

So during flashing, the PCM is controlled by the flashing kernel (aka boot loader)...

Good job