bistro-HD (OTSM, 4channel, Vcc,Eswitch, etc in attiny25)

43 posts / 0 new
Last post

Pages

Flintrock
Offline
Last seen: 3 hours 7 min ago
Joined: 09/10/2016 - 20:29
Posts: 860
bistro-HD (OTSM, 4channel, Vcc,Eswitch, etc in attiny25)

Ok here it is:

 


I present bistro-HD (alpha release).

It's called HD because it packs a bunch of new features into non-existent space. (The previous version was >2040 byte out of 2048 available in an attiny25).

Quick higlights:
E-switch operation, OTSM, voltage-read from VCC pin, QUADRUPLEDOWN (TM) layout (just kidding about the TM, but yes that's 4 PWM channels), and you can have that all at once in an attiny25, and with three channels there's still 200 bytes left to spare.

This version is designed for developmental drivers and so it comes with much overhauled layout and build option configurations that should make it easy to customize.

This was all started with just trying to get OTSM into bistro, but somehow became much more.

For any not following along OTSM is a replacement for the off-time-cap method. It uses a real electronic clock (the watchdog) run by capacitor power to measure off-click times for a couple of seconds. Click lengths are now defined in actual seconds, and old voodoo like changing a resistor from 19.1k to 20k wont affect it. It still needs a little more hardware testing to see just how small the pieces can be kept in the real world. Flashy Mike and Mike C did the initial feasibility tests which really brought this forward and I've added some new technical improvements in this version I think.

Of course this would not be without Toy Keeper who wrote the great original bistro, and many others probably. This version also includes TA's modes for tipples.


So here are my notes I've made as I was adding changes:

  /* Flintrock Updates Feb 2017, Bistro-HD release.
* Implements OTSM "off-time sleep mode" to determine click length based on watchdog timer with mcu powered by CAP.
*    -CLick lengths are now defined in bistro.c using real fractional seconds.
* They will not change with temperature or resistor values (but they may fail if the cap isn't strong enough).
*    -Senses pin fall on pin 7, goes into watchdog wake loop; counts time. Final wake on pin rise,
*    -Added powersaving (idle sleep timer) in main loop delays to reduce cap drain while detecting power-off.
* (rough global timer implemented with it but commented out for now).
*    -Included option to charge OTC CAP as a secondary OTSM cap, probably less effective than primary cap since it
spills over pin diode. Untested, but it should work.
*    -Uses BOD disable to reduce average click sleep power to ~8uA (4 is possible for longer sleeps) on supported chips.
*    -For good results requires BODS capable chip revision
(see datasheet page 36, attiny45's seem like best bet, but I have a revision G 25)
*    -For best results also requires V version of the chip (not actually verified working/attainable in right revision).
* Adds Vcc inverted voltage read option, with calibration table, allows voltage read of 1S lights without R1/R2 divider hardware.
* Implemented 4th PWM channel.
*    -Now can define and use any combination of 4 PWM pins. (PWM1: pb1, PWM2: pb0, PWM3: pb4, PWM4: pb3)
*    -PWM disabled on zero-mode to achieve full off on the non phase-correct channel.
* Now supports E-switches.
*    -Long press for off, short and mid for short and mid, like clicky.
*    -Presently just any tap for on. Could add a timeout double tap?
*    -E-switch can share pin with divider/otsm (ex: 4 channel light)
* (but could still be distinguished in functionality with future voltage sense development).
*    -Added eswitch lockout toggle (Menu option 9) (except if shared with voltage/OTSM pin, for now).
* Added define to use Vcc as a refernce for reading the voltage divider (not the same as reading Vcc).
* This should be used for LDO builds if OTSM is read from the voltage pin, and R1/R2 should keep on voltage > 1.8V.
* Algorithm-generated calibration tables now allow voltage adjustment with one or two configs in fr-calibration.h
*    -For traditional voltage read, one measurement should be enough for from-scratch calibration (I hope)
* and small adjustments are probably fine for, well small adjustments.
* New fr-attiny.h simplifies layout definitions and provides more easily-customizable layouts for future boards.
* Added BODS to voltage shutdown (and E-switch poweroff) to protect low batteries longer (~4uA for supported chips).
* #define VOLTAGE_CAL results in a battcheck-like build, blinks ADC value,
         produces VCC or divider values according to config
* Implements space savings (required for the other features, but some left over):
*   -implement TK size optimizations
*   -Save variables now stored in array for looped save/restore/toggle instructions (big savings).
*   -implement 0 termination of mode group definitions,
* Side effect: could now have a couple of very long ( >8) groups without much memory cost at all.
*   -Big overhaul to count_modes code, saves a few bytes.
*   -Many more size optimizations, especially in new ISR's
* Includes a blink_value function for debugging, blink_value(255) blinks strobe 2 __ 5 __ 5 strobe for example.
* (It's optimized out if not used, well, seems that requires the right linker flags.)
*
*

 

Note: Disabling OFFTIM3 no longer disables timing mechanism. OTSM or OTC can be used for long/short only builds.
although it's not clear how much sense that makes. If you want to save space, you'll still want to disable OTSM and OTC.
If you just want to turn off 3-way mode, you can just set the default menu option.

Code Size:
With all new features disabled (99% of them anyway), compiles to ~ 1742 bytes (so 300 bytes reduction).
Including every new feature at once (except debug options), in QUADRUPLEDOWN_LAYOUT with ESWITCH, OTC, and VCC read, it's 2002
bytes. (eswitch and OTSM is smaller because eswitch and otsm use the same coding, OTC requires extra.
Divider read is still possible with this layout too and saves 16 bytes)
A more standard tripple build with OTSM and VCC read is 1828 bytes, but there are many combinations. That leaves quite a bit of space.

modegroup.h ramp and modegroup definitions are now separated out int modegroup.h This allows separation of code development from modegroup
development and allows different modegroups to be defined for different builds, either adding defines or using separate files.

Bugs: There are MANY combinations of features and layouts that can be compiled in and the new features have very interconnected logic.
I've tried to think about how to make them all work in any combination, and test many or most I hope, but there are probably
exceptions/bugs. Particulary making eswitch and OTC (for clicky) work at the same time took some last minute thought, sinc
e-switch was built around OTSM. But it >>should<< work now. In principle you can have eswitch, OTSM and voltage read on the
same pin, separate pins, separate switch pins with OTC for the clicky, etc. The fallback fastpresses mode still exists too and
does off-time without any cap (it could use some updates for reliability). So there are sort of 4 ways to measure off time.

 

http://s000.tinyupload.com/?file_id=17549940329692337476
 

 

Edited by: Flintrock on 02/17/2017 - 10:53
DavidEF
DavidEF's picture
Offline
Last seen: 30 min 23 sec ago
Joined: 06/05/2014 - 06:00
Posts: 3889
Location: Salisbury, North Carolina, USA

This is great! Looking forward to quad-channel PWM becoming the standard for BLF drivers! The next step up from quad-channel for me is RGBW with independent dimming controls for each channel (and maybe some presets for quick access).

Ejected Filament wrote:
I could be wrong, or half wrong but Im unlikely to be completely right.
SawMaster wrote:
One of my rules of life: “A closed mouth gathers no foot.
LightRider
LightRider's picture
Offline
Last seen: 1 hour 29 min ago
Joined: 08/05/2015 - 09:52
Posts: 1429
Location: U.P. MI, USA

This is great!

By chance is there an easy way to make the level of each channel variably selectable by the user? Basically like a channel mixer. I’ve always wondered why bistro does not have variable dimming anyway, especially since it already has a ramp table.

Please don’t let my questions down play what has been created here! This is very exciting to see these advancements in such short time!!!

cbrake10
Online
Last seen: 31 sec ago
Joined: 11/25/2014 - 17:04
Posts: 421
Location: Alabama

This is awesome. Great to see such progress in firmwares lately. PartyBeer

-Clark

Flashy Mike
Flashy Mike's picture
Offline
Last seen: 47 min 26 sec ago
Joined: 01/14/2016 - 16:38
Posts: 527
Location: Germany

Congratulations!

chouster
Offline
Last seen: 51 min 11 sec ago
Joined: 02/20/2014 - 15:05
Posts: 626
Location: germany

ORSM!!! Congrats! You must’ve put a lot of time and effort into this. Terrific work. Thumbs UpBeer

Tom E
Tom E's picture
Offline
Last seen: 20 hours 51 min ago
Joined: 08/19/2012 - 08:23
Posts: 8807
Location: LI NY

Look'n Good!! Glad to see the 4 PWM channel feature worked out. Interested in the board designs/parts, etc. pairing up with all these features.

gchart
gchart's picture
Offline
Last seen: 21 min 26 sec ago
Joined: 03/19/2016 - 11:57
Posts: 508
Location: Central IL

Well done! Glad to see firmware improvements keep chugging along. Peaking at the code now…

Justintoxicated
Justintoxicated's picture
Offline
Last seen: 10 hours 19 min ago
Joined: 12/28/2016 - 19:36
Posts: 39
Location: California

Sounds amazing although I admit most of that read went right over my head.  Great summary of features although having not worked on the previous one I don't understand what the advantages are with the new ones.  For example I'd love to understand why I want 4 PWM's instead of 2?

 

OTSM "off-time sleep mode" got it Smile

But what is LDO? Triple Down? 3-way mode?

 

I don't understand allot of other advantages either but that's just because I am so new to this. Smile  

So OTSM requires a new driver board build, but will this run on current boards like the ones from RMM?  Sounds like it would just need to be configured to do so which is why I ask the stupid questions above Smile

 

Sorry I'm c-tarded  I'm a mostly a java web app developer Smile  This is a fun new world over here though.

MRsDNF
MRsDNF's picture
Offline
Last seen: 7 hours 46 min ago
Joined: 12/22/2011 - 21:18
Posts: 10170
Location: A light beam away from the missus in the land of Aus.

Wow. Orsm effort. Well done. Beer

My current and or voltage measurements are only relevent to anything that I measure. Budget light hobby proudly sponsored by my Mastercard and unkowingly paid for by a hard working wife. Free plug for my daughter. http://missymupsnails.com.au

old4570 "I'm not an expert , so don't suffer from any such technical restrictions."

Old-Lumens. Highly admired and cherished member of Budget Light Forum. 11.5.2011 - 20.12.16. RIP.

 

ImA4Wheelr
ImA4Wheelr's picture
Offline
Last seen: 1 hour 34 min ago
Joined: 02/03/2013 - 14:51
Posts: 7054
Location: SC

Wow!  I've been out of the loop on flashlight modding (including keeping up with FW developments, but this sounds like some seriously great achievements.  So many developments.  I really dig that you have disconnected OTC performance from the various factors that influence the OTC capacitor's behavior.

Hope you are ok with me adding a link in the OP of the "25" thread to this thread.

Flintrock
Offline
Last seen: 3 hours 7 min ago
Joined: 09/10/2016 - 20:29
Posts: 860

Expect problems.  There's a ton of new stuff.  There's going to be bugs I missed. I've tested on a bench, which has some advantages as far testing layout cases, but also misses some of the experience of real-world use.   Yeah, sorry about the fast write-up. 

 

4 channels was requested (I think by DavidEF) for RGBW.  No, at the moment there are no disco strobes or new ramping or anything like that. Yes the softstart code toy keeper wrote should be a solid starting point for ramps, but I think narsil is the ramping king probably.  I knew someone would ask about party modes, lol.  The main goal was to squeeze this into an an attiny25, although TA is now squeezing 85's onto smaller things anyway (I'm almost bummed about that lol).  Setting this free onto an attiny85 would probably allow tons of stuff like that. I  don't know how much I'll carry the ball forward with that kind of stuff either.  Contributions are of course welcome.  It's gpl.

 

LDO is, well some of those comments are for people pairing it up with new hardware.  LDO stands for Low drop Out, but it means tiny voltage regulator on the input to the mcu.  It's used for 2S etc lights as a better alternatve to a zener to power the mcu, and can provide a voltage reference to  the adc.  that's the only way to get voltage reading and power-off detection (and/or switch) onto the same pin in this firmware. But in an unregulated 1S build you don't need to.  You can just use the Vcc-pin voltage reading.

 

Trippledown is as far as I can tell the original 3 channel version of bistro.  Actually I kind of skipped that version and went from stock to TA version, which I think is based on trippledown. Three way, I was just referring to the short/med/long click options, that give mode reversal and hidden mode access, compared with short/long, that doesn't.

 

I think the most immediately-available test case for the biggest part of the code is probably e-switch lights. I kind of imagine DavidEF building an RGBW SRK or Q8.

Flintrock
Offline
Last seen: 3 hours 7 min ago
Joined: 09/10/2016 - 20:29
Posts: 860

Oh, one thing that's completely untested is the traditional divider voltage reading in the new parameterized form. I don't have a voltage divider on my test setup.  I tested the Vcc method and that works for me, but not the divider.  There is a hidden define in the voltage.h that unleashes the original ToyKeeper calibration table as a backup, but that's not tested either. It should work, but there could be a typo or two still there.

 

Oh, and I forgot to package in TA's build script.  I'll add it back when I get a chance.  It's useful for compiling on Linux.

Texas_Ace
Texas_Ace's picture
Offline
Last seen: 1 hour 24 min ago
Joined: 03/24/2016 - 07:44
Posts: 2955

Very nice work!

Don’t be bummed about the swap to tiny85’s in the new drivers, we will still need the space at some point plus all the older drivers still use tiny25’s and this firmware should work for them as well.

If guns cause crime, then pencils cause misspelled words.

Giving money and power to government is like giving whiskey and car keys to teenage boys. -- P.J. O'Rourke , Civil Libertarian

Texas Avenger Driver Series

My LED Test series - XP-L2 V5  - Nichia 219C 90+ CRILatticebright "XM-L"XHP35 & PWM efficiency - XHP50 - XP-L V5 - XM-L2 U2 - XP-G3 S5  - XP-L HI V2 - Oslon Square & direct comparison to Djozz tests

How I made a True integrating PVC sphere with no math involved

DavidEF
DavidEF's picture
Offline
Last seen: 30 min 23 sec ago
Joined: 06/05/2014 - 06:00
Posts: 3889
Location: Salisbury, North Carolina, USA

Texas_Ace, do you have a new driver board for this firmware? I know you’ve been talking about new driver design(s) you’ve been working on. Is this it? I’d love to see the hardware released that utilizes this firmware. Big Smile

Ejected Filament wrote:
I could be wrong, or half wrong but Im unlikely to be completely right.
SawMaster wrote:
One of my rules of life: “A closed mouth gathers no foot.
Flintrock
Offline
Last seen: 3 hours 7 min ago
Joined: 09/10/2016 - 20:29
Posts: 860

A couple of notes for anyone looking at the code.  The 4 channel stuff is mostly setup in fr-tk-attiny.h, init_mcu, and a couple of timer interrupts.

 

The OTSM and e-switch stuff is mostly done from PCINT0_vect, the watchdog interrupt (that does nothing), and some mild trickery with main_init and the early parts of main.  All that is kind of together in bistro.c 

Texas_Ace
Texas_Ace's picture
Offline
Last seen: 1 hour 24 min ago
Joined: 03/24/2016 - 07:44
Posts: 2955
DavidEF wrote:
Texas_Ace, do you have a new driver board for this firmware? I know you’ve been talking about new driver design(s) you’ve been working on. Is this it? I’d love to see the hardware released that utilizes this firmware. Big Smile

I have a new driver that is almost ready from the hardware side, although the firmware is not quite ready yet but a lot of the features in this firmware came about for this new driver.

I am going to be calling the new driver the “Texas Commander”.

It will take advantage of the OTSM and PWM regulation among other software features but no 4 channel at this time, mostly because it is not needed with this driver.

Long term I would love to see bistro and narsil come together to make a single firmware for both clicky and eswitch lights that can be selected in the menu thus allowing for a single driver to be produced and work with virtually any light setup with little to no hardware changes needed.

If guns cause crime, then pencils cause misspelled words.

Giving money and power to government is like giving whiskey and car keys to teenage boys. -- P.J. O'Rourke , Civil Libertarian

Texas Avenger Driver Series

My LED Test series - XP-L2 V5  - Nichia 219C 90+ CRILatticebright "XM-L"XHP35 & PWM efficiency - XHP50 - XP-L V5 - XM-L2 U2 - XP-G3 S5  - XP-L HI V2 - Oslon Square & direct comparison to Djozz tests

How I made a True integrating PVC sphere with no math involved

Flintrock
Offline
Last seen: 3 hours 7 min ago
Joined: 09/10/2016 - 20:29
Posts: 860

Yeah, I'd veer more toward talking about 45's than 85's if OTSM is something that matters.  We still have no datapoint of anyone having a late revision 85 where BODS actually works, and possibly  three examples where it didn't.  Who knows, maybe those revisions have only been sold through certain contracts and the retail supply has a 15 year production run of early revisions on the shelf. It does seem that on the other hand maybe almost every attiny45 in the wild is late revision and compatible (we don't really know).  For use on existing builds, it's going to be a YMMV situation. For new builds you can at least look at the bottom of the chip and find out.

Flintrock
Offline
Last seen: 3 hours 7 min ago
Joined: 09/10/2016 - 20:29
Posts: 860

I want to add more emphasis of the credit to Flashy Mike and Mike C.  Maybe it comes off like they did early test of my OTSM designs or something.  Not the case.  They made the first prototypes for hardware and software and communicated very useful results of that that heavily influenced this.  TA also was very involved in helping to figure out what configurations we can actually get into a driver and DEL even chimed in with some useful contributions to limits on the electronics. A bunch of people put thought and effort into it.

 

As far as merging things.  I think Tom E is probably the most consistently dedicated software person here, and don't expect that to change from my perspective. If some of this stuff just serves as a demo to get worked or reworked into Narsil, that's great, especially considering he will probably continue to maintain it.  Much of it would probably have to be done very differently in Narsil though. They are just completely different animals at the program flow level.

Flintrock
Offline
Last seen: 3 hours 7 min ago
Joined: 09/10/2016 - 20:29
Posts: 860

DavidEF wrote:
This is great! Looking forward to quad-channel PWM becoming the standard for BLF drivers! The next step up from quad-channel for me is RGBW with independent dimming controls for each channel (and maybe some presets for quick access).

Hmm.. I don't have a concept of a comfortable UI for that. How would it work? Already you can predefine combinations.  Clicking into 4 different ramps sounds pretty uncomfortable, and distinguishing 4 switches on one pin with battery read and poweroff detection, is technically not quite impossible, but probably not going to happen.

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 13 hours 1 min ago
Joined: 01/12/2013 - 14:40
Posts: 4634
Location: (469219) 2016 HO3

This looks awesome so far. I’ve been pulled away by Real Life™ for most of the past 5 months, but I’m finally back to making my backlog smaller instead of larger, and I hope to catch up on recent developments.

Do you mind if I copy the code into the main repository?

Also, is there much interest in migrating to github? I personally prefer launchpad, but git is quite a bit more popular so it might be useful to move the repository.

Flintrock
Offline
Last seen: 3 hours 7 min ago
Joined: 09/10/2016 - 20:29
Posts: 860

Hi TK.  Glad you like it (well, no real tests yet).  I had a good starting place to work from.

 

Yeah, I'm a little likely to take a break a bit for real life. I don't have much opinion where you put it.  Of course I don't mind if you copy it.  probably should get TA's build script in there if you've got it handy.  It should work as is from previous versions. I'll try to add it when I get around to it. I did forget to mention that my test rig is a very violated TA board. 

 

It's got 30uA of capacitance on C2, nothing on the OTC. I think 22k on R1, but the value doesn't matter because there is no R2.  I'm only using the voltage there as OTSM shutdown detection, which is why I haven't tested the voltage divider read option, just vcc read, and that's how would wire any 1S build.  

C1 capacitance and the bleeder (total resistance of bleeder and parallel divider to be accurate) are important for getting OTSM working well because  they determine how fast the power off is detected, and there's a bunch off-time power wasted while that's happening.  I'm presently using 1uF C1 and 500 ohms bleeder.  DEL likes 1uF C1 for stability against spikes, although 0.1 might do the trick. Lower bleeder is ok, unless you want heroic moon mode lifetime to survive the apocalypse. Anyway, I think after adding power saving in bistro, there's at most maybe 20% improvement to be had in off-time by going to lower values. 

 

I'm buying a V-chip now and a couple of these caps:

http://www.digikey.com/short/3fnfr4

 

It's quite expensive but being tantalum it won't lose capacitance with a DC bias or with high temperature(there is the whole explosion thing but that adds fun), and it's the best I can find in an 0805.  I think TA is trying to make space for 1206 C2's on his new boards, and there should be some benefit from adding an extra cap in the OTC position if it's not otherwise in use, or even if it is (can wire a switch across the cap).  I'll try to build it into a present model TA board and see how it goes.

 

 

Texas_Ace
Texas_Ace's picture
Offline
Last seen: 1 hour 24 min ago
Joined: 03/24/2016 - 07:44
Posts: 2955

ToyKeeper wrote:
This looks awesome so far. I’ve been pulled away by Real Life™ for most of the past 5 months, but I’m finally back to making my backlog smaller instead of larger, and I hope to catch up on recent developments.

Do you mind if I copy the code into the main repository?

Also, is there much interest in migrating to github? I personally prefer launchpad, but git is quite a bit more popular so it might be useful to move the repository.

Great to hear you are back poking around!

I am about to take some time off for real life myself so I also understand the break. Thats why I have been trying to finish this last driver before life takes over.

I should hopefully have a hardware setup nailed down before long for people to play with for the firmware side of things.

If guns cause crime, then pencils cause misspelled words.

Giving money and power to government is like giving whiskey and car keys to teenage boys. -- P.J. O'Rourke , Civil Libertarian

Texas Avenger Driver Series

My LED Test series - XP-L2 V5  - Nichia 219C 90+ CRILatticebright "XM-L"XHP35 & PWM efficiency - XHP50 - XP-L V5 - XM-L2 U2 - XP-G3 S5  - XP-L HI V2 - Oslon Square & direct comparison to Djozz tests

How I made a True integrating PVC sphere with no math involved

DavidEF
DavidEF's picture
Offline
Last seen: 30 min 23 sec ago
Joined: 06/05/2014 - 06:00
Posts: 3889
Location: Salisbury, North Carolina, USA

Flintrock wrote:

DavidEF wrote:
This is great! Looking forward to quad-channel PWM becoming the standard for BLF drivers! The next step up from quad-channel for me is RGBW with independent dimming controls for each channel (and maybe some presets for quick access).

Hmm.. I don’t have a concept of a comfortable UI for that. How would it work? Already you can predefine combinations.  Clicking into 4 different ramps sounds pretty uncomfortable, and distinguishing 4 switches on one pin with battery read and poweroff detection, is technically not quite impossible, but probably not going to happen.

Well, I’m not at all versed in firmware, so I can only say what I think I’ve seen/heard. If you’re interested, take a look at DrJones and tterev3 UI’s for inspiration. tterev3 even has R-G-B-W-UV working with e-switch. He uses PIC chips instead of ATtiny, but that doesn’t change the fact that he has an excellent single e-switch UI. I can’t remember now for sure if he has per-channel output-level ramping, but I think he has some kind of advanced color mixing.
Ejected Filament wrote:
I could be wrong, or half wrong but Im unlikely to be completely right.
SawMaster wrote:
One of my rules of life: “A closed mouth gathers no foot.
LightRider
LightRider's picture
Offline
Last seen: 1 hour 29 min ago
Joined: 08/05/2015 - 09:52
Posts: 1429
Location: U.P. MI, USA
DavidEF wrote:
Flintrock wrote:

DavidEF wrote:
This is great! Looking forward to quad-channel PWM becoming the standard for BLF drivers! The next step up from quad-channel for me is RGBW with independent dimming controls for each channel (and maybe some presets for quick access).

Hmm.. I don’t have a concept of a comfortable UI for that. How would it work? Already you can predefine combinations.  Clicking into 4 different ramps sounds pretty uncomfortable, and distinguishing 4 switches on one pin with battery read and poweroff detection, is technically not quite impossible, but probably not going to happen.

Well, I’m not at all versed in firmware, so I can only say what I think I’ve seen/heard. If you’re interested, take a look at DrJones and tterev3 UI’s for inspiration. tterev3 even has R-G-B-W-UV working with e-switch. He uses PIC chips instead of ATtiny, but that doesn’t change the fact that he has an excellent single e-switch UI. I can’t remember now for sure if he has per-channel output-level ramping, but I think he has some kind of advanced color mixing.

Dr jones really has the ultimate RGBW UI. And he does it with an mcu, capacitor and amc’s. Quite amazing.

An adaption of bistro or narsil for 4channel would be great but I imagine a good RGBW UI would have to have its own firmware…

DavidEF
DavidEF's picture
Offline
Last seen: 30 min 23 sec ago
Joined: 06/05/2014 - 06:00
Posts: 3889
Location: Salisbury, North Carolina, USA

LightRider wrote:

Dr jones really has the ultimate RGBW UI. And he does it with an mcu, capacitor and amc’s. Quite amazing.

An adaption of bistro or narsil for 4channel would be great but I imagine a good RGBW UI would have to have its own firmware…


Yeah, I know the RGBW firmware would NOT be Narsil or Bistro. I wouldn’t want a RGBW light to work like a white-only light. The “four channel” aspect of a Bistro or Narsil light is just a way to have more efficient mode levels. It’s the next step up from three channels, which is the next step up from two channels, which is a bit better than one channel. It’s almost like having a 8K television versus 4K versus 1080P versus 720P versus “standard DEF” in that it deals with “resolution”.
Ejected Filament wrote:
I could be wrong, or half wrong but Im unlikely to be completely right.
SawMaster wrote:
One of my rules of life: “A closed mouth gathers no foot.
LightRider
LightRider's picture
Offline
Last seen: 1 hour 29 min ago
Joined: 08/05/2015 - 09:52
Posts: 1429
Location: U.P. MI, USA

DavidEF wrote:
LightRider wrote:

Dr jones really has the ultimate RGBW UI. And he does it with an mcu, capacitor and amc’s. Quite amazing.

An adaption of bistro or narsil for 4channel would be great but I imagine a good RGBW UI would have to have its own firmware…


Yeah, I know the RGBW firmware would NOT be Narsil or Bistro. I wouldn’t want a RGBW light to work like a white-only light. The “four channel” aspect of a Bistro or Narsil light is just a way to have more efficient mode levels. It’s the next step up from three channels, which is the next step up from two channels, which is a bit better than one channel. It’s almost like having a 8K television versus 4K versus 1080P versus 720P versus “standard DEF” in that it deals with “resolution”.

And it does open up the possibility of having multiple led outputs. Like an all red mode or an led on the side and front of head as I’ve seen in some mods out there. It opens up many more possibilities and is a step toward another possible color firmware.

DavidEF
DavidEF's picture
Offline
Last seen: 30 min 23 sec ago
Joined: 06/05/2014 - 06:00
Posts: 3889
Location: Salisbury, North Carolina, USA

LightRider wrote:
DavidEF wrote:
LightRider wrote:

Dr jones really has the ultimate RGBW UI. And he does it with an mcu, capacitor and amc’s. Quite amazing.

An adaption of bistro or narsil for 4channel would be great but I imagine a good RGBW UI would have to have its own firmware…


Yeah, I know the RGBW firmware would NOT be Narsil or Bistro. I wouldn’t want a RGBW light to work like a white-only light. The “four channel” aspect of a Bistro or Narsil light is just a way to have more efficient mode levels. It’s the next step up from three channels, which is the next step up from two channels, which is a bit better than one channel. It’s almost like having a 8K television versus 4K versus 1080P versus 720P versus “standard DEF” in that it deals with “resolution”.

And it does open up the possibility of having multiple led outputs. Like an all red mode or an led on the side and front of head as I’ve seen in some mods out there. It opens up many more possibilities and is a step toward another possible color firmware.


Well yeah, that too. Silly
Ejected Filament wrote:
I could be wrong, or half wrong but Im unlikely to be completely right.
SawMaster wrote:
One of my rules of life: “A closed mouth gathers no foot.
ToyKeeper
ToyKeeper's picture
Offline
Last seen: 13 hours 1 min ago
Joined: 01/12/2013 - 14:40
Posts: 4634
Location: (469219) 2016 HO3

DavidEF wrote:
Yeah, I know the RGBW firmware would NOT be Narsil or Bistro. I wouldn’t want a RGBW light to work like a white-only light. The “four channel” aspect of a Bistro or Narsil light is just a way to have more efficient mode levels.

Yeah, they’re designed for only one actual LED, or maybe one plus an indicator somewhere. Adding more channels to a one-LED light has diminishing returns. Here’s a conceptual comparison of 1-channel, 2-channel, and 3-channel drivers:

As far as I can tell, the Tripledown or QuadrupleDown (lol) method is how Zebralight and some other premium brands do their drivers. On close inspection, their medium modes have fast oscillations between two stable output levels… just like what Bistro and Narsil do. Not all premium brands operate like the led4power linear drivers.

The really interesting parts of having more PWM channels is the ability to do more than one LED. Like, RGBW or white plus an indicator or two, or multiple color temperatures for adjustable CCT, or things like that. Or use extra pins for extra I/O, like another switch or an external temperature sensor or a backshine/feedback sensor. Of course, those aren’t going to happen in most cheap hosts, so I expect the 2-to-4-channel single-LED drivers will remain popular.

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 13 hours 1 min ago
Joined: 01/12/2013 - 14:40
Posts: 4634
Location: (469219) 2016 HO3

Texas_Ace wrote:
Great to hear you are back poking around!

I have the house to myself for about 5 months and plan to make the most of it. After that, I don’t know what will happen.

Texas_Ace wrote:
I am about to take some time off for real life myself so I also understand the break. Thats why I have been trying to finish this last driver before life takes over.

Before you go, could you upload the saber driver to oshpark? Smile
ToyKeeper
ToyKeeper's picture
Offline
Last seen: 13 hours 1 min ago
Joined: 01/12/2013 - 14:40
Posts: 4634
Location: (469219) 2016 HO3

Flintrock wrote:
It’s called HD because it packs a bunch of new features into non-existent space. (The previous version was >2040 byte out of 2048 available in an attiny25).

I had some similar experiences while trying to make bistro fit onto an attiny13 for biscotti. I hope to merge together both of our space-saving ideas soon, to make all the projects as small as possible.

Flintrock wrote:
Glad you like it (well, no real tests yet).

I must admit I haven’t really made time yet to read through it, after barely a week of catching up, and I don’t have hardware to test it on. But it sounds like you’ve been doing good things. Smile

Ideally, I’d rather curate people’s code instead of writing it. I never intended to write ALL TEH CODEZ, just to get it all together in one place and make it easier for people to collaborate. So, I’m really happy to see people making cool new stuff.

Pages