Get Connected!

Come and join our community. Expand your network and get to know new people!

Sorry, we currently have no events.
View All Events

Thanks for pointing that out.
I had not seen that article.

Yesterday I reported this matter to BTS at KStars. It appears that the source has already been corrected.

Read More...

If it helps, my usual preference for my own system is to use Ubuntu Mate on the Pi, not Raspbian. With Ubuntu MATE, you can use the PPA and install everything in much simpler ways. I have another script on the Repo you used that handles ubuntu, and it is much simpler and takes much less time. On Raspbian, you have to build everything, and if you are not comfortable with diagnosing problems with building software or used to doing it, I would probably recommend the ubuntu route.
In terms of the Terminal Scrollback, if you didn't save it, then it is probably gone. I usually try to keep it open until I check that the installation worked before closing it. While it is still open, you can save it as a text file if needed.

If you want to check if the software installation worked, you could go to terminal and type kstars and see if it runs. If not, maybe go into the astroroot folder, look in the kstars-build folder and see if kstars was built there. if so, you could go there in terminal and try ./kstars to see if it runs.

Read More...

It took well over an hour for the Pi to run the script through, or whatever it did do. But I guess that stuff was built, and it did not only set up the folders.
I did quickly look through of everything written in the terminal, but given that there were probably thousands of rows and I actually did not really not know what to look for there could very well possible be tons of problem that I missed. Is it possible everything stated in the terminal while running the script is saved somewhere so that one can look through it afterwards?

Sure, it is possible that it simply did not manage to create desktop shortcuts. If so, how do I create them myself?

I also have an SD card setup with Astroberry. So, for reference, I booted that up and looked where the kstars shortcut in Astroberry pointed to on the SD. The target folder was a folder called "application" which contained a type of object(again I do not know the proper terminology) for each of the programs installed in Astroberry, that is kstars, PHD2, internet browser and what not. The corresponding folder on my new installation had all the Raspbian regulars but all of the program that was supposed to be installed by the script were missing.

I am a Windows guy and pretty much completely Linux illiterate and I do not really have a clue how to proceed.

Read More...


Hi Thomas,

I have not updated the focuser’s firmware. Just Stellarmate.

Thanks,

Read More...

Hi Thomas,

I have not updated the focuser’s firmware. Just Stellarmate.

Thanks,

Read More...

That does appear to be the new firmware, there were some issues:

www.indilib.org/forum/focusers-filter-wh...-github-release.html

But it is supposed to be resolve with an updated indi driver .

Read More...

On Raspbian, all the astrophotography software needs to be built from scratch since there isn't anything like the PPA for Raspbian and the software in the package managers for Debian which Raspbian is built on is way out of date. From what you posted here, it sounds like you built a good deal of the software most likely. Did you have any information about any errors that might have printed to the console? It is possible that it all built perfectly and you just didn't get any icons for running it on the desktop. Maybe something about the Desktop on Raspbian has changed?

Read More...

Crashes on startup with a missing libindi1 library. Symbolically linking 1 to 2 indilib solves the problem. Not sure where to report this. So starting here.

Read More...

I was able to fix this. It appears that when I installed TheSkyX for my paramount (on the same ubuntu install), it wouldn't run unless I copied libssl.so.1.1/libcrypto.so.1.1 into my x86_64 lib folder. But apparently this breaks Kstars in several ways, even though the newer libraries are also present on the system. So now I need to figure out how to make TheSkyX latest x86 linux download work. So far symbolic linking the library to the newer version doesn't work, nor does copying those libraries into the TheSkyX folders. Not that this is an issue for this forum.

Now a new post is needed, because the Maxdomeii indi driver crashes due to missing libindi1 driver.

Thanks for anyone who spent any time thinking about this one. Fixed it myself.

Read More...

I have tried this script on a Raspberry Pi 4 running Raspbian Bullseye 64-bit. One issue is that it messes up my wifi and lan connections, network manager never starts on its own. This I can easily fix myself.
However, a more devestating problem is that none of the astrophotgraphy related software seems to be built/installed(or whatever the terminology is) correctly. A folder containing several gigabytes of data called Astroroot is created which does contain a set of folders named after the various astrophotography software. But I can not find any way of running them. There are no icons created either on the desktop or in the "start menu". How do I find out what has gone wrong so that I can fix it?

Read More...

