by xb9fog » Fri May 29, 2009 3:11 pm
There seems to be a lot of inaccurate information on a couple of other Buell Bulletin Boards regarding my integrity and how I gained the knowledge to put my products together. It appears there are others out there that feel I "stole" their knowledge and then turned around and started selling their knowledge as my own.
Although I freely admit there has been some limited collaboration with these individuals in the past, It was always a two way street - SHARING of information. I would provide information to them, they would provide information to me as a collaborative effort. For them to make statements like "I got him going" or "where Dave presents all the facts he got from me and other EcmSpy enthusiasts for free" is totally absurd and completely off base.
Since I can't post on the one board that this seems to be the main focus right now, I'll post the facts here as I see it, and have experienced it. I know this may seem lengthy but to get the complete picture there's a lot to tell.
My background
Tuning /Racing Background
I started tuning motorcycles in the '70s.When I was racing in the late 70s and early to mid 80s, I was tuning my own bikes that I raced. This is when I learned all my tuning fundamentals, although it was carburation, not Fuel injection.
All the fundamental tuning principals I learned during this time applied later to Fuel injection. I was fairly successful during this time, earning 4 WERA regional championships and 2 AMACCS Regional championships.
In 2002 I purchased my first Buell, an XB9R. At this time I started searching for anything I could find in the way of information on how the fuel injection system worked on the Buells. Information was scarce, and at this time EcmSpy or Direct Link software did not exist, and I did a lot of experimentation with stuff that didn't work very well, like resistors in the O2 circuit to trick the ECM into providing a little more fuel to the bike. I also purchased and installed a Power Commander and tuned it with limited success. Then Technoresearch came out with their Direct Link Tuning software, which I purchased as soon as it was available. I also purchased a Zietronix wideband controller at this time, to use with the DL software. I learned how to use these tools, and ended up with a very good tune for my Drummer equipped XB9. The bike ran great and I finally had a good solution for tuning it.
In 2004, after about 27K miles, I had a transmission failure on this bike that mucked up the engine cases. The search was on for a salvage bike with a good engine. I found and purchased a wreck, disassembled it completely, and got her up and running again with a fresh motor. During the winter of 2004 I purchased an XB factory race ECM and Tuner software as I felt it was a better solution for tuning over the limitations of using the Directlink software. This new DOS based software was amazing to me because with the factory software you could pretty much figure out every aspect of how this ECM works, and all the parameters that you could adjust - everything! I was in heaven! This is where I learned 90% of what I know about the DDFI Fuel injection system. I spent many months looking at all this information and experimenting with the tuning aspect of it. This was the pot of gold at the end of the rainbow.
Somewhere about this time, I had read about a group of guys in the UK and Europe that where researching and trying to find a way to tune their Buells. I had posted a couple of things up that I may be able to help, and did receive an email from one of the guys asking if I could provide some detailed information regarding what I knew about the factory race tuner. He was literally begging me for a copy of the Tuner software; Now I'm not going to say here if I provided it to him, but let it suffice to say that he was thankful for my help and I wished him success in his group's research. I don't know exactly how long after this it was, seems like maybe a year, but EcmSpy was released as a free tuning application and created quite a buzz. I downloaded this new software and took a look at it, and checked out the website. Found that there was a lot of good information on the site, and I did learn some additional things from it. But since, at this time I had the factory race ECM and tuner software (which gave me capabilities beyond what EcmSpy provides) I didn't have an need for it.
The winter of 2006 I decided I was going to build a tricked out big bore XB9 track bike with all the extra parts that I had accumulated. I used the factory race tuner on this project to handle the unique fueling requirements of this beast, and did so with success and further honed my knowledge and skills with DDFI tuning. In 2007, Buell announced the release if the 1125R, and after riding their demos and three inside pass trackdays, I had to have one.
So during the winter of 2007/2008, I parted out both my XBs and purchased the first one my local Dealer got in. Well we all know about the early fueling issues on the 2008 1125R, and my experience told me I had to find a way to correct it. It was so bad I couldn't stand riding it on the street. I was hoping that the EcmSpy software would be updated to be able to adjust the mapping on these new DDFI-3 Fuel injection systems. Then I read a post by one of the EcmSpy founders that they were not going to further develop the EcmSpy software to be compatible beyond the 2007 model year bikes. Reasons cited at that time where constantly changing EEPROM layouts by the factory, and some vague reference to legal issues and being forcefully asked not to develop the software further. It was also posted that the source code for the PC version of EcmSpy would not be made available, but if someone wanted to pick up the ball and start their own development, the Palm version source code was freely available (and still is available for download).
At this point in early-mid 2008, If I wanted to get the fueling corrected on my bike, I was pretty much on my own. And there were a lot of other owners looking for a solution as well. I experimented with using EcmSpy to fetch the EPROM data from the 1125, and found that it would in fact read in 13+ pages of EPROM data. I also found that once the data was fetched, I could get it to write changed value(s) to the EPROM, on a limited basis. Everything else in the program (fuel maps, etc.) was coming up gibberish, but this part seemed to work. But the EPROM data is hexadecimal, and I couldn't work with it like that.
I came up with an idea of taking the EcmSpy Hex dump, importing into an Excel spreadsheet, then creating a mirror of it in decimal values (through the use of Excel formulas) that made sense to me. Next, my focus was to determine where the fuel maps were located, and this was done by using my knowledge of where they were in the earlier XB EPROM’s, and finding like patterns in the data. Hours of staring at numbers in a spreadsheet it started coming out and I was able to define the fuel and spark maps, along with their axis. Then I went further to extrapolate the maps in a table format within Excel so I would have a somewhat crude interface in which I could see the TPS and RPM axis along with the cell seed values. I was on to something. Once I got this done, I installed my wideband, disabled the O2 sensor feedback and went data logging. After a few sessions of corrections on both front and rear cylinders, focusing on the cruise areas in the fuel maps, I had a very happy Helicon engine that ran like it should. I shared these maps (I code named this calibration "Nirvana") with several other local 1125 owners and the feedback was unanimous -- wow, finally this bike runs perfect!.
The rest is pretty much where I'm at now, I decided to further develop and refine the spreadsheet solution that I now offer as an application called BDDFI-III Tuner. After supporting the users and corresponding with people interested in the software, it became apparent to me that most didn't have the desire to learn how to become tuners; they really just wanted to be able to load a corrected calibration and enjoy. This feedback and need sparked the idea of building a software application that could load a calibration and switch back and forth at will between a stock calibration and a modified performance calibration. So I started developing from scratch a Visual Basic application called BDDFI-III Flash Utility. The main objective was to give users with little to no tuning and computer skills an easy means to correct the calibration on their bike for performance track use, and also comply with regulations for street use by being able to switch back to the box stock calibration.
Regarding the development of my Performance Calibrations, I will tell you that what I offer is completely developed by myself without any copying or use of anyone else's custom mapping or calibration "secrets" in whole or in part. Although one individual had provided to me (voluntarily, I didn't ask for it) his "core changes" , I never even looked at it because 1. I have no idea what his changes were, and 2. I was already in development using my own methods, which differ significantly from this individuals approach.
Computer Technology Background
I started programming in the Basic language in the early 90's. I've been the IT manager for a small manufacturing company that I have worked for 23 years. I have developed software beginning in the late 90's for my company that required serial interface coding to communicate with specialized machines that mark characters on metal nameplates. This serial interface programming is the basis of which I used in my Performance Flash Utility to communicate and write to the ECM. As you can see I had developed this years before EcmSpy was released.
I hope this gives everyone a clearer picture of how my software products evolved, my
background, and how I went about developing it. As you can see these software applications came about because of a personal need for a solution where a solution did not exist for me. I decided to spend even more time and effort to take it further and offer my solutions for others to use.
Please feel free to question or comment.