@MSmith wrote:
I've seen in this string a post by CORROSIVE. He brings up our fault code 12.7.1 as usually meaning the weather had a role to play. With respect,(because I'm the dumb one in this mix) I agree that the weather can cause problems. But, I've had my system for seven years and I've NEVER seen this before. If it is the weather, then, all of a sudden, every day, several times a day, for the past thirty days the weather has gotten ugly for very brief periods of time! I'm not buying it.
Weather at the users location isn't the only weather that matters, your signal comes down in an entirely different location in the country, and weather there can also cause 12.7.1 and 12.1.9 to occur. That aside, as I also stated, many things can cause those errors, it would require all posters in this thread essentially being on the exact same beam, which is unlikely as there appears for be 4 or so beams for Illinois.
A more likely scenario as to why that installer is suddenly replacing so many transmitters? There may be issues with them after so many years, and with the bulk of consumers signing up as soon as Jupiter One went online, a sudden spike in lets say, a potentially bad batch of transmitters that may have been made, being replaced may not be out of the question. But that is a potential scenario, not saying it has occured, but there are times in production when a bad batch of anything can make it out the doors, for anyone.
I have also had installers talk to me about things before, "yeup, seeing a lot of X Y and Z lately" but at the same time I have learned to ignore them because they are trained to install and service the equipment and that's it. They don't have diagnostic information, failure rates, or anything else to base claims off of. This goes for more than Hughesnet, it extends into all fields from HVAC contractors to Satellite installers. They may have had a bad rash with something because of 10 bad units and suddenly, "it's the manufactures fault, they are horrible", when they happened to get 10 units that was in the same package and the package potentially mishandled and damaged the units internally.
Just because you had never seen 12.7.1 in seven years during incliment weather, doesn't mean the error never occured before either.
All of that aside, let Liz and the engineers take a look and figure things out, but it may take time to find and fix the issue, and even more time if it is in fact a widespread issue.
Don't hesitate to post back in the community about your Gen 5 experience, and let us know if you have any other concerns.
