However, it didn't appear to respond to the keyboard or mouse. I opened APT and then switched apps using Alt Tab and seeing Stellarium in the list, I selected it and behold, there it is. I went back to remote desktop and still nothing. I hook up monitor and login locally and Stellarium is there and works fine. I run Stellarium and nothing seems to happen. Currently connected over ethernet but will go Wi Fi in the field. I'm using a mini PC for remote control with my laptop. And I have come across the most bizarre of issues. After several hours of trial and error I got everyti8ng actually talking to APT. I got the guide equipment camera last week along with other electronics so U figured I would set everything up on the PC that will be running the imaging session. Everything is here except for the telescope itself. TelescopeClientASCOM::TelescopeClientASCOM with telescope name "New Telescope 1" and ascomDeviceId "'s been a while since I've posted, been busy these last few months while I've been waiting for my scope to to arrive that ordered back in February.
OleInvoke: Exception GLE: 0Ĭould not connect to device: ""ĬonnectionType: 7 initString: "New Telescope 1:ASCOM:J2000::false"Ĭreating telescope "New Telescope 1:ASCOM:J2000::false" name/type/equinox/params: "New Telescope 1" "ASCOM" J2000 ":false"
TelescopeClientASCOM::TelescopeClientASCOM with telescope name "New Telescope 1" and ascomDeviceId "" port name: "COM3" vendor identifier: 1027 product identifier: 24597ĬonnectionType: 7 initString: "New Telescope 1:ASCOM:J2000::false"Ĭreating telescope "New Telescope 1:ASCOM:J2000::false" name/type/equinox/params: "New Telescope 1" "ASCOM" J2000 ":false" Here is what I see in the log file after my tests I was getting some errors from iOptron commander that an invalid slew request was made that was out of range. Sometimes when I tried to slew nothing happened, other times it wakes up after a minute or two and move the mount. For some reason there are two ASCOM mount devices listed in the drop down for the GEM45 (I see from the logs that one is 2014 and one is the 2017 version) Using the 2017 version I was able to connect but slewing was hit or miss and fairly random. I turned logging on and tried a few tests.
0 kommentar(er)
