Date   

Re: APPM with ASI6200 and TSX Imagelink - bogus image data

Bill Long
 


For the first, check those boxes that say to exclude points past a certain error amount. I set those to 10 but 20 is usually fine. The key thing is that you have outliers if you look at the plot and that's the easiest way to take them out.

For the second, looks good. Plenty within the models capability to correct PA error. Check correct for refraction as well.


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of ap@... <ap@...>
Sent: Sunday, August 1, 2021 9:10 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] APPM with ASI6200 and TSX Imagelink - bogus image data
 

@Bill Long wrote:

 

  • Post your model tab data. Curious to see your results.

 

Sure.  This is with an NP101is still s, short and light and shouldn’t have much flex, but this was only 37 points, just to see if I could get it to build.

 

Not sure if you mean this:

 

 

Or this?

 

 


Re: APPM with ASI6200 and TSX Imagelink - bogus image data

ap@CaptivePhotons.com
 

@Bill Long wrote:

 

  • Post your model tab data. Curious to see your results.

 

Sure.  This is with an NP101is still s, short and light and shouldn’t have much flex, but this was only 37 points, just to see if I could get it to build.

 

Not sure if you mean this:

 

 

Or this?

 

 


Re: Mach 2 + 12.5" AGO iDK?

Bill Long
 

Had to take a break but should be back in the swing tonight with this combo. I took Rolands advice and neutral balanced both axis on the Mach 2. Here is a photo of the beast in route to a fun night.

Counterweights are 1x30, 3x18, 2x10, aka all the weights I own. 😂

She's perfectly balanced though. We'll see how the night goes. 

image/jpeg 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Bill Long <bill@...>
Sent: Friday, July 30, 2021 12:14 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Mach 2 + 12.5" AGO iDK?
 
Night 5, still the same story. Excellent performance with a massive load on the Mach 2 mount. I have still done nothing at all in terms of the model, PA, or anything else.

I should probably add in for new people that this rig sits 2 stories in the air, on a wooden deck that is over 15 years old. If that doesn't show the power of this mount, nothing will. This is the ULTIMATE torture test. The mount is at its limits, and its environment is well past its limits. Yet -- with good equipment even you can image on a tightrope. 

😄 




From: Bill Long <bill@...>
Sent: Thursday, July 29, 2021 12:19 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Mach 2 + 12.5" AGO iDK?
 
Yep. Absolutely no problem at all.


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Roland Christen via groups.io <chris1011@...>
Sent: Thursday, July 29, 2021 12:08 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Mach 2 + 12.5" AGO iDK?
 
Great! So, this combination mount and scope is a winner. Good to know.

Thanks,

Rolando



-----Original Message-----
From: Bill Long <bill@...>
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Sent: Wed, Jul 28, 2021 10:57 am
Subject: Re: [ap-gto] Mach 2 + 12.5" AGO iDK?

A total of 4 all night imaging runs with this combo and still not a single sub thrown out. Excellent tracking and guiding performance. I haven't touched PA, PHD2 settings, or the model since night one when I set the mount up outside. It just works. Tonight will be night 5.


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Bill Long <bill@...>
Sent: Monday, July 26, 2021 2:49 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Mach 2 + 12.5" AGO iDK?
 
We had mild wind here about 5-6MPH and so I wanted to show that as well. No impact at all to subs, and the Mach 2 handled it fine. 






From: Bill Long <bill@...>
Sent: Sunday, July 25, 2021 8:47 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Mach 2 + 12.5" AGO iDK?
 
Here are some sample subs:


I took the highest and lowest FWHM from the data set and shared them. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Bill Long <bill@...>
Sent: Sunday, July 25, 2021 10:12 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Mach 2 + 12.5" AGO iDK?
 
Circling back on this as I finally got to test this out. I put my 12.5" AGO iDK, Moonlight Nitecrawler, FLI Proline 16803, CFW 5-7, Sagitta OAG, and Ultrastar guide camera on the Mach 2. Balancing the load was pretty easy to do, and I had just enough weights on hand for the job. This is pretty much at capacity for the mount based on the specifications. Might even be a tad over. 😁

