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

New mount - iOptron Skyhunter

  • Please log in to reply
294 replies to this topic

#101 RogerM

RogerM

    Viking 1

  • *****
  • Posts: 690
  • Joined: 13 Aug 2020
  • Loc: California

Posted 07 August 2022 - 04:54 PM

I'm going over what guide logs that were captured from last nights frustrating experience.  SkySafari and the Commander Lite apps continued to operate (even concurrently with the ASIAir USB link to the mount) within the limits of those apps functionality.  I am currently writing a rather lengthy report that I will be sending copies to both ZWO and to iOptron.  Hopefully the two of them will work together to resolve this big issue with the mount/app functionality.  I just hope my AAP will function as it used to....reliably.  But I'm not confident since I updated the AAP OS to the 803 rev. from 1.9

 

I will share what guide calibration logs that I was able to access, which came with an entirely new set of issues (but I will save that discussion with the ZWO-iOptron folks under separate cover.)  Note that I performed numerous calibration attempts on one target that was > 50º in elevation, west side of pier (but was getting close to meridian).  For the cal runs 7 & 8 I selected a secondary target on the east side of pier and a bit further away from meridian.  Yes, I had thought that maybe the proximity to meridian was causing the mount to stop functioning hence the last two calibration attempts...no joy there.

 

Cal_Runs_1-4.jpg

 

Cal_runs_5-8.jpg



#102 seven6

seven6

    Sputnik

  • -----
  • Posts: 43
  • Joined: 06 Oct 2021
  • Loc: Los Angeles

Posted 07 August 2022 - 05:15 PM

I'm going over what guide logs that were captured from last nights frustrating experience.  SkySafari and the Commander Lite apps continued to operate (even concurrently with the ASIAir USB link to the mount) within the limits of those apps functionality.  I am currently writing a rather lengthy report that I will be sending copies to both ZWO and to iOptron.  Hopefully the two of them will work together to resolve this big issue with the mount/app functionality.  I just hope my AAP will function as it used to....reliably.  But I'm not confident since I updated the AAP OS to the 803 rev. from 1.9

 

I will share what guide calibration logs that I was able to access, which came with an entirely new set of issues (but I will save that discussion with the ZWO-iOptron folks under separate cover.)  Note that I performed numerous calibration attempts on one target that was > 50º in elevation, west side of pier (but was getting close to meridian).  For the cal runs 7 & 8 I selected a secondary target on the east side of pier and a bit further away from meridian.  Yes, I had thought that maybe the proximity to meridian was causing the mount to stop functioning hence the last two calibration attempts...no joy there.

 

It is not just an ASIAir issue. I also tested this running PHD2/INDIGO on my laptop and could not get a guide calibration to succeed. So it seems like there is something wrong with the way the mount is "interpreting" guiding commands. It sounds like we are all hitting up iOptron, so hopefully this will get their attention.



#103 RogerM

RogerM

    Viking 1

  • *****
  • Posts: 690
  • Joined: 13 Aug 2020
  • Loc: California

Posted 07 August 2022 - 05:39 PM

So to summarize if I understand well:

 

- Unguided exposures lead to star trails due to jittery, no linear movement, of the gears.

- Setting up guiding / calibration, doesn't succeed due to the mount "fighting" the guide pulse.

- Firmware update could potentially fix those issues.

- You guys are in contact with iOptron.

