1. Ap-Gto | Main
  2. Topics

1100AE -- Amber led?

Arvind
 

An hour of the bright 'Flaming Stars' and the 'Tadpole' nebula from the backyard. Acquired using FSQ106, 2400MC Pro, Optolong L Ultimate. https://www.astrobin.com/full/br6ba6/0/ No processing other than stacking them up, to see star quality and tracking & guiding performance.

This was the real first-light test for the 1100-AEL where everything was balanced. 2 nights ago, I tried the setup without balancing anything, and last night I tried again after balancing the scope.

I encountered a slight hiccup upon startup: the CP4 had the Amber light on irrespective of which one was powered up first: ASIAIR vs the mount. The N, S, and E slew buttons would work, but the W wouldn't do anything. Doing a GoTo to Jupiter sent the scope in the opposite direction.

The switch from Red LED to Amber LED happened immediately after connecting with the ASIAIR; I'd like to point out that this was not a problem the previous times and with previous mounts. I also don't directly control time & location -- they're both automatically sent from ASIAIR to the CP4 upon initialization routine on every startup.

Googling for info and reading through the manual for CP4 on this topic of Amber LED, I tried the usual suggestions on checking for power, balance, etc. None of that helped in my case. Finally, I read a post from Roland a few years ago that this can happen if the mount is lost. Unclear how that happened, but I was eventually able to recover: I powered up CP4, waited a minute, started ASIAIR, then did a "goto" to a known bright star (Capella in this case), and as the slew was happening in the wrong direction I killed the goto and used the keypad controls on ASIAIR to point the OTA to roughly where Capella was. Then took a 2-sec exposure and did a Platesolve -> Align & GoTo to center it on the right target.

