I've been waiting a long time for this.....I've been adding support for the flash tool I've been developing with Envyous Customs into LS Droid over the last week and it's rather impressive if I don't say so myself
Android flashing.....over Bluetooth....Naw it'll never be reliable and sure as hell won't be fast



What's the flash time like these days for an OS swap on a P59? As in....how long does it take with a commercial program/flash tool?

 

Just touching base PeteS160. Still haven't had a chance to do the suggested testing yet as have been flat out with work but will get straight back to you as soon as I do.

 

Did you ever figure out why the update screen didn't work in Post #391?

I'm also having the same situation where the App opens, runs a Version Check, Says it's Ready, then I get the blank screen and can't update past Beta 0.2.0 (I used your link in this thread to install 0.2.0). I tried both normal phone internet connection and Wi-Fi internet connection.

My phone is a Samsung S5 Active with Android 6.0.1, which passes the Version Check.

All the other parts of the App seems to work fine, I just can't update to the V6 Write support. The V6 stuff was my main reason to try the App out, I have a 4.3 S10 and a GM 3400 FWD I wanted to play with.

Even if you could post a link to the most current version I can install it that way, just like I did with the 0.2.0 update you posted previous, it installed fine.

Thanks !

 

There are a number of reason people might get a blank screen. In most case people had an add on security program/web shield that was blocking the web connection. In some cases it was also due to insufficient premissions being given when the app was installed. Devices that were upgraded to Android 6.0.1 do not exhibit the exact same behavior as devices that came with 6.0.1 installed as the base OS on the device. When the OS is updated there are cases where permission settings may not be correctly requested and would block the apps attempt to load the web page.

V0.2.0 is the most recent public release I have done and FWD V6 flashing is not enabled. Due to a limited amount of testing and zero chance of recovery outside of whats been done in the flash kernel to try and "save" the PCM if something goes wrong on those FWD computers I have been very reluctant to release the update. And since it turns out there is almost zero interest in flashing these FWD computers it's not something I've been all that concerned with.

Depending on the year of the S10 ECU it's probally already supported by the LS flash routine. Those trucks either had the 'Black Box" pcm or they got the LS style P01/P59 computers. They are not in any way related to the FWD V6 computers.

Now if it turns out it is a black box PCM, it's not going to be supported either way. Your only option would be to repin the harness to use a P01 or P59 computer.

 

It doesn't get much faster then this....

 

Wow, can't wait until the hardware is ready!! Count me in for one!!

 

Thanks, I must have misunderstood something I read about V6 Write being enabled in an update. I previously checked to see if I had any security items on the phone enabled, I didn't see anything but I may have missed it.

The S10 PCM is an 0411 P01, I made sure to get that one specifically for what I'm doing. I wrote to it today and it does seem to work fine, I was waiting on my OBDLink which arrived yesterday.

 

Hi all:

Pete, when I had the problem with MY Samsung On5, I had just performed a factory reset on it!
I think it might be a bug with Android 6.01.. who knows, I sure don't.