@Astro446,  as a matter of clarity and not semantics argument.  These points you just cannot condense into a brief summary without loosing some context.

 

  1. Unguided SkyHunter mount operation yields irregular results.  Let me re-iterate what I personally wrote some posts back...Some of the images collected during an unguided session display fairly good star profiles while others exhibit various amounts of 'trailing'.  While 'star trailing' can be indicative of polar alignment issues that is not the case here.  In this case, star movement is a direct result of the mounts non linear operation as observed in the Right Ascension Axis.  I firmly believe it is not due to the shape of the gear(s), i.e., gear profile, eccentricity, etc. as there would be some form of periodicity (a.k.a. Periodic Error) which is not the case here...and, the irregularities are not due to a lack of torque output by the stacked gear assembly as in my configuration I am only loading the mount with less than four pounds of equipment (the mount is rated up to eleven pounds.)  There is clear evidence that irregular movement of the RA axis exists if you carefully study the image data.  For example, pay attention to the relative brightness of a singular star trace...
  2. We are not privy to what type of signal is being sent to the mount, we can only speculate that it may be a pulse signal. This is not coms via an ST-4 interface but rather a type of RS-232 style serial communications. We know this for certain because of the published information regarding a specific chip being used.  Here I would just state that Guide Calibration fails. period.
  3. Whether this is a firmware, coms or other s/w interaction issue we can't determine specifically (at this moment.)  We only know for certain that something just isn't working between the mount and guiding software.  As of this time we have observed this failure to guide calibrate both via ASIAir and PHD2 but that's the extent of our knowledge/understanding.  Keep in mind that while in the general sense this is a fairly straightforward methodology, there still remains a lot of 'stuff under the hood' in order to have things work in this instance.
  4. Folks have reached out but we do need to be mindful that this could be a simple fix or a more complex issue...I personally do not want to state that I contacted them only to turn around and see a post with something negative like 'we haven't heard anything from them'...it is still the weekend after all. ; )

I do understand why you are summarizing but again, and as when trying to resolve issues with anything, the more concise information/details that can be provided the more apt a resolution to a problem can be found.  Here we are hoping to find resolution by working as diligently as possible with two separate vendors, neither of whom has a mandate to support the other.  Certainly this is a frustrating experience and I have come to appreciate the convenience of the products offered by both of these companies so I am committed to doing what I can to help find a solution.  We all will benefit from any efforts even if it means being a 'guinea pig'.  To me, this experience only enables me to have a more intimate understanding of how my equipment works and that can only help serve me if/when I may have another issue pop up in the future.

 

Cheers!


  • gfstallin likes this

#104 RogerM

RogerM

    Viking 1

  • *****
  • Posts: 690
  • Joined: 13 Aug 2020
  • Loc: California

Posted 07 August 2022 - 05:54 PM

It is not just an ASIAir issue. I also tested this running PHD2/INDIGO on my laptop and could not get a guide calibration to succeed. So it seems like there is something wrong with the way the mount is "interpreting" guiding commands. It sounds like we are all hitting up iOptron, so hopefully this will get their attention.

Yes, I remember your earlier post about the calibration failure via PHD2.  I was just exemplifying my own experience using the AAP.  Your experience helps me in that I was going to try tonight with my PHD2/APT tablet so I thank you for saving me another night...and afternoon as I was about to do what these instructions lay out regarding the ASCOM and VCP drivers.



#105 joshumax

joshumax

    Explorer 1

  • -----
  • Posts: 94
  • Joined: 13 Mar 2013
  • Loc: Seattle

Posted 08 August 2022 - 03:25 AM

Well well well! I figured out why the ASIAIR devices such as the AAP do not guide the mount!

 

I have MITMed the serial protocol between my AAP and the SH -- these are the pulse commands sent to the mount during calibration:

