Come and join our community. Expand your network and get to know new people!
With a RPi4 running Raspbian I suggest using the AstroPi3 scripts to install indi and Kstars.
Download the script (git clone from the repository) and run the setupAstroRaspbianPi.sh script.
It will set your system to a good state with useful enhancements and install KStars and Indi with their dependencies.
My experience is that it just works.
Other solutions seem to me to require far more fiddling and configuring.
The Pegasus PPB connect to my Mac , just tried.
Under Indi Control Panel, what does it show you for System Ports? - For example mine shows /dev/cu.Bluetooth......,/dev/cu.usbseria-004014 and /dev/cu.usbserial-PPB3Gxxx
For my PPB, it connect using /dev/cu.usbserial-004014, 9600 baud. Not the PPB one.
Make sure you Refresh - ScanPorts, and turn off Auto Search until you get a connection. You may have to shut down Kstars and restart for every attempt. When it connects, save settings. Auto-connect will then work if selected with that profile.
Let us know how it goes..
I am new here and glad to be here. I hope this is the right thread to post these initial questions. But anyway this is what I am up to and confused about.
I have been imaging with ZWO cameras from my Win 10 machine for a few years now. I do DSO , Lunar and Planetary. Recently I have been itching to get involved with building a meteor All Sky setup with a ZWO camera.
So I read up on some stuff and saw the Rasberry Pi 4. It seemed to fit what I wanted to do so I purchased it and just got it today. I plan on building a weatherproof box with it inside and having one of my ZWO cameras in it pretty much all the time. Now I got 3 ZWO's but only 2 would be good for my ALL SKY project. The ZWO 385mc and ZWO 290mm (Regular non mini). I use them for my imaging and only want to put them in the box I make for special occasions like media showers.
So I plan on picking up a new/used ZWO for the ALL SKY running all night or if anyone has any other ccd/cmos recomendation.
Now I tinkered around with my Rasberry PI 4 tonight and had Rasberian OS on it. I ran into some snags. and here are my questions and hoping that someone can point me in the right direction
I was able to get Fire Capture working, but it would not recognize my ZWO385mc. I tried downloading and installing the indi drivers from ZWO site and it appeared the were installed properly but still no camera recognized and tried mulitple 3.0 cables.
So before I ramble on to much, I guess I should state my first Main Goal I wish to accomplish
My Goal is to stream live sky images from my homemade All Sky Setup to my home network and have them viewable on my website or youtube channel. The website part I can manage, but it is just the software and drivers to get my Rasberry PI 4 to start capturing with the ZWO.
So with that said What OS and Software & indi drivers should I be using with the Raspberry PI 4?
Thanks in advanced
I can take a look at it. Right now I'm a bit bogged down with other projects. But it is getting into the summer now and I should have more time since my students are almost done.
You did give me an idea though Jo. So, thanks for that!
The ASI120MC-S and the EFW are connected to the USB hub on the ASI6200 and then there is one USB3 cable coming down from the ASI6200 to connect all three devices to the mini-pc. What if the USB hub on the camera has an issue that somehow only manifests on Linux and not on Windows? So I have disconnected the ASI120MC-S from the USB hub and connected it directly to the mini-pc. Well, actually I am using another USB hub because I ran out of ports but at least it is not connected via the USB hub of the ASI6200 anymore.
I am running Ekos now in the living room with the ASI6200 taking 120 sec exposures (just like last night) and the ASI120MC-S looping on 3 sec images (mimicking guiding from last night). Let's see if I run into the same issue again. If not then I will repeat the experiment but with the ASI120MC-S connected to the USB hub of the ASI6200 again to see if I can reproduce the faulty behavior that way.
I'll post here as soon as I have results.
You are demanding answers, yet I have none to give you...
But since the ASI6200 works on its own, it clearly CAN be addressed correctly.
One probably silly idea is that after multiple huge images from the 6200 have been downloaded, a buffer may be overflowing and the ASI120MC cuts in and hijacks the address of the 6200????
In short, I don't know, grasping for straws here, but this smells like something that can be solved with systematic analysis without falling for NINA's seduction...
Good question. I'll need to check that. But if that's the case then why does it work at first and only start failing after a while?
By the way, I am imaging at this very moment with a ASI1600MM-Pro Cool and guiding with an ASI120MC-S on KStarts/Ekos/INDI nightly including the update to libasi that I pushed last week and for which Jasem managed to fix the build and it's working fine.
Probably a stupid question, but if you connect the ASI6200 and the ASI120MC-S, do they show the same address in $ lsusb ?
Sounds like the driver is working fine, the problem is how the two cameras are being addressed.
wotalota wrote: Reading through the entries under indilib.org/about.html provides a good overview. You generally monitor and control the indi
drivers from a client running locally or remotely. KStars/Ekos can also be run on the Rpi although it will be under powered. More common I think is for a client to communicate remotely to a Rpi running the drivers.
The Pi3 was definitely underpowered, but the Pi4 handles Kstars with plenty of power to spare. I am running the system entirely on the Pi4 under Ubuntu 20.04 and just VNC in from inside the house or from my Phone.
The Pi4 is plenty up to the task, including plate solving (completes with in 8 seconds on average).
Are you Clyde?
I am not using the PPB, but I am sure someone will be able to help you here.
Welcome to the forum of enlightened liberated spirits.
File Attachment:File Name: indi_pegasus_ppb_212917_2020-06-05.log
File Size: 1 KB
File Attachment:File Name: SystemReport_2020-06-05.rtf
File Size: 1 KB
Hello. I really hope someone can help me. I'm running Ekos on a Mac mini and I'm having an issue with it connecting to my Pegasus Pocket Powerbox. It's connecting directly to the back of the mini, there is no hub in-between. I've confirmed that it shows up in macOS system report. In the Ekos profile editor I have Aux 1 set to Pegasus PPB. When I hit connect Ekos uses auto search to try all of the available ports, but none seem to work. I've manually gone in and tried to connect using each of the available system ports with each available baud rate option, but that doesn't work either. Please, can someone help me and Bonnie out? We need a hero!
I tried the log using: $ indiserver -l /home/tg/ indi_moonlite_focus indi_asi_ccd &
tg@:~$ cat 2020-06-05.islog
2020-06-05T21:06:35: MoonLite: [INFO] Auto search is disabled.
Started ekos with the profile set to remote/localhost connecting to the drivers
Examined the log again:
tg@:~$ cat 2020-06-05.islog
2020-06-05T21:06:35: MoonLite: [INFO] Auto search is disabled.
2020-06-05T21:07:21: MoonLite: [INFO] Detected firmware version 2.0
2020-06-05T21:07:21: MoonLite: [INFO] MoonLite is online. Getting focus parameters...
2020-06-05T21:07:21: MoonLite: [INFO] MoonLite is online.
2020-06-05T21:07:21: MoonLite: [INFO] MoonLite parameters updated, focuser ready for use.
2020-06-05T21:07:21: MoonLite: [INFO] Loading device configuration...
2020-06-05T21:07:21: MoonLite: [INFO] Device configuration applied.
2020-06-05T21:07:22: ZWO CCD ASI1600MM Pro: [INFO] Setting intital bandwidth to AUTO on connection.
2020-06-05T21:07:22: ZWO CCD ASI1600MM Pro: [INFO] CCD is online. Retrieving basic data.
2020-06-05T21:07:22: ZWO CCD ASI1600MM Pro: [INFO] The CCD Temperature is 0.000
2020-06-05T21:07:22: ZWO CCD ASI174MM Mini: [INFO] Setting intital bandwidth to AUTO on connection.
2020-06-05T21:07:22: ZWO CCD ASI174MM Mini: [INFO] CCD is online. Retrieving basic data.
2020-06-05T21:07:22: ZWO CCD ASI174MM Mini: [INFO] The CCD Temperature is 28.600
2020-06-05T21:07:22: ZWO CCD ASI1600MM Pro: [INFO] Loading device configuration...
2020-06-05T21:07:22: ZWO CCD ASI1600MM Pro: [INFO] Upload settings set to client only.
2020-06-05T21:07:23: ZWO CCD ASI1600MM Pro: [INFO] Device configuration applied.
2020-06-05T21:07:23: ZWO CCD ASI1600MM Pro: [INFO] World Coordinate System is enabled.
2020-06-05T21:07:23: ZWO CCD ASI174MM Mini: [INFO] Loading device configuration...
2020-06-05T21:07:23: ZWO CCD ASI174MM Mini: [INFO] Upload settings set to client only.
2020-06-05T21:07:23: ZWO CCD ASI174MM Mini: [INFO] Device configuration applied.
As a new user I inquired about this as well. I believe that thread is possibly what come up in searches for INDI in regards to satellite tracking.
At the time there was a script that could issue leepfrog commands, but there was not way to make corrections, and the timing, location and fine adjustments are critical.
For satellite tracking the old Alt-Az, LX200 compatible mounts is the way to go. They permit continuously variable tracking rate changes.
The Satellite Tracker on Heavenscape has been around for a long time. The original developer recently ended support, and we lost the forums. But it has since been picked up by new developers.
There is one other independent developer who has created some interesting tools called TeleTrak for satellite tracking that is capable of image feature tracking. Enabling it to follow launching rockets. But again the software was developed for LX200.
Best of luck in your search.
His YouTube channel is called Astronomy Live. User ngchunter on Cloudy Nights.
ssh into the pi and type
ps ax |grep indi
That shows me all indi apps running.
BigMac:~ dallmon$ ps ax | grep indi 44995 ?? S 0:05.89 /Applications/KStars.app/Contents/MacOS/indi/indiserver -v -p 7624 -m 300 -r 0 -f /tmp/indififocd12bf59 44996 ?? S 0:03.43 indi_simulator_telescope 44997 ?? S 0:02.40 indi_simulator_ccd 44998 ?? S 0:05.49 indi_moonlite_focus 46829 s000 S+ 0:00.01 grep indi
I believe the feature you want is being developed by Florian S. It's referenced in the first page of this post as "poor-man's focus temp compensation").
Wow, I must be one of the lucky ones. I installed ASTAP and catalogs, ticked the ASTAP checkbox in Ekos, and it has worked (nearly) flawlessly for me ever since, with just default settings and no fussing about.
I'm sure the experts here will get it all sussed for you.
Also there is a new CEM70 model out along with an integrated Guider version as well. I'm assuming this will be under model 0070 if follows other models. Don't see a EC version for the CEM70 model, probably due to having a built in guider instead. So the base model and the guider model could be under the same 0070 model number or guider version could end up 0071. Don't have the new models to test with.
I don't know if this is the same issue as mine, but it sounds similar and I have a fix in code. You can also work around it by making sure that you stop guiding before doing a slew. Here's the thread, I think you posted to that thread.