KStars-Bleeding and indiweb on Tinker Board S - with Armbian Bionic - by: jrsphoto

January 25, 2019, 11:08 pm

≫ Next: Cant download image - by: MCBUTTERBUNS

≪ Previous: More RTC madness!!!! - by: BrianH

I recently purchased an Asus Tinkerboard S computer for use as a portable telescope mounted computer. I've noticed others have had luck getting kstars / ekos working and I wanted to post my notes so others might benefit. First off, Armbian Bionic is the OS you want. So far its worked with minimal issues. Kstars installs but as of right now, there is a missing sql5 dependency and kstars won't start. This has been mentioned several times in these forums so I won't go into detail. You simple add the missing dependancy: and kstars will load as expected. For those wondering, the uname -a output looks as follows:

Indiweb:
Before you can install indiweb, you will need to install pip:
But wait... your not done. First you need to install some additional modules and libraries:

And the python dev libraries:

And finally, you can install indiweb:

As I find out other useful information about this config, I'll update this post. One thing I can say for sure, this thing is fast!

Cheers

John

↧

Cant download image - by: MCBUTTERBUNS

January 25, 2019, 10:07 pm

≫ Next: Raspbian INDI 1.7.6 - by: Frostlock

≪ Previous: KStars-Bleeding and indiweb on Tinker Board S - with Armbian Bionic - by: jrsphoto

Hi all,

I'm new to INDI so please forgive my ignorance. I'm having trouble imaging through KStars/Ekos and I hope I'm in the right place.

I'm running Astroberry on a RPI 3 and I'm able to get my guider, mount, and CCD to connect. The problem I'm having is that whenever I try to capture anything from my CCD, its always "Downloading" but I never see the image. I can get the Ekos to guide and I can get the mount to slew. I cannot figure out why an image never downloads.

My CCD is the Altair Hypercam 183M.

Does anyone have any idea what I'm doing wrong?

Thanks!

↧

Raspbian INDI 1.7.6 - by: Frostlock

January 26, 2019, 12:37 pm

≫ Next: indiserver exits when try indi_asi_ccd, indi_altair_ccd - by: kamisan

≪ Previous: Cant download image - by: MCBUTTERBUNS

Hi,
newbie here

I'm trying to use INDI to drive a Skywatcher AZ-GTi mount.
I have everything working on my ubuntu desktop (latest INDI version from the repo v1.7.6), also several helpful threads on this forum. In short: good stuff!

However I'm also trying to run the same thing on my raspberry (raspbian OS), here the INDI version is listed as v1.7.4.
Unfortunately I can't get the AZ-GTi to connect and reading the INDI device page for the AZ-GTi, I understand I need INDI > 1.7.5
So, question: Any idea when/if INDI 1.7.6 is coming to raspbian?

Cheers,

Frost

↧

indiserver exits when try indi_asi_ccd, indi_altair_ccd - by: kamisan

January 26, 2019, 4:25 pm

≫ Next: Hypercam 183 crashes - by: Astrocommando

≪ Previous: Raspbian INDI 1.7.6 - by: Frostlock

Newbie here, so I probably did something stupid.

I cloned the indi github repo and built it according to the directions in the Developer Manual:

mkdir -p ~/Projects/build/libindi
cd ~/Projects/build/libindi
cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Debug ~/Projects/indi/libindi
sudo make install

Everything works great except for cameras.
When I say everything I mean: indi_simulator_telescope, indi_simulator_ccd, and indi_simulator_wheel.
And more recently "real" devices like: indi_asi_wheel and indi_flipflat

BUT when I try indi_asi_ccd with my ASI120MC, I get errors and server exit.
And when I try indi_altair_ccd with my GPCAM2 290M, I also get errors but those are different messages from the ASI cam.

I will first list the errors from the ASI120MC and then the 290M.