:Mw02000#> 2022/08/08 01:01:11.079041  length=9 from=164 to=172
:Mw02000#> 2022/08/08 01:01:14.083493  length=9 from=173 to=181
:Mw02000#> 2022/08/08 01:01:17.089310  length=9 from=182 to=190
:Mw02000#> 2022/08/08 01:01:20.114616  length=9 from=191 to=199
:Mw02000#> 2022/08/08 01:01:23.027646  length=9 from=200 to=208
:Mw02000#> 2022/08/08 01:01:26.099047  length=9 from=209 to=217
:Mw02000#> 2022/08/08 01:01:29.154534  length=9 from=218 to=226
:Mw02000#> 2022/08/08 01:01:32.105689  length=9 from=227 to=235
:Mw02000#> 2022/08/08 01:01:35.076211  length=9 from=236 to=244
:Mw02000#> 2022/08/08 01:01:38.120907  length=9 from=245 to=253
:Mw02000#> 2022/08/08 01:01:41.085060  length=9 from=254 to=262
:Mw02000#> 2022/08/08 01:01:44.041070  length=9 from=263 to=271
:Mw02000#> 2022/08/08 01:01:47.124545  length=9 from=272 to=280
:Mw02000#> 2022/08/08 01:01:50.079288  length=9 from=281 to=289
:Mw02000#> 2022/08/08 01:01:53.088606  length=9 from=290 to=298
:Mw02000#> 2022/08/08 01:01:56.075555  length=9 from=299 to=307
:Mw02000#> 2022/08/08 01:01:59.122885  length=9 from=308 to=316
:Mw02000#> 2022/08/08 01:02:02.101514  length=9 from=317 to=325
:Mw02000#> 2022/08/08 01:02:05.084235  length=9 from=326 to=334
:Mw02000#> 2022/08/08 01:02:08.082848  length=9 from=335 to=343

According to the iOptron serial command reference, this command is supposed to move an EQ mount "west" for 2000ms (my guide step size in AAP). HOWEVER: in the reference it also states "Note: These commands are deprecated and will be removed in a future version. These commands only available in equatorial mounts." So, it looks like they finally got rid of the Mn/e/s/w commands in the SH firmware. The v3 INDI drivers use the newer ZS/Q/E/C pulse commands. I used ":ZC02000" instead and sure enough I actually saw the guider image move!

 

See here: https://github.com/i...driver.cpp#L515

 

Is ZWO using the standard v3 driver? Did they patch INDI for some reason? Or are they using INDI startMotion routine instead? (That is not the correct way to utilize the driver for guider calibration...)

 

Edit: This does not fix the other issues with the mount such as tracking nonlinearity and sub-1sec pulse commands not registering...


Edited by joshumax, 08 August 2022 - 03:28 AM.

  • gfstallin and fmendes like this

#106 Astro446

Astro446

    Sputnik

  • -----
  • Posts: 41
  • Joined: 28 Apr 2022

Posted 08 August 2022 - 06:06 AM

Well well well! I figured out why the ASIAIR devices such as the AAP do not guide the mount!

 

I have MITMed the serial protocol between my AAP and the SH -- these are the pulse commands sent to the mount during calibration:

:Mw02000#> 2022/08/08 01:01:11.079041  length=9 from=164 to=172
:Mw02000#> 2022/08/08 01:01:14.083493  length=9 from=173 to=181
:Mw02000#> 2022/08/08 01:01:17.089310  length=9 from=182 to=190
:Mw02000#> 2022/08/08 01:01:20.114616  length=9 from=191 to=199
:Mw02000#> 2022/08/08 01:01:23.027646  length=9 from=200 to=208
:Mw02000#> 2022/08/08 01:01:26.099047  length=9 from=209 to=217
:Mw02000#> 2022/08/08 01:01:29.154534  length=9 from=218 to=226
:Mw02000#> 2022/08/08 01:01:32.105689  length=9 from=227 to=235
:Mw02000#> 2022/08/08 01:01:35.076211  length=9 from=236 to=244
:Mw02000#> 2022/08/08 01:01:38.120907  length=9 from=245 to=253
:Mw02000#> 2022/08/08 01:01:41.085060  length=9 from=254 to=262
:Mw02000#> 2022/08/08 01:01:44.041070  length=9 from=263 to=271
:Mw02000#> 2022/08/08 01:01:47.124545  length=9 from=272 to=280
:Mw02000#> 2022/08/08 01:01:50.079288  length=9 from=281 to=289
:Mw02000#> 2022/08/08 01:01:53.088606  length=9 from=290 to=298
:Mw02000#> 2022/08/08 01:01:56.075555  length=9 from=299 to=307
:Mw02000#> 2022/08/08 01:01:59.122885  length=9 from=308 to=316
:Mw02000#> 2022/08/08 01:02:02.101514  length=9 from=317 to=325
:Mw02000#> 2022/08/08 01:02:05.084235  length=9 from=326 to=334
:Mw02000#> 2022/08/08 01:02:08.082848  length=9 from=335 to=343

