Advertisment: Broadband via satellite
Advertisment: Worldwide satellite services from Ground Control Company

www.satsig.net

Satellite Internet Forum.

Welcome, Guest.        Forum rules.
      Home            Login            Register          
Pages: 1

No. of Terminals in an inroute

(Read 2653 times)
smlt_vsat
Senior Member
★★★
Offline



Posts: 56
Dec 10th, 2008 at 10:19am  
Hi

What is the calculation and factors included in assigning no.of remotes in an inroute. I think there is npt user guide which tells that but in short is there any other formula which we can calculate approximately.

Please let me know.

Also how I can know a MIDI card is ok or not , recently I saw some terminals in an iroute takes time to lock on RX, everything was running perfectly but it happens sudden. No changes or no terminals added in this inroute and was working last two years but nowadays i see same problem. I guess might be line card has got same problem. Is there any way to check that

smlt
Back to top
« Last Edit: Dec 10th, 2008 at 12:38pm by Admin1 »  
 
IP Logged
 
Ex Member
Ex Member


Reply #1 - Dec 10th, 2008 at 11:48am  
I dont know of any formula or calculation used to determine remote maximums for an inroute group.  I am pretty sure it is determined by utilization on the blades.

The long lock could be a number of things.  Do all of the nodes take a considerable amount of time to lock?  If it is common amongst all, I would start looking at:

1,  Your e/s  BDC (make sure you have your stability set appropriately...open it up if necessary).
2. Check your configured UCP.  Is it 9dB? What are the fine and course adjusts set to?
3. Remote (initial) power levels.  Check each of them and makes sure they are commissioned properly.  Under clear skies (both sides of the link).  TX initial should be 2-3dB down from the operating power observed under clear skies.  Max power should be set 2-3 dB down from the intial (or at the prescribed 1dB compression point).

The reason those power levels are important and need to be set properly, is in the event that multiple nodes take a bounce (due to a disruption in the downstream or upstream carriers).....you want to mimimize acquistion time when they all come piling back (re-entering) into the network.  With a UCP configed for 9dB bursts arriving too high or low may not get picked up by the UCP.
Back to top
 
 
IP Logged
 
smlt_vsat
Senior Member
★★★
Offline



Posts: 56
Reply #2 - Dec 10th, 2008 at 12:51pm  

Configured UCP is 7 dB

FIne Adjust

Below Nominal C/N  -1 dB
After Nominal C/N 1 dB
Power adjust 0.5 dBM

Coarse adjust

BElow Nominal C/N  -3 dB
After Nominal C/N  3 dB
Powr adjust 2

Remote Power Levels are Ok as said , 1 dB Compression is done while commisiong Terminals.

Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #3 - Dec 11th, 2008 at 2:11am  
7dB is fairly low.  What band are you operating in C or Ku?
Back to top
 
 
IP Logged
 
Darkside
Member
★★
Offline



Posts: 12
Reply #4 - Dec 14th, 2008 at 7:55am  
Although it is not the only factor but the surely the most important one , the number of remotes per inroute will be limited by the number of TDMA timeslots available. This can be calculated with the iNPT tool once all the carrier information etc. has been inserted.
Each remote will receive one timeslot by default thus in theory one cannot add more remotes than timeslots allocated. But…. One can adjust the default minimum CIR  so a remote will receive a timeslot in every second or third frame etc. (Limited to 2 Seconds). Note that this will increase latencies somewhat but it is useful for SCADA networks etc. The other way to make timeslots available to remotes is by putting some of the remotes in sleep mode or deactivate them because this will release the timeslots back to the pool.
iDirect conducts design training in all of their regions a couple of times of year and it covers these topics.
Back to top
 
 
IP Logged
 
Pages: 1