I can get the guiding working fine.
But when i start the imaging camera in either sharpcap or Altair capture both stop taking frames.
Tried on another laptop and the same happens.
I can get both to take image frames at the same time, one in sharpcap and the other in altaircapture to prove the usb hardware is coping.
If i start phd2 with just the 290M plugged in all works. Plug the 183C in and it drops frames and phd2 errors saying no frames taken in 25sec.
Stop looping phd2 and the image camera starts taking frames. Re start looping and i hear the image cameras fan stop for a second. This makes me wonder if PHD2 is signalling both cameras?
There is one option in PHD2 for Altair camera. Can it understand which Altair to talk to?
Thanks Rob
By reopening the setup and fork i can re select the 290M.
Just need to try it live again
Rob
Each time i restart sharpcap with the altair 183C phd2 is dumping the 290m and selecting the 183C?
Is there a way to stop phd2 from recognising the 183C to stop this happening?
After playing with the ST4 setup i tested connection via ASCOM.
Got the mount slewing via Cartes du using the simulated camera.
When trying to connect to the Altair Ascom camera (downloaded the driver from Altairs website) i am getting the error on this attachment.
Tried copying the dll file from the altaircapture folder to the phd2 folder but that causes an error preventing phd2 to open.
I have tried removing both phd2 and the altair ascom drivers but get the same attached error. Phd is latest download.
In the camera option in PHD2 i am getting two entries for Altair Ascom. But both do the same thing?
Cheers Rob
Tried copying the dll file from the altaircapture folder to the phd2 folder but that causes an error preventing phd2 to open.
I have tried removing both phd2 and the altair ascom drivers but get the same attached error. Phd is latest download.
I may have worked this out. Found an older version of the altair ascom drivers. Just trying now but that seems to have allowed me to connect. Will test tonight if can.
Thanks Rob
While the older version of the Altair Ascom drive was showing connected to the 290M i didnt get an stars show in phd2.
Had focused it first in sharpcap before a reboot of the laptop.
The Ascom version was from a nov. 2017 posting by nick on facebook.
My 290M is the usb 2.0 version from 2017
As well as just a black image while looping, when i stopped the looping it was hanging the app.
Assume you have to use the Ascom camera if using the ascom mount connection?
The mount was running via Ascom ok although star position was a long way out even though i had polar aligned in sharpcap.
Tried to syn cdc to polaris after locating via eqmod arrows. Check box came up saying am i pointing at polaris but after clicking the cross hairs wouldn't re centre. Does cdc only sync to certain stars?
Assume you have to use the Ascom camera if using the ascom mount connection?
Tried to syn cdc to polaris after locating via eqmod arrows. Check box came up saying am i pointing at polaris but after clicking the cross hairs wouldn't re centre. Does cdc only sync to certain stars?
I have the latest version of PHD2
It updated recently and i have also removed and re installed.
Same with the altair ascom drivers from their website. That is the version which prevents phd2 from opening if selected.
So if i run the mount via ascom but use the standard altair camera from the drop down instead of the altairascom do i lose any benefits?
What does the ascom for the camera achieve over the standard altair camera?
Thanks Rob
I have the latest version of PHD2
It updated recently and i have also removed and re installed.
Same with the altair ascom drivers from their website. That is the version which prevents phd2 from opening if selected.
So if i run the mount via ascom but use the standard altair camera from the drop down instead of the altairascom do i lose any benefits?
What does the ascom for the camera achieve over the standard altair camera?