Paul replied to the topic 'Re:Capture settings > 900 seconds are not maintained' in the forum. 4 days ago

Version about 2 weeks old.

1. This is because you use the spin arrows and not a digit entry, correct? So you require additional intermediate values? Yes or the ability to configure it for my own use.

2. Isn't this because you are not actually editing the job you want to modify? When you are in edit mode, the "+" button changes to a check, to validate your changes. Please confirm. No, this happens whether I use use the up/down buttons or edit it directly - any value over 900 gets set back to 900. It can be seen in simulated camera as well.

3. I have a differential pushed in review to fix that sort of thing and properly support locale characteristics. But the dust needs to settle first on kstars-bleeding. I am build locally on Raspbian but the latest kstars build is failing.

4. The count reset issue is fixed and tested OK on my side, but the differential might not be merged yet. Stay tuned for this. Will do.

Read More...

Paul created a new topic ' Capture settings > 900 seconds are not maintained' in the forum. 4 days ago

I have recently started using 1200 second exposures for narrowband.
There are three issues with this...
1) When incrementing the exposure times it jumps from 900 to 3600 seconds - intermediate steps of 1200 and 1800 would be nice and even better if this was configurable.
2) When any value over 900 seconds is set and you go to any other tab and then back to the camera tab it always sets the exposure time back to 900.
3) When logging the exposures at the bottom of the widown it has started displaying the times in an exponential format.

Further, and I am not sure if this is related, when taking exposures which restart when the guiding exceeds a limit, the exposure counter if being randomly reset back to zero. I have only started seeing this happen when using 1200 second exposures.

Read More...

Paul replied to the topic 'How to visually frame a subject?' in the forum. 5 days ago

Why not frame it as you want, run an alignment with "do nothing" to load the co-ordinates and copy the result into a scheduler job.

Paul

Read More...

Paul replied to the topic 'Failure to connect to QSI camera after build' in the forum. 1 month ago

I did that by running rm -rf * in the libindi directory and running cmake, make and make install and the same thing in 3rdparty, twice.
It did not work as the 3rdparty build keeps failing.

Read More...

Paul replied to the topic 'Failure to connect to QSI camera after build' in the forum. 1 month ago

I have posted this on giithub as I have exhausted my knowledge on builds.

Read More...

Paul replied to the topic 'Failure to connect to QSI camera after build' in the forum. 1 month ago

Jasem,
I have been build from source for a couple of years with the occasional issue.
I build all 3rdparty.
The problem it now keeps trying to connect to the camera and failing.
I have added another log file.

Read More...

Paul replied to the topic 'Failure to connect to QSI camera after build' in the forum. 1 month ago

Jasem,

I have downloaded using git pull.
I assume that is the latest?

Paul

Read More...

Paul replied to the topic 'Failure to connect to QSI camera after build' in the forum. 1 month ago

I performed another build today and the QSI camera still fails to b recognised.
As of today the 3rdparty build is returning the following errors:

indi-rtlsdr/CMakeFiles/indi_rtlsdr_detector.dir/build.make:62: recipe for target 'indi-rtlsdr/CMakeFiles/indi_rtlsdr_detector.dir/indi_rtlsdr_detector.cpp.o' failed
make[2]: *** [indi-rtlsdr/CMakeFiles/indi_rtlsdr_detector.dir/indi_rtlsdr_detector.cpp.o] Error 1
CMakeFiles/Makefile2:2012: recipe for target 'indi-rtlsdr/CMakeFiles/indi_rtlsdr_detector.dir/all' failed
make[1]: *** [indi-rtlsdr/CMakeFiles/indi_rtlsdr_detector.dir/all] Error 2
Makefile:149: recipe for target 'all' failed
make: *** [all] Error 2

Read More...

Paul created a new topic ' Failure to connect to QSI camera after build' in the forum. 1 month ago

I completed a bulld on my Raspberry Pi 3 running Raspbian today and now

File Attachment:

File Name: log_19-11-42.txt
File Size: 27 KB
the software fails to connect to my QSI 583 camera.

It was working fine before the update.

Read More...

Paul created a new topic ' Mount control buttons in kstars' in the forum. 1 month ago

From my experience I believe the synchronise button on the left is too similar to the stop sign used in many countries.

I often need to use the stop icon when the mount is doing something unpredicated and under those circumstances I have on a number occasions clicked the synch instead of the stop. The sort of thing you do when in a panic and don't have time to think.

My suggestion is to change the stop icon to a red octagon and the synchronise icon to an equals symbol without any red.

I also struggle with the goto symbol which is hard to recognise as meaningful at the size presented on a small screen.

Does anyone have any thoughts on this - am I the only one?

Paul

Read More...

Paul replied to the topic 'Guiding won't start because calibration fails' in the forum. 1 month ago

Anon,
I can feel your frustration as guiding can be a particularly frustrating exercise with so many factors in play.
I am surprised you can tell the mount is moving by listening to it as the guiding adjustments are very small. It would be impractical to do this on my G11.
From what you are describing I assume you can see the mount moving on screen by watching the calibration star moving.
If so, then the message may be correct.
You need to ensure the mount moves a sufficient distance within the number of steps defined.
There are a number of calibration reasons that this can occur
1) Too few steps allowed
2) Too little movement for each step
3) Too far to move
I have previously used the internal guider but I currently use PHD2 for guiding.
I cannot recall whether the internal guider has a manual setting but if it does you should first test that you can get the mount to move in the four directions.
PHD2 has a "wizard" option to allow you to configure it - I would try doing this if INDI has it. This will ensure the values are set to reasonable values.
If still having issues ensure the mount guiding rate is set correctly. With a G11 you can change it to a number of values with 0.5x as the default.
Paul

Read More...

Paul replied to the topic 'make is failing with a target error' in the forum. 2 months ago

Jasem,

Your fix has solved the problem. Thanks.

Read More...

Paul replied to the topic 'make is failing with a target error' in the forum. 2 months ago

I have tried to get rid of this error by clearing everything in the kstars directory and running make again, running git pull multiple times in the last week but it is still happening. Is this a problem? I can still use the software.

phomer60 wrote: I am getting the following error from a build today.. This is the first update in about a week and is on a Raspberry Pi running Raspbian.

kstars/CMakeFiles/KStarsLib.dir/build.make:2549: recipe for target 'kstars/CMakeFiles/KStarsLib.dir/ekos/ekoslive/message.cpp.o' failed
make[2]: *** [kstars/CMakeFiles/KStarsLib.dir/ekos/ekoslive/message.cpp.o] Error 1
CMakeFiles/Makefile2:328: recipe for target 'kstars/CMakeFiles/KStarsLib.dir/all' failed
make[1]: *** [kstars/CMakeFiles/KStarsLib.dir/all] Error 2
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2



Read More...

Paul created a new topic ' make is failing with a target error' in the forum. 2 months ago

I am getting the following error from a build today.. This is the first update in about a week and is on a Raspberry Pi running Raspbian.

kstars/CMakeFiles/KStarsLib.dir/build.make:2549: recipe for target 'kstars/CMakeFiles/KStarsLib.dir/ekos/ekoslive/message.cpp.o' failed
make[2]: *** [kstars/CMakeFiles/KStarsLib.dir/ekos/ekoslive/message.cpp.o] Error 1
CMakeFiles/Makefile2:328: recipe for target 'kstars/CMakeFiles/KStarsLib.dir/all' failed
make[1]: *** [kstars/CMakeFiles/KStarsLib.dir/all] Error 2
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2

Read More...

Paul replied to the topic 'sudo make install failing for kstars' in the forum. 3 months ago

Following on from kstars now working.
Today 3rdparty is failing - I assume it needs something additional to be installed, but what?
sudo make install
-- Found libnova: /usr/lib/arm-linux-gnueabihf/libnova.so
-- Found CFITSIO: /usr/lib/arm-linux-gnueabihf/libcfitsio.so
-- Found libnova: /usr/lib/arm-linux-gnueabihf/libnova.so
-- Found CFITSIO: /usr/lib/arm-linux-gnueabihf/libcfitsio.so
-- Found libnova: /usr/lib/arm-linux-gnueabihf/libnova.so
-- Found libnova: /usr/lib/arm-linux-gnueabihf/libnova.so
-- Found CFITSIO: /usr/lib/arm-linux-gnueabihf/libcfitsio.so
-- Found libtiffxx: /usr/lib/arm-linux-gnueabihf/libtiffxx.so
-- Found libqsiapi: /usr/lib/arm-linux-gnueabihf/libqsiapi.so
-- Found CFITSIO: /usr/lib/arm-linux-gnueabihf/libcfitsio.so
-- Found libqsiapi: /usr/lib/arm-linux-gnueabihf/libqsiapi.so
-- Found libsbig: /usr/lib/arm-linux-gnueabihf/libsbig.so
-- Found CFITSIO: /usr/lib/arm-linux-gnueabihf/libcfitsio.so
-- Found libsbig: /usr/lib/arm-linux-gnueabihf/libsbig.so
-- Found libinovasdk: /usr/lib/arm-linux-gnueabihf/libinovasdk.so
-- Found CFITSIO: /usr/lib/arm-linux-gnueabihf/libcfitsio.so
-- Found libinovasdk: /usr/lib/arm-linux-gnueabihf/libinovasdk.so
-- Found libfli: /usr/lib/arm-linux-gnueabihf/libfli.so
-- Found CFITSIO: /usr/lib/arm-linux-gnueabihf/libcfitsio.so
-- Found libfli: /usr/lib/arm-linux-gnueabihf/libfli.so
-- Found libapogee: /usr/lib/arm-linux-gnueabihf/libapogee.so
-- Found CFITSIO: /usr/lib/arm-linux-gnueabihf/libcfitsio.so
-- Found libapogee: /usr/lib/arm-linux-gnueabihf/libapogee.so
-- Found CFITSIO: /usr/lib/arm-linux-gnueabihf/libcfitsio.so
CMake Error at /home/pi/indi/cmake_modules/FindDC1394.cmake:44 (message):
DC1394 not found. Please install libdc1394 development package.
Call Stack (most recent call first):
indi-ffmv/CMakeLists.txt:16 (find_package)


-- Configuring incomplete, errors occurred!
See also "/home/pi/indi/build/3rdparty/CMakeFiles/CMakeOutput.log".
See also "/home/pi/indi/build/3rdparty/CMakeFiles/CMakeError.log".
Makefile:764: recipe for target 'cmake_check_build_system' failed
make: *** [cmake_check_build_system] Error 1

Read More...

Paul replied to the topic 'sudo make install failing for kstars' in the forum. 3 months ago

Sorry, I should have stated that I am running this on Raspbian, so it won't be an x86 install file.

Do I need to install anything to get this going?

Read More...

Paul created a new topic ' sudo make install failing for kstars' in the forum. 3 months ago

Can anyone tell me what is missing from today's update?

sudo make install
CMake Error at /usr/lib/arm-linux-gnueabihf/cmake/Qt5/Qt5Config.cmake:26 (find_package):
Could not find a package configuration file provided by "Qt5WebSockets"
with any of the following names:

Qt5WebSocketsConfig.cmake
qt5websockets-config.cmake

Add the installation prefix of "Qt5WebSockets" to CMAKE_PREFIX_PATH or set
"Qt5WebSockets_DIR" to a directory containing one of the above files. If
"Qt5WebSockets" provides a separate development package or SDK, be sure it
has been installed.
Call Stack (most recent call first):
CMakeLists.txt:75 (find_package)


-- Configuring incomplete, errors occurred!
See also "/home/pi/indi/build/kstars/CMakeFiles/CMakeOutput.log".
See also "/home/pi/indi/build/kstars/CMakeFiles/CMakeError.log".
Makefile:602: recipe for target 'cmake_check_build_system' failed
make: *** [cmake_check_build_system] Error 1

Read More...

Login



3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!