OK, thanks for the clarification on which mode and great that you're getting good results.

The JWST image is quite amazing. I'll need some time before I think I understand it but it's an amazing piece of work.

Read More...

Paul - Are you using the EQ or Alt-AZ mode for your subs?

Jasem is a star. He got my Stellarmate working again with at least the Alt-AZ driver from the 3rd-party family. I need to test the EQ driver as I currently have the wedge attached but at least I have a chance of testing again if it doesn't work and I remove the wedge.

Read More...

Jasem,
Which firmware version are you using in your AZ-GTI? Is it the newer one that supports equatorial operation or the original one that only supported Alt-AZ?

Thanks,
Mark

Read More...

I will send a support request on my AZ-GTi/Stellarmate/Canon camera setup but I think it's unlikely to improve much. I'm using it 100% over VNC to my home Google mesh network. The connection is pretty reliable. The AZ-GTi and Canon communicate with Stellarmate over USB - I have the AZ-GTi USB dongle. The connections to that hardware is reliable. That said this camera/mount/computer setup has never worked well. Possibly it's me not finding the right step-by-step instructions, or misunderstanding what I have read, but it's never tracked correctly using Ekos and KStars. As I say, targets are out-of-frame in 20-30 minutes using KStars but stays in frame for 2-3 hours using SynScan. I haven't used Stellarmate in months as it seemed pointless until Paul resurrected this thread but from memory attempting to duplicate SynScan's 3 star alignment in KStars has never been accurate, and sadly Stellarmate has never correctly plate solved a single shot for me on the Raspberry Pi, but plate solving works fine on the same shots when I do it on my Linux machine.

I'm going to attempt to save any special configurations I added, such as NFS mount instructions and a couple of batch files, and then just load the OS from scratch on a new memory card.

Like Paul I pretty much consider the AZ-GTi to be a bust. I'm glad it works for Jasem but it certainly doesn't work here for me. I don't plan on buying any new hardware. If I did it wouldn't be SkyWatcher hardware. The couple of support requests I made with them on this mount resulted in F-U responses saying they don't support astrophotography on the AZ-GTi. It's a fun little mount with SynScan though.

Read More...

Well, sadly I guess I've messed everything up. I'm still at the point where I cannot run Ekos with the Canon driver. I tried removing stuff that I thought I had added, and the Stellarmate Software Updater says I'm completely up to date (v1.7.1, channel stable) but the update_indi_drivers command is failing differently now and I don't know how to fix it after all this messing about short of blowing the whole Stellarmate installation away and reloading the whole OS which would lose all my NFS setting and other stuff that I currently care about but that's probably what I need to do.

