When the TCS box isn’t turned ON (a form of operator error) the NG GUI just hangs. It would help if NG put up an error box to alerted the observer about the problem and possibly offered the observer the option of using the GUI without the NG engine. Exactly why I’m not sure, possibly to look at the catalogs or operate other devices with embedded control that don’t need NG (future devices with their own IP address) .

The STOP button works well but when the ENABLE button is pushed the scope begins moving suddenly. This is a bit scary since there was probably a good reason to push the STOP button in the first place. I pushed STOP when the tube cover was getting a little too close to the upper platform and I wanted to check clearancebefore proceeding. Possibly a box could alert the observer that the scope will start moving fast again or give the operator the option of moving moreslowly when ENABLE was pushed.

Display the Alt-AZ of catalog objects so that the operator knows where the scope is going to go next before selecting an object.In many cases the move from one object to another may require a lengthy move of the dome and it would be nice to know before asking the scope to move. Sometimes a catalog object might be low in the sky and the observer might want to avoid it in favor of a different object.

Personally I would move Alt-AZ and Stow from the Utility scree to the main screen. These are things an observer might want to do during normal observing. That would keep the observer on one screen as much as possible and have the Utility screen for setup or other diagnostic tasks. This might make the main screen bigger, but there’s plenty of room on the monitor.

When moving to an object that is below the horizon the telescope doesn't move and doesn't explain why.