Tim replied to the topic 'Indi Support for Bullseye 64 bit RPI4' in the forum. 10 months ago

Hi Richard,

RE: your post #80320 above, this section:

$ ~/Projects/build/libasi $ mkdir -p ~/Projects/build/indi-asi
$ ~/Projects/build/libasi $ cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Debug ~/Projects/indi-3rdparty/indi-asi
CMake Error: The source "/home/pi/Projects/indi-3rdparty/indi-asi/CMakeLists.txt" does not match the source "/home/pi/Projects/indi-3rdparty/libasi/CMakeLists.txt" used to generate cache. Re-run cmake with a different source directory.

It seems you are trying to use the build directory you used (successfully...) for libasi to also make indi-asi.  Did you neglect to 'cd ~/Projects/build/indi-asi' after you created the directory in the first command, there?

Read More...

I didn't try with chrony.  Hopefully this helps if you try NTP...

My ntp.conf includes:

# Server from shared memory provided by gpsd
server 127.127.28.0 minpoll 4 maxpoll 4 prefer
fudge 127.127.28.0 refid GPS stratum 4
fudge 127.127.28.0 flag1 1

The flag1 parameter is to overcome the panic if the time is too far out of sync.

As mentioned above, the NTP shared memory only starts to get time from my GPS device after I wake it up with a client software such as gpsmon or cgps.  Otherwise, the system will sit there with no time source.  Starting gpsd in daemon mode fixes this, however, my indiserver indi_gpsd doesn't work then (if I could specify the indi_gpsd to connect to the network socket, rather than try to own the USB device, maybe that would work?)

Hope that helps.

Read More...

Tim replied to the topic 'Indi Support for Bullseye 64 bit RPI4' in the forum. 10 months ago

$ tree -d
.
├── build
│   ├── indi-eqmod
│   │   └── CMakeFiles
│   │       ├── 3.18.4
│   │       │   ├── CompilerIdC
│   │       │   │   └── tmp
│   │       │   └── CompilerIdCXX
│   │       │       └── tmp
│   │       ├── CMakeTmp
│   │       ├── indi_azgti_telescope.dir
│   │       │   ├── align
│   │       │   │   └── chull
│   │       │   ├── scope-limits
│   │       │   └── simulator
│   │       └── indi_eqmod_telescope.dir
│   │           ├── align
│   │           │   └── chull
│   │           ├── scope-limits
│   │           └── simulator
│   ├── indi-gphoto
│   │   └── CMakeFiles
│   │       ├── 3.18.4
│   │       │   ├── CompilerIdC
│   │       │   │   └── tmp
│   │       │   └── CompilerIdCXX
│   │       │       └── tmp
│   │       ├── CMakeTmp
│   │       └── indi_gphoto_ccd.dir
│   ├── indi-gpsd
│   │   └── CMakeFiles
│   │       ├── 3.18.4
│   │       │   ├── CompilerIdC
│   │       │   │   └── tmp
│   │       │   └── CompilerIdCXX
│   │       │       └── tmp
│   │       ├── CMakeTmp
│   │       └── indi_gpsd.dir
│   ├── indi-pentax
│   │   └── CMakeFiles
│   │       ├── 3.18.4
│   │       │   ├── CompilerIdC
│   │       │   │   └── tmp
│   │       │   └── CompilerIdCXX
│   │       │       └── tmp
│   │       ├── CMakeTmp
│   │       └── indi_pentax.dir
│   ├── libasi
│   │   └── CMakeFiles
│   │       ├── 3.18.4
│   │       │   ├── CompilerIdC
│   │       │   │   └── tmp
│   │       │   └── CompilerIdCXX
│   │       │       └── tmp
│   │       ├── CMakeTmp
│   │       ├── imported_ASICamera2.dir
│   │       ├── imported_EAFFocuser.dir
│   │       ├── imported_EFWFilter.dir
│   │       └── imported_USB2ST4Conv.dir
│   ├── libpktriggercord
│   │   └── CMakeFiles
│   │       ├── 3.18.4
│   │       │   └── CompilerIdC
│   │       │       └── tmp
│   │       ├── CMakeTmp
│   │       ├── pktriggercord.dir
│   │       │   └── src
│   │       │       └── src
│   │       │           └── external
│   │       │               └── js0n
│   │       └── udev_rules.dir
│   └── libricohcamerasdk
│       └── CMakeFiles
│           ├── 3.18.4
│           │   ├── CompilerIdC
│           │   │   └── tmp
│           │   └── CompilerIdCXX
│           │       └── tmp
│           └── CMakeTmp
└── indi-3rdparty-1.9.3