indiserver -v indi_asi_ccd
2019-01-26T23:02:02: startup: indiserver -v indi_asi_ccd
2019-01-26T23:02:02: Driver indi_asi_ccd: pid=13542 rfd=3 wfd=6 efd=7
2019-01-26T23:02:02: listening to port 7624 on fd 4
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Focuser Simulator.ABS_ROTATOR_ANGLE
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on SQM.SKY_QUALITY
2019-01-26T23:02:02: Driver indi_asi_ccd: stderr EOF
Child process 13542 died
2019-01-26T23:02:02: Driver indi_asi_ccd: restart #1
2019-01-26T23:02:02: Driver indi_asi_ccd: pid=13545 rfd=0 wfd=6 efd=7
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Focuser Simulator.ABS_ROTATOR_ANGLE
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on SQM.SKY_QUALITY
2019-01-26T23:02:02: Driver indi_asi_ccd: stderr EOF
Child process 13545 died
2019-01-26T23:02:02: Driver indi_asi_ccd: restart #2
2019-01-26T23:02:02: Driver indi_asi_ccd: pid=13548 rfd=0 wfd=6 efd=7
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Focuser Simulator.ABS_ROTATOR_ANGLE
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on SQM.SKY_QUALITY
Child process 13548 died
2019-01-26T23:02:02: Driver indi_asi_ccd: stderr EOF
2019-01-26T23:02:02: Driver indi_asi_ccd: restart #3
2019-01-26T23:02:02: Driver indi_asi_ccd: pid=13551 rfd=0 wfd=6 efd=7
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Focuser Simulator.ABS_ROTATOR_ANGLE
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on SQM.SKY_QUALITY
Child process 13551 died
2019-01-26T23:02:02: Driver indi_asi_ccd: stderr EOF
2019-01-26T23:02:02: Driver indi_asi_ccd: restart #4
2019-01-26T23:02:02: Driver indi_asi_ccd: pid=13554 rfd=0 wfd=6 efd=7
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Focuser Simulator.ABS_ROTATOR_ANGLE
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on SQM.SKY_QUALITY
2019-01-26T23:02:02: Driver indi_asi_ccd: stderr EOF
Child process 13554 died
2019-01-26T23:02:02: Driver indi_asi_ccd: restart #5
2019-01-26T23:02:02: Driver indi_asi_ccd: pid=13557 rfd=0 wfd=6 efd=7
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Focuser Simulator.ABS_ROTATOR_ANGLE
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on SQM.SKY_QUALITY
2019-01-26T23:02:02: Driver indi_asi_ccd: stderr EOF
Child process 13557 died
2019-01-26T23:02:02: Driver indi_asi_ccd: restart #6
2019-01-26T23:02:02: Driver indi_asi_ccd: pid=13560 rfd=0 wfd=6 efd=7
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Focuser Simulator.ABS_ROTATOR_ANGLE
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on SQM.SKY_QUALITY
2019-01-26T23:02:02: Driver indi_asi_ccd: stderr EOF
Child process 13560 died
2019-01-26T23:02:02: Driver indi_asi_ccd: restart #7
2019-01-26T23:02:02: Driver indi_asi_ccd: pid=13563 rfd=0 wfd=6 efd=7
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Focuser Simulator.ABS_ROTATOR_ANGLE
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on SQM.SKY_QUALITY
2019-01-26T23:02:02: Driver indi_asi_ccd: stderr EOF
Child process 13563 died
2019-01-26T23:02:02: Driver indi_asi_ccd: restart #8
2019-01-26T23:02:02: Driver indi_asi_ccd: pid=13566 rfd=0 wfd=6 efd=7
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Focuser Simulator.ABS_ROTATOR_ANGLE
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on SQM.SKY_QUALITY
2019-01-26T23:02:02: Driver indi_asi_ccd: stderr EOF
Child process 13566 died
2019-01-26T23:02:02: Driver indi_asi_ccd: restart #9
2019-01-26T23:02:02: Driver indi_asi_ccd: pid=13569 rfd=0 wfd=6 efd=7
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Focuser Simulator.ABS_ROTATOR_ANGLE
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on SQM.SKY_QUALITY
Child process 13569 died
2019-01-26T23:02:02: Driver indi_asi_ccd: stderr EOF
2019-01-26T23:02:02: Driver indi_asi_ccd: restart #10
2019-01-26T23:02:02: Driver indi_asi_ccd: pid=13572 rfd=0 wfd=6 efd=7
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on Focuser Simulator.ABS_ROTATOR_ANGLE
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME
2019-01-26T23:02:02: Driver indi_asi_ccd: snooping on SQM.SKY_QUALITY
2019-01-26T23:02:02: Driver indi_asi_ccd: stderr EOF
Child process 13572 died
2019-01-26T23:02:02: Driver indi_asi_ccd: Terminated after #10 restarts.
2019-01-26T23:02:02: good bye