Performance was stellar. I made a 98pt model in APPM, and used 5 second guide exposures. I took 5 hours worth of 20 minute HA subs and not a single one had any trailing at all. Very nice tight round stars in all of the images. Guiding was about 0.2-0.35" range throughout the night. Graph picture below.

I'll be getting some more data over the next few nights. I'll share some subs later this evening when I'm back on the Astro PC.

Conclusion: Mach 2 is a beastly mount that easily handled this challenge and passed with flying colors. Well done AP!

image/png


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Roland Christen via groups.io <chris1011@...>
Sent: Friday, April 23, 2021 5:44 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Mach 2 + 12.5" AGO iDK?
 
Well, I've never tried that scope, but I have loaded my Mach2 to the limit and imaged/guided just fine. Balance is critical and is easy to do.

Weight makes for larger moment, which makes the mount slower to respond to external disturbance, like wind. If your scope is open tube with no shroud, wind will not be a problem.

I will be loading my Mach2 with a 12" F8 carbon fiber Maksutov astrograph in the next couple days. Weight is about the same as your system. I expect that it will handle it fine and will post some guiding results. Will be getting ready for galaxy season.

Rolando



-----Original Message-----
From: Bill Long <bill@...>
To: AP-GTO Groups. io <ap-gto@groups.io>
Sent: Fri, Apr 23, 2021 7:07 pm
Subject: [ap-gto] Mach 2 + 12.5" AGO iDK?

What say ye?


46lbs, but would need to add focuser (8lbs), TCS System (1lb), and camera/accessories (call these 5 lbs). The OTA is about 18" tall (maybe 17.5" but lets call it 18") so this puts me at 18" and 60 lbs.  This puts me right on the yellow on the Mach 2 graph AP has. Length of everything, in focus with camera gear on would be about 45". 

Seems right at the limits, but likely safe. Any ideas on this from AP or others?

-Bill 

--
Roland Christen
Astro-Physics

--
Roland Christen
Astro-Physics


Re: APPM with ASI6200 and TSX Imagelink - bogus image data

Bill Long
 

Post your model tab data. Curious to see your results.


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of ap@... <ap@...>
Sent: Sunday, August 1, 2021 8:43 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] APPM with ASI6200 and TSX Imagelink - bogus image data
 

Ray said:

 

  • It's too bad you couldn't get around to proving APPM's ASCOM interface also works with the ASCOM Camera Simulator, as I know it does. Here's a screenshot as proof:  J

 

I will.  I probably could have done it instead of an APPM model, but I really wanted to see that work.  I’m now imaging, so tomorrow in daylight I can try the ascom simulator.  Though the simulator is not all that interesting, what I really wonder is why the real camera won’t work.  It clearly does with TSX.  I probably am setting something up wrongly, I realize, but struggling to find what is different than using it on TSX.

 

Linwood

 


Re: APPM with ASI6200 and TSX Imagelink - bogus image data

Bill Long
 

ASCOM Camera just throws the same errors he mentioned when used directly. The SIM might work but a real camera doesn't seem to. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <iogroups@...>
Sent: Sunday, August 1, 2021 8:38 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] APPM with ASI6200 and TSX Imagelink - bogus image data
 

I'm glad it's working!

 

It's too bad you couldn't get around to proving APPM's ASCOM interface also works with the ASCOM Camera Simulator, as I know it does. Here's a screenshot as proof:  J

 

-Ray

 

> -----Original Message-----

> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...

> Sent: Sunday, August 1, 2021 8:19 PM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APPM with ASI6200 and TSX Imagelink - bogus image data

>

> As a minor update, I had a bit of time before my target was high enough after I got all the other setup done so...

>

> I set up TSX, Image link and APPM so that APPM used TSX's Camera, which used my ASI6200 binned 2.   It might

> do bin 1 but pointless.

>

> It's running nicely, I was doing only 37 points and it's on 18 and has not missed a single one.

