Hi, just found out about your driver....what a find... I have 2 sxw mounts with the giant gameboys that I use for outreach. I've tried to install as per the instructions on the indi devices page, but I end up with the following error:

Package indi-starbook is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Do you have any ideas? or is it me .....
Thanks again
Terry

Well, you are dealing with my lack of response for sudden interest around this driver.
This driver is only 1 month old, so source-code is still quite hot. Therefore all updates are available in nightly channel. I updated link in devices page. You can lookup nightly ppa in downloads.

As for better documentation. For now I will have trouble keeping it up to date with current build.
I will point to github.com/indilib/indi/tree/master/3rdparty/indi-starbook for better documentation. It's in README.
But with increasing interest I will try to make it better over next month.

Stay safe, have fun, and don't trust programmers (like me).

Hi, thanks for that..... just installed, and it connects to the starbook.. When I give it a command, I get an error message at the bottom of the screen
2019-01-10T19:23:03: [ERROR] Goto [ERROR_ILLEGAL_STATE]: http://192.168.0.9:80/GOTORADEC?RA=19+16.11&DEC=015+07 . Most likely me...
any ideas?
Thanks again for getting something started , I'm more than willing to be a 'beta' tester...
cheers

When you first power up Starbook you should navigate to SCOPE mode using keys, or go to http://192.168.0.9:80/START
Why? Starbook is a state machine. When it powers up, it's in INIT state. When you enter SCOPE state it will then react to GOTORADEC.

Then you should be able to send commands. I would greatly appreciate full logs. I'm still working on better logging. I would use this driver myself when it will hit 0.5. It looks like you are using 0.3, even though in ppa it's 0.1.

Ok, seem to be getting somewhere..... I'm getting a time error and the driver forgets the ip address of the starbook, and goes back to the default. this is the log...

2019-01-10T20:03:01: [INFO] Goto [OK]
2019-01-10T20:02:13: [INFO] Goto [OK]
2019-01-10T20:02:00: [INFO] Sync [OK]
2019-01-10T20:01:22: [INFO] Goto [OK]
2019-01-10T20:00:56: [ERROR] updateTime [ERROR_ILLEGAL_STATE]: http://192.168.0.9:80/SETTIME?TIME=2019+01+10+20+00+56
2019-01-10T20:00:56: [INFO] Device configuration saved.
2019-01-10T20:00:56: [INFO] Saving device configuration...
2019-01-10T20:00:56: [INFO] Device configuration applied.
2019-01-10T20:00:56: [INFO] Loading device configuration...
2019-01-10T20:00:56: [INFO] Version [OK]: 2.7B50
2019-01-10T20:00:56: [INFO] Starbook is online.
2019-01-10T20:00:56: [WARNING] Found old handle, recreating
2019-01-10T20:00:56: [INFO] Creating HTTP handle for 192.168.0.9@80
2019-01-10T20:00:39: [ERROR] Version [ERROR]: Can't get firmware version
2019-01-10T20:00:36: [INFO] Creating HTTP handle for 192.168.0.102@80

although it says goto is ok, nothing has happened.
thanks again,
Terry

Commands are now working...... just the issue with UTC and the driver/indi not keeping the ip address...
Yet again , thanks....thought I was going to have to stay with ms virus for the rest of my days....

Good to hear.
I hope to resolve github.com/indilib/indi/issues/810 in 0.4.
And UTC time. You can only set it in INIT mode. I know, Starbook is a moody device. Errors should become natural to you when using this driver. And "ms virus" is? I guess it's windows with ASCOM driver from Peter Enzerink? enzerink.net/peter/blog/2008/06/28/ascom-star-book-driver

You guess right... Ran XP for years without problems, but then they stopped support..my astro camera is nolonger supported..Have always had linux running for meade lx..... Peter's driver was great, but yet again nolonger supported due to lack of interest from Vixen. Now I can set the observatory up with a RPI3...
by the way, programmers are not that bad... Dad was one for many years....
Let me know when a new version comes out, and I'll do my best to break / make it work ... 2 mounts and rempte on RPI.
Thanks again.

Hi,
I've been using the driver for a week.... not too many restarts.. really pleased to have found out about your hard work...
The only problems are the UTC settings throwing up errors and the ip address...keeps setting itself to 192.168.0.102:80 even just after a server restart.
Thanks again

Version 0.4 will hit nightly PPA with this PR github.com/indilib/indi/pull/841
It should provide mostly error free operation.
I'm looking for contributors, so I could make development less dependent on a single person.
Please tag me in PR and issues on github regarding this driver. I mostly work on my own fork github.com/not7cd/indi

Current roadmap:
1. Ability to auto-initialize Starbook when in wrong internal state
2. Implement rest of Starbook commands, or at least GETPLACE command
3. Documentation!
4. Figure what's wrong with HOME and RESET command.

Last one is pointed towards other users. I can't get HOME command working. I get ERROR_FORMAT. Please go to http://starbook-ip/HOME and see if it's working for you. Might be a regression from Vixen.

After that, there is nothing more to do. Maybe more error handling. But I want to avoid driver "smartness" for now.

Hi,
great news..... I've tried to update, but keep on getting version 0.3.... I've tried doing a full nightly update, but still the same..... any ideas, or instructions? It's bound to be me...
cheers
Terry

Still trying....today I uninstalled kstars and all the indi drivers. I've reinstalled from nightly builds and Starbook is still version 0.3... message on install: Setting up indi-starbook (0.1~201902020310~ubuntu16.04.1). I must be missing someting