One other thing that I also did (but didn't do it independently with the above, so I could use clarification on which one was probably the right fix) was to loosen the clutches a bit.

In any case, the night turned out to be a successful test but I still need to figure out exactly why the Amber light came on. Curious if folks have encountered the Ambed LED problem above (in any program) and what the usual suspects you usually check for, beyond power and balance.

Just for kicks, here's a screencap of the tracking after just regular alignment.

image.png

Thanks, and best regards,
Arvind


Dean Jacobsen
 

I found this info from a couple of months ago:

https://ap-gto.groups.io/g/main/message/88735
--
Dean Jacobsen
Astrobin Image Gallery - https://www.astrobin.com/users/deanjacobsen/

Mike Hanson
 

Arvind,

Your statement:
"The N, S, and E slew buttons would work, but the W wouldn't do anything."
Combined with the Amber LED, this indicates the mount is in a limit, specifically the west limit.  It is lost and needs a sync.

You'll need to check longitude, latitude, time zone, time, and date.  If these are correct, a fresh sync at the correct location will fix it.

Regards,
Mike Hanson

Arvind
 



On Mon, Nov 14, 2022 at 2:08 PM Dean Jacobsen <deanjacobsen@...> wrote:
I found this info from a couple of months ago:

https://ap-gto.groups.io/g/main/message/88735

Thanks Dean.

 

Arvind
 



On Mon, Nov 14, 2022 at 2:55 PM Mike Hanson <mikeh@...> wrote:
Arvind,

Your statement:
"The N, S, and E slew buttons would work, but the W wouldn't do anything."
Combined with the Amber LED, this indicates the mount is in a limit, specifically the west limit.  It is lost and needs a sync.

You'll need to check longitude, latitude, time zone, time, and date.  If these are correct, a fresh sync at the correct location will fix it.



Thanks, Mike!

Good piece of information from you. Thanks for that clarification!

Yes, the lat/lon & time are automatically picked up from the phone so they are as accurate as possible. I am thinking the init related info from ASIAIR was perhaps sent too soon before the mount was ready so something for me to do trial and error and triage it on avoiding this altogether. Atleast I know I can bring it back reliably by doing this sync.

Thanks and best regards,
Arvind 

Bill Long
 

The INDI driver used by the ASI product should have initialization parameters. The most important of which would be where you are unparking from:

APV2bMain

If t he Air set to unpark from the Last Parked, or something else?

From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Arvind <base16@...>
Sent: Monday, November 14, 2022 1:51 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: [ap-gto] 1100AE -- Amber led?
 
An hour of the bright 'Flaming Stars' and the 'Tadpole' nebula from the backyard. Acquired using FSQ106, 2400MC Pro, Optolong L Ultimate. https://www.astrobin.com/full/br6ba6/0/ No processing other than stacking them up, to see star quality and tracking & guiding performance.

This was the real first-light test for the 1100-AEL where everything was balanced. 2 nights ago, I tried the setup without balancing anything, and last night I tried again after balancing the scope.

I encountered a slight hiccup upon startup: the CP4 had the Amber light on irrespective of which one was powered up first: ASIAIR vs the mount. The N, S, and E slew buttons would work, but the W wouldn't do anything. Doing a GoTo to Jupiter sent the scope in the opposite direction.

The switch from Red LED to Amber LED happened immediately after connecting with the ASIAIR; I'd like to point out that this was not a problem the previous times and with previous mounts. I also don't directly control time & location -- they're both automatically sent from ASIAIR to the CP4 upon initialization routine on every startup.

Googling for info and reading through the manual for CP4 on this topic of Amber LED, I tried the usual suggestions on checking for power, balance, etc. None of that helped in my case. Finally, I read a post from Roland a few years ago that this can happen if the mount is lost. Unclear how that happened, but I was eventually able to recover: I powered up CP4, waited a minute, started ASIAIR, then did a "goto" to a known bright star (Capella in this case), and as the slew was happening in the wrong direction I killed the goto and used the keypad controls on ASIAIR to point the OTA to roughly where Capella was. Then took a 2-sec exposure and did a Platesolve -> Align & GoTo to center it on the right target.

One other thing that I also did (but didn't do it independently with the above, so I could use clarification on which one was probably the right fix) was to loosen the clutches a bit.

In any case, the night turned out to be a successful test but I still need to figure out exactly why the Amber light came on. Curious if folks have encountered the Ambed LED problem above (in any program) and what the usual suspects you usually check for, beyond power and balance.

Just for kicks, here's a screencap of the tracking after just regular alignment.

image.png

Thanks, and best regards,
Arvind


Howard Hedlund
 

I agree with Mike H.  You are probably in a west limit.  Solving this is simple.  You need a full initialization and a full sync on an AP pre-defined park position.  Contact me off-group and I can help a little further.  I'm not sure how the indi driver initializes, but we can quickly work around it if it's not providing the necessary inputs.  To assure us of success, please download and install Java, and then this little app.  
USB/Serial Utilities (VSU-09) USB/Serial Utilities is a simple program for performing maintenance actions on your GTOCP5 and GTOCP5 and limited function for the GTOCP3.  It uses a USB or serial connection to your CP3/4/5 and allows configuration of the Ethernet and Wi-Fi interfaces (CP4/5 only), firmware updates (CP4/5 only), manual command entry, and NVM archiving and restore. Works for any computer - Windows, Mac or Linux running Java.

Andrew Burwell
 

My guess is that these functions are absent from the UI in the ASIAir. I know for my 10Micron mount they only provide connectivity options like serial or network and purposefully omit more advanced features from the interface. While they are functions of the driver itself, ZWO tends to keep things simple. But if you complain to ZWO they might add them, especially if it's a requirement to get things working properly.

-Andrew

Arvind
 



On Tue, Nov 15, 2022 at 8:45 AM Andrew Burwell via groups.io <andrew_burwell=me.com@groups.io> wrote:
My guess is that these functions are absent from the UI in the ASIAir. I know for my 10Micron mount they only provide connectivity options like serial or network and purposefully omit more advanced features from the interface. While they are functions of the driver itself, ZWO tends to keep things simple. But if you complain to ZWO they might add them, especially if it's a requirement to get things working properly.

Thanks for that input, Bill.

Andrew, agreed, and you're right! The UI element for selecting park positions for Parking & Unparking is currently missing in the ASIAIR app.

Like you, I've used the ASIAIR with the 10u as well -- but my experience with 10u has been mostly unguided: I use the laptop with MW4 on it to build a ~50pt model that takes care of residual Polar Alignment Error (PAE), and overall helps with tracking. After building that model, I switch to ASIAIR for imaging through the night so I can bring the laptop back inside. For my initial nights with the 10u when I was still guiding, I was using the keypad to perform a 3-star manual alignment after which I'd switch to ASIAIR. 

Basically, the mount was pretty much fully initialized & aligned/modeled before even powering up the ASIAIR - all I needed to do, then, was just issue GoTo commands and image.

With A-P, I am not required to build a model so I am able to avoid the usage of a laptop/computer for portable use. As you've rightly called out, this now means that ASIAIR should ensure the mount is being initialized properly since it's the only computer now. As simple as ensuring "unpark" is sent from last-parked, sending time & loc. I've so far worked around any hiccups by manually moving the OTA around and sync'ing on a star. An alternative is to use a keypad to complete initialization (basically power up and unpark it) but it also means I'd now need to ensure the keypad has the correct time. Something I'm hoping to avoid to remove a source of user error.

Based on what I learn from the debugging exchange with Howard offline hopefully sometime this week, I'll surface any gaps to ZWO as well. :fingers crossed:

 

Brian Valente
 

Arvind (and I apologize if this may be too far afield) but based on your 10u experience, you could get an AP keypad and replicate your prior workflow?


On Tue, Nov 15, 2022 at 12:22 PM Arvind <base16@...> wrote:


On Tue, Nov 15, 2022 at 8:45 AM Andrew Burwell via groups.io <andrew_burwell=me.com@groups.io> wrote:
My guess is that these functions are absent from the UI in the ASIAir. I know for my 10Micron mount they only provide connectivity options like serial or network and purposefully omit more advanced features from the interface. While they are functions of the driver itself, ZWO tends to keep things simple. But if you complain to ZWO they might add them, especially if it's a requirement to get things working properly.

Thanks for that input, Bill.

Andrew, agreed, and you're right! The UI element for selecting park positions for Parking & Unparking is currently missing in the ASIAIR app.

Like you, I've used the ASIAIR with the 10u as well -- but my experience with 10u has been mostly unguided: I use the laptop with MW4 on it to build a ~50pt model that takes care of residual Polar Alignment Error (PAE), and overall helps with tracking. After building that model, I switch to ASIAIR for imaging through the night so I can bring the laptop back inside. For my initial nights with the 10u when I was still guiding, I was using the keypad to perform a 3-star manual alignment after which I'd switch to ASIAIR. 

Basically, the mount was pretty much fully initialized & aligned/modeled before even powering up the ASIAIR - all I needed to do, then, was just issue GoTo commands and image.

With A-P, I am not required to build a model so I am able to avoid the usage of a laptop/computer for portable use. As you've rightly called out, this now means that ASIAIR should ensure the mount is being initialized properly since it's the only computer now. As simple as ensuring "unpark" is sent from last-parked, sending time & loc. I've so far worked around any hiccups by manually moving the OTA around and sync'ing on a star. An alternative is to use a keypad to complete initialization (basically power up and unpark it) but it also means I'd now need to ensure the keypad has the correct time. Something I'm hoping to avoid to remove a source of user error.

Based on what I learn from the debugging exchange with Howard offline hopefully sometime this week, I'll surface any gaps to ZWO as well. :fingers crossed:

 



--

Arvind
 



On Tue, Nov 15, 2022 at 12:26 PM Brian Valente <bvalente@...> wrote:
Arvind (and I apologize if this may be too far afield) but based on your 10u experience, you could get an AP keypad and replicate your prior workflow?

Brian, valid response and not a stretch at all. In fact, like I mentioned in the previous response, this requires me to ensure that the location and time are manually entered and correct on the keypad -- and that the time and location are matching what's going to come later from ASIAIR for imaging/meridian flip planning purposes. For a portable setup (not just backyard), this means on every setup I need to input the lat/lon manually -- TZ changes are less frequent. Note that with 10u hand-controller, I am not as sensitive: I do the 3- star alignment, and then later sync time & lat/lon from ASIAIR overriding whatever time & location the keypad sent (and that's ok), but with A-P initialization is (from what I gather) a 1-time mount startup thing.

This is what I meant by "remove a source of user error" in my previous email.

In case it's anywhere close to being not clear -- I love everything about the 1100 and am only trying to figure out a workflow that is as close to hands-off as possible short of carrying it to the field and polar-aligning it. If it turns out the "sync" is unavoidable, then it is what it is :-)




 

Bill Long
 

Interesting. Definitely something worth asking them about. I'd certainly want control of the initialize from position. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Andrew Burwell via groups.io <andrew_burwell@...>
Sent: Tuesday, November 15, 2022 8:45 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] 1100AE -- Amber led?
 
