Comments for Online with Peter Enzerink http://enzerink.net/peter/blog Welcome to the entry point for my presence on the internet Thu, 06 May 2010 03:09:53 +0000 hourly 1 http://wordpress.org/?v=abc Comment on ASCOM Star Book Driver by Peter Enzerink http://enzerink.net/peter/blog/2008/06/28/ascom-star-book-driver/comment-page-1#comment-124 Peter Enzerink Thu, 06 May 2010 03:09:53 +0000 #comment-124 The current driver works well for most people. The update I have been very slowly progressing is mostly to ensure the driver remains compliant with the latest version of ASCOM and will also fix some bugs (which require more investigation and testing re the best solution). The current driver works well for most people. The update I have been very slowly progressing is mostly to ensure the driver remains compliant with the latest version of ASCOM and will also fix some bugs (which require more investigation and testing re the best solution).

]]> Comment on ASCOM Star Book Driver by Jim Fusco http://enzerink.net/peter/blog/2008/06/28/ascom-star-book-driver/comment-page-1#comment-123 Jim Fusco Thu, 06 May 2010 02:25:52 +0000 #comment-123 Hi Pete, Thanks for the great job. You made mention of a update comming out and also updates to people who help support the driver program 2008. I have made support over a year ago, but haven't seen updates. Hi Pete,
Thanks for the great job. You made mention of a update comming out and also updates to people who help support the driver program 2008. I have made support over a year ago, but haven’t seen updates.

]]> Comment on ASCOM Star Book Driver by Peter Enzerink http://enzerink.net/peter/blog/2008/06/28/ascom-star-book-driver/comment-page-1#comment-122 Peter Enzerink Sun, 18 Apr 2010 02:53:07 +0000 #comment-122 Hi Marques. There is an issue with version detection (a throw back from when features in the firmware directly affected the driver). It is largely cosmetic and you should be able to ignore the error and continue. Hi Marques. There is an issue with version detection (a throw back from when features in the firmware directly affected the driver). It is largely cosmetic and you should be able to ignore the error and continue.

]]> Comment on ASCOM Star Book Driver by Marques http://enzerink.net/peter/blog/2008/06/28/ascom-star-book-driver/comment-page-1#comment-121 Marques Sat, 17 Apr 2010 10:55:32 +0000 #comment-121 Hi, I installed your drive a while ago, and although I usually don´t use it bacause I still don´t control the mount with my telescope except for autoguiding, the tests that I did when I installed it were very satisfaying. Congratulations and thanks for sharing your work for free. Anyway, I recently reinstalled the OS, and I just tried to install your driver again, but I couldn´t. The reason is that I now have V2.1 and your driver says that it is too old. I don´t know if that is a bug easy to fix and if you are still willing to do it, but I whould really apreciate it. Thanks in advance. Hi, I installed your drive a while ago, and although I usually don´t use it bacause I still don´t control the mount with my telescope except for autoguiding, the tests that I did when I installed it were very satisfaying. Congratulations and thanks for sharing your work for free.

Anyway, I recently reinstalled the OS, and I just tried to install your driver again, but I couldn´t. The reason is that I now have V2.1 and your driver says that it is too old. I don´t know if that is a bug easy to fix and if you are still willing to do it, but I whould really apreciate it.

Thanks in advance.

]]> Comment on New Star Book driver coming by Peter Enzerink http://enzerink.net/peter/blog/2008/08/04/new-driver-coming/comment-page-1#comment-70 Peter Enzerink Sat, 10 Apr 2010 11:20:05 +0000 #comment-70 Clayton, people have had varying experiences using the Sphinx for photography. I suggest joining the yahoo group and posing your questions there. The driver as it stands works fine apart from the bug I mentioned in previous comments so it is a case of "if it ain't broke, don't fix it". Thanks for the offer though. Clayton, people have had varying experiences using the Sphinx for photography. I suggest joining the yahoo group and posing your questions there.

The driver as it stands works fine apart from the bug I mentioned in previous comments so it is a case of “if it ain’t broke, don’t fix it”. Thanks for the offer though.

]]> Comment on New Star Book driver coming by Clayton Summers http://enzerink.net/peter/blog/2008/08/04/new-driver-coming/comment-page-1#comment-69 Clayton Summers Sat, 10 Apr 2010 04:36:54 +0000 #comment-69 Peter, I'm getting my Sphinx next week, and already see that I will be looking at controlling it via the Ethernet port. I looks like your work on the new driver may be going slow. Any chance of getting source code and possibly helping out? I'm a product manager in the US for a Japanese company that sells precision motorized stages (among other things), so I am familiar with the frustrations of Japanese documentation (or lack thereof). I also have colleagues in Japan that might be able to assist with getting information from Japan. Another thought that has occurred to me is if it possible to actually guide from the PC, using a USB camera and doing the image processing on the PC, avoiding any special guiding hardware. Thanks for all of your efforts over what looks to be several years. Best regards, Clayton Summers Peter,