According to the iOptron serial command reference, this command is supposed to move an EQ mount "west" for 2000ms (my guide step size in AAP). HOWEVER: in the reference it also states "Note: These commands are deprecated and will be removed in a future version. These commands only available in equatorial mounts." So, it looks like they finally got rid of the Mn/e/s/w commands in the SH firmware. The v3 INDI drivers use the newer ZS/Q/E/C pulse commands. I used ":ZC02000" instead and sure enough I actually saw the guider image move!

 

See here: https://github.com/i...driver.cpp#L515

 

Is ZWO using the standard v3 driver? Did they patch INDI for some reason? Or are they using INDI startMotion routine instead? (That is not the correct way to utilize the driver for guider calibration...)

 

Edit: This does not fix the other issues with the mount such as tracking nonlinearity and sub-1sec pulse commands not registering...

Nice finding joshumax :)

 

1) So this issue only exist on AApro not AA+, correct ? If yes, fixing the AApro/SH connection issue using method 1 (Installing AA+ drivers on AApro, https://astronomy-im..._ASIAIR_Pro.pdf) should also fix the guiding issue. Which method did you use to fix the connection issue ?

 

 

2) I get the tracking nonlinearity but what is the sub-1sec pulse commands not registering ? Is it part of the nonlinearity tracking issue ?

 

Best,

 



#107 seven6

seven6

    Sputnik

  • -----
  • Posts: 43
  • Joined: 06 Oct 2021
  • Loc: Los Angeles

Posted 08 August 2022 - 01:12 PM

Well well well! I figured out why the ASIAIR devices such as the AAP do not guide the mount!

 

I have MITMed the serial protocol between my AAP and the SH -- these are the pulse commands sent to the mount during calibration:

:Mw02000#> 2022/08/08 01:01:11.079041  length=9 from=164 to=172
:Mw02000#> 2022/08/08 01:01:14.083493  length=9 from=173 to=181
:Mw02000#> 2022/08/08 01:01:17.089310  length=9 from=182 to=190
:Mw02000#> 2022/08/08 01:01:20.114616  length=9 from=191 to=199
:Mw02000#> 2022/08/08 01:01:23.027646  length=9 from=200 to=208
:Mw02000#> 2022/08/08 01:01:26.099047  length=9 from=209 to=217
:Mw02000#> 2022/08/08 01:01:29.154534  length=9 from=218 to=226
:Mw02000#> 2022/08/08 01:01:32.105689  length=9 from=227 to=235
:Mw02000#> 2022/08/08 01:01:35.076211  length=9 from=236 to=244
:Mw02000#> 2022/08/08 01:01:38.120907  length=9 from=245 to=253
:Mw02000#> 2022/08/08 01:01:41.085060  length=9 from=254 to=262
:Mw02000#> 2022/08/08 01:01:44.041070  length=9 from=263 to=271
:Mw02000#> 2022/08/08 01:01:47.124545  length=9 from=272 to=280
:Mw02000#> 2022/08/08 01:01:50.079288  length=9 from=281 to=289
:Mw02000#> 2022/08/08 01:01:53.088606  length=9 from=290 to=298
:Mw02000#> 2022/08/08 01:01:56.075555  length=9 from=299 to=307
:Mw02000#> 2022/08/08 01:01:59.122885  length=9 from=308 to=316
:Mw02000#> 2022/08/08 01:02:02.101514  length=9 from=317 to=325
:Mw02000#> 2022/08/08 01:02:05.084235  length=9 from=326 to=334
:Mw02000#> 2022/08/08 01:02:08.082848  length=9 from=335 to=343

