Pyxis Rotator Issues with 2.5.2.5


#1

Greetings
After my upgrade to 2.5.2.5 pyxis rotator does not seem to work. I am running pyxis commander 3.02
Downgrading to 2.5.2.4 works fine

My thoughts
The behavior may be related to
"SGPro now attempts to detect external device disconnections (and provide a notification to fix it)"

When starting SGPpro and connecting the rotator, if the rotator is not ready usually I need to home it.
So the steps are connect equipment/rotator -> settings -> home rotator -> ready to go
I think that the rotator once it performs its function it disconnects.

In 2.5.2.5 I connect equipment/rotator. Home and the rotator disconnects

Form the logs
[10/20/2016 10:04:11 PM] [DEBUG] [Equipment Connectivity Thread] SGPro thinks the rotator is connected, but it’s not, syncing UI…
[10/20/2016 10:04:11 PM] [DEBUG] [Equipment Connectivity Thread] Adding sequence level notification: External disconnect of rotator detected…
[10/20/2016 10:04:11 PM] [DEBUG] [Equipment Connectivity Thread] Handling monitoring event (Email 1, Warning): External disconnect of rotator detected…
[10/20/2016 10:04:11 PM] [DEBUG] [Main Thread] Disconnecting ASCOM Rotator: ASCOM.PyxisUniversal.Rotator

I have uploaded both logs. They are not that clean but I can reproduce the issue easily if needed.
Good rotator is on 2.5.2.4
Bad rotator is on 2.5.2.5

Please advise

bad rotator.txt (47.2 KB)
good rotator.txt (539.9 KB)


Are Optec Pyxis rotators incompatible with SGP?
#2

I don’t understand this. Why would it do that?


#3

Sorry I should have been more clear.
I am not disconnecting. SGP or the driver seems to disconnect.

My usually behavior
I connect to Pyxis through SGP. If the rotator is not homed It will not move
So I go to the equipment dialog, I do settings, on the pyxis settings I connect and home. I am then able to use rotator.
In 2.5.2.5
after home, SGP disconnects the rotator by itself

g


#4

There is no code in SGPro to do this. We would really need to correlate the device logs to figure out what is happening here.


#5

Ok, I will do some new tests and find the device logs


#6

ken,
I am still trying to find the pyxis logs. (if anyone knows where they reside please ping me)
In the meantime I did the following experiment
On 2.5.2.4 I started SGP connected to the rotator. In the control panel/ rotator /settings. Home the rotator through the pyxis interface. Set the rotator at 90degrees. Works great:

[10/25/2016 2:04:05 PM] [DEBUG] [Main Thread] Connecting ASCOM rotator…
[10/25/2016 2:04:18 PM] [DEBUG] [Rotator Thread] SGM_ROTATOR_MOVE_ABS message received…
[10/25/2016 2:04:18 PM] [DEBUG] [Rotator Thread] ASCOM Rotator: Moving rotator to 15
[10/25/2016 2:04:18 PM] [DEBUG] [Rotator Thread] ASCOM Rotator: Sync offset is 0
[10/25/2016 2:04:19 PM] [DEBUG] [Rotator Thread] SGM_ROTATOR_MOVE_ABS message complete…
[10/25/2016 2:09:29 PM] [DEBUG] [Rotator Thread] SGM_ROTATOR_MOVE_ABS message received…
[10/25/2016 2:09:29 PM] [DEBUG] [Rotator Thread] ASCOM Rotator: Moving rotator to 90
[10/25/2016 2:09:29 PM] [DEBUG] [Rotator Thread] ASCOM Rotator: Sync offset is 0
[10/25/2016 2:09:59 PM] [DEBUG] [Rotator Thread] SGM_ROTATOR_MOVE_ABS message complete…

On 2.5.2.5
Exact same scenario
[10/25/2016 1:58:25 PM] [DEBUG] [Rotator Thread] SGM_ROTATOR_MOVE_ABS message received…
[10/25/2016 1:58:25 PM] [DEBUG] [Rotator Thread] ASCOM Rotator: Moving rotator to 25
[10/25/2016 1:58:25 PM] [DEBUG] [Rotator Thread] ASCOM Rotator: Sync offset is 0
[10/25/2016 1:58:25 PM] [DEBUG] [Rotator Thread] SGM_ROTATOR_MOVE_ABS message complete…
[10/25/2016 1:58:45 PM] [DEBUG] [Equipment Connectivity Thread] SGPro thinks the rotator is connected, but it’s not, syncing UI…
[10/25/2016 1:58:45 PM] [DEBUG] [Equipment Connectivity Thread] Adding sequence level notification: External disconnect of rotator detected…
[10/25/2016 2:01:41 PM] [DEBUG] [Equipment Connectivity Thread] Handling monitoring event (Email 1, Warning): External disconnect of rotator detected…
[10/25/2016 2:01:41 PM] [DEBUG] [Main Thread] Disconnecting ASCOM Rotator: ASCOM.PyxisUniversal.Rotator

logs included
rotator24.txt (21.7 KB)
rotator25.txt (22.0 KB)


#7

Right. I know why SGPro is doing what it’s doing, I just don’t understand why your rotator property indicating a good connection is returning that the connection is no longer good.

We need to see the device logs in order to understand why this property indicating if the device is connected ( http://www.ascom-standards.org/Help/Developer/html/P_ASCOM_DriverAccess_AscomDriver_Connected.htm) is indicating that the device is no longer connected.


#8

Daniel (from Optec) here.

I think I can shed some light on this behavior seeing as I wrote the driver. The Pyxis Commander driver allows multiple clients to connect to the rotator at the same time. However several setup functions for Pyxis 2 and 3 instances require complete control of the rotator. Thus when the setup window for the Pyxis instance is open connected clients can not send commands and, as per the definition of Connected, the Connected state is set to false. Once the setup is complete the connected state is returned to true (assuming the rotator can still connect).

I had tested this behavior with several client programs, including SGP, without any issues. Given that there is now an issue I may change the behavior to pretend that the rotator is still connected while the setup is running.

Homing the rotator does not require the setup dialog. Both SGP and Pyxis Commander can connect to the same rotator at the same time. Pyxis Commander also offers a home feature under the device menu and this one will not disconnect the rotator.


www.mainsequencesoftware.com