Rob Lancaster's profile

Add as Friend Send Message

Stream About me

Thanks! That’s good to know

Read More...

Those are very good mounts. My current mount is a Losmandy G11 with Gemini 1 Level IV. It is now a little dated, but is a great performer. It works great on INDI when it is set up correctly.

Read More...

I do believe this discussion thread is now not about the original topic at all, but is now about several different topics at the same time.

Read More...

fmozza wrote:
TallFurryMan wrote: Don't you still need to have it in your profile if you are using the local indiserver launched by Ekos? PHD2 still need an INDI driver, doesn't it?

-Eric

Yes PHD2 needs the indi driver. I am running indi on the RPi in the observatory and Kstars and PHD2 on my desktop.

jmh

Here is how I configure PHD2 on a raspberry Pi to not need an INDI driver for a ZWO camera (so that it doesn't have to send guide images over the network), to use the ZWO ST4 guiding cable to send the guide commands, but to still benefit from pointing information from INDI.

Oh i just reread DerPit's question. My suggestion is what he said he already did. Sorry about that. So yes, I dont know if there is a better way

Read More...

TallFurryMan wrote: Don't you still need to have it in your profile if you are using the local indiserver launched by Ekos? PHD2 still need an INDI driver, doesn't it?

-Eric

PHD2 does not need an INDI driver for a camera that it has native support for. On Linux, support for ZWO is built in to PHD2. If you are using PHD2, you dont need the guide camera to be connected to Ekos. In fact, directly connecting PHD2 to the ZWO and then not including it in the profile in Ekos will cause an increase in performance, assuming that you are running PHD2 on a raspberry pi. The reason is because then it doesnt need to send the image over the network to your client computer it just sends it right to PHD2.
This is the way i run my imaging setup.

Now as to DerPit's question about having 2 zwo cameras. . . I am not sure. I will have to think about that one. Can you try just not including the guider in the profile, and when it shows up, just not connecting to it?

Read More...

Oh you are using phd2? Why do you have your guider in the profile then? If you are running phd2 on a raspberry pi, then you can directly connect it to the camera. No need for INDI or to have the Guide camera in the ekos profile.

Read More...

In the guide module I believe you can select your guide camera as qhy and disable the receipt of guide frames from that camera

Read More...

I'm pretty sure my ZWO has always given me at least 8 bit data. This is odd.

Read More...

Outstanding Video!! It's great to see beginner friendly videos to get people started and demonstrate the power of the software and equipment we have all been working on!!

Thank you very much!

Read More...

Hi Paul,

I know how you feel, I've had my own share of Github confusions. But typically that commit message that you mention has not been a problem for me. It seems to happen often when you do a "git pull" after you have already made a pull request. I don't think it causes any problems, it just gets in the way.

I would be more concerned about it not passing all the checks like here:

travis-ci.org/indilib/indi/builds/452469..._medium=notification

But it looks like you fixed the error in the next commit.

It does currently say there is an error, but if you look at the cause, it is an issue with free type not downloading properly which has nothing to do with your code I expect.

Thanks,

Rob

Read More...

Try this on the Pi in the terminal:

apt-cache policy libqhy

Read More...

Those are some outstanding photos!

Read More...

Basic Information
Gender
Male
Birthdate
19. 07. 1980
About me
Even though I am relatively young, I have been an astrophotographer for about 20 years. Within the last 5 years or so, I have taken my hobby to new heights. I built my own 10 inch telescope including grinding the mirror, bought a wide field newtonian for wider fields, acquired a much better mount to put them on (separately), got an SBIG camera for cooled CCD photos, modified a Canon XSi for better DSLR photos, and got lots of accessories. I have been doing all of my astrophotography with a Mac computer. I have basically made my own portable observatory, everything is carefully organized into boxes that I can load into my car in about 20 minutes. I take these things to dark skies and do lots of imaging at star parties.

I found out about INDI in May 2016 when Pleiades Astrophoto sent me an email about including an INDI client in their software. When I investigated further, I found out about KStars and Ekos. I quickly realized that I could install everything on a Raspberry Pi, velcro that to my scope, and use VLC to configure it from my computer using wifi. I have implemented 2 modes. The first is using the Raspberry Pi as an INDI server and using my Laptop as a wireless client using either the EKOS VM (running KStars and Ekos) or PixInsight as the client software. The second is using KStars and Ekos on the Raspberry Pi and controlling everything through VNC. Both methods have allowed me to cut the cords, move to WIFI control, and make all USB connections shorter. The second method also allows me to put my computer to sleep after I have configured the PI to do all the work. All I have to do is check in once in awhile to make sure it is working properly. So far this experiment is going very well, but I did have to work out quite a few issues along the way. I have been keeping a couple of logs of everything I have done to make it work, however, which is very useful. There are still a few problems, but the system is fully functional. It is a good thing it is summer so I have time to work on this!

The remarkable part is that you can automate your astrophotography setup, make the connection wireless, simplify the software by just running one program (KStars/Ekos) that runs it all, and you can make the connection to the devices separate from that program using INDIServer. (The last item is important because if KStars/Ekos were to crash, the devices would still be running on INDIServer.) And all of this will cost you around $100 including the Pi, a case, a 32 MB microSD card, the software, and a powered USB hub. There was a bit more work involved in setting it up and figuring it all out, but it was worth it.

I am an:
Astrophotographer
Amateur Astronomer
Physics and Computer Science Teacher
Delaware Astronomical Society Member
Mt. Cuba Observatory Education Associate

Contact Information
State
Delaware
City / Town
Wilmington
Country
United States

Login

3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!

Rob Lancaster

Basic Information

Gender

Birthdate

About me

Contact Information

State

City / Town

Country

Login

3rd Party

Got Problem?