PI stage throws errors if trying to exceed physical limits

[mkrumin]

If the software limits in componentSettings.m exceed the physical limits of the PI stages and then trying to move beyond the physical limits (but within the software limits). The errors are thrown in the command window, although nothing crashes.
The behavior for the z-stage is different - it just prints the usual message of the 'limits exceeded'.

[raacampbell]

Would a suitable solution be:

1. Silently honour whichever limit (software or hardware) is the smallest?
2. If the software limit is larger than the hardware limit, print to the command line in some prominent way that this is the case when the motion class instantiates. The warning message would therefore appear once when BakingTray starts.

This is not ideal, because the user won't get feedback until the software is restarted. However it's the easiest thing to do. Another easy option would be to print the warning message to the CLI every time the limit is checked. This seems like it could be messy, though. What do you think?