Jump to content

  •  

CNers have asked about a donation box for Cloudy Nights over the years, so here you go. Donation is not required by any means, so please enjoy your stay.

Photo

Evolution + Wedge + CPWI First Try Last Night Issue

  • Please log in to reply
8 replies to this topic

#1 Smithry3

Smithry3

    Sputnik

  • -----
  • topic starter
  • Posts: 34
  • Joined: 20 Nov 2016
  • Loc: Michigan

Posted 24 April 2019 - 01:14 PM

Hello, I've been excited to try out the new CPWI software with my Evolution mount.  One of the reasons I wanted to use it was because I've always been limited to two star alignments when doing an EQ North Polar align with the Nexstar + hand control.  I'm also interested in saving the alignments and using them on multi-day imaging sessions. 

 

The CPWI software worked great, I connected through my hand controller using the serial connection that I've used in the past for auto-guiding.  Which leads me to my issue.  I was unable to connect to my mount using PHD2 while connected using CPWI.  It complained that it was unable to connect via COM4.  I'm assuming that CWPI is using ASCOM and port COM4 and that is why PHD2 is unable to connect.  I tried to select a different port in PHD2 as I've had to do in the past but only COM4 was available for selection.  Has anybody encountered this or have any suggestions on how I might get around this?

 

Thanks!

 

Ryan


Edited by Smithry3, 24 April 2019 - 01:23 PM.

  • Stefan042 likes this

#2 skaiser

skaiser

    Viking 1

  • -----
  • Posts: 540
  • Joined: 16 Oct 2010
  • Loc: dallas Texas

Posted 24 April 2019 - 02:31 PM

Ryan

 You have to use the CPWI (ASCOM)  interface connection when you use CPWI.

This is different from the Celestron Ascom connection.



#3 Rac19

Rac19

    Apollo

  • *****
  • Posts: 1422
  • Joined: 05 Aug 2016

Posted 24 April 2019 - 04:00 PM

Ryan

 You have to use the CPWI (ASCOM)  interface connection when you use CPWI.

This is different from the Celestron Ascom connection.

I can second that. When you are using CPWI, other (third party) apps should connect through CPWI, NOT directly to the HC/Serial/USB port. I have done this successfully with APT and SharpCap.



#4 Smithry3

Smithry3

    Sputnik

  • -----
  • topic starter
  • Posts: 34
  • Joined: 20 Nov 2016
  • Loc: Michigan

Posted 24 April 2019 - 11:52 PM

Thanks for pointing me in the right direction, I needed to select CPWI (ascom) instead of Celestron Telescope (ascom) in the Phd2 dialog.


Edited by Smithry3, 25 April 2019 - 01:27 PM.

  • Stefan042 likes this

#5 Euphonia

Euphonia

    Sputnik

  • *****
  • Posts: 25
  • Joined: 26 Jan 2015

Posted 18 July 2019 - 08:54 PM

CPWI ASCOM for the mount, but what about the motor focuser? Is there a trick to let other software control the focuser while conected to CPWI? Example, I can't get Sharpcap to connect with the focuser while running CPWI

 

Thanks

Tobias



#6 RazvanUnderStars

RazvanUnderStars

    Viking 1

  • -----
  • Posts: 647
  • Joined: 15 Jul 2014
  • Loc: Toronto, Canada

Posted 18 July 2019 - 10:00 PM

Yeah, that doesn't work because CPWI does not yet expose the focuser as an ASCOM device to other apps (such as SharpCap). This feature has been requested by many users and I hope it will be added in a future version of CPWI.

 

In the meantime, you can still control the focuser from SharpCap if you connect the computer directly to the focuser with the USB cable and use the Celestron USB driver. It is an extra cable, granted, but until we get the feature in CPWI, it's the closest you can get. 

 

CPWI ASCOM for the mount, but what about the motor focuser? Is there a trick to let other software control the focuser while conected to CPWI? Example, I can't get Sharpcap to connect with the focuser while running CPWI

 

Thanks

Tobias



#7 Noah4x4

Noah4x4

    Vanguard

  • *****
  • Posts: 2468
  • Joined: 07 Apr 2016
  • Loc: Colchester UK

Posted 18 July 2019 - 11:53 PM

Suggestion; join TeamCelestron where there is a specialist Forum (under "Software") for CPWI.

 

This Forum documents the development progress of CPWI and embraces dozens of issues encountered along the way with Third Party Software  (like the integration with PhD, Micrococuser, ASCOM) and documents the solutions.

 

CPWI has long been work in progress, was only recently released into the public domain, and I suspect few members of Cloudy Nights will (as yet), have the depth of experience already accumulated in TeamCelestron. Hence, solutions might (initially) be harder to find in CN.  Maybe we ought to have a dedicated CPWI thread under the CN Computer Software Forum as under this Nexstar Forum I fear solutions might fast sink without trace until momentum is gained. Download CPWI and your anti-virus software is likely to warn you "too few users" as the community of early adopters remains small.



#8 RazvanUnderStars

RazvanUnderStars

    Viking 1

  • -----
  • Posts: 647
  • Joined: 15 Jul 2014
  • Loc: Toronto, Canada

Posted 19 July 2019 - 06:45 AM

Agree with Noah. You'll find a thread on precisely this question there and if you plan to use CPWI, you'll be able to interact directly with its developers and test beta releases (the 2.2 beta is available for testing, for instance, with a fix for the high CPU usage).



#9 Rac19

Rac19

    Apollo

  • *****
  • Posts: 1422
  • Joined: 05 Aug 2016

Posted 22 July 2019 - 07:05 AM

Agree with Noah. You'll find a thread on precisely this question there and if you plan to use CPWI, you'll be able to interact directly with its developers and test beta releases (the 2.2 beta is available for testing, for instance, with a fix for the high CPU usage).

Having tested beta version 2.2.2, I can say the I have seen CPWI CPU usage fall from 30% to 5%.


  • Stefan042 likes this


CNers have asked about a donation box for Cloudy Nights over the years, so here you go. Donation is not required by any means, so please enjoy your stay.


Recent Topics






Cloudy Nights LLC
Cloudy Nights Sponsor: Astronomics