I opened the Bin repository and wanted to start a discussion. Unfortunately I cannot private message at this time so I will need to send this here.

I have created an unofficial fork of the Repo to learn how to work with GitHub. I will not link the repo here but it can be found under my same username. I have structured things quite differently and I'm happy to discuss. As of right now only some P59 Bins have been processed.

Issues are open on my repo if one prefers to discuss there.

 

Do either of you own any other tuning software?
If you know were to look for it, you could enable it on a stock file and read it back out to get the BIN with it enabled.

I don't currently have anything to read out bin files.

 

Looks like BoredTruck has been out for a couple months. Happy to hear any feedback on the repo. The biggest difference is a flatter folder structure and a metacards to allow searching among the bin files

Full credit, other then possibly a handful of files all BINs and XDFs were from BoredTrucks repo. Metacard info is from PCMBinBuilder and .gov vin lookup.

https://github.com/Snoman002/Engine-...Ilive-TunerCat

 

Technically all Gen3 OS's can enable lean cruise, just have to access all the background parameters that make those options fully enable.

 

Here's an 04 GTO bin for the P59 along with a Holden bin but I don't think you'll find an XDF for these to look at lean cruise settings.

 

Here is one XDF that has the enabler for 12212156, 12587603 and 12587604. Must be edited in TunerPro as HPT user defined places these parameters out of bounds off allowed memory address mods.

 

Hopefully notifications are on...

Give me a shout please.

 

do you have a xdf to work with a 12585950

 

Your best bet would be to switch to an OS that does have an XDF.

Operating Systems · LegacyNsfw/PcmHacks Wiki · GitHub

 

Hey All,
Been a good while, due to some unforeseen circumstances I had to step back from the repo, we had major issues with work and up until recently I was working insane hours, only got to see the sunlight during my lunch break kind of hours.
Anyway, I will be picking up where I left off in growing the repo, a lot has changed since I have disappeared so I will spend the next few days informing myself before I get back to work. My main priority will be growing the wiki, there was a lot of information I was sitting on before I left that I can push to the wiki, but it will need fact-checking before I publish it. I've learned a thing or two about GitHub so I will also work on improving the structure a bit more, I've received some helpful feedback and will work on applying that as well.

If any of the owners of the other repos that have popped up would like to reach out and merge efforts, I am all ears.
Here's my current priority list and this will be revised as time goes on, but I'm also open to suggestions from anyone.

• OBDLink Compatible Firmware Note
• Expand Troubleshooting Help, I have a couple of sabotaged PCMs that I can recover and document
• Tuning Help, This is something I sat on for a while, I have a number of skeleton guides on what parameters need to be changed for certain mods, for example, it's super tricky to find a good video that explains what tables need to be revised with a stage two cam, and what some good starting numbers are.
• Walkthroughs, Since the beginning there has been a very limited number of good resources that explain what each feature does and when they are correct to use

The above is what I'll be focusing on working on in the coming weeks, the order is by no means how I will work on them, some will have to be put on the back burner until I can get more information, and some will take a lot of man-hours to get right.
My apologies to everyone for my abrupt disappearance.
Paul

 

You should check out the Ls Droid Facebook group, its public so you don't need to join it or even be logged into Facebook to view it.

Pretty much everything you've outlined has been discussed in great detail(firmware versions for example). Several members of the group have been doing volunteer work for helping people get setup with Tuner Pro and explaining the basics of how to use Tuner Pro. I also have a number of professional tuners in the group that chime in from time to time answering questions that can be hard to find details on online.

There would defiantly be interest in walk though video or even a written guide for things like headers, Airbox removal, Cam tuning etc.

Due to the number of users I was seeing with Ls Droid I didn't really have any other option other then to create a Facebook group and it's worked out very well for the most part. While it's not a good way to retain information in the same way a forum does it does; it does work well for getting answers quickly in most cases.

 

