click on connect on indi configure dialog will crash open phd guiding

[GoogleCodeExporter]

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. 

Original issue reported on code.google.com by benjamin...@gmx.de on 16 Dec 2009 at 5:00

[GoogleCodeExporter]

Original comment by geoffr...@gmail.com on 13 Jan 2010 at 9:01

• Changed state: Accepted

[GoogleCodeExporter]

please retry with the latest svn.
If it still happens, please start indiserver with -vvv in a seperate terminal 
and
capture its outputs

Original comment by geoffr...@gmail.com on 14 Jan 2010 at 2:49

• Changed state: WaitingForUser

[GoogleCodeExporter]

thanks. 
I will try it tomorrow and see if the telescope can now be guided with the 
program

Original comment by benjamin...@gmx.de on 14 Jan 2010 at 5:08

[GoogleCodeExporter]

Unfortately, there seems much to do.
Clicking on the movement-control tab and then using the telescope motion buttons
gives output this in the indi console.: 

2010-01-16T19:33:49: Driver indi_celestron_gps: initilizaing from Celeston GPS 
device...
2010-01-16T19:34:15: Driver indi_celestron_gps: Connecting to port: /dev/ttyUSB0
2010-01-16T19:34:17: Driver indi_celestron_gps: ConnectTel read 2 characters: x#
2010-01-16T19:34:17: Driver indi_celestron_gps: TelConnectFlag set to: 0
2010-01-16T19:34:56: Driver indi_celestron_gps: No ISwitch '��p��' in 
Celestron
GPS.Slew rate
2010-01-16T19:35:04: Driver indi_celestron_gps: No ISwitch '��p��' in 
Celestron
GPS.Slew rate
2010-01-16T19:35:20: Driver indi_celestron_gps: No ISwitch '��p��' in 
Celestron
GPS.Slew rate
2010-01-16T19:35:34: Driver indi_celestron_gps: No ISwitch '��p��' in 
Celestron
GPS.Slew rate
2010-01-16T19:35:42: Driver indi_celestron_gps: No ISwitch '��p��' in 
Celestron
GPS.Slew rate
2010-01-16T19:35:45: Driver indi_celestron_gps: No ISwitch '��p��' in 
Celestron
GPS.Slew rate
2010-01-16T19:35:55: Driver indi_celestron_gps: No ISwitch '��p��' in 
Celestron
GPS.Slew rate
2010-01-16T19:36:05: Driver indi_celestron_gps: No ISwitch '��p��' in 
Celestron
GPS.Slew rate

I want to add that this is rather dangerous.  Since if one can not stop or 
update the
telescope's motion properly, the scope could hang itself somewhere after it has
started its motion, like "forever drifting south" or such things.

And I have another question: 
I think I know what I must put in the indi_controls dialog.

But what values must I put in the indi_controls dialog, e.g for example to 
recognize
my webcam?

Original comment by benjamin...@gmx.de on 16 Jan 2010 at 8:03

[GoogleCodeExporter]

Looks like more 64-bit stuff.  I don't have the ability to run my scope on 64bit
linux, but I can test some things in my virtual machine.  I'll see what I can do
about these controls as well.

Original comment by geoffr...@gmail.com on 16 Jan 2010 at 9:25

• Changed state: Accepted

[GoogleCodeExporter]

I can't duplicate the behaviour you are seeing.  I assume you have the latest 
svn and
have rebuilt it?
Can you run:
indiserver -vvv indi_celestron_gps
then start PHD
Then (without connecting to the scope)
select INDI->Controls
(still without connecting to the scope) go to the 'Movement Control' screen and
select North, South, East, West
Then see what the indiserver logs show.
I've done the above and it is sending the proper buttons to the indiserver.  I 
don't
see anything like "��p��"

Original comment by geoffr...@gmail.com on 16 Jan 2010 at 10:37

• Changed state: WaitingForUser

[GoogleCodeExporter]

Without connecting the scope, Indi would just report that it can't do any 
movement
since the telescope is not connected.

To get the above reported behavior, I 
a)have to align my scope using an EQ_North_align, and then auto_align
b) connect it via an RS232 cable to an usb port of my laptop
c) download the latest svn and rebuild it
d) click on indi-controls dialog
e) set the correct port to /dev/USBtty0
d) click on connect

and then finally
click on the Movement Control buttons.

Then this happens.

Without connecting the scope, it says things like:

2010-01-17T03:56:14: Driver indi_celestron_gps: read message Celestron GPS   
'Cannot
change property West/East while the telescope is offline.'
2010-01-17T03:56:14: Client 5: queuing <message device='Celestron GPS' name=''>
2010-01-17T03:56:14: Driver indi_celestron_gps: read setSwitchVector Celestron 
GPS
TELESCOPE_MOTION_WE Idle
 MOTION_WEST='Off'
 MOTION_EAST='Off'
2010-01-17T03:56:14: Client 5: queuing <setSwitchVector device='Celestron GPS'
name='TELESCOPE_MOTION_WE'>
2010-01-17T03:56:14: Client 5: sending msg copy 1 nq 2:
<message device="Celestron GPS" timestamp="2010-01-17T03:56:14" message="Cannot
change property West/East while the telescope is offline."/>