indiserver -v indi_altair_ccd
2019-01-26T23:07:47: startup: indiserver -v indi_altair_ccd
2019-01-26T23:07:47: Driver indi_altair_ccd: pid=13823 rfd=3 wfd=6 efd=7
2019-01-26T23:07:47: listening to port 7624 on fd 4
2019-01-26T23:07:47: Driver indi_altair_ccd: indi_altair_ccd: symbol lookup error: indi_altair_ccd: undefined symbol: Altaircam_put_ExpoAGain
Child process 13823 died
2019-01-26T23:07:47: Driver indi_altair_ccd: stderr EOF
2019-01-26T23:07:47: Driver indi_altair_ccd: restart #1
2019-01-26T23:07:47: Driver indi_altair_ccd: pid=13824 rfd=0 wfd=6 efd=7
2019-01-26T23:07:47: Driver indi_altair_ccd: indi_altair_ccd: symbol lookup error: indi_altair_ccd: undefined symbol: Altaircam_put_ExpoAGain
Child process 13824 died
2019-01-26T23:07:47: Driver indi_altair_ccd: stderr EOF
2019-01-26T23:07:47: Driver indi_altair_ccd: restart #2
2019-01-26T23:07:47: Driver indi_altair_ccd: pid=13825 rfd=0 wfd=6 efd=7
2019-01-26T23:07:47: Driver indi_altair_ccd: indi_altair_ccd: symbol lookup error: indi_altair_ccd: undefined symbol: Altaircam_put_ExpoAGain
Child process 13825 died
2019-01-26T23:07:47: Driver indi_altair_ccd: stderr EOF
2019-01-26T23:07:47: Driver indi_altair_ccd: restart #3
2019-01-26T23:07:47: Driver indi_altair_ccd: pid=13826 rfd=0 wfd=6 efd=7
2019-01-26T23:07:47: Driver indi_altair_ccd: indi_altair_ccd: symbol lookup error: indi_altair_ccd: undefined symbol: Altaircam_put_ExpoAGain
Child process 13826 died
2019-01-26T23:07:47: Driver indi_altair_ccd: stderr EOF
2019-01-26T23:07:47: Driver indi_altair_ccd: restart #4
2019-01-26T23:07:47: Driver indi_altair_ccd: pid=13827 rfd=0 wfd=6 efd=7
2019-01-26T23:07:47: Driver indi_altair_ccd: indi_altair_ccd: symbol lookup error: indi_altair_ccd: undefined symbol: Altaircam_put_ExpoAGain
Child process 13827 died
2019-01-26T23:07:47: Driver indi_altair_ccd: stderr EOF
2019-01-26T23:07:47: Driver indi_altair_ccd: restart #5
2019-01-26T23:07:47: Driver indi_altair_ccd: pid=13828 rfd=0 wfd=6 efd=7
2019-01-26T23:07:47: Driver indi_altair_ccd: indi_altair_ccd: symbol lookup error: indi_altair_ccd: undefined symbol: Altaircam_put_ExpoAGain
2019-01-26T23:07:47: Driver indi_altair_ccd: stderr EOF
Child process 13828 died
2019-01-26T23:07:47: Driver indi_altair_ccd: restart #6
2019-01-26T23:07:47: Driver indi_altair_ccd: pid=13829 rfd=0 wfd=6 efd=7
2019-01-26T23:07:47: Driver indi_altair_ccd: indi_altair_ccd: symbol lookup error: indi_altair_ccd: undefined symbol: Altaircam_put_ExpoAGain
2019-01-26T23:07:47: Driver indi_altair_ccd: stderr EOF
Child process 13829 died
2019-01-26T23:07:47: Driver indi_altair_ccd: restart #7
2019-01-26T23:07:47: Driver indi_altair_ccd: pid=13830 rfd=0 wfd=6 efd=7
2019-01-26T23:07:47: Driver indi_altair_ccd: indi_altair_ccd: symbol lookup error: indi_altair_ccd: undefined symbol: Altaircam_put_ExpoAGain
2019-01-26T23:07:47: Driver indi_altair_ccd: stderr EOF
Child process 13830 died
2019-01-26T23:07:47: Driver indi_altair_ccd: restart #8
2019-01-26T23:07:47: Driver indi_altair_ccd: pid=13831 rfd=0 wfd=6 efd=7
2019-01-26T23:07:47: Driver indi_altair_ccd: indi_altair_ccd: symbol lookup error: indi_altair_ccd: undefined symbol: Altaircam_put_ExpoAGain
2019-01-26T23:07:47: Driver indi_altair_ccd: stderr EOF
Child process 13831 died
2019-01-26T23:07:47: Driver indi_altair_ccd: restart #9
2019-01-26T23:07:47: Driver indi_altair_ccd: pid=13832 rfd=0 wfd=6 efd=7
2019-01-26T23:07:47: Driver indi_altair_ccd: indi_altair_ccd: symbol lookup error: indi_altair_ccd: undefined symbol: Altaircam_put_ExpoAGain
2019-01-26T23:07:47: Driver indi_altair_ccd: stderr EOF
Child process 13832 died
2019-01-26T23:07:47: Driver indi_altair_ccd: restart #10
2019-01-26T23:07:47: Driver indi_altair_ccd: pid=13833 rfd=0 wfd=6 efd=7
2019-01-26T23:07:47: Driver indi_altair_ccd: indi_altair_ccd: symbol lookup error: indi_altair_ccd: undefined symbol: Altaircam_put_ExpoAGain
2019-01-26T23:07:47: Driver indi_altair_ccd: stderr EOF
Child process 13833 died
2019-01-26T23:07:47: Driver indi_altair_ccd: Terminated after #10 restarts.
2019-01-26T23:07:47: good bye

