I also did a git pull, and tried to build it using the qt creator. The cmake fails with this:

-- Found CFITSIO: /usr/lib/arm-linux-gnueabihf/libcfitsio.so
-- Found libsbig: /usr/lib/arm-linux-gnueabihf/libtoupcam.so
-- Found libaltaircam: /usr/lib/arm-linux-gnueabihf/libaltaircam.so
CMake Error at /home/astroberry/Projects/indi/cmake_modules/FindSTARSHOOTG.cmake:43 (message):
StarshootG not found. Please install StarshootG Library
www.indilib.org
Call Stack (most recent call first):
CMakeLists.txt:17 (find_package)

You want to hire me as a tester?

John

Read More...

I know this is volunteer work for you, and I really do appreciate the hours it takes to make this available and functional for all of us. I worked in software development for all my career and I understand the complexities in getting this done. So thank you for your efforts.

One suggestion - it would be really nice if the old driver stayed around until the new one was usable. Put the new one in place. Get user feedback that they can run it, then delete the old ones after a week or two. I am going to have the first clear night in a couple of weeks tonight and I will not be able to use this driver or my guide scope.

Here is what I get. No change to what I reported yesterday. I know I should not have had to add the repository again, but I did that just to confirm I got the right one. Note - I had to delete http from the beginning of many output lines because this messaging app said I had too many links in this message.

astroberry@astroberry:~/Projects/indi/3rdparty/indi-toupbase$ sudo add-apt-repository ppa:mutlaqja:ppa
Latest INDI Library and drivers!

This PPA is for stable Ekos & INDI drivers releases.
More info: launchpad.net/~mutlaqja/+archive/ubuntu/ppa
Press [ENTER] to continue or ctrl-c to cancel adding it

gpg: keyring `/tmp/tmpfj37c5t6/secring.gpg' created
gpg: keyring `/tmp/tmpfj37c5t6/pubring.gpg' created
gpg: requesting key 3F33A288 from hkp server keyserver.ubuntu.com
gpg: /tmp/tmpfj37c5t6/trustdb.gpg: trustdb created
gpg: key 3F33A288: public key "Launchpad INDI" imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
OK
astroberry@astroberry:~/Projects/indi/3rdparty/indi-toupbase$ sudo apt-get update
Hit:1 //ppa.launchpad.net/flexiondotorg/minecraft/ubuntu xenial InRelease
Hit:2 //ports.ubuntu.com xenial InRelease
Hit:3 //ports.ubuntu.com xenial-updates InRelease
Hit:4 //ppa.launchpad.net/mutlaqja/libgphoto2/ubuntu xenial InRelease
Hit:5 //ports.ubuntu.com xenial-security InRelease
Hit:6 //ports.ubuntu.com xenial-backports InRelease
Hit:7 //ppa.launchpad.net/mutlaqja/ppa/ubuntu xenial InRelease
Hit:8 //ppa.launchpad.net/pch/phd2/ubuntu xenial InRelease
Hit:9 //ppa.launchpad.net/ubuntu-mate-dev/welcome/ubuntu xenial InRelease
Hit:11//ppa.launchpad.net/ubuntu-mate-dev/xenial-mate/ubuntu xenial InRelease
Hit:12//ppa.launchpad.net/ubuntu-pi-flavour-makers/ppa/ubuntu xenial InRelease
Reading package lists... Done
astroberry:~/Projects/indi/3rdparty/indi-toupbase$ sudo apt-get install indi-toupbase
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package indi-toupbase
astroberry@astroberry:~/Projects/indi/3rdparty/indi-toupbase$

Read More...

Jasem,

I followed the new instructions on the Toupcam driver page, and got a message "E: Unable to locate package indi-toupbase"

Considering going back to a Windows 10 machine and ASCOM....

John

Read More...

Thanks for posting this announcement, it explains the issues I have been having. But there may still be files and/or instructions missing.

I did a git update. then tried to build the toupbase driver several ways:
1) per the instructions on the indilib web page under Devices - Cameras - Toupcam that said to do: sudo apt-get update / sudo apt-get install indi-toupcam (I tried with both that and indi-toupbase).
*********************************
astroberry@astroberry:~/Projects/indi/3rdparty/indi-toupbase$ sudo apt-get install indi-toupbase
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package indi-toupbase
astroberry@astroberry:~/Projects/indi/3rdparty/indi-toupbase$ sudo apt-get install indi-toupcam
Reading package lists... Done
Building dependency tree
Reading state information... Done
indi-toupcam is already the newest version (0.1~201907030401~ubuntu16.04.1).
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
astroberry@astroberry:~/Projects/indi/3rdparty/indi-toupbase$
*****************************

