Satellite Internet forum
https://www.satsig.net/cgi-bin/yabb/YaBB.pl
VSAT technology and installation >> iDirect Forum: hubs and terminals >> x3 acquisition time problem on different inroutes
https://www.satsig.net/cgi-bin/yabb/YaBB.pl?num=1330523187

Message started by Adnan Nazir on Feb 29th, 2012 at 1:46pm

Title: x3 acquisition time problem on different inroutes
Post by Adnan Nazir on Feb 29th, 2012 at 1:46pm
We are working on iDirect DVB-S2 with x3 netmodems our problem is that we have two inroutes. ku band-1 and ku band-2 while the transmit card is same for these two inroutes. inroute ku band-1 is populated with around 70 sites on network and more remote sites are coming in this inroute, now the incoming sites take 20 minutes to be on network each time the modem x3 is powered on or on commissioning. Sometimes the x3 in ku band-1 take more time to acquire network and needs rebooting too.

So, we shifted those sites which take time from ku band-1 to ku band-2 inroute which previously not have any remote than these sites only took 2 minutes to acquire network means on inroute ku band-1 sites take 20 or more minutes to acquire network while on inroute ku band-2 sites acquire network in about 2 minutes.

We have to install 300 sites soon on ku band, kindly tell me the method by which i can reduce the network acquisition time on inroutes with 100 and above sites on network.



Title: Re: x3 acquisition time problem on different inrou
Post by Adnan Nazir on Mar 2nd, 2012 at 6:42am
Hello! I am waiting very desperately for the replies of experts on the topic mentioned in this post this problem is urgent please reply as soon as possible. If anyone have doubts and queries you can ask, but at least please start to reply.

so, 30 peoples have view this problem but no one replied me !

I am waiting response of tdma mike and other respected iDirect specialists

Title: Re: x3 acquisition time problem on different inrou
Post by TDMAMike on Mar 9th, 2012 at 11:56am
Please provide me with the inroute upstream carrier specs:

Example:
Inroute 1 (Ku Band 1)
2ea Upstream carriers
MODCOD: 2D16S QPSK 3/4
oBW (occupied bandwidth): 1.5Mhz- per carrier

Additional info required:

1. Need to know HOW many remotes were in KuBand1 inroute at the time you were commissioning new remotes.
2. What is the stability setting for your Hub LNB/Downconverter (as configured in iBuilder)?

M


Title: Re: x3 acquisition time problem on different inrou
Post by Space on Mar 10th, 2012 at 8:57am
Hi

Let us know your Inroute distributions on the Timeslots.

How many  time slots does each inroute have

You could be having a problem  with  Time slots  allocations


Title: Re: x3 acquisition time problem on different inrou
Post by Adnan Nazir on Mar 10th, 2012 at 9:30am

wrote on Mar 9th, 2012 at 11:56am:
Please provide me with the inroute upstream carrier specs:

Example:
Inroute 1 (Ku Band 1)
2ea Upstream carriers
MODCOD: 2D16S QPSK 3/4
oBW (occupied bandwidth): 1.5Mhz- per carrier

Additional info required:

1. Need to know HOW many remotes were in KuBand1 inroute at the time you were commissioning new remotes.
2. What is the stability setting for your Hub LNB/Downconverter (as configured in iBuilder)?

M



Dear Mr. M, following are the details as you have asked


inroute upstream carrier specs:
Inroute 1 (Ku-Band 1) which takes 7-16 mins to acquire a remote
Occupied BW = 454.4376 kHz
Modulation : QPSK
Error Correction: TPC-676/1024

Inroute 2 (Ku-Band 2) which takes 3-4 mins to acquire a remote
Occupied BW = 727.1004 kHz
Modulation : QPSK
Error Correction: TPC-676/1024

Additional info required:  

1. Need to know HOW many remotes were in KuBand1 inroute at the time you were commissioning new remotes.

At the time we were commissioning new remotes there were around 40 to 50 remotes already commissioned and connected to HUB whereas around 25 to 30 remote sites were created but not commissioned (i.e. these sites have the status of "never applied" to them)
2. What is the stability setting for your Hub LNB/Downconverter (as configured in iBuilder)?

It is configured to 0.03 +/-  MHz.

We think the issue is related to the ACQ_TX packets being sent to all out of network remotes (either powered off by customer or a remote that has not been commissioned i.e. with "never applied" status).




Title: Re: x3 acquisition time problem on different inrou
Post by Adnan Nazir on Mar 10th, 2012 at 10:14am

wrote on Mar 10th, 2012 at 8:57am:
Hi

Let us know your Inroute distributions on the Timeslots.

How many  time slots does each inroute have

You could be having a problem  with  Time slots  allocations



Dear Space here is the time slot planing


Inroute-1 has 83 time slots with acquisition aperture of 651 sym whereas Inroute-2 has 134 with acquisition aperture of 1040 sym

Powered by YaBB 2.5.2!
YaBB Forum Software © 2000-. All Rights Reserved.