SatSig topic:

no NET LED on idirect x3 series

(Read 17822 times)

Aug 13^th, 2009 at 4:15pm

hello sir,
i bought an x3 evolution modem and trying to activate online with my provider. but it is not coming up on my provider's platform.although they login into it remotely, reboots it and do other things in it. i have rx/tx led on solid green state but no NET. pls, i want to know what could be the responsible for no NET.could it possible that there maybe a file(s)/software that my provider needs to upload to their HUB to accept the x3 series evolution modem.
pls sir, reply asap.
best regards
edwin

Aug 13^th, 2009 at 10:08pm

Your terminal can receive (UDP) without a NET LED. They are likely changing your TX Values to add or remove power (in an effort to meet the network UCP).

If your TX LED is illuminating (periodically) then the following could be possibilities:

1. You are not radiating enough power and are too far below the UCP.
2. Your radiating too much power and you are above and beyond the coarse adjust parameters of the UCP.
3. You BUC could be faulty
4. Your Uplink cabling could be faultly

Have you conducted a peak and pol (CW and Modular) with Controllers? If not, please consider that course of action. That will confirm whether or not you are radiating CW (pure carrier).... and modulated.

Additional Considerations:

1. Double check your software version and ensure that you have the same version as the Hub.
2. Ensure you have enough BUC to close the inroute/upstream the Hub has you populated in.

Aug 14^th, 2009 at 4:00pm

thanks mike,
i contacted my noc and it happens that we are running on different software versions.now am okay.my noc have gotten the newer version on the hub.

Aug 14^th, 2009 at 4:30pm

Glad to hear it.

May 21^st, 2013 at 8:01am

Dear MIKE,
I have the same problem in my X3 remote. 1 remote is not getting NET LED. RX and TX is solide green. i have checked my software version. i was same as HUB. My tx chain and BUC are not faulty because another modem is getting NET from this site. so we could say our TX chain is ok. I was trying to peak a CW carrier but i was not seen any CW carrier into my Spectram analyzer. What can i do now brother?

we have 14 remote which has same problem and it is now in my HUB store Room.

Note: It was a old modem which was running in my client premises.

May 21^st, 2013 at 8:42am

Maybe your option file does not match the BUC model. Please confirm what is the BUC model and what is the up translation in the option file?

May 21^st, 2013 at 8:59am

My BUC is right as Option File.

May 21^st, 2013 at 6:08pm

It must be then that GPS coordinates are wrong.

Please confirm in the option file that the satellite longtitude, site lat and site long are all correct.

Good luck and tell us how it goes

May 22^nd, 2013 at 6:11am

I have change my LAT LONG accurately but Nothing Happend. Any other idea?

May 22^nd, 2013 at 8:40am

It could be related to an IP address conflict on the hub or incorrect configuration of the IP address somewhere? The NET LED indicates that the link layer between the PP and management IP address is established.

May 22^nd, 2013 at 9:12am

