John Pane replied to the topic 'New Meridian Flip Issue' in the forum. 7 months ago

We're at the limits of my knowledge. I don't know if Ekos and the mount communicate regarding geographic position. I can imagine a scenario where they could properly sync on a target without agreeing on the geographic position of the mount, and thus when the meridian flip is necessary.

Looking at the manual, I see that the EQ6-R does not have a GPS. "At the end of the initialization of the SynScan hand control, after entering the proper local longitude, latitude". If you did not do this at least once after receiving the mount back perhaps it doesn't have the right coordinates?

Read More...

John Pane replied to the topic 'New Meridian Flip Issue' in the forum. 7 months ago

Is that consistent with the hour angles reported in the log?

[2022-01-07T22:18:15.321 EST DEBG ][ org.kde.kstars.ekos.mount] - Meridian flip planned with LST= "05h 14m 20s" scope RA= "05h 08m 19s" ha= 0.10045 , meridian diff= 0.1 , hrstoFlip= -0.000449513 , flipDelayHrs= 0 , "Pier Side: West (pointing East)"
[2022-01-07T22:19:13.536 EST INFO ][ org.kde.kstars.ekos.mount] - Meridian flip: slewing to RA= "05h 08m 02s" DEC= "-03° 18' 47\"" Hour Angle "00h 00m 29s"
[2022-01-07T22:19:31.942 EST DEBG ][ org.kde.kstars.ekos.mount] - Meridian flip planned with LST= "05h 15m 37s" scope RA= "05h 08m 02s" ha= 0.126487 , meridian diff= 0.1 , hrstoFlip= -0.0264867 , flipDelayHrs= 0 , "Pier Side: West (pointing East)"
[2022-01-07T22:19:32.929 EST INFO ][ org.kde.kstars.ekos.mount] - Meridian flip: slewing to RA= "05h 08m 02s" DEC= "-03° 18' 47\"" Hour Angle "00h 00m 30s"
[2022-01-07T22:35:12.340 EST DEBG ][ org.kde.kstars.ekos.mount] - Meridian flip planned with LST= "05h 31m 20s" scope RA= "05h 19m 44s" ha= 0.1935 , meridian diff= 0.1 , hrstoFlip= -1.89019e-05 , flipDelayHrs= 0.093481 , "Pier Side: West (pointing East)"
[2022-01-07T22:38:04.617 EST INFO ][ org.kde.kstars.ekos.mount] - Meridian flip: slewing to RA= "05h 08m 03s" DEC= "-03° 18' 47\"" Hour Angle "00h 01m 45s"

(Were the mount and Ekos in agreement on the geographic location of the mount?)

Read More...

John Pane replied to the topic 'New Meridian Flip Issue' in the forum. 7 months ago

My guess is that you hadn't yet tracked far enough past the meridian for the mount to switch to the east side when it received a goto command from Ekos.

Read More...

I removed the astrometry driver from my equipment profile. Curiously, it was still showing up when I started Ekos. I had to reboot the Stellarmate to have this change take effect.

After the remote astrometry drive was removed, Ekos no longer offers the astrometry tab unless the camera is present. When the camera is present, the four-click sequence does not crash.

Nonetheless, it would be good if KStars did not crash in the situation of my original configuration.


 

Read More...

Thank you for your reply.

The astrometry driver is a legacy of my original setup. I didi not think to remove it but will do so.

The camera is not showing up because it is unplugged when my scope is in the garage. Of course a camera is necessary to solve, but KStars shouldn't crash if one isn't available.

I do not have log files to offer, but if you are unable to reproduce the crash just let me know what you need and I'll get them for you.

Read More...

The four-click crash that I reported here is still present in your beta.

John
 

Read More...

I have a ZWO ASI6200MC camera. For a recent image, the FITS file contained an astrometric solution and also notes that the data are to be interpreted top-down. FITS header excerpt:

ROWORDER= 'TOP-DOWN'           / Row Order
RA      =         2.336768E+01 / Object J2000 RA in Degrees                     
DEC     =         3.063624E+01 / Object J2000 DEC in Degrees                       
CROTA1  =     2.4249720376E+02 / CROTA1                                         
CROTA2  =     2.4249720376E+02 / CROTA2                                         
This implies a camera rotation of 360-242 = -118 degrees. In fact, this is what PixInsight reports when it reads in the image.

