Andy

A bit more info would help !!!!!!!!

Emgee

Hi Andy… A good question…!

The reason why synchronisation of the two Arduino's is necessary is that the two motors (one drives the leadscrew and the other the Spindle), need to have their relative speeds constant, notice the term 'relative' .

For example if the required ratio of Spindle speed to Leadscrew speed was 1:4 then for 1 turn of the spindle there would be 4 turns of the leadscrew ; if the pitch of the leadscrew was 1mm then 4 turns would produce a pitch of 4mm on the work.

Now if the Arduino driving the leadscrew motor began to increase or decrease its speed relative to the Spindle motor speed, the ratio of 1:4 is altered and the required pitch on the work would no longer be 4mm.

It is an unfortunate fact that no matter how good the clock circuits are in any two microprocessor systems they will not keep in sychronisation if they are completely separate systems.

The Arduino can only provide a minimum clock pulse period of 1microsec duration, using two Arduino's the clock pulse rates will most certainly alter over time which is the root cause of the problem, and so by using only one clock for the two Arduino's the problem of clock drift is eliminated.

It might be thought that the difference in speeds would be so small that it really wouldn't amount to much, however when the work requires long pitches to be made all the errors begin to add up, If you have two Arduino's just try the Blink program with a 500ms delay period for switching the Leds on & off… it won't take long for the two Leds to be out of sync.

Hope that helps, if you need any more info I am only too glad to help.

rgds..Bob.

I had no idea why you would bother synchronising 2 Arduinos and certainly wouldn't have dreamt of connecting the oscillator pins together like that. Actually a fair chance of them not working correctly with this arrangement.

What accuracy are the crystals? And what accuracy do you think is required?

Normally crystals are so accurate you'd have difficulty measuring them with normal instruments. Sorry to sound negative but it all seems rather bizarre.

Normal micro crystals are 10’s of ppm

10 micron in a meter?
Btw ever read the step “error” figue for a stepper?
Yes 200 per rev..but are they equally spaced..

Edited By jason udall on 14/12/2015 18:56:26

36 pence to replace the ceramic resonator fitted to some Arduinos with a 30ppm crystal – 0.003%

.003% sounds very accurate, so I wondered what this would mean in real life. So lets take the spindle as the reference, not disengaging the half nuts and cutting 2" of 40 TPI thread. If the leadscrew is running slow by the .003%, then after the first cut the linear position of the tool would be .003% short of where it should be. i.e. towards the tailstock if cutting towards the chuck. Then running the lathe backwards to get back to the starting position, would also mean that the carriage would run 2" – .003% towards the tailstock which neatly coincides with its starting position. So the error is non accumulative. So the thread will compress by .00006" over 2" this would be extremely accurate!

If the lathe could not reverse, so the half nuts have to be disengaged, then the error is accumulative, both on the cut and the number of spindle rotations for winding the carriage back. So if you can wind the carriage back four times faster then the cutting speed and you need 5 cuts to complete the thread then the total error would be 5 times 1.2 times 2" times .003% , still not a lot. But if the spindle was left running half way through the thread cutting exercise while you have a cup of tea, the errors would become gross.

Frank

Bob's use of a single crystal to drive two oscillators was new to me, but hey it worked!

Using two Arduinos rather than one is apparently easier because of a limitation in the standard Arduino library, which is that the tone() function can only be used on one output at a time. Bob's project needs two outputs.

There are alternatives that don't require board surgery.

It is possible to synchronise two Arduinos using the code below, but they drift apart over time. I tested the code using a Duemilanove and a Mega2560. An oscilloscope shows that the Arduino's start exactly in step but drift apart thereafter. For a nominal 400Hz the Mega2560 outputs 400.7Hz whilst the Duemilanove outputs 400.64Hz. Their 16000kHz crystals are oscillating at slightly different frequencies (16000.30kHz and 16000.48kHz). For Bob's application I doubt this would matter, but his solution fixes that problem.

const int input_sync_pin = 6;
const int output_sync_pin = 7;
const int tone_out_pin = 8;
const int led_pin = 13;

void setup() {
// put your setup code here, to run once:
pinMode( input_sync_pin, INPUT_PULLUP );
pinMode( output_sync_pin, OUTPUT );
digitalWrite( output_sync_pin, LOW );
while ( digitalRead( input_sync_pin ) == HIGH )
{
; // Waiting
}
// Synchronised now
pinMode( led_pin, OUTPUT );
digitalWrite( led_pin, HIGH );
}

void loop() {
// put your main code here, to run repeatedly:
tone( tone_out_pin, 400 );
}

Connect GND to GND, and pin 7 on one to pin 6 on the other, twice.

Another way is to use one Arduino to produce two tones at the same time. This is possible by installing the third-party library at *LINK*. The library needs a small fix before it will work. After installing the library, find the file "Tone.cpp" and edit it. Change the line reading "#include <wiring.h>" to "#include <Arduino.h>" Don't forget to tell the Arduino IDE to use this library.

The tones produced by this example program are based on the same clock and are closely synchronised.

#include <Tone.h>

Tone t1;
Tone t2;

int f1 = 500; // Hz
int f2 = 1000; // Hz

void setup() {
// put your setup code here, to run once:
t1.begin(6); // Tone1 Output on pin 6
t2.begin(7); // Tone2 Output on pin 7

t1.play(f1);
t2.play(f2);
}

void loop() {
// put your main code here, to run repeatedly:
// Example increases Tone2 by 1000Hz after a second. Resets to 1000Hz when the output is higher than 65kHz
// Tone1 stays at 500Hz. The two tones are output on different pins at the same time.

delay(1000); //mS

f2 = f2 + 1000;
if ( f2 > 65000 )
f2=1000;
t2.play(f2);

}

Microcontrollers like the Arduino offer lots of opportunity to model makers. It's probably heresy but I think a well-built steam engine using an Arduino with sensors to control valve events and boiler pressure etc would be rather more efficient than a mechanical equivalent. I wish my workshop skills were up to it!

Kudos to Bob for having a go.

Regards,

Dave

Bob Mc

May I just say thanks for the article

This discussion about Arduino synch issues is interesting, but the big thing for me is that you have produced something that successfully replaces change-wheels.

Good on you, Sir.

MichaelG.

.

P.S. for convenient reference **LINK**