TS-MULTI-104: Difference between revisions
No edit summary |
No edit summary |
||
Line 36: | Line 36: | ||
<source lang=bash> | <source lang=bash> | ||
serial8250: ttyS2 at MMIO 0xee0003f8 (irq = | serial8250: ttyS2 at MMIO 0xee0003f8 (irq = 70) is a 16550A | ||
</source> | </source> | ||
So in this case the COM device will be /dev/ttyS2. You can use a terminal emulator like minicom or picocom to quickly test communication. Upon typing "AT" and pressing enter, the modem should respond with OK. | So in this case the COM device will be /dev/ttyS2. You can use a terminal emulator like minicom or picocom to quickly test communication. Upon typing "AT" and pressing enter, the modem should respond with OK. | ||
== Getting a Data Connection === | |||
Using our Linux boards you would use pppd to dial up to your carrier. For example, these scripts will work with tmobile: | |||
/etc/ppp/peers/tmobile | |||
<pre> | |||
/dev/ttyS2 | |||
noauth | |||
115200 | |||
debug | |||
usepeerdns | |||
persist | |||
defaultroute | |||
replacedefaultroute | |||
</pre> | |||
/etc/ppp/chatscripts/tmobile | |||
<pre> | |||
TIMEOUT 10 | |||
ABORT 'BUSY' | |||
ABORT 'NO ANSWER' | |||
ABORT 'ERROR' | |||
"" 'AT+CGDCONT=1,"IP","wap.voicestream.com"' | |||
ABORT 'NO CARRIER' | |||
OK 'ATD*99***1#' | |||
CONNECT | |||
connect "/usr/sbin/chat -v -f /etc/ppp/chatscripts/tmobile" | |||
disconnect "/usr/sbin/chat -v -f /etc/ppp/chatscripts/tmobile-disconnect" | |||
</pre> | |||
/etc/ppp/chatscripts/tmobile-disconnect | |||
<pre> | |||
"" "\K" | |||
"" "+++ATH0" | |||
</pre> | |||
Using a different carrier you will likely only need to replace wap.voicestream.com with the access point for your carrier. | |||
== Frequency Selection == | |||
{{Note|The MTSMC-H5 must be ordered with the correct model for the intended HSDPA service provider. This model cannot be reconfigured in software.}} | |||
The default configuration for the MTSMC-G2 module is for 1900MHz/850MHz which is used in the US, but this is configurable through software. You can find a list of gsm frequencies used by various countries [http://www.worldtimezone.com/gsm.html here]. If you require 900MHz/1800MHz you can add in the line before the AT+CGDCONT line in your chat script: | |||
<pre> | |||
"" 'AT+WMBS,5,1' | |||
</pre> | |||
You can replace the 5 with any from this table: | |||
{| class=wikitable | |||
|- | |||
! Band | |||
! Frequency | |||
|- | |||
| 0 | |||
| 850MHz | |||
|- | |||
| 1 | |||
| 900MHz extended (900E) | |||
|- | |||
| 2 | |||
| 1800MHz | |||
|- | |||
| 3 | |||
| 1900MHz | |||
|- | |||
| 4 | |||
| 850MHz/1900MHz | |||
|- | |||
| 5 | |||
| 900E / 1800MHz | |||
|- | |||
| 6 | |||
| 900E / 1900MHz | |||
|} | |||
The second argument of 1 tells the modem to restart immediately on the requested frequencies. | |||
= Features = | = Features = |
Revision as of 09:44, 28 November 2012
Product Page | |||
Documentation | |||
---|---|---|---|
Multitech Universal Socket Products | |||
Operating Temperature | |||
| |||
| |||
Some modems have smaller operating temperatures | |||
Mechanical | |||
96mm X 89mm | |||
Weight 20.4 (approx) |
Overview
The TS-MULTI_104 is a PC/104 device that carries Multitech socket modems. It uses a standard 16550 driver, and is designed to work with nearly all PC/104 hosts.
Getting Started
The TS-MULTI_104 will use the standard 16550 driver provided by the host system, but the driver will need to know the COM address and IRQ which are both selected by the onboard jumpers.
This example is for a TS-7800 with only IRQ6 on. If you have K1 populated you should also have the "1.8MHz" jumper on to get started.
# If you are in Debian the next 2 lines will turn on the PC104 bus
. /initrd/ts7800.subr
pc104on
modprobe ts7800_isa16550 irq=6 io=0x3F8
To view if it loaded correctly, run 'dmesg' and you should find a line similar to this:
serial8250: ttyS2 at MMIO 0xee0003f8 (irq = 70) is a 16550A
So in this case the COM device will be /dev/ttyS2. You can use a terminal emulator like minicom or picocom to quickly test communication. Upon typing "AT" and pressing enter, the modem should respond with OK.
Getting a Data Connection =
Using our Linux boards you would use pppd to dial up to your carrier. For example, these scripts will work with tmobile:
/etc/ppp/peers/tmobile
/dev/ttyS2 noauth 115200 debug usepeerdns persist defaultroute replacedefaultroute
/etc/ppp/chatscripts/tmobile
TIMEOUT 10 ABORT 'BUSY' ABORT 'NO ANSWER' ABORT 'ERROR' "" 'AT+CGDCONT=1,"IP","wap.voicestream.com"' ABORT 'NO CARRIER' OK 'ATD*99***1#' CONNECT connect "/usr/sbin/chat -v -f /etc/ppp/chatscripts/tmobile" disconnect "/usr/sbin/chat -v -f /etc/ppp/chatscripts/tmobile-disconnect"
/etc/ppp/chatscripts/tmobile-disconnect
"" "\K" "" "+++ATH0"
Using a different carrier you will likely only need to replace wap.voicestream.com with the access point for your carrier.
Frequency Selection
Note: | The MTSMC-H5 must be ordered with the correct model for the intended HSDPA service provider. This model cannot be reconfigured in software. |
The default configuration for the MTSMC-G2 module is for 1900MHz/850MHz which is used in the US, but this is configurable through software. You can find a list of gsm frequencies used by various countries here. If you require 900MHz/1800MHz you can add in the line before the AT+CGDCONT line in your chat script:
"" 'AT+WMBS,5,1'
You can replace the 5 with any from this table:
Band | Frequency |
---|---|
0 | 850MHz |
1 | 900MHz extended (900E) |
2 | 1800MHz |
3 | 1900MHz |
4 | 850MHz/1900MHz |
5 | 900E / 1800MHz |
6 | 900E / 1900MHz |
The second argument of 1 tells the modem to restart immediately on the requested frequencies.
Features
COM Port Address
COM | I/O | COM1 Jumper | COM2 Jumper | COM3 Jumper |
---|---|---|---|---|
COM1 | 0x3F8 | OFF | OFF | OFF |
COM1 | 0x3F8 | ON | OFF | OFF |
COM2 | 0x2F8 | OFF | ON | OFF |
COM3 | 0x3E8 | OFF | OFF | ON |
COM4 | 0x2E8 | ON | OFF | ON |
COM5 | 0x3A8 | OFF | ON | ON |
COM6 | 0x2A8 | ON | ON | ON |
PLD
The TS-MULTI_104 board contains a PLD with 1 register. This is available at offset 0x140, or if you depopulate
IRQ Selection
The IRQ can be selected by the jumpers labelled IRQ3 through IRQ7. On most of our SBCs only IRQ5-7 are used.
Faster Data Rates
When used with the GPRS modems and those requiring a maximum baud rate of 115200, you can use the PC104 clock to generate a 18.4MHz clock needed for the 16550. When using faster modems like the H4 for an HSDPA connection, K1 can be populated with a 14.7456MHz crystal. This will allow you to reach baud rates up to 921600. If you have K1 populated, you can set the jumper 1.8MHz to use the PC104 clock for standard baud rates.
To set a custom baudrate in Linux you would typically use the setserial command. When the spd_cust baud rate it set Linux will re-purpose 38400 to use your custom baud rate.
Divisor | Rate |
---|---|
1 | 921600 |
2 | 460800 |
3 | 307200 |
4 | 230400 |
5 | 184320 |
6 | 153600 |
7 | 131657 |
8 | 115200 |
Larger divisors will also work, but this should cover the common range. Using the setserial command you can specify the divisor. For example, to reach 460800
# ttyS4 is an example, but check "dmesg" after loading
# your 16550 driver to get the device
setserial /dev/ttyS4 spd_cust baud_base 921600 divisor 2
Note: | Custom baud rates can be up to 5% off of your target baud rate, and communication will still be possible with most devices. |
In your linux application you would set the baud rate to 38400, and access it as normal which will actually communicate at your faster speeds. The Linux Documentation Project has more details on serial programming.
Product Notes
FCC Advisory
This equipment generates, uses, and can radiate radio frequency energy and if not installed and used properly (that is, in strict accordance with the manufacturer's instructions), may cause interference to radio and television reception. It has been type tested and found to comply with the limits for a Class A digital device in accordance with the specifications in Part 15 of FCC Rules, which are designed to provide reasonable protection against such interference when operated in a commercial environment. Operation of this equipment in a residential area is likely to cause interference, in which case the owner will be required to correct the interference at his own expense.
If this equipment does cause interference, which can be determined by turning the unit on and off, the user is encouraged to try the following measures to correct the interference:
Reorient the receiving antenna. Relocate the unit with respect to the receiver. Plug the unit into a different outlet so that the unit and receiver are on different branch circuits. Ensure that mounting screws and connector attachment screws are tightly secured. Ensure that good quality, shielded, and grounded cables are used for all data communications. If necessary, the user should consult the dealer or an experienced radio/television technician for additional suggestions. The following booklets prepared by the Federal Communications Commission (FCC) may also prove helpful:
How to Identify and Resolve Radio-TV Interference Problems (Stock No. 004-000-000345-4) Interface Handbook (Stock No. 004-000-004505-7) These booklets may be purchased from the Superintendent of Documents, U.S. Government Printing Office, Washington, DC 20402.
Limited Warranty
See our Terms and Conditions for more details.