The latest beta firmware for the MX2 is now available for download. This new release addresses some common requests for features, while resolving some issues with Telescope head control.
The Release Notes contain the most detailed information on the fixes, features, and changes, but here's a quick summary:
A lot of people have asked for the 1/100th degree capabilities in the Telescope control, and while we are hesitant to "officially" support this, we've decided that we should leave it up to the users as to whether or not they want to use this mode. The primary issue is accuracy, with most of the Merlin/Orion/Celestron heads 1/100th of a degree is approximately 2.6 ticks of the encoder. As we the telescope head cannot register a position between encoder ticks, this means any move expectation of 0.01 degrees will be off by a minimum of 30% guaranteed, and perhaps more when positioning errors are taking into account. However, this error decreases the larger the number gets, 0.05, 1.37, etc. all have much lower error rates. This forum post speaks about the limitations of accuracy in much greater detail.
By changing direction when a limit switch is triggered, you can now let your rig run for quite a while, and it will automatically cross back and forth down the track. This is especially useful when the scene may be changing throughout the day, and you want the maximum amount of source material while having to do the minimum amount of work.
As for "chasing the shutter," this is an important topic when using another piece of equipment to control the camera, notably the Little BRamper or similar devices. Previously, one would have to split the shutter signal coming out of the device so that the device was connected both to the camera and to the Ext1 port on the MX2. With the MX2 configured to "Ext. Interval" on the I/O 1 port, it would then advance one frame whenever the shutter was -triggered-. This implied that the MX2 would have to be configured to know how long the exposure time was to prevent movement during the shot. With the new "Invert I/O" feature, you can now change the signal that the MX2 looks for to be the "rising" instead of the "falling" signal. In the case of a device doing bulb exposure control, this means the MX2 will not trigger until the bulb control is released rather than when triggered. If you want to get even more exact, you can hook up the camera's PC port to the Ext1 on the MX2 and only trigger exactly when the shutter actually closes. This will make integrated workflow with other devices easier and much more reliable.