Fe2o3Fish's dashboard

Tod,
I have an STK-500, think that'll re-flash an original BlinkM? I'm all into experimental firmware -- I write it all the time! {hint, hint} :-)

Also, I have used ping-pong balls with my BlinkM's. Problem is that the LED in the BlinkM has a clear lense. Sure would like to have a diffused lense. I've been thinking about using a Dremel tool to rough up the LED to see if that'll diffuse the light enough for a more consisent illumination of my ping-pong balls. Maybe a little foam might help. Hmmm...

BTW, just on the off chance, does anyone know if solid ping-pong balls (not made from two halves) are even obtainable, much less ones without printing on them? The printing can be removed but I'd sure like a solid, one piece ball. Thanks!

-Rusty-

Yes zombieCat, reproducing web colors between a BlinkM and a CRT or LCD video screen is pretty futile. Even going between CRT's can be a pain unless both monitors are color calibrated.

Just for, say, red alone -- the phosphor that produces the red color produces a different wavelength of red than that of an LED. Both rely on their chemical make up to produce a given "color" of RED and both are of completely different chemicals. The same goes for green and blue.

Then there's the linearity -- how much RED/BLUE/GREEN is output for a given value and whether it's uniform from 0 to 0xff. Oh... it's gets ugly quickly!

What's wrong with
{script_speed, { 'n', 255, 0, 0}},
{script_speed, { 'C', 0, 255, 0}}
?

ZombieDude,
Take a look at the previous topic of mine. In essence, what you'll
hafta do until Tod officially modifies the source code is to add a
'delay(20);' at the end of the BlinkM_writeScriptLine() in the file
'BlinkM_funcs.h'. This allows the BlinkM time to write settings to its
flash/eeprom memory.

-Rusty-

Hi Tod,

Well, continue to NOT test it then! :-P
Be that way! Oh, you are. (sigh)

Daggummit! That ScriptTool is just what I've been wanting.
Thank you, sir! I do appreciate it. :-)

Thanks Tod!

That doesn't surprise me at all although I s'pose I was of the thinking that the
code in the Tiny45 would have "dealt with that". Then again, not doing that
allows the host device to go off and do something else whilest the '45's
memory is settling down.

Please keep in mind that the BlinkM_writeScript() will need a mod since it's
just looping around BlinkM_writeScriptLine() with no delays. Users of the
API can not prevent this issue without modifying that function.

Thanks again for the quick response!

-Rusty-

Mike,
Since you're asking... :-) How 'bout Master and Slave commands?
Turning a BlinkM into a Master would revert the Tiny45's Reset pin to an
Output pin. The Master BlinkM would pulse this output just before step 1
of whatever light script it's running. The idea is to tie together any other BlinkM slaves using the Reset pin and achieve some sort of synchronization. The Slave command would return the BlinkM to its normal self.
Just a thought...