Then I tried in qt Creator, opened /home/astroberry/Projects/indi/3rdparty/indi-toupbase/CMakeLists.txt and I got this while trying to run cmake:
*****************************
See also "/home/astroberry/Projects/indi/3rdparty/indi-toupbase-build/CMakeFiles/CMakeOutput.log".
See also "/home/astroberry/Projects/indi/3rdparty/indi-toupbase-build/CMakeFiles/CMakeError.log".
CMake Error at /home/astroberry/Projects/indi/cmake_modules/FindSTARSHOOTG.cmake:43 (message):
StarshootG not found. Please install StarshootG Library
www.indilib.org
Call Stack (most recent call first):
CMakeLists.txt:17 (find_package)
****************************************
The files that were loaded when I did the git pull in the indi-toupbase directory are:

astroberry@astroberry:~/Projects/indi/3rdparty/indi-toupbase$ ls
CMakeLists.txt COPYING.LGPL indi_toupbase.h README.md
config.h.cmake indi_toupbase.cpp indi_toupbase.xml.cmake

What is next? How do I build this for Toupcam cameras?

John

Read More...

I am trying to start the toupcam driver (had it working a week ago but I had to rebuild the system). Now I get this in the log file:

[2019-08-15T00:53:30.348 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "dp->name: indi_toupcam_ccd - tDriver: indi_toupcam_ccd"
[2019-08-15T00:53:30.348 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2019-08-15T00:53:31.342 CEST DEBG ][ org.kde.kstars.indi] - Adding managed driver "ToupCam"
[2019-08-15T00:53:31.342 CEST DEBG ][ org.kde.kstars.indi] - Starting INDI Driver "indi_toupcam_ccd"
[2019-08-15T00:53:31.343 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "FIFO: start indi_toupcam_ccd"
[2019-08-15T00:53:31.344 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "FIFO: Starting driver indi_toupcam_ccd"
[2019-08-15T00:53:31.344 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2019-08-14T22:53:31: Driver indi_toupcam_ccd: pid=11276 rfd=5 wfd=8 efd=9"
[2019-08-15T00:53:31.344 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2019-08-15T00:53:31.347 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2019-08-14T22:53:31: Driver indi_toupcam_ccd: indi_toupcam_ccd: error while loading shared libraries: libtoupcam.so: cannot open shared object file: No such file or directory"
[2019-08-15T00:53:31.347 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2019-08-14T22:53:31: Driver indi_toupcam_ccd: stderr EOF"
[2019-08-15T00:53:31.348 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "Child process 11276 died"
[2019-08-15T00:53:31.348 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2019-08-14T22:53:31: Driver indi_toupcam_ccd: Terminated after #0 restarts."
[2019-08-15T00:53:31.348 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2019-08-15T00:53:31.349 CEST CRIT ][ org.kde.kstars.indi] - INDI driver "indi_toupcam_ccd" crashed!
[2019-08-15T00:53:52.042 CEST DEBG ][ org.kde.kstars] - Reporting new timestep value: 60
[2019-08-15T00:53:57.114 CEST DEBG ][ org.kde.kstars] - 0 StarBlocks freed from StarBlockFactory
[2019-08-15T00:53:57.154 CEST WARN ][ default] - QSqlDatabasePrivate::removeDatabase: connection 'userdb' is still in use, all queries will cease to work.
[2019-08-15T00:53:57.162 CEST DEBG ][ org.kde.kstars.indi] - INDI server disconnected. Exit code: -1
****************************************************************************************************************
It does this regardless of the connection status of the camera. I removed and re-installed both indi-full and indi-toupcam with no change in results. Other camera drivers (asi, qhy) work fine. Any ideas?

Thanks,
John

Read More...

Thanks for your response. Jasem solved this for me in another thread with this comment:

"Make sure to install libindi first either by compiling it and running sudo make install, or you can install it from the package manager:"

I am working on building a device driver, not a client which that other thread was discussing.

John

Read More...

Thanks for the response. That confirms and expands on some of my reading, so I appreciate the help.

But my confusion is this. in my system, 99-toupcam.rules contains only these lines:

ACTION=="add", ATTR{idvendor}=="0547"., RUN+="/bin/sh -c '/bin/echo 256 >/sys/module/usbcore/parameters/usbfl_memory_mb'"
# All ToupCam Devices
SUBSYSTEMS=="usb", ATTR{idvendor}++"0547", MODE="0666"

There is no list of the productid's that are served by this driver. In reading your comment above, I do see the MODE="0666" on this file. Is it possible that this is what the driver or something in either linux or the astroberry software is using to eliminate other cameras form this driver? Is it possible to read the mode value from a camera? How would I get that value for a Mallincam camera having the camera plugged into a computer?

Thanks again,
John

Read More...

Hi again,

I have an Astroberry server on RPi 3 or 3+ that I am setting up. I can network into it (with hardwire network or the astroberry WiFi link) from either a Windows 7 or a Windows 10 Home computer using either a browser or the Remote Desktop application after installing xrdp. However, when I try to access it from my Windows 10 Pro portable computer I get this while using the Remote Desktop:

I have read everything I can find including the github notes on reconfiguring the network, and I cannot figure out how to get the wifi hotspot name or password changed from astroberry . Here is what happens. (I am using Raspberry Pi 3 and 3+ units.)

1) I am using the latest Astroberry system prebuild download as of 6 August 2019 on the github site. I did an apt-get update and upgrade, and then installed xrdp to add remote desktop access. So far, so good.
Now I want to change the wifi name and password. I tried the scripts listed in the FAQ, as well as looking for the /etc/wpa_supplicant/wpa_supplicant.conf file which did not exist.
2) Whenever I add anything to a file /etc/wpa_supplicant/wpa_supplicant.conf (by clicking on the wireless icon on the top screen panel), after a reboot the system locks out all remote access - remote desktop, browser, and ssh. I can only use a keyboard and mouse connected to the Pi. Deleting that file and rebooting again restores remote access.
3) I can run the control center as administrator, and select network connections and see a Wi-Fi connection set up on vap0 with my new name and password. This information is ignored by the Ubuntu system even after reboots. The wireless is still astroberry.
4) The system also locks out remote access if I set the wifi up as a client to try to connect to another wifi network (instead of the wired LAN port). When I do this,I can use the network as superuser from the Pi but not as the astroberry user and not for any remote connections in. For instance, I can do 'sudo apt-get' and do system updates, but as user astroberry I cannot ping another computer. 'Sudo ping' works however.
5) I keep resetting the country code to 'US' but it keeps reverting to 'PL'. I am not sure where I have to set it to make it stay.

Please help if you have solved these. I am getting frustrated.

I am keeping a log of the things I have to do to make this work, and I expect to post it here when I finally get this running in hopes it can make life easier for others going through this.

John

Read More...

HI all,

I am going through the documentation and cannot find any help about this. Where is the documentation about how to make a driver understand which devices it should open and service? I do know there is a directory with rules files, but it seems incomplete as far as making a real determination.

The Toupcam driver is set up to be the driver for vendor id "0547" according to the rules files. That driver does work for my Solomark camera (product id b123) which makes sense since it was shipped with a disk of Toupcam drivers for PC and Mac systems.

The Mallincam camera I have (DS16C) that I am trying to generate a driver for also uses vendor id 0547. How does the Toupcam driver distinguish the camera product ids that it should not open?

Note the Toupcam driver also will not recognize my Orion Starshoot which is 0547:a004.

I did see that there is a rule for one product id in the 0547 vendor id within the qhyccd rules - product id 1002.

But this question is why and how does the Toupcam driver determine that it should ignore some of the cameras/ids in that vendor range?

Thanks,
John

Read More...

Jasem,
I have another question. The Toupcam driver is already set up to be the driver for vendor id "0547". That driver works for my Solomark camera (product id b123) which makes sense since it was shipped with a disk of Toupcam drivers for PC and Mac systems.

The Mallincam camera also uses vendor id 0547. How does the Toupcam driver distinguish the camera product ids that it should not open?

Note the Toupcam driver also will not recognize my Orion Starshoot which is 0547:a004.

I did see that there is a rule for one product id in the 0547 vendor id within the qhyccd rules - 1002.

But this question is why and how does the Toupcam driver ignore some of the cameras?

Thanks,
John

Read More...

Jasem, Thanks! That solved it.

John

Read More...

Hi,

Hopefully someone can tell me quickly what is wrong. Running on an Astroberry plaarform, Pi 3B. I want to extend the ToupCam driver for other cameras that use Toupcam drivers on other platforms.

I successfully pulled down the git sources form the repository and built the INDI server. But any 3rd party driver I try to build gives me this in CMake:

CMake error at /home/ .... /indi/cmake_modules/FindINDI.cmake:274 (message):
Could not find the include directory
Call Stack (most recent call first):
CMakeLists.txt:11 (find_package)

That is the call looking to find the INDI package.

Thanks for your help...
John

Read More...

Hi,

I want to create drivers that can work for Mallincam cameras, and I think I can start with the existing ToupCam drivers since the MallenCam devices are supported by ToupCam drivers in other platforms.
I downloaded (through git) the source library, and successfully build the INDI server on my Astroberry PI platform. However, trying to build any of the 3rd party packages gives me this:

CMake error at /home/ … /indi/cmake_modules/FindINDI.cmake:274 (message):

Could not find INDI include directory
Call Stack (most recent call first):
CMakeLists.txt:11 (find_package)

Line 11 is a call to find package INDI.

This comes up with either a command line build, or going through QT Creator when first loading the CMakeLists.txt file(s) and doing the CMake for the package I want to build. I suspect there is an environment variable I need to set but Ihave not been able to find it in the documentation.

Thanks for any help you can provide.
John

Read More...