Date   

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


1100GTO, slight free play in RA axis only. Is a backstop adjustment needed?

skester@...
 

I've had my 1100 for a few months and it has performed well.  However I noticed from day 1 a small amount of free movement in the RA axis while the Dec axis has none.  The amount of play in the RA axis is between 1 and 2 mm of movement at the tip of the counterweight shaft.  

Is this amount of play normal/correct, or should I adjust the RA gearbox backstop as described on page 34 fo the owners manual?

Thanks,
Scott


Re: New AP1100, indoor practice, lots of little questions

ap@CaptivePhotons.com
 

@Bill Long:  Should add that it is time for a new CDK14. Gotta test the maximum out! 

 

Yeah, there is a performance limitation involved that is far more difficult to fix:  the human that has to carry it out each night and back in.  😊

 

My C11 is about all I want to deal with.  Tried the small refractor first, but it’s been sidelined without a mount for so long I hear it whining in the closet.

 

Let me know if you hear how I can get a capacity upgrade.  😊

 

Linwodo


Re: 1200 not taking SGP corrections

Ray Gralak
 

Hi Peter,

 

> I entered them in the ASCOM driver. Finally I rechecked that driver and they were there.

 

If you are using APCC with the ASCOM driver, then APCC will initialize the mount. So, the place you should set up the lat/long coordinates is in the Sites dialog in APCC. Here's a screenshot:

 

 

-Ray

 


Re: 1200 not taking SGP corrections

Peter Bresler
 
Edited

Los Osos
 
35° 18' 36.54'' N
 
120° 49' 31.5804'' W

I entered them in the ASCOM driver. Finally I rechecked that driver and they were there.


Re: 1200 not taking SGP corrections

Christopher Erickson
 

Where did you enter your lat/lon numbers?

-Christopher Erickson
Observatory engineer
Waikoloa, HI 96738
www.summitkinetics.com
   

On Sun, Aug 1, 2021, 7:16 AM Peter Bresler via groups.io <PABresler=aol.com@groups.io> wrote:
I did manually enter the lat and longitude, and also powered the mount off several times and restarted APCC. The problem persisted. It mostly affected the DEC axis, but once the RA also did not correct. The cables look good, as usual. No other obvious problems. I will not be able to try again until I return from vacation in 3 weeks. What else do you suggest? I send an email to George.

I made a previous post about PHD not being able to make DEC corrections, but assumed that was a problem with the guide star.


Re: 1200 not taking SGP corrections

Peter Bresler
 

I did manually enter the lat and longitude, and also powered the mount off several times and restarted APCC. The problem persisted. It mostly affected the DEC axis, but once the RA also did not correct. The cables look good, as usual. No other obvious problems. I will not be able to try again until I return from vacation in 3 weeks. What else do you suggest? I send an email to George.

I made a previous post about PHD not being able to make DEC corrections, but assumed that was a problem with the guide star.


Re: New AP1100, indoor practice, lots of little questions

KHursh
 

The 'HOME' button does not exist on a mount without AE. It is on the AE tab of APCC pro.


Re: New AP1100, indoor practice, lots of little questions

Horia
 

Hi Bill,

 

 

>> Home would work even with the mount lost.

 

does this also apply to a mount without absolute encoders?

 

Kind Regards,

Horia

 

 

Von: main@ap-gto.groups.io <main@ap-gto.groups.io> Im Auftrag von Bill Long
Gesendet: Sonntag, 1. August 2021 02:07
An: main@ap-gto.groups.io
Betreff: Re: [ap-gto] New AP1100, indoor practice, lots of little questions

 

Park does not clear the recal/sync. Home does. A lost mount would not return to park 3 correctly via a park command. Home would work even with the mount lost. Once it returned home and cleared the errant recal/sync the mount is no longer lost. Major difference.

 

If you were to recal or sync the mount on a known star the 3D model would display correctly. 

 



Re: New AP1100, indoor practice, lots of little questions

Bill Long
 

Should add that it is time for a new CDK14. Gotta test the maximum out! 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Bill Long <bill@...>
Sent: Sunday, August 1, 2021 4:33 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] New AP1100, indoor practice, lots of little questions
 
Looks like its performing nicely and is only limited by the seeing conditions you have there. A 540mm FL scope is small and light so I doubt the 1100 even knew it was on the mount at all. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of ap@... <ap@...>
Sent: Sunday, August 1, 2021 4:10 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] New AP1100, indoor practice, lots of little questions
 

