Quick background. Site has spare parts of dubious origin; rebuilds, parts that were previously used to trouble issues in the field then placed back in stock, etc.
The problem. A Mk V started getting ETR1 Loopback diagnostic alarms for <S>/<Y> and common ETR1 alarms in all cores as all cores monitor all ETR's and all PTR's via a common on JLY, JLX, and JLZ. This leads me back to a bad ice cube in K5 on the TCTG. I replaced the TCTG, but upon doing so <Y> dropped down to A5 and would not return to A7 on power cycle. Okay. I've replaced the <Y> TCEA, triple checked my bergs, double checked revision level, powered it up , and it went to A7. I forced the cross trip to energize the TCTG, and no diagnostic alarms. I check diagnostic counters and see my ETR's and PTR's are all behaving properly in all cores. Unforce logic, master reset, and turn it over to site. The world is healed, or so I thought.
Unit gets dispatched and it won't synch. The 25's (K1, K2, and K3 on the TCTG) aren't working on the "new" TCTG. Okay, I go out and put the just removed "old" TCTG back in. "I may run with a bad ETR1 Loopback diag and know that a second failure will trip me , but at least I can synch" is the sites philosophy. Go through the steps to replace the "new" TCTG with the "old" TCTG. Again when I remove the TCTG, <Y> (The "new" TCEA) loses its mind and won't boot past A5. <X> and <Z> are fine through this whole evolution twice in under an hour not dropping out of A7 on loss of TCTG. IONET is fine as the TCDA's are going to A7 and they are further down the IONET daisy chain than the TCEA. I doubled checked it as well.
I have site getting "brand new" (new old stock I'm presuming) TCEA and TCTG cards hot shotted in overnight. Am I just the victim of bad spare parts or am I missing something as to why JUST <Y> keeps losing A7 just because of TCTG replacement? Again, <X> and <Z> went through the exact same condition without losing A7. I plan on checking continuity on all of the pins of JLY between the <Y>TCEA and TCTG tomorrow, but I've already successfully gotten <Y> to A7 once after the initial "new" TCTG/TCEA fiasco. Thoughts?
The problem. A Mk V started getting ETR1 Loopback diagnostic alarms for <S>/<Y> and common ETR1 alarms in all cores as all cores monitor all ETR's and all PTR's via a common on JLY, JLX, and JLZ. This leads me back to a bad ice cube in K5 on the TCTG. I replaced the TCTG, but upon doing so <Y> dropped down to A5 and would not return to A7 on power cycle. Okay. I've replaced the <Y> TCEA, triple checked my bergs, double checked revision level, powered it up , and it went to A7. I forced the cross trip to energize the TCTG, and no diagnostic alarms. I check diagnostic counters and see my ETR's and PTR's are all behaving properly in all cores. Unforce logic, master reset, and turn it over to site. The world is healed, or so I thought.
Unit gets dispatched and it won't synch. The 25's (K1, K2, and K3 on the TCTG) aren't working on the "new" TCTG. Okay, I go out and put the just removed "old" TCTG back in. "I may run with a bad ETR1 Loopback diag and know that a second failure will trip me , but at least I can synch" is the sites philosophy. Go through the steps to replace the "new" TCTG with the "old" TCTG. Again when I remove the TCTG, <Y> (The "new" TCEA) loses its mind and won't boot past A5. <X> and <Z> are fine through this whole evolution twice in under an hour not dropping out of A7 on loss of TCTG. IONET is fine as the TCDA's are going to A7 and they are further down the IONET daisy chain than the TCEA. I doubled checked it as well.
I have site getting "brand new" (new old stock I'm presuming) TCEA and TCTG cards hot shotted in overnight. Am I just the victim of bad spare parts or am I missing something as to why JUST <Y> keeps losing A7 just because of TCTG replacement? Again, <X> and <Z> went through the exact same condition without losing A7. I plan on checking continuity on all of the pins of JLY between the <Y>TCEA and TCTG tomorrow, but I've already successfully gotten <Y> to A7 once after the initial "new" TCTG/TCEA fiasco. Thoughts?
