telegraph to serial data (long)
Archiver
Posts: 46,084
Raoul,
the ideas listed here are not to discourage but to
give you ideas of what has been done. My wife (and
God, too) knows that I am not an expert at things so I
tend to cheat and use (or buy when I can) other
peoples knowledge. Just thought I would share what I
have found.
I have a Morse Machine II from a company called AEA
(AEA is now owned by Tempo Research in San Diego, CA,
the MM is no longer available). It uses an 8051 to do
almost everything you wrote about. I reads in a
straight or iambic keyer and has the ability to send
the resulting string of key closures to the decoded
ASCII string out the RS-232 port. The code was
probably written in assembly language as they had to
make use of several timing routines to determine Dot
or Dash up to a word speed of 65 words per minute;
something BASIC may have trouble with. You would be a
better man than me for just for trying - remember, I'm
lazy.
MFJ Enterprises (www.mfjenterprises.com) has the
manufacturing rights to a single chip (and a few
discrete components) solution for about $20USD which
will read anybodys "fist" (keying) and creates
perfectly spaced dots and dashes up to 65 words per
minute. It, too, will work with straight or iambic
keyers. The cleaned up output can then be sent off to
the BSII for conversion to whatever output format you
need to send to the internet. This chip is called the
Curtiss Keyer 8045ABM after the original
designer/manufacturer.
To get onto the internet, Microchip
(www.microchip.com), the manufacturers of the PIC
processor of which the BSII is based on, has an
application note on their website about PPP
negotiation. I haven't looked at it in a while. I
believe it was written in C but translating to BASIC
should not be a major undertaking. Someone has also
written an application for a morse code keyer using
the PIC processor. Maybe that application is posted to
this site also.
Next all you have to do is decide the format of the
data going out over the internet from the keyer - as
ASCII characters or as tokens for the individual dots
and dashes. I tend to like ASCII characters myself as
it is a compression of the dots and dashes (the whole
character). Dots and dashes to me represent the
strokes of a pen or pencil in writing the actual
character. Not a bad thing, just that in sending code,
the timeliness of sending and receiving dots and
dashes makes all the difference as to what the
characters being received actually are. We all know
that the internet is a very non-deterministic media
for sending data. Dots and dashes received in out of
time sequence lose their meaning. Converting to ASCII
also makes debugging your code easier as you can write
it to any ASCII terminal!
A word on keyers - I had mentioned straight and
iambic. Straight keys are your classic morse or
telegraph keys in which you pump up and down to create
the dots and dashes. More recently, in geologic times
(remember, basic telegraphy as a technology is about
150 or so years old!), there was a device called a bug
which was moved from side to side in which you created
the dashes and a moving weight created the dots for
you. Electrically, it looked like a straight key - a
single contact closure for either dot or dash. The
"latest" developement for keyers is the iambic keyer
in which there are separate (switch) contacts for dot
and dash, allows for discrete digital logic or
microcontrollers to assist in creating perfectly
spaced dots and dashes for the creation of characters.
The efficiency gained from the iambic keyer was that
there is an auto repeat function (much like the
electric typewriter or keyboard auto repeat) which
would detect either or both dot and dash being
squeezed and continue to generate and correctly
interleave the dots and dashes together. No sore or
well developed wrist and forearm; no carpal tunnel
syndrome from pumping the key!
Professionally, I don't build things anymore. I help
people put things together using my products or I
bring ideas into engineering to have things built.
I've found my niche in life where I can do something
by not producing anything! (remember the comment above
about being lazy?).
Hope I managed to give you some ideas and background.
You've got a great idea. Hope you can get the time to
get it working.
kevin k asato
KC6POB
--- raoul vaneigem <raoul@c...> wrote:
> Hi,
>
> A friend of mine asked me for help, as he wants to
> connect a telegraph to
> the Internet.Cool, I thought, I can do that! But
> then I got scared [noparse];)[/noparse]
>
> Here's my question - would it be enough to just hook
> a switch to the stamp
> using the button command and constantly send the
> result via serout, or do
> you think that I need to...
>
> a) buffer the data in case the telegraph typing time
> is faster than the serout
>
> b) use some kind of handshaking to make sure the
> data is transmitted.
>
> I've successfully used the button command and the
> serout command to send
> data to a computer, but I wanted to see if anyone
> can think of any gotchas
> I might be missing.
>
> Any and all advice gratefully received!
>
>
> To UNSUBSCRIBE, just send mail to:
> basicstamps-unsubscribe@yahoogroups.com
> from the same email address that you subscribed.
> Text in the Subject and Body of the message will be
> ignored.
>
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
the ideas listed here are not to discourage but to
give you ideas of what has been done. My wife (and
God, too) knows that I am not an expert at things so I
tend to cheat and use (or buy when I can) other
peoples knowledge. Just thought I would share what I
have found.
I have a Morse Machine II from a company called AEA
(AEA is now owned by Tempo Research in San Diego, CA,
the MM is no longer available). It uses an 8051 to do
almost everything you wrote about. I reads in a
straight or iambic keyer and has the ability to send
the resulting string of key closures to the decoded
ASCII string out the RS-232 port. The code was
probably written in assembly language as they had to
make use of several timing routines to determine Dot
or Dash up to a word speed of 65 words per minute;
something BASIC may have trouble with. You would be a
better man than me for just for trying - remember, I'm
lazy.
MFJ Enterprises (www.mfjenterprises.com) has the
manufacturing rights to a single chip (and a few
discrete components) solution for about $20USD which
will read anybodys "fist" (keying) and creates
perfectly spaced dots and dashes up to 65 words per
minute. It, too, will work with straight or iambic
keyers. The cleaned up output can then be sent off to
the BSII for conversion to whatever output format you
need to send to the internet. This chip is called the
Curtiss Keyer 8045ABM after the original
designer/manufacturer.
To get onto the internet, Microchip
(www.microchip.com), the manufacturers of the PIC
processor of which the BSII is based on, has an
application note on their website about PPP
negotiation. I haven't looked at it in a while. I
believe it was written in C but translating to BASIC
should not be a major undertaking. Someone has also
written an application for a morse code keyer using
the PIC processor. Maybe that application is posted to
this site also.
Next all you have to do is decide the format of the
data going out over the internet from the keyer - as
ASCII characters or as tokens for the individual dots
and dashes. I tend to like ASCII characters myself as
it is a compression of the dots and dashes (the whole
character). Dots and dashes to me represent the
strokes of a pen or pencil in writing the actual
character. Not a bad thing, just that in sending code,
the timeliness of sending and receiving dots and
dashes makes all the difference as to what the
characters being received actually are. We all know
that the internet is a very non-deterministic media
for sending data. Dots and dashes received in out of
time sequence lose their meaning. Converting to ASCII
also makes debugging your code easier as you can write
it to any ASCII terminal!
A word on keyers - I had mentioned straight and
iambic. Straight keys are your classic morse or
telegraph keys in which you pump up and down to create
the dots and dashes. More recently, in geologic times
(remember, basic telegraphy as a technology is about
150 or so years old!), there was a device called a bug
which was moved from side to side in which you created
the dashes and a moving weight created the dots for
you. Electrically, it looked like a straight key - a
single contact closure for either dot or dash. The
"latest" developement for keyers is the iambic keyer
in which there are separate (switch) contacts for dot
and dash, allows for discrete digital logic or
microcontrollers to assist in creating perfectly
spaced dots and dashes for the creation of characters.
The efficiency gained from the iambic keyer was that
there is an auto repeat function (much like the
electric typewriter or keyboard auto repeat) which
would detect either or both dot and dash being
squeezed and continue to generate and correctly
interleave the dots and dashes together. No sore or
well developed wrist and forearm; no carpal tunnel
syndrome from pumping the key!
Professionally, I don't build things anymore. I help
people put things together using my products or I
bring ideas into engineering to have things built.
I've found my niche in life where I can do something
by not producing anything! (remember the comment above
about being lazy?).
Hope I managed to give you some ideas and background.
You've got a great idea. Hope you can get the time to
get it working.
kevin k asato
KC6POB
--- raoul vaneigem <raoul@c...> wrote:
> Hi,
>
> A friend of mine asked me for help, as he wants to
> connect a telegraph to
> the Internet.Cool, I thought, I can do that! But
> then I got scared [noparse];)[/noparse]
>
> Here's my question - would it be enough to just hook
> a switch to the stamp
> using the button command and constantly send the
> result via serout, or do
> you think that I need to...
>
> a) buffer the data in case the telegraph typing time
> is faster than the serout
>
> b) use some kind of handshaking to make sure the
> data is transmitted.
>
> I've successfully used the button command and the
> serout command to send
> data to a computer, but I wanted to see if anyone
> can think of any gotchas
> I might be missing.
>
> Any and all advice gratefully received!
>
>
> To UNSUBSCRIBE, just send mail to:
> basicstamps-unsubscribe@yahoogroups.com
> from the same email address that you subscribed.
> Text in the Subject and Body of the message will be
> ignored.
>
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com