Convert Morse code to a timed light signal pattern

Enter dots and dashes, separate letters with spaces, place a slash between words, and choose the duration of one timing unit in milliseconds. The converter returns each on and off event in order, along with useful duration totals. It follows the familiar Morse proportions for dots, dashes, symbol gaps, letter gaps, and word gaps, while rejecting characters that do not belong in Morse input.

Write the Morse input with clear separators

Enter each encoded letter as one uninterrupted group of dots and dashes. Put whitespace between letter groups and use a forward slash between words. For example, the familiar distress signal is written as ... --- ..., while two words might look like .... .. / - .... . .-. .. Spaces around the slash are optional because the converter normalizes them in its result. The input is intentionally strict about its alphabet: only dots, dashes, whitespace, and the slash word separator are accepted. A letter is not checked against a dictionary of assigned Morse characters, because the job here is to time the supplied pulse pattern, including procedural or custom sequences. However, an unrelated character such as an asterisk, letter, digit, or underscore produces an input error with its position. Empty words and a slash at either end are also rejected, preventing an ambiguous silent interval from entering a device schedule. This makes the accepted notation compact enough to paste from an encoder while remaining predictable for automation.

Understand how the timing units become milliseconds

Choose unit_ms as the duration of a single Morse unit. Every dot keeps the light on for one unit, and every dash keeps it on for three. A pause of one unit separates adjacent symbols inside the same letter. A pause of three units separates letters, and a pause of seven units separates words. With a 100 millisecond unit, a dot is therefore 100 milliseconds on, a dash is 300 milliseconds on, and a word gap is 700 milliseconds off. The returned sequence is chronological and uses explicit on and off records, so a program can process it from the first item to the last without interpreting punctuation again. There is no trailing off record after the final symbol: the output describes the signal itself, not an arbitrary amount of silence after it finishes. Durations use integer multiplication, and the unit must be a whole number from 1 through 60,000 milliseconds. Those rules keep every reported duration exact and suitable for timers that accept millisecond values.

Use the sequence in lights, previews, and tests

The event list is useful anywhere a Morse pattern must cross from text into timing logic. A microcontroller script can iterate over the records, set an LED to the requested state, and wait for duration_ms before advancing. A browser preview can use the same list to animate a lamp icon, while an accessibility project can transform on events into vibration or audio without changing the spacing. Alongside the sequence, the result reports the normalized Morse notation, event count, accumulated on time, accumulated off time, and complete duration. Those totals help you size an animation, compare sending speeds, or assert that an implementation has preserved the intended rhythm. Hardware and operating-system timers can introduce scheduling latency, so the converter does not promise physical transmission precision; it supplies the ideal deterministic schedule. It also does not translate ordinary language into Morse. If you begin with letters or words, encode them first, then pass the resulting dots and dashes here to obtain the light pattern.