Before anyone says this is in the wrong forum it's definitely a Sonar problem.
So I hit the pad for Snare open hit (note 40) on my MPD232 in standalone AD2 mode and one can hear the snare drum and see the midi trigger, but when loaded in Sonar the same pad fires the Kick drum. So I recorded a sequence & the drum map shows it as the snare open hit but it still triggers the kick drum.
I have checked the drum mapping and its perfect there are no controller surfaces loaded so what am I missing as I'm sure its obvious?
 
Sonar: Platinum
PC: Intel i7 6 cores (12 threads) CPU @ 3.40GHz, RAM 16GB, Windows 10 - 64 bit, Sound Blaster ZxR DBpro, Nvidia GTX780 with 2 widescreen Monitors
Akai Advance 49, Roland A-500Pro, Akai MPD230

Verify that the mapping in the loaded drum map is correct. After that, check that the "Key" value in the track inspector is "0". Beyond that, I'm not sure what it could be. Good luck!
 
Regards,
Dan
 

werewindle,
 
I've noticed that myself too.   I've  checked everything I could in AD2 but the snare still triggers the kick when using individual track from AD2 in Sonar Platinum.   For this one reason, I went back to FXpansion BFD Eco partially. 
 
I still love AD2, but I'd rather use it as an instrument track that split the tracks and hear the snare trigger the kick.

By default C2 in the Piano Roll will appear as C0 in the AD2 Map Window. For individual tracks, set the Key+ value to 24. There's also a global option in Preferences | Customization | Display:
 
Base Octave for Pitches. There is no industry standard for numbering octaves. By default, SONAR calls MIDI note 0 (the lowest possible note) C0. The Yamaha FB-01, for example, shows MIDI note 0 as C-2 (C negative 2). To match SONAR to that standard, set Base Octave to –2.
 

This just gets weirder.
I cretaed a new project from same template I had used before, same drum map and now the snare is responding to note 40 correctly. But still not working on the other project which appears identical. Re-checked the drum map mapping and its correct.
Looks like my next step is to create another instance of AD2 copy over midi and delete original and see if that corrects issue.
 

If you open "Map" window in AD2, you should be able to see which note AD2 receives and to which peace it maps it.
 
After the "Key" shift for the track, there are 2 "Drum maps":
* Sonar "Drum map". The first in the chain. It maps one MIDI note to another
* AD2 "Drum map". The last in the chain. It maps MIDI note to the sound.
 
Since everything is visible, I mean the note on the track, the key shift and both Drum maps, there is no problem to check where wrong mapping happens.

I created my own drum map based on the AD2 one and everything checks out which is why the new project works.
 
But as I said have used same drum map on main project but note 40 which the drum map indicates that it goes to note 40 except it doesn't it seems to triggers note 36 the Kick drum. Doesn't matter whether I hit the pad for 40 or its in the midi track as snare note 40. It's bizarre obvioulsy something is corrupted but 1st I'll restore the project onto my backup PC and see if I can see same issue not sure what that will prove but it would provide a workaround if it works.

If in the AD2 own map window you see that the key is "40" (it is highlighted when engaged), the label on it is "Snare" but the sound is Kick, it is worse to contact XLN since after Sonar routes MIDI into VST it has no influence what is happening then.

This is why I don't use drum maps in AD2.. To me it's much easier to just have the PRV show note names 0-127 (right-click the left section in PRV and select use these note names and set it to 0-127).
 
Then you can look at your notes in AD2 map and assign them by number.  If a snare is note 40, then set it in PRV to "40." For most kits I generally find the snare in AD2 to be on note 38, kick on 36, toms on 65, 67, 69, 71 respectively. Doesn't take long to learn the notes and just set them with the number. This has stopped my never ending frustration with drum maps in sonar.
 
gabo

werewindle
I created my own drum map based on the AD2 one and everything checks out which is why the new project works.

Either the drum map in the one project is corrupted (unheard of AFAIK), or the mapping in the particular instance of AD2 in that project has changed (easy to do since the 'Learn' function is wonky, and just clicking back and forth between keys on the virtual keyboard to audition them can re-map or clear mappings). Inserting a new instance of AD2 and reloading the drum map should fix it in any case. Platinum bundles a drum map for AD2, I suggest you use that one if problems persist with the one you created.
 
BTW, the 'main' note number for snare is 38. 40 is a second mapping to the same set of samples (labeled 'dbl') to allow performing snare rolls, flams, etc. from the keyboard. Same goes for Rimshot and Rimshot (dbl) on 37 and 39.