Hello Everyone,

I need help ASAP to clear out this issue of C core remaining at A6 state.

Findings-
1. Card_ID out put file shows C-IOMA )
C-TCDA )
2. IO_state on --186--monitor shows
(1) TCCA -- A6
(4) **** -- 00 SOMETIMES *3*0 -- A2
(8) LCCB -- A6
(12) DCCB -- A6
(13 *0** -- A1 SOMETIMES **** -- A2

Messages scrolling on sDCC DISPLAY of <C>..
-Missing IOcfg
-QST DPM timeout
-IO cfg failed
-DCC to reset

C core was reloaded by defaulting the cards and putting original values. All the prom versions were correctly entered in IO_cfg.

I want to know where can be the problem.

Thanks and Best Regards,

Mambo

 

I need to understand what was the condition that prompted all of this downloading and I/O re-Configuration.

I don't recommend changing and defaulting cards unless one understands all the steps required to make sure the right information gets loaded into the I/O Configurator. Also, just defaulting cards does *NOT* make sure the proper site-specific values get loaded into the I/O Configurator.

Socket 4 is usually the TCDA card. Did you change the TCDA card? Are you sure the IONET termination resistors are in the proper positions on the new TCDA card? Or, if you changed the TCCA card, are you sure the IONET termination resistors are in the proper position on the new card?

It sure seems like something's not quite right with the IONET. Either a cable is not plugged in correctly, or termination resistors are not correct. Or, the wrong I/O Configuration values have been downloaded. I sure hope you have back-up I/O Configuration files from before the defaulting was done.

But, when you write a post like this, it's critical to tell us the *whole* story--what happened to start this process, as well as the steps that were taken during the troubleshooting.

 

Dear CSA,

Thanks for the reply.

When reached at site the unit is found torn apart and cards of MKV used as spares for other running units.

On first powering up it was found that all cores reached A7 status except core C stayed at A6 state with mentioned diagnostic alarms on the SLcc display.

#The ionet cable from C core to CD Loc 1 was checked prior to all defaulting/reloading the C core.
#Power supply was checked and found normal.
#Card ID was performed and found that IOMA and TCD shows **** on the display.
#Ionet terminals/plugs and resistors berg jumpers were confirmed correct. the cable originates from CTBA to CD core loc-1. All incoming and outgoing ribbon cables from CTBA to TCCA and CD core were throughly checked. 2PL, 3PL, 6PL, 8PL, ARCPL...

Todays further finding were...

1. There is alarm persisting - Common IO Communication loss and L3COM_B - 0 LOGIC.
2. On Prevote data page the readings of logic is normal but the top of the page is displayed in BLUE letters- C, R, S, T
3. When we force a logic it doesnt alarm as logic signal is forced. Also the R S T values are displayed correctly =0 or =1 but C values remains =0

4. All Thermocouple values shows negative (wheelspace, Load gear T/c and lube oil temperatures) which are on C core.

My further question is C core TCCA and SDCC and TCDA card are not communicating due to any 186, 196, 320 processors failure? Or any EEPROMs failure or card failure.

Presently I don't have any spare cards to swap so I am helpless. If you can further provide me with more tests and checks will be appreciated. I am also going through previous questions about EEPROM... topics earlier answered by CSA and markvguy... they are helping us a lot.

Best Regards,

Mambo

 

You certainly seem to have an IONET problem, possibly a '196 problem, since if I recall correctly (but it's been a long time) the '196 chip (the "I/O Master", IOMA) is also "on" the IONET.

But, if the processor is at I/O State A6 the problem may just be as simple as Major/Minor Revision levels not being correct. When you defaulted cards did you check the revision levels? Are you sure all the Major- and Minor Revision levels for every PROMset are correctly stated in the I/O Configurator? Do you know if any of the current revisions are a major revision level greater than what's stated in the I/O Configurator after the defaulting?

