I spent a little time trying to get it working properly, but I didn't succeed too well.
 
I got the AlphaTrack Preset going and I started tweaking the eq, but I kept getting messages about device disconnected etc.
 
I probably spent around 45 minutes trying to get it going. I then tried to flip back to the old AlphaTrack settings and that didn't go so well for me either. I'll try again another day (maybe). :-)
 
I should add that I was grateful for the chance to play with it. I wonder if my issues might have been related to me using USB 2 port rather than 3. Traditionally, I have to use USB 2 with the AlphaTrack and that is what I was using. 
 
Edit: I came back and reinstalled the alphatrack 1.3.0 driver and got everything working properly again.
Using the USB 3.0 port definitely doesn't work for me. I have to hard boot my pc after plugging it in that way.
 
So using the USB 2.0 port and the driver that comes with it, it works ok for me (altering fader volumes, selecting and arming tracks and hitting record/rtz etc.
 
Using the AzCtrl0_3r8b215M, I can slide the fader and move the fader in Sonar, but a moment later, the motorized fader is moving (untouched) and the level of the track fader in Sonar is not being moved.

I can get the old Alphatrack plugin working (not with plugins of course) but not Alexsy's. It doesn't even recognise my alphatrack.
That's to say that the Alphatrack doesn't respond in any way to Alexsy's plugin.

Mudgel,
 
You add the AZ Controller and map as usual.
 
Then > Utilities > AZ Controller > Options
Tweak Current Configuration > Choose AlphaTrack.
 
This is the ticket and it does work with the EQ, but the beta version I tried was still a touch buggy. I posted the version number I tried above.
 
It seemed to come disconnected at times. At times the motor moved the AT Fader to a different place than the fader on the selected track.
 
The controls adjusted the values on the EQ slower than the old AT did. Don't forget to push in the fader and rotate for faster pot adjustments of the EQ.

I am using version 0.3r9b217.
 
The Alphatrack is now responding. Any movement in the screen elements of a plugin are so slow/fine that it is much quicker to use a mouse. is this rate of movement adjustable somehow?
 
Is it able to work with the ProChannel?

Never mind. I've worked out how to make the encoders move faster and how to get the EQ in the ProChannel working. Thanks.

gswitz
The controls adjusted the values on the EQ slower than the old AT did. Don't forget to push in the fader and rotate for faster pot adjustments of the EQ.

At the moment, "fast" mode is MIDI, so 1/127 of the range per tick and "fine" mode is 1/1000 of the range per tick. I will think about adding more options.
 
I do not think "Disconnects" can be related to my plug-in, it has no influence on Sonar MIDI settings and for sure not on Windows drivers.
 
But if the Fader is moving to incorrect position, that can be my bug. Please try to find some "pattern" when that happened.
 
The preset was so far tested by Subtlearts only (I do not have the device). So there can be some not yet spotted bugs. Up to you to help eliminate them!

I can confirm that the plugin works very well on my device, I've put it through the paces and it's very stable here. There are some subtle differences (in most cases, improvements) from the original plugin which you have to kind of get used to - if I find myself with a bit of extra time I might try to whip up a quick document based on the original user guide that indicates where it's different. But mostly it follows the original pretty closely.
 
The display is not exactly the same (yet) but does give 'live' information about parameters and adjustments for everything important.
 
The Function keys are not mapped by default and in order to map them you need to get a bit deeper into the plugin's logic - basically, you go to the Logic tab, press the button you want to map, and add a logic entry with something from the Command menu (well you can get them to do most anything if you want to get into it, but in terms of straight mapping to a Sonar function, that's where you'll find most of them - a lot of the important ones are in the Menu sub-menu. Yes, it's a menu called Menu.

I've only really spent 30 minutes with it and that included the original troubleshooting to get the plugin working. Now that I have a bit of a better working knowledge of it I'm sure I can figure it out.

It's been ages since I've used the Alphatrack for anything other than transport control.

subtlearts
The Function keys are not mapped by default

They are mapped to what I could see in the original documentation as "default":
Save (with shift) and Recall (without shift) currently controlled strip. With bus/track automatic switch.
I thing that functionality is really useful for one strip controller, when you want switch back and force between 2 not adjacent strips.

Since I got my AT back on track I'm using this AZ preset. It works ok here. Didn't try the EQ that much, but tweaking Sends, Pan and Volume .
Actually I can't see many differences in performance between this preset and the original. I'm just using it now as I always did with the AT standard, my usual workflow (ie: ignoring the EQ) and it works fine.
Once I start using the EQ it'll be a great upgrade from the Frontier original.
Only difference so far: the display information.
This morning for example, I was tweaking a SEND that I needed at -9.6dB to match other tracks' sends, and I realized this AZ won't show decimals, so I went from 8dB to 9dN and then 10d, I couldn't make 9.6 without looking at the screen, that's a drag.
But didn't find any of Mike's original issues. I guess that with a little setup (as easy as with the original)  it works very well.