I have seen you post some concerns several times relating to your error codes and I would like to try and address that to some degree.
The Hughes modem is constantly recording data about itself and its connection to the Gateway .... and I do mean constantly.
Most of those "errors" are really more of a CONDITION REPORT than a true "error" and a closer inspection will reveal in most cases that the reported condition was very brief .... transitory in nature.
As an example here are mine from today:
Not every "error" is an error unto itself but is only a subcategory of another.
Not all of the "errors" (I prefer the word condition) are ...... fatal errors
Lets look at the one I highlighted ... 13.1.1
That error means that the Modem recorded a condition of not having anything plugged into the LAN port ... this has occurred 1 time, lasting for a total of 11 seconds and occurred between the specified dates.
Now that error in and of itself means nothing .... I didn't even notice it. It is a DATUM of sorts if the condition were to start occurring more frequently and for longer periods. It COULD be a sign of a bad LAN cable, a router (in my case) going bad or it could be the beginning of a Modem problem. But at this point it is nothing more than a report of a transitory condition.
For the everyday user there simply isn't a lot of use for the State Code Monitor unless the condition is persistent.
I wouldn't spend a lot of time and energy on that part.
There however a couple of pages of info that will benefit the average user.
Whenever a user encounters an issue with their connection the very first thing they should do is go to the modems main SCC page at 192.168.0.1
Just a quick peek at the color of the System Status icon will tell if the system is "up" or not.
Any color other than green is cause to look a little further.
FAP is pretty obvious as to cause...
Yellow or red we need to click on the System Status link and get more info:
Here we are interested in two things ...
Your signal strength and the location of your Gateway.
If your signal strength is low ... we need to find out why ....
It is possible for the sig to be right on the edge of "cut-off" where the connection will flicker on and off.
What are the weather conditions at the users location ?
Is LOS being obstructed by trees ?, snow/ice build up on the dish ?
If things are OK at the users location then we have to consider weather conditions at the users assigned Gateway location.
That can be determined from the first three letter noted above. The "FLG" in mine indicates that my Gateway is in Flagstaff AZ. It is entirely possible for me to be having sunshine and blue sky's here in west Michigan but terrible weather at the Gateway location affecting the ability of the Gateway to communicate with the satellite.
One error condition that happens occasionally is a "yellow" on the Status icon and a 30.1.1 state code. Doing a MBX Reset will force a reconnection to the W/A server and clear the condition and restore full connectivity.
As to your data loss issues, you really can't at this point at least directly compare your issue with Larry's.
The best way to proceed is to simply post a screenshot of your remaining allowance along with the time of shutdown and LAN cable disconnect and another of your remaining balance and time of reconnect.
The Hughes Mods will then take it from there.
If there is usage during the time of disconnect it is on the Hughes end.
Don, a failing radio would show as a high retransmission rate when remote diagnostics are ran, also it would show as a major change in the ratio of download/upload. I thing remote diags where run 4 days ago.
One thing I question is: With a loose coax, did the tech apply/reapply dialectic grease to prevent moisture penetration/condensation issues when he tightened it ?