Ableton Live 8, control change, midi-mapping-strul

However, I ran across an issue related to the FCB1010. In your tutorial you write:
"STEP 6:
Press the UP Footswitch again. Now a number will appear in the display. That is the command number. I’ve read that you have to only choose from certain sets of numbers but any of them seem to work fine. Now my Axiom has it’s own preset numbers so if you’re using another controller make sure you’re not using any that will conflict, unless you want them to serve the same function. You can enter the command number with the Footswitchs themselves, or you can use the Expression Pedal A to scroll to it."

Now the sentence "I've read that you have to only choose from certain sets of numbers but any of them seem to work fine." is true in one sense, but I realized that it seems that some command numbers have default functions, like modulation which appears to be "CC#1" by default in most midi keyboards. I'm not sure, but I think this is what you're aiming at when you say that your Axiom has it 's own preset numbers and another controller may conflict. I ran into this conflict. I programmed my FCB1010 by reading your tutorial and it worked great. Except for one thing. I assigned "footswitch #1" on the FCB1010 and ("obviously/logically") assigned it to command number #1 (or "CC#1 if you will), not knowing that it was (probably) the default command number for modulation. Still with me? I'm confused at this point. So, without knowing this, happy and satisfied with my footswitch programming, I began setting up midi mappings for a project in Ableton. I assigned the footswitch #1 to launch three loops. It all worked fine. But then, when I used the modulation wheel (from my midi keyboard) while playing a VST, it launched the same three loops as the footswitch #1! So apperantly, Live "misunderstands" my modulation wheel and thinks that it should do the same as the footswitch #1, which is control change at this point. Still with me?

I launched a new project and there was no problem with the mod wheel. It worked as it should. Forgot to midi map the footswitch for that project though...and now I'm at home with my gear standing in our rehearsal room. Gotta try that tomorrow.

So how do I solve this? Can I program the FCB1010 so it sends out midi to a different channel, like perhaps channel 2? Maye then there won't be no conflict. Or do I have to assign that footswitch #1 to another command number? I just want my mod wheel to behave normally again and have nothing conflicting with eachother.

Great, great appreciation if you're willing (and have the knowledge) to respond to this.
All the best