Paul replied to the topic 'Too much focusing going on.' in the forum. 1 month ago

John,

From the above
1. On startup the system ensures focus by focusing on Ha. Correct.
2. The next step is alignment. If you set Align to L then the L filter will be swapped in. Correct.
3. As you have Autofocus on filter change set, Focus will Autofocus on L. Incorrect - I do not want this and it does not happen.
4. Align then runs, when complete Ha is swapped back. Correct.
5. As you have Autofocus on filter change set for Ha then Focus will Autofocus. Happens but is not required.
6. Sequence starts on Ha. Correct.

I don't use offsets as the focus position is not always reproducable. I don't want or need a focus on L as it is okay for alignment without a refocus. I cannot align using Ha.
I effectively only want alignment for imaging not alignment.

Paul

Read More...

Paul created a new topic ' Too much focusing going on.' in the forum. 1 month ago

I have an issue that i want to focus with my Ha filter but align using the L filter.
I have the software set to focus on a filter change and after 120 minutes.
When I use the scheduler it performs a focus run using the Ha filter and then aligns using the L filter, but because I have refocus on filter change set, it will then perform a second focus run using the Ha filter. If it fails to align it can go through the same process multiple times.
As the filter used for focusing has not changed it is not required to keep doing this but I cannot see a way of stopping it.
Any suggestions would be appreciated.

Paul

Read More...

Luke,

I don't think what you are trying to do is possible, it would require too many amps to operate the motor, that is why you have a controller inbetween. I use an Arduino Uno with a motor controller hat.

Paul

Read More...

Chris,

The bit I don't understand is "wait for a satellite to cross through this field of view" because the Earth is turning and the telescope needs to track to keep the same field of view.

Paul

Read More...

Chris,

Chris,

If I read your email correctly, you want to slew to an object so that you can wait for a satellite to cross the path.

I think you would still want to track under these circumstances.

The only reason I can think of to turn off tracking is to time an object crossing the field of view but maybe I am missing something.

Paul

Read More...

This was a brand new install for testing on bookworm on a Raspberry Pi 5.

Paul

Read More...

Today I did another pull for indi and there were some additional changes which after compiling and installing the indi-qsi build is now working.

This has also fixed the kstars build.

At the moment I only have a problem with building phd2, but that is for another forum :)

Paul

Read More...

Just to make sure I have run sudo make install for libqsi and the make still fails for indi-qsi.

Paul

Read More...

Yes, libqsi is a prerequisite and it builds without issues.

I was thinking this might be a bookworm issue, but no idea really.

I know when building from source I often pick up issues.

Paul

Read More...

Yes, INDI built without issues, and libqsi but failed for indi-qsi.

Read More...

I am not sure if these are bookworm issues or something else.

build of indi-3rdparty indi-qsi
[ 50%] Building CXX object CMakeFiles/indi_qsi_ccd.dir/qsi_ccd.cpp.o
In file included from /home/indi/Projects/indi-3rdparty/indi-qsi/qsi_ccd.cpp:75:
/home/indi/Projects/indi-3rdparty/indi-qsi/qsi_ccd.h:71:79: error: ‘FITSRecord’ is not a member of ‘INDI’
71 | ddFITSKeywords(INDI::CCDChip *targetChip, std::vector<INDI::FITSRecord> &fitsKeywords) override;
| ^~~~~~~~~~

/home/indi/Projects/indi-3rdparty/indi-qsi/qsi_ccd.h:71:79: error: ‘FITSRecord’ is not a member of ‘INDI’
/home/indi/Projects/indi-3rdparty/indi-qsi/qsi_ccd.h:71:89: error: template argument 1 is invalid
71 | ords(INDI::CCDChip *targetChip, std::vector<INDI::FITSRecord> &fitsKeywords) override;
| ^

/home/indi/Projects/indi-3rdparty/indi-qsi/qsi_ccd.h:71:89: error: template argument 2 is invalid
/home/indi/Projects/indi-3rdparty/indi-qsi/qsi_ccd.h:71:18: error: ‘virtual void QSICCD::addFITSKeywords(INDI::CCDChip*, int&)’ marked ‘override’, but does not override
71 | virtual void addFITSKeywords(INDI::CCDChip *targetChip, std::vector<INDI::FITSRecord> &fitsKeywords) override;
| ^~~~~~~~~~~~~~~
/home/indi/Projects/indi-3rdparty/indi-qsi/qsi_ccd.cpp:913:75: error: ‘FITSRecord’ is not a member of ‘INDI’
913 | ddFITSKeywords(INDI::CCDChip *targetChip, std::vector<INDI::FITSRecord> &fitsKeywords)
| ^~~~~~~~~~

