Frameworx Communication Problem????

[ShawneeLanes]

OK this one has me absolutely baffled. Lanes 9 and 10 have been down for about 4 days. No communication with front counter. We've changed every board, power supply etc. So we decide to run a new ethernet cable from pinsetter to console. Still nothing. Next we wonder if the ethernet cable we used was a good cable so we take the cable down to lanes 1 and 2 and disconnect the current ethernet cable, hook up the replacement cable. Everything runs fine after switching out the cable on 1 and 2. Now is when things begin to make no sense. We disconnect the replacement cable on 1 and 2 and reconnect the existing cable. Now 1 and 2 are doing the exact same thing as 9 and 10. No communication with the front counter! How could this possibly happen. We changed nothing on 1 and 2. Just ran a new cable then reconnected the existing cable which was working fine prior to this. So now I have 2 pairs of lanes down instead of just the 1! The hub that they connect to does not light up for either of those pairs...all other pairs light up on the hub and are in working order. Does anyone have any answers for me? Man I hope so!

[Ted]

I've seen ports in the hub go bad. Once you've determined that the console is set for the right lane pair, and it is not in stand alone, Try changing the cat 5 wire into a different port in the hub. I'd consider a swap out that hub for a newer switch, and change the coax from the hub to the office computer to a cat 5 eliminating the 10 base 2 network. You should have a combo network card in the office computer - one with both the BNC 10 base 2 connector, and the RJ45 for 10 base T.

[ShawneeLanes]

We changed the hub tonight. The same 2 pairs of lanes are still down. No change.

[Ted]

Can you plug in a notebook, set the NIC to 10.0.0.100, subnet 255.255.0.0, and then go to run, cmd. type 'ping 10.0.0.x' where x=1, then 2, then 3, etc and see if you get a response to all the consoles. This will tell you if the cat 5 and NIC in the console are OK.
But, first, I think I'd try to reboot that console with the CMOS board, leave it in, and see if it comms.

[MASTERMIKE]

Sometimes x out at desk will clear comm issue....

if i remember correctly, score status type lane number 9 & 10 and hit x

any updates done in back office recently?

Mke

[ShawneeLanes]

Well I can't determine what lanes the hard drive is set for because the two pairs won't even boot up. On lanes 1 and 2 I get 3 beeps but the red light on the i/o board never comes on and the screens never get to the Brunswick splash screen. On lanes 9 and 10 I get 2 beeps and also no red light on the i/o board or splash screen on the monitors.

[ShawneeLanes]

Mike, we have Frameworx scoring but we have vector plus desk. The x out at the desk doesn't sound familiar to me?

[MASTERMIKE]

Mike, we have Frameworx scoring but we have vector plus desk. The x out at the desk doesn't sound familiar to me?

Well

X out will not do anything for you since you cant get them to boot anyway...

Im not sure if that is available with the vector plus...

You said you exchanged motherboards with working pair? And used cmos?

Mike

[ShawneeLanes]

Update on what we have done. Installed a new hard drive in lane 1 and booted with the cmos and I was able to get it up and running again. Lanes 9 and 10 are still down. We installed a new motherboard that we just received from brunswick a couple of weeks ago. Swapped i/o board with working pair. Tried booting with cmos. Tried replacement hard drive. Still nothing. I only get 2 beeps when I try to reboot...not the normal 3 beeps.

[MASTERMIKE]

Good deal dude
i would still exchange that motherboard in 9 & 10 again.. I have seen motherboards not boot from brunswick..
that would be good to exchange with working pair to confirm if that board does not boot from brunswick..
Cant hurt to check the battery on that motherboard also

[Ken Smoltz]

Verify power supply is plugged into motherboard correctly - black wires on the 2 connectors go next to each other in the middle. Remove all boards except the motherboard, i/o board, hard drive and the cmos board. Disconnect wires to i/o board except hard drive. Try to boot (see if red LED on i/o comes on). If it does not, one of those 4 items are bad. If it boots, install one board or cable at a time to determine where the problem is.

1st beep = console controller initializing

2nd beep beep = audio controller initializing

3rd beep beep beep = options board initializing (if installed)

these beeps do not signal the board is working properly, just that it initialized (powered up) properly.

[ProTech]

Good deal dude
i would still exchange that motherboard in 9 & 10 again.. I have seen motherboards not boot from brunswick..

I have seen that also.

Does the Console reboot after "Clearing NV"? Check the software version of your Frameworx, you can check directly at the console or from the desk [Lane Status] [Tasks] [Lane Details], all consoles should be the same. (Ours is 6.3.0). I would be suspicious of the hard drive and / or the I/O. Try swapping the Hard Drive and I/O together and see if the problem moves.