• Guiding Graph

Hello Chen, Ahh Patents! for a long time we viewed Patents as a double edged sword. A lot of in house engineering innovation was necessary to create the kinds of high speed automation capabilities necessary to produce our products to the extreme quality requirements we demanded. In the final analysis we viewed a lot of that as very valuable trade secrets. In many cases we had to take off the shelve equipment and re engineer it well beyond the capabilities of the original mechanism or sensor. We often had to re imagining how to use something that was designed to do a certain function, to be able to do something very different Think of it like re engineering my Ioptron CEM25ec and in the process give it the abilities of an 10 Micron Mount while outwardly nothing has changed.
So thus comes the Patent conundrum. Since you hold so many yourself I am sure you know exactly what I am speaking about. We did tend to more often patent certain things about our products more than or manufacturing processes. Essentially because reverse engineering a product is pretty straight forward and thus finding ways to circumvent patents easier than figuring out the secrets involved in putting together millions of our product each day with zero defect with nothing to hold in your hand or a patent you could read to find out. But if we could at least write the patents broadly enough and still get that patent issued it was worth doing.
I could tour you through one of our facilities to show you how we accomplished the almost impossible, as well as point out countless amazing trade secrets but then I would have to kill you as a result. Since we wouldn't want to deprive these forums of your amazing expertise I suggest for the sake of science we dismiss the tour idea :-)))))))
BTW I learned this lesson the hard way as a young engineer very early in my career. I was showing a vendor through one of our manufacturing areas and proudly showed off to him how I had designed an addition to his product that gave it a completely new function they never considered....... Shortly after they introduced an entirely new product completely based on my unpatented design. To this day that one hurts!!! But it was a great lesson at an early age.

Anyway, back to the PA issue I believe once again you will be proven correct. By not using the auto refresh during PA both the accuracy as well as time involved to PA will be improved. I suppose another simple improvement ZWO could add would be the ability to set some N number as you mention to refresh to. But they have enough to already work on just getting a few other things right and there already exists a very effective solution :-))

