so is the the bazzaz a true closed loop setup?
I believe so, but it is not automatic. You ride around data logging to a pre-set A/F you wish your map to be set at, and then after logging for a bit, hook up the PC and retrieve the info, and decide to apply some or all of the recommendations the data logger recorded.
The logger 'averages' the A/F ratio for each cell. You can just do a single run (pull) by keeping the RPM below 3K, until you are in 4th, and have the space/place to WOT it, and then return home below 3K and use that to apply... or just ride around and it will average out for anything above 3K. So in that way it is flexible.
Would be nice to have different types of 'run's pre-set to choose from for the data logging application/software.
Here are some observations I have had so far. (some repeat info). I am not bashing Bazzaz. When ever I get a new gadget, I usually 'test' the limits out of it as I can so I can understand what it is and is not capable of/how it works.
*****
1. the AFR unit and their dyno does not function well for gears 1-3, as the RPM run up is too quick for the unit to log the A/F well/accurately for the cells, so they recommend 4th and up. I then assume that applies equally for street riding/tuning as well.
2. the AFR unit ‘averages’ the A/F ratios that it finally sends over to your Zfi software, so the longer you ride around, the more data that is incorporated into the averaged results that are retrieved when you download the AFR data to your PC, to decide whether to apply some or all, or none of the AFR data to your map. Averaging on the AFR unit is different than their dyno as that logs per run, and does a type of ‘tuning link’ type of run/tune, similar to DynoJet dynos and PowerCommander units.
3. Per Bazzaz, the AFR does not do any data logging for RPM’s below 3K. That does not appear to be any issue/big deal.
4. For me either just riding around gathering data, or keeping the RPM’s below 3K, until 4th gear and blasting the throttle WO, then a casual ride back home to gather the data (which then would have been just one 4th gear run - similar to a single dyno pull), and not averaged since it only came from 1 run in 4th, appears to be the easiest. If you want the ‘averaging’ then just riding around, is even easier. Which one is better for a good performing map/bike? I have no idea.
5. Because the RPM-throttle position in normal runs form sort of a graph in my mind, increasing in both directions, from left to right, there will be cells that are not really ‘covered’ or data logged by the typical use/run of the AFR unit with ‘normal’ riding around/runs, since those cells will be outside of the run (graph) range.
6. Bazzaz appears to use a standard wiring harness for all of it's Fi units, with two connectors for each Fi, an input from the OEM harness to the ZFi unit, and then the output from the ZFi back to the Fi, as well as for most of the other connectors. While that my easily install on most bikes with removable air boxes, where the total ZFi install could take maybe 45 minutes, as Bazzaz states, on the 14, because the airbox is part of the frame, the install onthe 14 it is more like 3, maybe 4 hours relaxed install, requiring some particular tools to get to the connectors in that very tight space. That is a real pain.
My observation is that the Bazzaz unit, for the Fi connectors, TB connector and ‘speed sensor’ (crank), are a total of 12 connectors, all in the center of the bike under/in the tight space of the airbox ceiling-real wall/TB assembly and the far right side of the bike. The 14 has a single connector, on the left outside that is very easy to get to, and if Bazzaz used it, like the PC III folks do, would replace 12 connectors from the ZFi to a simple plug in on the left side of the bike. There would still be several other connectors on the left side as well, but those take about 5 minutes to do. That would then take the install of this kit down to 45 minutes, and it would be a very easy install, as well.
Additionally, if the need arises to remove/disconnect the Fi connectors, et. al. from the bike, you again are looking at the 3-4 hours to get everything back to OEM, should you have the unit or wiring go out while on the road, and you’d need your ‘special’ tools with you. That is a consideration to have in mind if one is contemplating purchasing this unit. My first ZFi unit was bad, but because the wiring harness is disconnectable from the ZFi unit, that helped. Had the wiring harness had an issue, or I needed to return to OEM, the entire thing would have to come out. Before I installed their wiring harness I checked the connectors, as they suggest. There were several that would not stay seated into the connector, so I used a touch of silicone for those wire leads/connectors.
Justification for not putting on a OEM type connector for the 14 was that they had to be purchased in lots of 10,000, which did not justify purchasing since Bazzaz does not have that type of volume in sale for the 14. That is understandable.
However, the fact is the OEM plug can be purchased in lots of 500, and perhaps less. That information was provided to Bazzaz. To me it appeared ‘inconvenient’ for them. The total cost of the plug comes to $5.27, wholesale, when purchased in lots of 500. So for pennies saved, or perhaps a few pennies extra, Bazzaz could service it’s 14 customers much better by using the OEM plug rather than their current setup. After some discussion with Bazzaz, they continue to appear disinterested to consider, despite the great increase in ease for 14 customers, perhaps a little savings for them (?).
7. The resolution for TP has more 'sensitivity/settings for TP percentages, while the RPM has increments of 500 RPM. I do not know how that would realistically compare in real bike use with the PCIII which has TP with less increments, but better RPM (250) increments/resolution.
8. The Bazzaz software could have included many, many options, as the AFR unit grabs the data, so formatting how to use the data, eg acquire only 4th gear only data, or only the first run in 4th gear, etc.. etc could make the software and resulting use very powerful for the purchaser.
There is a bug in the software that makes any cell empty when the A/F is at the setting desired in the software, e.g. if the user selects 13.2 as the desired A/F ratio to data log, when retrieving after runs, any cell that has an A/F ratio of 13.2 then is empty, or = 0 percent. No big deal. However, yesterday I was told something different, and that is when the cell is empty the Bazzaz unit reads from the stock map in the bikes ECU. Those two explainations seem pretty different.
I would think that if you have an empty cell or empty cells, and the stock map has pretty different settings for those cells, that could result in some inconsistent, less than smooth operation of the bike during acceleration. In the times I have seen an empty cell ot two, the cells around them are pretty close usually, meaning they are a few percent up or down from 0. So the better method may be to input something into an empty cell, based upon what is diagnal to it (lower left to upper right).
There is no current work by Bazzaz to resolve the bug, as I understand, or apparently not any work in the software at this time, though they may correct the bug the next time they schedule work on their next software ‘version’. They appear to have no idea when that will be.
In running the custom map made for me, dialed into a specific A/F ratio and using their sensor placed inside right near the O2 sensor I installed from their AFR kit, there were some differences in how the AFR unit would have made changes to their map after the dyno map was made.
The dyno tune/map ‘felt’ better than the AFR tune for the same A/F.
Which one is more accurate? I am guessing the dyno O2 sensor.
Their dyno has the caveats that their O2 sensor is not ‘quick’ enough to log runs in 1-3rd gears, either.
Whenever I have contacted Bazzaz the guys there, Amar, Joel or Del, they have always been very helpful.