Definition of beat error - Page 3

# Thread: Definition of beat error

1. ## Re: Definition of beat error

Originally Posted by Roland Ranfft
. . . . But I believe too exact definitions prevent people from reading posts. . . . .
They also afford the maximum in wiggle room.

2. ## Re: Definition of beat error

Originally Posted by Roland Ranfft
Hi there,

Here the simple formula (with ea = error angle, et = error time, la = lift angle, lt = lift time):

ea = (et/2) * (la/lt)

Regards, Roland Ranfft
Dear Roland, your formula is certainly correct. The problem, as you can
see, is in the inputs. In my post, I made that angular velocity depend on
the amplitude, you make it depend on the lift time. You see: the amplitude
and the lift time are basically the same thing. The lift time is the time
between the first and the third sound of the escapement. It is absolutely
clear, I believe, that as soon as you have the lift time you can compute
both the amplitude and your angle quite easily. As I was trying to explain
a couple of posts ago, if the audio is bad, one can fail to detect the
three sound clearly, or mistake, say, the second sound for the first. No
sounds, no time between the first and the third sound, no lift time. When
this situation occurs, it is often still possible to get good values for
the rate and the beat error (the error time of your formula).

Yes, your formula is Apple II stuff, but, sir, could you tell me please
where the Apple II gets his lift time from?

mathematician, amplitude and lift time, for instance, are the same thing.
Of course they are different numbers, but related via a trivial identity.
For an engineer, I see, it is not the case. I say "I don't trust the
amplitude!", and you answer "Use the lift time!". Of course I know how to
reduce one to the other, actually it is almost an insult to me suggesting
that I don't see a linear proportion (or that I don't see that the
derivative of sine is close to one for small angles). Point is that I say

3. ## Re: Definition of beat error

There is no point of presenting mathematical beat error in degrees. Mathematical beat error is only guess, but gives good idea of the symmetry.

If horological beat error is zero, when balance is at rest and roller is on the line drawn between balance wheel pivot and escape wheel pivot, mathematical beat error CAN be different than 0.

4.

5. ## Re: Definition of beat error

Originally Posted by kanikune
. . . . If horological beat error is zero, when balance is at rest and roller is on the line drawn between balance wheel pivot and escape wheel pivot, mathematical beat error CAN be different than 0.
hmmm . . . . geometric symmetry . . . .. . with regard to the pallet fork, the pallet stones' reach and the fork's banking and the actual force manifest by the hairspring in both directions . . . uhhh . . .

6. ## Re: Definition of beat error

Dear Ronald, I make a screenshot to better illustrate what I was attemting
to say. This is my program, as it is now, running on a watch (AS1950
movement) that yours truely has butchered countless times. The watch was
held in my hand, about five centimeters in front of my laptop. The data is

On the left you have a simple paper strip like diagram. On the right you
see a red sad watch, this means that the program is not picking up a watch
right now, and the data diplayed is what it was at the time the watch was
last detected (I took it away in order to make the screenshot). Then you
have the two waveforms. These waveforms are updated in real time, but they
result from a messy process of filtering and integration, which actually
adjusts its integration time dynamically, so they don't look crisp but
that is the best that I can do for now. As you can see the program detects
the waveforms very well and aligns them correctly in their windows. The
rate and beat error displays as well as the waveforms are also very
stable (but you would need an animation to see this, sorry).

The waveform windows are graduated in milliseconds and in degrees of
amplitude, so I can say that this watch has about 280 degrees of amplitude
(confirmed by the fact that both the waveform of the tic and that of the
toc suggest the same amplitude). However, as you can see, the first sound
is very very weak, possibly due to the butchering that this watch has
suffered, and no algorithm can be really expected to get a reliable number
out of this mess.

7. ## Re: Definition of beat error

Hi there,

Originally Posted by contrate_wheel
Point is that I say "Peasants have no bread!", and you answer "Let them eat cake!".
Well, if your noise analysis doesn't resolve the "ticks" marking start and end of pallet lifting, I really can't understand why you are interested in the definition of the beat error. I would then of course still trust in the displayed rate, but my trust in the displayed beat error would be more than limited, due to the differing noises in both directions.

