psy1280

I haven't the slightest idea what this is, hoping someone can clarify. Last night I was imaging NGC1499 using my Askar Fra600, 3nm Ha filter, 5 minute subs. This clearly seems like an object and not a guiding glitch, etc., What confuses me more is that this was a 5 minute sub, if it was an orbiting object wouldn't it be more blurry? Crazy, huh? (also, a jet traversed the frame)

Everything is tight, nothing loose....tonight same issue right from the start....guiding >90.55....crazy! During a brief period of guiding only the RA line was shown on the graph. Never had this happen...no DEC line. Quite depressing

1. Started imaging the Pacman Nebula last night. For the first four hours, my guiding was fine (i.e., 0.5 – 0.8). 2. At one point after four successful hours into the plan that I set up…using a 3nm Sii filter, I noticed star trails and watched as the guiding deteriorated (i.e., > 17.0 and rising). Star trails in each 5-minute sub getting worse and worse. 3. Multiple stars were circled in the star detection window. I was using an OAG and the stars were in focus. I tried the following: 1. Looping, calibrating, etc. Nothing helped 2. Checked all cables, no snags. 3. Shut down ASIAIR Plus and re-initiated the plan 4. Shut down ASIAIR, and returned the mount to ‘home.’ Re-started ASIAIR, re-did Polar Align (plate solved, focused, etc.) re-made a plan, and initiated the plan. Guiding continued to be extreme. 5. Updated firmware and re-started the entire process and Plan…nothing helped. [FYI: perfectly clear night—no clouds, target was 54 degrees high when I terminated the session] I’ve been successfully using my AM5 mount with my ASIAIR Plus for over a year and this has never happened. I’m hoping someone has some insight as to what might have happened.

I'm going to try to have my DSO images printed on metal. I'm going to be sending jpegs. Can some one tell me what resolution I should send for each print. I'm looking to order something around 12x18 (just an approximate size). I can change the resolution in Photoshop or Topaz Gigapixel AI. I would guess the resolution matters for sharpness and clarity. Thank you, Joe

As anyone who has ever been involved in this hobby knows, to waste a rare, perfectly clear night with an inexplicable glitch is….well, let’s keep this clean and say, frustrating!!! Two nights ago using my ASIAIR Pro and my AM5 mount I had absolutely no issues. Last night, however, I could not connect to my mount. The error message read: Connect Failed Please check the connection method, IP, port and protocol of your mount are correct I’m lost! I use a direct Ethernet Cat6 connection; I use two power sources, one to my mount and the other to my 2600 MM pro camera; I reinstalled the firmware; updated the AM5 mount; disconnected all cables and re-connected one-by-one….NO luck I think the only thing left would be to replace the cable (unless anyone has other ideas). Does anyone know what kind of cable is used by the AM5 to the ASIAIR? I’d like to purchase one). Looking forward to any feedback on this Thank you, Joe

