You will first need to obtain the TS-UART loader:
http://ftp.embeddedarm.com/rf2/
You will need to compile the tsuart-rf.c kernel module, or else download the pre-compiled module (if available).
Next install the module in the appropriate location for your distribution. Typically this will involve copying the .o files the somewhere in the /lib/modules directory, and possibly running a utility such as depmod to bring your module list up to date. Please consult the documentation for the distribution you are using for further information.
Note: If all else fails, you can always run the following command in the directory the module is stored in:
insmod ./tsuart-rf.oNote: The tsuart0.o module must be loaded before the above loader module can successfully run. If you are using a module dependency program such as modprobe these dependencies should be resolved for you automatically.
Once loaded, a new TS-UART device file will appear in /dev. The exact name of this file will depend on the the number of TS-UARTs already loaded on your system, but the name of the driver will be of the form:
ttyTSxwhere x is an integer denoting the order in which the driver was loaded.
Communication with the Aerocomm device defaults to transparent serial mode. If you have two units operational with a terminal emulation program running on both unit you should be able to verify operation by pointing both programs to use the appropriate ttyTS entry, and then typing on either side. Please consult the Aerocomm data sheet for more information on Aerocomm specific features which can be invoked using AT commands.
Technologic Systems has developed a simple protocol for communicating sensor telemetry using the ZIGBEE module; please contact us for more information or if you are interested in having this protocol adapted for the AEROCOMM unit.