>

> And it's using the same ASI ASCOM camera driver.

>

> So I have a workable system, at least until I sell my MyT.

>

> I still don't know what is wrong the other way, but this works fine, if a bit round-about..

>

> 22 successful and counting....

>

> Linwood

>

>

>

>

>

 


Re: APPM with ASI6200 and TSX Imagelink - bogus image data

ap@CaptivePhotons.com
 

Ray said:

 

  • It's too bad you couldn't get around to proving APPM's ASCOM interface also works with the ASCOM Camera Simulator, as I know it does. Here's a screenshot as proof:  J

 

I will.  I probably could have done it instead of an APPM model, but I really wanted to see that work.  I’m now imaging, so tomorrow in daylight I can try the ascom simulator.  Though the simulator is not all that interesting, what I really wonder is why the real camera won’t work.  It clearly does with TSX.  I probably am setting something up wrongly, I realize, but struggling to find what is different than using it on TSX.

 

Linwood

 


Re: APPM with ASI6200 and TSX Imagelink - bogus image data

Ray Gralak
 

I'm glad it's working!

 

It's too bad you couldn't get around to proving APPM's ASCOM interface also works with the ASCOM Camera Simulator, as I know it does. Here's a screenshot as proof:  J

 

-Ray

 

> -----Original Message-----

> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...

> Sent: Sunday, August 1, 2021 8:19 PM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APPM with ASI6200 and TSX Imagelink - bogus image data

>

> As a minor update, I had a bit of time before my target was high enough after I got all the other setup done so...

>

> I set up TSX, Image link and APPM so that APPM used TSX's Camera, which used my ASI6200 binned 2.   It might

> do bin 1 but pointless.

>

> It's running nicely, I was doing only 37 points and it's on 18 and has not missed a single one.

>

> And it's using the same ASI ASCOM camera driver.

>

> So I have a workable system, at least until I sell my MyT.

>

> I still don't know what is wrong the other way, but this works fine, if a bit round-about..

>

> 22 successful and counting....

>

> Linwood

>

>

>

>

>

 


Re: APPM with ASI6200 and TSX Imagelink - bogus image data

ap@CaptivePhotons.com
 

As a minor update, I had a bit of time before my target was high enough after I got all the other setup done so...

I set up TSX, Image link and APPM so that APPM used TSX's Camera, which used my ASI6200 binned 2. It might do bin 1 but pointless.

It's running nicely, I was doing only 37 points and it's on 18 and has not missed a single one.

And it's using the same ASI ASCOM camera driver.

So I have a workable system, at least until I sell my MyT.

I still don't know what is wrong the other way, but this works fine, if a bit round-about..

22 successful and counting....

Linwood


Re: APPM with ASI6200 and TSX Imagelink - bogus image data

Ray Gralak
 

I hit plate solve. It opened TSX itself, then gave the same error. TSX wasn’t connected to anything though, it was
open for imagelink.
You can easily prevent SkyX from starting by changing the platesolver to PinPoint.

Please try again and set the attached image to the image in the Camera V2 Simulator.

BTW, you're connected directly to the computer, right? (Not using a remote desktop application)

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@CaptivePhotons.com
Sent: Sunday, August 1, 2021 5:35 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APPM with ASI6200 and TSX Imagelink - bogus image data

@Ray Gralak wrote:



* Please close down SkyX *completely* so that it will not interfere. Despite what others have said, not all
ASCOM camera drivers work when there are two applications connected. (As far as I know, SkyX may not have
disconnected!)



* It would not hurt to restart APPM as well to make sure it has freed any possible previous instance of the
ASCOM Camera V2 Simulator.



* Then restart only using APPM. Again, do not start SkyX or any other application that might connect to the
ASCOM Camera V2 Simulator. The purpose of this test is to see if APPM returns only two values (e.g. 0 and
32767) like you mentioned in a previous post.



OK, I closed everything, opened APCC, connected, then APPM.



I went through the settings of the camera (they were all correct), and connected.



