If your bike is running the same, there is something definitiely wrong.
Rhino, it's not running "the same." Though it is running much the same. Acceleration isn't quite as sharp as it was before. The ping is slightly less pronounced. Less hard. But still there in all the same ranges. The revision was a step in the right direction. But, unfortunately, only a very very small one. You still can't just ride the bike. If past trends are instructive it'll only be worse on hotter days. So, yes, the revision made a difference. A slight one. But the general problem still exists.
It is a mystery for me at this point if you are POSITIVE the programming etc went properly without a missed step.
Rhino
Absolutely positive. With adamentine certainty. Connections are good, etc etc etc. The problem isn't in the computer, it's in the bike

the last response from you was that you could not load the map.
No Rhino, a much earlier response was that the version of SmartLink I had was reporting a file format error and that I didn't immediately find a link to dl the latest version of Smartlink. The software was later downloaded and the newer format file was used without problem.
(me, I think you did not get it to take, but that is just MHO).
Zing, across the bow goes the shot. No, Rhino, the new file loaded to the module. Granted, this IT stuff is difficult for me. I only did systems design and deployment for a few years, troubleshoot some minor systems for Raytheon, Boeing or Thiokol occasionally and worked in PC environments for a decade or so. So this hooking bike to a PC stuff is some deep chit. But I got the cheese to lead the mouse to the PC and I plugged the mouse's tail right in to that Thundermax thingie. The little bastard bit me, but he was in there. File went right in right after I got the rabies shot.
Ok, kidding and "humble opinions" aside; yes the file loaded. EVERYTHING that is supposed to report reports. Connections are fine. Engine assembly was fine. Pushrods were adjusted correctly per Zippers supplied data sheet. In fact ALL appropriate directions from Zippers have been followed to the letter; even when they themselves have been revised. It's all good. It still pings.
However, if you are certain all of the above is good, then I admit I am lost.
I started to write "Hallelujah," rest my tired fingers and just move on. But I do appreciate all the time you took to offer all the points of consideration; no matter how obtuse they might have been. It's the little things that will bite a guy in the ass after all. So any ideas offered really are appreciated.
Rhino, as has been said before, no one doubts that yours is doing well. And that's great. It's just that for some reason others of us aren't having the same experience. Why that seemed to trouble you so is beyond me. You crossed the line a bit from suggesting ideas on the one hand to looking for and pre-supposing end user blame on the other.
You don't need to defend your own experience. Really. I'm happy yours is a seamless usage of the system. Sure as well wish mine was the same.
No matter how effective your usage has been, however, you have to admit that if someone is experiencing a problem they need to know that effective assistance is easily gained from the supplier. That is especially true when the supplier and the product are as proprietary as is this system and the system in question is primarily responsible for keeping you off the side of the road.
We've really only got one source for help. With the prospect of being on the road in the middle of no where ahead of you that source must be reliable.
That being so the BIG issue here has never been the hardware. I still think that if implemented correctly this system would be the nuts. I don't think it's a hardware problem at all; I'd bet 103Thunder's left nut that it's software. But the two become one when support for either comes from one place. In my case, and unfortunately in the case of others, that support has been at times either difficult to get, ineffective or both.
Rhino, support issues aren't a problem when the system works great. When it works great you don't need the after the fact support. It's far easier to praise someone when you don't have to test them.
To summarize though, I've still got ping. With having done all the right things I've still got ping. I'm not a novice with the technology nor with the mechanical side. I'm also smart enough to know what I'm not familiar with and ask for help. Which is why help was requested of Zippers for further more sophisiticated responses or revisions in the map. But I've still got ping...
Have already received a response from Fitzmaurice with timing alternatives to try myself on top of what his revision offered. Most are steps I'd gone through before with the old map. But I'll gladly try it one more time with the revised map just because giving them every opportunity to make it right is the right thing to do.
Fitzmaurice is now making an effort. That is a profound improvement on the company representative's performance previously. Whether the effort is successful or not is yet to be seen. The proof of the pudding will be in the eating. And I've still got ping.