Agreed that in both Morse code and bell codes there are no specific "baud rates" and the length of the data frame varies per character/code, however the character/code is able to be recognised by the fact that there are start and/or stop pauses, although the duration of these may vary. I guess a pause and stop bit are determined by whether the code is valid and/or a ætimeoutÆ?railwest wrote:The 'problem' with bell codes is that everyone sends at different rates and how long is a long pause before you decide that is the 'stop bit' and not just a long pause?
Truerailwest wrote: With binary data comms systems the electrical signals which represent the 0 or 1 bits are at defined lengths,
Ignoring the low level comms (i.e. 0 and 1s) there are communication systems that don't require pre-defined lengths of packets or headers that state the length of the packet. Also even the time between characters is not always critical. An example of which is 'talking' to an æold fashionedÆ modem using AT commands. As long as the characters are recognised and the message is understood the required action is carried out by the modem.railwest wrote: à à the data is sent in packets either of a pre-defined size or with a 'packet header' which includes the length of the packet.
True, however as explained above a pre-defined length is not always required. The code is deciphered by comparing the number of ding's including possible pauses against a known code list.railwest wrote:With bell codes, when you start to receive a code you have no idea how long that code will be or how many pauses - if any - it will include.
I still think there are enough similarities to classify both Morse and bell codes as a form of binary communication.
