Date
1 - 20 of 106
New OnStep ASCOM drivers
A brand new set (Telescope, Focuser, Rotator, and Switch) of ASCOM drivers for OnStep is now available on my site:
http://www.stellarjourney.com/index.php?r=site/software_telescope
Keep in mind these drivers are Beta and might have bugs. Some of the dialogs below might look similar to those before but the code behind them is largely new. I'm looking for user testing and comments at this point...
http://www.stellarjourney.com/index.php?r=site/software_telescope
Keep in mind these drivers are Beta and might have bugs. Some of the dialogs below might look similar to those before but the code behind them is largely new. I'm looking for user testing and comments at this point...
These are all built to share com port(s)/IP. The current ASCOM drivers (Telescope and Focuser only) have a limitation where only one connection per com port is allowed hence they can require the user to have 2+ "ports" (com/IP) and/or use a hub like POTH. That hub POTH (etc.) only gets one the ability to share the telescope driver between applications though, you still can't have a focuser connected to a com port and also the telescope.
These new drivers dispense with the need for a hub and allow you to effectively forget about these limitations. One little gotcha, that might exist, is that this really needs some interface speed to work well (when all the drivers are contending for the serial port at the same time) and virtual serial ports based on cp2102/ch340/ATmega16U2 actually run at the slow 9600 baud rate set in my driver and in OnStep. I did design-in provision so the default baud rate can be changed in the ASCOM profile store though.
On the other hand Teensy's (and my new the MaxSTM3.6 and the FYSETC S6 AFAIK) ignore the baud rate settings and run at high speed so they should play well with no changes at all.
These new drivers dispense with the need for a hub and allow you to effectively forget about these limitations. One little gotcha, that might exist, is that this really needs some interface speed to work well (when all the drivers are contending for the serial port at the same time) and virtual serial ports based on cp2102/ch340/ATmega16U2 actually run at the slow 9600 baud rate set in my driver and in OnStep. I did design-in provision so the default baud rate can be changed in the ASCOM profile store though.
On the other hand Teensy's (and my new the MaxSTM3.6 and the FYSETC S6 AFAIK) ignore the baud rate settings and run at high speed so they should play well with no changes at all.
Thanks for the heads-up. I did a quick scan of my system (Windows Defender) and it found nothing. A full scan will require time so that will have to wait. Nothing is like scanning with Virus Total anyway...
So I scanned the installer file with Virus Total and it found the same "virus" you saw (Microsoft) and two other hits (for other "viruses") from lesser known scanners.
Very likely false positives.. darn Inno Setup installer has done this to me before. Installers do things that are "virus like" so trigger these detection's sometimes. As a precaution I also scanned all of my compiled ASCOM driver files (one .exe and four .dll) in Virus Total and they were all clear, not one detection.
I updated to the latest Inno Setup (v6.05) and built the installer again. Uploaded to Virus total and it still had three hits but all from lesser known scanners and two of the three were generic apparently flagging behavior but not naming a virus. Again very likely false positives and this solved the big issue of Microsoft's scanner false? positive.
So this new installer (now on my site) should make it past all the big name scanners and I'm calling it clean and functional.
So I scanned the installer file with Virus Total and it found the same "virus" you saw (Microsoft) and two other hits (for other "viruses") from lesser known scanners.
Very likely false positives.. darn Inno Setup installer has done this to me before. Installers do things that are "virus like" so trigger these detection's sometimes. As a precaution I also scanned all of my compiled ASCOM driver files (one .exe and four .dll) in Virus Total and they were all clear, not one detection.
I updated to the latest Inno Setup (v6.05) and built the installer again. Uploaded to Virus total and it still had three hits but all from lesser known scanners and two of the three were generic apparently flagging behavior but not naming a virus. Again very likely false positives and this solved the big issue of Microsoft's scanner false? positive.
So this new installer (now on my site) should make it past all the big name scanners and I'm calling it clean and functional.
This has been my experience also. The file was flagged when I went to install the Ascom driver. It was from Microsoft Security Essentials. The history of Inno and Microsoft is well known. That is why I did not commit to it being real. Nonetheless, It was a pretty specific filename, worth checking out. I will try the new installer and see what it reports on my end.
planetibo@...
Hi!
Good news!
I have tried it on MKS Gen-L v2.
-Onstep Focuser is OK
-Onstep Telescope failed at the Com Port connection
Good news!
I have tried it on MKS Gen-L v2.
-Onstep Focuser is OK
-Onstep Telescope failed at the Com Port connection
Consultez la fin de ce message pour plus de détails sur l'appel du débogage
juste-à-temps (JIT) à la place de cette boîte de dialogue.
************** Texte de l'exception **************
System.FormatException: Le format de la chaîne d'entrée est incorrect.
à ASCOM.OnStep.SetupDialogForm.comboBoxComPort_TextChanged(Object sender, EventArgs e)
à System.Windows.Forms.Control.OnTextChanged(EventArgs e)
à System.Windows.Forms.ComboBox.OnTextChanged(EventArgs e)
à System.Windows.Forms.Control.set_Text(String value)
à System.Windows.Forms.ComboBox.set_Text(String value)
à System.Windows.Forms.ComboBox.UpdateText()
à System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
à System.Windows.Forms.ComboBox.WndProc(Message& m)
à System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
à System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Assemblys chargés **************
mscorlib
Version de l'assembly : 4.0.0.0
Version Win32 : 4.8.4250.0 built by: NET48REL1LAST_C
CodeBase : file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
ASCOM.OnStep
Version de l'assembly : 1.0.0.0
Version Win32 : 1.0.0.0
CodeBase : file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/Telescope/OnStep/ASCOM.OnStep.exe
----------------------------------------
System.Windows.Forms
Version de l'assembly : 4.0.0.0
Version Win32 : 4.8.4250.0 built by: NET48REL1LAST_C
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Version de l'assembly : 4.0.0.0
Version Win32 : 4.8.4200.0 built by: NET48REL1LAST_C
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Version de l'assembly : 4.0.0.0
Version Win32 : 4.8.4084.0 built by: NET48REL1
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
ASCOM.Attributes
Version de l'assembly : 6.0.0.0
Version Win32 : 6.5.0.3091
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.Attributes/6.0.0.0__565de7938946fba7/ASCOM.Attributes.dll
----------------------------------------
ASCOM.OnStep.Focuser
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.0.0
CodeBase : file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/Telescope/OnStep/ASCOM.OnStep.Focuser.DLL
----------------------------------------
ASCOM.DeviceInterfaces
Version de l'assembly : 6.0.0.0
Version Win32 : 6.5.0.3091
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.DeviceInterfaces/6.0.0.0__565de7938946fba7/ASCOM.DeviceInterfaces.dll
----------------------------------------
ASCOM.OnStep.Rotator
Version de l'assembly : 1.0.0.0
Version Win32 : 1.0.0.0
CodeBase : file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/Telescope/OnStep/ASCOM.OnStep.Rotator.DLL
----------------------------------------
ASCOM.OnStep.Switch
Version de l'assembly : 1.0.0.0
Version Win32 : 1.0.0.0
CodeBase : file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/Telescope/OnStep/ASCOM.OnStep.Switch.DLL
----------------------------------------
ASCOM.OnStep.Telescope
Version de l'assembly : 3.0.0.0
Version Win32 : 3.0.0.0
CodeBase : file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/Telescope/OnStep/ASCOM.OnStep.Telescope.DLL
----------------------------------------
System.Configuration
Version de l'assembly : 4.0.0.0
Version Win32 : 4.8.4190.0 built by: NET48REL1LAST_B
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Version de l'assembly : 4.0.0.0
Version Win32 : 4.8.4220.0 built by: NET48REL1LAST_C
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Version de l'assembly : 4.0.0.0
Version Win32 : 4.8.4084.0 built by: NET48REL1
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
Version de l'assembly : 4.0.0.0
Version Win32 : 4.8.4084.0 built by: NET48REL1
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
ASCOM.Utilities
Version de l'assembly : 6.0.0.0
Version Win32 : 6.5.0.3091
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.Utilities/6.0.0.0__565de7938946fba7/ASCOM.Utilities.dll
----------------------------------------
ASCOM.Astrometry
Version de l'assembly : 6.0.0.0
Version Win32 : 6.5.0.3091
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.Astrometry/6.0.0.0__565de7938946fba7/ASCOM.Astrometry.dll
----------------------------------------
Microsoft.VisualBasic
Version de l'assembly : 10.0.0.0
Version Win32 : 14.8.4084.0 built by: NET48REL1
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
ASCOM.Exceptions
Version de l'assembly : 6.0.0.0
Version Win32 : 6.5.0.3091
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.Exceptions/6.0.0.0__565de7938946fba7/ASCOM.Exceptions.dll
----------------------------------------
mscorlib.resources
Version de l'assembly : 4.0.0.0
Version Win32 : 4.8.4084.0 built by: NET48REL1
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_fr_b77a5c561934e089/mscorlib.resources.dll
----------------------------------------
System.Windows.Forms.resources
Version de l'assembly : 4.0.0.0
Version Win32 : 4.8.4084.0 built by: NET48REL1
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_fr_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------
************** Débogage JIT **************
Pour activer le débogage juste-à-temps (JIT), le fichier de configuration pour cette
application ou cet ordinateur (machine.config) doit avoir la valeur
jitDebugging définie dans la section system.windows.forms.
L'application doit également être compilée avec le débogage
activé.
Par exemple :
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
Lorsque le débogage juste-à-temps est activé, les exceptions non gérées
seront envoyées au débogueur JIT inscrit sur l'ordinateur
plutôt que d'être gérées par cette boîte de dialogue.
hitosi sato
Hi Howard
It was possible to connect CDC, SharpCap and NINA at the same time.
I have not tried PHD2 yet.
I think it is a very wonderful progress.
I hope that future development will continue.
When I actually connected it, the virtual hand-pad of CDC, NINA and SharpCap did not work by an error.I think that the error message was "ASCOMmoveaxis primary rate".
In Device-hub and OnStep2.06, the hand-pad works with any application.
Hitoshi
On Friday, October 9, 2020, 1:20:08 PM GMT+9, <planetibo@...> wrote:
Hi!
Good news!
I have tried it on MKS Gen-L v2.
-Onstep Focuser is OK
-Onstep Telescope failed at the Com Port connection
Good news!
I have tried it on MKS Gen-L v2.
-Onstep Focuser is OK
-Onstep Telescope failed at the Com Port connection
Consultez la fin de ce message pour plus de détails sur l'appel du débogage
juste-à-temps (JIT) à la place de cette boîte de dialogue.
************** Texte de l'exception **************
System.FormatException: Le format de la chaîne d'entrée est incorrect.
à ASCOM.OnStep.SetupDialogForm.comboBoxComPort_TextChanged(Object sender, EventArgs e)
à System.Windows.Forms.Control.OnTextChanged(EventArgs e)
à System.Windows.Forms.ComboBox.OnTextChanged(EventArgs e)
à System.Windows.Forms.Control.set_Text(String value)
à System.Windows.Forms.ComboBox.set_Text(String value)
à System.Windows.Forms.ComboBox.UpdateText()
à System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
à System.Windows.Forms.ComboBox.WndProc(Message& m)
à System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
à System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Assemblys chargés **************
mscorlib
Version de l'assembly : 4.0.0.0
Version Win32 : 4.8.4250.0 built by: NET48REL1LAST_C
CodeBase : file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
ASCOM.OnStep
Version de l'assembly : 1.0.0.0
Version Win32 : 1.0.0.0
CodeBase : file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/Telescope/OnStep/ASCOM.OnStep.exe
----------------------------------------
System.Windows.Forms
Version de l'assembly : 4.0.0.0
Version Win32 : 4.8.4250.0 built by: NET48REL1LAST_C
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Version de l'assembly : 4.0.0.0
Version Win32 : 4.8.4200.0 built by: NET48REL1LAST_C
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Version de l'assembly : 4.0.0.0
Version Win32 : 4.8.4084.0 built by: NET48REL1
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
ASCOM.Attributes
Version de l'assembly : 6.0.0.0
Version Win32 : 6.5.0.3091
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.Attributes/6.0.0.0__565de7938946fba7/ASCOM.Attributes.dll
----------------------------------------
ASCOM.OnStep.Focuser
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.0.0
CodeBase : file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/Telescope/OnStep/ASCOM.OnStep.Focuser.DLL
----------------------------------------
ASCOM.DeviceInterfaces
Version de l'assembly : 6.0.0.0
Version Win32 : 6.5.0.3091
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.DeviceInterfaces/6.0.0.0__565de7938946fba7/ASCOM.DeviceInterfaces.dll
----------------------------------------
ASCOM.OnStep.Rotator
Version de l'assembly : 1.0.0.0
Version Win32 : 1.0.0.0
CodeBase : file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/Telescope/OnStep/ASCOM.OnStep.Rotator.DLL
----------------------------------------
ASCOM.OnStep.Switch
Version de l'assembly : 1.0.0.0
Version Win32 : 1.0.0.0
CodeBase : file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/Telescope/OnStep/ASCOM.OnStep.Switch.DLL
----------------------------------------
ASCOM.OnStep.Telescope
Version de l'assembly : 3.0.0.0
Version Win32 : 3.0.0.0
CodeBase : file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/Telescope/OnStep/ASCOM.OnStep.Telescope.DLL
----------------------------------------
System.Configuration
Version de l'assembly : 4.0.0.0
Version Win32 : 4.8.4190.0 built by: NET48REL1LAST_B
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Version de l'assembly : 4.0.0.0
Version Win32 : 4.8.4220.0 built by: NET48REL1LAST_C
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Version de l'assembly : 4.0.0.0
Version Win32 : 4.8.4084.0 built by: NET48REL1
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
Version de l'assembly : 4.0.0.0
Version Win32 : 4.8.4084.0 built by: NET48REL1
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
ASCOM.Utilities
Version de l'assembly : 6.0.0.0
Version Win32 : 6.5.0.3091
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.Utilities/6.0.0.0__565de7938946fba7/ASCOM.Utilities.dll
----------------------------------------
ASCOM.Astrometry
Version de l'assembly : 6.0.0.0
Version Win32 : 6.5.0.3091
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.Astrometry/6.0.0.0__565de7938946fba7/ASCOM.Astrometry.dll
----------------------------------------
Microsoft.VisualBasic
Version de l'assembly : 10.0.0.0
Version Win32 : 14.8.4084.0 built by: NET48REL1
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
ASCOM.Exceptions
Version de l'assembly : 6.0.0.0
Version Win32 : 6.5.0.3091
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.Exceptions/6.0.0.0__565de7938946fba7/ASCOM.Exceptions.dll
----------------------------------------
mscorlib.resources
Version de l'assembly : 4.0.0.0
Version Win32 : 4.8.4084.0 built by: NET48REL1
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_fr_b77a5c561934e089/mscorlib.resources.dll
----------------------------------------
System.Windows.Forms.resources
Version de l'assembly : 4.0.0.0
Version Win32 : 4.8.4084.0 built by: NET48REL1
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_fr_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------
************** Débogage JIT **************
Pour activer le débogage juste-à-temps (JIT), le fichier de configuration pour cette
application ou cet ordinateur (machine.config) doit avoir la valeur
jitDebugging définie dans la section system.windows.forms.
L'application doit également être compilée avec le débogage
activé.
Par exemple :
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
Lorsque le débogage juste-à-temps est activé, les exceptions non gérées
seront envoyées au débogueur JIT inscrit sur l'ordinateur
plutôt que d'être gérées par cette boîte de dialogue.
Howard Dutton
On Thu, Oct 8, 2020 at 09:20 PM, <planetibo@...> wrote:
For everyone; knowing the conditions leading up to any problem is essential information without which I'm in the dark:
Versions: OnStep and Windows at a minimum.
Hardware: What is OnStep running on.
Interface being used: IP or Com, is DTR control on, is ECP (error correction) on.
I have tried it on MKS Gen-L v2.I tested with an MKS Gen-L v2 during development. Naturally it's impossible to check every combination of everything...
-Onstep Focuser is OK
-Onstep Telescope failed at the Com Port connection
Consultez la fin de ce message pour plus de détails sur l'appel du débogagejuste-à-temps (JIT) à la place de cette boîte de dialogue.************** Texte de l'exception **************System.FormatException: Le format de la chaîne d'entrée est incorrect.
For everyone; knowing the conditions leading up to any problem is essential information without which I'm in the dark:
Versions: OnStep and Windows at a minimum.
Hardware: What is OnStep running on.
Interface being used: IP or Com, is DTR control on, is ECP (error correction) on.
Howard Dutton
On Fri, Oct 9, 2020 at 12:43 AM, hitosi sato wrote:
If you are referring to OnStep version 2.06 that isn't going to work...
these ASCOM drivers require OnStep release-3.16 or later.
When I actually connected it, the virtual hand-pad of CDC, NINA and SharpCap did not work by an error.I did basic testing with CdC and NINA (while connected in my Sky Planetarium) and had no issue.
I think that the error message was "ASCOMmoveaxis primary rate".
In Device-hub and OnStep2.06, the hand-pad works with any application.Not sure why one would need a Hub with these drivers, but ok.
If you are referring to OnStep version 2.06 that isn't going to work...
these ASCOM drivers require OnStep release-3.16 or later.
I don’t think I could do without poth as the hub. I think all the dome control offsets are stored in the hub.
How would users requiring observatory control do away with poth?
Curly
On Fri, 9 Oct 2020 at 12:23, Howard Dutton <hjd1964@...> wrote:
On Fri, Oct 9, 2020 at 12:43 AM, hitosi sato wrote:
When I actually connected it, the virtual hand-pad of CDC, NINA and SharpCap did not work by an error.I did basic testing with CdC and NINA (while connected in my Sky Planetarium) and had no issue.
I think that the error message was "ASCOMmoveaxis primary rate".
In Device-hub and OnStep2.06, the hand-pad works with any application.Not sure why one would need a Hub with these drivers, but ok.
If you are referring to OnStep version 2.06 that isn't going to work...
these ASCOM drivers require OnStep release-3.16 or later.
Howard Dutton
On Fri, Oct 9, 2020 at 04:22 AM, Howard Dutton wrote:
That isn't entirely surprising; a known "loose end" I need to look into.
On Fri, Oct 9, 2020 at 12:43 AM, hitosi sato wrote:I see what you're saying... basically it works but you have trouble with the hand pad controls.
When I actually connected it, the virtual hand-pad of CDC, NINA and SharpCap did not work by an error.I did basic testing with CdC and NINA (while connected in my Sky Planetarium) and had no issue.
I think that the error message was "ASCOMmoveaxis primary rate".
In Device-hub and OnStep2.06, the hand-pad works with any application.Not sure why one would need a Hub with these drivers, but ok.
If you are referring to OnStep version 2.06 that isn't going to work...
these ASCOM drivers require OnStep release-3.16 or later.
That isn't entirely surprising; a known "loose end" I need to look into.
I'm sorry for not understanding this right, but what new options does this open? With what can it be controlled outside of imaging software? Eqmod or is poth still the main controller (I used it as such, but if there's anything better to control the telescope please let me know)? Thank you!
On Fri, Oct 9, 2020, 5:32 PM Howard Dutton <hjd1964@...> wrote:
I should mention that I still need to implement the "Auto set date/time [ ]" option in the new Telescope driver. So if that doesn't work, it's not implemented in the driver!
Howard Dutton
On Fri, Oct 9, 2020 at 11:13 AM, Howard Dutton wrote:
On Fri, Oct 9, 2020 at 10:59 AM, Nikos Polikandriotis wrote:Version 1.0.2 is now on my site. Should fix this bug.
For reference I am using MKS gen L v1.0, Alt Azimuth mount TMC 2130 for both Axis and HC-05 BluetoothThanks, AltAzm mode bug... looks like the meridian limit check/upload on [Ok] press should be disabled but isn't.