Phonoland

So quick summary leading up to this...
Ive been working on my seeburg M100C to be fully functional. I had it mostly working properly on free play (a few selections didn't do anything, but 90% of them selected properly, went to pickup a record, played). I had an issue with credit and the coin mechanism. Part of this is that I knew the coin switch was broken. It had been damaged previously. I purchased a new one and soldered properly to the wire/plug to connect to the rest of the mechanism. When I plugged it in and turned it on, it made a bunch of noise that didn't sound right. I turned it off. Put it back into free play and it wouldn't select for a bit.

After checking all my connections and just leaving it on free play, and deciding to forget coin operation, I got it to select properly again, but instead of the mechanism going to the spot of a 45record and picking it up and playing, it scans continously 4 or 5 times, and THEN eventually picks a record up and plays.

Since the machine sat for a few weeks before attempting my repair, and I didn't test it out again beforehand, I'm not sure if this is related to my screw up with plugging in the coin mechanism, or if it this is a separate issue that just occured on its own.

I'm not worried about coin operation at the moment. Does anyone have any ideas though why it scans back and forth 4-5 times and then picks up a record? Sometimes it just does it once, but usually back and forth multiple times.

HELP!

On a side note, thanks to everyone for all the help up to this point. I'm also looking through Ron's seeburg mechanism guide for answers.

Also of note, while the mechanism scans, the portion that holds a record rotates as if its playing and noise comes from the speaker. Ive been reading that there is a mute circuit that should prevent this. I dont remember this happening before this continuous scanning problem occurred, but maybe it did.

Hi,
Thanks for buying the guide. If you will read the "sequence of operation Mech over view", and the "electrical sequence of operation for 100 selection mechs", you will see that there is no connection between the pricing unit plug and the mechanism scanning. Your "buzzing" in the CCU was simply because you have miss-wired the plug. Check the schematic for the common wire and each coil , and wire it that way.
As for the scanning--it simply means one or more of the pins in the SA Unit is partly pulled, or your sensor is not lining up, or, your "W" contact is not making good contact. One other thing can cause this--a "magnetized" Play Control Relay.
Ron Rich

I figured it must be wired incorrectly, but I wired it up exactly the same as the switch before. Double and triple checked. I inadvertently made a selection at that time too and heard a similar noise from the selection control next to the CCU on the main board. That's aside for now.

Anyways, prior to this it was reliable in regard to scanning straight to the record and picking it up to play. My thoughts from reading the book were possibly an issue with the relay. How would one "demagnetize" a magnetized relay? If not a magnetized relay what would be the mostly likely, or first cause to look into, for this to suddenly occur when previously otherwise fine?

Thanks.

- Brian

Hi Brian,
What I would do (with the power OFF) is remove the cover on the stepper portion of the WSR, and look at the relay, when it's scanning--to determine if it is energized, CAREFULLY pull up on the armature ,withOUT touching the relay blades ( which have line voltage on them !). If energized, you won't be able to pull up, without a "fight". If magnetized the armature will stay up--. If energized check ALL 100 pins--one is probably partly, in the selected position. Find out what's causing it and let us know- Ron Rich

So when I arrived home last night, I checked all the pins. None appears to be in a partly selected position but I made sure anyway. Then I tested the juke out. It did the continuous scanning twice, but rather than 4 or 5 times back and forth, only twice. After that, I played 7 or so records in a row without having any issues. I will test it again this later this week when I have a chance and see if it's consistently working again or scanning continuously.