I hit plate solve. It opened TSX itself, then gave the same error. TSX wasn’t connected to anything though, it was
open for imagelink.



If you care to try it, attached is the test image, and these were the settings.



I do have a workaround by using TSX’s camera instead.



Note that APPM didn’t return two values in my case, it returned one value – just 32767 as the min and max both.
Very weird. But it is worth noting that things are not the same with the simulator – I was using subframes because I
had to, as well as binning. I can’t actually simulate that with the simulator as it is limited in geometry.



I’m really curious what Bill has happen with an actual camera.



Linwood








Re: Possible CP5 Wi-Fi module failure #WiFi

Eric Weiner
 

***SOLVED***

I did some investigation and testing after reading about how some other folks have had similar Wi-Fi issues with the CP5.  I made several incremental settings changes to my home mesh network which now allows me to initialize the mount using RS232 (or anything else), then connect SkySafari through my iPhone via my home network Wi-Fi connection.  These modified settings also fixed the connectivity issues I was having with the CP5's built in access point.  These new settings have been completely reliable over several iterations of complete power-down power-on testing. 

I believe there were a few things going on beside what some have claimed to be RF interference and/or too much power out at the CP5 antenna.  The solutions I came up with do not require covering the antenna with foil or otherwise making changes to the CP5 Wi-Fi hardware. 

First, there was indeed indication of interference when using different channels for the home Wi-Fi network and the CP5.  Try selecting the same channel for both, such as 2.4GHz channel 1.

Second, reducing transmit power of the home network to 50% (I also tried 25%) significantly improved reliability of connections.

Third, reducing the CTS/RTS Threshold to something lower than max also significantly improved connection stability.  I changed from 2346 to 500.

Speed tests at 2.4GHz and 5GHz after making these settings showed improved download speeds across my entire home mesh network.

The APCC "Find CP4/5" tool still does not locate my CP5 Wi-Fi IP address, but if you have access to your router's device manager the CP5 is listed as "Sychip Router."  You can grab the IP from there if your router resets and changes it.

Hopefully someone else finds this information useful.

Cheers,

Eric


Re: APPM with ASI6200 and TSX Imagelink - bogus image data

ap@CaptivePhotons.com
 

@Ray Gralak wrote:

 

  • Please close down SkyX *completely* so that it will not interfere. Despite what others have said, not all ASCOM camera drivers work when there are two applications connected. (As far as I know, SkyX may not have disconnected!)

 

  • It would not hurt to restart APPM as well to make sure it has freed any possible previous instance of the ASCOM Camera V2 Simulator.

 

  • Then restart only using APPM. Again, do not start SkyX or any other application that might connect to the ASCOM Camera V2 Simulator. The purpose of this test is to see if APPM returns only two values (e.g. 0 and 32767) like you mentioned in a previous post.

 

OK, I closed everything, opened APCC, connected, then APPM.

 

I went through the settings of the camera (they were all correct), and connected. 

 

I hit plate solve.  It opened TSX itself, then gave the same error.  TSX wasn’t connected to anything though, it was open for imagelink.

 

If you care to try it, attached is the test image, and these were the settings.

 

I do have a workaround by using TSX’s camera instead.

 

Note that APPM didn’t return two values in my case, it returned one value – just 32767 as the min and max both. Very weird.  But it is worth noting that things are not the same with the simulator – I was using subframes because I had to, as well as binning.  I can’t actually simulate that with the simulator as it is limited in geometry.

 

I’m really curious what Bill has happen with an actual camera.

 

Linwood

 

 


Re: APPM with ASI6200 and TSX Imagelink - bogus image data

Ray Gralak
 

Please close down SkyX *completely* so that it will not interfere. Despite what others have said, not all ASCOM camera drivers work when there are two applications connected. (As far as I know, SkyX may not have disconnected!)

 

It would not hurt to restart APPM as well to make sure it has freed any possible previous instance of the ASCOM Camera V2 Simulator.

 

