ASIAIR v2.4.2 has been released!: Page 13

ASIAIR v2.4.2 has been released!

franco

I've been able to PA at 3000mm with an ASI294, don't remember the exact fov but it's small.

Corsair

Regarding plate solving with the ASIAIR this should be the case as per ZWO online manuals (that do need updating but are still mostly valid) https://www.yuque.com/zwopkb/asiair/plate-solve:

In order to perform a Plate Solve efficiently, your focal length need to be set in the Main Camera settings (or check at connection page on app startup).

Plate solve may fail if your imaging parameters (Exp / Gain) return either too few or too many stars. Best range is from 100 to 400 stars detected during Plate Solve.

The usable range for plate solve function is based on Field of View (FoV - combination of focal length of scope and sensor size) which has to be within 0.2 deg to 33 deg.

Exposure settings are in Telescope Settings, under Center EXP Time and Gain in Main Camera Settings.

Easiest way to check that you do meet that is by using the Field of View caluclator over at Astronomy Tools (just change it to Imaging Mode first): https://astronomy.tools/calculators/field_of_view/

Luxo

Not necessary.

ASIair determines the focal length from plate solving - and this is saved and restored from one setup to the next.

The only reason to reset the focal length to an approx value - manually - is if you swap scopes. And after the first solve it will determine the actual value anyway.

Or at least it did, in version 2.3.3. In my case platesolving never finishes in 2.4.4 so quite possibly that’s broken too.

Corsair

Luxo Not necessary.

For first time setup it is. Usually you would set the focal length to 0, then slew to an area of the sky greater than 5° away from NCP/SCP, take an exposure in Preview Mode, then tap Plate Solve and, if successful, it will then show calculated focal length. You then tap the Sync option to ensure it saves.

After that, then yes, the focal length should remain saved and there would be no need to change it UNLESS you make a change to equipment in your optical path (e.g. adding in a CAA, or EFW, etc) and/or changing scopes. In which case it is best to re-do the process to ensure the focal length is calculated correctly.

Everything else in the quote is also extremely relevant information especially this:

The usable range for plate solve function is based on Field of View (FoV - combination of focal length of scope and sensor size) which has to be within 0.2 deg to 33 deg.

