Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

The Netduino forums have been replaced by new forums at community.wildernesslabs.co. This site has been preserved for archival purposes only and the ability to make new accounts or posts has been turned off.

MorseCode Transmitter

Started by hoverbear, Oct 04 2011 12:42 AM

Please log in to reply

No replies to this topic

Poll: MorseCode Transmitter (4 member(s) have cast votes)

Would you like to see more from the project?

Yes, it would be neat to have morse code! (4 votes [100.00%])
Percentage of vote: 100.00%
No it's fine. (0 votes [0.00%])
Percentage of vote: 0.00%

If so, what would you like to see?

Morse De-coder (I can't read morse!) (3 votes [75.00%])
Percentage of vote: 75.00%
Simpler Usage (Eliminate the loop) (0 votes [0.00%])
Percentage of vote: 0.00%
Have a record function. (1 votes [25.00%])
Percentage of vote: 25.00%
Fix memory/resource hogging (0 votes [0.00%])
Percentage of vote: 0.00%

Vote Guests cannot vote

#1 hoverbear

New Member

Members
1 posts

Posted 04 October 2011 - 12:42 AM

Hi all,
Just posted my first C#/.net/.netMF/netduino project on Codeplex. You can find it here:

http://netduinomorse.codeplex.com/

What is it?
In the project you're find two files, MorseCode.cs, and Program.cs

MorseCode.cs:
A class file which, once instantiated with a message string, will allow you to send out your message with a simple loop and parsing 4 different possibilities (Dot,Dash,LetterGap,WordGap) and send them off as you choose. It's not amazingly optimized but it does it's job good enough. If anyone has suggestions please feel free to include a modified file or said suggestions.

Program.cs:
A simple example which transmits the given string (Found near the top of the program) via the onboard LED. It contains an example parse displaying how simple it currently is. I'm considering moving the transmission into the MorseCode class itself and having the caller pass in their desired interface device. But we'll see what happens.

I plan to do some more work on the project if it garners any interest, otherwise feel free to do what you wish with it!

Regards,
Andrew (Hoverbear)