Then restart only using APPM. Again, do not start SkyX or any other application that might connect to the ASCOM Camera V2 Simulator. The purpose of this test is to see if APPM returns only two values (e.g. 0 and 32767) like you mentioned in a previous post.

 

-Ray

 

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Sunday, August 1, 2021 4:20 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APPM with ASI6200 and TSX Imagelink - bogus image data

 

Thanks Ray, but I remain confused.

 

I did exactly that with TSX, set up the camera simulator after saving a M31 image from last night resampled to a third size to stay under the limit.  It worked fine, I can “take” an image with TSX.  I did an all sky image link against that simulated image and it found it, and had the right image scale (4.2).  No issues.

 

I disconnected the simulated camera from TSX (leaving it running for imagelink), opened APPM and added the simulated camera in the same way, the settings were already there (but I checked).   It then won’t actually expose, saying that 3192, which is the image width, is invalid for “StartExposureNumX” whatever that is (second screen shot below).  I also tried doing a “run” just to see, and got the same result on the first point then stopped it.

 

But do you see anything I am doing wrong?  How can TSX work, but APPM not, if it’s all just the ascom driver?   I turned on ascom logging and did it in both APPM and TSX and the separate logs are attached, if it gives a clue.

 

I guess the simple thing is to do it all through TSX until I can do it through NINA.  Then I can use native drivers.

 

Mostly was curious if any other users actually had made the ASI6200MM work.  I’m sure struggling now that I’ve entered the 32 bit world.  😊

 

Linwood

 

PS. I just saw Bill’s note, he does it through the TSX camera also.

 

 

 


Re: APPM with ASI6200 and TSX Imagelink - bogus image data

Bill Long
 

I'll try ASCOM Camera out later this evening as I'll be touching up my PA and running a new model on my Mach 2 / AGO 12.5 combo after pulling the cover off and waking it up from it's slumber during the last 36 hours of cloud cover. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of ap@... <ap@...>
Sent: Sunday, August 1, 2021 4:19 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] APPM with ASI6200 and TSX Imagelink - bogus image data
 

Thanks Ray, but I remain confused.

 

I did exactly that with TSX, set up the camera simulator after saving a M31 image from last night resampled to a third size to stay under the limit.  It worked fine, I can “take” an image with TSX.  I did an all sky image link against that simulated image and it found it, and had the right image scale (4.2).  No issues.

 

I disconnected the simulated camera from TSX (leaving it running for imagelink), opened APPM and added the simulated camera in the same way, the settings were already there (but I checked).   It then won’t actually expose, saying that 3192, which is the image width, is invalid for “StartExposureNumX” whatever that is (second screen shot below).  I also tried doing a “run” just to see, and got the same result on the first point then stopped it.

 

But do you see anything I am doing wrong?  How can TSX work, but APPM not, if it’s all just the ascom driver?   I turned on ascom logging and did it in both APPM and TSX and the separate logs are attached, if it gives a clue.

 

I guess the simple thing is to do it all through TSX until I can do it through NINA.  Then I can use native drivers.

 

Mostly was curious if any other users actually had made the ASI6200MM work.  I’m sure struggling now that I’ve entered the 32 bit world.  😊

 

Linwood

 

PS. I just saw Bill’s note, he does it through the TSX camera also.

 

 

 


Re: APPM with ASI6200 and TSX Imagelink - bogus image data

ap@CaptivePhotons.com
 

Thanks Ray, but I remain confused.

 

I did exactly that with TSX, set up the camera simulator after saving a M31 image from last night resampled to a third size to stay under the limit.  It worked fine, I can “take” an image with TSX.  I did an all sky image link against that simulated image and it found it, and had the right image scale (4.2).  No issues.

 

I disconnected the simulated camera from TSX (leaving it running for imagelink), opened APPM and added the simulated camera in the same way, the settings were already there (but I checked).   It then won’t actually expose, saying that 3192, which is the image width, is invalid for “StartExposureNumX” whatever that is (second screen shot below).  I also tried doing a “run” just to see, and got the same result on the first point then stopped it.

 