My guess is that these functions are absent from the UI in the ASIAir. I know for my 10Micron mount they only provide connectivity options like serial or network and purposefully omit more advanced features from the interface. While they are functions of the driver itself, ZWO tends to keep things simple. But if you complain to ZWO they might add them, especially if it's a requirement to get things working properly.

-Andrew

Arvind
 

I had a chance to test this earlier this week in the driveway over a few nights.

Upon powering up and connecting, the lat/long and time were synced correctly every time. Still, the Mount Info (basically what's reported from CP4 is shown on the ASIAIR) displayed some unusual RA/DEC values for what was supposed to be its Park3 position where I had parked the mount the previous night.

image.png
(Pic 1: Mount reads unusual RA/DEC upon startup. Expected value: DEC close to or at 90deg and a reasonable RA)


image.png
(Pic 2: The mount after being asked to go its Park position - supposed to be its Park 3)

I slewed E, W, N, and S a bit (it turns out nothing was locked/in-limit this time) to move it out of the "Park 3" area and then issued a "Home" command that should ideally send the OTA to the Park 3 position. That command instead sent the mount upside down and pointing West (See Picture 2).

On that night I was able to get it out of the lost position using my usual tricks: power down CP4, loosen clutches, re-orient the OTA using my hands to have the scope in Park 3 correctly, power up CP4 again, then a goto+sync.

On night 2, everything worked without a hiccup, even without the Park/Unpark button.

On another night, I was out of luck and no particular sequence could help.

I've sent the above pic to ZWO to see if they do what's needed to fix this. Until this is addressed, I will move off of ASIAIR for my 1100. The main attractiveness of ASIAIR for me, at least with other mounts (even previous CP4), is their good UI and reliable functionality but the reliability has been at a loss at least with the new mount.

Here's to hoping this is not going to happen with NINA & Windows drivers 🤞 as I move to it. 

Makes me wonder, too, though: Is there a setting we can have in the future on CP4, perhaps combined with help from the absolute encoders, to let the mount know where it is pointing? If this requires some kind of hardware upgrade (homing sensor?) would be willing to purchase that as well. 



On Tue, Nov 15, 2022 at 3:07 PM Bill Long <bill@...> wrote:
Interesting. Definitely something worth asking them about. I'd certainly want control of the initialize from position. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Andrew Burwell via groups.io <andrew_burwell=me.com@groups.io>
Sent: Tuesday, November 15, 2022 8:45 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] 1100AE -- Amber led?
 
