Last modified: 2023-08-31 19:49:16
2023-09-01 >I'm reading "A practical course in horology" by Harold C. Kelly with the aim of making my own watch movement.
On page 25, on the topic of determining the thickness of a mainspring, step 3 is "measure the inside of the barrel and divide by 12.5" - but where does 12.5 come from?
When I make a watch gear I turn a blank on the lathe and then transfer it to the 4th axis on the milling machine to cut the teeth. Moving it between machines introduces a concentricity error of about 0.3mm. Is this caused by the chuck register on the 4th axis being off-centre, or is it just unavoidable? I should try re-cutting the chuck register, and failing that develop a workflow for using the dial indicator to measure the high spot, and a perl script for correcting the error.
I need to develop a workflow for crossing out tiny gears. Either a high-speed spindle for the milling machine, or just do it on the router. Probably the router is fine as it is such a tiny amount of material to remove.
I need a way to drill tiny holes in gears on the lathe. Probably a pin vise that I can put in the drill chuck, but I bought a set of pin vises before and they are very poor quality. Either get better ones, or decide on a drill size and make a collet (but how will you drill the hole in the collet?!)
I need to work out how to make escapements. Possibly continue experimenting in FreeCAD until I have the broad principles figured out, and then adapt the oscillating engine simulator into a pin pallet escapement simulator.
Meshmill still needs to cut helical paths in rotary mode, and I need to sort out the UI (i.e. hide irrelevant fields) in rotary mode. And I need to make the "origin" offsetting stuff work in rotary mode.
It would be cool to be able to load in an STL of the "stock", and have it generate a starting heightmap from that to feed in as the read-stock of the first job. Slightly more annoying than it sounds as you need to specify the dimensions independently. Maybe I should move away from PNG heightmaps and use a custom format.
The ETA calculation seems good, but the delta time was miles off. What is up there?
Needs to automatically update reference route.
Need to make a silencer bracket, and maybe fit the new handlebar grips.
When the foam fillers arrive (why haven't they arrived yet? I paid for Parcelforce 48, 6 days ago!), need to fit the flashing against the house, then barge boards around the low edge, then move on to the interior.
Need to sell the Rekluse auto-clutch.
Related to the Bangle.js commute timer, I kind of want to make a generic OpenStreetMap viewer
that lets you input JSON and plots the points in the view, and lets you click points and export
JSON. It's like a super-MVP GIS system for people who aren't interested in GIS. Basically like
the embedded OpenStreetMap UI for Waypointer Moto, except general-purpose. Base it on
the hacked version in ~/commute-timer/editor.
Maybe such a thing already exists, but I can't find one.
This page gives a description of a JSON format: https://wiki.openstreetmap.org/wiki/OSM_JSON
But I would probably be looking at a simpler format than that. Just something like what the Waypointer Bangle.js apps use:
[ {lat:123,lon:123}, {lat:123,lon:123}, ... ]
The OSM JSON format is close enough though if there is a straightforward viewer with import and export.
2023-09-01 >