No second ball score...odd solution

[Pietenpol]

Never seen this one yet. SS chassis with Omega-tek/expander. Newer masking units with LED ball lights. Accuscore gold chassis, single pedestal bowlers terminal. Machine scores first ball and cycles. When machine cycles second time there is no ball light change and no score. I go to manually step the ball light from the machine and I can't get the second ball light to go on. Changing chassis and issue stays with machine. Rebooted scoring chassis and no change. About this time I notice that switching between left or right lane on the bowler terminal sometimes turns on both left and right lane leds. I pull the keyboard from the next lane and get the same result. I pull the board from the next lane and put it into the bad lane pedestal. Now the leds seem to work smoothly switching from left to right. I reset the lane and scoring works correctly, ball lights work properly. I put the bad board into the other lane and everything appears to work great there as well. My only guess is from sitting for 2 years the connections needed to be re-seated? Had never seen a ball switching issue caused by the terminal either.

[Tablejam]

I'm just going to say this.. ... WTF?

[Disturbed1]

Those darn gremlins at work again!

[keeth]

I'm just going to say this.. ... WTF?

I must second this unless it is a omega thing other than a cycle command or a fast cycle the accu dont boss around the machine.

[tomnimrosjoncar]

Some time ago I had a similar mystery issue with our Qubica scoring which seemed to be with the keyboard. Switched keyboards and interface between pairs to see where the problem went - and it went away never to return!

[triac]

I doubt that the scoring components had anything to do with the fix. This is why the parts you thought were bad worked in other pairs. This problem may rear its ugly head again at the most inconvenient time.

The machine controls the output to the second ball light even if the scoring is turned off. It is this output that is sent to the scoring interface to let it know what ball it’s on.

Most likely you have a bad connection to the chassis’s output since another chassis didn’t cure the problem. I’m thinking it was a coincidence that it just started working.