Later, when I plate solve using PixInsight, I get a rotation angle of -62 degrees. -118 + -62 = -180 degrees (mirrored vertically).

Is Ekos recording the astrometric solution as if the image is written bottom-up instead of top-down?

Thanks,
John
 

Read More...

Please see screen recording . Excerpt from crash report below.

Kstars 3.5.5. Build: 2021-09-15T21:27:44Z



Translated Report (Full Report Below)

Process:               kstars [76741]
Path:                  /Applications/KStars.app/Contents/MacOS/kstars
Identifier:            
Version:               3.5.5 (3.5.5)
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
User ID:               502

Date/Time:             2021-11-05 05:54:45.2272 -0400
OS Version:            macOS 12.0.1 (21A559)
Report Version:        12
Bridge OS Version:     6.0 (19P548)
Anonymous UUID:        25CD5339-DD65-AE76-4CFE-E4523542801F


Time Awake Since Boot: 570000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000028
Exception Codes:       0x0000000000000001, 0x0000000000000028
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [76741]

VM Region Info: 0x28 is not in any region.  Bytes before following region: 4429221848
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->  
      __TEXT                      108009000-108da1000    [ 13.6M] r-x/r-x SM=COW  .../MacOS/kstars

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   kstars                                   0x10815d3f2 0x108009000 + 1393650
1   QtCore                                   0x10c7b80f2 0x10c5a6000 + 2171122
2   QtWidgets                                0x10c1dc86f 0x10bffd000 + 1964143
3   QtCore                                   0x10c7b8232 0x10c5a6000 + 2171442
4   QtWidgets                                0x10c1bd566 QTabBar::setCurrentIndex(int) + 406
5   QtWidgets                                0x10c1c1dff QTabBar::mousePressEvent(QMouseEvent*) + 703
6   QtWidgets                                0x10c0475b5 QWidget::event(QEvent*) + 421
7   QtWidgets                                0x10c1bfb42 QTabBar::event(QEvent*) + 130
8   QtWidgets                                0x10c00e746 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 262
9   QtWidgets                                0x10c01142a QApplication::notify(QObject*, QEvent*) + 6922
10  QtCore                                   0x10c787a16 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 166
11  QtWidgets                                0x10c00f052 QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) + 898
12  QtWidgets                                0x10c066242 0x10bffd000 + 430658
13  QtWidgets                                0x10c06495e 0x10bffd000 + 424286
14  QtWidgets                                0x10c00e746 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 262
15  QtWidgets                                0x10c00fafd QApplication::notify(QObject*, QEvent*) + 477
16  QtCore                                   0x10c787a16 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 166
17  QtGui                                    0x10cbb1227 QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) + 3543
18  QtGui                                    0x10cb96cdb QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 203
19  libqcocoa.dylib                          0x10f416768 0x10f3db000 + 243560
20  CoreFoundation                        0x7ff8021bb84d __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
21  CoreFoundation                        0x7ff8021bb7b5 __CFRunLoopDoSource0 + 180
22  CoreFoundation                        0x7ff8021bb534 __CFRunLoopDoSources0 + 242
23  CoreFoundation                        0x7ff8021b9f6b __CFRunLoopRun + 893
24  CoreFoundation                        0x7ff8021b952d CFRunLoopRunSpecific + 563
25  HIToolbox                             0x7ff80add73e1 RunCurrentEventLoopInMode + 292
26  HIToolbox                             0x7ff80add7008 ReceiveNextEventCommon + 284
27  HIToolbox                             0x7ff80add6ed5 _BlockUntilNextEventMatchingListInModeWithFilter + 70
28  AppKit                                0x7ff804be48f0 _DPSNextEvent + 886
29  AppKit                                0x7ff804be2f5c -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1411
30  AppKit                                0x7ff804bd5359 -[NSApplication run] + 586
31  libqcocoa.dylib                          0x10f415414 0x10f3db000 + 238612
32  QtCore                                   0x10c7840d7 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 471
33  QtCore                                   0x10c787fb2 QCoreApplication::exec() + 130
34  kstars                                   0x1080217c2 0x108009000 + 100290
35  dyld                                     0x10abdb4fe start + 462
Translated Report (Full Report Below)

Process:               kstars [76741]
Path:                  /Applications/KStars.app/Contents/MacOS/kstars
Identifier:            
Version:               3.5.5 (3.5.5)
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
User ID:               502