Are the LEDs on the <C> TCDA flashing in the same sequence as those in <QD1>? (That's about the only thing the card LEDs are good for is comparing to other known good cards; if the sequence is different, it's likely there's at least one Diag. Alarm being annunciated for that card.)

But the PROMs from the cards which were presumed to have failed should have been transferred to the cards replacing the suspected bad cards, so there should have been no reason for defaulting cards. Did the new cards have PROMs on them which were different revisions (be specific) than those on the card being replaced?

 

I mis-spoke (seems to be a bit of that going around these days); I believe the I/O Master is the TI 320nnn chip, not the '196 chip, and I believe they are only present on DCC cards, not SDCC cards, but I may be mis-speaking again; I don't have access to a Mark V ("A" or "B") these days.

 

Dear CSA,

Thanks for the reply, I again re-confirm that All the prom versions were copied seperately and the results tally with the Card_ID results, and then they were reloaded after C core cards were defaulted with original IO config values.

It was found on boot-up of C core, when arcnet is displayed the lights of TCDA keep on scrolling from right to left as if it is searching and is continuously searching till now. I swapped the <CD> TCDA loc-1 card with <QD> TCDA loc-1, 2, 3 cards but the result still the same... the green LED keeps continuously scrolling left to right on CD core.

I also reconfirmed the cards installed on C core have the same proms when they were replaced or swapped to other units.

The single green Led on TCCA card is continuously on and stays on always as in R, S, T cores.

The MSB Red LED (extreme left) on SDCC blinks same time as R, S, T does when I reset the 04 diagnostic mentioned earlier on the SLCC display.

One more question, which are the Diagc values to be checked verified for if Diagc is run?

I am awaiting the SDCC, SLCC cards to replace as you mentioned about 196 chip.

Best Regards,

Mambo

 

I again re-confirm there is some problem with the IONET in <C> or with the IONET getting back to the SDCC card.

I believe if you look at the Maintenance Manual, GEH-5980, you will see that the IONET in <C> runs from the TCCA to the TCDA. When you used CARD_ID you say it can't "see" the TCCA or the TCDA. I would think that if you used the LCC Display it would also not be able to "see" the TCDA and the TCCA.

Have you performed a continuity check on the IONET cable of <C>?

Another possibility is the 3PL cable that connects the SLCC, SDCC, and TCCA. There are no pull tabs on that cable (what's up with that?!!??!) and if one doesn't use care when pulling that cable when changing cards it can easily become a problem. Try pressing very firmly on the the plastic connectors of the 3pl cable while they are plugged into the cards. It sounds like you have a "spare" panel; have you tried replacing the 3PL cable on <C>?

I will second what markvguy always said about DIAGC: unless you can be certain that DIAGC.DAT is correctly configured for the panel (and 97% of DIAGC.DAT files are *not*), the data can't be really trusted. You can try looking at the communication "counters" (I think there was something like in DIAGC) and possibly compare it to something from <Q>, but I just didn't use it very much myself.

Finally; I believe I was wrong about the IOMA being the '196 chip; see my previous response.

I've also seen chips inserted backwards (with the notches not lining up) and still actually survive. Have you checked for proper orientation of the chips on the cards that were replaced? And checked for any bent or shorted pins on the chips? Is it possible that one of the chips may have not been handled properly and received a "shock"?

The TCDA needs to get it's configuration from the EEPROM on the SDCC card via the IONET. If the LEDs keep "searching", then there's something preventing the TCDA from accessing the EEPROM on the SDCC.

 

Dear CSA,

There are some Diagnostic alarms which gets reset after sometime on I-Dos. 1.0322 T-S-R LCC No arcnet communication with C. 2.0312 C - LCC: Processor re-boot independently

Persisting alarms are:

Q-0243 - Start-up shutdown C comm failure-Trip Q-0062 - ommon IO communication Loss.

Once I get new cards I will comeback with this issue again. Can you please provide me informations about how Diagc tool can help me on checking further problems.

Thanks and Best Regards,

Mambo