User Manual
Table Of Contents
- INTRODUCTION
- CONTROLLING THE ACCESS SERVER
- CONFIGURATION
- USING THE SYSTEM
- BLUETOOTH TECHNOLOGY OVERVIEW
- INTRODUCTION TO SDK
- INSTALLING THE WRAP SOFTWARE DEVELOPMENT ENVIRONMENT
- CREATING WRAP APPLICATIONS
- BLUETOOTH SERVER SOCKET INTERFACE
- I/O API
- ABOUT BLUEGIGA
- APPENDIX A – WRAP DIRECTORY STRUCTURE
USER'S AND DEVELOPER'S GUIDE WRAP MULTIRADIO ACCESS SERVER
Serial Cable
User
device A
User
device B
Serial
Cable
User
device A
User
device B
Serial
Cable
WRAP
DevA
WRAP
DevB
Bluetooth
A)
B)
Figure 3. Serial Cable Replacement Physical Setup.
State A) in the figure is the starting situation with a serial cable connecting the devices. This
cable is to be replaced with a Bluetooth connection.
In state B) the long serial connection is replaced with a Bluetooth Serial Port Profile connection
between the two WRAP devices. These WRAP devices are then connected locally to the user
devices with (short) serial cables. The cable between user device A and WRAP device A must
be a cross-over cable. The cable between user device B and WRAP device B must be similar
(direct or cross-over) to the one used in state A).
If RTS/CTS handshaking is used to ensure correct data transfer, the serial cables must have
these pins connected. Note: This handshaking is "local": it takes place between the user
device and the WRAP board. No handshaking between user device A and user device B on the
other end of the Bluetooth connection is provided.
If RTS/CTS handshaking is not used, CTS must be connected to DTR.
DCD, DTR, and DSR signals are not supported. This also means that user devices A and B will
not be able to tell whether or not the Bluetooth connection is up.
When the physical setup is ready, you can create the Bluetooth connection. By default, the
Serial Port Profile is started up at boot with the default settings. That is, listening in DevB
mode, at 9600 bps, 8 data bits, no parity, 1 stop bit, and RTS/CTS enabled. To change these
settings, use the "setup" application, as described in section 3.1.2.3.
You can also start the Serial Port Profile manually by calling its init script: "/etc/init.d/spp
start".
Note: When the Serial Port Profile is enabled, the WRAP SMS Gateway Server can not be used,
as they share the same physical user serial port
4.1.4 O
BJECT PUSH AND FILE TRANSFER PROFILE
The WRAP also has two OBEX profiles: the Object Push Profile (ObjP) and the File Transfer
Profile (FTP). You can use these profiles to transfer files easily between different WRAP devices
and other devices supporting them.
Bluegiga Proprietary, Copyright © Bluegiga Technologies 2001-2004 23 (94)