I’m getting my Sphinx next week, and already see that I will be looking at controlling it via the Ethernet port.

I looks like your work on the new driver may be going slow. Any chance of getting source code and possibly helping out? I’m a product manager in the US for a Japanese company that sells precision motorized stages (among other things), so I am familiar with the frustrations of Japanese documentation (or lack thereof). I also have colleagues in Japan that might be able to assist with getting information from Japan.

Another thought that has occurred to me is if it possible to actually guide from the PC, using a USB camera and doing the image processing on the PC, avoiding any special guiding hardware.

Thanks for all of your efforts over what looks to be several years.

Best regards,

Clayton Summers

]]> Comment on Vixen Star Book FAQ by Rob Burrowes http://enzerink.net/peter/blog/2008/06/24/vixen-star-book-faq/comment-page-1#comment-22 Rob Burrowes Sun, 14 Mar 2010 01:54:47 +0000 #comment-22 /move does work, but only has an effect if the values are from 10 .. 19. /move does work, but only has an effect if the values are from 10 .. 19.

]]> Comment on Vixen Star Book FAQ by Peter Enzerink http://enzerink.net/peter/blog/2008/06/24/vixen-star-book-faq/comment-page-1#comment-21 Peter Enzerink Sun, 14 Mar 2010 00:07:18 +0000 #comment-21 It is best to align the scope then not use the StarBook further as the ASCOM driver will become confused if state is changed outside of the software. It is best to align the scope then not use the StarBook further as the ASCOM driver will become confused if state is changed outside of the software.

]]> Comment on Vixen Star Book FAQ by Rob Burrowes http://enzerink.net/peter/blog/2008/06/24/vixen-star-book-faq/comment-page-1#comment-20 Rob Burrowes Sat, 13 Mar 2010 23:52:12 +0000 #comment-20 My fault. Sort of. I manually had put the starbook into scope mode. I think this was causing a conflict between your commands and the starbook firmware. Both are trying to control the scope. I have done a tcpdump of the traffic to see what is happening. The /start command returns an error if the starbook is not in the INIT state. The starbook was already in the SCOPE state. Hence the initial error trying to connect. The /stop command also returns an error if the scope state had been manually put into SCOPE mode. It doesn't give the error if the /start command put the starbook into SCOPE mode, though it doesn't seem to stop the scope either. It does work when the starbook is doing a goto command. It does stop the slew if it is sent then. I looked at the latitude and longitude in the tcp dump, and they are 1 minute out too, so your driver is returning what it is being given by the starbook, which means the starbook is at fault. The screen shows what I entered. I found a /gohome?home=0 command too, which returned the scope to the powered on position. Just randomly typing to see what it would do:) I couldn't see what the move? command did. Your driver sends it, but the scope didn't move if I changed the values from 0. The command was not rejected. Is this a set up for another command? My fault. Sort of. I manually had put the starbook into scope mode. I think this was causing a conflict between your commands and the starbook firmware. Both are trying to control the scope.

I have done a tcpdump of the traffic to see what is happening. The /start command returns an error if the starbook is not in the INIT state. The starbook was already in the SCOPE state. Hence the initial error trying to connect.

The /stop command also returns an error if the scope state had been manually put into SCOPE mode. It doesn’t give the error if the /start command put the starbook into SCOPE mode, though it doesn’t seem to stop the scope either. It does work when the starbook is doing a goto command. It does stop the slew if it is sent then.

I looked at the latitude and longitude in the tcp dump, and they are 1 minute out too, so your driver is returning what it is being given by the starbook, which means the starbook is at fault. The screen shows what I entered.

I found a /gohome?home=0 command too, which returned the scope to the powered on position. Just randomly typing to see what it would do:)

I couldn’t see what the move? command did. Your driver sends it, but the scope didn’t move if I changed the values from 0. The command was not rejected. Is this a set up for another command?

]]> Comment on Vixen Star Book FAQ by Peter Enzerink http://enzerink.net/peter/blog/2008/06/24/vixen-star-book-faq/comment-page-1#comment-19 Peter Enzerink Sat, 13 Mar 2010 07:12:38 +0000 #comment-19 Hmm I haven't seen that problem before but I'm not familiar with StellariumScope. You are best off enquiring on the <a href="http://tech.groups.yahoo.com/group/Vixen_Sphinx/" rel="nofollow">Yahoo Group</a> regarding usage and compatibility as there are many combinations of setup and I've only tested a fraction. Hmm I haven’t seen that problem before but I’m not familiar with StellariumScope.

You are best off enquiring on the Yahoo Group regarding usage and compatibility as there are many combinations of setup and I’ve only tested a fraction.

]]>