Great post Jim. Believe it or not, I had a similar experience with an ERC II (electronic range controller) when I worked for GE. We absolutely could not understand why our on-board clock was losing time. Not much time but it would lose approximately 10 to 15 seconds per day. We contacted Robertshaw and they were baffled also. One of our engineers, a EE type, had come to us from Louisville Power. He made several phone calls and discovered the problem was just as you mentioned an input of 50 to 55 Hz instead of 60 Hz. That solved our test problem. Again, great post
krruss wrote: "A synchronus motor does have brushes, and requires a dc voltage on the rotor coil to lock it to the system frequency. Since it does have brushes, and requires a separate power supply for the rotor, they are actually not very common."
Wikipedia suggests that there are several varieties of synchronous motor. One type, DC-excited, is produced in sizes greater than 735 W. Three other types of non-excited motors, reluctance motors, hysteresis motors, and permanent magnet motors. do not use DC excitation and do not have brushes. They rely on either induced rotor current or permanent magnets in the rotor. Each has different self-starting characteristics.
I'm not sure it was ever common practice, but I don't really know. What was mystifying to me was how they were able to move the whole grid in a controlled fashion.
Someone mentioned the tendency for slower generators to be 'pushed' by faster ones. So perhaps there was a self-synchronizing effect across the grid. The freq. shift must have been quite slow. I've got a contact at Public Service Energy Group who would be in a position to know what happened.
I've designed dozens of clock-based appliances, and they all used line cross for a time base. Most of it is about money; if it plugs into the wall then line cross is free and a crystal costs money, a lot of money. Then there are some practical aspects of using line cross; the software can determine 50Hz or 60Hz using the microcontroller's internal oscillator, multiplexing the display can be synced to the line to prevent flicker with fluorescent lighting, if you know where line cross is you can phase fire triacs, you can "walk" relays by firing them at different parts of the linecycle to minimize relay wear and you know when the power has been interrupted long before VCC fails because line cross has ceased before the power supply bleeds off (handy for saving stuff in EEPROM and shutting the system down nicely).
My parents had a synchronous clock on the mantel when I was growing up in the 40s & 50's. It kept perfect time, but whenever we had a power outage the clock had to be reset and a small knob on its back had to be rotated to get it going. It was a common prank to hold the knob to stop the clock at noon, and then spin the knob in the opposite direction to make it run in reverse. We could tell what time it was by mentally transposing the numbers on its face, but it used to drive my old man crazy.
Your proposed "experiment" could be flawed (depending).
Putting two oscillators of the same frequency (mechanical or electronic) near each other will demonstrate a strange affect. They will sync with each other. This gives an additional edge to the two time pieces tracking together in the same environment.
The experiment would be valid if the two time pieces are verified to track closely (but not exactly) with same temperatures - but physically separated enough to eliminate this effect.
The syncing effect is more pronounced with certain types of electronic oscillators. But can be demonstrated at some level in nearly all types.
I suspect using watches with metal cases and a modest distance would provide most of the required isolation to make the experiment valid.
Festo's BionicKangaroo combines pneumatic and electrical drive technology, plus very precise controls and condition monitoring. Like a real kangaroo, the BionicKangaroo robot harvests the kinetic energy of each takeoff and immediately uses it to power the next jump.
Design News and Digi-Key presents: Creating & Testing Your First RTOS Application Using MQX, a crash course that will look at defining a project, selecting a target processor, blocking code, defining tasks, completing code, and debugging.
Focus on Fundamentals consists of 45-minute on-line classes that cover a host of technologies. You learn without leaving the comfort of your desk. All classes are taught by subject-matter experts and all are archived. So if you can't attend live, attend at your convenience.