Jerry Black replied to the topic 'Powered USB Hubs' in the forum. 6 days ago

From recent experience, I can confirm that my Samsung T5 1TB SSD works down to at least -8.5 C.

DeeJayD wrote: Hello folks,
...
And does anyone know if an SSD works at temperatures down to -10°C / 14°F?

Regards
Danny



Read More...

I agree about Astroberry being armhf, but his original message referred to amd rather than arm, so it made me think he had downloaded a version for an AMD chip based PC rather than a RPi.

Read More...

And are you installing on amd64 or arm hardware?

Read More...

rickbassham wrote: Hey, I've got a CGX as well and don't have any issues. Which driver are you using? Some things to check, make sure your location and time are set correctly. Look for the "Align" button on the "Main Control" tab in the INDI control panel, and click it. This will send the mount to the switch position and let the hand controller know it is aligned.


I've got a CGX connected via the usb connector on the hand controller with the CGX driver. My workflow has always been to do a Celestron 2 star alignment, followed by a Celestron Polar Alignment and then launch KStars. At that point I can (optionally right click on the planetarium display and find the telescope position and) find my target for imaging with plate solving. I've never found KStars polar alignment to agree or be as good at the Celestron Polar Alignment although undoubtedly this is my fault in that it's something I'm doing wrong. I also find that Phd2 works better for me than the built-in guiding. Almost always, the internal guider says there's a mount problem and won't let me guide. Phd2 works for me. I expect this too, is operator / configuration error.

Do you have any gems of wisdom to help?

Thanks

Read More...

Use sudo nano When editing the file. ?

Read More...

jabian wrote: I'm not sure I haven't modified any parameters involuntarily but...
It happened both with latest Stellarmate stable on an Raspi4 and with latest KStars 3.5.0 stable on PC running Ubuntu, just after burning the image (Stellarmate) or apt upgrade (Ubuntu)

- Start KStars
- Select Simulators profile in EKOS and connect
- Set telescope tracking to ON
- Capture and solve
--> FAIL! :(

I would expect simulation parameters to be set for success to start with.
Then, one could start from there...

Am I [doing|expecting] something wrong ?
On a fresh install, what would be the shortest path for solving success on a simulation ?


It may not be causative, but I find solving works for me (only) when I do a goTo with the simulators before asking it to plate solve.

Read More...

Jerry Black replied to the topic 'Kstars 3.5.0 OSx' in the forum. 2 months ago

rlancaste wrote:

jerry wrote:

jerry wrote:

rlancaste wrote: Please see the instructions here:

github.com/rlancaste/KStars-INDI-Mac-Dev...folder-in-qt-creator


Thanks. I had an out-of-date version of that page open in my browser for some time. The "forked-build" helped, <em>as well as actually following your instructions</em> :)


Following up on this, to get KStars to launch from within QT on OS X I had to uncheck the "Add build library search path to DYLD_LIBRARY_PATH and DYLD_FRAMEWORK_PATH " option from the Run section in the Projects


Yes, that has been necessary for awhile. Did you see the instructions about that in the readme file? I added the instructions to do that several months ago.


Whoops. I see it now. Thanks.

Simulator Plate solving in .28 seconds. wow.

Read More...

Jerry Black replied to the topic 'Kstars 3.5.0 OSx' in the forum. 2 months ago

jerry wrote:

rlancaste wrote: Please see the instructions here:

github.com/rlancaste/KStars-INDI-Mac-Dev...folder-in-qt-creator


Thanks. I had an out-of-date version of that page open in my browser for some time. The "forked-build" helped, <em>as well as actually following your instructions</em> :)


Following up on this, to get KStars to launch from within QT on OS X I had to uncheck the "Add build library search path to DYLD_LIBRARY_PATH and DYLD_FRAMEWORK_PATH " option from the Run section in the Projects

Read More...

Jerry Black replied to the topic 'Kstars 3.5.0 OSx' in the forum. 2 months ago

rlancaste wrote: Please see the instructions here:

github.com/rlancaste/KStars-INDI-Mac-Dev...folder-in-qt-creator


Thanks. I had an out-of-date version of that page open in my browser for some time. The "forked-build" helped, as well as actually following your instructions :)

Read More...

Jerry Black replied to the topic 'Kstars 3.5.0 OSx' in the forum. 2 months ago

Most of this is beyond me, but I'd like to get to a QT environment on OS X. My current problem is in opening the CMakeLists.txt in QT.

I get.

Running /Users/jerry/Qt/Tools/CMake/CMake.app/Contents/bin/cmake -S /Volumes/Data_Raid/kstars_dev/src-forked/kstars -B /private/var/folders/2j/rl4qjhx13tj22xnht5hhzwrw0000gn/T/QtCreator-SSiACh/qtc-cmake-HSzmudjE -GNinja -DCMAKE_BUILD_TYPE:String=Debug -DQT_QMAKE_EXECUTABLE:STRING=/Users/jerry/Qt/5.15.2/clang_64/bin/qmake -DCMAKE_PREFIX_PATH:STRING=/Users/jerry/Qt/5.15.2/clang_64 -DCMAKE_C_COMPILER:STRING=/usr/bin/clang -DCMAKE_CXX_COMPILER:STRING=/usr/bin/clang++ in /private/var/folders/2j/rl4qjhx13tj22xnht5hhzwrw0000gn/T/QtCreator-SSiACh/qtc-cmake-HSzmudjE.
-- The CXX compiler identification is AppleClang 12.0.0.12000032
-- The C compiler identification is AppleClang 12.0.0.12000032
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/clang++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/clang - skipped
-- Detecting C compile features
-- Detecting C compile features - done
CMake Error at CMakeLists.txt:64 (find_package):
  Could not find a package configuration file provided by "ECM" (requested
  version 1.7.0) with any of the following names:

    ECMConfig.cmake
    ecm-config.cmake

  Add the installation prefix of "ECM" to CMAKE_PREFIX_PATH or set "ECM_DIR"
  to a directory containing one of the above files.  If "ECM" provides a
  separate development package or SDK, be sure it has been installed.


-- Configuring incomplete, errors occurred!

I see a file at: /Volumes/Data_Raid/kstars_dev/ASTRO-ROOT/share/ECM/cmake/ECMConfig.cmake

but I'm not sure what the problem is at the moment.

Sorry Rob, if this is more work than it might benefit.

Cheers

Read More...

Jerry Black replied to the topic 'AstroPi3 Scripts revised' in the forum. 2 months ago

I'm guessing... are you compiling with a "-j x" option that exceeds you available memory? On a 4G Odroid, I've had to cut back my compile processes to -j2 it seems.

TomAstro wrote: no idea why I am still getting this in Raspbian OS 64bit

[ 32%] Building CXX object kstars/CMakeFiles/KStarsLib.dir/ekos/auxiliary/dustcap.cpp.o
c++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make[2]: *** [kstars/CMakeFiles/KStarsLib.dir/build.make:1244: kstars/CMakeFiles/KStarsLib.dir/ekos/manager.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:1004: kstars/CMakeFiles/KStarsLib.dir/all] Error 2
make: *** [Makefile:141: all] Error 2



Read More...