As for V6 Flashing (NOT the 4.3l that uses an '0411) THAT is MY main need.
How many others are there here that are waiting? Sound off!!!

Mike

 

if you have a "spare" FWD V6 computer your willing to risk you can PM me and I'd be happy to give you a copy of the app with the FWD Pcm flashing enabled. I've personally tested it pretty extensively on the bench with a couple of random modules hooked up just to make sure they didn't freak it out and a couple of others have done a reasonable amount of bench testing but none of them were attempting to crash the app or test the flash kernels limits. Only 1 person has done any kind of "In vehicle" testing with it and they were absolutely positive every module on the data bus was in good working order and also had no trouble flashing with it.

What makes the V6 so much different then the P01/P59 stuff found on the SBC and LS engines is they do not have a separate section on the flash chip for calibration data. Part of the OS and all of the calibration data as well as the check bytes for the boot sector are ALL in the same block. If ANYTHING goes wrong there is no recovery mode to fall back on. The ONLY thing that will save you if something goes wrong is going to be from the changes made in how all the flash kernels work.

The changes made to how the kernels work are....something unlike anything that's ever been done before and is also why they make me a bit apprehensive to release.

A typical flash kernel has a command that can be sent to "Exit" the kernel at any point in time regardless if the flash is complete....or if exiting would even be "Safe" with out bricking the PCM. Ls Droid BetaV0.2.0 has the exit code disabled if the boot block is erased but not fully written. However the PCM can still choose to forcibly exit the flash kernel if it tries to do something that's out of bounds or it doesn't like something on the data bus that may have gone very wrong. In these cases it would be possible for the PCM to force the kernel to exit...but may end up bricking the PCM when it does so. Because the Calibration data in the V6 is outside of the boot block but has data that impacts the boot block similar methods to try and keep the kernel running at all costs were not possible. So rather then dealing with a possibility the PCM may try to force the kernel to exit....or if the app was not shut down or restarted correctly a decision was made to remove ALL exit points in the primary kernel.

What this means is..... there is no command that can be used to exit the flash kernel until the kernel see that the flash has completed. The kernel can not self exit, the PCM can not force it to exit...the ONLY way the kernel can be removed it by removing ALL power from the PCM. Even turning the key off isn't able to shut down or exit the kernel anymore. But....this also means you are able to read the PCM if a write fails part of the way though now. When the read is completed..... even if the app tried to exit the flash kernel... like it should when using a read kernel....it won't. The kernel will continue running until it sees a valid flash complete message triggered. Being able to read back the PCM after it fails on a block write is about the most valuable piece of information possible. You can see what was in the block that the PCM didn't like. Maybe there was data corruption on the bus from noise....maybe battery voltage was low enough that it was impacting how the bus is written or maybe data was mixed up during the BT transmission. You can compare the read back to the write log and see exactly where things went wrong, something that was also not possible before.

In short....once a write is started you have 2 outcomes. It completes or you have a paper weight. If it doesn't complete the kernel can run for days on end and keep the PCM alive as long as it has power to the B+ input on the PCM. This is so that any issues can be resolved by working 1 on 1 with someone to resolve what ever the issue is....it it also means I need to have the free time to spend working with someone and that is not something I can always promise.

 

Hi Pete,
Thanks for the info. While I understand what you are getting at - that there is NO recovery routine in the PCM - most of the technical aspects a still a bit over my head.
Looks like I'll need to acquire a spare PCM to play with for the 3.4l v6 in my van. Fortunately there a a few in my area, though I have NO idea how much the places want, or if they are even any good.

Mike.

P.S. At this point in time I do NOT need the app as I can't use it - still looking forward to the release of the new interface you all are developing!!!

 

You can pick them up on ebay pretty cheap most of the time. I've bought 5 or 6 of the V6 one's and they usually cost $30-$40 bucks. Look for something in the 2001-2005 year range. 2000 will be splitting hairs on the Seed/Key algorithm and 06 is going to be dependent on where the vehicle was built and the production date.

 

Hi Pete,

Thanks for the info on the PCMs.

Mike

 

Followed a link here from GMT400.com ... @PeteS160 let me just preface this with a big thank you for all the work you've put into this... I'm in awe. I have HPTuners currently and a 0411 swapped 350/5-speed 97 GMC Sierra I intend to either LS swap or 24x reluctor swap at some point, and either (from what I've read) requires an OS swap to the PCM, which would cost me another two HPT credits to a PCM I've already licensed, something that's been putting off the project longer and longer.. Everything I see here makes my prospective swap that much more doable. Definitely count me in for one of those Xpro interfaces when you get them into production! I have a few spare 0411s and at least one P59 to work with, so I don't see breaking things too badly

 

So.... I did a thing..... and added the ability to swap calibration segments in Ls Droid

 

That will come in handy, especially with the limited, only 1 XDF for the P59 pcms.

 

pete did you ever figure out a way to write vin & serial to p59's without opening the case?

 

Clone the PCM from a source file with the security block you want to use then flash just the OS you want to use back onto the PCM. Right now that's about the best solution I have.

 

right arm. thats easier than what i'm doing now.

HMU if you wanna talk PID boost controllers again. I'm over my holley phase haha

 

Is that a possibility? Adding a PID to the stock ECU?

 

yes and no. Pete and I were jabbering about stand alone boost controller that ran off canbus data. I had poo-pooh'd the PID idea since I really didnt quite understand how well it works when set up correctly.

But yes, on the stock pcm it was supposed to be possible with the introduction of the HPT MVPI 1 pro. it had four working inputs from the beginning, with 4 user configurable outputs and tables to come later....which never came. much to the disappointment of those of us that bought the pro for that reason.

That's all ancient history now of course.

If there was someone motivated enough they could use existing, unused PCM logic switching (like egr for example) to control another PID. Would take a pretty savvy coder though