openphdguiding / phd2 Goto Github PK

Replace existing crosshairs with pairs of parallel lines, finely spaced (as in 
a reticule eyepiece)

Hi celst ,
I am new to this open phd guiding and was trying to look on the source files , 
Is it possible for guys like me to have brief explanation what its doing for 
all the files given as the source files..
I have have gone through those files but better if you provide it...

On my 64 bit gentoo (unicode) system, the following will lead to a crash of
open-phd-guiding:

1) I start an indiserver, 
2) start phd, 
3) then click at connect in the indi configure dialog,  

In the log of the indi server, one sees that phd has made contact with
indi. However, the last log only contains some strange chars. I do not know
what this is. Perhaps an xml and char problem with phd on 64 bit platforms? 

In kstars, indi works well. 

A user requested the ability to have two independent copies of PHD running.  
I'm not sure how common this use case might be, but enabling seems really ease.

We would have to add an instance/n to the configuration path, have a command 
line option to set the instance (with a default of 0), and then use that to 
look up the correct configuration data and select a socket port number.

It seems like a good time to make these changes is now, before people have 
really installed and set it up.

We really need someone to take on adding QuickTime support for the Mac folks...

What steps will reproduce the problem?
1. start PHD
2. try to connect camera
3. choose either INDI or 4vl

What is the expected output? What do you see instead?
Expect to see camera working but only get 
INDI: failed to connect to indi server and 
problem connecting to camera
V4L: the camera does not show up on the list of cameras

What version of the product are you using? On what operating system?
KDE with kubuntu operating system
 PHD v.1.12.4
Please provide any additional information below.
I am a total linux newbie. I tried to download and install v4l and INDI and may 
not have done so correctly. The make of PHD went through finding all v4l 
requirements and compiled and made no problem. I don't think I got INDI working 
OK yet.

I would like to compile openPHD for windows, is this possible, I don't see any 
msvc specific files apart from the readme which doesn't really give any clues.

What steps will reproduce the problem?
1. set up an indiserver, like : indiserver indi_v4l_philips

Now the question is how to configure PHD to use this INDI camera.

I've tried configuring PHD in various ways using the INDI->Configure , 
INDI->Controls and the Main Camera button in different order.

The following lists the farthest I could get, using a weird setup order I'm 
sure :

I can get PHD to connect to the INDI camera, but not use it. The 'loop' button 
stays grayed out.

I start with configure INDI server in PHD with : INDI->Configure, fill in 
hostname and port.

Then pressing 'Connect' results in :

Failed to connect to INDI server.

However, pressing OK and going to INDI->Controls and pressing 'Connect' there 
aways works. I see the camera start, the INDI server logs :

2011-05-29T18:18:51: Driver indi_v4l_philips: width: 160 - height: 120
2011-05-29T18:18:51: Driver indi_v4l_philips: pixel format: V4L2_PIX_FMT_YUV420
2011-05-29T18:18:51: Driver indi_v4l_philips: Min X: 160 - Max X: 640 - Min Y: 
120 - Max Y: 480
2011-05-29T18:18:51: Driver indi_v4l_philips: V4L 2 - All successful, returning
2011-05-29T18:18:51: Driver indi_v4l_philips: Philips Webcam is online. 
Retrieving basic data.
and some more details.

Now I go back to INDI->Configure and the dropdown box for the Camera Driver is 
filled in. I select 'Philips Webcam' and guess /dev/video0 for the Camera Port.

Next I use the main window Camera button and select INDI camera.

PHD logs :
Found CONNECTION for camera Philips Webcam
Camera connected state: 0
Camera connected state: 0
Camera connected state: 0
etc.

The INDI server logs :

2011-05-29T18:25:15: Driver indi_v4l_philips: VIDIOC_DQBUF error 9, Bad file 
descriptor
2011-05-29T18:25:15: Driver indi_v4l_philips: VIDIOC_DQBUF error 9, Bad file 
descriptor
2011-05-29T18:25:15: Driver indi_v4l_philips: VIDIOC_DQBUF error 9, Bad file 
descriptor
etc.

What version of the product are you using? On what operating system?

PHD 1.12.4 compiled from trunk r74
32-bit Ubuntu-10.10 using Linux-2.6.35-28-generic-pae wx-2.8.11.0-0ubuntu4.1
Stock SPC900 webcam
INDI server Code $Revision: 726523 $. Protocol 1.7.

Please provide any additional information below.

The INDI Options screen shows a green light next to the Connection, the INDI 
server confirms this :

2011-05-29T17:08:35: startup: indiserver indi_v4l_philips 
2011-05-29T17:10:52: Driver indi_v4l_philips: width: 160 - height: 120
2011-05-29T17:10:52: Driver indi_v4l_philips: pixel format: V4L2_PIX_FMT_YUV420
2011-05-29T17:10:52: Driver indi_v4l_philips: Min X: 160 - Max X: 640 - Min Y: 
120 - Max Y: 480
2011-05-29T17:10:52: Driver indi_v4l_philips: V4L 2 - All successful, returning
2011-05-29T17:10:52: Driver indi_v4l_philips: Philips Webcam is online. 
Retrieving basic data.
2011-05-29T17:10:52: Driver indi_v4l_philips: Brightness -- min: 0 max: 128 
step: 1 value: 63
2011-05-29T17:10:52: Driver indi_v4l_philips: Contrast -- min: 0 max: 64 step: 
1 value: 0
2011-05-29T17:10:52: Driver indi_v4l_philips: Saturation -- min: -100 max: 100 
step: 1 value: 0
2011-05-29T17:10:52: Driver indi_v4l_philips: Red Gain -- min: 0 max: 256 step: 
1 value: 40
2011-05-29T17:10:52: Driver indi_v4l_philips: Blue Gain -- min: 0 max: 256 
step: 1 value: 17
2011-05-29T17:10:52: Driver indi_v4l_philips: Gamma -- min: 0 max: 32 step: 1 
value: 0
2011-05-29T17:10:52: Driver indi_v4l_philips: Shutter Speed (Exposure) -- min: 
0 max: 256 step: 1 value: 219
2011-05-29T17:10:52: Driver indi_v4l_philips: Gain Level -- min: 0 max: 256 
step: 1 value: -9
2011-05-29T17:11:35: Driver indi_v4l_philips: Starting the video stream.

