[chp]

First, contrite_wheel thank you for developing this software. I basically scrapped my other timegrapher apps in favors of yours. I read the links you posted, and it looks like you ran into people with HUGE egos. So, thank you for your perseverance developing this software.

Instead of using a clip, I decided to go another route. Here is my setup - a notebook running your software, a box of electronics to provide adjustable gain and filtering, and a watch holder modified with a piezo speaker as a sensor.

Here is a picture of my amplifier box (with on/off switch and gain knob) and my modified watch holder.

Here is a zoom of my modified watch holder. The piezo speaker fits in between the holder's rails. I superglued a small plastic cylinder from a mechanical pencil to the speaker to act as a pickup. The plastic cylinder contacts the watch to pick up the movement's vibrations and won't scratch the watch.

Here is a picture with the piezo speaker moved to the side. I used an arch shaped piece of foam with a flat top inside to the holder to push the piezo speaker's pickup against the watch. The holder's spring and bolt fit inside the arch, and the top of the arch is flat to mate against the flat back of the piezo speaker.

This holder will allow you to balance the watch in 5 of the 6 measurement positions. When I need to take a measurement with the side of the holder with the bolt and wingnut, I'll set it against something or just hold the holder in that position. I'm working on a device that will let you rotate the holder in all 6 positions.

When I regulate my watches, I place the watch face down in the holder and open the back. I make the adjustments and see my changes on the timegrapher. For example, if your watch is running 20 s/d fast when you wear it and face down measures +15 s/d, you can adjust the face down s/d to be -5 s/d and this will get you close. For this example, I'd actually adjust face down to -4 s/d because I regulate my watches to run 0 to +1 s/d.

I made this setup well over a year ago, and I have to dig up my schematic for my amplifier. I think I had three or four filter/gain stages. The gain of the first stage is set internally by a potentiometer. The final gain is set by the knob on the outside. I used ultra low noise op amps. I didn't need 3 or 4 stages for the gain, but needed them to provide filtering from outside electrical and mechanical noise. I think I used a multi-pole band pass filter from ~500 Hz to 20kHz. This filtered out the 60 Hz and 120 Hz electrical noise and a lot of the room noise (talking, TV, etc.).

I used a quartz watch to perform the calibration as instructed. Then, (here comes the anal part), I checked the calibration of the quart watch over a long period of time and made a tweak to the initial calibration. This is a small ~0.2 s/d tweak to the initial calibration.

If there is a next version, is it possible to:

1) Select the integration time from several choices like the choices from a standalone timegrapher.

2) With a longer integration time, can you display the s/d with one number after the decimal point (e.g, +1.2 s/d).

 

[chp]

Hi contrate_wheel