Like I said it is probably something really stupid on my part. I apologize for the inconvenience.

Thank you!

↧

Hypercam 183 crashes - by: Astrocommando

January 26, 2019, 4:49 pm

≫ Next: Capture Module - Light, Dark, Bias, Flat Sequence - by: NH

≪ Previous: indiserver exits when try indi_asi_ccd, indi_altair_ccd - by: kamisan

I updated /upgraded the Altair drivers recently which got my GPCAM 1 working that I use for guiding. But the Hypercam 183 keeps crashing and still can't complete an exposure and it's getting annoying haha. Am I doing something wrong or is there something else I need to do? Could it be the firmware of the Hypercam?

↧

Capture Module - Light, Dark, Bias, Flat Sequence - by: NH

January 27, 2019, 3:22 am

≫ Next: Help adding a focuser device to KStars/Ekos for Windows dropdown - by: pwn3du

≪ Previous: Hypercam 183 crashes - by: Astrocommando

Hello everyone,

I am new here and a beginner in Astrophotography. I use StellarMate / KStars / Ekos and it is great.

Now I have a (perhaps stupid) Question (sorry for that). I did not found the answer in the tutorials or in the forum (sorry if it is there): If I click on "Preview" in the capture module and check "Auto Dark" then there is a warning that I should cover the telescope with a Dust Cap before contine. Ekos will only take the Dark after I put the Dust Cover on and click continue.

But if I create a sequence with first my Lights, then the Darks (with the calibration "Dust Cover with Build-in Flat Light" or "Manuell"), then the Bias (again with that calibration) and the Flats (with the calibration and a specific ADU for my DSLR) and then click on run, then there is no warning to cover the telescope etc. The sequence is simply running throught the whole process, that means the Lights, Darks, Bias and Flats are taken without any chance the put on the Dust Cover or the Flat-Light-Gernerator on my telescope. So the only chance is that I create a sequence for my Lights. Then make the Lights. Then put the Dust Cover on. Then create a sequence for the Darks and Bias (by the way is there an option that Ekos automatically takes the shortest possible exposure?). Then make the Darks and Bias. Then put the Flat-Light-Gernerator on. Then create a Flat-sequence. Then make the Flats.