Selecting 'Stream on' in the INDI Options screen results in a yellow light.

Do we have a mailing list ? Or an IRC channel ? I think that'll be a lot easier 
to communicate.

This has come out of an email conversation with Jared Wellman, one of the 
authors of Sequence Generator Pro (SGP).

SGP interacts a lot with the PHD socket server, and it has the option to show a 
little PHD graph as a window.  The data for that window currently comes from 
scraping the PHD log file, whose format has changed enough from PHD1 to PHD2 
that it is currently broken.

As part of the conversation on how to fix it, I proposed another socket 
interface to provide real time guiding data. He countered by proposing that it 
also provide other status data (lock lost, etc.).

This seems like a cool thing for applications that want to interact with PHD, 
including things like programs that show PE, SGP, etc.

A device should not make GUI call except through proxy wrapper like the 
wxMessageBoxProxy.

To make it work in the worker thread, the functions HasNonGuiCapture and 
HasNonGuiMove must return true.

SBIG : OK
Simulator : OK
Starshoot Autoguider : OK

After termination, I can often see remaining threads of open-phd-guiding on
my system monitor in kde4

What steps will reproduce the problem?
1. Use Nexstar 8i with HC v2.2.
2. Select star and start guiding. Calibration will trigger.
3. After calibration in W direction, E starts

What is the expected output? What do you see instead?

After calibration steps in W direction, E should start, but after brief stop 
when calibration direction changes star will continue moving W, even if PHD 
displays it is calibrating in E direction. After this calibration can be 
successful but when real guiding starts the star will move quickly towards W 
and will be lost.

What version of the product are you using? On what operating system?
Open PHD from CVS (current version) on Linux, connected via indi v. 0.7.2 from 
Ubuntu.

Please provide any additional information below.

Here is log from indi from beginning of calibration:

2011-09-24T19:52:59: Client 5: read <newSwitchVector device='Celestron GPS' 
name='TELESCOPE_MOTION_WE'>
2011-09-24T19:52:59: Driver indi_celestron_gps: queuing responsible for 
<newSwitchVector device='Celestron GPS' name='TELESCOPE_MOTION_WE'>
2011-09-24T19:52:59: Driver indi_celestron_gps: sending <newSwitchVector 
device="Celestron GPS" name="TELE
2011-09-24T19:52:59: Driver indi_celestron_gps: read <setSwitchVector 
device='Celestron GPS' name='TELESCOPE_MOTION_WE'>
2011-09-24T19:52:59: Client 5: queuing <setSwitchVector device='Celestron GPS' 
name='TELESCOPE_MOTION_WE'>
2011-09-24T19:52:59: Client 5: sending <setSwitchVector device="Celestron GPS" 
name="TELE
2011-09-24T19:52:59: Driver indi_celestron_gps: read <setNumberVector 
device='Celestron GPS' name='EQUATORIAL_EOD_COORD'>
2011-09-24T19:52:59: Client 5: queuing <setNumberVector device='Celestron GPS' 
name='EQUATORIAL_EOD_COORD'>
2011-09-24T19:52:59: Client 5: sending <setNumberVector device="Celestron GPS" 
name="EQUA
2011-09-24T19:53:00: Client 5: read <newSwitchVector device='Celestron GPS' 
name='TELESCOPE_MOTION_WE'>
2011-09-24T19:53:00: Driver indi_celestron_gps: queuing responsible for 
<newSwitchVector device='Celestron GPS' name='TELESCOPE_MOTION_WE'>
2011-09-24T19:53:00: Driver indi_celestron_gps: sending <newSwitchVector 
device="Celestron GPS" name="TELE
2011-09-24T19:53:00: Driver indi_celestron_gps: read <setSwitchVector 
device='Celestron GPS' name='TELESCOPE_MOTION_WE'>
2011-09-24T19:53:00: Client 5: queuing <setSwitchVector device='Celestron GPS' 
name='TELESCOPE_MOTION_WE'>
2011-09-24T19:53:00: Client 5: sending <setSwitchVector device="Celestron GPS" 
name="TELE
2011-09-24T19:53:01: Client 5: read <newSwitchVector device='Celestron GPS' 
name='TELESCOPE_MOTION_WE'>
2011-09-24T19:53:01: Driver indi_celestron_gps: queuing responsible for 
<newSwitchVector device='Celestron GPS' name='TELESCOPE_MOTION_WE'>
2011-09-24T19:53:01: Driver indi_celestron_gps: sending <newSwitchVector 
device="Celestron GPS" name="TELE
2011-09-24T19:53:01: Driver indi_celestron_gps: read <setSwitchVector 
device='Celestron GPS' name='TELESCOPE_MOTION_WE'>
2011-09-24T19:53:01: Client 5: queuing <setSwitchVector device='Celestron GPS' 
name='TELESCOPE_MOTION_WE'>
2011-09-24T19:53:01: Client 5: sending <setSwitchVector device="Celestron GPS" 
name="TELE
2011-09-24T19:53:03: Client 5: read <newSwitchVector device='Celestron GPS' 
name='TELESCOPE_MOTION_WE'>
2011-09-24T19:53:03: Driver indi_celestron_gps: queuing responsible for 
<newSwitchVector device='Celestron GPS' name='TELESCOPE_MOTION_WE'>
2011-09-24T19:53:03: Driver indi_celestron_gps: sending <newSwitchVector 
device="Celestron GPS" name="TELE
2011-09-24T19:53:03: Driver indi_celestron_gps: No ISwitch '    ' in Celestron 
GPS.TELESCOPE_MOTION_WE
2011-09-24T19:53:03: Driver indi_celestron_gps: read <setSwitchVector 
device='Celestron GPS' name='TELESCOPE_MOTION_WE'>
2011-09-24T19:53:03: Client 5: queuing <setSwitchVector device='Celestron GPS' 
name='TELESCOPE_MOTION_WE'>
2011-09-24T19:53:03: Client 5: sending <setSwitchVector device="Celestron GPS" 
name="TELE
2011-09-24T19:53:04: Client 5: read <newSwitchVector device='Celestron GPS' 
name='TELESCOPE_MOTION_WE'>
2011-09-24T19:53:04: Driver indi_celestron_gps: queuing responsible for 
<newSwitchVector device='Celestron GPS' name='TELESCOPE_MOTION_WE'>
2011-09-24T19:53:04: Driver indi_celestron_gps: sending <newSwitchVector 
device="Celestron GPS" name="TELE
2011-09-24T19:53:04: Driver indi_celestron_gps: read <setSwitchVector 
device='Celestron GPS' name='TELESCOPE_MOTION_WE'>
2011-09-24T19:53:04: Client 5: queuing <setSwitchVector device='Celestron GPS' 
name='TELESCOPE_MOTION_WE'>
2011-09-24T19:53:04: Client 5: sending <setSwitchVector device="Celestron GPS" 
name="TELE
2011-09-24T19:53:05: Driver indi_celestron_gps: read <setNumberVector 
device='Celestron GPS' name='EQUATORIAL_EOD_COORD'>
2011-09-24T19:53:05: Client 5: queuing <setNumberVector device='Celestron GPS' 
name='EQUATORIAL_EOD_COORD'>
2011-09-24T19:53:05: Client 5: sending <setNumberVector device="Celestron GPS" 
name="EQUA
2011-09-24T19:53:05: Client 5: read <newSwitchVector device='Celestron GPS' 
name='TELESCOPE_MOTION_WE'>
2011-09-24T19:53:05: Driver indi_celestron_gps: queuing responsible for 
<newSwitchVector device='Celestron GPS' name='TELESCOPE_MOTION_WE'>
2011-09-24T19:53:05: Driver indi_celestron_gps: sending <newSwitchVector 
device="Celestron GPS" name="TELE
2011-09-24T19:53:05: Driver indi_celestron_gps: read <setSwitchVector 
device='Celestron GPS' name='TELESCOPE_MOTION_WE'>
2011-09-24T19:53:05: Client 5: queuing <setSwitchVector device='Celestron GPS' 
name='TELESCOPE_MOTION_WE'>
2011-09-24T19:53:05: Client 5: sending <setSwitchVector device="Celestron GPS" 
name="TELE

