Thank you for your feedback.
We are working with third party software to insure full compatibility between FL (and future developments such as full frame guiding/focusing) with other applications as much as possible.
FL was developed with the idea of being a cross platform solution such as many as possible people can use it across many different applications. For this goal FL supports ASCOM compliant devices.
I am certainly open to discuss the integration (native stand alone) of our technologies in some popular software, however having an independent application (supporting ASCOM) provides more flexibility to deliver improvements and consistent user interface and efficient maintenance across platforms.
On this matter FL + ONAG is similar to a camera,a rotator, or a focuser, it interfaces with third party software in a native mode through an interface such as a COM server.
FL acts as a driver would do, abstract the hardware and functionality from the application layer.
SL technology is a new concept and it takes some time to update current software to support/provide the proper communication protocol to full support it.
FL works with most auto-guiding software and any ASCOM compliant focuser.
Focuser corrections from FL are issued only if there are incoming new guide star frames, which happens when there is active auto-guiding.
When a third party software, such as SGP, is slewing the mount for instance auto-guiding should be put in hold and as a consequence FL automatically too.
On that matter FL is fully synchronized with the auto-guiding software.
The guide star reference roundness used by FL for auto-focus can be related to a given filter, if filters are not parfocal. This functionality requires that FL can access to the current filter selection from the imaging program or the FW driver.
In order to be as universal as possible FL is able to communicate with an ASCOM compliant FW.
The FW ASCOM driver would first connect with the OPTEC ASCOM sever which will share the ASCOM driver compliant device (such a filter FW) between several applications, for instance FL and an imaging software.
If the FW ASCOM driver provides filter information (as it should) this will be available to FL and any other third party software (such as SGP) connected to the OPTEC ASCOM sever.
I am strong support, when feasible, of using a standardized approach to communicate between all devices and software for astronomical applications, in my opinion this is the best way for many products and companies to provide a robust and unified way to interconnect.
It is useful since there is not one company providing all the parts anyway. This is the goal and the idea behind the ASCOM initiative and I think we should promote and support such an approach whenever possible. Some new ASCOM functionalities may need to be added with new technologies.
However not all software/hardware support ASCOM, but more and more do, for instance SBIG are working for providing ASCOM drivers for most of the camera eventually.
Since there are still many equipment using native drivers, and legacy to deal with, we have also implemented native (non ASCOM) connections to some of the most popular software (and we are still expending the list) .
However since there is no standard anymore here the task is harder, not only FL should know how to interface with each and every third party software, the software should also provide the necessary tools and information for a fully integrated solution.
OPTEC and us are working to improve the situation, which in turns may require some modifications to third party software, outside of our direct control.
This is why we have fully supported ASCOM compliant devices (FW, focuser) for providing an unified way too.