Meade LPI and Linux
Posted 03 September 2010 - 09:43 AM
I suppose there's always the virtual pc route, but this laptop isn't really powerful enough to support such an option (it's an old P3 with 256MB of Ram and 6G HD...quite the screamer !)
Posted 03 September 2010 - 01:19 PM
Posted 03 September 2010 - 01:49 PM
I like the XFCE desktop better, but it's worth the tradeoff for performance. Next step...trying out SkyX and Starry Night under wine.
Posted 03 September 2010 - 01:52 PM
I have no experience with this app but I have read good reviews about it. It supports webcams, so it may support your LPI.
just remembered this venerable app: XEphem
I have used this app before. It is not eye candy, but it is very powerful software and if you take the time to learn it, it is amazing what you can do with it. It will control a Meade LPI camera using the INI drivers. There is a freeware copy and a purchase copy; you will want the purchase copy (69.95 US download or 79.95 US for 3 CDs).
Posted 03 September 2010 - 02:22 PM
Posted 03 September 2010 - 02:32 PM
Posted 03 September 2010 - 02:51 PM
There is KStars, it uses the INI driver plugins and use to support various cameras. You might have to install it from source as well if you want all of KStars's features to work. KStars is in Ubuntu's repository.
Posted 03 September 2010 - 03:07 PM
Will try the Linux version when I find a working download link.
Posted 03 September 2010 - 03:41 PM
Posted 04 September 2010 - 10:51 AM
If anyone is interested, I did manage to get Starry Night installed and running...but it's (pardon the pun since it's running on Puppy Linux) dog slow! I suspect this is due to the lack of hardware acceleration. I haven't figured out how to get that working yet...or if it's even possible under puppy with the old graphics the laptop is using (ATI Rage 128). SkyX wouldn't even install properly. (These installs are under WINE). Starry Night would probably work okay on a faster machine.
I have an old copy (version 2) of the Meade Autostar Suite...that might work better on this machine. I'll have to give that a try next. If that fails, somewhere I have a star atlas that was written for DOS...I used to use it back in my Tandy 1000 days (8088 CPU). That one should surely run!
Posted 04 September 2010 - 02:25 PM
Posted 04 September 2010 - 09:46 PM
Posted 05 September 2010 - 12:16 AM
Much like the NexImage from celestron is just a rebadged philips webcam, the lpi is just 'yet another rebadged webcam', so shouldn't be difficult to get going at all with a relatively recent linux distribution.
Once the correct drivers are in, and recognize the camera, then any program that can work with a v4l device should work fine with the lpi.
An old page with some of the details is here:-
Posted 05 September 2010 - 06:09 AM
SN9C10 PC Camera Controller detected (vid/pid 0x0C45/0x602A)
HV7131D image sensor detected
These are key information!
I have not found the long exposure related config information (exposure control 1 - 25) for the SN9c102 device driver. Probably LPI does not support long exposure at all???
PS. just found HV7131D conf registers:
0x26 and 0x27, max. integration time 65535*648*100nS= 4.246Second
P.S.2 another driver
Posted 05 September 2010 - 12:41 PM
Posted 26 December 2010 - 01:01 AM
Posted 26 December 2010 - 10:00 AM
On some systems I find Indi, libindi, and indilib. Not all are needed and some combinations won't work at all. Kstars may have some of the drivers included. I'm using Mint Linux 2010 and CDC 3.2.
Posted 26 December 2010 - 01:10 PM
Posted 27 December 2010 - 05:56 PM
Posted 28 December 2010 - 12:02 PM
In the Kstars telescope setup panels, click on the 'client' tab, then set up a server connection using the 'add' tab for the indiserver running at localhost port 7624. Hilight that one, and click 'connect'.
For Cdc, in the telescope settings, select indi driver, then configure localhost port 7624, leave the 'automatically start' unchecked. Set the device port for your serial port (/dev/ttyUSB0) and in telescope type, it really shouldn't matter what's there, I have 'other' selected, but if you have the full indi package installed, there should be an entry in that drop-down for the celestron scope. That should only be used by Cdc if it's actually starting the indiserver, but the current release of Cdc has a few issues in this area, which have been corrected in the svn issue daily builds after I submitted problem reports.
When I first started using indi with kstars and cdc, I had some issues figuring out the right twiddling to get it all working, but once going, it seemed to work ok. I really wanted all of my gear at the telescope to work over the indi connection, so I dug in a couple months ago, and started writing some drivers. I have recently commited to the indi svn drivers for
SXV-H9 ccd with sxv guide head attached
Starlight Xpress filter wheel
fcusb focus motor controller
In the process of getting all of the drivers going correctly, I ran into a few issues with both indi and Cdc. Much to my surprise / delight, bug reports to the Cdc bug tracker setup got response / fix within a week, and bug reports into the indi mailing list resulted in fixes showing up in the svn within 24 hours in most cases.
I believe most distributions that carry indi are still packaging 0.6x, but there is a ppa for ubuntu that has the most recently released 0.72 variant. It's listed with 'howto' for ubuntu at the indi website in the downloading section ( www.indilib.org ).
For our own use here, we will be putting indiserver onto headless little solid state boxes for set up at the telescope. I'm using a couple old atx motherboards, with a minimal lucid install that boots from a jumpstick. I've got pico-ps power supplies in them, and it's a fanless cpu, so we end up with all solid state, no moving parts for the 'outside' stuff. I'm running gigabit ethernet between the house network and the telescope location, so, we'll be using it all over the network, the little headless boxes at the telescope will have no user-land programs on them other than the basic indiserver and the drivers for telescope, camera, filter wheel and focus stuff. It'll be a good setup, and I'll finally have a proper 'network aware' remote telescope operation happening.
I have played with some of the other drivers etc in the indi package. The gphoto driver for dslr 'just worked' with my Canon 350, likewise the qhy5 stuff. I checked open-phd out of it's version control, and it built with no issues here. It looks just like phd on any other platform, but I haven't had a chance to feed it real starlight yet due to incessant and continuous rain over the last few weeks. Csc is hinting at some possible clear time over the next few days, so, I may get a chance to finally put starlight into all of this new stuff, but I'm not getting my hopes up to high right now.
Posted 28 December 2010 - 04:33 PM
I have KStars on Mint 9. I've installed it directly using Synaptic. It runs but no telescope control. I uninstalled completely and installed again as part of Kdeedu. I did not solve the problem. All the same files are present in /usr/bin. However, none of the drivers are seen in the telescope setup.
I'm trying your ideas now. I have Name=indiserver, Host=localhost, and Port=7624. However, when I try to connect I get "encountered an error. Connection refused". In the Telescope Wizard, the scope dropdown list is empty. Apparently, KStars is not looking in the right location. The Indi info in Configure KStars is all correct. If I start the server from a terminal, it appears to run but is looking at ttyS0. That apparently doesn't hurt as CDC works. The KStars wizard says the drivers cannot be found. I found in a Google search a comment on a forum about a misconfigured XML file for KStars but cannot find it now.
Your setup sounds like top-line.
Posted 28 December 2010 - 07:54 PM
Apparently, KStars is not looking in the right location. The Indi info in Configure KStars is all correct. If I start the server from a terminal, it appears to run but is looking at ttyS0. That apparently doesn't hurt as CDC works. The KStars wizard says the drivers cannot be found. I found in a Google search a comment on a forum about a misconfigured XML file for KStars but cannot find it now.
The indi install should have put drivers.xml into /usr/share/indi, and that's the default place where things will look for drivers. But, you can bypass that all by simply starting things from the command line with your indi server, then connect via the tcp connection as if it's a remote indi server.
With kstars, ignore the wizards. Devices -> Device Manager -> Client. Set up the info to connect to your indi server there, and hit connect. Once connected, go to the indi control panel. Select your telescope from the top tab, and in the options tab there, you can change the serial port. You should be able to save the configuration once it's changed, and it'll remember the config after that. I've never used the celestron driver so, I cant say for sure it saves/restores correctly.
It's all working very well here now, keeping in mind that I've got all the most recent svn changes in my locally built copy. One indi server running on the remote box connected to the telescope hardware, then multiple clients here connecting to it. open-phd can guide via the qhy5 connection. Kstars will manage the ccd and filter wheel for a photography run, and it can do telescope controls at the same time, altho I am using Cdc for that.
There is some work afoot right now to try get a 0.8 cut on the indi stuff out during january, and that will have a significant amount of upgrades / changes, as well as a few new drivers included.
Posted 29 December 2010 - 10:13 AM
Is there a hot key or toolbar button to slew to the selected object? I'm using right-click on object then Celestron/Slew.
Thanks for the help.
Posted 24 May 2011 - 11:26 AM
I know this is kind of a dead thread. How's the work on INDI coming? I've had some troubles compiling the SVN (Ubuntu 11.04) 0.72.
When I do cmake . in the trunk/libindi folder, I get the following error:
/home/chris/devel/indi/trunk/libindi/libs/indibase/basedriver.h:4:32: fatal error: boost/shared_ptr.hpp: No such file or directory
Any ideas? I'm trying to get Open PHD to work so I can autoguide on my macbook.