Which is why putting your equipment details into Astronomy Tools first (https://astronomy.tools/calculators/field_of_view/) BEFORE even buying the ASIAIR - is important to determine if the ASIAIR can actually plate solve with your chose equipment.

azskyguy

Sonixx
I get failed flips 100% of the time on my current build which is 2.4.4. I was having it on previous builds now going back several weeks. As I approach the meridian tracking turns off, the flip occurs and the position is confirmed to be correct, but tracking never comes back on, and as the guider tries to grab a star the stars just drift away. Others have reported this and logs have been sent. I'm in an email conversation with someone from support, who is waiting for engineers to examine the logs, but it's some sort of weeklong holiday in China.

Last night while imaging an old bug resurfaced. During an Auto Run, the sequence stopped. The app displayed 'loading' and the last image never downloaded while everything just sits there stuck on loading. I can work around it by hitting pause and then resume, but it's not exactly the unattended sessions I was hoping for and used to have.

When it works, the software is great, but over the last several weeks there's always something broken.

I'm trying to help ZWO with logs and descriptions.

Also, Wifi continues to be terrible. I have the all in one air , and it really needs an ethernet port. I can have my laptop 5 inches from the camera and still get crummy connections.

Sonixx

azskyguy

I am currently staying on the current release, as everything works OK.

Regarding your Meridian Flip failure, I had something like this with my TeenAstro and it was actually a bug in the TeenAstro Firmware.

Which mount are you using and did you try to activate the option to calibrate the guider after meridian Flip/ every object. That helped with my TeenAstro a while ago.

azskyguy

Sonixx There's no doubt there's a bug in the software/firmware.
I use a ZWO AM3 mount. Yes, I tried the option to recalibrate after a flip, but since the bug turns off tracking it can't get to a guide star.

Sonixx

That is very strange, have no issues with my AM5N and AM3. But I have not updated the Firmware of the mounts.

azskyguy

I don't think it's the mount.. this issue started with ASIAIR update a few versions ago...others are reporting it as well. I've made ZWO aware and they are examining my logs. My mount firmware is up to date.

Haggy38

Absolutely no Issues whatsoever, Focussing, Meridian Flip, CAA, Guiding, etc. My setup:

ASIAIR v2.4.2

Bogota, Colombia
ZWO AM5
ZWO Asi2600MC Pro
ZWO CAA
ZWO EAF
Svbony sv550 122mm APO
ZWO Asi120mm Mini
ZWO Asiair Mini

Hope gets solve for you'll guys sooo.

retman

Haggy38 android or iOS?

V5HL6Ecz

Haggy38

Me too, no problem

ASIAIR v2.4.3
Tablet Samsung Galaxy A10+

Italy - Milano ( Bortle 9 )
Sky-watcher GTI
ZWO Asi533MC Pro ( svbony sv220 - optolong l-pro )
ZWO EAF
Askar 71F - 490mm APO
ZWO Asi120mm Mini
ZWO Asiair +

Haggy38

retman IOS iPad, iPhone and Mac mini M4

Luxo

This is an issue with the app and firmware. Version 2.3.3 and earlier behave correctly.

Corsair

Corsair
Well so far I've tested doing calibration frames in Live Mode. All is working well and as expected using ASIAIR AppFirmware 2.4.3-12.55 on my Galaxy S22 Ultra running Android 15.

Slewing around with the on screen mount controls works fine. Going to Home position works fine. Manually focusing for daylight then night time rough focusing works fine.

Mount Time is correct . We've entered Daylight Saving Time now and the time shown on the mount (under Mount Settings > Mount Info ) is one hour behind the time at my location (shown in the top left of the App and on my Android device itself) with the little warning message now showing. All as expected.

All this has been done indoors due to not so great weather. Hoping I'll get a chance soon to test outdoors.

My use case:
Unguided EAA using Live Mode for Live Stacking. I only ever use Preview, Live, Focus, and Video modes. I don't do Meridian Flip.

My equipment:
Galaxy S22 Ultra running Android 15
ASIAIR App-Firmware 2.4.3 - 12.55
ASIAIR Plus 32GB

HEQ5 Pro mount connected as EQMOD Mount (EQMOD cable from mount to usb 2.0 port on ASIAIR Plus) with its own power supply.
C8 SCT with f/6.3 Reducer and dew shield
ASI294MC Pro camera cooled to 0°C connected to usb 3.0 port on ASIAIR and powered from the ASIAIR.

Luxo

Sure slew works .. it’s GOTO with platesolve that has an issue - the platesolve never finishes.

And you haven’t tried autoguiding.

Corsair

Luxo
And, like I said, I'll test when I get the chance. Weather and available time have to coincide.

And I've clearly stated I only do unguided EAA in Live Mode so rely purely on mount tracking to keep me on target after the ASIAIR does a Go To, platesolve, centre, platesolve routine.

So I won't be testing guiding. I won't be testing Autorun. I won't be testing Plan Mode. I won't be testing Mosaic.

I also don't use an EAF, EFW, or CAA. Nor do I use dew heaters.

I have a comparatively simple setup. Will see if it works with just the basics.

flappah

Ive git two rigs. The first, an SQA55 with Star Adventurer GTi, asi120mm mini, EAF, asi533mc pro and an ASIAIR plus work fine enough. PA, goto, plate solving, guiding. All work as expected. So no problems there.

The second rig is an FF80 scope with EAF, EFW, 220mm mini, asi585mc-pro and CAA on an AM5 do work with an AISAIR but the CAA support is a mess. So i converted the whole rig to Nina. Nina has at least the 90 degrees support for the CAA.

Now I’m busy setting up a third rig with Intes Micro scope and from what I gather from Luxo from his comments on CloudyNights is that the more exotic combinations have issues with the 2.4.x release of the ASIAIR. So I expect issues with this third rig.

Sonixx

From the posts above it seems there are only very isolated problematic cases where the root cause of problems is unknown.
For the vast majority of people the current stable version just seem to work fine.

While this does not help our friends who have indeed real issues, in the grand scheme of things the ASIAIR is a great product which just works for tens of thousands of users. Nobody else to this day came close offering a similar package.

After all the recent ZWO bashing I think we should stop for a moment and appreciate the team behind the the Asiair. That hopefully will continue improving and innovating ( and have a more rigid testing regime).

Thanks for listening,

Stephan

franco

Sonixx is it too much to ask that a commercial product does what it claims to do?

« Previous Page Next Page »