FCUSB/JMI PCFC with CCDSoft
FCUSB/JMI PCFC with CCDSoft
I'm attempting to use the JMI PC Focus controller, similiar if not identical to the FCUSB, with the @focus and manual focusing features of
CCDSoft. Every time I connect to the focus control an error message
is displayed which is The ASCOM Focuser reported an incorrect value for the MaxPos property. What does this mean? Is there anyway around this error? Is there a more recent update for the Focuser ASCOM driver software for the FCUSB that would work with the PC Focus Control?
CCDSoft. Every time I connect to the focus control an error message
is displayed which is The ASCOM Focuser reported an incorrect value for the MaxPos property. What does this mean? Is there anyway around this error? Is there a more recent update for the Focuser ASCOM driver software for the FCUSB that would work with the PC Focus Control?
-
- Site Admin
- Posts: 1060
- Joined: Fri Apr 28, 2006 1:34 pm
- Location: central Iowa
- Contact:
Doug,
There is some additional info that might help diagnose the problem. Two CCDSoft error codes appear after the IN and OUT buttons on the Focus tab are activiated. Code 218 Limits Exceeded occurs when the IN button is depressed. Code 1 ACL undefined Error happens after clicking OK on the MaxPos property error box after the OUT button is depressed. Hope this helps.
There is some additional info that might help diagnose the problem. Two CCDSoft error codes appear after the IN and OUT buttons on the Focus tab are activiated. Code 218 Limits Exceeded occurs when the IN button is depressed. Code 1 ACL undefined Error happens after clicking OK on the MaxPos property error box after the OUT button is depressed. Hope this helps.
-
- Site Admin
- Posts: 1060
- Joined: Fri Apr 28, 2006 1:34 pm
- Location: central Iowa
- Contact:
-
- Site Admin
- Posts: 1060
- Joined: Fri Apr 28, 2006 1:34 pm
- Location: central Iowa
- Contact:
Bill,
After some dialogue with Software Bisque tech support and the fellow that wrote the FocusAPI that allows ASCOM drivers to work with CCDSoft, I don't think there is a quick and easy solution to this problem. CCDSoft expects a focuser to be able to report its position. Because the FCUSB has no knowledge of its position, it reports it back as an error. I may try to write a FocusAPI plugin that would allow the FCUSB to work with CCDSoft, but until I can get a temporary license for CCDSoft so I can debug the FocusAPI, I won't be able to work on it.
After some dialogue with Software Bisque tech support and the fellow that wrote the FocusAPI that allows ASCOM drivers to work with CCDSoft, I don't think there is a quick and easy solution to this problem. CCDSoft expects a focuser to be able to report its position. Because the FCUSB has no knowledge of its position, it reports it back as an error. I may try to write a FocusAPI plugin that would allow the FCUSB to work with CCDSoft, but until I can get a temporary license for CCDSoft so I can debug the FocusAPI, I won't be able to work on it.
Doug,
I thought it might be as simple as FCUSB software providing some kind of positional data to keep the FocusAPI and CCDSoft happy. If you're looking for help in debugging any software to correct the problem, maybe by providing my equipment and CCDSoft as test bed for any downloaded test software that you might want to try could shorten debug time? I would think it worth while for FCUSB to work with the focus features of CCDSoft.
I thought it might be as simple as FCUSB software providing some kind of positional data to keep the FocusAPI and CCDSoft happy. If you're looking for help in debugging any software to correct the problem, maybe by providing my equipment and CCDSoft as test bed for any downloaded test software that you might want to try could shorten debug time? I would think it worth while for FCUSB to work with the focus features of CCDSoft.
-
- Site Admin
- Posts: 1060
- Joined: Fri Apr 28, 2006 1:34 pm
- Location: central Iowa
- Contact:
Bill,
I'll modify the ASCOM driver so that it reports "position" and email it to you to give a try. I probably won't get to it until Sunday at the earliest. This will not indicate the actual position, but an approximate position based upon how much time in milliseconds the motor has been asked to move. Hopefully that will keep CCDSoft happy, and provide a workable solution.
I'll modify the ASCOM driver so that it reports "position" and email it to you to give a try. I probably won't get to it until Sunday at the earliest. This will not indicate the actual position, but an approximate position based upon how much time in milliseconds the motor has been asked to move. Hopefully that will keep CCDSoft happy, and provide a workable solution.
-
- Site Admin
- Posts: 1060
- Joined: Fri Apr 28, 2006 1:34 pm
- Location: central Iowa
- Contact:
I have the same issue, using CCDSoft and a JMI Motofocus. I would be happy to beta the driver also.dpanderson wrote:Bill,
I'll modify the ASCOM driver so that it reports "position" and email it to you to give a try. I probably won't get to it until Sunday at the earliest. This will not indicate the actual position, but an approximate position based upon how much time in milliseconds the motor has been asked to move. Hopefully that will keep CCDSoft happy, and provide a workable solution.
Kent
-
- Site Admin
- Posts: 1060
- Joined: Fri Apr 28, 2006 1:34 pm
- Location: central Iowa
- Contact:
-
- Site Admin
- Posts: 1060
- Joined: Fri Apr 28, 2006 1:34 pm
- Location: central Iowa
- Contact:
Thanks Doug, looking forward to it.dpanderson wrote:Bill, Kent,
Just a note to let you know I finally have some time to work on this. I have a basic FocusAPI for the FCUSB, and should have one for the PCFC soon. There are a few thing I want to add, but then I'll get out a beta for each of you to try.
KEnt