Version 1.5 Guiding issues: Page 4

Version 1.5 Guiding issues

Flincken

the new ios version now available, anyone tried the guiding with that?

mdskies

I'm new to my equipment, ASIAIR Pro, EQ6-R Pro, and had a chance to get some imaging in last night. I'm using the Synscan Wifi dongle to connect to the ASI as the USB port direct to the mount will not work at all. Updated to 1.5.1 yesterday. When I use USB to Synscan controller, the mount switches latitude from W to E and obviously causes my goto function to be unusable. Anyway, initial setup last night was fine, PA, guiding, etc... started my autorun session and got 12 subs before meridian flip. After the flip, I spent an hour and a half trying to resume the session. At first, the guiding never resumed. I managed to start guiding again but it quickly wandered off target. I had to restart the session which wasn't a huge deal but I seemed to get into a loop of not being able to image when guiding started, and then guiding would not maintain. This was all with dithering off. I then started over, enabled dithering, and the guiding was much worse. I suspected my issues were due to a wireless communication issue between the ASI and the Synscan wifi. At first i thought I was doing something wrong but after reading the above, I feel like I'm on the right track. I also have an EQmod cable that arrived today so I will try it next time we have clear skies. Also, I don't get why I can't use the USB port on the mount to connect to ASI. I've tried EQmod, 115,200 baud, every possible power on sequence, it will not detect the mount. PC detects the mount no issues so I know my USB ports and cables are good.

seb

mdskies Do you know if it would be possible to resolve the E/W latitude flip by manually specifying a wrong GPS coordinate during setup (or is there a calculation during the GOTO step that can account for it)? I've had the same issue.

slickwill1675

Reverted to device and app to 1.5.0 and guiding seems to work for ASIAIR Pro + EQ6-R.

I had another sd card lying around so I used that to revert the device firmware back to 1.4.2 using the official restore guide (thanks @mc0676), I copied the license file from the 1.5.1 sd to the new sd 1.4.2 as suggested. Then uninstall the 1.5.1 app on my tablet and installed the older 1.5.0 apk, turned off autoupdates for the app in play store. Then let the asiair app update firmware to be 1.5.0 compatible. Guiding took a while to calibrate but it was able to move the mount and track with no issues unlike 1.5.1. Was able to get a decent picture of the Eastern Veil Nebula over 1.5 hrs, so I think I'm at least unblocked for now.

chris packman

Looking at my Pro when the guiding has gone crazy I see the frame rate drop on the guiding camera too. From my experience, the guiding can be absolutely fine one night then really poor on another. One thing I learnt when mine went crazy recently was not to redo your calibration. It won't help and you will lose your good calibration data. It's far better to just re-boot everything and hope it all comes good.

mdskies

seb Not sure. My EQmod cable came in so I ditched the controller altogether. Have not had an issue with the latitude since.

mdskies

@chris packman#41933 Interesting. When I had troubles after a MF, I had enable post MF calibration. I'm going to try without next time to see how it goes.

Owenpasley

Is it disturbing that zwo doesn't seem to be acknowledging that there may be an issue with this guiding. I have had several corispondents with them and they have suggested different fixes , unfortunately non have worked, my guiding works fine when using phd2 on my laptop so I'm having a hard time believing this isn't software. Anyways hope zwo comes out with some fix

mdskies

I've always tried guiding with the default calibration step, max dec, and max ra which is 2000. I watched a video that states those numbers are too high, perhaps for a different mount. I'm using an EQ6-R Pro with EQmod cable. I had to end my session early tonight due to clouds rolling in but I managed to get guiding working with upping the calibration step to 10000 and max dec and ra to 3000. Completely random choices and I don't understand what these numbers do but I took a 10 minute exposure of CA nebula and the stars were perfectly round. Dithering also worked correctly. I will experiment more next session but can anyone using an Eq6-R pro tell me what numbers they use for guide settings? Also, does the guiding rate play a factor when using a guide scope?

kvastronomer

Can anyone recommend optimal slew speed in ASIAir to guide with EQ6-R? Thanks

PMTeam@ZWO

kvastronomer The guidance speed of cs1x can needs to be set

PMTeam@ZWO

kvastronomer Can anyone recommend optimal slew speed in ASIAir to guide with EQ6-R? Thanks
There are three ways,
#1 Thru EQMOD, do not need to care about the slew spd
#2 Thru the SynScan HC, need to set to 1x which equals to sidereal rate

Thrax05

I am getting thoroughly fed up with these guiding problems and the lack of response from Zwo to fix the issue. I have approx £5000 pounds worth of kit for an automated system that is hobbled by poor guiding, also the ZWO the promised Nikon Z7 support does not work and other supported DSLR's seem to have been removed from ver 1.51 according to other threads here! This is a joke and needs sorting out, I am going to starty posting a warning on the Astro forums to make others aware of these issues and hopefully stop them wasting their money on a piece of crap that not only doesnt guide, support its claimed DSLR list, but also makes it impossible to roll back the updates, good god even microsoft allow you to do that with a system restore! I would urge all asiair users to go to their forums and make others aware of these problems. If Zwo wont listen to, or help people who have already spent there money with them, perhaps they will take notice if people stop spending their money on ZWO products!

PMTeam@ZWO

New DSLRs will be supported in future versions. The Z7 were recognized in the beta of v1.5.Thrax05

Thrax05

@asiair@zwo#42236 Yes it was recognised but the files were unreadable and just gave coloured dashes across the entire image so was still unuseable. Try to give the full answer if you wish to support your customers!

kvastronomer

Is this considered good guiding?
Total RMS error is around 1" but both RA and DEC lines occasionally reach 2" and -2".

billx

I also have found that guiding does not work well with the 1.5 update. I am using an Ioptron ieq30pro mount. If I use PHD2 – I am able to guide. However, I did need to use the guiding assistant to get my guiding down to 0.5. Is there any way to incorporate a guiding assist in Asiair. It might fix the problems we are having with guiding. Using the Asiair v1.5, I can not guide – errors of 1.5 or worse is all I have been able to get. I have set slew speed to 1x. I have had no problems with v1.4. Please advise on what can be done to fix this.

kvastronomer

In my previous post with the screenshot of guiding graph I did not mean to complain but was asking advice of experts out there. My imaging resolution (scope+camera) is around 1". Would this kind of guiding be enough for quality astrophotography? Are those high peaks caused by bad seeing conditions and not by the software?

andybrownyc

I've now tested guiding on the Asiair Pro on two rigs (a heavy Esprit 100 and a lighter Zenithstar 73), both before and after doing a Rowan belt mod and updating to 1.5, and while he guiding is slightly better after the mod, the RA always goes off the rails and the Dec hovers around 3.00. I'm using an ASI290mini for guiding, through both 50mm and 60mm guidescopes. My balance is good, as is PA, and I've tried many different combinations of settings for aggressiveness, duration, calibration resets, etc. I'm not technical at all, but I feel like it's an issue with how the software is interacting with the guidescope. Love the ASIAIR but hope this is worked out in the next version.
Thanks.

Thrax05

@asiair@zwo#42242 Can anyone tell me where to set guidance speed cs1x can? Can't find a setting for it, is it related to slew speed as shown in an image above?

PMTeam@ZWO

Thrax05 It's under the Telescope Settings page, at the bottom part.

« Previous Page Next Page »