SatSig topic:

remote cannot get into the network

(Read 3469 times)

Apr 8^th, 2009 at 4:43pm

Hi,

the remote has problem getting into the network.
the remote RX and TX are lighted up except the Net LED.

Also in the ibuilder, the remote icon is greyish in colour.
Is this the correct colour when this is a new created remote? Or the remote needs to get into the network before this icon will turn blue?

Pls advice any troubleshooting tips. thank you.

Apr 8^th, 2009 at 8:23pm

Grey is normal if the remote was recently built (as it has not been issued a socket)

Things to check:

1. Has this remote had a 1dB compression test? CW and modulated (pn)? If so, is its initial and max tx power levels been set accordingly (in its options file, in iBiuilder)?
2. In the iMonitor events and conditions tab, does it say ACQ (sweeps) or UCP (with offsets)?
3. Check physical connections (uplink IF/RF chain).
4. If the remote has been compression tested and you have it set accordingly, probe it up and down +/- 2-3 dB in 1dB increments in an effort to get an ACQ!
5. Does the systems BUC require voltage? If so, can you confirm that it has bias enabled in the options file (same applies to 10MHz Ref). Have the customer check/confirm the presence of that voltage with a meter if possble.
6. Is this remote a mobile remote fed by GPS? If fixed, ensure the geo location you have in it is accurate (D.M.S or decimal) and N, S, E, W is specified for its location. Since the tx LED is ilumminated it appears the remote knows its operating location (to calculate fsd) but please reconfirm that it is right. Also, check your rx line cards (line card stats) for excessive ACQ errors (another indication of inaccuracy in the remotes geo coordinates).
7. Is this remote the first customer in the upstreams, or are there other customers already operational in the upstreams?

I cannot emphasize enough the importance of a good peak/pol/isolation check with controllers. A lot of guesswork can be eliminated in checking that block.

Apr 8^th, 2009 at 10:39pm

I recall having a similar case. The problem was that the config on the imonitor included coordinates in the east while we where in the west hemisfere. No net! Open the opt file in a text editor and double-check.

Apr 9^th, 2009 at 12:47am

Past experiences for me are covered in the post above. Majority of the times it was physical connection or a faulty BUC/SSPA determined to be the culprit.

Apr 10^th, 2009 at 5:31am

Hi,

>>2. In the iMonitor events and conditions tab, does it >>say ACQ (sweeps) or UCP (with offsets)?
Yes.

Since i have another similar remote at the same location which is not connected, i used the same setup and changed to another modem, it is able to get into the network, meaning that the whole remote setup is working fine.

I have measured the problem modem with the SA and its ouput is similar to the good one. But at the hub SA, i cannot see the problem remote modem carrier while i can see the good modem carrier. Does this means anything?

Best Regards,

Apr 10^th, 2009 at 11:56am

When you say you tested another remote, do you mean an entirely different system? Read: a different antenna, buc, etc? Or did you swap the modem only?

When you answered yes to ACQ or UCP, which is it? UCP? Or ACQ?

Apr 10^th, 2009 at 2:35pm

Hi,

I have one nominal remote (not connected) and i tried to duplicate this remote. Thus this new remote is in greyish colour. With the same setup, the nominal remote is able to get into the net while the new greyish remote cannot get into the net with only the RX and TX LED on. These 2 remotes are using different modems.

To say, these 2 remotes are using the same setup i.e. same BUC, same antenna except the modems. But using the SA, the IF output of both modems are the same.

>>When you answered yes to ACQ or UCP, which is it? >>UCP? Or ACQ?
ACQ.

Apr 10^th, 2009 at 5:51pm

Ok.

Does the customer report receiving the options file when your send it to him (UDP w/reset)? Does the modem reset once it is written? Have you confirmed the modem serial number and model type...ensuring it is accurate?

The suspect modem is reporting RX and TX LEDs, correct? If so, are there any errors on your line cards?

Hate to state the obvious, but the modulator in that modem may be faulty.

Any chance of this modem having a mismatch in iDS firmware? Can you have the user telnet in and run the version or versions_report command on it (in falcon). Have him check the iDS version and the BSP (if required). While he is on falcon, have him confirm the serial number and DID by typing DID (all caps) and confirm the SN and derived ID.

M