Skip to main content

ESPCLOCK4 - A Rethink On Tick Pulse Generation

Having dabbled recently with PWM (Pulse Width Modulation) for motor control, it struck me that maybe the same technique can be applied for pulsing the Lavet stepper motor in the analog clock.

Just a recap. The Lavet stepper motor within the analog clock is design to function at ~1.5V. However, the output on the ESP8266 and ESP32 is 3.3V, and in ESPCLOCK3, the ATtiny85 is powered at ~3V. For reasons I don't fully understand, the pulse width needs to be as long as 100ms in this case, otherwise the clock will not tick reliably. This also leads to high power draw, because higher voltage + longer pulse width. In contrast, the original clock signal is 32ms pulse width at ~1.5V (which can go as low as ~1.1V since it is running on a normal AA battery).

So in ESPCLOCK3, a diode bridge is introduced, where 2 diodes in each direction drops the 3V output by the ATtiny85 down to ~1.8V (3V - 0.6V x 2), which worked remarkably well in reducing the power draw and making the clock tick with 100% reliability.

Much like PWM in DC motor control, the idea is to eliminate the diode bridge and instead output a PWM modulated pulse signal, which should reduce the effective voltage to the clock.


With some experimentation, the ideal duty cycle of the PWM was found to be 62.5%. The output is 1.25ms on, 0.75ms off, repeated 20 times (for a total of 40ms). Both 62.5% and 40ms were found to be lower bounds for reliable operation.

The 62.5% duty cycle surprised me, because from my naive calculation, for an effective voltage of say, 1.5V, the duty cycle should be 1.5 / 3.3, which is 45%. 62.5% duty cycle implies an effective voltage of ~2V, which is much higher than I expected. I suspect my naive formula for calculating the duty cycle is wrong.

It was quite easy to modify the test program to output PWM pulses. This macro was added:

// Pulse given tickpin - 40ms duration = 20 x (1.25/2ms) PWM => 62.5% duty cycle ~ 2V
#define X_TICK_PIN(pin) \
    I_MOVI(R0, 20), \
  M_LABEL(_PULSE_##pin), \
    X_GPIO_SET(pin, 1), I_DELAY(10000), \
    X_GPIO_SET(pin, 0), I_DELAY(16000-10000), \
    I_SUBI(R0, R0, 1), \
    M_BGE(_PULSE_##pin, 1)

The macro is then used in the ticking logic:

    // Decide which pin to tick
    X_RTC_LOAD(TICK_PIN, R0),                           
    M_BGE(_HANDLE_TICKPIN2, 2), 
    // Pulse tick pin 1
    X_TICK_PIN(TICKPIN1),
    X_RTC_SAVEI(TICK_PIN, 2),
    I_HALT(),
  M_LABEL(_HANDLE_TICKPIN2),
    // Pulse tick pin 2
    X_TICK_PIN(TICKPIN2),
    X_RTC_SAVEI(TICK_PIN, 1),
    I_HALT()

I was pleasantly surprised this worked very well. It made the clock tick reliably without the diode bridge. Even better, this approach brought the power draw from 1.37mA down to 1.13mA, so it's a keeper!

Comments

  1. What would the code equivalent for X_TICK_PIN be if I want to drive the clock using PCA9685 https://www.nxp.com/products/power-management/lighting-driver-and-controller-ics/ic-led-controllers/16-channel-12-bit-pwm-fm-plus-ic-bus-led-controller:PCA9685 via ESP32 ?

    ReplyDelete
    Replies
    1. Apologies, but I am not mighty familiar with the PCA9685. But it's just a standard PWN signal. As long as you can program it to output a PWN signal on one of its pins, you can play around with the duration and duty cycle of the signal. It doesn't take long to find the approximate duration/duty-cycle to use for a particular clock. It takes longer to home in on the right values for reliable operation. Sometimes slippages will occur after 10 or 20 minutes, so it is not sufficient to let the clock run for only a few minutes.

      Delete
    2. Will try that next week. Was being lazy and trying to get the conversion of your X_TICK_PIN code to more standard PWM code :)

      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.

Filament Joiner Part 2 (With Display and Knob)

Thanks to the current corona-virus crisis, the parts I ordered for the filament joiner project were taking forever to arrive. But now that they have finally arrived, I can put them to good use. These were the parts ordered: 0.96" OLED display SSD1306 Rotary switch encoder KY-040 Here is the final circuit diagram: The OLED display is connected to the SDA and SCL pins of the Nano (A4 and A5 respectively), and powered by 5V and GND. The rotary switch encoder is connected as follows: VCC => 5V GND = > GND CLK => D9 DT => D8 SW => D2 My prototype board now looks like this: The updated code for driving the knob and display is available in  heater-with-display.ino in the Github repository . We now have a fairly compact (about 7cm x 5cm) and independent filament joiner (no need to connect to PC) that is driven solely by a 12V power supply. Here's how to use it to join printer filaments. More usage details in my previous post .

Adding "Stereo Mixer" to Windows 7 with Conexant sound card

This procedure worked for my laptop (Thinkpad E530) with a Conexant 20671 sound card, but I suspect it will work for other sound cards in the Conexant family. I was playing with CamStudio to do a video capture of a Flash-based cartoon so that I can put it on the WDTV media player and play it on the big screen in the living room for my kids. The video capture worked brilliantly, but to do a sound capture, I needed to do some hacking. Apparently, there was this recording device called "Stereo Mixer" that was pretty standard in the Windows XP days. This allowed you to capture whatever was played to the speaker in all its digital glory. Then under pressure from various organizations on the dark side of the force, Microsoft and soundcard makers starting disabling this wonderful feature from Windows Vista onwards. So after much Googling around, I found out that for most sound cards, the hardware feature is still there, just not enabled on the software side. Unfortunately, to