/home/indi/Projects/indi-3rdparty/indi-qsi/qsi_ccd.cpp:913:75: error: ‘FITSRecord’ is not a member of ‘INDI’
/home/indi/Projects/indi-3rdparty/indi-qsi/qsi_ccd.cpp:913:85: error: template argument 1 is invalid
913 | ords(INDI::CCDChip *targetChip, std::vector<INDI::FITSRecord> &fitsKeywords)
| ^

/home/indi/Projects/indi-3rdparty/indi-qsi/qsi_ccd.cpp:913:85: error: template argument 2 is invalid
/home/indi/Projects/indi-3rdparty/indi-qsi/qsi_ccd.cpp: In member function ‘virtual void QSICCD::addFITSKeywords(INDI::CCDChip*, int&)’:
/home/indi/Projects/indi-3rdparty/indi-qsi/qsi_ccd.cpp:915:31: error: no matching function for call to ‘QSICCD::addFITSKeywords(INDI::CCDChip*&, int&)’
915 | INDI::CCD::addFITSKeywords(targetChip, fitsKeywords);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/indi/Projects/indi-3rdparty/indi-qsi/qsi_ccd.h:35:
/usr/include/libindi/indiccd.h:508:22: note: candidate: ‘virtual void INDI::CCD::addFITSKeywords(INDI::CCDChip*)’
508 | virtual void addFITSKeywords(CCDChip * targetChip);
| ^~~~~~~~~~~~~~~
/usr/include/libindi/indiccd.h:508:22: note: candidate expects 1 argument, 2 provided
/home/indi/Projects/indi-3rdparty/indi-qsi/qsi_ccd.cpp:933:18: error: request for member ‘push_back’ in ‘fitsKeywords’, which is of non-class type ‘int’
933 | fitsKeywords.push_back({"EPERADU", electronsPerADU, 3, "Electrons per ADU"});
| ^~~~~~~~~
make[2]: *** [CMakeFiles/indi_qsi_ccd.dir/build.make:76: CMakeFiles/indi_qsi_ccd.dir/qsi_ccd.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:83: CMakeFiles/indi_qsi_ccd.dir/all] Error 2
make: *** [Makefile:136: all] Error 2

build of kstars
[ 7%] Building CXX object kstars/CMakeFiles/KStarsLib.dir/fitsviewer/fitstab.cpp.o
In file included from /home/indi/Projects/kstars/kstars/fitsviewer/fitstab.h:25,
from /home/indi/Projects/kstars/kstars/fitsviewer/fitstab.cpp:7:
/home/indi/Projects/kstars/kstars/ekos/auxiliary/solverutils.h:9:10: fatal error: stellarsolver.h: No such file or directory
9 | #include <stellarsolver.h>
| ^~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [kstars/CMakeFiles/KStarsLib.dir/build.make:614: kstars/CMakeFiles/KStarsLib.dir/fitsviewer/fitstab.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
In file included from /home/indi/Projects/kstars/kstars/fitsviewer/fitstab.h:25,
from /home/indi/Projects/kstars/kstars/fitsviewer/fitsviewer.cpp:15:
/home/indi/Projects/kstars/kstars/ekos/auxiliary/solverutils.h:9:10: fatal error: stellarsolver.h: No such file or directory
9 | #include <stellarsolver.h>
| ^~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [kstars/CMakeFiles/KStarsLib.dir/build.make:586: kstars/CMakeFiles/KStarsLib.dir/fitsviewer/fitsviewer.cpp.o] Error 1
In file included from /home/indi/Projects/build/kstars/kstars/KStarsLib_autogen/GB6ZSSQLTO/../../../../../kstars/kstars/fitsviewer/fitstab.h:25,
from /home/indi/Projects/build/kstars/kstars/KStarsLib_autogen/GB6ZSSQLTO/moc_fitstab.cpp:10,
from /home/indi/Projects/build/kstars/kstars/KStarsLib_autogen/mocs_compilation.cpp:49:
/home/indi/Projects/kstars/kstars/ekos/auxiliary/solverutils.h:9:10: fatal error: stellarsolver.h: No such file or directory
9 | #include <stellarsolver.h>
| ^~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [kstars/CMakeFiles/KStarsLib.dir/build.make:558: kstars/CMakeFiles/KStarsLib.dir/KStarsLib_autogen/mocs_compilation.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:1534: kstars/CMakeFiles/KStarsLib.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 7%] Built target pofiles-adce09dc0369cccc41618d007d7eef25
make: *** [Makefile:146: all] Error 2

Read More...

Paul replied to the topic 'Kstars 3.6.8 and INDI 2.0.5 released' in the forum. 4 months ago

Steve,

You aren't by any chance getting a low voltage warning?

Paul

Read More...

Steve,

Astro cameras are very sensitive and will need to be tested at night or a dark room.

Paul

Read More...

Steve,

Use another application to run the camera and see what it does.

If it works fine then it must be some setting or fault with Kstars/Ekos.

Paul

Read More...