My guess is that these functions are absent from the UI in the ASIAir. I know for my 10Micron mount they only provide connectivity options like serial or network and purposefully omit more advanced features from the interface. While they are functions of the driver itself, ZWO tends to keep things simple. But if you complain to ZWO they might add them, especially if it's a requirement to get things working properly.

-Andrew

Roland Christen
 

Is this a "funny"?

The first pic shows the scope completely upside down.If you sent that to ASIAir you will have them totally confusicated.

Rolando



-----Original Message-----
From: Arvind <base16@...>
To: main@ap-gto.groups.io
Sent: Sat, Nov 19, 2022 12:29 pm
Subject: Re: [ap-gto] 1100AE -- Amber led?

I had a chance to test this earlier this week in the driveway over a few nights.

Upon powering up and connecting, the lat/long and time were synced correctly every time. Still, the Mount Info (basically what's reported from CP4 is shown on the ASIAIR) displayed some unusual RA/DEC values for what was supposed to be its Park3 position where I had parked the mount the previous night.

image.png
(Pic 1: Mount reads unusual RA/DEC upon startup. Expected value: DEC close to or at 90deg and a reasonable RA)


image.png
(Pic 2: The mount after being asked to go its Park position - supposed to be its Park 3)

I slewed E, W, N, and S a bit (it turns out nothing was locked/in-limit this time) to move it out of the "Park 3" area and then issued a "Home" command that should ideally send the OTA to the Park 3 position. That command instead sent the mount upside down and pointing West (See Picture 2).

On that night I was able to get it out of the lost position using my usual tricks: power down CP4, loosen clutches, re-orient the OTA using my hands to have the scope in Park 3 correctly, power up CP4 again, then a goto+sync.

On night 2, everything worked without a hiccup, even without the Park/Unpark button.

On another night, I was out of luck and no particular sequence could help.

I've sent the above pic to ZWO to see if they do what's needed to fix this. Until this is addressed, I will move off of ASIAIR for my 1100. The main attractiveness of ASIAIR for me, at least with other mounts (even previous CP4), is their good UI and reliable functionality but the reliability has been at a loss at least with the new mount.

Here's to hoping this is not going to happen with NINA & Windows drivers 🤞 as I move to it. 

Makes me wonder, too, though: Is there a setting we can have in the future on CP4, perhaps combined with help from the absolute encoders, to let the mount know where it is pointing? If this requires some kind of hardware upgrade (homing sensor?) would be willing to purchase that as well. 



On Tue, Nov 15, 2022 at 3:07 PM Bill Long <bill@...> wrote:
Interesting. Definitely something worth asking them about. I'd certainly want control of the initialize from position. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Andrew Burwell via groups.io <andrew_burwell=me.com@groups.io>
Sent: Tuesday, November 15, 2022 8:45 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] 1100AE -- Amber led?
 