According to the iOptron serial command reference, this command is supposed to move an EQ mount "west" for 2000ms (my guide step size in AAP). HOWEVER: in the reference it also states "Note: These commands are deprecated and will be removed in a future version. These commands only available in equatorial mounts." So, it looks like they finally got rid of the Mn/e/s/w commands in the SH firmware. The v3 INDI drivers use the newer ZS/Q/E/C pulse commands. I used ":ZC02000" instead and sure enough I actually saw the guider image move!

 

See here: https://github.com/i...driver.cpp#L515

 

Is ZWO using the standard v3 driver? Did they patch INDI for some reason? Or are they using INDI startMotion routine instead? (That is not the correct way to utilize the driver for guider calibration...)

 

Edit: This does not fix the other issues with the mount such as tracking nonlinearity and sub-1sec pulse commands not registering...

Ah, this does help explain why it was failing for my laptop tests. I am using Indigo and it looks like their iOptron drivers are the old v2 drivers. It will connect and operate the mount, but guiding does not work. I have given up trying to figure out how to run the iOptron V3 INDI library and drivers on a Mac. Kstars/Ekos is supposed to do it, but I can't get it run on any of my computers.

 

Also, I just noticed that you can also connect to and control the SH on the AAPro by selecting the CEM70 mount. Not sure this will change anything if the AAPro/AA+ are using the wrong protocol for sending guiding commands? But I might give it a test tonight just to see.

 

I am tempted to go buy a cheap PC just to test this...


Edited by seven6, 08 August 2022 - 01:26 PM.


#108 Astro446

Astro446

    Sputnik

  • -----
  • Posts: 41
  • Joined: 28 Apr 2022

Posted 08 August 2022 - 10:23 PM

Clear skies allowed me to tested the tracking and guiding after installing the AA+ drivers on the AApro.

 

I also have the non linear tracking issue. Here is a GIF of 6 sequential 60sec exposure. The FOV is strongly moving, and on some frame the stars are elongated. Did you guys try to track without connecting ASIairPro ?

 

https://www.dropbox....6pckbn.gif?dl=0

 

The guiding is not passing the calibration steps: "RA Calibration Failed: star did not move enough"


Edited by Astro446, 08 August 2022 - 10:24 PM.


#109 Astro446

Astro446

    Sputnik

  • -----
  • Posts: 41
  • Joined: 28 Apr 2022

Posted 08 August 2022 - 10:34 PM

Are the tracking and guiding issue also occur when using AA+ ?



#110 joshumax

joshumax

    Explorer 1

  • -----
  • Posts: 94
  • Joined: 13 Mar 2013
  • Loc: Seattle

Posted 09 August 2022 - 04:49 AM

The plot thickens!

 

Apparently, the mount is only registering pulse guiding commands on the DEC axis...

 

I discovered this when my patched v3 INDI driver for the ASIAIR pro wasn't calibrating on RA. I ran the ZQxxxxx/ZSxxxxx commands manually and there was absolutely no effect on the mount. I will disassemble the front cover to confirm my suspicions in the morning...

 

In the meantime, anyone who wants to test this out on there own can download the patched driver (just a few bytes were changed to correct pulse commands) and inject it into the rootfs of the AAP. Be sure to chmod 755 after moving to /usr/bin/indi_ioptronv3_telescope.



#111 swilson88

swilson88

    Lift Off

  • -----
  • Posts: 4
  • Joined: 14 Jun 2022

Posted 09 August 2022 - 04:23 PM

Any updates from ioptron on this issue? 



#112 RogerM

RogerM

    Viking 1

  • *****
  • Posts: 690
  • Joined: 13 Aug 2020
  • Loc: California

Posted 09 August 2022 - 10:29 PM

@joshumax,

 