Hello,

There are cameras, like icam tracer, which seem to support even under
windows only 320x240 and do the other resolutions available under windows
via software interpolation.

especially Icam tracer is often sold in astronomy stores because of its
light sensitivity, for example see here:
http://www.astroshop.de/webcams-%26-usb-okulare/i-tec-icam-tracer-1-3-mp-ccd-web
cam/p,16561?sid=1b14baedd008dcb38e1b4960c08bac1f

After exchanges with the webcam driver maintainer, it seems that the next
kernel will include a working gspca driver for that cam. A version which
more or less seems to work is in the gspca test tarball which can be
downloaded here: http://moinejf.free.fr/

Unfortunately, as it came out from usb sniffs, it seems that Icam tracer
supports only 320x240 images and then the driver interpolates to higher
resolutions.

Today I tried to use the cam under linux with open-phd guiding.

Attached is a screenshot of how the image window from open-phd-guiding looks.

I do not believe that this would really work for guiding.


I think that the video for linux driver should take care somehow of the
different resolutions from the numerous webcams.

(req) Your Name: Tom Zalmstra

(req) Your Email: [email protected]

(req) Program PHD Guiding

Version of program 1.14

(req) Operating system Windows XP

What camera are you using in the affected program (or doesn't it matter)? 

(req) The problem is Consistent and repeatable

(req) Describe the problem as simply as possible. What exactly is going wrong? 
PHD crashes when I click "take dark" before connecting a camera. Older versions 
warned to connect a camera first

What steps will reproduce the problem?
1.  Pick any 8bit v4l camera as input (lifecam cinema hd in my case)
2.  Choose say 1sec exposure and shoot darks
3.  uncover lens and observe preview frames

What is the expected output? What do you see instead?
Expected to see dark background, instead it's a light gray

What version of the product are you using? On what operating system?
Latest svn checkout, ubuntu 10.10 I think

Please provide any additional information below.
 I traced the culprit, and it's in image_math.cpp in the dark subtract method.  For some reason, the threshold for dark subtraction is 100, which also gets added into the pixel value when subtracting.  I changed it to zero and everything is now fine.  I'm thinking this was done so only really bright pixels are subtracted rather than also noise, but if a camera has a high bias (as in my case) it just elevates the bias signal by 100, which makes the background light gray. Once I use straight subtraction (took out the +100) it works fine.  Perhaps this is worth asking Craig or investigating further?

Thanks.

Daniel

To see this, start an indiserver, e.g:

indiserver indi_celestron_gps

then start open-phd-guiding

click on "indi control planel"

if you enter some names for the device port (e.g /dev/ttyUSB0) the
indiserver will record only some strange chars.

On a system where the serial port is at the standard /dev/ttyS0 phd-guiding
would crash if I click connect...

(By the way, how do I connect this open-phd-guiding to my
celestron-nextstar? The indi_celestron_gps driver works in kstars. The
device is located at /dev/ttyUSB0. In Kstars I can move the telescope. With
open-phd-guiding, I was not able to connect. How do I do this?

What steps will reproduce the problem?
1. Try command svn checkout http://open-phd-guiding.googlecode.com/svn/trunk/ 
open-phd-guiding-read-only

What is the expected output? What do you see instead?
I expect to get source code in working directory, but I get svn: access to 
'/svn/!svn/vcc/default' forbidden

checkout of other projects using SVN, let's say stellarium works.

Since currently PHD does not have any notion of where it is pointed, you have 
to recalibrate if you move in Declination.

We should add HasDeclination() and GetDeclination() methods to the scope class, 
and then for scopes that have declination available, the calibration code 
should record it, and the guide code should take it into account.

What steps will reproduce the problem?
1.  Setup INDI and LX200Generic and Camera in USB
2.  Start guiding 
3.  Click Stop, mount still slews (stop command not issued to mount)

What is the expected output? What do you see instead?
Mount must stop slew

What version of the product are you using? On what operating system?
Latest SVN, Archlinux

Please provide any additional information below.

Compilign in 64bits with gcc:

paco@jupiter:~/Astro/open-phd-guiding-read-only> make
[  5%] Building CXX object CMakeFiles/PHD.dir/cam_INDI.cpp.o
/home/paco/Astro/open-phd-guiding-read-only/cam_INDI.cpp: In member
function ‘virtual bool Camera_INDIClass::CaptureFull(int, usImage&, bool)’:
/home/paco/Astro/open-phd-guiding-read-only/cam_INDI.cpp:190: error: cannot
convert ‘unsigned int*’ to ‘size_t*’ for argument ‘5’ to ‘int
ffomem(fitsfile**, const char*, int, void**, size_t*, size_t, void*
(*)(void*, size_t), int*)’
make[2]: *** [CMakeFiles/PHD.dir/cam_INDI.cpp.o] Error 1
make[1]: *** [CMakeFiles/PHD.dir/all] Error 2
make: *** [all] Error 2

It looks like a problem in definition of indi_element_t struct.

Hi,

Thanks for your great soft!

I realize that guidding using ST4 port of indi camera it is a missing feature 
thus I modified your code (cam_INDI) to implement it. It is not fully testing 
but works!

When I finish testing I would like to send you for inclusion in openPHD next 
release (if you agree, of course). Please tell me how to do it. You can contact 
me at ignacio.mas at gmail.com

Cheers
Nacho Mas

PE in RA can alter the Dec calibration info.  Flag to enforce a right angle in 
the Dec cal section (make it ortho to RA to factor out PE getting into the Dec 
cal).

What steps will reproduce the problem?
1. Stream from V4L2 camera
2. wait
3. watch crash everytime

What is the expected output? What do you see instead?

$ PHD
raw pixfmt: MJPG 640x480
pixfmt: RGB3 640x480
mmap method

v4l_convert error 5, Input/output error
v4l-convert: error parsing JPEG header: Not a JPG file ?


What version of the product are you using? On what operating system?
OPENPHD 1.12.4
Ubuntu 10.04

Please provide any additional information below.

What steps will reproduce the problem?
1. compile trunk r74 on 32-bit Ubuntu-10.10 Linux-2.6.35-28-generic-pae using 
wx-2.8.11.0-0ubuntu4.1, connect SPC900 webcam
2. start PHD, click camera, select V4L(2) Camera
3. Click the 'loop' button

What is the expected output?

- 640x480 resolution
- regular frame updates

What do you see instead?

- 160x120 resolution :

raw pixfmt: YU12 160x120
pixfmt: RGB3 160x120
mmap method

- 1 frame update per minute or so.

What version of the product are you using? On what operating system?

PHD 1.12.4 compiled from trunk r74
32-bit Ubuntu-10.10 using Linux-2.6.35-28-generic-pae wx-2.8.11.0-0ubuntu4.1
Stock SPC900 webcam

Please provide any additional information below.

- Webcam works fine in 640x480 using vlc or mplayer
- libv4l-0: /usr/lib/libv4l2.so.0
- 20110528_202010 hans@x:~/src/astro/open-phd-guiding-build/ ldd PHD 
        linux-gate.so.1 =>  (0x00cc3000)
        libcfitsio.so.3 => /usr/lib/libcfitsio.so.3 (0x0043a000)
        libwx_baseu-2.8.so.0 => /usr/lib/libwx_baseu-2.8.so.0 (0x00e74000)
        libwx_gtk2u_core-2.8.so.0 => /usr/lib/libwx_gtk2u_core-2.8.so.0 (0x005f5000)
        libwx_baseu_net-2.8.so.0 => /usr/lib/libwx_baseu_net-2.8.so.0 (0x00110000)
        libwx_gtk2u_html-2.8.so.0 => /usr/lib/libwx_gtk2u_html-2.8.so.0 (0x0013c000)
        libudev.so.0 => /lib/libudev.so.0 (0x00bb5000)
        libv4l2.so.0 => /usr/lib/libv4l2.so.0 (0x001d3000)
        libv4lconvert.so.0 => /usr/lib/libv4lconvert.so.0 (0x001de000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00cd9000)
        libm.so.6 => /lib/libm.so.6 (0x00323000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00b7c000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x0024b000)
        libc.so.6 => /lib/libc.so.6 (0x009d2000)
        libz.so.1 => /lib/libz.so.1 (0x00265000)
        libdl.so.2 => /lib/libdl.so.2 (0x0027a000)
        libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x00fbb000)
        libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x0027e000)
        libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x00349000)
        libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0x00bc1000)
        libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x00364000)
        libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x0038a000)
        libpng12.so.0 => /lib/libpng12.so.0 (0x003a3000)
        libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x003c8000)
        libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00dc4000)
        libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x0040a000)
        libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00941000)
        libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x00315000)
        libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x00319000)
        librt.so.1 => /lib/librt.so.1 (0x00984000)
        libglib-2.0.so.0 => /lib/libglib-2.0.so.0 (0x0d316000)
        libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0x0031e000)
        libSM.so.6 => /usr/lib/libSM.so.6 (0x0098d000)
        libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x00b2f000)
        libtiff.so.4 => /usr/lib/libtiff.so.4 (0x1661b000)
        /lib/ld-linux.so.2 (0x009b4000)
        libXext.so.6 => /usr/lib/libXext.so.6 (0x00996000)
        libXrender.so.1 => /usr/lib/libXrender.so.1 (0x009a6000)
        libXi.so.6 => /usr/lib/libXi.so.6 (0x00b50000)
        libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0x00b5e000)
        libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0x00b66000)
        libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0x00b70000)
        libX11.so.6 => /usr/lib/libX11.so.6 (0x08ad0000)
        libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0x009b0000)
        libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0x00b98000)
        libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x00b9c000)
        libcairo.so.2 => /usr/lib/libcairo.so.2 (0x01d8b000)
        libpcre.so.3 => /lib/libpcre.so.3 (0x00e3b000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x00cad000)
        libselinux.so.1 => /lib/libselinux.so.1 (0x0138b000)
        libexpat.so.1 => /lib/libexpat.so.1 (0x1db9e000)
        libICE.so.6 => /usr/lib/libICE.so.6 (0x09b87000)
        libuuid.so.1 => /lib/libuuid.so.1 (0x00ba2000)
        libxcb.so.1 => /usr/lib/libxcb.so.1 (0x1a298000)
        libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0x05e7b000)
        libxcb-shm.so.0 => /usr/lib/libxcb-shm.so.0 (0x00ba7000)
        libxcb-render.so.0 => /usr/lib/libxcb-render.so.0 (0x00bab000)
        libXau.so.6 => /usr/lib/libXau.so.6 (0x00cc4000)
        libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00cc8000)