My guess is that these functions are absent from the UI in the ASIAir. I know for my 10Micron mount they only provide connectivity options like serial or network and purposefully omit more advanced features from the interface. While they are functions of the driver itself, ZWO tends to keep things simple. But if you complain to ZWO they might add them, especially if it's a requirement to get things working properly.

-Andrew

--
Roland Christen
Astro-Physics

Arvind
 

Sorry, no, quotes are not intended to mean funny or mean sarcasm. Just calling out a literal.


On Sat, Nov 19, 2022 at 11:55 AM Roland Christen via groups.io <chris1011=aol.com@groups.io> wrote:
Is this a "funny"?

The first pic shows the scope completely upside down.If you sent that to ASIAir you will have them totally confusicated.

Rolando



-----Original Message-----
From: Arvind <base16@...>
To: main@ap-gto.groups.io
Sent: Sat, Nov 19, 2022 12:29 pm
Subject: Re: [ap-gto] 1100AE -- Amber led?

I had a chance to test this earlier this week in the driveway over a few nights.

Upon powering up and connecting, the lat/long and time were synced correctly every time. Still, the Mount Info (basically what's reported from CP4 is shown on the ASIAIR) displayed some unusual RA/DEC values for what was supposed to be its Park3 position where I had parked the mount the previous night.

image.png
(Pic 1: Mount reads unusual RA/DEC upon startup. Expected value: DEC close to or at 90deg and a reasonable RA)


image.png
(Pic 2: The mount after being asked to go its Park position - supposed to be its Park 3)

I slewed E, W, N, and S a bit (it turns out nothing was locked/in-limit this time) to move it out of the "Park 3" area and then issued a "Home" command that should ideally send the OTA to the Park 3 position. That command instead sent the mount upside down and pointing West (See Picture 2).

On that night I was able to get it out of the lost position using my usual tricks: power down CP4, loosen clutches, re-orient the OTA using my hands to have the scope in Park 3 correctly, power up CP4 again, then a goto+sync.

On night 2, everything worked without a hiccup, even without the Park/Unpark button.

On another night, I was out of luck and no particular sequence could help.

I've sent the above pic to ZWO to see if they do what's needed to fix this. Until this is addressed, I will move off of ASIAIR for my 1100. The main attractiveness of ASIAIR for me, at least with other mounts (even previous CP4), is their good UI and reliable functionality but the reliability has been at a loss at least with the new mount.

Here's to hoping this is not going to happen with NINA & Windows drivers 🤞 as I move to it. 

Makes me wonder, too, though: Is there a setting we can have in the future on CP4, perhaps combined with help from the absolute encoders, to let the mount know where it is pointing? If this requires some kind of hardware upgrade (homing sensor?) would be willing to purchase that as well. 



On Tue, Nov 15, 2022 at 3:07 PM Bill Long <bill@...> wrote:
Interesting. Definitely something worth asking them about. I'd certainly want control of the initialize from position. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Andrew Burwell via groups.io <andrew_burwell=me.com@groups.io>
Sent: Tuesday, November 15, 2022 8:45 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] 1100AE -- Amber led?
 