But do you see anything I am doing wrong?  How can TSX work, but APPM not, if it’s all just the ascom driver?   I turned on ascom logging and did it in both APPM and TSX and the separate logs are attached, if it gives a clue.

 

I guess the simple thing is to do it all through TSX until I can do it through NINA.  Then I can use native drivers.

 

Mostly was curious if any other users actually had made the ASI6200MM work.  I’m sure struggling now that I’ve entered the 32 bit world.  😊

 

Linwood

 

PS. I just saw Bill’s note, he does it through the TSX camera also.

 

 

 


Re: APPM with ASI6200 and TSX Imagelink - bogus image data

Bill Long
 

I use my cameras via TSX to do APPM models since I use TSX for image link solving for APPM anyhow. I've never used the ASCOM Camera option.


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of ap@... <ap@...>
Sent: Sunday, August 1, 2021 1:59 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: [ap-gto] APPM with ASI6200 and TSX Imagelink - bogus image data
 
I'm confused.  I have an ASI6200MM.  I have the latest ASCOM drivers installed.  I realize APPM is 32 bit and so struggles, so I have it set to bin 2, subframe 1/2x1/2 center.  If I don't use a subframe and bin 3 (the max it allows) I get an Expose Failed.  With bin 2 and 1/2x1/2 it exposes, but... 

The resulting exposure has DN's of 32767.  Every pixel is 32767, min, max, etc.   So it's clearly bogus.  Is there any magic I may be missing?  See ASCOM settings below (there's no native driver I think).  Note I've tried USB 40 and 100 (100 works fine with other programs). 

I'm finding the image in c:\users\ferguson\documents\Astro-Physics\APPM, and I've viewed it in Pixinsight to double check.  I've done it both on "run" and "platesolve" now. 

I connected the same way to the camera feature in TSX with the same driver and got an image. 

What am I missing? 

Should I be using the TSX Camera from APPM?   I think I can do that (and yes, just tried, I get an image).  Is that the proper way?

But should it work as set up below?   I was trying to avoid TSX's camera just because one less thing but lacking another solution will try that next time.

Linwood

PS. Log segment below it, no error from the exposure. 



0000006 2021-08-01 16:41:04.066:       Info,  Connect Driver, AP V2 Driver Version: 5.30.0010, Result: OK
0000007 2021-08-01 16:41:06.001:       Info,  Connect Camera, ASCOM Camera ASCOM.ASICamera2.Camera: 6.5.19.1, Result: OK
0000008 2021-08-01 16:42:27.498:       Info,   State Machine, Entering State=StartPlateSolveNow
0000009 2021-08-01 16:42:27.582:       Info,   State Machine, StartPlateSolveNow via SkyXPro ImageLink: Starting Exposure=2
0000010 2021-08-01 16:42:27.601:       Info,  StartTakeImage, ASCOM Camera: Binning=2, Subframe Type: 1, Duration=2, IsDarkFrame=False
0000011 2021-08-01 16:42:28.319:       Info,   State Machine, Entering State=WaitPlateSolveNow
0000012 2021-08-01 16:42:31.099:       Info,   State Machine, WaitPlateSolveNow: Exposure Done. Saving to: C:\Users\ferguson\Documents\Astro-Physics\APPM\SolveNow-2021-08-01-164231.fit



Re: APPM with ASI6200 and TSX Imagelink - bogus image data

Ray Gralak
 

Hi Linwood,

 

APPM just displays whatever is provided to it via the ASI ASCOM driver.

 

Have you tried using APPM with the ASCOM Camera V2 Simulator? You can supply a jpeg image to be displayed. Then in APPM issue a Plate Solve to test the output. The goal of this is just to see if APPM can properly display an image from the baseline Camera V2 Simulator. If it can, the problem you are seeing is likely with the camera settings, the ASI camera driver, or some hardware issue.

 

Here’s a screenshot with the “flow” to setup to test APPM:

 

 

-Ray

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Sunday, August 1, 2021 2:00 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] APPM with ASI6200 and TSX Imagelink - bogus image data

 

