I just installed the SGP API Guider and when I pick it from the list, PHD fails to connect to the camera and error message says Ascom driver is missing cameraxsize property. I tried both drivers through ascom camera chooser and the main list. The only thing is the settings is enable logging.
Yeah that won’t work, as you’ve discovered. Only one application can connect to an sbig camera at once. Do the sgp api guider actually talks to sgp that talks to the camera
I downloaded a trial copy a while back. When I saw it used phd I uninstalled it thinking it’s not possible without looking further. May I get another trial?
I get the same error message. I use the latest version of SGP and PHD2. My camera is an Sbig ST-2000XM
In SGP camera settings I chose internal guide chip.
The first thing I do is starting SGP pro and connecting my camera. Then I start Stellarium scope, Stellarium, Eqmod and lastly, I start PHD2.
In PHD2 I select SGP API guider and when I try to connect I receive the “CameraXsize is missing” error message.
Try selecting “External” for the guide chip in SGP. SBIG changed the meaning of these a while back. I can’t recall if the ST-2000XM has 2 guide chips or just 1.
Hello,
today I want to try SGP if it is compatible to my hardware. Both my Moravian G2-8300 and my old SBIG STL11000 could be connected successfully. Both filter wheels work too. The SBIG filter wheel selection “auto” does not work at all, but I know which manual selection is righ.
Connecting PHD2 (v2.5) to the internal guider chip via your SGP API fails. The error message says Ascom driver is missing cameraxsize property. What should I do?
Thomas
The camera is conneced in SGP, I took some images successfully… The guider chip is selected as internal guider, as it is. I used SGP API Guider v1.3.0. What should I check next?
Thomas
Unfortunately I can’t seem to duplicate this with my STL-11000. The only other thing I can think of is maybe windows is blocking the API port for SGP. If you go here does it resolve when SGP is running? http://localhost:59590/metadata
Hello,
thanks for your fast reply, you gave the right way.
I found that SGP has to be started with the option “as administrator”. The second was that I had select SGP in the windows firewall. The error message “CamereXsize” it misleading. Now the Guider Chip is available in PHD2.
I am very sorry that I come with a another issue, which I cannot resolve at my own. It is not clear, if it is a SGP API Guider issue, but I had not this case with my two other guidcams (ASI and QHY).
Issue:
PHD said, that I had to make a new dark library, right. Immediately after finishing it, the message apeared again. I tried it many times, no success to make a new dark lib.
The dialog in the middle is german. It says “Operation complete, Dark Lib created”. After closing this dialog, the message “Dark library does not match the camera in this profile” reapeared again.
You should not need to run SGP as Admin. And I would recommend that you do NOT run it as Admin as it can cause other driver issue. Allowing it through the firewall should be adequate. When first ran windows should prompt you for this exception. I’m guessing it was denied.