Edit: Oops, I had a phone call in between, and uploaded my post without reading your last. Of course the first noise is weak compared with the big bang at the end. And I can ony say what I did when considering to realise a cheap timing machine many years ago (pre smart phone age): I optimized the gain for every escapement noise individually for better distiction between the noise to be detected, and background noises. This allowed pretty exact trigger moments even with a poor mic.

Regards, Roland Ranfft

8. ## Re: Definition of beat error

Originally Posted by contrate_wheel
Dear Ronald, I make a screenshot to better illustrate what I was attemting to say. . . . . .
So no lift angle input?

9. ## Re: Definition of beat error

Originally Posted by pithy
So no lift angle input?
Pardon me, I don't understand. The lift angle input is at the very top of the window. You have "bph: guess", i.e. autodetect, and "lift angle: 52".

Of course I need the lift angle to produce the amplitude graduation. Did I ever claim that I would have done without it? That is clearly not possible.

10. ## Re: Definition of beat error

Originally Posted by contrate_wheel
Pardon me, I don't understand. The lift angle input is at the very top of the window. You have "bph: guess", i.e. autodetect, and "lift angle: 52". Of course I need the lift angle to produce the amplitude graduation. Did I ever claim that I would have done without it? That is clearly not possible.
I was viewing from a phone screen and the "52" is quite small.

Thank you for helping me locate it on your screenshot.

Persecution complex is a common diagnosis for many of the watches submitted here for evaluation.

11. ## Re: Definition of beat error

Originally Posted by Roland Ranfft
Hi there,

Well, if your noise analysis doesn't resolve the "ticks" marking start and end of pallet lifting, I really can't understand why you are interested in the definition of the beat error. I would then of course still trust in the displayed rate, but my trust in the displayed beat error would be more than limited, due to the differing noises in both directions.

Regards, Roland Ranfft
Dear Ronald, you are clearly free to trust what you like, and, if you have
access to professionally built hardware or software, by all means, that is
going to be better! However I will tell you now why you can trust my beat
error, and for that I need you to examine the screenshot again.

Now, you see that the two waveform appear aligned one over the other (you
have the graduations to make sure of this). The algorithm first computes
the beat error, and then uses this to "zoom in" on the two waveforms. Now,
in your mind, move one of the waveforms to the right by one millisecond:
do they still look aligned? Very definitely not. So you can tell that the
alignemnt is much more precise than one millisecond. How much? Well, move
one of the waveforms by two tenths of a millisecond: do they still look
OK? Yes, acceptably yes. So I know, almost by logical necessity, that my
beat error, in this case, can not be off by 1ms, but it might be off by
0.2ms.

You see, this is one of the reasons why I like my approach. Suppose that
one of those smartphone apps gives you the wrong answer, can you tell
this? No, because all that they display are numbers, and maybe some dots.
(Granted these apps are possibly much better programs than mine, here I am
discussing only the approach.) Now, if my program gets its rate or its
beat error wrong, the waveforms appear immediately, in real time, either
out of aligment (if only the beat error is wrong) or completely messed up
(if also the rate is wrong). So the user doesn't have to trust it, he can
see with his very eyes how well (or badly) the algorithm is working.

Now to how I get the beat error without detecting the pulses. This is the
idea: take the tic as a whole waveform and try to match it to the toc as a
whole waveform, and then compute the delay in time that gives you the
better match. This must be the tic-to-toc time, and from now you know how
to do the math. As a toc looks much more like a tic than like a Dirac
delta, this tecnique is much less sensitive to noise than the trigger
based methods.

Page 3 of 4 First 1 2 3 4 Last

There are currently 1 users browsing this thread. (0 members and 1 guests)

#### Posting Permissions

• You may not post new threads
• You may not post replies
• You may not post attachments
• You may not edit your posts
•