As a conclusion I have to create three sequences. That is ok, but it would be more convenient if I could create one sequence with Lights, Darks, Bias and Flats and during the process there is a warning to put the Dust Cover on etc. and Ekos stops the taking frames until I click continue (like in the Preview mode). How can I activate this in Ekos?

THANK YOU VERY MUCH!!!

↧

Help adding a focuser device to KStars/Ekos for Windows dropdown - by: pwn3du

January 27, 2019, 6:47 am

≫ Next: Unable to install Kstars V3.0.0 - by: algady

≪ Previous: Capture Module - Light, Dark, Bias, Flat Sequence - by: NH

I've managed to build the Moonlite DRO INDI driver and get it working directly on my StellarMate, but I really want to control my setup through KStars on Windows remotely.

Where I'm stuck is I can't figure out how to get this device listed as a choice in the dropdown for focuser selection on Windows. I found an XML file that has a collection of names bound to their corresponding INDI drivers and I added it to that list, but it still doesn't show up after relaunching KStars.

How can configure KStars for Windows to look for/use the Moonlite DRO driver on the StellarMate?

P.S. There is a bug in the Moonlite DRO driver code related to the :GI# command that I had to fix up to get the driver working properly.

↧

Unable to install Kstars V3.0.0 - by: algady

January 27, 2019, 3:31 pm

≫ Next: Unable to compile astroberry-piface - by: eplumer

≪ Previous: Help adding a focuser device to KStars/Ekos for Windows dropdown - by: pwn3du

Hi all,
I 'm unable to install Kstars v3.0.0 on Ubuntu 18.10!
I followed this steps from this page: Kstars installation

The first and second commands finish ok, but the third line gives this error:

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
indi-full : Depends: indi-asi but it is not going to be installed
Depends: indi-toupcam but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Not sure what is the problen, Can anybody help please?

Thanks

↧

Unable to compile astroberry-piface - by: eplumer

January 27, 2019, 4:06 pm

≫ Next: 3D Printed Case for Piface - by: eplumer

≪ Previous: Unable to install Kstars V3.0.0 - by: algady

Got my PiFace Relay+ installed on a RPi 3B with ubuntu-mate xenial. I already have Kstars/Ekos/Indi running on the device. The "libindi1" package was up to date and I installed "libindi-dev".

I then ran the suggested build steps:

<code>git clone github.com/rkaczorek/astroberry-piface.git
cd astroberry-piface
mkdir build
cd build
cmake ..
make
make install</code>

The errors started on the "make install" step which gave the following trace:

<code>Performing update step for 'libmcp23s17'
Current branch master is up to date.
No stash found.
No stash found.
No stash found.
CMake Error at /home/edward/Tilion/astroberry-piface/build/libmcp23s17/tmp/libmcp23s17-gitupdate.cmake:136 (message):

Failed to unstash changes in:
'/home/edward/Tilion/astroberry-piface/libs/libmcp23s17/'.

You will have to resolve the conflicts manually

