12-26-2012, 08:47 PM | #16 | |
Connoisseur
Posts: 71
Karma: 18140
Join Date: Jul 2011
Device: PRS-T1&KOBOTOUCH
|
Quote:
|
|
12-26-2012, 08:54 PM | #17 |
Connoisseur
Posts: 71
Karma: 18140
Join Date: Jul 2011
Device: PRS-T1&KOBOTOUCH
|
|
12-26-2012, 09:02 PM | #18 | ||
Connoisseur
Posts: 71
Karma: 18140
Join Date: Jul 2011
Device: PRS-T1&KOBOTOUCH
|
Quote:
, Quote:
Last edited by xuyn2003; 12-26-2012 at 09:08 PM. |
||
12-26-2012, 11:34 PM | #19 | |
Groupie
Posts: 196
Karma: 1086780
Join Date: Jul 2012
Device: Kobo H2O Ed. 2, Glo HD, Glo, Touch
|
Quote:
|
|
12-26-2012, 11:57 PM | #20 |
GranPohbah-Fezzes r cool!
Posts: 1,056
Karma: 3151024
Join Date: Jul 2010
Device: Nook STRs, Kobo Touch, Kobo Glo
|
Strobing is usually a sign that the PWM frequency is way too low, or that they should have used a better cap to filter or smooth the output voltage -or, worse yet, that software PWM is failing due to variable response time in a system which does not employ proper multi-tasking. There should be no requirement for high speed changes in a simple brightness circuit, so smoothing would be desirable. Further, most micro controllers available today provide for one or more timer/counters capable of hardware PWM which is greatly preferred.
|
12-27-2012, 08:37 AM | #21 |
No Comment
Posts: 3,239
Karma: 23878043
Join Date: Jan 2012
Location: Australia
Device: Kobo: Not just an eReader, it's an adventure!
|
I'm getting the feeling that the Glo uses software PWM. I've noticed that when turning pages (or doing anything that requires serious CPU cycles), the backlight blinks (sort of). It's a very fast blink, but it's there.
|
12-27-2012, 09:54 PM | #22 |
GranPohbah-Fezzes r cool!
Posts: 1,056
Karma: 3151024
Join Date: Jul 2010
Device: Nook STRs, Kobo Touch, Kobo Glo
|
Could be. Hardware based PWM should be rock solid, and if properly filtered or smoothed with an RC filter should appear to gradually change even when levels are adjusted because the write to a hardware register for the PWM should be very short.
|
12-27-2012, 10:07 PM | #23 |
Connoisseur
Posts: 56
Karma: 31830
Join Date: Oct 2012
Location: Australia
Device: Aura HD, after a train ate my Glo
|
If true, this should ruin battery consumption, because the CPU would have to be continuously running.
Filtering is not nearly as easy as you make it sound. Firstly, LEDs are current-controlled not voltage-controlled, so you want to smoothen current, not voltage. This immediately points to an inductor rather than capacitor, and inductors are big and expensive. Secondly, you don't want to dump the unwanted energy (the high frequency components) to a resistor, it's an immediate waste of precious battery power (as soon as you include any resistor anywhere, it might very well defeat the purpose of PWM). I'm not saying it's all not solvable (with some compromise between cost and power waste) but in the end, I don't think I've ever seen a PWM/switchmode LED controller that would have any filtering. They usually just use frequency that's high enough instead... Curious about the 241 magic number. Can it be that another number controls the frequency? I'll have to figure out if I can cross-compile on Windows too... [edit later] BTW, I don't see any flickering at light level 1 - maybe it's too bright outside to see it... it's just like level 2 (GUI minimum) only a little bit darker. Last edited by sysKin; 12-27-2012 at 11:23 PM. |
12-28-2012, 01:19 PM | #24 |
Groupie
Posts: 196
Karma: 1086780
Join Date: Jul 2012
Device: Kobo H2O Ed. 2, Glo HD, Glo, Touch
|
If Kobo devs are reading this, a white-on-black 'night mode', as seen on basically every other modern device with an illuminated screen, would allay most of the concern. Pics are of the new Cybook with essentially the same hardware as the Glo.
Last edited by stewacide; 12-28-2012 at 01:33 PM. |
12-28-2012, 02:28 PM | #25 |
Addict
Posts: 348
Karma: 209937
Join Date: Jan 2012
Location: Virginia, US
Device: Kobo Wifi, Kobo Glo
|
The Glo already has support for inverting the screen, it just has to be specified when updating the e-ink display. I've attached a picture of my Glo after running the e-ink code with invert enabled. But the screen doesn't stay inverted; as soon as you change the page the display goes back to normal.
|
12-28-2012, 07:46 PM | #26 |
Grand Sorcerer
Posts: 5,659
Karma: 66420972
Join Date: Dec 2011
Location: Australia
Device: Kobo Libra 2, iPadMini4, iPad4, MBP; support other Kobo/Kindles
|
Most or some, but certainly not all - there are plenty of us out there who can't read white-on-black comfortably.
|
12-29-2012, 03:24 PM | #27 | |
Wizard
Posts: 3,032
Karma: 52740263
Join Date: Feb 2012
Location: New England
Device: PW 1, 2, 3, Voyage, Oasis 2 & 3, Fires, Aura HD, iPad
|
Quote:
Shari |
|
12-29-2012, 06:52 PM | #28 |
GranPohbah-Fezzes r cool!
Posts: 1,056
Karma: 3151024
Join Date: Jul 2010
Device: Nook STRs, Kobo Touch, Kobo Glo
|
SysKIN,
My guess would be that they would include a current limiting resistor, or resistors, in series with the LEDs to specify maximum current allowed so the LEDs would not burn out if PWM accidentally got locked at 100% on time. If so, then varying the voltage would in effect vary the current through the circuit as I = (E - LEDvdrop) / R... I would guess a buffering cap couldn't hurt. I shouldn't have called it an RC filter as it really isn't since the LED would be in series with the resistor. At least that would be my take on it. You have to allow for situations where the LEDs might be burnt out and engineer for it in a consumer device, or the first time a processor locks up with the PWM full on it's bye-bye LEDs. |
12-29-2012, 09:38 PM | #29 |
Connoisseur
Posts: 56
Karma: 31830
Join Date: Oct 2012
Location: Australia
Device: Aura HD, after a train ate my Glo
|
Ah, a cap immediately at PWM pin before the resistor? I see what you mean and maybe, but (not saying you're wrong) let me explain how this is still not easy:
If PWM is to do its power-saving job properly, in its "on" state it should have near-zero resistance. So, each pulse would immediately charge the capacitor to full voltage. Now, if the capacitor is able to sustain the LEDs until the next pulse, the pulse WIDTH is no longer modulating anything - the LEDs are lit, from a periodically discharging capacitor, with nearly the same current pattern, regardless of pulse width. Alternatively if the cap is only sustaining LEDs for a short fraction of the pulse period, it's hardly filtering anything. The LEDs go dark a little bit later and smoother (not a sudden switch-off), but this doesn't change the fact they're still switching between full bright and full dark at the same frequency as before. So not only there is no smoothing in peak-to-peak sense, but there are new disadvantages: brightness control got harder because even an infinitely short pulse, as long as it charges the capacitor fully, produces some non-zero brightness, purely from capacitor's discharge. Second problem is that the capacitor tries to charge very fast which produces very high currents from PWM pin. Very high currents multiplied by hopefully-very-small resistance of PWM pin -- that becomes a sizeable power waste which was not there before. Disclaimer: while my education is in electronics engineering, I'm actually a software engineer so my modelling above can be detached from reality. Hopefully my explanation makes some sense >_< Last edited by sysKin; 12-29-2012 at 09:56 PM. |
12-29-2012, 11:57 PM | #30 |
GranPohbah-Fezzes r cool!
Posts: 1,056
Karma: 3151024
Join Date: Jul 2010
Device: Nook STRs, Kobo Touch, Kobo Glo
|
sysKin,
The biggest problems I see with your reasoning is the idea that the cap can charge instantaneously -it can't, or how you'd get enough current to power 4 or 5 LEDs in parallel from one pin when most micros only source a few ma, or sink up to 20ma... I would expect the PWM output would drive a MOSFET likely through a resistor to the gate. The MOSFET, maybe a 2N7000(200-300ma depending on manufacturer last time I used one), would probably go directly to the rail. The LED gets driven through a resistor that sets maximum current in case the FET is left on. Positioning the cap on the gate side would probably be best. Tiny cap by the way, just to smooth out spikes on either end of the PWM cycle waveform -maybe not required, but a little buffering never hurts unless you need really fast response time. Pulse width modulation can be power saving, especially in high current applications or when supply voltage is much higher than the device's operating voltage because it's more power efficient than throwing away power on resistors, but in general it's also the easiest way to provide multiple output power levels or speeds from one microcontroller pin. It sounds great to leave the resistors out, but when the micro goes splat then the LEDs get burnt out if your PWM output gets locked on and your LEDs get excessive current because the MOSFET is continuously passing full rail voltage to your LEDs. Could be kind of embarrassing. Not sure it's worth a little power savings. OTOH, if the supply voltage is very near the LED drop, you might get away with it... maybe... for a while. |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Touch What is the microsd card limit (gb) for the Kobo Touch? | Nietzsche | Kobo Reader | 31 | 12-12-2022 03:24 PM |
Touch Checkers for Kobo Touch and Kobo Glo | sergeyvl12 | Kobo Developer's Corner | 24 | 01-03-2013 04:36 PM |
Glo How to import reading Life Statistics from Kobo Touch to Kobo Glo? | the_m | Kobo Reader | 5 | 12-13-2012 03:40 PM |
Kobo Glo fonts compared to Kobo Touch | RobertJSawyer | Kobo Reader | 3 | 10-11-2012 12:10 AM |
Kobo Glo Vs Kobo Touch Sizes (Want to use my Skindigital cover) | Chocky | Kobo Reader | 3 | 09-25-2012 10:47 AM |