Martin Gleim replied to the topic 'CEM40 usb drops connection' in the forum. 6 months ago

Hi, I had a similar problem. First the CEM 40 worked flawlessly with raspi and stellarmate. It was about a year ago. I had months of cloudy nights, few clear skies. One clear night the CEM 40 was not seen by the raspi 4, In the meantime I had updated the firmware of the CEM, had another kstars version etc. First I downgraded the firmware of the CEM, installed older kstars and indi versions, tested legions of usb cables. I have another pi..... tried 3 different power-supplies, other computers. Result: raspi 4 with raspbian sees the CEM, Windows computer with ascom sees the CEM, raspi with stellarmate doesnt see the CEM, Mac sees the CEM. With help of Jasem Mutlaq I tried some kind of debugging, prduced endless protocoll files but no new findings... One day I placed an old powered usb - hub between raspi and CEM: It works.[/strike]


Hi, my procedure is similar to the others: I make a fits picture exactly with the section I want. Be sure that the fits contains the coordinates of the section, i.e. you have prior to activate WCS in the indi control panel for your telescope. Then save the Fits. Then in the solver tab: load and solve....


Martin Gleim created a new topic ' Mac crash kstars' in the forum. 1 year ago

I am using a macbook pro with intel processor. Kstars runs on the macbook (3.5.4), on a raspi ekos. Each session I have several crashs of kstars. I cannot identify any special situation or procedure that leads to the crash, but some jobs are prone to crashes: platesolving, focussing, starting a series of long-time exposure eg. 300secs. I had no crash when doing flats or darks the next day. I had no crash related to guiding or moving the mount (goto an aim or searching the sky).
Running kstars on the raspi over vpn never produced a crash.
There a 2 types of crashprotocols:Crashed Thread:        0  Dispatch queue:
Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY
Application Specific Information:
terminating with uncaught exception of type std::__1::system_error: mutex lock failed: Invalid argument

Crashed Thread:        0  Dispatch queue:
Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       EXC_I386_GPFLT
Exception Note:        EXC_CORPSE_NOTIFY
Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [2922]

.Seeing through the saved protocols I found that  >>Exception Type:        EXC_CRASH (SIGABRT)<<  only occurres once a day/session while  >>Exception Type:        EXC_BAD_ACCESS (SIGSEGV)<<  comes several times. 
I don't coding and cannot interprete the crash-report. The folder where kstars should save reports is mainly empty, last entry is a half year ago (extensive protocolling has been checked).
Perhaps I can help to avoid these annoying crash.