I thought within 1% or so was good enough and was happy with
that. Within 50ns is really good, is it complicated to implement
on micro controller?
For machine control 1% is probably good enough. But I also have some
other uses with high speed (100MS/s) adc's in mind. These
> CANopen sounds interesting. I'll have a look at it, a quick scan at
> wikipedia also shows IEEE 1451. It would be really nice if a drive would
> just present itself and all the variables would be available as pins.
> Using existing and open protocols is definitely preferred.
I have looked at pro
> As far as I understand PTP protocol is for very accurate clock
> synchronization?
>
> Which is exactly what I want. Many microcontroller and network cards have
> support for this, it's also called IEEE 1588. There even are switches
> which re-timestamp so the jitter caused by the sw
As far as I understand PTP protocol is for very accurate clock
synchronization?
Which is exactly what I want. Many microcontroller and network cards have
support for this, it's also called IEEE 1588. There even are switches
which re-timestamp so the jitter caused by the switch can
> Well actually not. A full period of jitter then using average
> time over 100 samples is 1% or about if not exact 1/n=(100/n)%
> of jitter.
>
> The ethernet controller of the processor has a clock with a very
> fine-grained control of the time. Currently this clock takes 3 sec
Well actually not. A full period of jitter then using average
time over 100 samples is 1% or about if not exact 1/n=(100/n)%
of jitter.
The ethernet controller of the processor has a clock with a very
fine-grained control of the time. Currently this clock takes 3 seconds
t
> I've been working on an ethernet controlled servo drive for some time now.
> This drive uses RTNET and Xenomai-3.0.3 for the real-time communication.
> The current control loop is on the drive, but the position control loop
> is on the PC.
I also have ethernet servo drives.
> ...
> Since the d