Nice sleuthing there!  Your message regarding the deprecated function curiously ties in with another observation on my part.  Since I obtained the 8410 HC I noticed the absence of a serial port on it.  Unlike the 8404 that I use with my CEM25P and SGP that allows me to tie in a serial interface to the AAP, this new HC does not have that option.  So, the question now is was this mount ever considered to be auto guided at all?



#113 joshumax

joshumax

    Explorer 1

  • -----
  • Posts: 94
  • Joined: 13 Mar 2013
  • Loc: Seattle

Posted 10 August 2022 - 11:26 AM

@joshumax,

Nice sleuthing there! Your message regarding the deprecated function curiously ties in with another observation on my part. Since I obtained the 8410 HC I noticed the absence of a serial port on it. Unlike the 8404 that I use with my CEM25P and SGP that allows me to tie in a serial interface to the AAP, this new HC does not have that option. So, the question now is was this mount ever considered to be auto guided at all?

The 8410 HC does not use traditional iOptron firmware (as the underlying protocol since the CEM120 has moved most functionality to the mount mainboard). HBX therefore communicates with the mount MB over secondary RS232 channel. This has numerous advantages such as decoupling the HC and MB interfaces and controlling/updating the mount without the need for a GoToNova to be connected. Fun fact; the 8410 port can double as another serial interface to the MB with the right level converters.

In other news, I took off the front cover again and found that the RA axis does indeed accept pulse guiding commands; sometimes. In reality it is unusably buggy. Sometimes nothing happens, and other times the motor will spin wildly after finishing the command. The DEC motor exhibits no such problems in my testing however there is significant backlash when guiding DEC due to the way the belt meshes with the gearing assembly. Something is very, VERY wrong with the RA axis motor board. I will reverse engineer the firmware later to investigate further.

Edited by joshumax, 10 August 2022 - 11:29 AM.

  • dciobota likes this

#114 dciobota

dciobota

    Mercury-Atlas

  • *****
  • Posts: 2,873
  • Joined: 07 Aug 2007
  • Loc: Sitting in a corner in southeast Arizona

Posted 10 August 2022 - 11:29 AM

You know, ioptron should pay you for all this work. ;-). Great job of sleuthing there.

#115 Astro446

Astro446

    Sputnik

  • -----
  • Posts: 41
  • Joined: 28 Apr 2022

Posted 10 August 2022 - 01:10 PM

The 8410 HC does not use traditional iOptron firmware (as the underlying protocol since the CEM120 has moved most functionality to the mount mainboard). HBX therefore communicates with the mount MB over secondary RS232 channel. This has numerous advantages such as decoupling the HC and MB interfaces and controlling/updating the mount without the need for a GoToNova to be connected. Fun fact; the 8410 port can double as another serial interface to the MB with the right level converters.

In other news, I took off the front cover again and found that the RA axis does indeed accept pulse guiding commands; sometimes. In reality it is unusably buggy. Sometimes nothing happens, and other times the motor will spin wildly after finishing the command. The DEC motor exhibits no such problems in my testing however there is significant backlash when guiding DEC due to the way the belt meshes with the gearing assembly. Something is very, VERY wrong with the RA axis motor board. I will reverse engineer the firmware later to investigate further.

Amazing findings!

 

Are you still using ASIairPro during all those test ?

 

Best,
 



#116 GerryGoldman

GerryGoldman

    Sputnik

  • -----
  • Posts: 42
  • Joined: 14 Oct 2021

Posted 10 August 2022 - 03:46 PM

I have an AAPro - Those settings do not appear to work for me. So maybe there is a +/Pro difference in play.
 

I don’t have a SkyHunter, but I’m seriously looking at it. I do have the CEM40 and Asiair Plus and they require a USB hub between the mount and Asiair. Perhaps it’s the same case here?

 

im trying to find online reviews on the iOptron SH, but there’s almost nothing out there. 



#117 Astro446

Astro446

    Sputnik

  • -----
  • Posts: 41
  • Joined: 28 Apr 2022

