Here's Friday night at the draggy race.
My internet was still great at 6:30 PM. I was gonna set up a routine as soon as I saw speeds beginning to drop. I don't know when it started tanking tonight because I got called out to remove a cottonmouth moccasin from a pumphouse so I was away for a while.
When I got back around to my computer, I got the 463 kbps reading. At that point I bypassed the router and set up an auto-test routine of every 10 minutes for two hours. I let testmy choose the default file size. If I specified 12 MB, it probably would have been non-stop download test for two hours.
For orientation, you'll first see the 8.65 Mbps test from Thursday night that I mentioned above. Then you'll see a 19.12 Mbps test from 6:30 PM. Then you see it has hit the wall by 8:30 PM.
I'll also attach some corresponding Hughes tests from Thursday and Friday.
Just for fun, I'll leave my computer connected to the modem and set up an hourly routine to run all night.
They are a fragile lot.The poor folks. LMAO.
In a couple of your posts you indicated that your modem was prone to rebooting if the modem was ... touched or the LAN cable fiddled with.
This really isn't normal.
Items to check:
> Is the DIN connector from the power supply to the modem FULLY inserted ?<
It has been my experience that the plug goes in further than expected and needs a FIRM push to seat it fully.
> Is the coax (both cables on 9000 modem) firmly tightened ?<
> Does the LAN cable and LAN socket of the modem appear to be in good condition and the RJ-45 connector seats firmly and with a positive "snap"?<
Years ago there was a production run of HN9000 modems that had a flakey modem socket and connection to the Modems mainboard that cause all kinds of issues.
> Does doing any bending right at the end of either the coax, DIN connector or Ethernet cable cause any symptoms?<
I'm thinking along the lines of a strain being placed on a connector from the weight of the cabling.
> You stated in one post that even "touching" the modem may cause a reboot.<
I'm thinking static discharge. Is the AC receptacle that the modem is plugged into a properly wired three prong, three wire grounded system ?
Do you know for a fact that the reflector.TRIA body and the modem are all tied to the same common ground point ?
I think there was something hokey about the power connection. It sits on top of an APC UPS in between outlet rows and is powered by the battery side. Since I have other things also plugged into the UPS, I goof with them on occasion. I've made the modem reboot by leaning it to the side to unplug/replug a printer and the cooling fan for the modem and also swapping LAN cables. After pulling and reseating the power supply plug, it seems to be doing better.
I've also moved my router very close to the modem with a short cable rather than having it up high and 6' away with a longer cable so maybe that had something to do with it too.
Third thing I found is my coax was a quarter turn loose. It's probably been that way since the coax/grounding block was changed out last year which is what eventually solved the persistent SQF 15 error I was experiencing for so long. In fact, I don't think I've ever had to disconnect coax and/or power since that was done. Doing the cable dance by disconnecting both used to be the only way to recover from the SQF 15 error.
I know for a fact everything is grounded properly. When I got my original Gen4 install, I had a real pi***** match with the installation company who (twice) refused to ground it to Hughes specs. Of course, I wasn't allowed by Hughes to do it myself so this required a completely different service company to come out and complete the work.
A couple of thoughts on your modem placement and power connection.
How good is the airflow to the modem ? They generate some heat and that needs to be carried away. Is it in a place where you can see the modems front panel LED's ?
If a overtemp occurs the power LED will turn red prior to doing a shutdown.
As to being on the battery side of the UPS ...
That is likely to isolate the modem grounding wise. The ODU and Modem need to be at same grounding point.
Also, UPS's (except for very expensive models) put out a modified sine wave.
It is possible that the modem isn't liking the "flavor" of its input voltage both in waveform and perhaps current at a given instant.
The speeds held up reasonably well for a Saturday but started crashing after 6. I set up another auto testing routine beginning at 7 PM to run on 15 minute intervals throughout the primetime period. I set it to allow testmy to choose it's own file size and wired direct from my main computer to the modem.
As usual, the first test shown in the series is the last test shown in the previous series.
Will run an hourly test overnight again.
Here ya go Liz. Since Friday night, I've built you a very comprehensive picture of what it looks like to be a HughesNet customer who does weekends on Beam 55/Rapid City. It makes using the internet like watching paint dry.
For the Sunday night grand finalé, I did use the commonly requested 12 MB tests. Like all of the "primetime" tests done for you this weekend, this series ran with my main computer wired directly to the modem.
All through the weekend, every time I looked at my SQF I had 125-130. They can't blame it on bad signal or bad weather.
All tests except for the long duration hourlies were run while connected directly to the modem. Look through the results and you'll see they can't blame it on my network, whether I use it or not.
Notice the speed range over the course of the weekend. From a low of 79 kbps to a high of 24.36 Mbps. They can't blame it on anything on my side of the modem. It's all Hughes.
An 8 PM 164 kbps Hughes test concurs with the immediately previous testmy result of 166 kbps. They can't blame it on testmy.
This screenshot is a 14 minute segment of that 79 kbps download test. Note the few peaks above 200 kbps and also note the complete halts in transfer.
I hope there's a solution. The only one I can think of is prohibiting HughesNet sales from selling something they don't have. You can't balance a load that commonly drags down to such low speeds. It's like trying to pour a 50 pound bucket of ummm, fertilizer into a beer bottles without a funnel. It just doesn't work.
Something that may help in the near term is simply letting anyone and everyone who complains about low speeds out of their contract immediately. Refund with apologies. This should start freeing up some bandwidth quickly.
The HughesNet Community is here for you
to find answers and ask fellow HughesNet
subscribers for help. This is a great
opportunity to discuss and share your
expertise to enhance your HughesNet
experience and that of fellow subscribers.
Visit the About the Community board for
information on how to get started with using