Announcement

Collapse

Forum Rules and Etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Rule 1: Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Rule 2: Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Rule 3: Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


Rule 4: "PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Rule 5: Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

Morse-Baudot

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Morse-Baudot

    Does anyone else have one of these Morse-Baudot S-100 boards by Curtis Electro? It looks like basically a fancy UART with onboard ROMs to presumably handle ASCII to Morse conversion. I'm interested to learn how it operates, would it take an audio input from a HAM radio via the RCA jack and decode the dots and dashes? There's also an empty DIP socket in the upper left, perhaps a connection to some other peripheral. I don't know HAM radio, so wondering if someone else can take a more educated guess.

    The big chip on the board is an AY-5-1013a

    IMG_2511.jpg

    #2
    Not sure at this stage in computing any one was good at converting received morse to dots and dashes on screen. The trouble is that certaining when this card was built a lot of morse was hand sent so there is a lot of variability in for example the lengths of the dots and dashs, which computer programs find hard to work with. Do I have that right? There are 8k of code on there? I think you need a manual
    Dave
    G4UGM

    Looking for Analog Computers, Drum Plotters, and Graphics Terminals.

    Comment


      #3
      FWIW, Jack Curtis passed away last year at age 87. He was known mostly for his keyer devices.
      Reach me: vcfblackhole _at_ protonmail dot com.

      Comment


        #4
        Looking at the back of the board, the empty socket may have had an op-amp. It looks to have unusual power pins. I suspect they are +/- 15V.
        Dwight

        Comment


          #5
          Using an IMSAI with the Cromemco 8K bytesaver (I knew it would come in handy some day) I was able to dump the contents of the ROMs into a HEX file capture on my laptop terminal and from there convert it to a 7K binary. The address switches on the Morse-Baudot board were set to A0, presumably that's where the ROM code would start. It should be Intel 8080 code.

          It is a curious question how this thing would work if decoding human generated Morse code, perhaps it was only meant to receive from another Morse-Baudot board, that way one could expect a fixed rate of transmission.ROMs.txt

          Comment


            #6
            There were (and are) programs that decode hand sent morse. Basically you use heuristics to work out if its a dot, dash and if the space is an inter-element space. This paper (behind a pay wall) dates from 1959 so folks have been looking at it for a while...

            https://ieeexplore.ieee.org/document/1057478

            have a google...
            Dave
            G4UGM

            Looking for Analog Computers, Drum Plotters, and Graphics Terminals.

            Comment


              #7
              Originally posted by new_castle_j View Post
              I was able to dump the contents of the ROMs into a HEX file capture on my laptop terminal and from there convert it to a 7K binary. [ATTACH]55721[/ATTACH]
              Just a question about the file as the whole Rom thing worries me in terms of data retention and I'm fairly new to programming and using Roms. In that file, towards the end, there are some broad zones where a number of the byte values have gone to (or were originally FF). Is that the sort of appearance one gets in a Rom file when there is Rom rot ? Or would it look different ? I noticed that there were no light occlusive covers over the Rom windows, so they might have been more at risk of it ?

              Comment


                #8
                Sometimes (and you find this in a lot of early code), routines need to be at fixed locations, so the intervening unused spaces simply aren't programmed.
                Reach me: vcfblackhole _at_ protonmail dot com.

                Comment


                  #9
                  I believe 2708s erase to 0FF so 0 is ok.
                  Dwight

                  Comment


                    #10
                    Originally posted by Chuck(G) View Post
                    Sometimes (and you find this in a lot of early code), routines need to be at fixed locations, so the intervening unused spaces simply aren't programmed.
                    So you are saying that the sort of appearance seen there in that file with the zones of FF's you would judge as probably original programming ?

                    Comment


                      #11
                      According to the attached article, the ROM software on this board was developed on an ALTAIR with a Tarbell cassette system, an ASR-33 Teletype and some SOL-20 boards and utilities. Oh, and a Cromemco Bytesaver! Examining the HEX, there's some oddball sections like this one:

                      RAMjunk.jpg

                      Stuff like that is likely garbage that was left over in RAM when the code was burned into ROM. There's probably a bunch of other garbage scattered throughout the ROM image as well. After reading the manual on how ROMs were written from an Altair front panel and a Bytesaver board, it makes perfect sense. You would get your code running in RAM, then copy that RAM into the ROM, it would include all the artifacts that were left in RAM at the time.

                      curtisElectro.jpg

                      Comment


                        #12
                        There were also editor/assemblers that were completely RAM resident (e.g. Processor Technology) along with the source files. I used one on my Altair. Worked pretty well for what it was. That's likely where the source code comes from--the editor was one that used a BASIC-type line numbering system.
                        Reach me: vcfblackhole _at_ protonmail dot com.

                        Comment


                          #13
                          Originally posted by Hugo Holden View Post
                          So you are saying that the sort of appearance seen there in that file with the zones of FF's you would judge as probably original programming ?
                          Some would intentionally fill with 0's. Others would leave these areas blank. Some would even fill with whatever garbage was in the unspecified RAM at that time. I know that the programmer for Heathkit was religious as he'd put something related in the empty locations. Most programs that used a checksum byte at the end of a ROM image would pad with 0's. My point was that erased by age would float to 0FFh rather than 00.
                          Dwight

                          Comment


                            #14
                            The only way to really be certain is to dump the PROMs and disassemble them to see if the code makes any sort of sense.

                            My money's on the 0ffh areas simply being unprogrammed. I imagine that the PROM programmer source was in the form of Intel .HEX files, which need not present contiguous data--there can be gaps and it's considered to be perfectly normal. A smart EPROM programmer would ensure that unused areas remained ff's.
                            Reach me: vcfblackhole _at_ protonmail dot com.

                            Comment


                              #15
                              I have seen this board listed on eBay during the summer (several months).

                              From the 1970s to mid-1980s there were a variety of Morse/Bardot products (discrete & IC designs),
                              before the usage of Digital Signal Processors (DSP) in late 1980s (Texas Instruments & Motorola chips).

                              Since the FCC did not permit the usage of ASCII during the 1970s, the majority of the products
                              decoded Continuous Wave (CW)/Morse Code and 5-bit Baudot / Radio Teletype (RTTY). This changed by 1984 (AT&T Break-up).

                              The more advanced amateur radio products used keyboard (computer’s or dedicated)
                              to encode for transmission (Audio Output & Push-To-Talk)
                              ==
                              Curtis Electro Devices was founded by Jack Curtis, K6KU (sk, 2018 ).
                              Jack designed “purpose built” ICs at Signetics (his 8044 series) in 1970s.
                              This specific board was very expensive, and not often seen.
                              http://www.arrl.org/news/curtis-keye...curtis-k6ku-sk

                              The RCA Jack should connect to Audio Output of a Shortwave Receiver,
                              THEN tune the radio to a CW (Morse) or Bardot (RTTY) transmission.

                              greg
                              w9gb
                              ==
                              In mid-1960s Bill Henry (Illinois BSEE) founded HAL Communications in Urbana, IL (before A. Clarke/S. Kubrick “2001”)
                              and had a number of dedicated RTTY and CW products throughout same period (1970-1990s).
                              Bill retired in 2012 ... but is still with us.
                              http://www.halcomm.com/about/history/
                              Last edited by w9gb; September 3, 2019, 04:57 PM.

                              Comment

                              Working...
                              X