CMakeFiles/libmcp23s17.dir/build.make:94: recipe for target 'libmcp23s17/src/libmcp23s17-stamp/libmcp23s17-update' failed
make[2]: *** [libmcp23s17/src/libmcp23s17-stamp/libmcp23s17-update] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/libmcp23s17.dir/all' failed
make[1]: *** [CMakeFiles/libmcp23s17.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2</code>

Deleted the directory and repeated with same results. Is the build process doing local stashes? I made no explicit source changes or any git actions.

↧

3D Printed Case for Piface - by: eplumer

January 27, 2019, 4:44 pm

≫ Next: Basic Question about EKOS's focus settings - by: PK

≪ Previous: Unable to compile astroberry-piface - by: eplumer

After not finding a good option, I created my own 3D case designed for use with RPi and the two PiFace boards used for the Astroberry-Piface project. I also slipped in a PiFace RTC shim into the assembly. I have posted STL files for anyone interested on ThingiVerse at www.thingiverse.com/thing:3386245

↧

Basic Question about EKOS's focus settings - by: PK

January 28, 2019, 12:29 am

≫ Next: ScopeDome dome controller driver - by: jpaana

≪ Previous: 3D Printed Case for Piface - by: eplumer

I may have missed this in the documentation:
- When EKOS changes filters during an imaging session, will it reset the focus for each filter to the previously measured settings in the focus module?
I know that in the scheduler it will refocus between jobs, but in just the capture module will it change the focus to the last settings used?

Peter

↧

ScopeDome dome controller driver - by: jpaana

January 28, 2019, 3:00 am

≫ Next: "indi-web" command does not work anymore... - by: the.cakemaker

≪ Previous: Basic Question about EKOS's focus settings - by: PK

In case there are other ScopeDome users around, my driver has now been added to the main INDI repository and should appear in PPA in due time. It's included in the main tree and not under 3rd-party so no new packages to install. I'd prefer any feedback and feature requests in this one thread so feel welcome to add it here. The driver has so far only been tested with my own 2M dome with controller version 2.1 using two firmware versions (3.52 and 3.70) so any additional testing is good

Things that are missing (in semi-random order):
- initial dome calibration (steps per revolution, inertia table generation), need to use the Windows setup utility for that
- firmware update support, also need to use Windows software for that
- support for controller versions prior to 2.1
- roll-of-roof support, currently the driver probably has assumptions that it's driving a dome, though might work to some extent
- explicit support for 3M+ domes' requirement for shutter control only at home sensor position, normal parking and unparking should work if parking position is at the home sensor position, otherwise needs manually moving to home first
- support for negative home sensor signaling
- support for automatic closing of shutter directly via the controller, there is some preliminary UI elements for it, but they don't do anything yet, can be done with INDI's autopark mechanism for weather warnings
- support for adjusting heater parameters
- simulator support, there is a stub for that but it doesn't really do anything yet

↧

"indi-web" command does not work anymore... - by: the.cakemaker

January 28, 2019, 3:25 am

≫ Next: ASI 1600 is not capturing (preview is white screen), yet ASI 120mm capturing ok. - by: lemmu

≪ Previous: ScopeDome dome controller driver - by: jpaana

I always started with the command "indi-web" on my linux notebook which stays outside next to my mount connected to all my stuff. Then i connected via my iMac. For a long period of bad wheather i could not use the whole system for almost 2 months now.
Today i wanted to start setting all up again, but then i get this message...
Can someone please tell me where the fault is?

cheers
Niki

↧

ASI 1600 is not capturing (preview is white screen), yet ASI 120mm capturing ok. - by: lemmu

January 28, 2019, 4:42 am

≫ Next: guide star lost: scheduler does not recover - by: alacant

≪ Previous: "indi-web" command does not work anymore... - by: the.cakemaker

Hi,
I'm running Stellarmate on PI 3+. All my equipment is connected fine. For some reason I can't cet any images from 1600MM pro. Just blank white "image". Yet my guiding camera ASi 120 mm is 6working fine. Any ideas how to solve this? I did re-arrange ports and restarted, but nada...

↧

guide star lost: scheduler does not recover - by: alacant

January 28, 2019, 7:43 am

≫ Next: FITS Liberator vs KStars FITS Viewer - by: kamisan

≪ Previous: ASI 1600 is not capturing (preview is white screen), yet ASI 120mm capturing ok. - by: lemmu

Hi everyone
This occurs once per session **. The guide star is lost but the scheduler does nothing about it.
I have to intervene; I simply hit 'stop' in the ekos guide window, another guide star is selected and imaging continues.
Would it e possible for the scheduler to recover without manual intervention?
Cheers,
Steve
**Happens here around 22:18:
logs: drive.google.com/open?id=1y-VOi45tdKfb55yxdUzZZJziqQ4q9I-l

Copy sent to Andy at PHD2

↧

FITS Liberator vs KStars FITS Viewer - by: kamisan

January 28, 2019, 8:17 am

≫ Next: Multiple USB Serial Devices (FTDIs and such) - by: dcpontius

≪ Previous: guide star lost: scheduler does not recover - by: alacant

Using Altair 290M camera and INDI Control Panel, I captured a bias frame using Gain 200 (quite low) and Exposure of 10ms.

Attached are side-by-side comparison of the FITS Viewer histogram and FITS Liberator. There are significant differences.

↧

Multiple USB Serial Devices (FTDIs and such) - by: dcpontius

January 28, 2019, 8:20 am

≫ Next: No control over OFFSET for Altair 290M - by: kamisan

≪ Previous: FITS Liberator vs KStars FITS Viewer - by: kamisan

As I continue to build out my observatory and add devices, I'm getting swamped by all the gadgets that use FTDI serial devices (or something equivalent) yielding an arbitrary "ttyUSB??" device assignment. I know how to use udev in Linux to create symlinks by serial number (which many do not have) or by physical port number, but is there a way to tell the various INDI drivers to look at a specific device name (/dev/focuser, for example, being a symlink to ttyUSB2)? Or is there some other way to disambiguate these devices so that everything works properly? My workaround is to add more Pi's, NUC's, etc. for these gadgets, and that just gets old, and somewhat klunky!

↧

No control over OFFSET for Altair 290M - by: kamisan

January 28, 2019, 8:31 am

≫ Next: Park mount after failed meridian flip and hangup during imaging sequence - by: El Corazon

≪ Previous: Multiple USB Serial Devices (FTDIs and such) - by: dcpontius

I am setting up for my first outing with Ekos.

In INDI Control Panel I cannot find any control called Offset. There is 'brightness' and 'black level' but I tried these and I discovered that neither of them affects the offset of the histogram of a bias frame.
It is possible, I would imagine, that this control has fallen through the cracks since INDI support for Altair cameras is relatively new. Perhaps a constant value is being set. Thankfully that value is perfectly fine for AP using Gain 200 but as you can see in the attached screenshots that the histogram of Gain 3000 is being clipped on the left-hand-side of the histogram. Although I don't image at such a high gain it would be nice, for the sake of completeness, to have control over Offset.

For CMOS cameras it is important to get the Offset setting right. Thankfully Offset is simply a function of Gain. From past experience with SharpCap I have determined that Offset 30 should be used with Gain 200. Also, as Gain is increased Offset should also be increased. I've determined all of these Offset values ahead of time using SharpCap.

Thank you.

↧

Park mount after failed meridian flip and hangup during imaging sequence - by: El Corazon

January 28, 2019, 9:14 am

≫ Next: ISSUE WITH MY CANON 450D - by: astro31

≪ Previous: No control over OFFSET for Altair 290M - by: kamisan

It does not happen often, but when it does, it is distressing: The scheduler is humming along, everything is working great, but then the meridian flip fails.
At that point, Ekos gives up, but unfortunately, the mount doesn't. It continues to track until it wraps the telescope around the pier or the tripod legs.

That happened to me again the other night. I wonder whether it would be possible to instruct the mount to park itself, if 2 retries at the meridian flip fail, and then restart the imaging schedule from there.

Another idiosyncracy: When I image a sequence manually including guiding, but then want to stop that sequence and start the scheduler for the rest of the night, the scheduler starts fine, will command focus, plate solve and align, but then it will hang when it is supposed to start the imaging sequence again. All it says is "Waiting".....

There is no way to get out of this without restarting Ekos.

↧

ISSUE WITH MY CANON 450D - by: astro31

December 19, 2018, 10:28 am

≫ Next: Help Required! Polar Alignment Experiment - by: knro

≪ Previous: Park mount after failed meridian flip and hangup during imaging sequence - by: El Corazon

Hi ,

I have an issue with my Canon 450D DSLR connected to my Raspberry PI 3 with Stellarmate .

The PI doesn't find the DSLR , it worked before ? i try to replace the USB cable , initialization of the canon , BUBL, etc ... but with out success , my QHY5 is find ?? any ideas ?

thank for your help

Richard

↧