Posted 10 August 2022 - 04:07 PM

I don’t have a SkyHunter, but I’m seriously looking at it. I do have the CEM40 and Asiair Plus and they require a USB hub between the mount and Asiair. Perhaps it’s the same case here?

 

im trying to find online reviews on the iOptron SH, but there’s almost nothing out there. 

I have a CEM40 too, it is indeed a USB connection between the mount and ASIair, but big difference is that the CEM40 has a ST4



#118 seven6

seven6

    Sputnik

  • -----
  • Posts: 43
  • Joined: 06 Oct 2021
  • Loc: Los Angeles

Posted 10 August 2022 - 04:29 PM

I don’t have a SkyHunter, but I’m seriously looking at it. I do have the CEM40 and Asiair Plus and they require a USB hub between the mount and Asiair. Perhaps it’s the same case here?

 

im trying to find online reviews on the iOptron SH, but there’s almost nothing out there. 

In short, there are just not that many out there yet. So the users on this thread are the guinea pigs.
 

We have sorted out the connectivity problems, now we are dealing with two separate but related issues:

  1. The ASIAir is not sending the correct guiding commands to the mount. This will require an update from ZWO unless you want to patch yourself like @joshumax.
  2. The mount is exhibiting some very strange behavior in the RA axis. The result is that you can't do unguided exposures 30sec or longer without star trailing.

