Wow AC thanks for exploring this. ::012:: It is exactly what I have been waiting for!
I am a long way from an EFI expert but I did convert my DR-650 to EFI and did all the programing and tuning of the maps. I learned a lot and have had an absolute blast doing it. It runs great and I still have not blown up the motor! ;D At least so far. :
I will be ordering one of these kits as soon as I get home from my current C to C trip. (I am at present still 2,000 miles from home in Albuquerque)
As you alluded to in another post, a complete tuning set up would require a dyno or a data logging set up so you can see what you are doing. I believe data logging would would require extra software in the ECU, unless Yamaha has it hidden in the current code and someone figures out how to access it. And Dyno time is $$$$$$!
On the DR, I do have data logging ( built into the MicroSquirt ECU) which is wonderful but I also have a wide band O2 sensor and AFR gauge. I am thinking I could add the Wide band O2 sensor and AFR meter to the S10 and do at least some minor tuning based on observing the reading in real time as I ride. This is a much slower process than using a dyno or data logging set up but I am not in a hurry.
I look forward to developing and swapping maps. This is going to be fun! ::015::
Quote from: jbrown on Today at 09:35:30 pm
I'd like to have control over everything the ECU does!
For instance, assuming the ECU conditions data for the display, I'd like to fix the speedometer without messing up the input used for other purposes.
Having access to the machine code makes lots of stuff possible, if you're willing to spend enough time on it.
JB, Another EE here and I get your desire for access to the code but if I understand this correctly, we will not have access to the actual executable code itself.
All EFI code I know of makes extensive use of table look ups, or maps as they are known in the EFI world. What we will be able to access and modify is those maps. But as AC states, you will need to clearly understand how the maps work and interact. If you really want to have full control you could replace the ECU with a MicroSquirt processor. With that ECU you can download the complete source code and the compiler for free and hack away. But that would be a heck of a lot of work for little improvement I expect. I think the maps will give me plenty to play with for a LONG time! ::013::
I am a long way from an EFI expert but I did convert my DR-650 to EFI and did all the programing and tuning of the maps. I learned a lot and have had an absolute blast doing it. It runs great and I still have not blown up the motor! ;D At least so far. :
I will be ordering one of these kits as soon as I get home from my current C to C trip. (I am at present still 2,000 miles from home in Albuquerque)
As you alluded to in another post, a complete tuning set up would require a dyno or a data logging set up so you can see what you are doing. I believe data logging would would require extra software in the ECU, unless Yamaha has it hidden in the current code and someone figures out how to access it. And Dyno time is $$$$$$!
On the DR, I do have data logging ( built into the MicroSquirt ECU) which is wonderful but I also have a wide band O2 sensor and AFR gauge. I am thinking I could add the Wide band O2 sensor and AFR meter to the S10 and do at least some minor tuning based on observing the reading in real time as I ride. This is a much slower process than using a dyno or data logging set up but I am not in a hurry.
I look forward to developing and swapping maps. This is going to be fun! ::015::
Quote from: jbrown on Today at 09:35:30 pm
I'd like to have control over everything the ECU does!
For instance, assuming the ECU conditions data for the display, I'd like to fix the speedometer without messing up the input used for other purposes.
Having access to the machine code makes lots of stuff possible, if you're willing to spend enough time on it.
JB, Another EE here and I get your desire for access to the code but if I understand this correctly, we will not have access to the actual executable code itself.
All EFI code I know of makes extensive use of table look ups, or maps as they are known in the EFI world. What we will be able to access and modify is those maps. But as AC states, you will need to clearly understand how the maps work and interact. If you really want to have full control you could replace the ECU with a MicroSquirt processor. With that ECU you can download the complete source code and the compiler for free and hack away. But that would be a heck of a lot of work for little improvement I expect. I think the maps will give me plenty to play with for a LONG time! ::013::