Has anyone used the COS3 bin that's floating around here? I've been looking at it and it appears that almost none of the tables are properly populated. I'd hate to spend hours on end to straighten it out just to find it doesn't work.
Has anyone used the COS3 bin that's floating around here? I've been looking at it and it appears that almost none of the tables are properly populated. I'd hate to spend hours on end to straighten it out just to find it doesn't work.
I have no experience using this OS but have you seen this thread? Maybe it will help you locate more specific answers?
I have its been a learning experience. I been using LTR's xdf seems fine just figuring out the fuel and PE just wish the odd wasn't locked so I could farther the rev reverse engineering. I've tried messaging him to get an unlocked version. If you run crossed one let me know. The bin I have is for a 5.7 auto.Originally Posted by Chromedome
I donated numerous XDFs for all to use. That these XDFs are locked, is the only "cost" of them being free of charge.
Feel free to write your own XDF, purpose built for your specific needs.
Last edited by LRT; 1 Week Ago at 11:46 PM. Reason: typo
I wasn't trying to be rude. Or anything. I do appreciate everything you've done. I've got by with jumping to the cos 5 to set baro parameters.
I know it not the smartest idea but it worked for my purpose.
I'm doing it all the hard way with a 68k disassembler and memorizing the chip sets but it's working slowly but surely
I've talked to nfsw about writing a cos for boost but I've got a lot to learn yet to have the skills to achieve that
I donated 11 XDFs to the general public.
This first few XDFs took me well over 100 hours, per XDF, to complete. Once I got into the swing of things, the last XDFs took me around 40 hours each
That works out to nearly 1000 hours of work donated to people that I have never met.
HP Tuners, EFILive, TunerPro, PCM Hammer, and LS Droid are all "locked" - that is how *.exe files or APK files are structured - the difference is that these do not do not tell you that they are locked.
Some freeware will have a "nag" window, that highlights who wrote the software, and encourages you to visit their website. Others will feature a "donate" popup - unless the company is a registered charitable organization, any monies forwarded are not a donation, but rather a payment.
My XDFs have no such features - they function the same for you, as they do for me.
i'd guess your reason for protecting your XDFs are just so commercial guys don't come along and try to profit by your work?
i just hope you have a plan for when you get bored/disinterested/dead, so your hard work can continue in the hands of others, especially when the vehicles it covers slip into obscurity. i see a lot of really good tools that become obsolete and then have to be recreated from the ground up, which is a total waste in every way.
I've notice all you done. It's a lot and I speak for many people when I say you rock. Not to mention all the time you've spent explain how to use them.
I really only need to add two things to yours maybe three
1. Long Term fuel trim disable flag.
2. The barO refresh parameters
Maybe 3. Short term fuel trim at idle. Disable flag. Just what efilive instructions say to do. But if the VE TABLE IS tuned well I'm not sure that is needed.
Just didn't want to ask for you to do it since you've done so much.
I have one more question should the checksum plug-ins be working for this O.S. didn't know if it would with there being code out of the stock O.S's addresses.
So which COS is better efi or hptuners. I plan to crack open some of the cos because they are really basic piece of shit compared to the charge it is being paid.
Or even improve or add some basic patches first. Which needs to be done first. enable / disable hardcoded features.
It is not enough for you that I donated 11 XDFs to the general public ?
This is why I often regret having ever posted the XDFs - some people feel the need to dictate to me, how I should manage my own work.
The XDF and the Checksum Plugin must come from the same source - they are written to work together. Using an XDF from one source, and a Checksum Plugin from another source, may lead to the Checksums failing to be properly calculated / updated.
I'm using the ones you posted with the cos xdfs. I was just assuming it would work. Never had a problem tell I upgrade my laptop. Now it give s me checksum error. I thought it might be the updated tunerpro I downloaded. I'll figure out what I'm doing wrong.
I'm not dictating what you do with your work just would be nice the work you've done is crazy and your skills are well above mine. I'm just happy If i see a stop instruction I know what it is. I'm using pcmlogger and that's a big help finding addresses.
What did you use to reverse engineer the os's? If you don't feel like revealing your secrets I do understand. Just trying to learn the best way.
was i criticizing what you've done in any way? was anyone?
does the word hope mean dictate to you?
it's nice you gave away 11 XDFs. it's very generous. i never said otherwise.
You can try to do the verbal "Texas Two Step" all that you want, just like any politician would, but the theme of your initial comment in this thread is indeed as I described.
Reply With Quote
Bookmarks