Last night I shot an unguided (since we can't currently guide) stack of about 15 x 60 sec frames. It looks to me like there is a gnarly periodic error in the gearing that causes the image to shift forward and then back in the RA axis. The result is stars that look like UFO's. iOptron asked that I run a tracking test without the ASIAir attached and I will do that tonight assuming I can see stars.

 

Here is the stacked image:

CalNebula 60sec 15img stack 2

 

Here is a screen capture of me running the stack through Blink in PI: https://vimeo.com/738356450/19c9d3d800

 

I plan to shoot a longer stack of 60sec exposures tonight. Will blink them again just to see if there is repetition in the error.


Edited by seven6, 10 August 2022 - 04:46 PM.


#119 RogerM

RogerM

    Viking 1

  • *****
  • Posts: 690
  • Joined: 13 Aug 2020
  • Loc: California

Posted 10 August 2022 - 07:54 PM

In short, there are just not that many out there yet. So the users on this thread are the guinea pigs.
 

We have sorted out the connectivity problems, now we are dealing with two separate but related issues:

  1. The ASIAir is not sending the correct guiding commands to the mount. This will require an update from ZWO unless you want to patch yourself like @joshumax.
  2. The mount is exhibiting some very strange behavior in the RA axis. The result is that you can't do unguided exposures 30sec or longer without star trailing.

Last night I shot an unguided (since we can't currently guide) stack of about 15 x 60 sec frames. It looks to me like there is a gnarly periodic error in the gearing that causes the image to shift forward and then back in the RA axis. The result is stars that look like UFO's. iOptron asked that I run a tracking test without the ASIAir attached and I will do that tonight assuming I can see stars.

 

Here is the stacked image:

 

 

Here is a screen capture of me running the stack through Blink in PI: https://vimeo.com/738356450/19c9d3d800

 

I plan to shoot a longer stack of 60sec exposures tonight. Will blink them again just to see if there is repetition in the error.

I got essentially the same request in my return email from iOptron but from a different 'tech' vs the first communique.  I had to re-iterate that I already had supplied a link to subs collected with the mount operating in unguided mode which were confirmed by the first tech that they had reviewed them...sounds like another team is engaging in this issue.  I also uploaded a video capture taken with my 3D printed Newtonian Planetary rig which shows the erratic RA movement, amplified by the scopes sensitivity to any vibration and sent the link to them to study.   

Attached Thumbnails

  • SH_Newt_Test.jpg


#120 John59

John59

    Viking 1

  • *****
  • Posts: 730
  • Joined: 06 Nov 2011
  • Loc: Round Rock,TX

Posted 10 August 2022 - 08:59 PM

In short, there are just not that many out there yet. So the users on this thread are the guinea pigs.
 

We have sorted out the connectivity problems, now we are dealing with two separate but related issues:

  1. The ASIAir is not sending the correct guiding commands to the mount. This will require an update from ZWO unless you want to patch yourself like @joshumax.
  2. The mount is exhibiting some very strange behavior in the RA axis. The result is that you can't do unguided exposures 30sec or longer without star trailing.

Last night I shot an unguided (since we can't currently guide) stack of about 15 x 60 sec frames. It looks to me like there is a gnarly periodic error in the gearing that causes the image to shift forward and then back in the RA axis. The result is stars that look like UFO's. iOptron asked that I run a tracking test without the ASIAir attached and I will do that tonight assuming I can see stars.

 

Here is the stacked image:

 

 

Here is a screen capture of me running the stack through Blink in PI: https://vimeo.com/738356450/19c9d3d800

 

I plan to shoot a longer stack of 60sec exposures tonight. Will blink them again just to see if there is repetition in the error.

Yes, I am seeing some drift in my images even at 30 seconds.  This is after excellent PA and plate solving with ASIAIR+.  I will continue to testing.  My setup is very lightweight as it is only the SW EVOGUIDE 50DX using ZWO ASI1600MM Pro. The ASIAIR+ is mounted on the tripod and no guiding scope used.



#121 seven6

seven6

    Sputnik

  • -----
  • Posts: 43
  • Joined: 06 Oct 2021
  • Loc: Los Angeles

Posted 11 August 2022 - 03:18 AM

Yes, I am seeing some drift in my images even at 30 seconds.  This is after excellent PA and plate solving with ASIAIR+.  I will continue to testing.  My setup is very lightweight as it is only the SW EVOGUIDE 50DX using ZWO ASI1600MM Pro. The ASIAIR+ is mounted on the tripod and no guiding scope used.

Yeah, I actually think just placing my camera static on a tripod would actually have less drift that what I am seeing in these 30 sec exposures!


Edited by seven6, 11 August 2022 - 03:23 AM.


#122 GerryGoldman

GerryGoldman

    Sputnik

  • -----
  • Posts: 42
  • Joined: 14 Oct 2021

Posted 11 August 2022 - 08:52 AM

I have guided SkyHunter with ASiAir via USB cable and it works. 

Do you track in RA only with this mount?



#123 metamorphosis1008

metamorphosis1008

    Sputnik

  • -----
  • Posts: 43
  • Joined: 16 Apr 2022

Posted 11 August 2022 - 09:45 AM

My SkyHunter stopped recognizing the DEC guiding on AA+. It also began having trouble slewing (extremely slow slewing speed). I returned the mount. I think it has a potential, but not yet ready for prime time!

#124 seven6

seven6

    Sputnik

  • -----
  • Posts: 43
  • Joined: 06 Oct 2021
  • Loc: Los Angeles

Posted 11 August 2022 - 10:28 AM

My SkyHunter stopped recognizing the DEC guiding on AA+. It also began having trouble slewing (extremely slow slewing speed). I returned the mount. I think it has a potential, but not yet ready for prime time!

Yeah, starting to be my conclusion as well. Just talked to my vendor yesterday about returning mine. Such a bummer. I was so excited for this thing, but as your said, it was clearly not ready for release.



#125 GerryGoldman

GerryGoldman

    Sputnik

  • -----
  • Posts: 42
  • Joined: 14 Oct 2021

Posted 11 August 2022 - 10:52 AM

My SkyHunter stopped recognizing the DEC guiding on AA+. It also began having trouble slewing (extremely slow slewing speed). I returned the mount. I think it has a potential, but not yet ready for prime time!

I'm a bit confused. My understanding is that this mounts tracks in RA only. Shouldn't you shut off DEC guiding? (There's a setting on the Asiair+ for RA only)




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