Ls Droid - Android BT Pcm flashing P01&P59 Cal+OS+ Clone

They go by many names, P01, P59, VPW, '0411 etc . Circa 1999 to 2006. All VPW OBD2 PCMs.
Posts: 62
Joined: Thu Sep 21, 2017 3:00 pm

Ls Droid - Android BT Pcm flashing P01&P59 Cal+OS+ Clone

Postby 160plus » Fri Feb 22, 2019 5:51 pm

I'm already maintaining nearly a dozen threads on various forums and Facebook groups so I'll keep this as short and to the point as I can.

I have been working with Antus, NSFW and others on the PCM Hammer for over a year now. During that time I've also been developing a free Android based app for flashing the P01 and P59 pcm's. My app was running in parallel with the PCM Hammer during the development of the bin reading last srping/early summer. Over the summer I continued development on my app while a suitable flash kernel for reading was found. Near the end of summer I got in touch with Kur4o on Gearhead-EFI and we started development of a flash kernel. This is where my app and the PCM Hammer parted ways and started down separate paths.

I wasn't just looking to create something to read and write most files I wanted to be able to flash anything...well anything the PCM would be able to use :)

I also wanted to address the shortcomings that other flash tools suffered from and looking back over the last 20 years it was pretty easy to make a list of ways to kill a pcm while flashing.

I have no idea how Kur4o was able to pull of some of the things we wanted to address but over the course of several months we created what I would call "Virtually" a full proof flash kernel and I was able to create a number of algorithms in my app for PCM recovery in ways that have never been attempted before. It took nearly a month making slight tweaks to the app and the flash kernel to pull off what I wanted but in the end the results were almost breath taking.

If a flash fails with any tool in just about every case my app will still be able to recover the pcm. With 2.5kb worth of data on the flash chip I can reliably recover a pcm after a couple of attempts, with closer to 4kb worth of data it will recover with out any issues on the first attempt every time.

While we were creating the flash kernel I was also looking for exploits in the pcm's circuit board design and I was able to find exactly what I was looking for. In the case of a PCM that has become unresponsive due to a failed flash the pcm can be forced to boot into 1 of 3 recovery modes. The recovery mode it boots into is based on what part of the flash chip has corrupted or invalid data....or perhaps nothing at all on it. Using this method in conjunction with my Android app has made recovery of a failed flash into a very simple and quick process.

I have had people testing the app for almost 3 months. Middle of January I had about a dozen people who were testing my app do every thing they could think of that would brick a pcm to the point my app could not recover the pcm. They were given specific instructions to meet the minimum of 3kb worth of data before attempting to brick a PCM and only 1 exploit was found. It was obscure enough that it wasn't even worth looking into a way to correct the issue with the flash kernel. It was the type of thing you would have to do about every stupid thing you could think of in a very specific order for the pcm to brick.

Last week I moved from a closed testing group to an open Alpha on a per request basis just to make sure there isn't some odd underlying compatibility issue on uncommon types of devices. For example the Read version of the App will work on Chrome OS with an Android APK plugin but the write version of the app has some odd screen issues making it almost impossible to use. It wasn't intended to run on the Chrome OS but it was helpful to know it's not going to be reliable with it.

If you would like to try out the "Pre-release" version of the write side of the app you can send me a PM.

The app will work on Android 6.0 and higher
The app will only work with the Obdlink Lx, Mx or Mx+ Bt devices
While no one has run into any issue with the app at this point that's not to say it isn't possible. This is an alpha version and may still have bugs that no one's found yet or there may be a compatibility issue with a type of phone that hasn't been tested yet. I would not suggest running out and using this on your daily driver...it may not end well.

The app is fully functional.....
P01 and P59 calibration write takes between 2 and 3 minutes depending on how fast the phone is.

P01 OS write takes about 10 minutes on most phones, a full PCM clone takes about 12 minutes.

P59 OS write takes about 18 minutes and a clone takes about 20 minutes.

The Obdlink devices only work at 1x speeds so they are a slow but in most cases the time a calibration write takes even at 1x isn't long enough to make it a big deal. An OS write on a P59 is about the only thing slow enough that's going to annoy people.







Posts: 58
Joined: Wed Jul 05, 2017 8:30 am
Location: TX USA

Re: Ls Droid - Android BT Pcm flashing P01&P59 Cal+OS+ Clone

