![]() Also I wanted to try my hand at that binary tree thing (again - since its some old code I made that I converted to C(++?) / Arduino). That's not to say it can't be further optimized, which I'm sure it can. I was maybe not as concerned about memory usage (for this particular application at least), as to just try to not use (much) more than needed. Not that I think I will have much use for it myself (you never know), but I wouldn't have continued this without this thread you started I also want to add it's not my intention of "taking over" your thread or project!ītw, true, PROGMEN is where tables should go, but I have to admit I haven't actually meddled too much with that yet. I don't have it as a cool stand-alone device, so input/output is via serial (and a beeper + LED). Well.unless my timing in the code is off. Starting to get a little practical (and fun) too, as I at last can hear what a properly timed Morse code sounds like that I type myself and practice right away with it. What I'm trying to get working now is the simple stuff (but managing to mess it up) - getting Morse audio input! I couldn't let that reverse-binary tree beĪnd I'm pleased to say the reverse tree path tracer worked, even on first try! (That's not too often) So using the same table for decoding and encoding. Same here, except encoder (combined with the decoder). Probably soon.ish.Īlmost ready for the debut of Morse decoder. In fact I think I'll look into that soon-ish, as well as to see how well it actually decodes audible morse (not tested yet, and requires a little modification for the input).ĮDIT: To clarify that it's not that I promise anything, it was just a thought I got now and want to follow at some time. But when I think about it, it should be possible to make a "reverse-dichotomic" (or reverse-binary tree) table lookup algorithm. For a morse coder (not de-coder), I suppose a list is needed. It's primarily used for double-clicks and so on, and a bit cumbersome / unintuitive to use I think.Īnd for the search table, I was more concerned with memory usage. I'm not entirely sure how well it would fit with the morse decoder as-is at the moment either. I guess it depends on the button and circuitry.Īs for a button class, I already made one a little while back Google Code Archive - Long-term storage for Google Code Project Hosting.īut I did not use it for this. Optimized for decoding weak, fading signals in the presence of interference, especially on the Amateur Radio. Seems to work for 8wpm speed, and also 13 wpm. Morse Expert decodes Morse Code audio to text. Which probably is a bit small for debouncing. Also I have one of those piezo beepers for an audible feedback.Īs for debouncing it already is debounced in that code, but I was a bit vary on the value of the debounce timer, which was set to 20ms. The circuit is very simple, using the built-in pullup resistor too. It's no good for serious morse keying, and I don't really know morse other than what I learned while testing the code. Thanks! I just use a pushbutton that fits nicely on a breadboard.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |