There's no need to accept the trims. When I first bought the AT kit I used a close map from Jamie and rode the bike for an entire day, trying to hit every RPM/TP point on the map more than once. The Target AFR's used were Jamie's rich values, not those that I would ultimately use (more on that later). At the end of that day I accepted the trims and that was my new base map based on the rich values. I then re-set the target AFR's to leaner values for better mileage, and the O2 sensors then create the trims on the fly based on those new targets. For all of the cruise range I have negative numbers in the trim tables, some in double-digits, and that's the way it should be. By doing it this way I can use an on-off switch to toggle between the richer base map for better cooling when needed and AT mode most of the time (using the trims) for better mileage.
There is absolutely no practical reason to continually accept trims, IMO, unless you want to create a base map to install on another bike with like equipment. Or, if you want to create a base map like I did for use with a switch.
They can be a PIA, but follow this procedure and you shouldn't have any trouble.
1. Warm the bike up and spray some WD-40 or other penetrant on the base of the sensor, then let it sit for 10 min. or so.
2. Using a socket like this, slowly loosen the sensor, repositioning the wires in the socket about every turn or so. If it becomes hard to turn, spray more WD-40 on the base and turn it in a turn or so, then out. Don't force it or you may damage the threads on the sensor.
3. Put some anti-sieze compound on the threads of the new sensor and torque into place.
That's the way the basic PCV (no AT) works, too. It goes like this: On a stock system the ECM sends out signals to the EFI. A basic PCV intercepts those signals and alters them according to the values in your base map. End of story with the basic PCV. Now with AT you have more going on, the O2-sensors and two additional tables, Target AFR and Trim. Let's assume we have inserted a value of 14.0 in the Target AFR table for 2000 RPM @ 10% TP (throttle position). The O2-sensor reads the AFR coming from the exhaust, and if it sees 13.5 (for example) it will subtract unti it meets the 14.0 value dictated in the Target AFR table. It subtracts by inserting negative values in the Trim Table. So, if you have a 10 in your base map for 2000 @ 10% and the O2-sensors have inserted a -5 in the Trim Table the bike will run as if the base map had a 5 in that cell (10-5). What it's doing is leaning it out to meet the 14.0 AFR value that you have provided in the Target AFR table.
So, if you accept trims it will take that -5 and apply it to the existing 10 in the old base map and create a new value of 5 in the base map for 2000 @ 10%. Note that it will do this for the entire tables (both front and rear cylinder), not just one cell. If you do this it will run exactly the same as if you did nothing at all, and accepting trims is only necessary when you are trying to create an accurate base map to start from for your bike, but you don't even need to do that. If you want to create a rich map like I did, then be able to switch between open- and closed-loop, the above procedure is the proper one to use. I hope this is clear, as it is a simple process but very hard to describe.
Correct, but you don't really need to do this unless you are connecting a switch like I have done. You could theoretically put in a zeroed map, or even one for a totally different bike, and let it auto-tune. It then creates the appropriate trims based on your target AFR's, and it will run as well if you accept trims or not. One caveat is that the further the base is from reality (your desired AFR's) the longer it will take to trim properly. So if AT needs to trim +20 it will take longer to do that than if the values were closer to reality.
All this said, if I was not using the switch I would probably run the bike for a week or two, then accept trims once. That's really all you need to do, as it works the same either way.