What steps will reproduce the problem?
1.checkout svn (currently -r76)
2.mkdir build; cd build; cmake ../; make

What is the expected output? What do you see instead?
I expect the PHD binary to be built. 
Scanning dependencies of target PHD
[  3%] Building CXX object CMakeFiles/PHD.dir/camera.cpp.o                      


[  6%] Building CXX object CMakeFiles/PHD.dir/cam_INDI.cpp.o                    


[  9%] Building CXX object CMakeFiles/PHD.dir/cam_SBIG.cpp.o                    


[ 12%] Building CXX object CMakeFiles/PHD.dir/cam_simulator.cpp.o               


[ 15%] Building CXX object CMakeFiles/PHD.dir/canvas.cpp.o                      


[ 18%] Building CXX object CMakeFiles/PHD.dir/config_INDI.cpp.o                 


[ 21%] Building CXX object CMakeFiles/PHD.dir/eegg.cpp.o                        


[ 25%] Building CXX object CMakeFiles/PHD.dir/frame_events.cpp.o                


[ 28%] Building CXX object CMakeFiles/PHD.dir/graph.cpp.o                       


/home/bgilsrud/openphd/graph.cpp: In member function ‘void 
GraphLogWindow::OnButtonMode(wxCommandEvent&)’:                               

/home/bgilsrud/openphd/graph.cpp:182:15: warning: variable ‘mstate’ set but 
not used [-Wunused-but-set-variable]
[ 31%] Building CXX object CMakeFiles/PHD.dir/guide_routines.cpp.o
[ 34%] Building CXX object CMakeFiles/PHD.dir/image_math.cpp.o                  


