User Manual

Table Of Contents

USER'S AND DEVELOPER'S GUIDE WRAP MULTIRADIO ACCESS SERVER

Usage:

serialbluetooth [options]

To see the options, enter the command "serialbluetooth --help".

Basically, serialbluetooth takes commands from a serial port and forwards them to the

Bluetooth server. All the commands available via socket interface are also available via serial

port.

There are two exceptions:

1) After making an outgoing RFCOMM data call, all input from the serial port is forwarded to

the data socket, not the control socket. To close the data socket, you have to write "+++" with

a 200ms pause before each character. There is no way to have two concurrent RFCOMM calls.

2) All incoming RFCOMM calls are answered automatically. Again, to close the data socket,

write "+++" as with the outgoing call.

4.2 C

OMPACT FLASH GPRS CARD

The Compact Flash GPRS card is identified automatically by the operating system when

inserted. At that time, the device file "/dev/ttyS0" is created.

A GPRS connection is made with command "pppd call gprs" and closed by killing the pppd –

process handling the GPRS connection.

The connections settings are in the directory "/etc/ppp/peers". The default GPRS call settings

work with major Finnish operators (TeliaSonera, Radiolinja, DNA).

If needed for special use, the Compact Flash GPRS card can also be accessed directly from

"/dev/ttyS0".

4.2.1 SIM C

ARD’S PIN CODE

If your SIM card has PIN code checking enabled, insert the following line just after the line '""

AT' in file "/etc/ppp/peers/gprs.connect":

OK 'AT+CPIN="pincode"'

4.2.2 GPRS TROUBLESHOOTING

If you don’t get connection, check "/var/log/messages". To get more verbose error messages

from the GPRS modem, enable more verbose error codes by adding line "OK 'AT+CMEE=2'"

just after the line '"" AT' in file "/etc/pp/peers/gprs.connect".

4.2.3 C

ONSOLE MESSAGE "SERIAL_CS: PARSETUPLE: BAD CIS TUPLE"

Sometimes, the Compact Flash GPRS card does not get identified. Instead, an error message

"serial_cs: ParseTuple: Bad CIS tuple" appears at console and the device file "/dev/ttyS0" is

not created. This happens most likely because of timing problems but there is no fix available

yet.

As a workaround, one can force the identification process to restart with the command line: "[

! -c /dev/ttyS0 ] && cardctl eject && cardctl insert".