Patrick Chevalley replied to the topic 'Live stacking methods?' in the forum. 2 days ago

Han, this look very good!

You can detect if the telescope as moved with the RA and DEC FITS keyword.
But it is necessary to compare with some tolerance because the mount driver can update the coordinates after pulse guide command.

This is probably the most universal way to deal with the problem. For example many people doing EAA use the telescope handpad to move the telescope and the imaging application is not aware of that.
But the most reliable is a Start/Stop button in the stacking application, so it not stack until the user finish to center the object and sometime focus manually.

Patrick

Read More...

Patrick Chevalley replied to the topic 'Live stacking methods?' in the forum. 4 days ago

Hi,

Han, this is good if you add this function to ASTAP.

From my experience in CCDciel, it work better with a simple addition of each new frame. This is because people doing EAA don't really fear about star saturation but want the faint nebulae level to increase as quickly as possible. When you divide by the number of frame, you keep the faint nebula level very low, as it was on a single image, just with less noise. Also 60 x 5 sec. do not saturate more than 1 x 300 sec.
But the best option is to do the stacking in 32bit floating point, then scale to 16bit for the display.

Maybe with ASTAP you can also try to keep every frame to redo the full stacking each time, in this case you can use sigma clipping to improve the result. If I understand correctly this is what AstroToaster do.
And as Jasem say this can also be used to preview the result of a standard sequence, not only for EAA.

At the moment CCDciel shift the image with a single star alignment before stacking. This work fine with unguided mount but not with alt/az mount. It is good if ASTAP can also apply a rotation but this imply that more than one star can be measured in the frame.

Patrick

Read More...

Patrick Chevalley replied to the topic 'How can I modify a driver?' in the forum. 3 months ago

Good!

Sorry to not reply to your last question but I am traveling and not always connected.
To clarify some points:
- RPi3 is 64bit hardware but most operating system are still 32bit so you need armhf packages.
- always delete the build directory if you want to start clean, otherwise cmake keep cache of previous files and not see the change in the environment.

Read More...

Patrick Chevalley replied to the topic 'How can I modify a driver?' in the forum. 3 months ago

Please remove this /usr/bin/cmake directory.

Then follow carefully all the steps in this page:
www.indilib.org/develop/developer-manual...ent-environment.html

cmake is installed part of the pre-requisit:
sudo apt-get install libnova-dev libcfitsio3-dev libusb-1.0-0-dev zlib1g-dev libgsl0-dev build-essential cmake git libjpeg-dev libcurl4-gnutls-dev kdesudo

And do not not copy files around, just follow the instruction.

Make sure the procedure to build and install Indi work, then edit the file you want and run "make install" again, this compile only the modified file and install the modified version ready for use.

Read More...

Patrick Chevalley replied to the topic 'How can I modify a driver?' in the forum. 3 months ago

The indi deb (indi-full and other) get installed in /usr

This is why you specify -DCMAKE_INSTALL_PREFIX=/usr in the cmake command. This way when you run "sudo make install" it install in /usr , overwriting the version installed by the deb. This is much better than having two install at different place.
Ekos will use your new compiled version without any other configuration.

Read More...

Patrick Chevalley replied to the topic 'How can I modify a driver?' in the forum. 3 months ago

You must replace ~/Projects/indi/libindi by the exact path where you install the indi source code. From your previous message it is projects in lowercase.

If you get other error message please copy the error text here.

Read More...

Patrick Chevalley replied to the topic 'How can I modify a driver?' in the forum. 3 months ago

OK, if you want to try to modify the driver all the documentation is here:
www.indilib.org/develop/developer-manual.html

Start by : www.indilib.org/develop/developer-manual...ent-environment.html
For such a simple change you can probably ignore the part about QtCreator but you can use it if you prefer.

To help to understand the driver :
www.indilib.org/develop/developer-manual...ver-development.html
If you want to add more messages to the log for debugging:
www.indilib.org/develop/developer-manual/160-debug-logging.html

As your driver is in libindi you only need to build this, no need to compile anything in 3rdparty to test the mount.

Patrick

Read More...

Patrick Chevalley replied to the topic 'How can I modify a driver?' in the forum. 3 months ago

Before to change the code you must be sure this is really required.

It is normal that N/S are reversed depending on the meridian side. Normally if you move the mount on the other side of the meridian you must find that N/S work normally.

Are you sure E/W is reversed ? Do it track in the right direction? Do the mount as a Northern/Southern hemisphere setting? Is your latitude configured right at every place?

Read More...

Patrick Chevalley replied to the topic 'Slew to Target never slews far enough' in the forum. 4 months ago

Maybe it is not necessary to change the default, this can be a bit disruptive for people that rely on this function.

I have added a note in the Eqmod documentation at the Alignment chapter:
www.indilib.org/devices/mounts/eqmod.html

Read More...

Patrick Chevalley replied to the topic 'update for INDI drivers for Raspberry Pi' in the forum. 4 months ago

The apt system (apt, dpkg, ...) do not know you install 1.7.9 because you not install it using a deb, so for apt indi is not installed.

The pacman applet probably launch the dpkg and apt command with options to process automatically all the package suggestion.
This can also be configured system wide in /etc/apt/apt.conf.d/ so the behavior can change depending on the distribution.

This is good for the end user, in this case if they install indistarter without indi, indi is first installed from the distribution repo, if later they change to the ppa indi is automatically updated to the last version.

This is something you must be careful when mixing install from source and from deb. It is better if you learn the few command line to install the deb and not use this pcaman or gdebi frontend that hide how it work.
This two command normally do the thing and give you exact message about what is done, the first install the deb you want, the second install the missing dependencies and finalize the deb install:
- dpkg -i indistarter*.deb
- apt install -f

The qhy driver and everything in 3rdparty must be compiled and installed separately. You must compile and install libqhy first. Or just compile and install all 3rdparty two time, the first time it fail to compile the driver but install the library, the second time it compile the driver.

Read More...

Patrick Chevalley replied to the topic 'EQMod problems' in the forum. 4 months ago

From your description it is possible this is the same problem as this one:
www.indilib.org/forum/mounts/4651-slew-t...ar-enough.html#35385

Read More...

Patrick Chevalley replied to the topic 'update for INDI drivers for Raspberry Pi' in the forum. 4 months ago

Han,

This is because indistarter package specify "Recommends: indi-bin" in the control file.

Normally this must not make the package to be installed automatically, but show a message about this recommendation. But sure INDI itself is a strong recommendation before you can use indistarter.
www.debian.org/doc/debian-policy/ch-relationships.html

If you downloaded the deb file, dpkg do not process the dependencies, you eventually have to run apt for that. Do you remember all the command you use to install?
If you do "apt install -f" after dpkg it may have installed indi-bin from the Raspbian repo, but normally it must not, only the "Depends:..." list must be processed automatically.

To remove this files do:
sudo apt remove indi-bin
sudo apt autoremove

Then run "make install" again from your libindi build directory.

Read More...

Patrick Chevalley replied to the topic 'update for INDI drivers for Raspberry Pi' in the forum. 4 months ago

Yes, this 1.7.5 lib must not harm because the 1.7.9 is in use with the links.

What is strange is in the lib you have :
_ZThn4768_N4INDI3CCD....
But the simulator want:
_ZThn4632_N4INDI3CCD....

I don't know enough about c++ mangled names to be sure why, but my intuition is it not use the same lib when linking the simulator.

Read More...