[ 37%] Building CXX object CMakeFiles/PHD.dir/phd.cpp.o                         


[ 40%] Building CXX object CMakeFiles/PHD.dir/prefs.cpp.o                       


[ 43%] Building CXX object CMakeFiles/PHD.dir/scope.cpp.o                       


[ 46%] Building CXX object CMakeFiles/PHD.dir/socket_server.cpp.o               


[ 50%] Building CXX object CMakeFiles/PHD.dir/tele_INDI.cpp.o                   


[ 53%] Building CXX object CMakeFiles/PHD.dir/usImage.cpp.o                     


[ 56%] Building CXX object CMakeFiles/PHD.dir/GC_USBST4.cpp.o                   


[ 59%] Building C object CMakeFiles/PHD.dir/libindiclient/indi.c.o              


[ 62%] Building CXX object CMakeFiles/PHD.dir/libindiclient/wx/indigui.cpp.o    


/home/bgilsrud/openphd/libindiclient/wx/indigui.cpp: In member function ‘void 
IndiGui::CreateSwitchCombobox(indi_prop_t*, int)’:                            

/home/bgilsrud/openphd/libindiclient/wx/indigui.cpp:370:80: warning: cast to 
pointer from integer of different size [-Wint-to-pointer-cast]
[ 65%] Building CXX object CMakeFiles/PHD.dir/libindiclient/wx/indi_io.cpp.o
[ 68%] Building CXX object CMakeFiles/PHD.dir/libindiclient/wx/indi_list.cpp.o  


/home/bgilsrud/openphd/libindiclient/wx/indi_list.cpp: In function ‘void* 
il_item(void*)’:                                                              

/home/bgilsrud/openphd/libindiclient/wx/indi_list.cpp:81:10: error: ‘NULL’ 
was not declared in this scope
/home/bgilsrud/openphd/libindiclient/wx/indi_list.cpp: In function ‘void* 
il_first(void*)’:
/home/bgilsrud/openphd/libindiclient/wx/indi_list.cpp:89:10: error: ‘NULL’ 
was not declared in this scope
make[2]: *** [CMakeFiles/PHD.dir/libindiclient/wx/indi_list.cpp.o] Error 1
make[1]: *** [CMakeFiles/PHD.dir/all] Error 2
make: *** [all] Error 2

What version of the product are you using? On what operating system?
SVN on ubuntu 11.10


Please provide any additional information below.

===================================================================
--- libindiclient/wx/indi_list.cpp      (revision 76)
+++ libindiclient/wx/indi_list.cpp      (working copy)
@@ -1,5 +1,6 @@
 #include "../indi_list.h"

+#include <cstring>
 #include <list>
 using namespace std;

What steps will reproduce the problem?
1.Click on 'configure'
2.enter data and close
3.reopen only shows the localhost and 7624 filled in

What is the expected output? What do you see instead?
data to remian as entered

What version of the product are you using? On what operating system?
I downloaded and compiled the source from here
http://code.google.com/p/open-phd-guiding/source/checkout

SUSE 11.2 on an AMDx64.

Please provide any additional information below.
This my first go at PHD so not sure what is required.
I do get some error messages when I start PHD but they did not seem
relevant to this. I was thinking about putting them in a separate issue.

I really need this app to run my observatory
http://astronomicalresearchaustralia.org
so I am happy to keep testing it until it works.
Thanks,
Brian

