ASIAIR v2.4.2 has been released!: Page 11

ASIAIR v2.4.2 has been released!

franco

Tested 2.4.4 (12.63) and can confirm the planet stacking and editing now works.

The odd looking histograms when in video mode still persist.

gm6wS8xS

azskyguy

the binaries for platesolving (from Astrometry.net) has changed

Luxo

gm6wS8xS
Really ? How did you know that ?

azskyguy

Is that good? I hope so. Clear tonight so will see how plate solving and meridian flips go. If this is another horrible release I'm going to drop ZWO. There's something wrong when a company stops communicating with customers and issues several bad releases in a row?

viperduude

viperduude I used a different AA+ with same cables and guiding never dropped. It seems my "guiding to looping" issue is with that AA+ unit.

gm6wS8xS

Luxo

I unzipped the firmware update archive in the app bundle and looked at the debian package in it, then the changed binaries.

givoly

PMTeam@ZWO So what is the recommended gain for the ASI585mc Air? Should it be sent ideally to 200? Under what circumstances what gain should be used? It would be helpful to have recommendations for this, in general.

flappah

givoly afaik this depends on the software you’re using. If you use the ASIAIR or ASIStudio latest versions then gain is to be set to 200 for HCG. If you’re using the Ascom drivers it’s still 252. Unless there’s a new ascom driver update I’m not aware of.

Steden

I've not been able to get the rotate function to work, both that and the frame button are greyed out in the sky atlas.

I have tried something I saw online about taking a preview image, plate solve then sync mount but its still greyed out.

Luxo

Version 2.4.4. has issues, see post #49 at https://www.cloudynights.com/topic/973090-asiair-242-beta-is-available-for-testing/page-3

Regarding GOTO with plate solving never finishing, I experienced that too with 2.4.2; GOTO with platesolving is broken in that it never completes.

As gm6wS8xS noticed, you have changed the binary for platesolving and in the process you have broken it.

For the bazillionth time STOP CHANGING STUFF THAT WORKED.

malc

After weeks of problems, and using ASIAIR v 2.4.3 on my Android phone I was able to get a good imaging run last night, 19-360sec lights before thick fog put paid to it. Calibration, DEC Duration & RA Duration on ASIAIR are 2000, 2000, 2000 by default. I chaged these to Calibration=600, Max DEC Duration = 450, Max RA Duration = 450, and also Guide Camera Gain to 200. Platesolve took around 3 seconds and guiding was almost instant. I’m slightly in disbelief, it will be several days here before weather clears sufficiently for another night of tests. In also upgraded my PC from Windows 10 to 11 yesterday, and installed ASIAIR plus camera drivers. Tried Maxim DL6 (which was installed on the PC several years ago) and it recognised and opened the ASIAIR2600MM Air camera and guider though I haven’t yet tried a test run using it.

azskyguy

Tried version 2.4.4 last night. Meridian flips still fail. Sent logs to ZWO, but heard nothing back. Scope swings to the west properly, plate solves, then tries to acquire guide stars. That fails and it looks like tracking is off, because as I watch the guiding camera the stars are slipping away. I'm on an AM3 mount, with the ZWO rotator. I'm stumped. I think it's a software issue. Guiding is perfect to the east. A disaster to the west. ZWO is unresponsive. Tried to log on to their new and unneeded site, but it wouldn't let me, insisting I check off the privacy and rules box, but none appears for me to check off.

ZWO seems to be headed downhill rapidly, taking their customers along with them.

Gatsu87

The last reply from a zwo employee to this section was 20 days ago. I don't think this is correct. All the requests and reported problems are in this forum; it makes no sense to post them on the new site, but we would like a response from zwo regarding the numerous problems reported in the latest versions of the software.

Corsair

I know it's currently National Day holiday (October 1 to October 8) but @PMTeam@ZWO and @Tech@ZWO should've posted something beforehand AND posted in here about the holiday (during which time they won't respond).

Sonixx

I know it is extremely frustrating if the astro gear is not working right.

At least for me and some Astro Friends the 2.4.2 is working absolutely flawless.

I wonder what could be the reason that some people are experiencing such issues. Maybe we can help isolating the issue.

To start I will list the conditions the software works:
-Location: Germany
-Time Zone GMT+1
-Apple and Android
-Asiair Pro and Plus
-Zwo Mount and Skywatcher EQ6 and Skywatcher SA GTI
-simple setups like Asi main + guide cam only + SW mount
-Full blown ZWO setup including mount and Rotator and Filter wheel
-Plan and Autorun modes

However, a friend was using an Android Tablet that was not to connected to any Phone or WLAN, had incorrect location and time zone data. This false data was transmitted to the mount and as a consequence the meridian flip happend at the wrong time almost running the Camera into the Tripod. I can only recommend checking time and location data in the mount tab before going Autopilot.

I hope these issues can be resolved fast for the affected folks. Did anyone try to reset the asiair and deleting the app to start from scratch to check if the issues disappeared ?

AstroDude42

Sonixx do you mind sharing what scope and focal length you’re using? Thanks in advance.

Luxo

I have done the firmware reset and re-install cycle more times than I've had hot dinners in the past 3 weeks.

What also matters is your selection of camera and scope/guide focal lengths; I use a 2600MC DUO and the focal length for main and guide is 3000mm.

On 2.4.4 I experience:

polar alignment - worked,
Catalog is OK,
Autofocus - seems quicker than it was in 2.3.3,
GOTO with plate solve - the initial slew seems always to be off-target and the subsequent plate solve never finishes,
Autoguiding ... starts, shows GUIDING but after a minute or so it fails and the mount drifts.
Meridian flip - it flips, but after the flip does not acquire a guide star and AUTORUN does not resume imaging.
CAA can be used manually with the handset, but does unwanted rotations with no way to disable short of disabling it entirely in ASIAir.
Some user-interface changes I dont like - making the UI more cryptic than it was. For example for example the word "GOTO" has been removed just the icon remains.

Not useable.

Staying on 2.3.3

AstroDude42

Luxo i remember a discussion on this forum about maximum focal length. It’s been a while, unfortunately i can’t find it anymore – afaik Chen ( @w7ay ) has been part of the discussion. I do remember that 3000 mm focal length is a lot and might reach the upper maximum of ASIAir‘s capabilities in regards to plate solving. Would be interesting to know more about your setup, like a) are you plate solving with a filter attached b) the exposure time when plate solving, etc.

Sonixx

AstroDude42

Currently I am using an Askar SQA106, having 505mm FL.
My friends are using 250mm to _600mm

In the Galaxy Season I was using a 6“ RC with _1300mm fl without issue. However I did not try this with the new Firmware.

AstroDude42

Sonixx thanks for the quick response. Much appreciated. I wonder if it’s a problem related to focal length some others have. I still have to find the time to get my 250 mm, 480 mm and 2032 mm scopes out again and try it with my ASIAirs.

« Previous Page Next Page »