replacing PU4DC

[abuokarem]

Hi all,

I have replaced in one site all PU4DC boards with the new RG5DC according to service advice regarding faulty PU4DC.
After I replaced the PU4DC, every thing worked fine except the TLU44 in some magazines.
TLU44 in some magazines get blocked and alarm code 260 takes place. The alarm code says that it’s a current feed problem (No current feed). What this mean and how to be solved??
Did any one have faced such problem??
The magazines were the TLU44 got blocked are LBP 14 & 15

Plz advice
Thnx

 

[abuokarem]

any ideas ??

 

[lancbomb]

I have no "field experience" with this,

but to pre-empt, have you checked the voltages and all connections ?

 

[abuokarem]

hi lancbomb, i have checked the voltages and the connections and every thing seems ok.
i just want if any one know what is the meaning of the alarm : no current feed on the TLU44!!!!

thnx

 

[lancbomb]

error code 260 is.........................

260 Fault on line to interworking PABX or public exchange
see fault locating directions for FAULT CODE 260

ADD INFO 1: Individual pointer to TRS data individual

ADD INFO 2: Description about the type of line fault for analogue external lines

1 = No current feed

2 = No proceed-to-send signals

3 = No seizure acknowledgement

4 = No clear acknowledgement from cooperating exchange has been received

5 = Lack of ringing signal at incoming seizure

6 = Received faulty decadic pulse from public exchange

7 = Time out occurred during digit reception

8 = Wrong pattern received

9 = Pulse out of range

10 = Faulty MFPI/MFPII signal detected or time out occurred during MFPI/MFPII signalling

 

[lancbomb]

do an allop prinout,
blfdp printout
route prinout
and susip prinout

 

[lancbomb]

also 260 says that

The alarm is generated in the following situations:

- The voltage on the line is not in accordance with the table values

- No current in idle state is detected

- No seizure acknowledgement has been received

- A number of consecutive proceed-to-send signals have failed to appear

- No clearing acknowledgement has been received

 

[abuokarem]

ALLOP;
ALARM LOG
IDENTITY: ST-BC12-SP05
VERSION: CXP1010101/2/BC12SP5/R2A

260 FAULT ON LINE TO INTERWORKING PABX OR PUBLIC EXCHANGE
DATE TIME ALP NOIF UNIT EQU BRDID INF1 INF2
******* 02:12:18 2 7 TLP11 001-0-63-00 7 98 1


<blfDP;
FAULTY DEVICES
EQU BOARDID BLOCKING DISTMARK LINELOCK
001-0-63-00 007 B'0000000000001000 NO NO

END

TRU
<susip:rou=10,tru=all;
STATUS INFORMATION AT 00:00:00 01JAN00
ROU TRU TYPE TRAFFIC STATE/PTR LINE STATE/PTR ADD INFO
10 001-1 TL11 IDLE #0062 BLOCKED #00F4
END

<rodap:rou=10;
ROUTE DATA
ROU TYPE VARC VARI VARO FILTER
10 TL11 H'00000101 H'00000108 H'000000D1 NO

END

<rocap:ROU=10;
ROUTE CATEGORY DATA
ROU SEL TRM SERV NODG DIST DISL TRAF SIG BCAP
10 0110000010000010 4 3110000000 0 30 128 00151515 400000000000 001100

END

 

[lancbomb]

thankxs

have you tried or can you try the folowing and post the results

1> block card/reseat card/restart card/unblock card

2> physically check that line is ok

3> swap the card/port for another in the system

4> see if the fault follows the card or the line.

I still find it hard to believe that the Powerd card has caused this.

 

[MDfreak]

which BC release do you have and do you have REU's still in MAG,s