Quote Originally Posted by Ger21 View Post
Sorry guys, I missed this.

Here's the deal.
If you install the 2017 screenset with an AXBB-E, it won't work. The reason is that each controller actually has it's own screen, and the AXBB-E did not exist when I created the screenset.
I have a screen file that works with the AXBB-E, that uses a copy of the UC300ETH-UB1 screen, but the diagnostic page is not correct.
But there are some other issues involved here.
The AXBB-E requires the latest test release of UCCNC, which contains a lot of features that are not supported by the 2017 screenset. It **should** work OK, but you won't be able to use any of the new features.

I'm working on a new screenset that will support the AXBB-E, and the next full release of UCCNC. But I can't finish it until the actual version is released, as new features keep getting added with each test release.
One other thing to note, is that the next release of UCCNC contains a very thorought probing plugin, which is integrated into the screens. This will NOT be included with my next screenset, due to the way the plugin and screens were done.
But my screen will have it's own probing routines, which I plan on expanding, to be better and more powerful.


And I do have an AXBB-E, which I'll be using for testing the new probe routines.
Thanks for t he heads up Ger.
cheers
Andrew