What steps will reproduce the problem?
1.cmake PHD
2.make
3.lorne@nosferatu:~/PHD$ make -B
[  3%] Building CXX object CMakeFiles/PHD.dir/camera.cpp.o
[  6%] Building CXX object CMakeFiles/PHD.dir/cam_INDI.cpp.o
[  9%] Building CXX object CMakeFiles/PHD.dir/cam_SBIG.cpp.o
[ 12%] Building CXX object CMakeFiles/PHD.dir/cam_simulator.cpp.o
[ 16%] Building CXX object CMakeFiles/PHD.dir/canvas.cpp.o
[ 19%] Building CXX object CMakeFiles/PHD.dir/config_INDI.cpp.o
[ 22%] Building CXX object CMakeFiles/PHD.dir/eegg.cpp.o
[ 25%] Building CXX object CMakeFiles/PHD.dir/frame_events.cpp.o
[ 29%] Building CXX object CMakeFiles/PHD.dir/graph.cpp.o
[ 32%] Building CXX object CMakeFiles/PHD.dir/guide_routines.cpp.o
[ 35%] Building CXX object CMakeFiles/PHD.dir/image_math.cpp.o
[ 38%] Building CXX object CMakeFiles/PHD.dir/phd.cpp.o
[ 41%] Building CXX object CMakeFiles/PHD.dir/prefs.cpp.o
[ 45%] Building CXX object CMakeFiles/PHD.dir/scope.cpp.o
[ 48%] Building CXX object CMakeFiles/PHD.dir/socket_server.cpp.o
[ 51%] Building CXX object CMakeFiles/PHD.dir/tele_INDI.cpp.o
[ 54%] Building CXX object CMakeFiles/PHD.dir/usImage.cpp.o
[ 58%] Building C object CMakeFiles/PHD.dir/libindiclient/indi.c.o
[ 61%] Building CXX object CMakeFiles/PHD.dir/libindiclient/wx/indigui.cpp.o
[ 64%] Building CXX object CMakeFiles/PHD.dir/libindiclient/wx/indi_io.cpp.o
[ 67%] Building CXX object CMakeFiles/PHD.dir/libindiclient/wx/indi_list.cpp.o
[ 70%] Building CXX object CMakeFiles/PHD.dir/libindiclient/wx/indi_config.cpp.o
[ 74%] Building CXX object CMakeFiles/PHD.dir/libindiclient/wx/indisave.cpp.o
[ 77%] Building CXX object CMakeFiles/PHD.dir/libindiclient/wx/wxled.cpp.o
[ 80%] Building CXX object 
CMakeFiles/PHD.dir/libindiclient/wx/wxchecktreectrl.cpp.o
[ 83%] Building C object CMakeFiles/PHD.dir/libindiclient/base64.c.o
[ 87%] Building C object CMakeFiles/PHD.dir/libindiclient/lilxml.c.o
[ 90%] Building CXX object CMakeFiles/PHD.dir/cam_VIDEODEVICE.cpp.o
[ 93%] Building CXX object CMakeFiles/PHD.dir/config_VIDEODEVICE.cpp.o
[ 96%] Building CXX object CMakeFiles/PHD.dir/v4lcontrol.cpp.o
[100%] Building CXX object CMakeFiles/PHD.dir/cameras/linuxvideodevice.cpp.o
Linking CXX executable PHD
/usr/bin/ld: cannot open output file PHD: Is a directory
collect2: ld returned 1 exit status
make[2]: *** [PHD] Error 1
make[1]: *** [CMakeFiles/PHD.dir/all] Error 2
make: *** [all] Error 2
lorne@nosferatu:~/PHD$ 


What is the expected output? What do you see instead?
lorne@nosferatu:~/PHD$ make -B
[  3%] Building CXX object CMakeFiles/PHD.dir/camera.cpp.o
[  6%] Building CXX object CMakeFiles/PHD.dir/cam_INDI.cpp.o
[  9%] Building CXX object CMakeFiles/PHD.dir/cam_SBIG.cpp.o
[ 12%] Building CXX object CMakeFiles/PHD.dir/cam_simulator.cpp.o
[ 16%] Building CXX object CMakeFiles/PHD.dir/canvas.cpp.o
[ 19%] Building CXX object CMakeFiles/PHD.dir/config_INDI.cpp.o
[ 22%] Building CXX object CMakeFiles/PHD.dir/eegg.cpp.o
[ 25%] Building CXX object CMakeFiles/PHD.dir/frame_events.cpp.o
[ 29%] Building CXX object CMakeFiles/PHD.dir/graph.cpp.o
[ 32%] Building CXX object CMakeFiles/PHD.dir/guide_routines.cpp.o
[ 35%] Building CXX object CMakeFiles/PHD.dir/image_math.cpp.o
[ 38%] Building CXX object CMakeFiles/PHD.dir/phd.cpp.o
[ 41%] Building CXX object CMakeFiles/PHD.dir/prefs.cpp.o
[ 45%] Building CXX object CMakeFiles/PHD.dir/scope.cpp.o
[ 48%] Building CXX object CMakeFiles/PHD.dir/socket_server.cpp.o
[ 51%] Building CXX object CMakeFiles/PHD.dir/tele_INDI.cpp.o
[ 54%] Building CXX object CMakeFiles/PHD.dir/usImage.cpp.o
[ 58%] Building C object CMakeFiles/PHD.dir/libindiclient/indi.c.o
[ 61%] Building CXX object CMakeFiles/PHD.dir/libindiclient/wx/indigui.cpp.o
[ 64%] Building CXX object CMakeFiles/PHD.dir/libindiclient/wx/indi_io.cpp.o
[ 67%] Building CXX object CMakeFiles/PHD.dir/libindiclient/wx/indi_list.cpp.o
[ 70%] Building CXX object CMakeFiles/PHD.dir/libindiclient/wx/indi_config.cpp.o
[ 74%] Building CXX object CMakeFiles/PHD.dir/libindiclient/wx/indisave.cpp.o
[ 77%] Building CXX object CMakeFiles/PHD.dir/libindiclient/wx/wxled.cpp.o
[ 80%] Building CXX object 
CMakeFiles/PHD.dir/libindiclient/wx/wxchecktreectrl.cpp.o
[ 83%] Building C object CMakeFiles/PHD.dir/libindiclient/base64.c.o
[ 87%] Building C object CMakeFiles/PHD.dir/libindiclient/lilxml.c.o
[ 90%] Building CXX object CMakeFiles/PHD.dir/cam_VIDEODEVICE.cpp.o
[ 93%] Building CXX object CMakeFiles/PHD.dir/config_VIDEODEVICE.cpp.o
[ 96%] Building CXX object CMakeFiles/PHD.dir/v4lcontrol.cpp.o
[100%] Building CXX object CMakeFiles/PHD.dir/cameras/linuxvideodevice.cpp.o
Linking CXX executable PHD
/usr/bin/ld: cannot open output file PHD: Is a directory
collect2: ld returned 1 exit status
make[2]: *** [PHD] Error 1
make[1]: *** [CMakeFiles/PHD.dir/all] Error 2
make: *** [all] Error 2
lorne@nosferatu:~/PHD$ 



What version of the product are you using? On what operating system?
Source Code on this site

Please provide any additional information below.

I am getting a smooth compile intill link

What steps will reproduce the problem?

It always occurs in PHD with the native sx camera, but not with the sx-ascom 
driver. It concerns blurring and emphasis of camera noise for dark field 
exposures eg for 10s exposures and noise below 2000 counts. 
It does NOT occur for the sx driver in Nebulosity3 v.3.1.0

What is the expected output? What do you see instead?