Pete,
I am in the group and was gonna PM you to see if you were alright with me borrowing some of the more prevalent people in the group for some information if they are willing, specifically on the PCM recovery portions as those are what trip most people up. My ideas for the tuning and walkthrough sections are written guides with pictures of what needs to be done as those can be the easiest to follow when they are written right. As for the tuning part, that's where I am most comfortable doing write-ups, when I first began I didn't understand what each table did or the logic behind it but as time progressed I figured I was able to put two and two together and tune it just like any other platform.

 

Shot me an IM on Facebook, it sounds like you might be just the person I've been looking for.

One of the things I'm doing differently with Ls Droid for Windows(since displaying this is so much easier) is adding in as much information as possible and this includes written guides and embedded links for video's.

As for PCM Recovery......I have a special place for something like that if someone was to do a quality writeup with detailed pictures. I attempted to do it in Android but it was nearly impossible to display the information while trying to still interact with the apps UI. The way I've built Ls Droid for Windows I can removes the need to interact with the UI where the program starts a constant loop polling for frames from the databus, when it reads a frame that it knows what do to with it will lock onto the response and attempt to start the flash routine. If the flash routine fails or is reject it's able to jump right back to polling for frames again. I've had Dustin from the Ls Droid group do a bunch of testing for me with a BDM since I no longer have one that works on these computers where specific parts of the flash chip are erased or corrupted intentionally to make sure the programs able to deal with this type of thing in virtually any scenario.

 

Cam tuning guide is currently in progress, it'll be in written form factor with pictures of before and afters of the tables for a sloppy stage 2 cammed 5.3. That said, I am primarily focusing on the P59 XDF for now, I want to get a few guides out into the open and then work back and adapt the guides to the P01s, I haven't tuned a P01 yet so will need to familiarize myself with the XDFs.

I'm not familiar with the structure of XDFs, but is it possible to have two identical tables in different categories?
One of the things I would like to do is create new categories with all the parameters needed to tune something. For example, a category called cam tuning would have the necessary table for tuning idle and such, that way someone new to tuning can pull open the guide, have TunerPro open, and use the guide to go through each of the steps without having to pause and look for tables.

Also, maybe someone can correct me if I'm wrong, but I believe this is the first TunerPro cam tuning guide, the biggest flaw I see in the opensource LS tuning community is consistency, the XDFs are all different, there are no clear guides on what does what, what to change, or how to do it. One thing I want to try and do is to standardize a naming convention and structure in the XDFs for the P01 and P59, that way the guides would apply to both more or less. The XDF made by DzidaV8 already has everything logically structured, and the comments are helpful in understanding the parameters. I think that style of structure is the easiest to understand and find what you are looking for, the only other structure I see working is one similar to HPTuners so those tuning guides would also apply to the us.
The only way this would work is if the community adopts it, so thoughts or comments on the above?

Lastly, I am looking for one or two tuners who would be willing to read through the guides and fact check it, make recommendations, etc. If anyone is interested, please PM me and we will work things out.
Paul

 

Hi, I am trying to download the 12212156 XDF file but it only shows up as text when I click on it, how do you download it to use it?
Thanks!

 

Try clicking the "Raw" button, then right-click and "save as."

 

Thank you!

 

How to i tune these becides the lean cruise? i have not been able to access my 04 gto bin because there is no xdf for it.

 

" Try clicking the "Raw" button, then right-click and "save as." When I try to save as, it only will save as text. How do I convert the text file to xdf?
Thanks in advance.
Michael.

 

Would anyone happen to have a bin/xdf file for a 2001 Silverado 6.0/4L80 2wd with a sloppy stage 2 cam ? I don't know how to tune yet but don't want to buy a new stock cam when I can buy an upgrade for the same or less money. I am using LS droid and PCM hammer. I don't know of anyone in my area that can tune these . If it matters I'm putting it into a 1970 gm A body I have an 0411 PCM and a dbc throttle body