Thanks for the input Hellfire! Come to think of it, my buddy had his a/c on full blast, we're having a heat wave up here in Canada's capital
So maybe that was adding to the problem.
But I also had brought home the module to update it and sync it with my home trigger and memory settings.. and there was a time I'd set up some kits with the second kick channel for another pad.. and now I remember that at at least one point in the jam (I'd had a couple gin and tonics, mind you, in my defence!) I looked down at the module and saw that I'd moved up to kit 001 or kit 002 (and I'm using Addictive so I need to be on 000 mostly because I've made sure 000 has all the midi settings I need mapped properly, the other kits may not match up 1 to 1 where I want things). I may have put myself on a kit where I had Kick2 programmed as another kick or tom pad.
But even more possible was that when I put the module back on, and plugged everything in, I grabbed a TRS cable and used that on the kick by mistake.. I'm usually more careful but it's been 35 degrees and the first gin and tonic went down pretty fast after walking in his door.. should have had water and waited to hit the harder stuff after I re-configured the kit..hahahaha.. next time I go back first thing I'll check is that cable.