I've seen it brought up a few times now from folks who just got their MicroHD and it has to do with the "moving dish" popup on the screen. Folks have reported it as a bug or a feature change
I noted it right away when I got mine in the review and Brian did respond at the time. Here is that snippet
One thing that really bugs me is there is a "moving dish" popup that shows up no matter what you do. I know some receivers have it but most that popup leaves right away. This stays up for 15 seconds unless you hit "exit" before that. This shows up if you go into the transponder list and antenna setup. I understand if you are going from say 83W to 91W but why when you are on 91W already and you want to blind scan it does that popup when you hit OK to scan? The only time it is rather quick is when you power it on for the first time. It only shows up for about 2 seconds. I know my Coolsat 5000 only does it for a couple seconds but I’m still using version 1.00 software. Anything else (including the factory 3rd party stuff) has that popup too for longer.
This is what SatelliteAv sent back to me about it
"Dish Moving" - It also drives me nuts! We are working on this irritant so the display will leave after 3 or 4 seconds, but their are other functions hard coded by ALI that is making this very difficult. If the display is programmed to disappear earlier, there is currently no way to prevent he next step of the process from starting. There are no time place holders without the display. The result is if the display is removed early, the next event step starts. What happens for example is that if in a scan mode, the scan is initiated prior to the dish landing on the target satellite. I have been playing with displaying a blank screen, but this can confuse the user as you still must either press exit to skip to the next step or wait. If the user does not visually see that a motor move event command is still waiting to time out, the RCU would not function until the exit button was pressed or the event times out. It is totally a ALI coding issue that we are fighting a work around
The easiest fix right now it to hit "exit" when it pops up. The motor still will move properly
I noted it right away when I got mine in the review and Brian did respond at the time. Here is that snippet
One thing that really bugs me is there is a "moving dish" popup that shows up no matter what you do. I know some receivers have it but most that popup leaves right away. This stays up for 15 seconds unless you hit "exit" before that. This shows up if you go into the transponder list and antenna setup. I understand if you are going from say 83W to 91W but why when you are on 91W already and you want to blind scan it does that popup when you hit OK to scan? The only time it is rather quick is when you power it on for the first time. It only shows up for about 2 seconds. I know my Coolsat 5000 only does it for a couple seconds but I’m still using version 1.00 software. Anything else (including the factory 3rd party stuff) has that popup too for longer.
This is what SatelliteAv sent back to me about it
"Dish Moving" - It also drives me nuts! We are working on this irritant so the display will leave after 3 or 4 seconds, but their are other functions hard coded by ALI that is making this very difficult. If the display is programmed to disappear earlier, there is currently no way to prevent he next step of the process from starting. There are no time place holders without the display. The result is if the display is removed early, the next event step starts. What happens for example is that if in a scan mode, the scan is initiated prior to the dish landing on the target satellite. I have been playing with displaying a blank screen, but this can confuse the user as you still must either press exit to skip to the next step or wait. If the user does not visually see that a motor move event command is still waiting to time out, the RCU would not function until the exit button was pressed or the event times out. It is totally a ALI coding issue that we are fighting a work around
The easiest fix right now it to hit "exit" when it pops up. The motor still will move properly