×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

AstroPi3 Scripts revised

  • Posts: 73
  • Thank you received: 8
Sounds good. I'll comment out the line and the section where it installs and carry on. Then later I'll attempt to re-install.

BTW, have you looked further into adding ASTAP install and their stellar catalog install as part of your script? Even if it is an option you could querry for "Install ASTAP and Catalog?" [Y/N] or whatever. That would be great.

Thanks!
4 years 4 months ago #45875

Please Log in or Create an account to join the conversation.

  • Posts: 1067
  • Thank you received: 140

Replied by AstroNerd on topic AstroPi3 Scripts revised

Just a request really....
I have used your script, and the whole set up is really good, but is there another small script that could automate the update process, but just running a script and it updating just Kstars and INdI, rather than the manual way of doing the git pull, then Make install on each one in turn..?.
Just an idea... :)
4 years 4 months ago #45880

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226

Replied by Andrew on topic AstroPi3 Scripts revised

The portion of the script that builds PHD2 includes the condition -DOPENSOURCE_ONLY=1 which is not used by default and should be removed. This option builds a version of PHD2 that does not include the QHY, ZWO and other camera binaries, thus the list of internally supported cameras is limited; excluding ZWO ASI, ToupTek, QHY 5, and Omegon Pro cameras from the list.
The following user(s) said Thank You: Rob Lancaster
4 years 4 months ago #46207

Please Log in or Create an account to join the conversation.

  • Posts: 2876
  • Thank you received: 809
Thanks for the heads up! Just changed that!
4 years 4 months ago #46213

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

I am on AstroBerry 2.0. I ran the Raspian script as AstroBerry 2.0 is Buster based. The script dies at “ 12% Building CXX indifilterwheel.ccp.o. This is an RPI3 b+. CPU goes to 100% and the helm is locked.
4 years 4 months ago #46314

Please Log in or Create an account to join the conversation.

  • Posts: 238
  • Thank you received: 15

Replied by Tom on topic AstroPi3 Scripts revised

Another issue of applying AstroPi3 script n top of Astroberry is my QHY ccd cannot detect in Astroberry. :( Others all okay. Any idea?
4 years 4 months ago #46334

Please Log in or Create an account to join the conversation.

  • Posts: 1067
  • Thank you received: 140

Replied by AstroNerd on topic AstroPi3 Scripts revised

Why would you even need to run this script ontop of Astroberry, it’s already all there... I’m confused....
4 years 4 months ago #46337

Please Log in or Create an account to join the conversation.

  • Posts: 2876
  • Thank you received: 809
I am likewise a little confused, but it should work if they want to run it unless there is some custom installation stuff that Astroberry has. One issue I have seen on a couple of systems is that the installation directory for the libraries is different and so when building, the Indi drivers are looking for them in one directory when they were installed in another directory. This sort of thing is not actually a problem with my script but a build issue for INDI, because for the most part, my script is using the standard installation procedure for INDI.
4 years 4 months ago #46338

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

Because the gadgets of AstroPi3 on AstroBerry 1.1 are not on 2.0. That is why. The serial tool and others were not there. Although, the serial tool needs help. It’s better than nothing.

I miss the log viewer. Raspbian does not have one. The tool dmesg is ok. I want to see specific things.
4 years 4 months ago #46340

Please Log in or Create an account to join the conversation.

  • Posts: 1067
  • Thank you received: 140

Replied by AstroNerd on topic AstroPi3 Scripts revised

:S :S
The following user(s) said Thank You: John Robison
4 years 4 months ago #46341

Please Log in or Create an account to join the conversation.

  • Posts: 2876
  • Thank you received: 809
If by gadgets you are referring to the scripts that I put into the utilities folder, basically those are scripts that I wrote to make it easier to set up things like persistent serial ports. They could probably use some improvement, but as you say they are better than nothing. If you have suggestions for improvement or changes you would like to make for them, you can let me know.

As for the QHY driver, that is probably a general INDI problem. Did all of the drivers including QHY build or were there errors in the build? Also, can you see where the qhy library got installed? As I was mentioning earlier, sometimes on some systems the library gets installed in an odd place and then the drivers are looking in the wrong place to link them. I need to mention that to Jasem.

For the frozen one, I would probably just run it again. See if it has an issue at a similar spot the second time.

Thanks,

Rob
4 years 4 months ago #46349

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

Yes. This command in UDEV rules helped solve my UBLox GPS and AstroEQ conflict. ATTRS {KERNEL==ttyACM*} added ttyACM1. The ttyACM0 was consumed by the GPS. Only one ttyACM type is given in Buster. To get another, the rules have to be added. Basically, serial communications requires a dedicated COM port. Throwing everything to SUBSYSTEM==usb is a free for all for the one ttyACM, ttyACM0. Last one standing is left out.

The QHYCCD issue is resolved after the update from yesterday occurred to KSTARS. I conducted a test run yesterday with AstroBerry 2.0 and no ret=-1 occurred. I got a big white screen to resolve. I don’t think ASTAP and Astrometry have any images of out of focus white walls. It was very fast also.
4 years 4 months ago #46357

Please Log in or Create an account to join the conversation.

Time to create page: 0.675 seconds