Home page of Satellite Internet and Information

Satellite Internet Forum.

Welcome, Guest.
Welcome to this satellite broadband discussion forum. Wherever you are and whatever your problem we are here to help each other. Connecting to the internet via satellite is not always easy but is critically important to those in remote places or with poor terrestrial infrastructure. Both service providers and customers are encouraged to contribute. Register at the bottom of the forum home page if you wish to contribute or ask question. Read the Forum rules.
      Satellite Internet Forum : Home Page          
Pages: 1

Freezing Infinity 3100 Modem

(Read 3122 times)
Ex Member
Ex Member


Jun 9th, 2008 at 7:20pm  
Hello good eve,
I come once again. Having some difficulties with my site and really need your help. You will see my post on the satsig forum saying same. Please help me now. I am having difficulties with my modem, Infinity 3100. My ISP says it freezes and comes on only when he checks my SNR on his NMS or so.
On my side, I get TX and RX locked, green even with the TX cable removed on the modem. I have reinstalled my firmware, changed my LNB, changed my cables. I do not seem to know what next to do. Please kindly tell me what I could do to get this modem back on track. I can enter with isite and via console. My 1db compression point is -19. and my tx power was set at -20. I use an NJT 2 watt BUC pointed to AMC 12.
Please come to my rescue.
Thanks a lot
Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #1 - Jun 9th, 2008 at 7:53pm  
1dB of weather flex before reaching saturation?  Wow, that isnt much to work with.

Do not load anymore software or options files on the box.  They are probably good (TX and RX is lit)

1) Please ensure that your NOC/HUB has actived your terminal.  
2) If activated, start looking at your IF/RF uplink chain by ensuring that all associated cabling is connected and good (simple stuff but it is the starting point in troubleshooting).

If the problem persists after checking cables, you need to start looking at your BUC. Normally, (and I have seen this many, many times) when the TX and RX are illuminated and you are not able to achieve a network light your BUC has faulted or possibly gone bad.  

The presence of a TX light means that the modem knows its location and is radiating LBand (which is why it is staying green when you remove the Tx cable....the 3100 is transmitting). We wont completely rule out the 3100 at this point, but I would start with your cables and BUC.

I must say with the little amount of extra power you have (i.e. -19 compression test) if you, or your HUB is under weather ANY whatsoever, you may not come in the network.  

M
Back to top
« Last Edit: Jun 9th, 2008 at 9:06pm by N/A »  
 
IP Logged
 
Ex Member
Ex Member


Reply #2 - Jun 11th, 2008 at 1:11pm  
Also, make sure you have exact GPS coordinates (latitude and longitude).
Cheers
Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #3 - Jun 11th, 2008 at 8:40pm  
Hi
GPS not nesscery in this case, we have a sites work with area 30 - 200 Km moved without any issue in service.. check this issue with your ISP.
Back to top
 
 
IP Logged
 
Eric Johnston
Senior Member
***
Offline


Personal text from Profile,
Options, Top line

Posts: 2109
Reply #4 - Jun 11th, 2008 at 11:12pm  
Unless the hub ranges your site and measures and corrects any error in your lat long, your bursts will arrive at the satellite at the wrong time.  If someone else then transmits and their burst overlaps with yours, then you both will lose that burst.  Tyhe fault may be evident all the time, sometimes or hardly at all, depending on traffic load etc.

Do tell the VSAT hub and your modem your lat long coordinates.  They are needed.

Best regard, Eric.
Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #5 - Jun 12th, 2008 at 1:07am  
Normally when the Tx LED is iilluminated, the box knows its location. If the box does not know its location the LED will be out, and the transmitter will remain muted until it has one of two things:  

1. NMEA provided on console(4800 or 9600)

or

2. Lat/Long info hardcoded in the (iBuilder) config (opt).  This is done in the form of DMS or decimal.  When hardcoding, iBuilder calculates the Frame Start Delay (FSD) and places it in the options file....most in here probably know this, but I am expounding for those who dont know..

Some nodes request to be hardcoded by their ISP (making them FIXED), others request to be MOBILE and use a gps input device to provide serial/nmea at either 4800 or 9600 on console.

In this case, I think there is a cable issue (uplink chain) or the BUC has gone bad.
Back to top
« Last Edit: Jun 14th, 2008 at 10:14pm by N/A »  
 
IP Logged
 
Ex Member
Ex Member


Reply #6 - Jun 14th, 2008 at 8:50pm  
Thank you all. I will be looking through all the suggestions. TDMA Mike, you have really been helpful on and off this forum. Eric, you are good. Everybody, thanks a million.
Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #7 - Jun 21st, 2008 at 10:06am  
Not ruling out the physical issues.  But i have seen this in the past as well.  The noc or hub has good intentions but they accidently leave out an important part of the option file.  Alexas if you wouldn't mind looking through your option file and making sure you have this field in there.

[ROUTE_1_0]
     interface = sat0
     network = 0.0.0.0
     netmask = 0.0.0.0
     gateway = 0.0.0.0
     metric = 1

It may not be the same but just make sure that the "Route_1_0" is there.  If not you will not pass any traffic out of your modem however all indicators on the modem will be fine.

EDIT: oops, i forgot to ask... you didn't really make it clear if you were in the net or not... only check what i said above if your net LED is solid green.
Back to top
 
 
IP Logged
 
Pages: 1