Postby MudDuck514 » Fri Feb 22, 2019 6:27 pm

Hi all,

AWESOME work Pete!!!

Now I just need to buy an OBD Link LX adapter.

Mike

User avatar
Posts: 162
Joined: Fri Feb 02, 2018 3:13 pm

Re: Ls Droid - Android BT Pcm flashing P01&P59 Cal+OS+ Clone

Postby NSFW » Fri Feb 22, 2019 8:03 pm

Right on!

This is a great time to be playing with LS engines.
Please don't PM me with questions about tuning or flashing - start a thread instead. Thanks!

Posts: 3140
Joined: Mon Aug 02, 2010 6:35 pm

Re: Ls Droid - Android BT Pcm flashing P01&P59 Cal+OS+ Clone

Postby Dylan » Fri Feb 22, 2019 8:16 pm

I have some of your previous work and it's fantastic.

Good to see the enthusiasm in this one

Posts: 7
Joined: Wed Feb 13, 2019 9:56 am

Re: Ls Droid - Android BT Pcm flashing P01&P59 Cal+OS+ Clone

Postby Speedy » Sat Feb 23, 2019 12:40 pm

The following tests were conducted on a P01 512k PCM service# 09354896, with operating system 9381344. A Samsung J3 (s327vl) Android v6.0.1, OBDLink MX bluetooth and bench harness were utilized.

LS Droid Flash v2.1.6 VIN/Serial change
-BT_ON: ok
-Id_Pcm: ok, vin/serial/osid all correct. Seed 3B98 Key FB12
-VIN# Change: ok, functional after all power removed.
-Serial# Change: Repeatedly failed. "Wrong Length" warning appears momentarily, despite correct 12 digit entry. Same results, after checking Alt Serial Write box "Wrong Length."

LS Droid Alpha v5.3.1 (Read Only)
-BT_ON: ok
-ID_PCM: Repeatedly failed. Warning box appears on screen, blinking sporadically "Invalid text operation Segment: Start (11) + length (8) -1 exceeds text length (3). END APPLICATION." Phone gets buggy, app stops, phone will then go to restart screen for several seconds.

The same '4896 P01 PCM had issues with PCM Hammer v4 and v5, utilizing the AllPro USB. It repeatedly failed the following:
-Quick Comparison
-Test Write
-Write Calibration
-Write Parameters (Clone)

Antus suspected bad checksums. After review of the attached .bin file and xdf, he determined checksums were good.

I will seek an extra '0411 P01 PCM for comparison testing, next weekend.
Attachments
99-00 F+Y Body XDF.zip
XDFs for 9360361 and 9381344 O/S
(485.17 KiB) Downloaded 5 times
My Xtra P01 PCM '00 Silverado 1500 4.8 4l60e.bin
successfull read w/ PCM Hammer v4
(512 KiB) Downloaded 4 times
Screenshot_20190221-093051.png
warning blinks sporadically, then app stops
Screenshot_20190221-093042.png
ok to this point

Posts: 62
Joined: Thu Sep 21, 2017 3:00 pm

Re: Ls Droid - Android BT Pcm flashing P01&P59 Cal+OS+ Clone

Postby 160plus » Sat Feb 23, 2019 4:30 pm

Speedy wrote:The following tests were conducted on a P01 512k PCM service# 09354896, with operating system 9381344. A Samsung J3 (s327vl) Android v6.0.1, OBDLink MX bluetooth and bench harness were utilized.

LS Droid Flash v2.1.6 VIN/Serial change
-BT_ON: ok
-Id_Pcm: ok, vin/serial/osid all correct. Seed 3B98 Key FB12
-VIN# Change: ok, functional after all power removed.
-Serial# Change: Repeatedly failed. "Wrong Length" warning appears momentarily, despite correct 12 digit entry. Same results, after checking Alt Serial Write box "Wrong Length."

LS Droid Alpha v5.3.1 (Read Only)
-BT_ON: ok
-ID_PCM: Repeatedly failed. Warning box appears on screen, blinking sporadically "Invalid text operation Segment: Start (11) + length (8) -1 exceeds text length (3). END APPLICATION." Phone gets buggy, app stops, phone will then go to restart screen for several seconds.

The same '4896 P01 PCM had issues with PCM Hammer v4 and v5, utilizing the AllPro USB. It repeatedly failed the following:
-Quick Comparison
-Test Write
-Write Calibration
-Write Parameters (Clone)

