Ok... I had the chance to do nine quality runs today with RaceChip installed and my new Dragy, and I'm a little disappointed. The weather was cloudy, windy, dry pavement but humid air, cool for central TX ~65*F. Tire pressures were 35-37psi all around. The run had a slight decline ~-0.35-0.69 degrees depending on which calculation you believe. The run was basically the same every time. I did some runs with launch control off, some with it on, some with RaceChip off, some with it on Race setting, either level 5 or 7...
60 ft: 2.43-2.50s
330 ft: 6.14-6.27s
1/8 mi: 9.12-9.29s @81.68-83.36 mph
1.000ft: 11.66-11.88s @94.58-96.61 mph
1/4 mi: 13.79-14.06s @103.58-105.57 mph
The first run of the day was the best run. It's the one that yielded a 13.78s @ 105.57mph. I rolled straight from the highway to my secret test strip. RaceChip was already on and set to Race level 5. It went downhill from there. I was unable to duplicate or exceed the result and I also wasn't able to tell much difference between having RaceChip on or off. My next 2 runs were with RaceChip off to get a baseline. I ran a 13.82 at 104.97 and 13.89 at 104.29. You could maybe argue it was worth a tenth of a second in ET and maybe 1.3 mph in trap speed; certainly not what I was expecting from a chip that claimed to add 41 HP and 61 Torque. I boosted the Race setting from 5 to 7, and my times got slightly worse: 3 runs yielded ETs from 13.86-13.96 at 103.58-104.87 mph. After thinking about it, maybe it was from excessive wheel spin at lower speeds, but the 60 ft numbers were so close - hundredths of a second from best to worst, it almost didn't matter. It has me wondering if it's connected correctly or if it was even on. My 7th and 8th runs were with the RaceChip set to 7 and launch control off. I got lots of wheel spin and my worst 60 ft times (2.48s and 2.50s) but surprisingly still within hundredths of a second of my best with launch control on (2.42s). My last run was RC on 7, launch control 13.89 at 105.48.
RaceChip doesn't like to connect while my phone is connected to my K5. It hangs in the "connecting" phase indefinitely more often than not. I found that I can best connect when I have the car turned off, and turn the K5 and my phone's Bluetooth on at the same time, before my phone connects to the K5. My phone, a Samsung Galaxy S22 Ultra runs Bluetooth 5 and should be able to connect to multiple devices. It connects to the K5 and Dragy reliably every time with ease. It's only the RaceChip that gives me trouble. If you don't even have the car on, the screen around the buttons goes black. When it's connected, the screen is orange.
The K5 launch control sucks too. Sometimes, it wouldn't let me get into LC, saying, "Launch Control Conditions Not Met". Sometimes it would. The results weren't too different either way. There was still some wheel spin with launch control on and I found I could almost modulate the throttle as well as launch control.
Either way, my ETs and trap speeds seemed to get worse the more I ran. Maybe it's from increasing humidity, or maybe my engine compartment was getting hot or maybe it's because of the excessive wheel spin. I don't know, but I do know RaceChip didn't give me the WOW factor I was looking for today.
Conclusion: I'm currently undecided if RaceChip even works at all but the K5 may benefit from better /stickier tires up front.
Way forward: I will reach out to RaceChip to see what they say about the connection issue and the performance stats. I may try a few more runs with less pressure in the front tires, and maybe higher pressure in the back. RaceChip has a 30 day money-back guarantee and if I don't see some differences, I may test that guarantee.