ASIAIR v2.4.1 Public Beta Released!: Page 2

ASIAIR v2.4.1 Public Beta Released!

PMTeam@ZWO

9Ej7KtYy We have recorded this requirement and will implement it in subsequent versions.

9Ej7KtYy

PMTeam@ZWO Thank you! I’ve been waiting for this to come. Now I will have to not sell my equipment. Again thank you and please release this soon because I have a few clear nights coming up and want to try it!

PMTeam@ZWO

andrelucasmelo You can try this public beta version. Any feedback is welcome and we will deal with it in time. Thank you.

PMTeam@ZWO

azskyguy exposures times in auto run and guide exposures that are randomly set to zero and can't be changed, forcing a reboot,

Hello, can you give more description of the problem? What operations were you doing at the time? If possible, please send us a log immediately after the problem occurred. Or if there is any log containing this content before, can you share the BT number? We take this issue very seriously.

azskyguy

PMTeam@ZWO
I was in an auto run session. I looked and the guider was way out of position. I checked the guide exposure and it said zero. I tried to change it and it would not move from zero. I had to reboot the 2600 Air.
something similar happened in preview when I was setting up. suddenly the exposure time was set to 0 and I had no other options. I had to reboot camera. I've sent many logs over the last several days.

R0k9pZfT

So far, here are my findings tonight using the Android app and 2.4.1_0626.

Object list filtering works. I still don't like the interface, but it works. I must be dense--what are the white arrows along the top of each row? I can't figure those out.

Goto from saved image works. However, there are problems. I took about 6 images in Live mode of M101. I stopped that, went to Preview, then opened the saved images from my Live lights folder for IC 5070. I chose one and told it to goto and that worked, although on the Preview page it now just says "Target" where it should say IC 5070. Then I switched back to live mode, started guiding, and started a Live mode capture. This all worked, but all of these new images of IC5070 were named for M101 and landed in the M101 folder, not the IC 5070 folder and name.

Plate solve from saved image isn't consistent. I next chose a bright, detailed light of M16 and told it to goto. This time it took about 110s to plate solve! I don't know if it applies here, but I have the ASIair set to plate solve using the old method because I find the new plate solve to be really really slow.

Oh, and my M16 sequence is now also landing in my M101 folder. M101 is the last object for which I manually did a Goto and not using a saved image as described above.

I had a couple WiFi disconnects, both times when I was accessing the on-board flash of my ASIair Plus. Not reproducible, but this has never happened before. I'm using station mode. Wifi seems otherwise fine.

Live stacking appears to be fixed.

Flats histogram appears fixed.

All sky polar align works.

I'll post more if I gather more data. Probably going to wrap this up for the night soon.

PMTeam@ZWO

R0k9pZfT First of all, thank you very much for helping us with testing.

R0k9pZfT Object list filtering works. I still don't like the interface, but it works. I must be dense--what are the white arrows along the top of each row? I can't figure those out.

The white arrows indicate the positions of celestial bodies at different times.

R0k9pZfT Goto from saved image works. However, there are problems. I took about 6 images in Live mode of M101. I stopped that, went to Preview, then opened the saved images from my Live lights folder for IC 5070. I chose one and told it to goto and that worked, although on the Preview page it now just says "Target" where it should say IC 5070. Then I switched back to live mode, started guiding, and started a Live mode capture. This all worked, but all of these new images of IC5070 were named for M101 and landed in the M101 folder, not the IC 5070 folder and name.

This is a bug in our file name saving design. We will optimize the overall design here in subsequent versions.

R0k9pZfT Plate solve from saved image isn't consistent. I next chose a bright, detailed light of M16 and told it to goto. This time it took about 110s to plate solve! I don't know if it applies here, but I have the ASIair set to plate solve using the old method because I find the new plate solve to be really really slow.

Could you please send us this Fits image so that we can analyze it and see if it is a bug or if the parsing algorithm needs to be further improved? My email is luffy.liu@zwoptical.com

R0k9pZfT I had a couple WiFi disconnects, both times when I was accessing the on-board flash of my ASIair Plus. Not reproducible, but this has never happened before. I'm using station mode. Wifi seems otherwise fine.