- I expect a clean image showing only isolated hot pixels 
http://hewat.net/nog/sx/PHD-ASCOM-10s=blur=0-Max2000.jpg
(screen shot of 10s PHD exposure for sx-ascom driver}.
- I see blurred and emphasized noise that is difficult to filter
http://hewat.net/nog/sx/PHD-SX-10s-Max2000.jpg
(screen shot of 10s PHD exposure for native sx driver}.

What version of the product are you using? On what operating system?

This with v.1.14.0 of the Stark PHD under 64-bit Windows-7/8

Please provide any additional information below.

I suspect this unwanted effect is due to attempted de-interlacing, which cannot 
be switched off. De-interlacing should only be done after de-speckling to 
remove isolated hot pixels. The de-speckle filter and even-field de-interlacing 
code as used by ImageJ does a much better job 
http://rsbweb.nih.gov/ij/plugins/de-interlace.html 

I would like to see these algorithms as options in PHD, as well as a doubling 
of each step of exposure time (14 steps from 0.05 to 512s)

Not an open-phd issue per se, but this is a nice cam suited well for guiding 
IMHO.  I will use it with the Orion drivers in Windows, but seems Orion has yet 
to open up drivers/support for linux.

Hoping someone here can shed some light on it, otherwise this is a junk bug.

Thanks!

Mike

open-phd can't be compiled/used on latest kernels as v4l support has been 
dropped.

It seems like it is often possible to not be able to get a visually pleasing 
display of the guide camera. On my setup, the background never gets dark enough.

What steps will reproduce the problem?
1. Build open-phd-guiding on Linux Mint 12
2. Connect V4L camera
3. Push Cam Dialog Button

What is the expected output? What do you see instead?
Window/Dialog borders are missing, including - unfortunately - the 'Close' 
icon, so there's no way to close the dialog!

What steps will reproduce the problem?
1. Start PHD2
2. Drag the graph window out of the main window

What is the expected output? What do you see instead?

