Thanks guys,
These are valid issues, and it makes sense to ask the manufacturer to have them fixed. Unfortunately, I don't have OpenBox at the moment to look through setup screens, but remember guys in the past did some testing and composed a good
list of suggestions to fix Sathawk's firmware. I wonder, if someone can confirm, to what extent these suggestions are now implemented in Sathawk and OpenBox FWs? Anyone tried to install Sathawk's FW on OpenBox?
Chapelrun
Can you post pics of these 2 more screens, you have to drill down to get to Goto X screen? Does it have Goto 0 function and East & West Limits - did you try to change them? Talking of 15W, what are your Geo coords, and on what screen do you enter them in OpenBox? What happens, when you click East or West buttons on Goto X screen: do you have to click them again to stop the motor? It looks like this STB uses traditional USALS control: "store one sat position accurately - get them all via USALS" by changing channels.
One may wonder, why motor and DiSEqC switch control are weak in some STBs. This is not a matter of philosophy, other factors are in play, such as lack of coder experience, high coders workload, different production priorities based on markets demand, insufficient STB model memory for larger Setup UI, and lack of testing equipment and access to sat signals available in sales regions. For example, a smaller CN STB maker would usually test DiSEqC signals output of a STB by using a Scope, but not actual motor and various switches. Why - they don't have a motorized and complex switch matrix dish setup at their factory...because cutting costs of their R&D and production allows to offer lower wholesale prices. Now imaging a coder guy, who never had a motorized dish setup at home, and doesn't have a chance to play with it at work. He needs pretty wild imagination to get it right, despite looking at popular STB Setup examples.
That's why suggestions of experienced users from different Continents like Ice, JimS and Lak7 posted are
invaluable for them, if they reach the factory.
Speaking of coder challenges... Different motor makes and models have different Step-to-Angle ratio. How Sonicview 8000HD combats that? From what I read, the FW allows a user to position a motor via USALS at Setup, then fine tune the position in "abstract" STB angular steps, and once you click SAVE, the motor position is saved in STB in a number of "abstract" steps from motor "0". Next time you switch a channel, the motor is turned by a DiSEqC 1.2 command instead of USALS, which is used only at Setup. So the whole thing is a bit less straightforward than it looks like - to ensure repeatable positioning accuracy, since some motor models tend to accumulate USALS positioning errors over time.