There is some fundamental breakage between feisty and gutsy, let me explain:
I use kstars to control my telescope. This uses the Meade standard cable set, which includes a pl2303 USB->serial adapter.
If I boot feisty, kstars will drive the telescope just fine using the pl2303. 8)
If I boot gutsy, kstars will read firmware data from the Meade Autostar handset and get basic firmware data, but it will not slew the telescope or send other commands to the telescope.
I have a symlink /dev/telescope I set up in my udev rules, this is correct each time, it points happily to what ever /dev/ttyUSB... the pl2303 driver has made the actual pl2303 serial adapter. Permissions and groups are fine (if not how could kstars read the firmware data anyway). i.e. I am a member of dialout, and dialout has rw on the relevant ttyUSB... device.
Log files reveal nothing abnormal unless kstars is doing some logging that I don't know about.
More specifically, here is a list of what can and can't be done with kstars under gutsy with the pl2303 USB->serial adapter:
1. Start lx90 service from device manager. Device manager log looks normal.
2. Goto the star chart, right click, select lx90/connect - does not connect.
3. Goto the INDI control panel, click on connect, connects, reads back firmware, site, etc.
4. Goto the star chart, right click, lx90 shows as connected now. Issue commands to slew, sync, etc. Nothing happens.
5. Select centre and track crosshair, nothing happens, manually instruct kstars to centre the object the telescope is pointed at, voila, there are the crosshairs.
In case anyone is speed reading this post, let me emphasise again that if I run kstars under feisty, everything works fine.
Are there any known issues? Is this a problem with the pl2303 driver, or kstars?
Thanks.
UPDATE: I tried an older pl2303 driver (2.16.20.16) with my 2.16.22.14 current kernel, no difference, behaviour is still broken. I have also tried renaming my kstarsrc and setting up from scratch, and a complete reinstall of kstars with no success.
I use kstars to control my telescope. This uses the Meade standard cable set, which includes a pl2303 USB->serial adapter.
If I boot feisty, kstars will drive the telescope just fine using the pl2303. 8)
If I boot gutsy, kstars will read firmware data from the Meade Autostar handset and get basic firmware data, but it will not slew the telescope or send other commands to the telescope.
I have a symlink /dev/telescope I set up in my udev rules, this is correct each time, it points happily to what ever /dev/ttyUSB... the pl2303 driver has made the actual pl2303 serial adapter. Permissions and groups are fine (if not how could kstars read the firmware data anyway). i.e. I am a member of dialout, and dialout has rw on the relevant ttyUSB... device.
Log files reveal nothing abnormal unless kstars is doing some logging that I don't know about.
More specifically, here is a list of what can and can't be done with kstars under gutsy with the pl2303 USB->serial adapter:
1. Start lx90 service from device manager. Device manager log looks normal.
2. Goto the star chart, right click, select lx90/connect - does not connect.
3. Goto the INDI control panel, click on connect, connects, reads back firmware, site, etc.
4. Goto the star chart, right click, lx90 shows as connected now. Issue commands to slew, sync, etc. Nothing happens.
5. Select centre and track crosshair, nothing happens, manually instruct kstars to centre the object the telescope is pointed at, voila, there are the crosshairs.
In case anyone is speed reading this post, let me emphasise again that if I run kstars under feisty, everything works fine.
Are there any known issues? Is this a problem with the pl2303 driver, or kstars?
Thanks.
UPDATE: I tried an older pl2303 driver (2.16.20.16) with my 2.16.22.14 current kernel, no difference, behaviour is still broken. I have also tried renaming my kstarsrc and setting up from scratch, and a complete reinstall of kstars with no success.
Comment