Multiple ACT Controllers; is this even supposed to work?

I have an Oxygen 25 and a Trigger Finger.

I have managed to get the sliders and knobs MIDI learned in both, but I noticed an oddity when I was doing the ACT controller mapping.

I mapped in appropriate values for ProChannel EQ on the Oxygen  knobs.  Then I tried to do the same for the TriggerFinger.  Because the TF has 12 CCs and the Oxygen has 8, I was trying to map them to different places.  This didn't seem to work; there seemed to be only one mapping.

Am I correct that all ACT mapped controllers always control the same parameter?  For instance, is the first rotary knob in the first bank always controlling the same thing, regardless of preset?  

I do see references to surfacecontrolid's in the ACT parameters XML files, which tends to support this hypothesis.  And, it may make sense, but I would really like a confirmation.

If anyone else has been in this boat, how have you handled it?  I suppose that I could create a preset for the Oxygen that mapped it into Bank 2.  Is that the best way to approach this (or did I miss my exit a few miles back)?

That's almost the question.  I understand that there is one  thing that is the target.

My question is best illustrated with an example.  If I configure rotary 1 in bank 1 on both my TF and Oxygen, these knobs will always control the same parameter on whatever the target is.  There is no way to have something assigned to same ACT 'slot' and have what is controlled vary by the hardware surface.

I'm not at my DAW at the moment but I have 2 different controllers working with ACT, a PCR 800 and an A & H ZED-R16 and they are both set up in different configs.

I could be wrong but I'm fairly sure this isn't an issue for me in that button one on the ZED controls a different control to Button One on my PCR. But that to me sounds more like a MIDI learn function than an ACT learn problem.

Remember that there is a difference between 'ACT learn' and 'MIDI learn' when setting up controllers. MIDI learn is linking the control to the ACT 'slot'. ACT learn is linking the 'slot' to the plugin parameter.

Yes there is and that could well be the difference. Good thinking, not that that helps you much.