I’m still not sure I understand the fine points here, but thought I would share this.  It was unexpectedly clear all night (hazy but image-able), so the new mount got its first light (if that can apply to mounts).

 

It started at 0.30” which was the worst all night,  by the morning it was guiding at 0.22” (at 540mm image/guide focal length (OAG)).

 

So the mount understands even if I don’t.  😊

 

Happy round stars.  Happy sleep deprived user.

 

AP, you folks build well!

 

Linwood

 

 

_,_


Re: New AP1100, indoor practice, lots of little questions

Bill Long
 

Looks like its performing nicely and is only limited by the seeing conditions you have there. A 540mm FL scope is small and light so I doubt the 1100 even knew it was on the mount at all. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of ap@... <ap@...>
Sent: Sunday, August 1, 2021 4:10 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] New AP1100, indoor practice, lots of little questions
 

I’m still not sure I understand the fine points here, but thought I would share this.  It was unexpectedly clear all night (hazy but image-able), so the new mount got its first light (if that can apply to mounts).

 

It started at 0.30” which was the worst all night,  by the morning it was guiding at 0.22” (at 540mm image/guide focal length (OAG)).

 

So the mount understands even if I don’t.  😊

 

Happy round stars.  Happy sleep deprived user.

 

AP, you folks build well!

 

Linwood

 

 

_,_


Re: New AP1100, indoor practice, lots of little questions

ap@CaptivePhotons.com
 

I’m still not sure I understand the fine points here, but thought I would share this.  It was unexpectedly clear all night (hazy but image-able), so the new mount got its first light (if that can apply to mounts).

 

It started at 0.30” which was the worst all night,  by the morning it was guiding at 0.22” (at 540mm image/guide focal length (OAG)).

 

So the mount understands even if I don’t.  😊

 

Happy round stars.  Happy sleep deprived user.

 

AP, you folks build well!

 

Linwood

 

 

_,_


Re: 1200 not taking SGP corrections

Ray Gralak
 

Bill is correct. Not only that, both Latitude and Longitude are incorrectly set to 0 at one point:

 

0000050 2021-08-01 00:40:54.250:      Debug,  Command Thread, TX = ':Gt#'

0000051 2021-08-01 00:40:54.250:      Debug,        UDP Send, --> :Gt#   Timeout(msecs)= 100

0000052 2021-08-01 00:40:54.252:      Debug,        UDPReply, <-- +00*00:00#      (1 msecs)

0000053 2021-08-01 00:40:54.252:      Debug,  Command Thread, TX=':Gt#'|RX='+00*00:00#'

0000054 2021-08-01 00:40:54.253:      Debug,  Command Thread, TX = ':Gg#'

0000055 2021-08-01 00:40:54.253:      Debug,        UDP Send, --> :Gg#   Timeout(msecs)= 100

0000056 2021-08-01 00:40:54.255:      Debug,        UDPReply, <-- +00*00:00#      (2 msecs)

0000057 2021-08-01 00:40:54.255:      Debug,  Command Thread, TX=':Gg#'|RX='+00*00:00#'

 

Power off the mount if it is not off already. Then power on the mount and run APCC . Watch APCC to make sure that it initializes the mount with the proper Lat/Long values. If something else initializes the mount first (e.g. the keypad?) you will not see APCC’s popup initialization window, and APCC will not set the mount’s latitude and longitude. You can check thevalues set in the mount on APCC’s Site tab.

 

-Ray

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
Sent: Sunday, August 1, 2021 2:14 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] 1200 not taking SGP corrections

 

Not sure this is causing your problem, but this warning entry is all over the place in the log:

 

 

Is your site information correct? If not, update it and reboot the mount and try again.

 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Peter Bresler via groups.io <PABresler@...>
Sent: Sunday, August 1, 2021 2:01 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: [ap-gto] 1200 not taking SGP corrections

 

Plate solve corrections generated by SGP are not being made by my 1200. The plate solve may work as a blind solve or direct solve by PS2, the error is shown, but on the next try there is no change in the error. I tried a couple of different computers, thinking there might be some problem with the settings.

https://www.dropbox.com/s/v2simav8cflq749/ApccZip-Peter_Bresler-2021-08-01-011435.zip?dl=0

7081 - 7100 of 86804