Hello,

trying to protect my observatory, I am tryning to use the weather shutdown procedure but without success.. The scheduler is runing even if wheater condition are not OK. I am using "OpenWeatherMap" as web site to get the weather conditions. The site is connected anf wheather condition are accessible. Any idea why the scheduler is not runing the shutdown procedure ...?

Have a clear night...
JC

Read More...

Hi,

Juste to inform that with with KStar 3.6.0, this working much better !

Wishing you nights cloudless...

JC

Read More...

Thank you Bryan !

I tried with succes the update this week !
My setup did change since 3 years... I was forgeting how it is simple to up-date KStart. Thanks again ...

Wishing you nights without cloud !

JC

Read More...

Hello,

I tried to update KSTARS/EKOs on my Raspberry 3B+ since two weeks, (due to to the fact that the scheduler stay in idle when I start it through python script on my actual release ) The problem is that after sending the command"sudo apt install indi-full kstars-bleeding", when I try to run Kstar, I get the "hour glass arrow" then nothing...

Is this due to the Buster release or Raspberry 3B+ release ?

Have good night.
JC

Read More...

Hello,

2 year after this discussion I tried to start and stop the scheduler with the ekos_controller.py script still without success as Sean ( The scheduler is starting but there is no progress on the job ). Is there still no progress on this topics ?

Best regards.
JC

Read More...

For your info, I get the same issue. Need to create a new profile to enter the API key...before entering this key the driver is crashing.

JC

Read More...

one more time...JC

Read More...

Hi mark,

I have reinstalled the last release ofEKOS and effectively, it crash... So I recompile again the indi_qhy_ccd and it works... I send you in attachment the new driver and also the QHY8.HEX file .indi_qhy_ccd have to take place in /usr/bin directory ( using UNIX command cp  and rm  with"sudo" in prefix  ) qhy8.hex in /lib/firmware/qhy directory.Let me know if it works.best regards.JCHi mark,I have reinstalled the last release ofEKOS and effectively, it crash... So I recompile again the indi_qhy_ccd and it works...

I send you in attachment the new driver indi_qhy_ccd and also the QHY8.HEX file.

indi_qhy_ccd have to take place in /usr/bin directory ( using UNIX command cp  and rm  with"sudo" in prefix  ) and before...,  rename the file indi_qhy_ccd.log in indi_qhy_ccd ( remove the log extention set for contouning the fire wall) 

QHY8.HEX in /lib/firmware/qhy directory. ( rename the QHY8.log in QHY8.HEX , remove the log extention  and put .HEX, log extention set for contouning also the fire wall ....)take care about the case.. you are in the UNIX world.Let me know if it works.best regards.JC

Read More...

Hi Mark,Sorry for the delay... here is the last release done for this driver hopping it will be compatible with your release of Astroberry. before putting the file in the usr/bin diretory, remove the .log extention thta I was abliged to add to pass the firewall. Tell me if it is not working  

HI,

Just to modulate Hank, with Astroberry, I never succed to use the 1x1 bin . The image is never opened with the imager .... In 2x2 seems OK.

JC

Read More...

Hi Hank, sorry for my very late replay. Concerning the stability of the Astroberry set, I am thinking that the system have to be given for any set running well. Personnaly I get a Rpi3+ with 16Go that perharps is not enough, and the first feeling thta I get is a lot of adjustement to be done not to get crash of theINDI server.
Actualy, the best that I get is a 60 pictures in one sequence done without crash. When I try to restart the sequence, after some shoot the Indi crash...I have aslo notice that using ASTAP before a sequence, is if the solver failed some times, crash of the Indi sever is also frequent..


Perharps on windows the Indi systeme is more robust.. I didn't not try and will be of course interreseted to have your feed back on this setup.

Regards.
JC

Read More...

Small correction...40 acquisitions...

Read More...

Hi just found apparently in the FITS/Configurer - KSTAR the solution... When I made trial, I discovered a veery strange behaviour of the FITS image, there were zooming every time a acquistion was occuring...Exepted when I set the bining in4X4... At the same times, I have seen that in the FITS/Configurer - KSTAR, one option called "Adaptive Sampling " is used when the ressource of the system is reducing. So I uncheck this option and... no more crash over 50 acquisition ( 10R/10B/10G/10L)... Hoping this is the solution up to the next bug...

Best regards.
JC

Read More...