BTW This morning I was able to upload the FW update for my 120mini guide camera but sadly a look out the window right now is not looking at all encouraging for tonight. It was supposed to be partly cloudy. But right now that is not the case. Last forecast still says it will be, so I have my fingers crossed Al

    Byrdsfan1948 I suppose another simple improvement ZWO could add would be the ability to set some N number as you mention to refresh to.

    My guess is that the ASIAIR could keep on taking plates and display a "wait" notification until two successive plates give the same result to say, within 5 arc seconds. Problem is the cheap mounts might take literally minutes to settle to that amount :-).

    Too bad you have already applied the firmware update, else I would have requested that you save a PHD2 log before and another PHD2 log after the update, to see if anything changed. In a different thread last week, I had mentioned the jitter and lag of the guide sampling timestamps in PHD2 log.

    However, perhaps you can check your USB drive (Udisk on the ASIAIR Samba server) or the microSD disk (Disk on Samba) for old logs and squirrel them away, and note the date and time you had applied to update so there is something to compare in the future.

    Chen

    Chen

    Byrdsfan1948 BTW This morning I was able to upload the FW update for my 120mini guide camera

    Sorry to butt in here, I’m considering updating the firmware on my 120mm mini also. Can you tell me if you installed the .img file in the USB3 folder ? The instructions are a little confusing to me.

    Ron

    Certainly not butting in here at all Ron. I saw someplace else recently the same question you are asking here. The response from ZWO was to use the img file. Which is what I did yesterday. I'll see if I can find that response and if I do, I'll try to post it here.

    Just wondering what if any issues are you having with your 120mm mini? I'm just wondering if you are having any, if they match mine? I've watched my guide star just disappear, ( in perfect seeing conditions ) the image screen break up, the star being lost etc. An assortment of issues that once they start, often times making guiding totally impossible.
    Lastly I want to make clear I am no computer expert so while I'm am fairly certain I did this update correctly I can't say with certainty that I have. I probably won't know until I get a chance to test it, the next even somewhat clear night. Which here in New England does not look like any time soon.


    To do the update all I did was to connect my 120mm mini via it's USB cable to my windows computer. I opened the USB3 folder mention and the camera was immediately recognized. When I hit update ( or whatever that button is ) it appeared that the update only took a second or two. I then got a message that it had been successfully installed. BUT as I said until I can test it I won't be 100% sure. Nor of course will I have any idea if it even helps with my above mentioned problems.
    I was able this morning quickly able to at point 120mm mini and guide scope out the window at some stars and confirm that it still works after this update. So at least I know at this point I didn't break it :-)) Good Luck!! Al

    • RonM replied to this.

      "However, perhaps you can check your USB drive (Udisk on the ASIAIR Samba server) or the microSD disk (Disk on Samba) for old logs and squirrel them away, and note the date and time you had applied to update so there is something to compare in the future."

      Hello Chen, I would be very happy to try that if you wouldn't mind telling me how???? :-))) You are asking me to do something currently beyond my computer skill levels........... :-)) Al

      • w7ay replied to this.

        Byrdsfan1948

        I can’t seem to get consistent guiding on the same target each night. Sometimes it’s the RA axis that’s off (high RMS error) other times it’s the DEC axis. I have yet to get a total RMS below 3.00. Also it was taking a long time to calibrate. I also noticed a line in all my guiding logs that says “Settling Failed “.

        I’m not sure the problem is the guide camera and will wait to update the firmware. I spent more $ on my mount to get the EC version to speed up imaging without guiding and I’ve taken 4min exp/ 30 frames with good results, at least to me anyway. I started using guiding to take longer exposures that’s when all this started.

        A couple times I did seem to have trouble locking on a star. I’ve since added a red filter on the guiding camera and am not having that problem now. I have pictures of my last 3 guiding graphs and can post them if I can figure out how to do it.

        Ron

        Byrdsfan1948 Hello Chen, I would be very happy to try that if you wouldn't mind telling me how???? :-)))

        Do a Google search on how to access a Samba server with your computer.

        On macOS and Linux, it is simply a matter of using the network to connect to smb://192.168.1.123 (the actual IP address is what your router has assigned to the ASIAIR). Raspbian (the OS that ASIAIR uses) has a built in Samba file server.

        You can use the GUI in macOS by selecting the Go item in the Main Menu of the Finder and choose "Connect to Server...". Then simply type in the address as above (the "smb" identifies the type of server), or let the Go dialog browse for all connected file servers on your home network. The ASIAIR will be one of them.

        While you are at it, go to your router and change the ASIAIR DHCP address to a fixed, reserved address. This way, each time you try to access the ASIAIR on your network in the future, it will be available at the same fixed address.

        Furthermore, in the ASIAIR network setup window, you can give your ASIAIR a distinct name (in case you have more than one; or you take the ASIAIR out to a remote site that has other people using ASIAIR). My four ASIAIR (two v1, and two current models) each have its own name and fixed address at home. If you don't do that, the ASIAIR will append part of its serial number to the string "ASIAIR_" and use that as the device's name -- which makes it difficult to figure out which is which.

        When you open the network volume, you log in as guest. You will see two items, one is "Disk" (the microSD card) and the other is named Udisk (for USB flash card or SSD). Pick the one that you were using in ASIAIR while autoguiding and you should find the PHD2 logs in there (the logs disappeared between ASIAIR v1.5 and v1.5.3, but is back).

        Chen

        Thanks Chen, I give this a try but no guarantees :-) Al

        Hello Chen it's been a few cloudy nights here, until a few hours of clearer skies early last night, and this morning. Hopefully maybe a couple of hours tonight as well before our next storm rolls in.
        I didn't want to risk anything after I did the ASI120mm mini FW upgrade so I have not tried your PHD2 log suggestion above here. I wanted to be sure I would not put myself out of business before I tried out that upgrade. Well now I have a few hours of experience after that upgrade to report on.

        The bottom line so far is....... Still very unstable and very problematic guiding. So here are a few details. First of all I used my Iphone 12 to do my PA with and got to under 0.30 Arc Secs fairly quickly. What is interesting is that once I hit finished, I got that fireworks display. I never had gotten that before on my Samsung tablet. Not that I am enamored by that display, but I do find it worth mentioning that for whatever reason it does not happen on my Samsung tablet. Also another very minor difference. When finishing the auto centering after slewing to an object, my tablet says "Finished", my IPhone says "Confirmed". Perhaps why the difference makes some sense to you?

        As far as the guiding. At first it was a total mess. Actually I was not even able to do a calibration. At times it seemed that the camera just stopped taking pictures and would just do totally black. I had instances of Star Lost as well as what appears to be the mount slewing looking for a star. Sometimes it would re find the star and resume guiding other time not. Eventually things seemed to settled down and I was able to star guiding but I'm unsure if the calibration sequence was every totally completed. Once guiding I started my auto sequence. Since I was just testing, I set up a simple sequence of 40, 60 sec subs on M-13. I dithered every other sub. What I soon learned was the dithering really screwed up the guiding until the point where eventually I had to stop it. The subs looked OK but the total error was all over the place. I'm assuming that the frequent dithering probably resulted in guiding number that are not reflective of the actually guiding tightness. After about 20 subs I paused the Autorun, and stopped the dithering, I resumed the Autorun and for the next 19 subs had guiding results often under 0.65 error. I had also increased my camera gain to 50. During the 20th sub the guiding just stopped again.
        I also noticed that when I tried to slew to M-81 my tablet said it was below the horizon. But in fact it was very high in the sky. On the Go To page it did appear to show as to be below the horizon. Which was wrong! I decided to restart my tablet and it showed properly and I was then able to slew to it. Something is very weird there.
        With all the issues I'm mentioning here do you think it might be a reasonable idea for me to delete the ASIair APP and then reload it? Or do you think perhaps my ASIair OS might be corrupted? I did make a back up when I got my ASIair new and I do know it was done properly. Should I give those ideas a try? Al

        • RonM replied to this.

          Byrdsfan1948 I have the same mount as you and this might be a long shot but did you set the guiding to “Allow RA guiding” in the hand controller settings. It’s on page 30 in the instructions.

          Hi Ron, Thanks for the suggestion. To answer your question, YES that is set to "allow RA guiding". Which as the instructions say would allow input corrections from the ASIAir Pro. Also on page 28 the instructions discuss setting the guide rates for RA and DEC. In my case I have them both set to 50% of the sidereal rate. I am using a WO GT71 with a .8 reducer so my effective FL is about 340mm. With that FL I am finding that the Ioptron CEM25ec does an excellent tracking job for me even without auto guiding. However with the ASIair I really need to guide in order to be able to dither. I would think that since I can get some very excellent guiding as I did for a while last night that my problem is not with the mount. What is your experience? Al

          • w7ay replied to this.

            Byrdsfan1948

            Al, if you are constantly losing stars, see if you can attain a better focus. Then set the gain so that the intensity of the star profile in the upper left corner is between 150 and 250. Don’t let it flat top (255) since the centroid will jump around when it goes through various degrees of saturation. If the intensity jumps around by more than a factor of 2, you probably have thin clouds.

            However, I suspect that there is somthing fundamentally wrong with ASIAIR. ZWO is barely passed the first step of the alcoholic anonymous seven step scale, so perhaps they will finally be looking for a bug.

            In the meantime try the real PHD2, and you will discover that your mount probably autoguides fine.

            Chen

            Hi Chen I've missed our daily exchanges. Good to hear from you... I've reached the same conclusion. There is a fundamental flaw here that is not being addressed, or at best, not being properly resolved. YES!! First of all I did spend a fair amount of time last night dialing back in my guide camera focus because I had, had, to remover it to to the FW update. I also made changes to my gain last night as you suggest. For exactly the reasons you suggest.

            Yeah thin high clouds. That right now looks like that maybe my issue tonight if I even get a few hours to experiment. There has to be a bug, or two, or three, here !!! I was getting better MUCH BETTER guiding with exactly the same equipment when I first started using guiding back in FW 1.5 than I am now 4 months latter.

            I don't know what the problem at ZWO maybe, but clearly they seem to be very unconcerned about this obvious problem. I just finished watching a video on You Tube about setting up the old fashioned Windows lap top control platform including PHD2. I am one more bad night of guiding problems away from pulling the trigger. Honestly if I was the SVP at ZWO I'd fired everyone, and hire YOU!!!! Al

            • w7ay replied to this.

              Byrdsfan1948

              Sorry for the curt messages. Comcast has been out for two days now, and I am trying to type into my cellular connected iPad. I am ready to connect a real keyboard to it!

              We had a snow and ice storm in PDX with over a quarter million homes out of power in our small state. Probably over 100k still. We lost power for a while, probaby to restore power to a nearby line. But cable TV and iinternet has been out for two days now. Too many trees and tree huggers not willing to cut them down :-)

              Chen

              Chen, WOW sorry to hear about that power outage. Same story in Texas I guess. HAHA yes I know about the frustrations of trying to type, using the screen of a tablet, or Iphone as your keyboard !!

              Anyway I'll post my experience of last night here for you to consider, and I'll wait to hear back when your better able to respond.

              We had a few hours of reasonably clear sky last night before the clouds ahead of today's latest snow storm ended the night. It was certainly a night of very contrasting guiding experiences. I again used my Iphone to do my PA and quickly got to 30 arc seconds, and the simile face and the fireworks display. I again only mention that as a very obvious difference to my Samsung Galaxy 10 Tablet where I have never gotten that display even when my PA was far better.

              Once I was PA'd and done a sync to mount, I switched back to my tablet, because of the much bigger screen size. I slewed to M-42 simply because it is currently perfectly located from where I can locate my scope due to the snow. The mount found it, and centered it perfectly. I then set up a test Autorun sequence. Last step was to calibrate a guide star then hopefully start guiding and imaging. I was able to calibrate and get the sequence started but then immediately ran into the same guiding problems as I have been having. Lost star, huge swings in RA and DEC, etc. A total mess. I tried tweaking ( lowering ) the aggressiveness setting which were both set to 55. I ended up with the DEC at 40 and the RA at 35. But still that made no difference. Essentially I was unable to guide. So I shut down the Samsung and tried switching to my Iphone.

              BINGO! Immediately there was a HUGE difference. I was able to start the guiding, and it stayed reasonably stable. I then added a dither every 5 shots and started another Autorun sequence. I was able to run two sequences targeting different objects in different parts of the sky. The bottom line was that the total guiding error stayed mostly between 1.00" and 2.00" . It would vary up to around 4" after a dither, but then fairly quickly settle back down to the 1" - 2" range within 30 seconds or so. It often was slightly below 1.00 as well.............. Now I know that for you, these are not great guiding numbers. But for me, with all the problems I've been having they are outstanding. My RA fluctuations were typically very tight around the 0 line of the graph with most of the error coming from the DEC adjustments. Lastly I even set up a third short sequence that required a Meridian Flip. Everything went perfectly. After the flip the ASIair found a new guide star, I believe re calibrated, and in a few minutes started guiding and then continuing with the imaging.

              OK so what's the difference? The only thing I changed here was moving from my Samsung Tablet to my IPhone12. I know your going to say that should not make any difference, but I am seeing a huge difference, and now for the second time!! The fact the the Tablet does not show the Fireworks PA display which initially to me was only worth a comment, is now is suggesting to me that there clearly is some difference here. I checked to make sure both the tablet and Iphone show the same FW and they do, 1.5.3............ It seems that the upgrade to the ASI120mm mini FW I did a few days ago at least has not put me out of business. However I am not at all sure if it has helped at all however.

              OK so does any of this make any sense to you? My thought is to uninstall the ASIair app on my Tablet and then re install it. But I am just shooting in the dark.......... Since the next few days will be snow filled I won't get another imaging chance until the week end, so I will wait to hear from you before I do anything else Good luck with your weather related issues out your way And of course good luck to our latest Mars Rover as if goes through it's 7 minutes of terror about 3:45 PM my time today Al

              • w7ay replied to this.

                Byrdsfan1948 BINGO! Immediately there was a HUGE difference.

                This is really weird.

                We are told that everything is being done inside the Raspberry Pi and the tablet simply displays the results and provides GUI.

                It is just possible that the firmware payload (that gets uploaded to ASIAIR from the tablet) is different. But you did not mention that your iPhone had downloaded any new firmware.

                The only thing I can think of is that the Raspberry Pi is spending more process cycles servicing the app when the app is running Samsung's version of Android. I had a while back suggested to ZWO that they check their process priorities to make sure the guide camera and the autoguiding process have the highest thread/process priority in the system.

                I will forward your note to my contacts at ZWO and let them scratch their heads as to what the root cause can be, and this may lead finally to the ASIAIR autoguiding bug (relative to PHD2). There may still be on their Lunar New Year ("Spring Festival"). (Yeah, I know, it is still dead in Winter here :-).

                Thanks for your observation, Al (it takes an engineer, eh?). You might be the savior of what people are seeing! :-)

                Chen

                P.S. Comcast restored. Any typo is caused by my fat fingers and incompetence.

                Chen I did not see anything from you in my spam folder. But I did send you an e-mail as you suggested above here. Let me know if you got it. Al PS no worry, no typos!!! I'm the king of typos!!!

                • w7ay replied to this.