I have now received the Frederick Constant Analitics Clip and here is a very short review. (If anyone wants more information please PM me and I'll try and respond with a post here.)

Firstly the app
The app is called SwissConnect Analytics and it's available from the Play Store.
Before one can use the app one needs to create an account and authenticate the FC clip number.
All the data is stored on the Cloud and the phone must be connected to the Cloud to store your additions.
It is a very basic app that is slow to operate but, with the clip it does work.
It has stuff that I'm not interested in like
Purchase Price
Proof of Purchase
Last Service etc
However, others might think that is good.
The app design IMHO is cluncky.
In particular the menu is minimalistic. There is also a (reasonable) requirement to SAVE the readings BUT the Save button is out of the window and I have a 6" screen.
It took me a few goes to figure where my readings went.

The app has a list of manufacturers and models but I would have thought that as they are measuring movements they would have an inbuilt list of calibres with the associated vph and lift angles etc. That is not the case but these can be modified by the user.

How does it work?
On my phone it seems to work fine.
There is a 30 second default measurement time and the app does its thing and it shows a trace of the variation in timekeeping in spd.
Once complete it allows the user to add a description and this is where one needs to add the position of the measurement.
I was expecting that there would be defaults for things like Face Up, Face Down, 3 up, 3 down etc but no! What novice designed the app!!

As mentioned above, the phone needs to be connected to the web to save readings and any new watches added.
Is it a replacement for tg software?
Not in my opinion.
However, If you need to check some watches that maybe you are thinking of purchasing then this will likely be a simple and compact option.
With a bit of clip repositioning it worked on three mechanicals that I tried. (It does not work on quartz)

Other things to note.
I tried using the FC clip on my computer but with no success.
It may be that my Flintstone computer doesn't talk to the clip but the computer and tg work fine with a straight USB web cam mic.

HTH

I've used two android apps in the past: WildSpectra and TickOPrint.

WildSpectra only provides the s/d (no beat error or amplitude). It provides three averages: 5, 30, and 60 seconds for the s/d reading. It provides a numeric valves for each and a graphic display using pointers on a semicircle display. You can adjust the input gain and the bandpass filter endpoints. This was my main app. When the three pointers converge on a s/d you have a pretty good indicator. The only issue I saw was that when I was measuring small s/d every so often the 5 second pointer would move from +5 s/d to -10 s/d, for example, then the 30 second pointer would follow later and the 60 second pointer would bump somewhat later. It was like something ran in the background (like GooglePlayService) and took some resources or the phone's clock was not very stable and created an instant measurement error. I saw the same effect on two phones. On the rooted phone, I changed the clock freq to be fixed at different frequencies and it didn't help. MY guess for larger s/d you might not notice this. Once you recognize the blip, you can just stop and restart the measurement.

TickOPrint provides the dot display, numeric s/d, beat error, and amplitude in the full version. You can change the averaging time. The gain is not adjustable in the latest version. My issue was that I would run the app, and a s/d would converge after a minute or so. Then I would stop and start again (not close and open the app), and I would get different results. Also, the beat error was not consistent. For example, the watch from my previous post above has a consistent 0.1ms beat error on TG Timegrapher, but on TickOPrint it would vary from 0.1 to 2.5 ms. I was feeding an extremely clean signal and I was adjusting the gain of my amplifier, and I could not find a sweet spot to get good consistent results.

Tg Timegrapher gave me consistent results. I also ran the calibration several times on different days with my netbook cold and running for a while and got consistent calibration values. This is why I stopped using my other apps.

 

[chp]

I was asked why I shoot for a 0 to +1 s/d regulation. I typically measure the s/d in three or four positions. If you wear you watch on your left wrist, I measure stem down, face up, and 12 down. Sometimes, I use a new fourth position where 12 is down by 45 degrees. If you are a desk jockey, this is a common position for your watch during the day. These 3 or 4 positions are pretty consistent with the behavior when you wear the watch. I shoot for slightly positive s/d day to compensate for movement of the watch causing it to slow down slightly. Also, having a slightly positive s/d allows easier setting of the time after a while. You simply pull the stem out to hack the seconds and then press it back in to re-start. If you run a negative s/d, you have to move the minute hand which is more of a pain.

 

[chp]

A bug that was causing crashes on Windows was identified and fixed. Might help those who want to try on that operating system. I've made a 0.6.1 release with the fix. You'll still have to compile yourself on Windows unless someone figures out how to make an install package.

Fedora Linux can just add my copr repository, dnf copr enable tpiepho/tg-timer and new versions will show up in the package manager.

Could I please get some help compiling your version for windows. Everything went smoothly with no errors until I tried running tg-timer from my MSYS64 folder and I was missing some dll files. I copied the dll files from the Program Files (x86)/tg-timer folder and then got the “application was unable to start correctly (0xc000007b)” error. I copied my newly created tg-timer.exe to my Program Files (x86)/tg-timer folder and got the “application was unable to start correctly (0xc000007b)” error. My existing tg.exe (0.5.0) runs fine in the Program Files (x86)/tg-timer folder, but won't run if I copy it to my MSYS64 folder

I new to the windows compiling stuff. Could you please give me some suggestions.

 

[chp]

Have you tried launching it from within the MSYS64 shell that you compiled it in? From the shell prompt after the successful compile, trying typing ./tg-timer.exe

Thank you for your help.

I didn't. I just tried and nothing happens. No errors, no missing dll's like before. I guess I complied it incorrectly? There were no errors flagged when I compiled it.

 

[chp]

Thank you for your help.

I didn't. I just tried and nothing happens. No errors, no missing dll's like before. I guess I complied it incorrectly? There were no errors flagged when I compiled it.

I deleted everything in my home folder and restarted. I'm missing two packages now: gtk+-3.0 and glib-2.0.

Reinstalled Msys2. I now get:

configure: error: Package requirements (gtk+-3.0 glib-2.0) were not met:

Package 'gtk+-3.0', required by 'virtual:world', not found
Package 'glib-2.0', required by 'virtual:world', not found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables GTK_CFLAGS
and GTK_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.