Let's analyze the logs

R0k9pZfT

PMTeam@ZWO The white arrows indicate the positions of celestial bodies at different times.

I still don't understand. What position? What exactly are we being shown?

R0k9pZfT

I haven't seen this problem before on 2.3.3 with goto from a saved image putting the new images in the wrong folder with the wrong name. Can this not be reverted? Otherwise now we have to goto the object to get the name & folder correct, then goto from the saved image so the camera rotation is checked & aligned. Why should we want to wait for a future update to avoid this craziness? For this alone I will stick with 2.3.3 unless I've just been lucky that it hasn't affected me yet.

PMTeam@ZWO

R0k9pZfT S N E W. Arrow pointing up indicates north

R0k9pZfT

azskyguy was in an auto run session. I looked and the guider was way out of position. I checked the guide exposure and it said zero. I tried to change it and it would not move from zero. I had to reboot the 2600 Air.

2.4.1?

PMTeam@ZWO

azskyguy 我当时正在自动运行。我查看了一下，发现导星仪的位置完全偏离了。我检查了导星仪的曝光量，它显示为零。我尝试更改曝光量，但它无法从零开始移动。我不得不重启 2600 Air。

Please send the log again after the problem occurs and before restarting the camera, thank you. After restarting the camera, the log content will be overwritten and cleared.

Could you provide a screenshot of the problem so that we can better understand the problem? Thank you

R0k9pZfT

Went back to 2.3.3 and the plate solve on my M16 took a long time also (I stopped it at 30s). I went back & forth between old & new plat solve and the new one solves it every time in 8s. The old takes way longer. So odd, because in other menus the new method is sooo slow!

And I'm wrong--2.3.3 also has the same issue with file naming based on a plate solve goto. I've just been lucky I guess in how I was doing things.

PMTeam@ZWO

R0k9pZfT I contacted you by email and suggested that you use the new plate solve algorithm for images with many stars, which will be faster.

azskyguy

R0k9pZfT
2.4

azskyguy

PMTeam@ZWO

I've dumped 2.4. Why would I keep using it? It doesn't work, so can't provide fresh logs. went back to 2.33. I will note that plate solves work on 2.33 (so it wasn't my NB filter that was the problem, but the 2.4 software. No more random meridian flips. No loss of exposure control. 2.41 did not appear to have fixes of the issues I was having, so didn't bother with it.

Luxo

@ZWO:

Please locate your code for version 2.3.3 and re-release that as version 2.4.2 so that everyone will be”updated” to that automatically.

That way we all have something that at least works.

Tomorrrow is Saturday, it’s going to be clear, and I expect I will lose another month because your firmware is broken.

Ditch 2.4.1 and start afresh please.

Corsair

Luxo you on Apple or Android?

PMTeam@ZWO

Luxo Hello. Version 2.4.1 fixes some issues reported by users

PMTeam@ZWO

azskyguy Hello. We have fixed the wrong meridian flip problem in 2.4.1.

I checked the logs you submitted, all of which are about meridian flip problems and status stuck at loading. Our developers have responded to all the logs you submitted.
Regarding the "No loss of exposure control" you mentioned, we suspect that the camera is offline, so the exposure time cannot be modified. This requires you to upload the log after the problem occurs so that we can further verify the guess. We have not received any feedback from other people about similar problems.

As for the plate solve failure during PA and GoTO, first of all, we recommend that you use the old parsing algorithm. Secondly, we have optimized PA in v2.4.1, and the effect of this version is consistent with v2.3.3. Thirdly, if you encounter parsing failure during the GoTo process, you can also upload the log to us to further find the cause.

enzinho25

a few month ago i opened the ticket, becauae the asi air pro not take the input voltge and the support close faster my ticket. they didn't explain the technical issue, why this feature it is not compatible with the last version?

R0k9pZfT

enzinho25 What input voltage?

PMTeam@ZWO

enzinho25 Hello. Could you please give a more detailed description of the problem so that we can better understand what you are encountering?

enzinho25

R0k9pZfT i attach the file

« Previous Page Next Page »