Does someone have a solution for this?
I'm on Ubuntu and it's been a pain to set up kstars, multiple crashes and so on.
I downloaded the index files for plate solving, but I lost the FOV for the camera and I can't even plate solve or anything , although I have nearly all the index files downloaded.

Polar alignment says "FOV must be 10" or greater".



I know there was a default link in the index file location, but I replaced that with my local drive location.

How do I solve this? Do I have to delete Kstars and reinstall?

Read More...

I may be having the same issue as you, but I believe it is the fault of Ubuntu and not INDI.

Running Ubuntu 22.04 MATE on a Beelink U59 mini-pc. The OS is up to date.
The QHY5iii462C is the OAG guide camera for my RC6. Had that rig out last night, the previous time out for it was early January - all was OK then. (this fits lanco's timeline)

On starting up, the camera did not appear when I ran lsusb. I re-seated plugs, rebooted the computer, powered everything down and back up, went in and fetched another usb cable, even plugged the usb cable that runs to the on-scope hub directly into the QHY camera - nothing. Obviously not an INDI driver issue - the camera simply is not there.

So I brought everything in and installed the QHY all-in-one windows package onto a windows desktop. Plugged the QHY5iii462C into that machine - and it works fine in the QT-Capture program. So it seems to not be actually dead.

Back to the Ubuntu machine, I disconnected all other external usb devices and plugged the camera in using the same cable that just worked - still no sign of it. Ran dmesg and cannot find any hint of the camera or even of a failed attempt to connect to a usb device. (the dmesg file is attached, because I don't really know my way around linux boot logs and could easily have missed it).

Any ideas? Some Ubuntu update in the 4 weeks that broke the camera's ability to be seen? I do not know how to roll back the recent Ubuntu updates.

File Attachment:

File Name: dmesg_02-06-23.txt
File Size: 78 KB


Read More...

I finally managed to get the SBIG ST10 guider connected:

Apparently there is no need for a second optical train for the second (guider) camera chip. (and strangely no longer need to select SBIG-STI for the guider camera).
I changed the profile to both main and guider = SBIG-CCD
When I then also select the primary optical train under the guiding tab in EKOS, the screen is no longer greyed out and I could capture guiding chip images.

Tom

Read More...

I've had the devil's own time getting INDI to work with an Orion HDX110 EQ-G mount. The hand controller is defective. It doesn't even work as a hand controller, let alone a PC interface. I got an ST4 to USB converter from Astro Gadget, since Shoestring Astronomy didn't answer emails. It uses the indi_ardust driver, which does not seem to be a part of INDI full, or at least I don't see it where all the other drivers are. I acquired the source from Github, but the make step coughed up a lung when it could not find defaultdevice.h. The full set of responses is:

I found a defaultdevice.h bu it is (a) derpecated, and (b) putting it in the same folder as ardust.h didn't make it any more findable. Not being a programmer, I'm stymied at this point. I've been working on this mount for months, and I'm about over it. What am I doing wrong? Thanks!

Read More...

nou replied to the topic 'XISF support' in the forum. 9 hours 10 minutes ago

Hello you can now test it.
First clone LibXISF gitea.nouspiro.space/nou/libXISF run usual cmake commands

cmake -B build -S . && make && sudo make install

Then clone this branch of indi, build and install
github.com/nouspiro/indi/tree/feature/xisf_support
Then fetch latest master from indi-3rdparty compile and install.
Lastly clone and compile this kstars from here invent.kde.org/nou/kstars/-/tree/feature/xisf_support

Read More...

I am happy you got it resolved.

It looks to me like the python modules were setup without a virtual environment. The setup.sh script assumes a virtual environment will be used. If it is not, the gunicorn service will also have to be updated.

Read More...

Tamas Tordai replied to the topic 'I'm desperate!' in the forum. 11 hours 6 minutes ago

I realized one important thing: the error only occurs if the file name contains the "target name" (%t).
This is what I use now in the format line: /%t/L_%F_%e_ So everything is fine!

Read More...

Hi Folks,
Kstars on PC has been down for a few weeks now and I'm trying to update it, and it's giving me problems with the repository.
I have linux ubuntu 20.04 and until recently Kstars was working well, but now when I update it it tells me that it can't find some files in the repository (message like: not find 403..., not find 406..., ). What do I have to do?
Delete it? how should I do it, well.
Reinstall it? but appear the same "find" problems.
Thanks,
Pep

Read More...