Last night I had to position my mount slightly further away from the house which meant that my wifi connection from my laptop running Kstars and INDI on the Pi was not strong.
I lost connection a few times and focussing was impossible (too long required for the download).
I had an old Airport Express (mini router/Access point) which I have now connected directly to the Pi with a cable. Seems to have solved my wireless woes.
I think the Pi wireless access point is very weak and only really seems to work if you are within a couple of metres.
Read More...
Hi Stephan
Once you have done the initial setup all focussing and guiding is driven from the front end app (Kstars).
You can run Kstars either from a remote system or directly on the Pi.
I let INDI run on the Pi and run Kstars from a laptop. If you are using this setup make sure connection between your laptop/PC and the Pi is a strong one. You do not want to be loosing connections or have a slow connection. A slow connection is a real killer for Focus and Guiding. I guess you could run Kstars on the the Pi for Focus and Guiding but that is a little too complex for me.
Read More...
I have taken the plunge and replaced my Pi3 with the Pi 4.
All seems to work well with HEQ5, 294MC, 224MC and Pegasus PPB.
One question I have is should the Update button in the StallaMate dashboard work?
Mine runs the percentage usual goes to about 3% then I get a message saying the update was successful but the update icon remains red with a little red exclamation mark next to it.
Read More...
Try "sudo chmod -R 776 *"
Make sure you are in the /Pictures directory before executing this command.
Read More...
I have switched to the Simulator to try and get this working.
Now the UI is no longer greyed out (I assume because I did not have my mount attached it was greyed out) and I can start a ASTAP solve but I always get "Solver Failed. Try again".
Is there anything I need to do in ASTAP to get it setup?
2019-11-10T09:50:15 Solver failed. Try again.
2019-11-10T09:50:09 /Applications/ASTAP.app/Contents/MacOS/astap -O --no-plots --no-verify --resort --downsample 2 -L 20.339 -H 25.424 -u aw -3 23.7958 -4 30.7606 -5 30 -f /private/var/folders/kg/s3p7zt0x11z16l_jcq1s8vmr0000gn/T/fitsXptWhn.fits -o /private/var/folders/kg/s3p7zt0x11z16l_jcq1s8vmr0000gn/T/solution
2019-11-10T09:50:09 Starting solver...
2019-11-10T09:50:09 Solver iteration #1
2019-11-10T09:50:09 Image received.
2019-11-10T09:50:05 Capturing image...
Read More...
I just updated to 3.3.7 on OSX.
I had the solver setup but now it seems I have to set it up again. I have installed the ASTAP software and set the correct path in the Solver option menu but the Solver page remains inactive (grayed out).
What steps should I be taking to get it setup?
Read More...
I have been viewing the images from within PI. They were not yet debayered.
I though PI displayed images as gray scale until they are debayered?
Is that the tram line effect I am seeing? Only the red pixels.
Read More...
As usual it turned out to be user error.
Out of the box the driver has the format set to 8 bit (which is I assume to improve the frame rate for lucky imaging).
Once I set it to 16 bit my darks looked normal.
Read More...
As usual it turned out to be user error.
Out of the box the driver has the format set to 8 bit (which is I assume to improve the frame rate for lucky imaging).
Once I set it to 16 bit my darks looked normal.
Read More...
Thanks. That was it! It was still set to 8 bit which I guess is the default to improve frame rate.
Very happy to have this solved. Now I can start collecting data again.
Read More...
I have been using the default (for Indi) offset value of 8 for all my frames.
I am also using the unity level of gain (120).
I am not using any bias frames but Flat Darks. My flats are 4 seconds to avoid short exposures.
The Indi driver does have some settings I don't completely understand.
Default the Format is set to 8 bits with RGB, 16 bit and Luma as options. If I set it to 16 bit my darks immediately look much better. I would have expected 16 bit to be the default unless I was trying to get a high FPS?
Read More...
Hi All
I started a new thread because I am now a step further.
I cannot take good Darks using the Indi driver via Ekos. They show no randomness and do not display the amp glow. We noticed a checkerboard pattern, this doesn't look random, all the "lanes" have the same value, and the black pixels exactly half of that.
Maybe its a setting (I am using the defaults) but I cannot get it right.
So I decided to install APT and use ASCOM to connect. The Darks I get via APT are exactly as I would expect. I can clearly see the amp glow and star burst pattern.
Any idea's why the INDI driver behaves so differently from the Ascom?
I have 2 samples on dropbox which I can share to illustrate what I mean. The examples have both been stretched the same amount using the STF function in PixInsight.
Read More...