It’s important to emphasize that Teletype does not require any other modules or hardware to function. It comes with a keyboard, which is the only thing it needs.
Regarding Ansible, the best way to think about it is a 6HP multi-module where most of the functionality is broken out into a large, tactile external interface that doesn’t eat up HP. When connected to Grids, you can choose between Kria or Meadowphysics with the push of a button. Kria is a very good step sequencer, while Meadowphysics is a very good trigger and gate generator (it can also generate CV sequences, but I don’t use it as much). When connected to an Arc, you get Cycles and Levels. Cycles is a quad LFO with some physical rules (friction) and frequency dividing, while Levels is an offset generator with sequencing.
Alternatively, without Grids or Arc, Ansible can be used as a Teletype expander (more outputs!) or as a MIDI-to-CV converter. In the MIDI-to-CV conversion modes, you can convert USB MIDI data to CV in all sorts of ways, including arpeggiation. In that regard, the Ansible becomes something like the Expert Sleepers FH-1.
If you have an Ansible, you don’t need both a Grids and an Arc. However, you can’t use the associated modes if you don’t have the associated hardware.
The “Remote” functionality is a way for Teletype to communicate with other modules using an i2c cable behind the modules. The Ansible does not have CV inputs, so a Teletype becomes the only way to externally modulate its behavior. You can write scripts on Teletype that do simple things to change the Ansible’s behavior. For instance, “If Teletype receives a trigger on input 1, reset this row on Meadowphysics” or “If Teletype receives a trigger on input 2, change the speed of the Cycles LFO 1 by amount X”… This scripts can become much more complicated if you want.
@scanner_darkly is adding a way to control Teletype from Grids, but it’s still in beta. It will also require a power solution. It’s worth noting that it exists, though.
