C
ColinD
Hi, Just signed up.. I'm ColinD from Jamma+
Just trying to sort a Roadshow pinball out.... and its giving me the usual dozer blade issues that come up and get talked about....
Ok, here what I can gather and understand......
You have a motor, which drives a cam that raises and lowers the dozer blade..... motor only drives one way....
The cam has a blade that interrupts two opto sensors, so that the cpu knows when the dozer is up , down or in between....
So... the cpu says.... raise the dozer, it might check that its already up via the up opto, but if not, turns the motor on, waits for the up opto to be interrupted by the blade on the cam.... saying its now UP.... and then turns the motor off....
Same in reverse.... CPU says... Lower the dozer, another check maybe if down, if not motor goes on, and then waits for the down opto to be interrupted.... and then turns the motor off......
Now... from Diagnotics , this seems to work fine.... Motor drives, Dozer goes up and down, and the opto's register ok....
But... It does not work properly during the game ?? (Yes... everything is enabled in the menus and factory reset etc)
Now I hear that there is a replacement opto board available.... which is going to cost about £50+taxes delivered from the USA.... and its supposed to work much better ??
I'm reluctant to buy this... as if it aint broken... why fix it ??? Can anyone shed any light on this please ? - Is it a software bug or something that doesn't take into account a bit of wear and tear etc ???
I'm thinking that there may be either some interference generated that causes false feedback and causes this to fail...
If I can't fix this, I might design a little add on board that goes between the optos and motor drive, and takes care of the issue automatically.... simulating the whole assembly, giving the right feedback to the cpu... and doing its own thing while de-bouncing the opto's etc.... but that's a last measure.... would be simple enough to implement though with a PIC microcontroller , a few components and a few lines of code !!!
So... whats the score with this then please ??
Thanks, Colin
Just trying to sort a Roadshow pinball out.... and its giving me the usual dozer blade issues that come up and get talked about....
Ok, here what I can gather and understand......
You have a motor, which drives a cam that raises and lowers the dozer blade..... motor only drives one way....
The cam has a blade that interrupts two opto sensors, so that the cpu knows when the dozer is up , down or in between....
So... the cpu says.... raise the dozer, it might check that its already up via the up opto, but if not, turns the motor on, waits for the up opto to be interrupted by the blade on the cam.... saying its now UP.... and then turns the motor off....
Same in reverse.... CPU says... Lower the dozer, another check maybe if down, if not motor goes on, and then waits for the down opto to be interrupted.... and then turns the motor off......
Now... from Diagnotics , this seems to work fine.... Motor drives, Dozer goes up and down, and the opto's register ok....
But... It does not work properly during the game ?? (Yes... everything is enabled in the menus and factory reset etc)
Now I hear that there is a replacement opto board available.... which is going to cost about £50+taxes delivered from the USA.... and its supposed to work much better ??
I'm reluctant to buy this... as if it aint broken... why fix it ??? Can anyone shed any light on this please ? - Is it a software bug or something that doesn't take into account a bit of wear and tear etc ???
I'm thinking that there may be either some interference generated that causes false feedback and causes this to fail...
If I can't fix this, I might design a little add on board that goes between the optos and motor drive, and takes care of the issue automatically.... simulating the whole assembly, giving the right feedback to the cpu... and doing its own thing while de-bouncing the opto's etc.... but that's a last measure.... would be simple enough to implement though with a PIC microcontroller , a few components and a few lines of code !!!
So... whats the score with this then please ??
Thanks, Colin