Antus suspected bad checksums. After review of the attached .bin file and xdf, he determined checksums were good.

I will seek an extra '0411 P01 PCM for comparison testing, next weekend.


Sounds like you need to update your OBDLinks firmware..... or that you have an issue with the pcm on your bench. The reason I suspect a PCM issue is that the Allpro use's Elm commands. Ls Droid Read has ZERO Elm commands used for sending or reading data in the app. The app is built around the ST command set(not to be confused with the Elm AT command set).

In your screen shot the word STOPPED appears. This will only occur when the Obdlink tries to send data while the PCM is still sending data to the OBDLink. SO that means the port on the Obdlink didn't close or that the PCM likely isn't sending a proper end of frame message so the Obdlink knows to close the port.

It's also possible your bench harness isn't as "good" as you think it is. I just had someone using the write app run into issues that they ended up tracing back to poor connections in the bench harness they were using.

As for Ls Droid flash 2.1.6 I have never had anyone run into an issue with the length of the number they entered. I would suggest counting from 1 to 12 in HEX for a "test" serial number to write and then adding or subtracting a digit on the end if it still gives you an error.

Posts: 58
Joined: Wed Jul 05, 2017 8:30 am
Location: TX USA

Re: Ls Droid - Android BT Pcm flashing P01&P59 Cal+OS+ Clone

Postby MudDuck514 » Sun Feb 24, 2019 1:20 am

Hi all,

Pete, is this due to the fact it uses an STN11xx series chip?
The app will only work with the Obdlink Lx, Mx or Mx+ Bt devices
The app is built around the ST command set(not to be confused with the Elm AT command set).

Would a devices built from a GENUINE STN1110 and an HC06 work?
Just curious as I have one of the ICs that they gave me! (Free for the asking on there website)

Mike

Posts: 62
Joined: Thu Sep 21, 2017 3:00 pm

Re: Ls Droid - Android BT Pcm flashing P01&P59 Cal+OS+ Clone

Postby 160plus » Sun Feb 24, 2019 4:09 am

The Lx use the STN1131 and the Mx uses the STN1151. I'm not sure of the Mx+ chip but it is probably the 22XX family chip.

From a command standpoint the STN1100 does work with the ST commands my app is built with, however I'm not sure how large the buffer on the 1100 chip is. I use 2048 byte blocks for reading and writing......so if the STN 1100 has a buffer of at least 2064 bytes it would work.

You can check the buffer size by sending a message formatted for data length.

STPX H:6C10F0, L:2064 \r(or hit enter)

The chip will respond with one of 2 answers. If it gives you a prompt that says "DATA>" then the buffer is larger enough to work with my apps. If it returns "BUFFER FULL" then thats more then it can handle. You could whittle the number of bytes down until you find what the buffer is capable of though.

Posts: 58
Joined: Wed Jul 05, 2017 8:30 am
Location: TX USA

Re: Ls Droid - Android BT Pcm flashing P01&P59 Cal+OS+ Clone

Postby MudDuck514 » Sun Feb 24, 2019 11:17 am

Hi all,

Pete thanks for the response. Guess I'll need to cobble something together using the chip I have. (STN1110 28-pin DIP)
From what I can tell from the OBDSolutions website [url](https://www.obdsol.com/solutions/chips/[/url]) they technically make 3 chips:
STN1110, STN1170, and STN2120 with the STN1110 chip not having built-in CANBUS support for GM Single-Wire CAN or FORD Medium-Speed CAN (SW-CAN and MS-CAN).
I THINK that I read somewhere that the STN113x and STN115x is what sScanTool uses to ID the particular device it is in. BUT I could be wrong.

Mike

Site Admin
User avatar
Posts: 5618
Joined: Sat Feb 28, 2009 8:34 pm

Re: Ls Droid - Android BT Pcm flashing P01&P59 Cal+OS+ Clone

Postby antus » Sun Feb 24, 2019 1:46 pm

Good app this. If you want to do it from an android device and have a bluetooth interface, give it a shot.
Have you read the FAQ? For lots of information and links to significant threads see here: viewtopic.php?f=7&t=1396

Next

Return to GM LS1 512Kbyte and 1Mbyte

Who is online

Users browsing this forum: No registered users and 2 guests