I sit here in Little Rock running along just fine until around 10:30A local time. Then, my link drops. Is it just me or did atContact on 123W just go down?
We had rain / thunder last night. I stowed the dish last night to avoid the wind/storm. Then, the temps dropped from mid-60's to upper 20's. This morning at 7:30A local, did the search routine and came back online. Since then, I've been hearing ice fall on the roof of the rig.
Around 10:30A local, the link went down with signal strength around 60 (.98M dish/6W BUC). I did another search and it re-found the satellite but, won't come online.
So, it looks like the satellite/NOC is having issues to me. Anyone else?
Thanks,
tom
-------------------- F2/6W | D3 3.9.6V | iDirect | 123W | AtContact 768/384 | Vonage VOIP | AT&T Software VPN | Kyocera KR2 | DA4000SBR - 50U Digital Antenna | Our location and our story Posts: 173 | From: On the road, exploring the US & Canada | Registered: Oct 2007
| IP: Logged |
posted
Michael, Not sure about the location of the @contact Hub (NOC as you refer to it).
If Tx and Rx are illuminated it means your system has its FSD (frame start delay) and is trying to burst into the hub...meaning Lband is exiting the IF port on the back of the modem.
Problem could be a multitude of things. Bad Buc, bad tx cable, or even a problem at the Hub. That is why I asked if more than one customers was down. If there are multiple customers down, then the problem is obviously at the earthstation hub.
-------------------- Mike Posts: 567 | From: North Carolina | Registered: May 2007
| IP: Logged |
posted
The NOC/Teleport/Hub/Spaceport (depending on your upbringing!) for atContact is in Sedalia Colorado, just southwest of Denver. There has been snow, but that rarely causes problems(uplink to G18 with a 9 meter dish). I just checked and the link is running fine on my 1.2 meter/4 watt setup on G18 with them (1024 x 256 circuit): Last Result: Download Speed: 1031 kbps (128.9 KB/sec transfer rate) Upload Speed: 158 kbps (19.8 KB/sec transfer rate) Ping statistics for 209.191.93.52: Packets: Sent = 24, Received = 24, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 547ms, Maximum = 583ms, Average = 562ms
[ December 04, 2008, 07:07 PM: Message edited by: Randy VSAT U.S. ]
-------------------- Randy Scott | www.vsatus.com 1.2M | 4W | 123W- atContact 20:1 | iDirect 3100 |TrailManor 2720SL | Winegard Traveler HD | Posts: 606 | From: Monument, CO | Registered: Mar 2005
| IP: Logged |
posted
If it is isolated to a single customer, and that customer is reporting GREEN TX and RX LEDs on the iDirect unit, then the uplink cabling, connectors, and potentially the BUC are suspect/questionable. That, or his INITIAL power needs to be adjusted in his options file to add a few more dB of power.
How does that happen? Answer is simple. Weather or cloud attentuation can be a factor or quite possibly another user of your transponder. Often there are ocassional-use customers that put up LARGE carriers on the same transponder (that the little guys operate on) and it raises/elevates the noise floor....which means the "old tx power" may not longer get the job done (over that noise). Read: the options file's "inital tx power" is no longer enough power to close the link and meet the Hubs UCP - read: the nodes bursts are arriving way below the low end (course adjusts) of the UCP.
So, long/short check the BUC and cabling...and ask the hub to add some power.
You can add that power yourself if your options file has any additional tx margin, but I know the providers are not warm to me telling you to do something like that. If you have a couple dB of power before you achieve the point of BUC saturation (as determined by a 1dB compression point) you can add a couple dBs from the command line in telnet. Once in the network, the NMS will ultimately reel you back in to the configured UCP sweet spot (normally 9dB c/n). Too easy.
posted
There may be confusion in this thread, because the topic starter has not returned, and the report of green RX/TX came from another user who is without trouble. We don't know what lights were illuminated on the modem of the original poster.
posted
I kinda figured that Don, but I figured Tom would stumple back to this thread and have something to go one. I am thinking he has something going on locally on his system. If Randy is running fine, that is more than likely the case...
-------------------- Mike Posts: 567 | From: North Carolina | Registered: May 2007
| IP: Logged |
quote:Originally posted by TDMAMike: If it is isolated to a single customer, and that customer is reporting GREEN TX and RX LEDs on the iDirect unit, then the uplink cabling, connectors, and potentially the BUC are suspect/questionable. That, or his INITIAL power needs to be adjusted in his options file to add a few more dB of power.
How does that happen? Answer is simple. Weather or cloud attentuation can be a factor or quite possibly another user of your transponder. Often there are ocassional-use customers that put up LARGE carriers on the same transponder (that the little guys operate on) and it raises/elevates the noise floor....which means the "old tx power" may not longer get the job done (over that noise). Read: the options file's "inital tx power" is no longer enough power to close the link and meet the Hubs UCP - read: the nodes bursts are arriving way below the low end (course adjusts) of the UCP.
So, long/short check the BUC and cabling...and ask the hub to add some power.
You can add that power yourself if your options file has any additional tx margin, but I know the providers are not warm to me telling you to do something like that. If you have a couple dB of power before you achieve the point of BUC saturation (as determined by a 1dB compression point) you can add a couple dBs from the command line in telnet. Once in the network, the NMS will ultimately reel you back in to the configured UCP sweet spot (normally 9dB c/n). Too easy.
posted
Just FYI - If you believe that your modem compression setting may need re-adjustment Please email support@atcontact.com and someone will be happy to check your BUC compression point. This only takes a few minutes to do. Alternatively, you can contact MotoSat and have them connect you to the NOC via phone. The ATCONTACT NOC is manned 24 x 7.
Yeah, I shot some notes to Motosat and they asked me to re-point. I'd done that a couple times but, complied. What'dya know?! It came online!
The lights I had were green power and two flashing orange - Rx and Net. I worked for a few more days before moving to Arlington TX where things came back up fine - until the wind came up yesterday and the dish was put to sleep again :-(
oh well... ;-)
Thanks for the info and suggestions.
tom
-------------------- F2/6W | D3 3.9.6V | iDirect | 123W | AtContact 768/384 | Vonage VOIP | AT&T Software VPN | Kyocera KR2 | DA4000SBR - 50U Digital Antenna | Our location and our story Posts: 173 | From: On the road, exploring the US & Canada | Registered: Oct 2007
| IP: Logged |
UBBFriend: Email this page to someone!
Printer-friendly view of this topic