The cmake and make commands were given from the build/libasi/ working directory.

Read More...

I can't comment regarding Stellarmate, but I do have an RPi system with a USB GPS (Ublox 7) that I have working for location and time source.

The best I have configured this so far is to have the gpsd.socket service active - but do not start the gpsd daemon and own the GPS device, if I do that, then my indi_gpsd driver won't seem to work.  I have configured NTP to use the time that gpsd dumps to shared memory (I don't have PPS available) as its time source.  I manually start 'gsmon' or 'cgps', then the time dumps begin to appear in 'ntpshmmon' soon after.  I can use 'indiserver indi_gpsd' in this configuration.

Read More...

Tim replied to the topic 'Indi Support for Bullseye 64 bit RPI4' in the forum. 10 months ago

In case this helps, I had no trouble building the libasi from indi-3rdparty v1.9.3.  This was on the same Raspberry Pi OS Bullseye 64bit system that I used to test Jerry's script (above, with some feedback provided on his Github issues page).

$ cmake ../../indi-3rdparty-1.9.3/libasi
-- The C compiler identification is GNU 10.2.1
-- The CXX compiler identification is GNU 10.2.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: /home/jesus/Downloads/indi-3rdparty/build/libasi
$ make
Scanning dependencies of target imported_USB2ST4Conv
[  8%] Generating libUSB2ST4Conv.so.1.0
[ 16%] Generating libUSB2ST4Conv.so.1
[ 25%] Generating libUSB2ST4Conv.so
[ 25%] Built target imported_USB2ST4Conv
Scanning dependencies of target imported_EAFFocuser
[ 33%] Generating libEAFFocuser.so.1.4
[ 41%] Generating libEAFFocuser.so.1
[ 50%] Generating libEAFFocuser.so
[ 50%] Built target imported_EAFFocuser
Scanning dependencies of target imported_EFWFilter
[ 58%] Generating libEFWFilter.so.1.7
[ 66%] Generating libEFWFilter.so.1
[ 75%] Generating libEFWFilter.so
[ 75%] Built target imported_EFWFilter
Scanning dependencies of target imported_ASICamera2
[ 83%] Generating libASICamera2.so.1.20.2
[ 91%] Generating libASICamera2.so.1
[100%] Generating libASICamera2.so
[100%] Built target imported_ASICamera2
$ sudo make install
[ 25%] Built target imported_USB2ST4Conv
[ 50%] Built target imported_EAFFocuser
[ 75%] Built target imported_EFWFilter
[100%] Built target imported_ASICamera2
Install the project...
-- Install configuration: ""
-- Installing: /lib/udev/rules.d/99-asi.rules
-- Installing: /usr/local/include/libasi/ASICamera2.h
-- Installing: /usr/local/include/libasi/EFW_filter.h
-- Installing: /usr/local/include/libasi/USB2ST4_Conv.h
-- Installing: /usr/local/include/libasi/EAF_focuser.h
-- Installing: /usr/local/lib/libASICamera2.so
-- Installing: /usr/local/lib/libASICamera2.so.1
-- Installing: /usr/local/lib/libASICamera2.so.1.20.2
-- Installing: /usr/local/lib/libEFWFilter.so
-- Installing: /usr/local/lib/libEFWFilter.so.1
-- Installing: /usr/local/lib/libEFWFilter.so.1.7
-- Installing: /usr/local/lib/libUSB2ST4Conv.so
-- Installing: /usr/local/lib/libUSB2ST4Conv.so.1
-- Installing: /usr/local/lib/libUSB2ST4Conv.so.1.0
-- Installing: /usr/local/lib/libEAFFocuser.so
-- Installing: /usr/local/lib/libEAFFocuser.so.1
-- Installing: /usr/local/lib/libEAFFocuser.so.1.4