If the scope is connected, and if I click the direction buttons, then I get the
output above. 
At first, my scope did not move. Then, after clicking around with the all the 
buttons
on that dialoges, It started a movement, though I could not stop it. 
My nextstar scope wend down towards south, and this was the moment where I 
feared the
Schmidt plate would crash against the tripod, so I disconnected (fortunately, I 
then
found that the scope is small enough, so it cannot crash against the the mount)

geoffreyh, you wrote:
 I don't have the ability to run my scope on 64bit
linux,

Why not?
If you have a linux distri like gentoo or ubuntu, programs like kstars or xephem
should work. On my box both applications work fine under 64 bit. Xephem and 
kstars
move my nexstar scope accurately. No scope that is compatible with indi should 
not
care whether indilib is compiled with 64 or 32 bit.

Original comment by benjamin...@gmx.de on 17 Jan 2010 at 4:05

[GoogleCodeExporter]

To run a 64 bit host that is able to connect to a scope, I would suggest the
following procedure:

1) Get a 64 bit linux live CD, for example a gentoo 64 bit live DVD
http://mirrors.us.kernel.org/gentoo//releases/amd64/10.1/

2) download the libindi source code 
http://www.indilib.org/index.php?title=Download_INDI

and the source code of open-phd guiding to an USB stick

3) start the 64 bit live cd and load a kde or gnome desktop

4) plug in the USB stick

5) compile indi-lib and open-phd-guiding

6) connect your scope

7) test the 64bit compiled indi and PHD 

Original comment by benjamin...@gmx.de on 17 Jan 2010 at 6:11

[GoogleCodeExporter]

The only machine I have that can connect to my scope can't run 64-bit linux.  My
other machines are either not in a place I can get the mount to, or can't boot 
to a
different OS due to policy.  I can run 64bit Linux via VirtualBox, but I can't 
get
access to the usb port if I do that.  I could just as easily ask you to boot a 
32bit
OS to see if it works there.

The reason I asked for a specific set of commands is that it shows that PHD 
does send
the correct switches to the scope on your system, so those ISwitch commands you 
are
getting aren't due to the switches being sent incorrectly, and may not be 
64bit-isms.
 I'm at a loss as to where they are coming from.  It is quite possible this is
something specific to the celestron-gps that I don't see with my autostar mount.

Original comment by geoffr...@gmail.com on 17 Jan 2010 at 4:43

• Changed state: Accepted

[GoogleCodeExporter]

geoffreyh wrote:
The only machine I have that can connect to my scope can't run 64-bit linux. 

Oh. I see. That is a problem. Well, what I think is interesting is this line 
here:

2010-01-16T19:34:17: Driver indi_celestron_gps: ConnectTel read 2 characters: x#
2010-01-16T19:34:17: Driver indi_celestron_gps: TelConnectFlag set to: 0

what does this mean? read 2 characters: x#

Perhaps the problem is located there? Perhaps it is not the switsches, but that 
the
program reads the data of the scope incorrectly? can this be?

Original comment by benjamin...@gmx.de on 17 Jan 2010 at 5:19

[GoogleCodeExporter]

those look like commands from INDI to the mount, not commands related to 
OpenPHD. 
But you said that your mount works fine in kstars, right?

it might be interesting to run it with kstars and log the results with 
indiserver in
debug-mode (-vvv) to compare to what we are getting.

Original comment by geoffr...@gmail.com on 28 Jan 2010 at 6:53

[GoogleCodeExporter]

hi!

may I add a comment? i am afraid that there is an issue with the german locale. 
my
ubuntu 9.10 box works fine with kstars and appears to work with open PHD 
guiding if i
start an INDI server manually and connect to this one.

some other guys - there was a recent discussion on this topic in the german
Astrotreff.de forum - had trouble, which resolved when they localized their 
system to
"English". I did not see this since I have an english system (with a german 
keyboard
- this does not affect the whole thing). however, i also ran open PHD with a 
separate
INDI server last night on a german system, and it connected fine and did 
something ...

yours
wolfi 

Original comment by wbirkfel...@gmail.com on 28 Jan 2010 at 8:47

[GoogleCodeExporter]

OK. I tried it with kstars yesterday (same actions. Just clicking the direction
buttons). Attached to this post is the indiserver -vvv celestron_gps output with
scope connected from kstars.

Apparently no line like:2010-01-16T19:34:17: Driver indi_celestron_gps: 
ConnectTel
read 2 characters: x#
2010-01-16T19:34:17: Driver indi_celestron_gps: TelConnectFlag set to: 0

Appears when kstars is used.

Original comment by benjamin...@gmx.de on 12 Feb 2010 at 7:20

Attachments:

• indi_kstars.txt

[GoogleCodeExporter]

Hi Benjamin,

Does this issue still exist today now that Geoffrey's INDI work got ported back 
into trunk ?

-- Hans

Original comment by h...@dse.nl on 7 May 2014 at 10:23

• Changed state: WaitingForInput

[GoogleCodeExporter]

Original comment by h...@dse.nl on 7 May 2014 at 10:25

• Added labels: OpSys-Linux