TS-RF2-AERO: Difference between revisions
No edit summary |
|||
| Line 21: | Line 21: | ||
== Getting Started == | == Getting Started == | ||
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. | 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. The datasheet will specify the baud rate range, but make sure you enable hardware flow control. Please consult the Aerocomm data sheet for more information on Aerocomm specific features which can be invoked using AT commands. | ||
Revision as of 11:13, 21 July 2011
 | |
| Documents | |
|---|---|
| Schematic | |
| AC4790 Product Page | |
| AC4790 Datasheet | |
| AC4790 User Manual |
Overview
The TS-RF2-Aero provides a UART connecti over PC104 to the AeroComm/Laird AC4790 RF device.
Driver
The driver is available here. You can install the module to your kernel module directory (usually /lib/modules/<kernel version>) and use modprobe, or run 'insmod ts-rf2.ko' with the absolute path of the module. If you receive a message that the symbols are invalid, you will have to compile that module with your kernel sources. The sources are available in the same directory as the binaries.
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 ttyTSx for the TS-72XX series, or from tttsx where x is an integer denoting the order in which the driver was loaded. You can run dmesg after loading the driver to see where it is created.
Getting Started
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. The datasheet will specify the baud rate range, but make sure you enable hardware flow control. Please consult the Aerocomm data sheet for more information on Aerocomm specific features which can be invoked using AT commands.