P.S. I've discovered that the ASIAIR does not beep twice. It beeps once and the EAF is the other beep. I've had some limited success this afternoon starting the ASIAIR with the EAF unplugged, then plugging it in when I get into the app. (this doesn't explain the disconnect(s) last night when I was, in fact, in the app, but I'll try again tonight and see what else I find out. Joe

I sincerely doubt anyone can answer this (assuming my ASIAIR Plus is defective), but, I'm hoping I'm wrong. The problem that I now see seems to be with the ASIAIR Plus itself. Last night after losing the Wifi connection (I'm using direct Ethernet connection along with house A/C current), I tried to reboot everything (i.e., turned everything off, even the iPad) when I turned on the ASIAIR unit I would only get the first beep, not the second (which allows you to enter the app). This was the case time after time…I couldn’t get the second beep. At one point I disconnected everything and the unit did turn on. I was able to reset the firmware, but when I tried to use the app, I couldn’t switch out of Preview mode. From that point on for about (at least) 25 more attempts (even with a 'naked' unit, i.e., nothing connect to it) I could never get that second beep and could therefore never connect to the app. I tried disconnecting everything from the unit and that didn’t help. I just kept turning it on and off. Each time one beep no connection. I tried direct Ethernet connection and I tried the ASIAIR’s Wifi, no luck. I’m exhausted. How do I know if I have a defective unit. I cannot see any other reason but to think about purchasing a new unit. Am I wrong. Please help. In summation: I did disconnect all devices from the ASIAIR unit. This left just the naked AIR. When turning on the AIR I heard the first beep, but not the second. The (I think it was 2 time out of 25) I did get booted up (i.e., got that second beep) things froze using the app (although I did manage to do a firmware update) I'm using an Ethernet cable from my router to the unit. I'm using house A/C current, which I've been using for the past year without a problem (I don't have a battery) I'm using a 5 amp power converter Referring to #1 above, since the "naked ASIAIR" wouldn't boot up, I guess it's not a cable issue. I tried a different Ethernet cable also the unit's Wifi I do need to try direct power to the unit (although I did try this recently without any positive results). I'm getting the power through the AM5 directly. Is this a defective unit??? Thank you for any help/suggestions Joe

Just tried a spare power adapter and the preview imaged loaded correctly (hopefully, that was the problem). Will test tonight.

Last night I encountered a few weird problems with my ASIAIR Plus (which I have connected with a direct Ethernet cable). Any suggestion will be greatly appreciated. Here’s what happened: 1. 4-5 attempts to connect to the app 2. Biggest problem I noticed was when an image was loading. Previously it would take about 10-15 seconds, last night it took more than 60 seconds to load. (this was at 600 kb/s) 3. When going to the guiding page the background was black (instead of the usual sky background). Then it would revert back to normal screen. 4. When going to the camera menu, once it wouldn’t open, and once or twice the screen was black. Once, when checking the camera menu it took 15 seconds for the camera information to come up on my screen. P.S. I just tried a firmware update and the loading issue (i.e., 60 seconds to load) continues. Also, not sure if I’m doing the firmware update correctly. The instructions say you should not be connected to your device when doing an update. If you disconnect the ASIAIR, you can’t get to the app. Confused on this. P.P.S. I was, in fact, able to image through the night in spite of the above. Much thanks to anyone who has waded through the above. Joe

Problem solved (I think?) When I saw the scope pointing toward my house this morning at 7:46 AM, I assumed it was ‘frozen’…however from the log file I see that it was still trying to find a guide star, i.e., the scope wasn’t ‘frozen’ it was still tracking!!! (unfortunately, I had disconnected the power before ascertaining this) Guiding failed completely. Whether it was the clouds or my house, no guiding occurred after the second sequence (i.e., “guiding failed” note in logs) and, I assume, the AIR kept trying to acquire a guide star until I found it this morning. Since I’m used to using Plan Mode, I’m used to the ASIAIR powering down after the run. So, my guess is that the AutoRun will continue to run (indefinitely???) until it completes the designated captures…is that correct? If so, then since my AutoRun was not completed the AIR was still trying to complete the schedule. Make sense?

I set up an auto run for each of my LRGB filters. Only the first two sequences were completed. The last two were never initiated. What could cause this to happen? (a power surge??? I'm running this from my home A/C). I'm using a direct Ethernet connection to my ASIAIR Plus. I'm using the AM5 ZWO mount. Note: This morning I see that the scope stayed stuck in the position of the last frame of the 2nd capture, e.g., the mount never finished or parked. It’s still pointed at the last frame of the second AutoRun. Also significant: The last 10 frames before the run stalled showed that second run image began to clip the roof of my house. But why did the tracking stop at this point, which was still about 50+ degrees above the horizon…was it because there were no more stars to guide? Why would the ASIAIR just freeze in this position?

I tried a new cable, no luck. Currently I'm trying to power the AVX separate from the AIR. First try I had one disconnect. However, my second try is still running. I'm going to see if I can leave everything running and then try to image tonight. I'm not optimistic.

Ever since the last firmware update my AVX mount randomly disconnects at various times from the ASIAIR plus. Last night this happened a dozen times before I decided it was time to give up. This is the third time I’ve tried since the update. Totally frustrated! Any suggestions will be greatly appreciated. Has any other AVX user had these issues???

Yes, the mount gets shown initially when I start up, in fact, I can do a preview image, but when I try to do a PA routine I get the error message and the mount has been disconnected. I simply can't just turn on the mount, I have to shut everything down and try again....and again. After 14 tries the other night it worked! Why? How? No idea. But yesterday, same problem, i.e., disconnecting during PA routine. Also, I did see where you can revert back to an earlier firmware but when I tried to do that it only allowed me to update to the new firmware....kind of a loop where I get stuck

Thanks Jim, nice to have support with this problem. As of now, I don't feel it's possible to use my kit. I do love the ASIAIR PLUS, but if I can't use it with my trusty AVX mount, does this mean I'm needing to look at a new mount (ugh). Without the PA routine I'm sunk. [just posted on facebook and sent a bug report through the app] Joe