photon Posted October 14, 2023 Report Share Posted October 14, 2023 No, there is no new driver from ASA for us. Instead I wrote an ASCOM telescope driver with connects to the existing AutoSlew ASCOM driver as "man in the middle" translator. This driver adds some missing features from the original driver. I was able to connect to NINA without issues and to do an automatic 3 point polar alignment :-) It's not yet super polished, but works for me. If anybody is interested please visit https://github.com/photon1503/ASCOMProxyHub and also open discussions and issues directly on GitHub. -- Gerald Link to comment Share on other sites More sharing options...
Rsanalb Posted October 14, 2023 Report Share Posted October 14, 2023 (edited) Thanks for your time and Work, i try and tell you something. great notice Edited October 14, 2023 by Rsanalb Link to comment Share on other sites More sharing options...
AnakChan Posted October 14, 2023 Report Share Posted October 14, 2023 (edited) @photon #1 thank you so very much for this. I believe this will make many N.I.N.A. <-> AutoSlew users very happy. #2, small issue but when trying to download this on my Windows PC, Windows Defender blocked with a virus threat warning. I created and left an issue in your project. Not certain if it's a header/signture/crc issue. Pls ignore! Looks liked you've fixed it. I'm able to download and am testing it now (running Conformance on it). Edited October 14, 2023 by AnakChan Link to comment Share on other sites More sharing options...
Rsanalb Posted October 14, 2023 Report Share Posted October 14, 2023 I try and perfect connection. I connect phd2 and connect too. I try other time and tell you the result. thanks again Link to comment Share on other sites More sharing options...
photon Posted October 14, 2023 Author Report Share Posted October 14, 2023 Great to hear that it works for you 😀 @AnakChan You can also find the result of my Conformance tests here: https://github.com/photon1503/ASCOMProxyHub/tree/main/Conform Let me know if you find some issues. I'm not using PulseGuide so can't test this one. Link to comment Share on other sites More sharing options...
Rsanalb Posted October 14, 2023 Report Share Posted October 14, 2023 Hace 2 horas, el fotón dijo: Me alegro de saber que funciona para ti 😀 @AnakChanTambién puedes encontrar el resultado de mis pruebas de conformidad aquí: https://github.com/photon1503/ASCOMProxyHub/tree/main/Conform Avísame si encuentras algún problema. No estoy usando PulseGuide, así que no puedo probar este. Of course, I send you the practice, but now it’s raining, ajjajaj Link to comment Share on other sites More sharing options...
photon Posted October 15, 2023 Author Report Share Posted October 15, 2023 In the meantime Stefan from NINA also built some workarounds in the nightly build. Maybe this also helps us to directly connect now without having the "Proxy" in between. Link to comment Share on other sites More sharing options...
photon Posted October 15, 2023 Author Report Share Posted October 15, 2023 FYI, the connection issues in NINA nightly build #63 has now gone. So for most users this should be fine. But for 3PPA, we still cannot switch tracking on/off due to missing implementations in the ASA ASCOM driver. Only when using the ASCOM Proxy we have control over this feature. Link to comment Share on other sites More sharing options...
AnakChan Posted October 16, 2023 Report Share Posted October 16, 2023 Will you be updating your driver to skip the UTCDate part now that Stefan's addressed it? But will still need your ASCOMProxyHub for the TrackingRate property? FYI can't remember if it's 1.01 or 1.02, I did have issues in syncing the location from N.I.N.A. to the mount - in my case it's just the elevation on my site. Link to comment Share on other sites More sharing options...
photon Posted October 16, 2023 Author Report Share Posted October 16, 2023 Hi, yes I'll keep UTCDate calcluation in the driver in order to pass the conformance test. Basicall it doesn't matter at which level the UTCdate is being calculcated. And for TrackingRate you need the driver anyway. Regarding syncing the location - this doesn't also work for me. Did this work with direct connection to AutoSlew? Link to comment Share on other sites More sharing options...
Rsanalb Posted October 21, 2023 Report Share Posted October 21, 2023 On 10/16/2023 at 8:00 PM, photon said: Hi, yes I'll keep UTCDate calcluation in the driver in order to pass the conformance test. Basicall it doesn't matter at which level the UTCdate is being calculcated. And for TrackingRate you need the driver anyway. Regarding syncing the location - this doesn't also work for me. Did this work with direct connection to AutoSlew? Nina take my location from auto slew. In my case Link to comment Share on other sites More sharing options...
photon Posted October 25, 2023 Author Report Share Posted October 25, 2023 On 10/21/2023 at 5:36 PM, Rsanalb said: Nina take my location from auto slew. In my case It will work from AutoSlew to NINA. But if you want to sync the other way - from NINA to AutoSlew - the new location will not be persistent in AutoSlew unfortunately. Link to comment Share on other sites More sharing options...
Joha Posted November 16, 2023 Report Share Posted November 16, 2023 Thank you very much for your interesting implementation. I would prefer to use the ASA DDM 60 with NINA for long time exposures of ~ 20 min and would need good pointing files. For short time exposures of ~ 2min I use an existing pointing file via ASCOM Device Hub. Unfortunately I get a severe error when I try to connect the ASA DDM 60 mount in NINA. The ASCOM.photonProxyHub.Hardware log says: ... 17:57:15.675 Connected Set True 17:57:15.688 Connected Set Connecting to proxy AstrooptikServer.Telescope 17:57:15.700 Connected Set Threw an exception: System.Runtime.InteropServices.COMException (0x80040154): Die COM-Klassenfactory f[FC]r die Komponente mit CLSID {99352175-9A79-4457-BFE5-05BBBB61FB5C} konnte aufgrund des folgenden Fehlers nicht abgerufen werden: 80040154 Klasse nicht registriert (Ausnahme von HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). bei System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck) bei System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) bei System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) bei System.Activator.CreateInstance(Type type, Boolean nonPublic) bei System.Activator.CreateInstance(Type type) bei ASCOM.photonProxyHub.Telescope.TelescopeHardware.set_Connected(Boolean value) bei ASCOM.photonProxyHub.Telescope.Telescope.set_Connected(Boolean value) When I check the registry CLSID {99352175-9A79-4457-BFE5-05BBBB61FB5C} is not available. Looks like a component is not found / registered. Any idea how to overcome this issue - thanks. Link to comment Share on other sites More sharing options...
photon Posted November 17, 2023 Author Report Share Posted November 17, 2023 Joha, which versions of ASCOM, NINA and ASCOMProxyHub are you using? With latest ASCOM 6.6SP2, NINA 2.3HF2 and https://github.com/photon1503/ASCOMProxyHub/releases/download/1.0.0.3/ProxyHub.Setup.1.0.0.3-direct.exe I cannot reproduce the issue. Link to comment Share on other sites More sharing options...
Joha Posted November 18, 2023 Report Share Posted November 18, 2023 Hello photon, last night I had the chance to verify the issue on the Windows 10 telescope computer. I used ASCOMProxyHub-1.0.0.3 and slightly older versions of the ASCOM and NINA software, e.g. ASCOM 6.6SP1. After updating to the versions you mention, the behavior is the same. On my Windows notebook I tested ASCOMProxyHub-1.0.0.3, NINA and ASCOM Simulator Telescope without any problems. I will try further options on the telescope computer. Link to comment Share on other sites More sharing options...
robertp Posted January 21 Report Share Posted January 21 (edited) Hi Gerald, when I try to connect Nina to my DDM60 via your proxy hub, I get the same error message as Joha. Updating to Ascom 6.6SP2 did not help. I tried to test the proxy from within MaximDL and when I try to connect via the proxy, a window pops up asking for the type of mount: When I select e.g. German Equatorial, MaximDL disconnects from the proxy (without a visible error message). Here's what the ASCOM Diagnosis shows when trying to connect: Is there anything that I can do to help you track the problem down? Thanks and best regards, Robert Edited January 21 by robertp Link to comment Share on other sites More sharing options...
robertp Posted January 28 Report Share Posted January 28 (edited) Hello Gerald, I just realized that there is a newer version (1.0.0.5) of your proxy. I uninstalled my older version (1.0.0.3) and now everything works as intended! Thanks again for your great support of the community, Robert Edited January 28 by robertp Link to comment Share on other sites More sharing options...
astrobry Posted March 26 Report Share Posted March 26 On 10/14/2023 at 8:13 AM, photon said: Instead I wrote an ASCOM telescope driver with connects to the existing AutoSlew ASCOM driver as "man in the middle" translator. This driver adds some missing features from the original driver. I was able to connect to NINA without issues and to do an automatic 3 point polar alignment :-) It's not yet super polished, but works for me. If anybody is interested please visit https://github.com/photon1503/ASCOMProxyHub and also open discussions and issues directly on GitHub. Hi Gerald, Due to a faulty PC in the observatory, I had to fit a new PC and had problems with the ascom driver of my DDM85 mount. Thanks to your solution, it works fine now with the Sky 6.22 and Maxim DL 5 ! Thanks for the great support !! greatly appreciated ! Erik Link to comment Share on other sites More sharing options...
photon Posted March 31 Author Report Share Posted March 31 Hi Erik and others, thank you, I am happy that the workaround works for you! I rarely visit this forum. If anybody needs support please use the GitHub Issue feature. https://github.com/photon1503/ASCOMProxyHub/issues Otherwise I encourage everybody to insist ASA to provide an updated driver for us "legacy" users. Gerald Link to comment Share on other sites More sharing options...
Wojtek Gdańsk Posted April 21 Report Share Posted April 21 (edited) Hello, I would like to ask for help. My computer is Windows 10 Pro. NINA plugin for creating ASA models. It doesn't work for me. The file is saved as grd and is not saved in the ASA >Sequence>PonitingPics folder, therefore I cannot open this file for conversion. Maybe you know what I'm doing wrong. Thank you for your help . Regards. Wojtek. Edited April 21 by Wojtek Gdańsk Link to comment Share on other sites More sharing options...
photon Posted April 25 Author Report Share Posted April 25 Hi Wojtek, The Model Builder Plugin automatically saves a .pox files in Sequence/PointingPics after a successful run. There is also a notification in NINA which will appear after the last position has been solved. The .grd Files are just for Grids (Positions). They also can be imported/exported but are not used for calculating the model. You can also check the NINA log file if something went wrong. I made a new model yesterday and it should look like this: Link to comment Share on other sites More sharing options...
Wojtek Gdańsk Posted May 1 Report Share Posted May 1 Hello and thank you for your interest in my problem. For me, the NINA plug-in, after creating a model of about 10 stars, for some reason does not want to save the model in the ASA>Sequence>PointingPics folder. Perhaps because there is no NINA folder in ASA>Sequence>PointingPics. Apart from the NINA plug-in for creating ASA models, do I need to upload anything additional? Thank you for your help. Regards. Wojtek. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now