Looks like same issue as in this topic
www.indilib.org/forum/ccds-dslrs/3833-ca....html?start=36#62386
using ROI and 16bit broke down things.
Read More...
After quick smoke test on Linux worked just fine.
I wrote simple FITS viewer using cfitsio for myself and was also using toLocal8bit() and it was working fine even on windows.
Read More...
I have same problem. Recording with ASI1600 ROI in 16 bit mode result in just bunch of noise. Also the timestamps are all over the place like year 10000 and such. I am using ser-player to play back recorded files. But with some ROI sizes it seems like it can record properly. Like 500x500 it is recording fine but tanything smaller result in noise.
Read More...
I have issue opening FITS file if the path contain non Latin1 characters like ážť. Found out that changing toLocal8Bit() from toLatin1() fix this issue for me.
Providing patch file that should fix this issue
Read More...
Can you post which libraries are you missing? Only thing that I needed to compile from github is stellarsolver for Kstars. But INDI itself should compile without problem with just libraries from repository.
Read More...
I think all difference is that PixInsight move background more to the black so it looks better.
Read More...
No i could not reproduce it with simulators. Quite possible that this is some sort of race condition.
Read More...
Yes I am building it from sources regullary. This was from recent version c55c2c3a8.
Logs were set to verbose but only capture and focus module were selected.
Read More...
I did shared log in third post. First one doesn't start from beginning but both contain when meridian flip started. The guiding was running up until the meridian flip. Is there a way to test with simulators?
If you say that with scheduler it should be more consistent then I think I will start to use it.
Read More...
I am running raspbian and running tightvncserver. This run independently on main screen so it should be run multiple times.
systemd starting script /etc/systemd/system/vnc.service
[Unit]
Description=VNC server
After=graphical.target
[Service]
Type=forking
User=pi
WorkingDirectory=/home/pi
ExecStart=tightvncserver -geometry 1920x1080 :1
ExecStop=tightvncserver -kill :1
[Install]
WantedBy=default.targetRead More...
Well from logs it looks like it crash somewhere in guiding. I would try to use Ekos internal guider for a change. For power issue I think that is logged into kernel log. So try run "dmesg"
Read More...
