Single slew command possible

[ventikappa]

I'm evaluating trial of version 3.2.0 against a competitor app.

BYE costs 3 times more but I acknowledge it has a better crafted UI.

However, I'm facing a blocking problem.

After connecting my mount, I can only issue a single slew command, either RA or DEC. After that, the mount motion control stops working.

The mount control works ok in EQMOD app and in the competing app.

[dkerber]

I run into the same problem, but never pursued it; I just use CPWI's slew control. I don't think I've tested it with the latest version, though.

[admin]

Send me the log file.

 

 

[astroman133]

I have no problem using BYE 3.2.0 telescope control (jogging, not slewing) with the ASCOM Simulator or with my Celestron CGEM using the Unified Celestron driver.

There are many capabilities of an ASCOM telescope driver that are optional. BYE does not know those capabilities until it has been connected to the driver. The capability of BYE when using the telescope jog direction buttons depends on the ASCOM driver supporting the optional capability of "MoveAxis". If the driver that you are using does not support MoveAxis calls at the rates specified by BYE then those buttons will be ineffective.

My Celestron mount allows MoveAxis calls to jog the mount at any speed up to 5 degrees/second. It works fine with BYE.

[admin]

Well, you claim using 3.2 in your post... but the log file you sent is 3.1.18. 

Quote

2020-09-28 23:52:30,317 [Main] INFO  - BackyardEOS 3.1.18.36628 started!
2020-09-28 23:52:30,340 [Main] INFO  - Built on 2019-12-22

 

[ventikappa]

5 hours ago, admin said:

Well, you claim using 3.2 in your post... but the log file you sent is 3.1.18. 

 

Then my post is incorrect. If you show me how to do I'll edit it.

Still, however, neither 3.1.8 nor 3.2 seem to support slewing.

[admin]

just to confirm, this is not slewing....it is telescope nudging... which uses the ASCOM MoveAxis command.

I need your 3.2 log file regardless. 

[ventikappa]

20 minutes ago, admin said:

just to confirm, this is not slewing....it is telescope nudging... which uses the ASCOM MoveAxis command.

I need your 3.2 log file regardless. 

20 minutes ago, admin said:

just to confirm, this is not slewing....it is telescope nudging... which uses the ASCOM MoveAxis command.

I need your 3.2 log file regardless. 

 

Bear with me: I'm not too familiar with terms.

As I told, it looks like 3.2 is not creating log. I'll do some more testing this evening or during the week-end.

[astroman133]

ventikappa,

BYE 3.2.0 does create logs. You may be looking in an old folder.

Before running BYE to create a log to show your slewing issue, delete the existing logs or move them to a different folder. Then you are sure that any logs in BackyardTEMP\Logs are new and for BYE 3.2.0.

Thanks!

 

[ventikappa]

On 10/2/2020 at 2:04 PM, admin said:

just to confirm, this is not slewing....it is telescope nudging... which uses the ASCOM MoveAxis command.

I need your 3.2 log file regardless. 

I managed to collect 3.2 logs. I'm attaching those here.

logfile-[20201004-22h27m15s812]-[9624]-2020-10-04.txt logfile-[20201004-22h30m40s763]-[2892]-2020-10-04.txt

[admin]

Are you 100% sure the mount does not move... it will be very subtle.

Also, is there is place in EQMOD to set the actual Epoch, yours is returning euqOther.

 

2020-10-04 22:32:31,811 [5] ERROR - Telescope Epoch equOther not supported.  Defaulting to JNOW
2020-10-04 22:32:31,851 [5] INFO  - Telescope EQMOD HEQ5/6 connected.
2020-10-04 22:32:31,851 [5] INFO  - +--- Epoch                : JNOW
2020-10-04 22:32:31,851 [5] INFO  - +--- RightAscension       : 11.5378463991761 : 11h32m16s
2020-10-04 22:32:31,851 [5] INFO  - +--- Declination          : 90 : 90°00'00"
2020-10-04 22:32:31,851 [5] INFO  - +--- Altitude             : 14.5833333133396 : 14°34'60"
2020-10-04 22:32:31,851 [5] INFO  - +--- Azimuth              : 1.88462201872186E-07 : 00°00'00"
2020-10-04 22:32:31,851 [5] INFO  - +--- SiteLongitude        : 120.95
2020-10-04 22:32:31,851 [5] INFO  - +--- SiteLatitude         : 14.5833333333333
2020-10-04 22:32:31,851 [5] INFO  - +--- SiteElevation        : 1000
2020-10-04 22:32:56,475 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2020-10-04 22:33:57,301 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2020-10-04 22:34:37,721 [Slew(Down)] INFO  - Telescope can move axis(axisSecondary), count(1)
2020-10-04 22:34:37,878 [Slew(Down)] INFO  -   Range[GetEnumerator](0, 3.34245933333333)
2020-10-04 22:34:37,878 [Slew(Down)] INFO  -   MinMax(0,3.34245933333333) => Rate(-0.334245933333333, -10%)
2020-10-04 22:34:52,658 [Main] DEBUG - IconPlus_MouseClick(iconMoveSouth = '')

[ventikappa]

Well, first movement is surely very evident and noticeable.

I need to double check about subsequent ones. However, the fact that it always shows "slewing" irrispectively of what I do is a bit odd.

However, for me to be able to do more tests I need to get my trial further extended: it's expiring today.

That said, you made me realize that the speed of the first movement doesn't seem to match the 10% rate that is shown. To explain what I mean, at the first command scope moves at a speed comparable with 2x in EQMOD control panel.

Edited October 6, 2020 by ventikappa

[astroman133]

To answer Guylain's question...Yes you can, and should, set the Epoch to JNOW in the EQASCOM driver's Setup dialog:

As you can see, it defaults to "EPOCH Unknown" which is probably why equOther is returned by the driver. That said, I do not know why the OP is having a problem jogging the mount. Looking at the EQASCOM Simulator, it supports rates of 0-3.34246 degrees/sec for both the primary and secondary axes.

Looking at the second log file (version 3.2.0.37080) previously supplied by ventikappa, the log file seems to end prematurely, supporting his description that telescope control stops after the initial jog is issued. Subsequent releasing the jog button does not seem to end the jog as it should. I ran the ASCOM driver conformance tool against the EQASCOM Simulator driver. The driver failed the testing with 3 errors and 2 issues. The 2 issues that were reported by Conform indicate that the driver behaves incorrectly when ending a move. That is when the BYE chevron button is released, the mount should return to its previous tracking state and set Slewing to false. The driver does not correctly restore the previous Tracking state when Tracking is off. I do not know if it correctly sets Slewing to false as this is not reported. I attached the Conform log file to a bug report with the EQMOD project. 

Since I do not have a Synta mount I could not test Conform against the real driver, only against the Simulator driver.

[admin]

I have just cancelled your trial.  Go ahead and add it again in your cart.

Please note, this is your 3rd trial and final one.

Regards,