Batboard

I have centra com gold elite console were after about a day of use the DIU resorts to self test and red X appears at console display. All console traffic for that channel is halted. The DIU self tests and comes back up. Is there any type of setting that would cause this in the RSS?

Is this on a trunked system or conventional system? As you know the Gold Elite is a network based console..

On 2001-11-03 01:11, 2wayguru wrote:
Is this on a trunked system or conventional system? As you know the Gold Elite is a network based console..

Uhmm....the LAN shouldn't have any "direct"
bearing on his problem. Not unless a COIM
upload or OP position change is being made.

Have you examined the error dumps in the RSS
service menus ? Are you using the ACIM via a
quad connector of COMM1 or the "W cable" off
the back of the DIU ? Or are you using the
standard "station", and "console" terminal
blocks on the back of the DIU ?

If that's all it is (ie. you've got 4 wire
copper pairs running to it). You might want
to check your function tone table. I've seen
a few DIU's reset themselves when configured
for incompatible options that are defined in
the function tone tables).

It'll get confused and reset itself.

I just thought I throw out an update just in case someone else is having the same problem. We have replaced everything from the modem to the DIU and the ACIM/bim nothing would fix it.At first we thought it was just one channel but, we switched the sheriffs dept over to secondary and in an hour the console had a red x on the display and the diu was running through its start up test. At this piont we said it is a DIU problem. Our system has been in place for about 10 months and this problem has been off and on for the last six. SSC could not come with any real help becuase this is non trunked digital simulcast system. No one really knew much about it. We finally went and record every error log we could this include the astrotac, quantar, diu and event viewer for the console. I emailed that plus the codeplug to SSC. I also sent every bit of firmware version numbers I could find. They agreed with us that it was with the diu. The diu firmware is the problem. According to the diu engineer. The selftest was a problem with version 4.00-5.19. THey are sending me version 5.23( i think thats it) I should have it today. I will post an update in a couple of days. I have to give it time to see if it fixes the problem.

Aaron
[email protected]

Figures, there's a KNOWN issue with the DIU firmware, and "nobody" at Motorola knows anything about it until you prove it (yet again) beyond the shadow of a doubt. One of the many things that piss me off about the big M. "Admit nothing" seems to be their motto. Thanks for the info Aarontech, it'll probably save somebody else a lot of hassle next time.

Todd

On 2001-11-06 08:10, wavetar wrote:
Figures, there's a KNOWN issue with the DIU firmware, and "nobody" at Motorola knows anything about it until you prove it (yet again) beyond the shadow of a doubt. One of the many things that piss me off about the big M. "Admit nothing" seems to be their motto. Thanks for the info Aarontech, it'll probably save somebody else a lot of hassle next time.

Todd

In all fairness, SSC runs across a lot of
misconfigured equipment. So yes, naturally
they want field personnel to exhaust all
possibilities before blaming it on any type
of firmware issue.

I had suspected this, but typically you
check the simple things first, before going
after the more complicated possibilities.

For the 'admit nothing' comment....reminds
me of the old adage I learned working with
certain units back in Southeast Asia in the
70's.

Admit nothing, deny everything, demand proof!

Job well done on the DIU reset root cause
troubleshooting approach. As the other poster
stated, thanks for sharing the info.

Well ithas been alittle over a week and our diu console problem has not reoccured. It looks like the firmware fix was a good solution. I hope the info helps all you techs out there.

Aaron