Hi there,
I was recently pointed at this thread as I was experiencing poor FPS with my ASI174MM on RPi4/USB3 at any higher ROI than 1536x1024 (more details
here
). I gave the libASICamera2Boost.so a whirl with some mixed results:
With indiserver running the library on the RPi I was able to get about 51FPS over gigabit ethernet (~940Mbits/sec). A big difference compared to it barely working at all at full resolution (< 1FPS)! However the indi_asi_ccd driver crashed quite often on the RPi saying something like:
2021-09-15T22:13:13: Driver indi_asi_ccd: No INumber 'Gain' in ZWO CCD ASI174MM.CCD_CONTROLS 2021-09-15T22:13:13: Driver indi_asi_ccd: No INumber 'Offset' in ZWO CCD ASI174MM.CCD_CONTROLS 2021-09-15T22:14:19: Driver indi_asi_ccd: stderr EOF 2021-09-15T22:14:19: Driver indi_asi_ccd: restart #1 Child process 7329 died
2021-09-15T22:11:59: [ERROR] Failed to get control information (ASI_ERROR_INVALID_INDEX).
Thanks guys. I should have known that but had completely forgotten about it. I must have done the DCMAKE_INSTALL_PREFIX=/usr with my old drivers as they were in the right place.
Just as a thought would it not make sense to have indi-web look into /usr/local too?
Read More...
Continuing my monologue...
Looks like it's because of what I have in my CMakeLists.txt e.g.
set(INDI_DATA_DIR "${CMAKE_INSTALL_PREFIX}/share/indi")
After poking around a bit more I sort of solved the problem.
Looks like indi-web is looking in
/usr/share/indi
/usr/local/share/indi/
Hi,
I've recently completed a new INDI driver for my DIY focuser. It compiles, installs and runs just fine but for some reason the INDI Web Manager running on the same system does not list the driver at all. Is it supposed to find it automatically or do I need to do something?
sudo make install installs these two files:
/usr/local/bin/indi_bullseye_focus
/usr/local/share/indi/indi_bullseye_focus.xml
Strangely it does list my super old drivers that I've done years ago the same way.
Any pointers to how to solve this?
Cheers,
Kari
Read More...
Hi,
For quite some time I have had trouble compiling kstars from latest git pull if I have tests enabled. Here's what I usually do:
cd <kstars git repo folder>
git pull
mkdir build
cd build
cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=RelWithDebInfo ..
make
[ 98%] Building CXX object Tests/kstars_ui/CMakeFiles/test_ekos_meridianflip_specials.dir/qrc_kstars.cpp.o
In file included from /home/kbrown/Documents/dev/git_repos/kstars/Tests/kstars_ui/test_ekos_capture_helper.cpp:13:0:
/home/kbrown/Documents/dev/git_repos/kstars/Tests/kstars_ui/test_ekos_capture_helper.cpp: In member function ‘bool TestEkosCaptureHelper::startCapturing(bool)’:
/home/kbrown/Documents/dev/git_repos/kstars/Tests/kstars_ui/test_ekos_capture_helper.h:258:18: error: ‘qWaitFor’ is not a member of ‘QTest’
cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=RelWithDebInfo -DBUILD_TESTING=OFF ..
Awesome, that works. I'll just write a simple script to apply this fix to all of my broken files.
Cheers,
Kari
Read More...
That's helpful! Thank you! Wonder if there is a way to edit the header? I've got gigabytes of data of (cropped) mars. If I could just tell the software it's not actually cropped I might be able to revive the files...
Read More...
Feels like the cropped area doesn't get written to the file correctly as all the various players I've tried are showing the problem same way.
Jasem: Did you have any luck with the files I linked?
Read More...
My videos are 8-bit. I've managed to narrow the problem down to the fact that I used cropping (Left: 320, Top: 240, Width: 640, Height: 480) while capturing the videos. Full frame videos seem to play back just fine. I've uploaded an example of these here:
www.dropbox.com/sh/uqnoj2gyhths6k7/AAByT...YwsyTcjuHoFibqa?dl=0
Read More...
Hi. I've just captured a load of SER video files with Ekos using my QHY5L-II mono camera. Everything seemed to go okay and the live video stream showed up correctly.
I'm now trying to play back the captured files and none of the programs I tried are displaying them correctly. The attached screenshot shows what they typically look like. What could be the problem?
Read More...
I'm somewhat tempted to have a closer look at the oaCapture source code and see if it would be easy to write an indi ccd driver based on it. I believe it does not depend on the QHY SDK. Does that make any sense? Obviously it would make it less generic...
Read More...