My guess is that these functions are absent from the UI in the ASIAir. I know for my 10Micron mount they only provide connectivity options like serial or network and purposefully omit more advanced features from the interface. While they are functions of the driver itself, ZWO tends to keep things simple. But if you complain to ZWO they might add them, especially if it's a requirement to get things working properly.

-Andrew

--
Roland Christen
Astro-Physics

Arvind
 

https://developers.google.com/style/quotation-marks, for instance, shows how we use it in technical documentation (design docs, emails, ..) at work, so that style got carried over here. The example on this page for "escape" is not sarcasm but refers to a literal word that the customer would perhaps enter into a text box or a prompt.

In any case, I wanted to bubble up the last line from my previous email: It'd help even if I were using Windows: the park positions would only help for as long as the clutches aren't released and the OTA moved. Can the CP4 be made to use the encoders and figure out where it is? 

Is the above already possible with APCC or with the keypad?



On Sat, Nov 19, 2022 at 12:34 PM Arvind via groups.io <base16=gmail.com@groups.io> wrote:
Sorry, no, quotes are not intended to mean funny or mean sarcasm. Just calling out a literal.

On Sat, Nov 19, 2022 at 11:55 AM Roland Christen via groups.io <chris1011=aol.com@groups.io> wrote:
Is this a "funny"?

The first pic shows the scope completely upside down.If you sent that to ASIAir you will have them totally confusicated.

Rolando



-----Original Message-----
From: Arvind <base16@...>
To: main@ap-gto.groups.io
Sent: Sat, Nov 19, 2022 12:29 pm
Subject: Re: [ap-gto] 1100AE -- Amber led?

I had a chance to test this earlier this week in the driveway over a few nights.

Upon powering up and connecting, the lat/long and time were synced correctly every time. Still, the Mount Info (basically what's reported from CP4 is shown on the ASIAIR) displayed some unusual RA/DEC values for what was supposed to be its Park3 position where I had parked the mount the previous night.

image.png
(Pic 1: Mount reads unusual RA/DEC upon startup. Expected value: DEC close to or at 90deg and a reasonable RA)


image.png
(Pic 2: The mount after being asked to go its Park position - supposed to be its Park 3)

I slewed E, W, N, and S a bit (it turns out nothing was locked/in-limit this time) to move it out of the "Park 3" area and then issued a "Home" command that should ideally send the OTA to the Park 3 position. That command instead sent the mount upside down and pointing West (See Picture 2).

On that night I was able to get it out of the lost position using my usual tricks: power down CP4, loosen clutches, re-orient the OTA using my hands to have the scope in Park 3 correctly, power up CP4 again, then a goto+sync.

On night 2, everything worked without a hiccup, even without the Park/Unpark button.

On another night, I was out of luck and no particular sequence could help.

I've sent the above pic to ZWO to see if they do what's needed to fix this. Until this is addressed, I will move off of ASIAIR for my 1100. The main attractiveness of ASIAIR for me, at least with other mounts (even previous CP4), is their good UI and reliable functionality but the reliability has been at a loss at least with the new mount.

Here's to hoping this is not going to happen with NINA & Windows drivers 🤞 as I move to it. 

Makes me wonder, too, though: Is there a setting we can have in the future on CP4, perhaps combined with help from the absolute encoders, to let the mount know where it is pointing? If this requires some kind of hardware upgrade (homing sensor?) would be willing to purchase that as well. 



On Tue, Nov 15, 2022 at 3:07 PM Bill Long <bill@...> wrote:
Interesting. Definitely something worth asking them about. I'd certainly want control of the initialize from position. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Andrew Burwell via groups.io <andrew_burwell=me.com@groups.io>
Sent: Tuesday, November 15, 2022 8:45 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] 1100AE -- Amber led?
 
My guess is that these functions are absent from the UI in the ASIAir. I know for my 10Micron mount they only provide connectivity options like serial or network and purposefully omit more advanced features from the interface. While they are functions of the driver itself, ZWO tends to keep things simple. But if you complain to ZWO they might add them, especially if it's a requirement to get things working properly.

-Andrew

--
Roland Christen
Astro-Physics

1 - 16 of 16