I'm confused.  I have an ASI6200MM.  I have the latest ASCOM drivers installed.  I realize APPM is 32 bit and so struggles, so I have it set to bin 2, subframe 1/2x1/2 center.  If I don't use a subframe and bin 3 (the max it allows) I get an Expose Failed.  With bin 2 and 1/2x1/2 it exposes, but... 

The resulting exposure has DN's of 32767.  Every pixel is 32767, min, max, etc.   So it's clearly bogus.  Is there any magic I may be missing?  See ASCOM settings below (there's no native driver I think).  Note I've tried USB 40 and 100 (100 works fine with other programs). 

I'm finding the image in c:\users\ferguson\documents\Astro-Physics\APPM, and I've viewed it in Pixinsight to double check.  I've done it both on "run" and "platesolve" now. 

I connected the same way to the camera feature in TSX with the same driver and got an image. 

What am I missing? 

Should I be using the TSX Camera from APPM?   I think I can do that (and yes, just tried, I get an image).  Is that the proper way?

But should it work as set up below?   I was trying to avoid TSX's camera just because one less thing but lacking another solution will try that next time.

Linwood

PS. Log segment below it, no error from the exposure. 

0000006 2021-08-01 16:41:04.066:       Info,  Connect Driver, AP V2 Driver Version: 5.30.0010, Result: OK

0000007 2021-08-01 16:41:06.001:       Info,  Connect Camera, ASCOM Camera ASCOM.ASICamera2.Camera: 6.5.19.1, Result: OK

0000008 2021-08-01 16:42:27.498:       Info,   State Machine, Entering State=StartPlateSolveNow

0000009 2021-08-01 16:42:27.582:       Info,   State Machine, StartPlateSolveNow via SkyXPro ImageLink: Starting Exposure=2

0000010 2021-08-01 16:42:27.601:       Info,  StartTakeImage, ASCOM Camera: Binning=2, Subframe Type: 1, Duration=2, IsDarkFrame=False

0000011 2021-08-01 16:42:28.319:       Info,   State Machine, Entering State=WaitPlateSolveNow

0000012 2021-08-01 16:42:31.099:       Info,   State Machine, WaitPlateSolveNow: Exposure Done. Saving to: C:\Users\ferguson\Documents\Astro-Physics\APPM\SolveNow-2021-08-01-164231.fit

 


Re: Possible CP5 Wi-Fi module failure #WiFi

Eric Weiner
 

One last observation,

More often than not after a power cycle (power off, wait 2 min, power on, wait 2 min) there would be no networks available on the Wi-Fi Network Connection Selection settings page. Smashing "Re-scan for available networks" would result in zero returns.  Not even the access point.


Re: Possible CP5 Wi-Fi module failure #WiFi

Eric Weiner
 

As a follow up:

After tinkering around I was able to connect to my home network, but I didn't do anything different.  Then I noticed this odd behavior:

1. The Wi-Fi connection would only show up in APCC-FIND if I unplugged the LAN cable and refreshed FIND

2. If I initialized using "serial" in APCC I could not connect to the CP5 Wi-Fi using SkySafari Pro

3. I could connect to the CP5 Wi-Fi but only if I initialized using SkySafari Pro (iPhone) or the LAN connection, but the SkySafari connection was very sketchy. Any slew commands resulted in a runaway scope.  I had to do an emergency stop using APCC.  SkySafari locked up in the button pushed position and even doing a hard close didn't stop the slew.  Timeout was set for 3 seconds in SkySafari.

4. Even when the settings page showed I was connected to my home network, I could still not connect or initialize the mount via Wi-Fi using APCC (2000ms timeout set).  The Wi-Fi address would not show up using APCC-FIND, and APCC would not connect when I manually entered the IP shown on the settings page as connected to my home network.

Subsequent power cycles resulted in the Wi-Fi module not connecting to my home network as described in the original post. When I would try to manually connect through the setting page I would often get an error which says, " 169.254.0.102 says Join Failed, General Error."

This Wi-Fi module is definitely flakey.  It seems like it isn't initializing upon power-up most of the time, and when it does initialize it still doesn't operate correctly.  


APPM with ASI6200 and TSX Imagelink - bogus image data

ap@CaptivePhotons.com
 

I'm confused.  I have an ASI6200MM.  I have the latest ASCOM drivers installed.  I realize APPM is 32 bit and so struggles, so I have it set to bin 2, subframe 1/2x1/2 center.  If I don't use a subframe and bin 3 (the max it allows) I get an Expose Failed.  With bin 2 and 1/2x1/2 it exposes, but... 

The resulting exposure has DN's of 32767.  Every pixel is 32767, min, max, etc.   So it's clearly bogus.  Is there any magic I may be missing?  See ASCOM settings below (there's no native driver I think).  Note I've tried USB 40 and 100 (100 works fine with other programs). 

I'm finding the image in c:\users\ferguson\documents\Astro-Physics\APPM, and I've viewed it in Pixinsight to double check.  I've done it both on "run" and "platesolve" now. 

I connected the same way to the camera feature in TSX with the same driver and got an image. 

What am I missing? 

Should I be using the TSX Camera from APPM?   I think I can do that (and yes, just tried, I get an image).  Is that the proper way?

But should it work as set up below?   I was trying to avoid TSX's camera just because one less thing but lacking another solution will try that next time.

Linwood

PS. Log segment below it, no error from the exposure. 



0000006 2021-08-01 16:41:04.066:       Info,  Connect Driver, AP V2 Driver Version: 5.30.0010, Result: OK
0000007 2021-08-01 16:41:06.001:       Info,  Connect Camera, ASCOM Camera ASCOM.ASICamera2.Camera: 6.5.19.1, Result: OK
0000008 2021-08-01 16:42:27.498:       Info,   State Machine, Entering State=StartPlateSolveNow
0000009 2021-08-01 16:42:27.582:       Info,   State Machine, StartPlateSolveNow via SkyXPro ImageLink: Starting Exposure=2
0000010 2021-08-01 16:42:27.601:       Info,  StartTakeImage, ASCOM Camera: Binning=2, Subframe Type: 1, Duration=2, IsDarkFrame=False
0000011 2021-08-01 16:42:28.319:       Info,   State Machine, Entering State=WaitPlateSolveNow
0000012 2021-08-01 16:42:31.099:       Info,   State Machine, WaitPlateSolveNow: Exposure Done. Saving to: C:\Users\ferguson\Documents\Astro-Physics\APPM\SolveNow-2021-08-01-164231.fit



Possible CP5 Wi-Fi module failure #WiFi

Eric Weiner
 

I've been using the CP5 Wi-Fi successfully for several months now.  My primary method of connectivity to my PC is serial over USB, but I always connect the CP5 to my home Wi-Fi network so I can simply control it via my iPhone using SkySafari Pro when I want.

Recently I was having issues connecting to my home network from my observing site which is less than 100 feet from the router.  I brought my Mach2 inside today to troubleshoot and was unsuccessful.  The CP5 Wi-Fi will not connect in station mode, or allow a connection as an access point.

With the mount 10 feet from the router it won't connect to my home Wi-Fi network (which is working); no IP or hostname shows up in APCC for Wi-Fi.  I've tired several antenna orientations.
I made a direct LAN connection to check the settings
The CP5 did connect to my home LAN network and populated the IP in APCC (still not Wi-Fi IP shown in APCC)
The CP5 would not connect to my home Wi-Fi network from the setting page (I confirmed the password is correct)
I started up the built in access point, connected, but could not join the access point network; all access point settings started out as OEM including the password
I tried several passwords, several power cycles, turning the Wi-Fi off and on, but even when the access point was created (sometimes it failed to even transmit the host name) I would get "Unable to join the network "GTOCP5_NET_102".

It sure seems like this Wi-Fi modules is toast.  Any ideas from users or A-P?

Thanks,
Eric

3481 - 3500 of 83216