Date/Time:             2021-11-05 05:54:45.2272 -0400
OS Version:            macOS 12.0.1 (21A559)
Report Version:        12
Bridge OS Version:     6.0 (19P548)
Anonymous UUID:        25CD5339-DD65-AE76-4CFE-E4523542801F


Time Awake Since Boot: 570000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000028
Exception Codes:       0x0000000000000001, 0x0000000000000028
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [76741]

VM Region Info: 0x28 is not in any region.  Bytes before following region: 4429221848
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->  
      __TEXT                      108009000-108da1000    [ 13.6M] r-x/r-x SM=COW  .../MacOS/kstars

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   kstars                                   0x10815d3f2 0x108009000 + 1393650
1   QtCore                                   0x10c7b80f2 0x10c5a6000 + 2171122
2   QtWidgets                                0x10c1dc86f 0x10bffd000 + 1964143
3   QtCore                                   0x10c7b8232 0x10c5a6000 + 2171442
4   QtWidgets                                0x10c1bd566 QTabBar::setCurrentIndex(int) + 406
5   QtWidgets                                0x10c1c1dff QTabBar::mousePressEvent(QMouseEvent*) + 703
6   QtWidgets                                0x10c0475b5 QWidget::event(QEvent*) + 421
7   QtWidgets                                0x10c1bfb42 QTabBar::event(QEvent*) + 130
8   QtWidgets                                0x10c00e746 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 262
9   QtWidgets                                0x10c01142a QApplication::notify(QObject*, QEvent*) + 6922
10  QtCore                                   0x10c787a16 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 166
11  QtWidgets                                0x10c00f052 QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) + 898
12  QtWidgets                                0x10c066242 0x10bffd000 + 430658
13  QtWidgets                                0x10c06495e 0x10bffd000 + 424286
14  QtWidgets                                0x10c00e746 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 262
15  QtWidgets                                0x10c00fafd QApplication::notify(QObject*, QEvent*) + 477
16  QtCore                                   0x10c787a16 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 166
17  QtGui                                    0x10cbb1227 QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) + 3543
18  QtGui                                    0x10cb96cdb QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 203
19  libqcocoa.dylib                          0x10f416768 0x10f3db000 + 243560
20  CoreFoundation                        0x7ff8021bb84d __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
21  CoreFoundation                        0x7ff8021bb7b5 __CFRunLoopDoSource0 + 180
22  CoreFoundation                        0x7ff8021bb534 __CFRunLoopDoSources0 + 242
23  CoreFoundation                        0x7ff8021b9f6b __CFRunLoopRun + 893
24  CoreFoundation                        0x7ff8021b952d CFRunLoopRunSpecific + 563
25  HIToolbox                             0x7ff80add73e1 RunCurrentEventLoopInMode + 292
26  HIToolbox                             0x7ff80add7008 ReceiveNextEventCommon + 284
27  HIToolbox                             0x7ff80add6ed5 _BlockUntilNextEventMatchingListInModeWithFilter + 70
28  AppKit                                0x7ff804be48f0 _DPSNextEvent + 886
29  AppKit                                0x7ff804be2f5c -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1411
30  AppKit                                0x7ff804bd5359 -[NSApplication run] + 586
31  libqcocoa.dylib                          0x10f415414 0x10f3db000 + 238612
32  QtCore                                   0x10c7840d7 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 471
33  QtCore                                   0x10c787fb2 QCoreApplication::exec() + 130
34  kstars                                   0x1080217c2 0x108009000 + 100290
35  dyld                                     0x10abdb4fe start + 462

 

Read More...

That sounds great, thank you. It sounds like that will be perfect. I will anxiously await the updated new version.

Read More...

Hello Jasem,

Are the streaming properties available via the Stellarmate Android app?

I set up my mount for every session, and its polar alignment routine requires me to see live view through the OTA while standing at the scope. Currently I use a Canon DSLR and can view the image on the back of the camera. But I am considering purchasing a dedicated astro camera that does not offer this. It is a very expensive purchase, so I am trying to make sure I will be able to see the live image for polar alignment.

I did some testing with my current DSLR and the app, and can get a sufficient frame rate. However, I do not know whether this will be true for the new camera without adjusting the streaming properties.

If I cannot use the app, I guess my solution may be to carry my laptop out there for the alignment.

In either case, it would be extremely helpful to be able to superimpose a crosshair at image center over the live view. Is that possible?

Thank you,
John

Read More...