Hughesnet HT2000W
What is the best off the shelf wireless router to buy then using Hughesnet HT2000W router? I would like to replace it with the ORBI wireless cable modem.
Forum Discussion
Just to put a lag time on it, independent of channel speed or frequency :
22,300 mi * 4 legs * sec = 478.843 mSec (minimum)
leg 186,282 mi
[The speed of light is 186,282 mi/sec]
I don't think I have ever seen my average latency being less than 600 ms. Given, I usually test on WiFi, which may contribute to that.
I've got an algorithm to calculate the actual distance between a geosynchronous satellite at lat 0, long y, alt z, and your location at any given lat x', long y', alt z'.
It's almost as complicated as calculating the seven symbols on a stargate.
- There’s an app now that calculates the symbols on stargates.
Given it's around 500, add about 100 to the destination for anything added on the upstream route.
Add at least 200 if your upstream is Level3 going to Microsoft. Level3's connection to MS is abysmal right now.
Eek! It looks like Greek, to me. I'll just stick with my guesses. :)
GabeU wrote:Eek! It looks like Greek, to me. I'll just stick with my guesses. :)
Or you could just use this site: http://www.cosinekitty.com/compass.html
What's neat about that site is that it gives full sighting: azimuth and take off angle.
In real practice I doubt very many people, if any, ever see a latency below about 550ms or so (aside of flukes, of course). The stock info given is vastly simplified, and really only applies if someone lives directly below the satellite, in the middle of the ocean. All of us actually have greater distances from the satellite than listed, and the further north, and the further east or west from the satellite we are, the more time it adds. And, of course, the same goes for our gateway.
And then, of course, there're all of the switches and such that the service goes through, which slows it down even more.
I'm pretty far north on the east coast, and my gateway is pretty far north on the west coast. I'm usually seeing latencies in the mid 600s.
It's funny, but if you ever test your speed with Google's speed test, it evidently only measures the latency between their server and the gateway, so it gives you latencies of about 15ms to 30ms. :p
Here's the process if you want to figure it out:
1. Get your location and the location of your gateway (North lats are positive, West longs are negative).
Location of E19 is at lat 0, lon -97.1071, elev 35786000 m.
2. Convert all the locations from degrees to radians (e.g., φ * pi / 180).
3. Convert all three locations to a point in 3-space:
Earth's radius: Er = √( [ (6378137²*Cos(lat))² + (6356752.3²*Sin(lat))² ] / [ (6378137*Cos(lat))² + (6356752.3*Sin(lat))² ] )
Geocentric Lat: Glat = ArcTan( (1-0.00669437999014)*Tan(lat) )
Point:
x = Er*Cos(lon)*Cos(Glat) + elev*Cos(lat)*Cos(lon)
y = Er*Sin(lon)*Cos(Glat) + elev*Cos(lat)*Sin(lon)
z = Er*Sin(Glat) + elev*Sin(lat)
3. Calculate the path distances in km for each leg by taking the square root of the sum the squares of the differences in each direction and then dividing by 1000:
Dkm = √(Δx² + Δy² + Δz²) / 1000 m/km
4. Calculate the minimum lag time by dividing twice the total path by the speed of light:
Tlag(ms) = 2*(Dkm(dish to sat)+Dkm(sat to gateway)) / 299.7924 km/ms
Turns out the lag for me in C.Virginia to E-19, and San Diego and back is 500.54ms.
MarkJFine wrote:
GabeU wrote:Eek! It looks like Greek, to me. I'll just stick with my guesses. :)
Or you could just use this site: http://www.cosinekitty.com/compass.html
Good site. Thanks!
Sat to home = 23,585 miles = 0.127 seconds x 2 = .254 seconds.
Sat to gateway = 23,794 miles = 0.128 seconds x 2 = .256 seconds.
So, the latency for me that is due solely to distance is .510 seconds.
