A few questions
Posted: Mon Apr 02, 2018 9:50 pm
Now that I've had my neglected mx5 running and checked everything over I've ordered a Frankenso kit. After spending the last few days (and then some) reading up on rusEFI, I have a few questions;
1. My mx5 is already running on megasquirt, the fuel map is fairly close, can I copy this straight into the rusEFI?
2. Knock sensor, I understand this is alpha version and I believe none of the components are included in the kit, but I would like to use it if at all possible. First off, I don't understand any of the settings for it in tuner studio, second, what sensors are compatible, and third, there's no spec for X161 on the hardware manual. Is there anywhere I can get more info on this or is it best left alone for now?
3. I plan on using a MPXH6300 or MPXH6400 MAP sensor, I saw there was a PCB being made for these sensors, is it available to order anywhere?
4. This may need it's own thread. I've seen that it's possible to read the MAF/RPM fuel map from a stock ECU, would it be possible/how hard would it be to use the rusEFI as a "piggy back" to the stock ECU to learn any map you needed? Sort of like how auto tune in tuner studio collects data to alter the current map, could you use the stock ECU with rusEFI collecting data while you drive around or rolling road if available, for however long it takes to gather sufficient data. It would likely require some specific driving styles to collect all relevant data and I imagine some things you will still have to figure out, but if you can read the timing and duration of ignition or injector pulse width and feed it into a MAP/RPM map, you could also figure out warmup enrichment etc. by capturing a cold start or two. One or two people per engine could possibly build a database of base maps, if you were going to be the first doing that engine anyway, it may even make your own job easier, would it be much extra work to make this possible, or is that a completely different project?
If you could get past the hurdle of getting an engine running by making it as "simple" as, for this engine use this firmware, with this map, and assemble your board like this, then you could get to tuning a lot faster, I'm not saying this would make rusEFI a plug 'n play replacement for your stock ECU, but it would be a lot closer, and the data collected in theory wouldn't need updating, maps from the stock ECU would always be a great starting point.
1. My mx5 is already running on megasquirt, the fuel map is fairly close, can I copy this straight into the rusEFI?
2. Knock sensor, I understand this is alpha version and I believe none of the components are included in the kit, but I would like to use it if at all possible. First off, I don't understand any of the settings for it in tuner studio, second, what sensors are compatible, and third, there's no spec for X161 on the hardware manual. Is there anywhere I can get more info on this or is it best left alone for now?
3. I plan on using a MPXH6300 or MPXH6400 MAP sensor, I saw there was a PCB being made for these sensors, is it available to order anywhere?
4. This may need it's own thread. I've seen that it's possible to read the MAF/RPM fuel map from a stock ECU, would it be possible/how hard would it be to use the rusEFI as a "piggy back" to the stock ECU to learn any map you needed? Sort of like how auto tune in tuner studio collects data to alter the current map, could you use the stock ECU with rusEFI collecting data while you drive around or rolling road if available, for however long it takes to gather sufficient data. It would likely require some specific driving styles to collect all relevant data and I imagine some things you will still have to figure out, but if you can read the timing and duration of ignition or injector pulse width and feed it into a MAP/RPM map, you could also figure out warmup enrichment etc. by capturing a cold start or two. One or two people per engine could possibly build a database of base maps, if you were going to be the first doing that engine anyway, it may even make your own job easier, would it be much extra work to make this possible, or is that a completely different project?
If you could get past the hurdle of getting an engine running by making it as "simple" as, for this engine use this firmware, with this map, and assemble your board like this, then you could get to tuning a lot faster, I'm not saying this would make rusEFI a plug 'n play replacement for your stock ECU, but it would be a lot closer, and the data collected in theory wouldn't need updating, maps from the stock ECU would always be a great starting point.
See also