[quote author=dot link=1250176517/0#9 date=1369208404]It could be related to an IP address conflict on the hub or incorrect configuration of the IP address somewhere? The NET LED indicates that the link layer between the PP and management IP address is established.[/quote]

Dear dot, This was a running modem in my client end. suddendlly it was behaving like this problem . I think you could be right. so if it happend (According to your thinking) how can i troubeshoot this problem.

Note: we have some remote as the same problem. Please do something for me.

May 22^nd, 2013 at 11:34am

Please anyone kind give a suggestion

May 22^nd, 2013 at 12:39pm

Dear Sohel,

If BUC is good,
and modem is good,
and RX and TX are green but net is off,
it means that the hub cannot get a good signal from the remote side.

Maybe you can send us the option file and your location, with your BUC model so we will analyze it?

Another possible thing that was not mentioned before is please check the OMT.

If it is a Ku band, maybe you installed the BUC on the LNB arm with the RTF.
Or maybe you are set to Co-pol and need to work in Crosspol etc.

May 22^nd, 2013 at 12:55pm

Ok i am giving you the option file and my geo location.

[MAPSERVER_0]
hostname = 10.110.110.100
port = 5003

[BEAMS]
beam_3 = SquareHub
alt_beam_3 = 15
beam_15 = SquareHub
maxbeam = 15

[OPTIONS_FILE]
product_mode = dvbs2
modem_sn = 81170
generated_by = NMS-10.0.1
did = 33635602
modem_type = Remote
modem_hardware = X3
is_mesh = 0
disable_options_flash_command = 1
carrier_type = 0

[SECURITY]
password = $idi3$0ZNZYp$0tjc87RnZPYHk.8TtlwhCZC8oswa0xDBWExal2un367GzF5CSxn3LnxhJ/Poedigy8T
Fj5YwvqPVF6Z8L5geFe
admin_password = $idi3$0fnghp$18ygXJqRf469zokiSDxUaScHal0aJBPq7EbgRdpcCsefWnDjamMQGvEnuwLaEuWo3qk
SDw0BK37gxcX7flaJMm
os_password = $1$1IrQJs$hjRF6x1EHksk5AttwbsCQ/

[NMS]
timeout = 20000
server_ip = 10.110.110.100
broadcast_ip = 10.110.110.100
keep_alive_port_number = 2860
NRD_server_ip = 10.110.110.100
NRD_remote_status_port_number = 2859
service_monitor_interval = 1000
download_monitor_group = 239.192.0.0
download_monitor_port = 9000
download_monitor_credentials = 1
is_nms_managed = 1
event_server_ip = 10.110.110.100
event_server_port = 2860

[VLAN]
mode = 0
vid = 1

[ETH0_1]
address = 172.201.200.57
netmask = 255.255.255.252
rip_enabled = 0

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

[SAT0_1]
address = 10.235.205.1
netmask = 255.255.255.0
rip_enabled = 0

[ETH0]
interface = ixp0
phy_count = 1

[LAN]
lan_ip = 172.201.200.57
lan_subnet_ip = 255.255.255.252
lan_gw_ip = 0.0.0.0

[DVBS2]
pilot = 1
ncr_interval = 3375000
mode = acm
frame_size = short
rc_roll_off = 0.200000
inroute_frame_length = 125.000000
frame_length = 0.0

[MODEM_PARAMETERS:3]
rx_freq = 1693639999
rx_acqrange = 750000
rx_bitrate = 1024000
rx_mode = 2
rx_modtype = 5
rx_fecrate = 22
rx_scram = 1
rx_diff = 0
rx_specinv = 0
tx_freq = 1000000000
tx_bitrate = 302000
tx_mode = 0
tx_modtype = 1
tx_clksource = 0
tx_fecrate = 5
tx_scram = 1
tx_diff = 0
tx_specinv = 0
tx_power_in_dbm = -16.000000
rx_fsd = 24528
tx_spreading_factor = 1
rx_spreading_factor = 1
tx_spread_enable = 0
rx_spread_enable = 0
is_demod2_active = 0
rx_symrate = 1024000.000000
tx_symrate = 228734

[ACQUISITION_PARAMETERS]
fsd = 26743

[UCP]
power_uplink_control_processing = 1
max_power_level_in_db = -5.000000

[ODU]
music_present = 0
odu_rx_dc_power = 1
odu_rx_10_mhz = 0
odu_tx_dc_power = 1
odu_tx_10_mhz = 1
lnb_tone_enable = 1 # !! Custom Parameter !!
lnb_dc_voltage = 19
odu_disable_tx_pwm = 0

[TDMA]
tx_watchdog_timeout_in_frames = 2

[TIMEPLAN:3]
fec_blocks_per_outroute_frame = 128
unique_word_len_downstream = 32
symbols_per_inroute_frame = 28591
outroute_fec_block_len = 0
outroute_fec_type = 1000
inroute_fec_block_len = 128
inroute_fec_type = 660
unique_word_len = 32
symbols_per_outroute_frame = 128000
num_acq_slots = 1
aperture_traffic = 8
aperture_acq = 788
num_traffic_slots = 49
payload = 512
scaling_factor = 0
skip_slots = 2

[MODEM_INSTALLATION]
hub_lat = 23.570000
hub_long = 90.170000
remote_lat = 23.570000
remote_long = 90.170000
spacecraft_long = 108.200000
reflector_offset_angle = 0.000000

[FREQ_TRANS]
down_translation = 10600.000000
up_translation = 12800.000000

[DEBUG]
cpu_util_test_enabled = 0

[GUI_SERVER_PROXY]
port = 14599

[POWER_MANAGEMENT]
enable = 0
sleep_timeout = 0

[ENC]
enc_layer_enabled = 0
enc_enabled = 0
enc_mode = 0
peer_mode = 1
auth_level_required = 0

[NET_ENC]
id = 1
is_encrypted = 0

[UDP]
passthru = 1
force_udp_fullheader = 1
force_rtp_fullheader = 1
payload_comp = 0
max_hdr_comp_packet_size = 180

[COMPRESSION]
Threshold = 90

[OOB]
mem_low_percent = 75
mem_high_percent = 90

[TX]
device_path = /dev
device_mode = tdma
device_name = tx

[RX1]
device_path = /dev
device_mode = scpc
device_name = rx1

[BTP]
device_path = /dev
device_mode = tdma
device_name = btp

[SOF]
device_path = /dev
device_mode = tdma
device_name = sof

[BTP_REQ]
device_path = /dev
device_mode = tdma
device_name = btp_req

[TX_SOF]
device_path = /dev
device_mode = tdma
device_name = tx_sof

[SATELLITE]
min_look_angle = 0.000000
name = NSS-11
channelname = SquareHub
longitude = 108.200000
max_lat = 0.000000
pol_skew = 0.000000
hunt_frequency = 0.000000
polarity = H
tx_polarity = X
noise_reference_frequency = 0.000000

[SYSTEM_TRAY]
mode = 1
server = 10.110.110.100
port = 2859
interval = 5000
service_monitor_group = 239.255.255.1
service_monitor_port = 9001

[MODEM_PARAMETERS:15]
rx_freq = 1694069999
rx_acqrange = 750000
rx_bitrate = 1780000
rx_mode = 2
rx_modtype = 5
rx_fecrate = 22
rx_scram = 1
rx_diff = 0
rx_specinv = 0
tx_freq = 1000000000
tx_bitrate = 302000
tx_mode = 0
tx_modtype = 1
tx_clksource = 0
tx_fecrate = 5
tx_scram = 1
tx_diff = 0
tx_specinv = 0
tx_power_in_dbm = -16.000000
rx_fsd = 24523
tx_spreading_factor = 1
rx_spreading_factor = 1
tx_spread_enable = 0
rx_spread_enable = 0
is_demod2_active = 0
rx_symrate = 1780000.000000
tx_symrate = 228734

[TIMEPLAN:15]
fec_blocks_per_outroute_frame = 128
unique_word_len_downstream = 32
symbols_per_inroute_frame = 28591
outroute_fec_block_len = 0
outroute_fec_type = 1000
inroute_fec_block_len = 128
inroute_fec_type = 660
unique_word_len = 32
symbols_per_outroute_frame = 222500
num_acq_slots = 1
aperture_traffic = 8
aperture_acq = 788
num_traffic_slots = 49
payload = 512
scaling_factor = 0
skip_slots = 2

#

I mentioned it before that there is no chance to fault OMT, RF cable, LNB, BUC, Connector, alignment. because another x3 is running in the same site.

understand?

My LNB and BUC both Manufacture are iDirect (Part No- E0001-100-0001)

Note: HUB latlong and remote latlong will be same in my option file because both are now in same loacation & i am from my HUB. If you want i can give you teamviewer access to the remote with a Console cable.

May 22^nd, 2013 at 7:51pm

ok, so we eliminated GPS coordinates problem and also pointing, ODU and IFL. We comes to the modem now.

If the modem is at the hub, maybe you can connect a spectrum to the Tx port of the modem, just make sure you disable the DC and 10Mhz. Try to send to the modem CW command and try to see if you see it on the spectrum.

Another thing is to confirm there is no software mismatch. Maybe something is faulty there as well...

May 23^rd, 2013 at 6:05am

[quote] Another thing is to confirm there is no software mismatch. Maybe something is faulty there as well... [/quote]

What is software mismatch? My NMS package and Remote package both are same version.

why need off DC volt and 10 MHz? i am not checking Rx chain. so why we need to off those?

N.B: Today i am seeing that tx and net is blinking. so Tx LED is not stable? so i am not going to check the CW. Why it is blinking? what is the problem ?

May 28^th, 2013 at 4:54am

Problem is solved. Just i have do nothing. connect Rx & Tx cable into the modem and after 2 days later suddenly i saw that NET LED comes up. i don't know what was the problem. Anybody guess what was the problem???

Jul 8^th, 2013 at 5:30am

Quote:

It could be related to an IP address conflict on the hub or incorrect configuration of the IP address somewhere? The NET LED indicates that the link layer between the PP and management IP address is established.

Check your router to make sure that the correct routes listed, etc...Maybe they have added something else to the network at the hub site that could be in the same IP subnet.

Also check the QoS that these remotes are running on. This can also cause issues. Get the HUb to revert this to default and see if this fixes the issue.