Skip to main content

Hacking an analog clock to sync with NTP - Part 4

Assuming the jumper wires from the clock are connected to pins D1 and D2 on the ESP-12, the following Arduino sketch will make it function as a normal clock that ticks every second:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
tickPin = D1;
os_timer_t secTimer;

// Triggered by system timer every second
void timerCallback(void *pArg) {
  tickOccured = true;
}

void setup() {
  // Setup GPIO outputs
  pinMode(D1, OUTPUT);
  pinMode(D2, OUTPUT);
  digitalWrite(D1, LOW);
  digitalWrite(D2, LOW);

  // Start system timer which triggers every second
  os_timer_setfn(&secTimer, timerCallback, NULL);
  os_timer_arm(&secTimer, 1000, true);
}

void loop() {
  if (tickOccured) {
    tickOccurred - false;
    tickPin = (tickPin == D1 ? D2: D1);
    digitalWrite(tickPin, HIGH);
    delay(100);
    digitalWrite(tickPin, LOW);
    delay(100);
  }  
  delay(250);
}

To be continued...

Comments

  1. You refer to D1 & D2 on your board, however I'm having trouble translating that to a normal ESP-12. Could you tell me which pins you have defaulted to using this diagram?

    http://simba-os.readthedocs.io/en/latest/_images/esp12e-pinout.png

    ReplyDelete
    Replies
    1. From this link:

      http://www.esp8266.com/viewtopic.php?f=21&t=1388

      I believe D1 = IO14, D2 = IO12

      Delete
  2. Thanks for sharing! I'm using this for an art project at the FB HQ.

    A few comments:

    Line 23 should be: tickOccurred = false;

    And in some places of the code there's a typo — you use "tickOccured" instead of "tickOccurred".

    ReplyDelete
    Replies
    1. Thanks for pointing out the spelling error. I have corrected it in the Github repo.

      Delete

Post a Comment

Popular posts from this blog

Update: Line adapter for Ozito Blade Trimmer

Update (Dec 2021): If you access to a 3D printer, I would now recommend this solution , which makes it super easy to replace the trimmer line. I have been using it for a few months now with zero issue.

Attiny85 timer programming using Timer1

This Arduino sketch uses Timer1 to drive the LED blinker: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 /* * Program ATTiny85 to blink LED connected to PB1 at 1s interval. * Assumes ATTiny85 is running at 1MHz internal clock speed. */ #include <avr/io.h> #include <avr/wdt.h> #include <avr/sleep.h> #include <avr/interrupt.h> bool timer1 = false , led = true ; // Interrupt service routine for timer1 ISR(TIMER1_COMPA_vect) { timer1 = true ; } void setup() { // Setup output pins pinMode( 1 , OUTPUT); digitalWrite( 1 , led); set_sleep_mode(SLEEP_MODE_IDLE); // Setup timer1 to interrupt every second TCCR1 = 0 ; // Stop timer TCNT1 = 0 ; // Zero timer GTCCR = _BV(PSR1); // Reset prescaler OCR1A = 243 ; // T = prescaler / 1MHz = 0.004096s; OCR1A = (1s/T) - 1 = 243 OCR1C = 243 ; // Set to same value to reset timer1 to

3D Printer Filament Joiner

I have been looking at various ways of joining 3D printing filaments. One method involves running one end of a filament through a short PTFE tubing, melting it with a lighter or candle, retracting it back into the tubing and immediately plunging the filament to be fused into the tubing: One problem with this method is that you can't really control the temperature at which you melt the filament, so you frequently end up with a brittle joint that breaks upon the slightest bend. Aliexpress even sells a contraption that works along the same line. As it uses a lighter or candle as well, it suffers from the same weakness. I am not even sure why you need a special contraption when a short PTFE tubing will work just as well. Another method involves using shrink tubing/aluminium foil, and a heat gun: But a heat gun is rather expensive, so I wanted to explore other alternatives. The candle + PTFE tubing method actually works quite well when you happen to melt it at the rig