SkyX Camera Add-on & PI

[jkmorse]

Hey folks,

I know people sometimes have issues with the communication between acquisition software and PI as to interpretation with the FITS format.  Personally, I have run into translation issues between MaximDL and PI for years.  There are work arounds that fix almost all issues, but why go through that if you can avoid it.  In that regard, this past weekend I tried out the SkyX's Camera Add-on for the first time.  It was driven, in part, by wanting to go further with T-Point and my Paramount MX using automatic calibration runs.  I can happily report that the software worked seamlessly and was very easy to use.  It also provided superb guiding.  (I also used a baht mask for focusing for the first time and if you are using manual focusing, like I do with my Takahashi e130D, its something you should really look into). 

Best of all, when I went to import the data into PI, it came over with no issues whatever.  Applied equally well to my calibration subframes and the lights.  Not having to tinker was such a pleasure. 

For what it's worth. 

Best,

Jim

[pfile]

thanks, Jim. that's good to know. i was thinking about using TSX+CAO since i primarily run macosx and it's one of the few soultions that in theory would work with my SBIG+integrated guiding filter wheel.

rob

[jkmorse]

Rob,

Please let me know how it works out if you try it.  I am currently running in Windows but likely will need a second computer up and running if I ever retire and build an observatory and that second machine will most likely be my Mac and I will be using it with an SBIG CCD as well.

Best,

Jim

[cfranks]

Jim,

I've been using TSX (Windows) with all the add-ons since it was introduced and never had a problem handling the images in PI.  Fits and CR2 are the only ones I am familiar with and TSX doesn't (yet?) create Xisf format. 

Charles

[CharlesW]

What would be a real treat is if the kind folks at SB would work out some kind of licensing and software agreement with the kind folks at PI to replace that horrific FITS image viewer in TSX. Or at least add an STF choice to the other bizarre stretching formats they use.

[jkmorse]

Charles²

Agree that is a weak point, but since I move so quickly into PI, its not been a major problem so far, though it can make framing a bit of a pain before acquisition.  STF or a look-alike would be a great add.  And great to know you've never had a translation problem.  Up to now with MaximDL that has been a bane of my existence on at least half of my targets.  But, thankfully, the images I took last weekend with CAO made the move without a hitch. 

Only thing I noticed was that in the initial calibration PI subtracts the 100 count pedestal that CAO must put in, then later in the process steps PI issues a warning that it needs to ignore the pedestal value because it has gone negative.  It is not affecting the images so I have not dug any further but would love to hear if you have worked through that yourself.

Best,

Jim

[CharlesW]

I don't do any processing outside of PI. I just pull the images straight from the Camera Auto Save folder in TSX or CCDAP. I've never seen the message you reference above so no help there, I'm afraid.

[chris.bailey]

Jim

I have been using TSX/CAO since launch with various CCD's and never had an issue with the .FITS files moved over into PI. Once you get a decent Point model running you will have repeatable all sky pointing to within a few arc seconds so checking framing becomes less of an issue. Used with Closed Loop Slew you can also go exactly to a previous image and continue imagine night to night. I have never seen the message on Pedestal

Slightly off topic but adding in an electronic focuser is a game changer and @Focus in TSX works very well with temperature compensation and filter offsets.

Chris