ASCOM SQM Serial Driver

Version History:
1.0 Initial version, COM Port support (SQM-LU/LR) only
1.1 Support for non-english speaking locales
2.0 Tentative support for SQM-LE; 
      Reimplement setup dialog; 
      Pluggable architecture for device model implementations
2.1 Removed nonstandard Farenheit support
      Fixed trace error

This driver works with Unihedron SQM devices that present themselves to Windows
as a serial port. As of version 2.0, there is support for the SQM-LE (ethernet).

When queried, the driver provides two pieces of information;

- the current sky quality in Mpsas
- the current temperature as measured by the SQM device


I have tested this driver with the SQM-LU, and it should work with the
SQM-LU-DL. I also expect it to work with the SQM-LR. Support for SQM-LE has had
limited testing.

This is a 32-bit driver. It will work with most astronomy software because most
astronomy automation software is written to be 32-bit. If needed in the future,
64-bit software support can be added.

When installed, this driver will appear as a provider of "Observing Conditions"
data. In the ASCOM selector for your software, this driver may be listed with
the name "Serial SQM ObservingCondition"

The configuration dialog for this driver allows you to select the SQM model, and
the connection details for the selected model. 

For the SQM-LU and SQM-LR models, you can select the COM port on which the SQM
device is connected. 

For the SQM-LE, the device's IP address and port must be entered. These are
configured on the device itself, please see the device's documentation for
details. 

The "Simulate" device setting allows the user to simulate the existance of a SQM
device. he driver will return simulated temperature and sky quality values
without a SQM device being present.

Please ensure the following prerequisites are already installed:

- ASCOM version 6.2 or later
- Unihedron SQM Windows drivers (not needed for the SQM-LE model)
- .NET Framework 4.0 or later


Please make sure to uninstall older versions of this driver before upgrading to
a newer version.

If I get the chance, I may rewrite this driver in a cleaner form, using what I
learned in this attempt.


Thanks!
Martin Mangan.
http://www.dizzy.eu/