Q: Why are there a lot of uplink errors in my diagnostics?
Q: Why do I frequently see 12.x.x state code errors?
A: Many things can cause these errors, to include dish alignment and poor cabling, which would require a skilled technician to remedy. However, it’s also possible that a quick inspection of the dish can show where the problem is.
Tree limbs around the dish that appear to be out of the way may actually be reflecting stray signals back onto the dish. These then cause standing waves that the modem interprets as transmission errors.
Generally, the dish should be clear of any foliage within 45 degrees in any direction. Pay particular attention to any branches that may be blowing into that area, which could possibly cause intermittent problems.
In the fall and winter you might also want to inspect the dish to see if there are any fallen leaves or ice stuck to it. These will reduce the reflective nature of the dish, possibly causing additional transmission (and reception) errors.
As well, cables and connections may become brittle or loose with frequent weather changes. So you may also want to see if the connectors are finger-tight and the cabling isn’t cracked or weathered to the point where coax shield wire is showing through.
Some error codes (e.g., 12.1.9) stem from the modem’s sensitivity to power levels. You may want to inspect the routing of the power cable to make sure the DIN plug in the back of the modem is firmly seated, as well as at the wall and at the power brick.
If those are fine, make sure that the modem’s power cord is plugged directly into a wall socket and the wall socket is on a circuit intended for lights. Use on the same circuit as heavy-use items (e.g., air conditioners/heaters, washers/dryers, ovens, etc.) will cause power drops that may contribute to modem errors. Powering the modem though a surge protector may likewise cause power levels to drop and is therefore not recommended, the power brick has built in surge suppression very similar to that of a surge protector.
--------------------------------------------------------------------
Q: I get a Javascript Error when the meter loads
Q: Usage Meter History Display is incorrect.
A: Under some circumstances, the configuration and cached information that the Usage Meter needs to operate gets corrupted.
In the event that this happens:
1. Fully quit the Usage Meter from it’s own menu by clicking on the donut in the menubar and clicking “Quit”.
2. Look for the following directory
Windows: C:\Users\[your User name]\AppData\Roaming\
Mac: /Users/[your User name]/Library/Application Support/
3. Carefully delete just the “HughesNet Usage Meter” directory under that and empty the trash.
4. Restart the Usage Meter. This will regenerate all the underlying information as if it were run for the first time, thus correcting the error.
If you are running under Windows, you may need to enable the Hidden items on the View tab in order to see the AppData\Roaming folder and anything inside inside it, as shown below:
Disregard other recommendations that say to uninstall and reinstall the app and/or update Java as those do absolutely nothing to fix the problem. Uninstalling doesn’t delete the directories above. Likewise, the application is written in JavaScript which is completely separate from Java, which of itself is a stand-alone runtime environment.
The only reason you should possibly uninstall something is if you are not running the current version, have inadvertently deleted part of the application, or have the older “HughesNet Status Meter” still installed. Uninstalling the older Status Meter and using the most recent version of Usage Meter is highly recommended.
