RandomUsername

Did you get this sorted? I had an issue with the Windows defender, and I had to add the software to the 'ok' list. Windows 11. My process was, create a folder on my desktop (I called it Synscan Pro - probably not important, but I would believe the programme needs all files in the same folder, not on a desktop), clicked on the .exe file. The system gave a warning. I scanned with my anti-virus - all ok. Continued with opening it, and it wasn't doing anything. After a search I just added it to the ok list. Also, be aware, it tried to setup the network connection as public, not home. Not sure if it makes a difference, but I wanted it closed.

Hello, Been a while since I've been on here, but you guys on here are most likely to know how to help. I have a Sky-Watcher Go-to mount using a Synscan Wi-Fi module. I am using Synscan Pro on either my laptop or phone. I am getting tired of having to argue with my Go-to mount about where things are, and how long it takes to set-up. Once it is setup, it's actually a half decent bit of kit. However, there are times when I input the stars and it seems like it believes it's concave and looking up it's own Bottom - pointing nowhere near my object goal and into the planet.... My aim is to: Auto-setup/calibrate my telescope - So, I can lend it to family and friends, and they can just put it down in a field and get watching. The process I intend going to go through is: Figure out how to manually insert my 'numbers' into Synscan Pro to make it believe it has been calibrated. Does anyone know if you can manually insert a home point - i.e. I make the telescope level and point to north, then tell the software this is home? There seems to be something about easy tracking, but I'm not sure it's what I want. Then, I will use a magnetometer on the mount to test accuracy (suggested +/-1°). I'll start with using it as a compass. Once I can get the numbers from the Magnetometer (somehow get that auto-inserted). Then, once I can reliably get my rough home, I can start the more accurate alignment process- e.g. 3-point This might be enough, but after having this odd random pointing through the planet thing (that once nearly broke the cables), I am going to push on.... This will be the hard part - using a DSLR and pattern matching software, centre the right star/planet in the viewfinder, and then give it the 'OK' to move onto the next point in the calibration. There are two parts I believe I will need to investigate after this: A 're-centering' button if I'm a little bit out - it bugs me when the target is slightly off to the side. Calibration of the stepper motors Sometimes I get a drift where the object moves out of vision (this could actually be only down to calibration accuracy..?). Either way, sorting this would greatly effect/improve any long-exposure photos. Does anyone have experience with this sort of thing? Any help, greatly appreciated. Thanks

Ok, thanks. But that's not quite what I need. I actually need to force the programme to run so I can check what's going wrong. I am going to presume for the moment that the cable is ok, and that the problem lies with either the mount or the programme. I think I'll give either stargazer or ASCOM a shout.

Is there any way to force it to 'run' with an oscilloscope? I think that would be the best place to start. I could keep buying things and I'm not 100% sure that the programme is working correctly. I need to measure a 'what if signals were being given out' scenario. For nothing to happen at all doesn't prove anything about the cable. It could even be an issue with the mount itself. It hasn't been used in a couple of years. If I could get a signal outgoing I would have some confidence that the programme can do something. Who knows, it could be an issue with a firewall, or conflicting programme/driver.

Thanks for the reply. My 'adapted' RS232 was producing the required voltage and signal. That aside, there was still no option to choose a COM. Any ideas on why? I also purchased a TTL connector to remove all arguments. The programme still doesn't allow any COM whatsoever. Even if I 'force' it to give me the COM5 where I am connected to. Device manager says COM5... unless that's different somehow?

I know this topic is old, but I thought I'd continue as it's one of the only few threads similar to mine. My serial adaptor is COM5. All working fine. When I get to the properties, there is no COM5. I have a Synscan AZ, and the handset is broken. So I am going direct. I have also downloaded the Skywatcher driver, which I am told is for my mount. When I add COM5 to the 'force' option, it still doesn't appear. The logs say: 19:56:05.799 Init Driver Version 6.0.6262.14792 19:56:05.830 GetId Generated new ID: 1 19:56:05.830 Telescope Instance ID: 1, new: Driver ID: ASCOM.SkyWatcher.Telescope 19:56:05.862 Set Connected Set Connected 1 to: True, AlreadyConnected: False 19:56:05.909 ConnectSerial unexpected serial exception System.ArgumentException: The PortName cannot be empty. Parameter name: PortName at ASCOM.Utilities.Serial.set_Connected(Boolean Connecting) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 520 at ASCOM.SkyWatcher.Serial.set_Connected(Boolean value) at ASCOM.SkyWatcher.Serial.ConnectSerial() 19:56:05.924 DisconnectSerial force True 19:56:05.924 DisconnectSerial finished 19:56:05.924 Connected set True, id 1, error System.ArgumentException: The PortName cannot be empty. Parameter name: PortName at ASCOM.Utilities.Serial.set_Connected(Boolean Connecting) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 520 at ASCOM.SkyWatcher.Serial.set_Connected(Boolean value) at ASCOM.SkyWatcher.Serial.ConnectSerial() at ASCOM.SkyWatcher.Serial.SetConnected(Int64 id, Boolean value) at ASCOM.SkyWatcher.Telescope.set_Connected(Boolean value) 19:56:07.900 Set Connected Set Connected 1 to: False, Successfully removed: False 19:56:07.900 DisconnectSerial force False 19:56:07.900 DisconnectSerial serial Disconnect error System.NullReferenceException: Object reference not set to an instance of an object. at ASCOM.SkyWatcher.Serial.DisconnectSerial(Boolean force) 19:56:07.900 Connected set False, id 1, error System.NullReferenceException: Object reference not set to an instance of an object. at ASCOM.SkyWatcher.Serial.DisconnectSerial(Boolean force) at ASCOM.SkyWatcher.Serial.SetConnected(Int64 id, Boolean value) at ASCOM.SkyWatcher.Telescope.set_Connected(Boolean value) 19:56:10.576 Set Connected Set Connected 1 to: False, Successfully removed: False 19:56:10.576 DisconnectSerial force False 19:56:10.576 DisconnectSerial serial Disconnect error System.NullReferenceException: Object reference not set to an instance of an object. at ASCOM.SkyWatcher.Serial.DisconnectSerial(Boolean force) 19:56:10.576 Connected set False, id 1, error System.NullReferenceException: Object reference not set to an instance of an object. at ASCOM.SkyWatcher.Serial.DisconnectSerial(Boolean force) at ASCOM.SkyWatcher.Serial.SetConnected(Int64 id, Boolean value) at ASCOM.SkyWatcher.Telescope.set_Connected(Boolean value) 20:05:18.439 GetId Generated new ID: 2 20:05:18.439 Telescope Instance ID: 2, new: Driver ID: ASCOM.SkyWatcher.Telescope 20:05:20.549 IdentifySynScan Port COM5 - found nothing I checks COM5, but doesn't offer it on the drop down list. I have wired my own RS232 RX-Pin2 TX-Pin3 Signal Gnd-Pin 5 Why can't the programme at least detect that COM5 is there? if there's an issue, it should at least say: Yes, it's there, but there's something wrong... Any ideas?