#Gem flipclock rail how to#
#Gem flipclock rail install#
#Gem flipclock rail update#
#Gem flipclock rail code#

Then advance the mechanism by hand using the setting knob to work in the lubricant. Add a couple of drops at each location where the drums contact the axle. Lubricate the flip card spool wheels at the main metal axle prior to refitting the motor. Move your attention to the flip card mechanism. Is/was it lubricated? If it was or is, strip down the gearbox, clean down all the gears and re lubricate all the gears with a light plastic friendly lubricant such as clock oil. This indicates to me the possibility of excessive drag/friction somewhere within the clock. The motor unit in your report seems to run happily without a load, ie when not driving the flip card display. Your report back seems to indicate to me that the fault presents once the motor is paired with the readout mechanism. I have a theory, as I don't own a tuning fork clock it is only a theory on what might be going on here. Is there anyone on this forum with some kind of experience with these clocks? I would love to be able to fix it, but opening up the casing of the motor already looks like a possible horror-story to me :-) Replacing a capacitor is something I will be able to do, once I have located the correct culprit and have sourced a correct replacement for it. These clocks are actually quite sophisticated as far as the technology behind it goes.Īttached a link where you can find more info on them, also someone who suggests a method of repairing them and also has a suggestion of why they break down. When I first came across this clock, I thought that it had something to do with playing music, but since then, I have learned. It did work, for several hours and after that, I can only get it to start and stop after max 2 to 3 seconds :-( This one, I (unfortunately) bought as a working specimen.

#Gem flipclock rail how to#

If you want to learn how to set up scheduled tasks using Heroku, check out their scheduler's documentation here.I owned one of these (I believe a yellow one) years and years ago and because that one was working perfectly, I never bothered to look inside. To learn more about the Cron, check out the wiki here and a useful guide here. To learn more, check out the documentation here. This was just a brief overview of whats all available with the Whenever gem. The Whenever gem allows for easy manipulation of the Cron from a rails backend. Once you have your tasks defined and your crontab updated, keep an eye on your cron.log file to view the changes every time a cron job runs.Ĭron is a very useful tool that allows for defining and running scheduled tasks. You can also clear your crontab by running this: To make sure it worked, run this to view all current cron jobs:

#Gem flipclock rail update#

Read the documentation to find out how.Įvery time you make a change to the schedule.rb file, you must update the crontab with the newly changed file in order to implement the changes. The whenever gem also lets you define your own job types. The command found at that file path will now run every 1 minute. Now, before starting to add tasks, it is good to add these lines to the top of your schedule.rb: If successful, you will find a schedule.rb file inside of your config folder. Once you have installed the whenever gem, you need to create a special ruby file called schedule.rb that will house our crontab.

#Gem flipclock rail install#

To set up the whenever gem, you must first install it or add it to your GemFile.

#Gem flipclock rail code#

So now that we know a little bit about cron jobs, how do we use them with our rails backend? Well, lucky for us, there's a ruby gem that sets up cron and translates ruby code into a cron table for us. This equates to it running at 1:05, 1:10, 1:15, so on and so forth for the hours 1, 2, and 3. This means that the cron job will run and print 'hello world' every fifth minute of the first, second, and third hour. So, for the minutes, this cron job has */5 and for the hours, it has 1,2,3.

Enter fullscreen mode Exit fullscreen mode