Thanks for that. I wasn't really clear I was hoping the software would enable a ZX-10 sensor to be used.
It has been swapped out because the OEM sensor on the H2 is unidirectional meaning it only works in one direction. Others out there have opted out for replacing it with an OEM, sensor off of the stock 16 ZX-10R which is bidirectional meaning it works in both directions. Which is fine, except that specific sensor isn't that
great. Running the stock sensor on my 16 10R since February, I have had several instances where the OEM sensor cannot keep up with the downshifts and has had issues detecting some higher speed upshifts. Now for me, starting my approach and entrance to T1 at anywhere from 165-175 MPH, depending on my exit at T13, requires me to get back into either 1st or 2nd to properly hit my line and marks to make the best time and fastest speed through T1. I've had a bunch of instances where the sensor can't keep up and I end up in a gear higher than I should be causing me to be weak in that specific turn and lose time and have to find it back elsewhere on the track. It got to the point to where I just went old school and used my wrist's auto blip :P
It was not just me either... we have quite a few sponsored racers that had the same issues which lead us to replace the sensor with the upgraded unit. They all experienced the same thing and it was all rectified with the better quality sensor. Ever since switching out to the new replacement sensor late July, I haven't had any of those issues either with the QS not being able to keep up on extremely fast downshifts or on the intermittent non-detection at higher speeds in higher gears.
Reason we don't allow sensors from other manufacturers is say you purchase a sensor from Dynojet, enable it and it doesn't respond well. We could then spend the entire time troubleshooting the issue only to find out at the very end it was a problem with the sensor itself. So by keeping everything under the same set of controlled constraints, we are better able to diagnose and troubleshoot potential issues since everyone is using the same exact hardware and software which allows us to get to the root cause faster. Similar issue here, if we let people use the Kawi sensor and they start to experience issues, who would get the blame for the issues we've noticed with the OEM sensor? Definitely wouldn't be Kawi getting their doors busted in with people complaining. Luckily, these replacement sensors are about as tough and reliable as they come and have had nary an issue with them across all of the models we use them on. Would the stock 16 ZX-10R sensor work with our software? Yes. But would it work well? Not nearly as well as the upgraded replacement sensor.