Read More...

Tim replied to the topic 'Indi Support for Bullseye 64 bit RPI4' in the forum. 10 months ago

Hi Richard,

if your browse around Jerry Black's Github page (already linked above) you should find an answer to what the script installs, as well as some helpful information on how to run it, with the various parameters ranging from "all" to the specific sections, if you would like to step through it. There is the readme text, as well as comments in the script itself. Studying these before you download/run it might be helpful.

As far as running the script, you will need to download it then rename it (replace the .txt extension with .sh). Your GUI file explorer program could do this. Then go to your terminal emulator and use your keyboard to interact. You will want to use the "cd" command (example only: "cd Downloads") to change your working directory to wherever you downloaded the script, and the "chmod" command (example only: "chmod u+x buildKstarsNightlyFromGit_Bullseye.sh") may be required to set the permissions on the script file to be executable.

Hope that helps.

Read More...

Tim replied to the topic 'Indi Support for Bullseye 64 bit RPI4' in the forum. 12 months ago

No weak links mate, I'm sure we'll both learn something.
PM sent.

Read More...

Tim replied to the topic 'Old Pentax driver' in the forum. 12 months ago

Thanks smile.png

Even the "old" is new to me!  I only recently discovered INDI and first plugged my Pentax K-1 to it a couple of days ago.  As far as I've been able to work out, this camera isn't supported by libgphoto2 and the Ricoh API which should let me use PTP mode is not available in ARM64.  To be honest I'm not sure what I'm missing out on with either of those but I was happy enough to get it working with the "new?" indi_pentax driver and MSC mode.

I hope you get your K5 working back the way you liked.

If "Pentax believes in the future of SLR photography", I hope Ricoh believes in the future of ARM architecture grin.png

Read More...

Tim replied to the topic 'Old Pentax driver' in the forum. 12 months ago

Afraid I can't answer your question about the "old" file, but on my Bullseye arm64 machine /usr/bin/indi_pentax_ccd is just a link to /usr/bin/indi_gphoto_ccd

The indi_gphoto_ccd driver was made from indi_gphoto under the indi-3rdparty source code.

Read More...

Tim replied to the topic 'Indi Support for Bullseye 64 bit RPI4' in the forum. 12 months ago

Hi Jay,

do you have a spare SD card that you can use for a fresh Raspbian Bullseye arm64 install?  I would be glad to step through Jerry Black's script together over private message.  The only way I can see it working is if we start from the same place and work synchronously.

We might come up with some useful feedback for the script and arm64 build, and you should end up with a working environment and experience to go ahead and build specific projects yourself in future.

Read More...

I'm having the same trouble.  Seems like it is not supported - if I understand, it is because the Ricoh API isn't available for the architecture we are running.

Read More...

Tim replied to the topic 'Indi Support for Bullseye 64 bit RPI4' in the forum. 12 months ago

I see the OP has a few options by now.

I just thought to add that I was able to natively build INDI v1.9.3 with some INDI 3rd party drivers, stellarsolver v1.8 and finally KStars (github commit 6782a28d34d354ba1a73f173afeffbe0157bea15) on a Raspberry Pi 400 (4GB RAM) running Debian Buster arm64.  I am novice and learning to use INDI/KStars; things seem to be working but I can't say I've tested thoroughly.

I went through each step manually, referring to the build instructions from each project as a guide.  It went smoothly, however I scribbled some notes that I think related to packages I had to install instead/in-addition-to some similarly-named ones in the instructions: kio-dev, libqt5datavisualization5-dev, libkf5notifyconfig-dev

My 4GB Pi ran out of RAM while making KStars with -j4, but succeeded on a retry with -j1.

Read More...