1. The left click handler does not seem to release the window when the button 
is released.
2. The background of the newly undocked window remains semi transparent (this 
could be caused by #1.

What version of the product are you using?

svn version 278

In PHD1 there are some guide settings that can be modified either on the Brain 
dialog, or from the graph window (aka "mini brain"), and this needs to be 
redesigned.

It currently provides setting that may not apply to the user (i.e. parameters 
for a guide algorithm that isn't in use), and it was pretty easy to do in PHD1, 
where there are a lot more global variables. 

It needs to be redesigned to be dynamic, like the brain box. When the user 
presses the guide button, we could create it, display it in the graph window, 
and destroy it when guiding ceases, since I don't think you can change any 
parameters that would make the box stale while guiding (you cannot change 
mounts, cameras, algorithms, etc.)

I want PHD to be able to take an image directory as input, this way it 
becomes easy to add new camera devices ...
I'm trying to build distribution on Mac ...
- I had to disable most of the camera's as the headers drivers are not 
included ...
- solved one ambiguous error by changing one of the wx header files, yuk 
...
- then I needed to change the path separator constant by _T("/") as again 
some overloaded issue became apparent.

Now however I'm blocked by the fact GC_USBST4.h and ShoeString.h are 
not present ... I can solve this but then I would not be able to build a PHD 
that I can use ... 
So question how do I obtain the missing files so that at least I can try to 
build a working prototype before I even begin to implement what I have in 
mind?

Did I mention I'm not a programmer ;-)

What steps will reproduce the problem?
1. connect to scope
2. disconnect from scope
3. check tracking

What is the expected output? What do you see instead?
scope should not move when driver session is finished

What version of the product are you using? On what operating system?
Phd guiding latest Win7 x86

Please provide any additional information below.

I am writing an ASCOM telescope driver, when the driver is finished
being used, I am putting the scope into a safe non-moving state
(tracking off). Most programs that use the driver will set the
connected property to false when disconnecting and I can safe the
scope and close the serial port. I tried putting the shutdown code in
a destructor which also seems to not get called.

looking at the code it appears that PHD Guiding does not disconnect
the scope when quitting is there a reason for this?

if not can the Connected property be set to false before
ScopeDriverDisplay->Release();

http://code.google.com/p/ascom-nexstar-telescope/source/browse/

- Set Windows to have 125% font size
- Open the graph
- You'll get a poor display

In the main window, the font size is fixed but the graph one must use the 
system default font.

I am trying to compile phd guiding code on TURBO c , will it work ? its giving 
compile time error.

Actually this is a feature request not a bug report but as I haven't seen
any place to enter one, I use this form.

As the source is drifting towards the open-source world I think it is high
time to give ideas to those who have enough energy to add new features to
this anyway wonderful product.

I use PHD guiding as a stand-alone guider (because my Canon 300D is not
supported by other - higher level - components) and it would be nice if the
program would solve the dithering between exposures. What I think of is a
simple button which would start the dither with any random number (max
value could be customizable via the "brain" dialog) with a nice standard
deviation around the original starting point.

Please consider something like this in the future and please inform me
about your decision.

-- joseph ([email protected])

In PHD2, the "Brain dialog" is created dynamically, and when I did that it 
seemed enough better than the PHD1 box that I moved on. An alpha tester pointed 
out that having tabs might be better yet, and after hearing the suggestion I 
agree.

There should probably be 1 tab for what is now a section.

the fonts of the advanced setup dialogue are too small.

What steps will reproduce the problem?
1.Start camera
2.set mount to oncamera
3.press telescope icon

What is the expected output? What do you see instead?
A telescope connected message within 1sec.
Nothing

What version of the product are you using? On what operating system?
PHD Guiding 1.12.4

Please provide any additional information below.
I did a wireshark trace on the windows version running under virtualbox. When 
you press the telescope icon under Windows a telescope connected comes back 
within 1sec and Nothing goes to the camera. i.e. when you press the telescope 
icon no data is sent down the USB link. This suggests to me that under Windows 
this option does nothing but return the connected message as it assumes that 
future mount commands will come from the camera.

This problem should be easy to fix(says he with a hopeful smile:)
Thanks,
Brian
PS. I can run USBMON and Wireshark traces here to get data if required.

What steps will reproduce the problem?
1. cmake .
2. make

What is the expected output? What do you see instead?
NULL not defined in indi_list.cpp. Patched that, but then a whole host of 
linker errors:

Linking CXX executable PHD
CMakeFiles/PHD.dir/cam_INDI.cpp.o: In function 
`Camera_INDIClass::ReadFITS(usImage&)':
cam_INDI.cpp:(.text+0x81b): undefined reference to `ffomem'
cam_INDI.cpp:(.text+0x8c0): undefined reference to `ffghdt'
cam_INDI.cpp:(.text+0x971): undefined reference to `ffgidm'
cam_INDI.cpp:(.text+0x993): undefined reference to `ffgisz'
cam_INDI.cpp:(.text+0x9c7): undefined reference to `ffthdu'
cam_INDI.cpp:(.text+0xb18): undefined reference to `ffgpxv'
cam_INDI.cpp:(.text+0xba1): undefined reference to `ffclos'
CMakeFiles/PHD.dir/cam_simulator.cpp.o: In function 
`Camera_SimClass::CaptureFull(int, usImage&, bool)':
cam_simulator.cpp:(.text+0x14a): undefined reference to `ffdkopn'
cam_simulator.cpp:(.text+0x177): undefined reference to `ffghdt'
cam_simulator.cpp:(.text+0x228): undefined reference to `ffgidm'
cam_simulator.cpp:(.text+0x24a): undefined reference to `ffgisz'
cam_simulator.cpp:(.text+0x27e): undefined reference to `ffthdu'
cam_simulator.cpp:(.text+0x3cf): undefined reference to `ffgpxv'
cam_simulator.cpp:(.text+0x458): undefined reference to `ffclos'
CMakeFiles/PHD.dir/frame_events.cpp.o: In function 
`MyFrame::OnSave(wxCommandEvent&)':
frame_events.cpp:(.text+0x59a): undefined reference to `ffinit'
frame_events.cpp:(.text+0x5d2): undefined reference to `ffcrim'
frame_events.cpp:(.text+0x60b): undefined reference to `ffppx'
frame_events.cpp:(.text+0x61e): undefined reference to `ffclos'
collect2: ld returned 1 exit status
make[2]: *** [PHD] Error 1
make[1]: *** [CMakeFiles/PHD.dir/all] Error 2
make: *** [all] Error 2


What version of the product are you using? On what operating system?
Latest checkout on Arch Linux x86_64

Please provide any additional information below.
N/A

What steps will reproduce the problem?
1. Open PHD
2. Click Camera Icon
3. Select V4L(2) Camera
4. Choose Videoloopback 0 input

What is the expected output? What do you see instead?
PHD 
VIDIOC_QUERYCAP error 25, Inappropriate ioctl for device
Segmentation fault



What version of the product are you using? On what operating system?
1.12.4
2.6.32-30-generic #59-Ubuntu SMP
Ubuntu 10.04


Please provide any additional information below.
I would love to see this project take shape.  Am very active in Linux and 
Astronomy but cannot code.

Mike

This might be interesting: http://code.google.com/p/skywatcher/

I did only a very basic test and it seems it's even usable from IronPython + 
Mono + Linux 64 bit :) Now it's time to setup Prolific RS-232 -> USB under 
Linux and shake the mount a bit...

What steps will reproduce the problem?
1. run INDI qhy driver and PHD
2. Data channel set to "compression"
3. Press the arrow button.

What is the expected output? What do you see instead?
The cycling period for images to be taken and displayed (when pressing arrow) 
is inconsistent. Sometimes it is 3 sec but sometimes it is as long as 40 sec. 
If selecting "Raw" the cycling period is solid at 8 sec. So, I want to increase 
the speed by using compression. However, the speed is inconsistent. Is it the 
problem of slow zlib used in compiling or something else? And how can I solve 
this problem?

What version of the product are you using? On what operating system?
Raspberry Pi + Raspbian (Debian Wheezy)
INDISERVER and PHD are run on Raspberry Pi with X server on another PC.

Please provide any additional information below.

What steps will reproduce the problem?
1. no Problem, just a small wish.

What is the expected output? What do you see instead?
My expectation is a binned picture out of the Lodestar-Guiding-Cam. This option 
is allready present in Nebulosity but in PHD i miss it very much.

What version of the product are you using? On what operating system?
PHD 1.14 on Win7 64bit


Please provide any additional information below.
I know that the Lodestar is realy sensitiv, but with an OfAxisGuider there is 
often the wish to do a binning. Focal length is with an OAG not the problem, 
but to find an bright enough star in this real small part of the sky is often 
to tricky.

PS Please excuse my bad english.

What steps will reproduce the problem?
1. svn checkout

svn checkout http://open-phd-guiding.googlecode.com/svn/trunk/ 
open-phd-guiding-read-only
Checked out revision 74.

2. cmake 

darren@frodo2 ~/Downloads $ cd open-phd-guiding-read-only
darren@frodo2 ~/Downloads/open-phd-guiding-read-only $ sudo cmake .
-- Configuring done
-- Generating done
-- Build files have been written to: 
/home/darren/Downloads/open-phd-guiding-read-only

3. make

darren@frodo2 ~/Downloads/open-phd-guiding-read-only $ sudo make
Linking CXX executable PHD
/usr/bin/ld: CMakeFiles/PHD.dir/libindiclient/indi.c.o: undefined reference to 
symbol 'inflate'
/usr/bin/ld: note: 'inflate' is defined in DSO /usr/lib/libz.so.1 so try adding 
it to the linker command line
/usr/lib/libz.so.1: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
make[2]: *** [PHD] Error 1
make[1]: *** [CMakeFiles/PHD.dir/all] Error 2
make: *** [all] Error 2

What is the expected output? What do you see instead?

"Make" doesn't work.  Errors result.

What version of the product are you using? On what operating system?

Running on Linux Mint Debian Edition (LMDE).  

Please provide any additional information below.

I think I have all the needed libraries (?):

||/ Name                                     Version             
+++-========================================-====================
ii  cmake                                    2.8.4+dfsg.1-2      
ii  libcfitsio3-dev                          3.260-1             
ii  libudev-dev                              167-3               
ii  libv4l-dev                               0.8.3-2             
ii  libwxgtk2.8-dev                          2.8.10.1-3.1        
ii  zlib1g-dev                               1:1.2.3.4.dfsg-3

Craig branch - No longer remembering screen location (at least on Windows) 
across sessions.

What steps are necessary for compiling the LE webcam drivers for linux?  is it 
possible or does the driver need porting?