stellarmate@stellarmate:~ $ update_indi_drivers
Hit:1 raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 archive.raspberrypi.org/debian buster InRelease
Hit:3 ppa.stellarmate.com/repos/apt/stable buster InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
build-essential is already the newest version (12.6).
git is already the newest version (1:2.20.1-2+deb10u3).
libboost-dev is already the newest version (1.67.0.1+b1).
libboost-regex-dev is already the newest version (1.67.0.1+b1).
libcfitsio-dev is already the newest version (3.450-3).
libcurl4-gnutls-dev is already the newest version (7.64.0-4+deb10u2).
libdc1394-22-dev is already the newest version (2.2.5-1).
libfftw3-dev is already the newest version (3.3.8-2).
libftdi-dev is already the newest version (0.20-4).
libftdi1-dev is already the newest version (1.4-1+b2).
libgps-dev is already the newest version (3.17-7+b1).
libgsl-dev is already the newest version (2.5+dfsg-6).
libjpeg-dev is already the newest version (1:1.5.2-2+deb10u1).
liblimesuite-dev is already the newest version (18.06.0+dfsg-1+b1).
libnova-dev is already the newest version (0.16-4).
libtiff-dev is already the newest version (4.1.0+git191117-2~deb10u4).
libusb-1.0-0-dev is already the newest version (2:1.0.22-2).
zlib1g-dev is already the newest version (1:1.2.11.dfsg-1+deb10u1).
cmake is already the newest version (3.16.3-3~bpo10+1).
librtlsdr-dev is already the newest version (0.6-1+rpt1).
libgphoto2-dev is already the newest version (2.5.29-stable~202205251835).
libraw-dev is already the newest version (0.20.0-stable~202201171501).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Cloning into 'indi-3rdparty'...
remote: Enumerating objects: 2803, done.
remote: Counting objects: 100% (2803/2803), done.
remote: Compressing objects: 100% (2032/2032), done.
remote: Total 2803 (delta 1014), reused 1707 (delta 665), pack-reused 0
Receiving objects: 100% (2803/2803), 116.39 MiB | 5.75 MiB/s, done.
Resolving deltas: 100% (1014/1014), done.
Checking out files: 100% (2756/2756), done.
-- The CXX compiler identification is GNU 8.3.0
-- The C compiler identification is GNU 8.3.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Performing Test COMPATIBLE_FORTIFY_SOURCE
-- Performing Test COMPATIBLE_FORTIFY_SOURCE - Success
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29")
-- Checking for module 'libavcodec>=57.64.101'
-- Found libavcodec, version 58.35.100
-- Checking for module 'libavdevice>=57.1.100'
-- Found libavdevice, version 58.5.100
-- Checking for module 'libavformat>=57.56.100'
-- Found libavformat, version 58.20.100
-- Checking for module 'libavutil>=55.34.100'
-- Found libavutil, version 56.22.100
-- Checking for module 'libswscale>=4.2.100'
-- Found libswscale, version 5.3.100
-- Found FFMPEG: /usr/lib/arm-linux-gnueabihf/libavcodec.so;/usr/lib/arm-linux-gnueabihf/libavdevice.so;/usr/lib/arm-linux-gnueabihf/libavformat.so;/usr/lib/arm-linux-gnueabihf/libavutil.so;/usr/lib/arm-linux-gnueabihf/libswscale.so, /usr/include/arm-linux-gnueabihf
-- Since FFMPEG was found, INDI Webcam Driver can be built
-- Found USB1: /usr/lib/arm-linux-gnueabihf/libusb-1.0.so (found version "1.0.22")
-- Performing Test USB1_HAS_LIBUSB_ERROR_NAME
-- Performing Test USB1_HAS_LIBUSB_ERROR_NAME - Success
-- Found CURL: /usr/lib/arm-linux-gnueabihf/libcurl.so (found version "7.64.0")
CMake Error at cmake_modules/FindINDI.cmake:285 (message):
Could not find INDI include directory
Call Stack (most recent call first):
libapogee/CMakeLists.txt:26 (find_package)


-- Configuring incomplete, errors occurred!
See also "/home/stellarmate/Projects/build/indi-3rdparty/CMakeFiles/CMakeOutput.log".
make: *** No targets specified and no makefile found. Stop.
make: *** No rule to make target 'install'. Stop.
-- Found FFMPEG: /usr/lib/arm-linux-gnueabihf/libavcodec.so;/usr/lib/arm-linux-gnueabihf/libavdevice.so;/usr/lib/arm-linux-gnueabihf/libavformat.so;/usr/lib/arm-linux-gnueabihf/libavutil.so;/usr/lib/arm-linux-gnueabihf/libswscale.so, /usr/include/arm-linux-gnueabihf
-- Since FFMPEG was found, INDI Webcam Driver can be built
CMake Error at cmake_modules/FindINDI.cmake:285 (message):
Could not find INDI include directory
Call Stack (most recent call first):
indi-eqmod/CMakeLists.txt:10 (find_package)


-- Configuring incomplete, errors occurred!
See also "/home/stellarmate/Projects/build/indi-3rdparty/CMakeFiles/CMakeOutput.log".
make: *** No targets specified and no makefile found. Stop.
make: *** No rule to make target 'install'. Stop.
stellarmate@stellarmate:~ $

Read More...

Agreed: It doesn't look right but that's what it does. I've completely removed the Projects directory, rebooted and tried a couple of times. It fails.

Question: The github build instructions had me install a bunch of libraries, some of which I could find and some of which I could not. Might those be causing problems?

From my .bash_history file:

sudo apt-get -y install libnova-dev libcfitsio-dev libusb-1.0-0-dev zlib1g-dev libgsl-dev build-essential cmake git libjpeg-dev libcurl4-gnutls-dev libtiff-dev libfftw3-dev libftdi-dev libgps-dev libraw-dev libdc1394-22-dev libgphoto2-dev libboost-dev libboost-regex-dev librtlsdr-dev liblimesuite-dev libftdi1-dev libavcodec-dev libavdevice-dev
sudo apt-get -y install libindi-dev
sudo apt-get -y install libqsi
sudo apt-get -y install libqsi-dev
sudo apt-get -y install libfli-dev
sudo apt-get -y install libapogee-dev
sudo apt-get -y install libapogee

Read More...

I tried that but it failed. Error message below. That's why I thought I had to go to Github.

[ 25%] Linking CXX executable indi_nexdome
[ 25%] Built target indi_nexdome
make: *** [Makefile:152: all] Error 2
[ 6%] Built target indi_azgti_telescope
[ 11%] Built target indi_staradventurer2i_telescope
[ 16%] Built target indi_eqmod_telescope
[ 16%] Built target indi_astrolink4
[ 17%] Built target indi_lx200aok
[ 19%] Built target indi_starbook_telescope
[ 20%] Built target indi_starbook_ten
[ 20%] Built target indi_sx_wheel
[ 22%] Built target sx_ccd_test
[ 23%] Linking CXX executable indi_sx_ccd
/usr/bin/ld: CMakeFiles/indi_sx_ccd.dir/sxccd.cpp.o:(.data.rel.ro+0xcc): undefined reference to `INDI::CCD::addFITSKeywords(fitsfile*, INDI::CCDChip*)'
collect2: error: ld returned 1 exit status
make[2]: *** [indi-sx/CMakeFiles/indi_sx_ccd.dir/build.make:102: indi-sx/indi_sx_ccd] Error 1
make[1]: *** [CMakeFiles/Makefile2:1401: indi-sx/CMakeFiles/indi_sx_ccd.dir/all] Error 2
make: *** [Makefile:152: all] Error 2
stellarmate@stellarmate:~ $

Read More...

OK, so I see I need the indi-3rdparty code.

I need instructions to download and build it on Stellarmate. I'm not a programmer.

Read More...

Different firmware in our AZ-GTI's? I've updated 6-12 months ago for the equatorial mode but I think this error, now a warning, was there before. Just not totally sure.

Anyway, I need to solve the canon driver crash first.

Read More...

[2022-07-07T11:21:34.830 MST INFO ][ org.kde.kstars.ekos] - "AZ-GTi Alt-Az WiFi is online."
[2022-07-07T11:21:34.959 MST INFO ][ org.kde.kstars.ekos] - "Guider port from AZ-GTi Alt-Az WiFi is ready."
[2022-07-07T11:21:35.077 MST INFO ][ org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[INFO] Mount is unparked. "
[2022-07-07T11:21:35.078 MST INFO ][ org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[INFO] Loading device configuration... "
[2022-07-07T11:21:35.081 MST INFO ][ org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[INFO] Auto search is enabled. When connecting, the driver shall attempt to communicate with all available system ports until a connection is established. "
[2022-07-07T11:21:35.083 MST INFO ][ org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[INFO] Dome Policy set to: Dome ignored. Mount can park or unpark regardless of dome parking state. "
[2022-07-07T11:21:35.085 MST INFO ][ org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[INFO] Observer location updated: Latitude 32:13:14.0 (32.22) Longitude -110:58:08.0 (-110.97) "
[2022-07-07T11:21:35.087 MST INFO ][ org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[INFO] Device configuration applied. "
[2022-07-07T11:21:35.237 MST INFO ][ org.kde.kstars.ekos.mount] - "Telescope info updated successfully."
[2022-07-07T11:21:35.325 MST INFO ][ org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[INFO] Observer location updated: Latitude 32:13:14.0 (32.22) Longitude -110:58:08.0 (-110.97) "
[2022-07-07T11:21:37.785 MST CRIT ][ org.kde.kstars.indi] - INDI driver "indi_canon_ccd" crashed!
[2022-07-07T11:21:40.789 MST CRIT ][ org.kde.kstars.indi] - INDI driver "indi_canon_ccd" crashed!
[2022-07-07T11:21:41.917 MST INFO ][ org.kde.kstars.ekos] - "Unable to establish:\n+ Canon DSLR\nPlease ensure the device is connected and powered on."
[2022-07-07T11:21:51.335 MST DEBG ][ org.kde.kstars] - 22 StarBlocks freed from StarBlockFactory

Read More...

Also, both of the red error message about Zero Microsteps per worm revolution is now a warning message in an orange/yellow color.

It says 'Possible corrupted data'.

Am I to understand that you do not see this on your AZ-GTI?

Read More...

OK, the build process worked with one error message that the indi directory existed and wasn't empty. the update_indi_core command appears to have worked fine.

Sadly the update has caused my Canon driver to crash when starting Ekos. I think there was a comment about this already. When I get a moment I'll go back and reread the thread but for now the system appears to be unusable.

Read More...

The libev-dev part worked but update_indi_core still looks a bit weird:

stellarmate@stellarmate:~ $ sudo apt-get -y install libev-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libev-dev is already the newest version (1:4.25-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
stellarmate@stellarmate:~ $ update_indi_core
Already up to date.
make: *** No targets specified and no makefile found. Stop.
make: *** No rule to make target 'install'. Stop.
stellarmate@stellarmate:~ $

Read More...

Jasem,
I attempted the update_indi_core but it failed. According to the Stellarmate software updater this is version 1.7.1 stable channel. I hadn't used the device since last March, so 4 months ago. I did a full update and rebooted before running this update_indi_core command:

Setting up manpages-dev (4.16-2) ...
Setting up libgsl-dev (2.5+dfsg-6) ...
Setting up libcfitsio-dev:armhf (3.450-3) ...
Setting up libfftw3-bin (3.3.8-2) ...
Setting up libalgorithm-diff-perl (1.19.03-2) ...
Setting up libnova-dev-bin (0.16-4) ...
Setting up libnova-dev:armhf (0.16-4) ...
Setting up libusb-1.0-doc (2:1.0.22-2) ...
Setting up libjbig-dev:armhf (2.1-3.1+b2) ...
Setting up linux-libc-dev:armhf (1:1.20220308~buster-1) ...
Setting up libusb-1.0-0-dev:armhf (2:1.0.22-2) ...
Setting up libcurl4-gnutls-dev:armhf (7.64.0-4+deb10u2) ...
Setting up libfakeroot:armhf (1.23-1) ...
Setting up dpkg-dev (1.19. ...
Setting up fakeroot (1.23-1) ...
update-alternatives: using /usr/bin/fakeroot-sysv to provide /usr/bin/fakeroot (fakeroot) in auto mode
Setting up liberror-perl (0.17027-2) ...
Setting up libasan5:armhf (8.3.0-6+rpi1) ...
Setting up libuv1:armhf (1.24.1-1+deb10u1) ...
Setting up liblzma-dev:armhf (5.2.4-1+deb10u1) ...
Setting up libubsan1:armhf (8.3.0-6+rpi1) ...
Setting up librhash0:armhf (1.3.8-1) ...
Setting up git-man (1:2.20.1-2+deb10u3) ...
Setting up cmake-data (3.16.3-3~bpo10+1) ...
Setting up libc-dev-bin (2.28-10+rpt2+rpi1) ...
Setting up libalgorithm-diff-xs-perl (0.04-5+b1) ...
Setting up libfftw3-dev:armhf (3.3.8-2) ...
Setting up libcfitsio-doc (3.450-3) ...
Setting up libcc1-0:armhf (8.3.0-6+rpi1) ...
Setting up libjsoncpp1:armhf (1.7.4-3) ...
Setting up libtiffxx5:armhf (4.1.0+git191117-2~deb10u4) ...
Setting up libalgorithm-merge-perl (0.08-3) ...
Setting up git (1:2.20.1-2+deb10u3) ...
Setting up libgcc-8-dev:armhf (8.3.0-6+rpi1) ...
Setting up cmake (3.16.3-3~bpo10+1) ...
Setting up libc6-dev:armhf (2.28-10+rpt2+rpi1) ...
Setting up libstdc++-8-dev:armhf (8.3.0-6+rpi1) ...
Setting up gcc-8 (8.3.0-6+rpi1) ...
Setting up gcc (4:8.3.0-1+rpi2) ...
Setting up libjpeg62-turbo-dev:armhf (1:1.5.2-2+deb10u1) ...
Setting up zlib1g-dev:armhf (1:1.2.11.dfsg-1+deb10u1) ...
Setting up g++-8 (8.3.0-6+rpi1) ...
Setting up libjpeg-dev (1:1.5.2-2+deb10u1) ...
Setting up libtiff-dev:armhf (4.1.0+git191117-2~deb10u4) ...
Setting up g++ (4:8.3.0-1+rpi2) ...
update-alternatives: using /usr/bin/g++ to provide /usr/bin/c++ (c++) in auto mode
Setting up build-essential (12.6) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.28-10+rpt2+rpi1) ...
ldconfig: file /usr/lib/arm-linux-gnueabihf/libmtpricoh.so.9 is truncated

ldconfig: file /usr/lib/arm-linux-gnueabihf/libRicohCameraSDKCpp.so.1.1.0 is truncated

ldconfig: file /usr/lib/arm-linux-gnueabihf/libRicohCameraSDKCpp.so is truncated

ldconfig: file /usr/lib/arm-linux-gnueabihf/libmtpricoh.so is truncated

ldconfig: file /usr/lib/arm-linux-gnueabihf/libmtpricoh.so.9.3.0 is truncated

ldconfig: file /usr/lib/arm-linux-gnueabihf/libRicohCameraSDKCpp.so.1 is truncated

Cloning into 'indi'...
remote: Enumerating objects: 875, done.
remote: Counting objects: 100% (875/875), done.
remote: Compressing objects: 100% (725/725), done.
remote: Total 875 (delta 209), reused 506 (delta 136), pack-reused 0
Receiving objects: 100% (875/875), 2.70 MiB | 4.18 MiB/s, done.
Resolving deltas: 100% (209/209), done.
-- The C compiler identification is GNU 8.3.0
-- The CXX compiler identification is GNU 8.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test COMPATIBLE_FORTIFY_SOURCE
-- Performing Test COMPATIBLE_FORTIFY_SOURCE - Success
fatal: No names found, cannot describe anything.
-- Looking for mremap
-- Looking for mremap - found
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
CMake Error at cmake_modules/FindPackageHandleStandardArgs.cmake:148 (message):
Could NOT find Libev (missing: LIBEV_LIBRARY LIBEV_INCLUDE_DIR)
Call Stack (most recent call first):
cmake_modules/FindPackageHandleStandardArgs.cmake:388 (_FPHSA_FAILURE_MESSAGE)
cmake_modules/FindLibev.cmake:36 (find_package_handle_standard_args)
CMakeLists.txt:155 (find_package)


-- Configuring incomplete, errors occurred!
See also "/home/stellarmate/Projects/build/indi-core/CMakeFiles/CMakeOutput.log".
See also "/home/stellarmate/Projects/build/indi-core/CMakeFiles/CMakeError.log".
make: *** No targets specified and no makefile found. Stop.
make: *** No rule to make target 'install'. Stop.
stellarmate@stellarmate:~ $

Read More...

Thanks Jerry. To be clear, the mount does work. It has accuracy limitations that aren't out of line with its price, and as I say, if I'm shooting a single target an evening then as long as I look after centering every couple of hours I've managed a few nice shots. However I had hoped that with Stellarmate I could shoot 2 or 3 targets each evening which so far I just cannot do. Possibly Astroberry of some other computer solution would be better but I've never gotten the plate solver to work automatically with Stellarmate and the drift is way worse (FOR ME!!!) with Stellarmate than the SynScan phone app so I'm never up for much more than 4 hours a night - set it up, run 2 hours, recenter, run 2 hours, shut down.

I had hoped that, being a low cost mount, there'd be a few people anyway using it with the whole Ekos/Indi infrastructure but apparently not.

In the next month or so I'll start gearing up for next winter and clearer skies. Maybe I'll do better this year.

Read More...