Active Topics

 



Notices


Reply
Thread Tools
Posts: 5 | Thanked: 0 times | Joined on Jan 2010
#11
I reckon this is a great idea, but the morse code seems a bit complicated.
I realise its not so accurate but I would be happy just knowing what hour it is, 3 flashes would be 3 am/pm ( i say pm cos i work nights too!)

Cheers
swst
 
F2thaK's Avatar
Posts: 4,365 | Thanked: 2,467 times | Joined on Jan 2010 @ Australia Mate
#12
do it in 24 hr time.......... its 2400..... so 24 flashes
 
Posts: 10 | Thanked: 10 times | Joined on Apr 2010
#13
excellent! Thanks! Very grateful to you

PS. how to restart LED Clock after reboot?

Several requests:
put a pause of 2 seconds between showing the time
allocate each 5 signal (brightness level or color)
Dozens little bit longer

do it in 24 hr time.......... its 2400..... so 24 flashes
no 24 flashes
Only: 2 long flashes and 4short flashes.

Last edited by IDis; 2010-05-19 at 17:01.
 
pH5's Avatar
Posts: 138 | Thanked: 375 times | Joined on Aug 2009 @ Berlin
#14
Originally Posted by IDis View Post
how to restart LED Clock after reboot?
If you have rootsh installed, use "vi /etc/event.d/chledclk" to replace the "start on started mce" line with "start on started hildon-desktop". Or start it manually with "start chledclk".

Edit: This should be fixed in version 0.0.2-1.

Originally Posted by IDis View Post
put a pause of 2 seconds between showing the time
allocate each 5 signal (brightness level or color)
Dozens little bit longer
The timing can be made configurable, but a brighter 5th flash would make some patterns too long to fit into a single engine (16 commands). For example, the 19:55h pattern right now would already be:
Code:
9d80 4000 087f 09ff 047f 05ff a404 11ff 047f 05ff a208 043f 057f 7105 0000

Last edited by pH5; 2010-05-19 at 19:41. Reason: Charging LED Clock 0.0.2-1 uploaded to extras-devel
 

The Following 2 Users Say Thank You to pH5 For This Useful Post:
Posts: 306 | Thanked: 566 times | Joined on Jan 2010 @ Romania
#15
if only one color is needed read this
http://talk.maemo.org/showpost.php?p...6&postcount=99
because only 14 commands are available we can make ( at first sight ) 7 loops like this ( 23 : 55 )
0 >> 9d80
1 >> e104 call & wait second engine
2 >> repeat step 2 for x times ( a081 for 2 cycles)
3 >> 7f02 interdigits pause
4>> e104 call & wait second engine
5>> repeat step 4 for Y times ( a104 for 3 cycles second digit )
6 >> 7f02 interdigit pause
7 >> e104 call & wait second engine
8>> repeat step 7 for x times ( a207 for 5 cycles third digit )
9 >> 7f02 interdigits pause
10 >> e104 call & wait second engine
11 >> repeat step 10 for x times ( a20a for 5 cycles four digit)
12 >> 7f00 last digit pause
13 >> a28c cycle for more pause
14 empty
15 >> 0000 reset

the second engine

9d80
087f pulse up
097f pulse down
e082 trig & wait from engine 1
4000 just in case ....
0000
it is a lot of command available even for black steps

engine 1 jump to second engine steps are the same e104
branch command a000 + 80 * times + start_loop_step_number ( in hexa )

for morse code lovers ... SOS pattern
Code:
R;9d80e104150fa101e104a104150fa104e104150fa1087f0b0000;9d80e08040ff140f4000e0020000

Last edited by blue_led; 2010-05-19 at 20:59.
 

The Following User Says Thank You to blue_led For This Useful Post:
chemist's Avatar
Administrator | Posts: 1,036 | Thanked: 2,019 times | Joined on Sep 2009 @ Germany
#16
moved to Apps

The Morse code idea is lovely! Having it one at a time makes it 20 signals long plus 3 gaps.

What about binary/hex? For digit by digit you only need 4 times 4 signals. For a 12hour pattern you need 11 and for 24hour pattern 12, so having the 12/24h pattern is the shortest. For hex you could use Morse code, that would be just one pattern at a max of 10 flashes and one gap.
 
Posts: 642 | Thanked: 486 times | Joined on Aug 2008
#17
Not that I don't appreciate you guys trying to make this app - but I don't really see the point! Morse code is so long and you need to concentrate and count the dots/dashes!

A better idea would be to create and app that every 20minutes or so slowly increases the display brightness and shows the time then slowly disappears.

This way it's not disturbing, and doesn't require much concentration to see the time!
 
Posts: 158 | Thanked: 67 times | Joined on Jan 2008
#18
Originally Posted by rash.m2k View Post
Not that I don't appreciate you guys trying to make this app - but I don't really see the point! Morse code is so long and you need to concentrate and count the dots/dashes!

A better idea would be to create and app that every 20minutes or so slowly increases the display brightness and shows the time then slowly disappears.

This way it's not disturbing, and doesn't require much concentration to see the time!
But that might require me to stare into the darkness for close to 20 minutes in the middle of the night if I wake up and wonder what time it is.
 
Posts: 123 | Thanked: 122 times | Joined on Feb 2010
#19
Originally Posted by swst View Post
I reckon this is a great idea, but the morse code seems a bit complicated.
I realise its not so accurate but I would be happy just knowing what hour it is, 3 flashes would be 3 am/pm ( i say pm cos i work nights too!)

Cheers
swst
I like this as a rough idea of the time. It is likely to be used in the small hours by the vast majority, so perhaps avoid 24hr clock, but the LED colour could be used to interpret this. Seriously, though. If you don't know already if it's am or pm right now, you need to get out more! The hours could be represented by long flashes, followed by either one, two, three or four short flashes to signify which quarter of the hour you're in e.g. flaaash, flaaash, flash, flash would mean between quarter past and half past two.
 
Posts: 642 | Thanked: 486 times | Joined on Aug 2008
#20
Originally Posted by Andrew_b View Post
I like this as a rough idea of the time. It is likely to be used in the small hours by the vast majority, so perhaps avoid 24hr clock, but the LED colour could be used to interpret this. Seriously, though. If you don't know already if it's am or pm right now, you need to get out more! The hours could be represented by long flashes, followed by either one, two, three or four short flashes to signify which quarter of the hour you're in e.g. flaaash, flaaash, flash, flash would mean between quarter past and half past two.
This is probably a better idea! Morse code was a bad idea.

But using different colours to represent times would be better, in total we would need 4 different colors - (2^4 = 16 > 12) plus 2 colours for the minute hand.

We have blue, green, orange and white as four colours.

We can flash the four colours quickly - then pause for 1/2 second then flash two colours representing 15, 30, 45, 60.
 
Reply


 
Forum Jump


All times are GMT. The time now is 02:53.