Frameworx. Scores slow to be displayed.

[HouseBall]

I have a pair of lanes where the scores sometimes takes awhile for the scores to be displayed. I don't think the issue is in the processor, because the timing of when the camera takes its picture is correct (checked when I hooked up the tester). The problem seems to be getting the information from the processor to the LGP. It might take a couple extra seconds to display the score, never display the score, or displays the score at the correct time. When it does score, the score that is displayed is the correct score. Here's what I've changed: Console I/O, Hard Drive, Motherboard, LLAN from pinsetter I/O to the console I/O. I can't seem to get the problem to move. I've been chasing this problem for awhile now, hopefully someone else has had a similar problem with a remedy.

Thanks,

Joey

[Brillion77]

Check your switch cluster mounted to detector. Be sure they zeroed correctly. Also, check gearbox clutch adjustment is at zero.

[Wookie8662]

I will go with the ball detector and cluster switches on this one.

A ball detect at 0 degrees (0 switch closed) initiates a scoring cycle.
These two conditions must be present for any scoring to happen.
If either of these signals are missing, or occur at the wrong time, it can cause all of the above you mentioned.

Edit: Also make sure the ball detect is not "cross-talking" with the pairs on either side (out of line detects/reflectors).

[Ted]

I think I'd go for changing the Video Processor board with another pair. When you see the tester plugged in, and it shows '0' closed when the machine stops, I think the scorer will have reset to accept another ball detect. Plus, you say it does display the right score. I'll vote for communications issues in the LLAN from the processor - or cable underground to the console (ball damage, rake rubbing it, rabbit ears rubbing it etc).

[drhookmec]

Joey, Is it the overhead monitor or the lower console thet is slow to display the score?

I had this problem recently and is was the remote video PCB for the overhead monitors.

[BrunsBoy]

Did you ClearNV this Pair, Sometimes the Ram it's so load that either stop scoring or scores slow, also this is on A-2 Pinsetters or 82-70's pinspotters?

[spareme]

houseball,

I agree with Ted on this one for changing the viedo processor board first.

[HouseBall]

When I try to troubleshoot this issue, I always look at the overhead (I never walk past the end of the approach to the consoles). I cannot be certain if it's just the overhead, but I imagine it's both because bowlers have to make the score correction (really "add" the score). I've not considered swapping video boards, but I'll give it shot on my next day in.

Thanks,

Joey

[drhookmec]

Joey, did you find he problem?

If you did post what you found maybe it will help someone else.

Tim