User's Guide

USER MANUAL WRAP PRODUCT SERIES
In the state B) the long serial connection is replaced with a Bluetooth Serial Port Profile connection between
the two WRAP devices. Those WRAP devices are then connected locally to the user devices with (short)
serial cables. The cable between the user device A and the WRAP device A must be a cross-over cable. The
cable between the user device B and the WRAP device B must be the same cable (direct or cross-over) that
was 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 the user device A and the user device B on the other end of the Bluetooth
connection is provided.
DCD, DTR and DSR signals are not supported. This also means that the user device A and B will not be able
to tell whether or not the Bluetooth connection is up. If the connection is up, the data flow is guaranteed to be
error free.
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.3.3.
You can also start the Serial Port Profile manually by using the "serialport" application. To see the usage of
this application, give the command "serialport --help" at WRAP command prompt.
Note: When Serial Port Profile is enabled, the WRAP SMS Gateway Server cannot be used as they share the
same physical user serial port
4.1.4 OBJECT PUSH AND FILE TRANSFER PROFILE
WRAP has also two OBEX profiles: the Object Push Profile (ObjP) and File Transfer Profile (FTP). You can
use these profiles to transfer files easily between different WRAP devices and other devices supporting them.
These profiles are handled by forwarding incoming calls to "obexserver" program, which handles both
profiles. The default work directory is /tmp/obex and users have full read and write access there. By default
that directory also contains the default vCard.
Outgoing calls can be made by "obexbrowser" program which is documented in the WRAP SDK Manual.
Two simple command line utilities, "obexput" and "obexget" are also provided. They can be used to send
and retrieve a single file to and from another Bluetooth device supporting OBEX. Give either of the
commands without parameters to get a short help of using the command.
4.2 SERVERS
The WRAP server applications are started automatically at system power-up or when needed by the
Bluetooth server or the Internet services daemon. The servers and their purposes are described in Table 3.
Server Purpose
bluetooth WRAP Bluetooth Server, described in detail in section 4.1 and in WRAP SDK Manual.
httpd WRAP Web Server, described in detail in section 4.2.1.
crond Daemon to execute scheduled commands. Configurable with /etc/crontab in the same way as
any UNIX crond.
ftpd Internet File Transfer Protocol Server. Configurable with /etc/ftpd.conf.
dhcpcd DHCP client daemon for automatic network configuration.
In.telnetd Telnet protocol server.
inetd Internet services daemon
pppd Point to Point Protocol daemon. Used by Bluetooth server. Can be used manually over the user
serial port (/dev/ttyS3).
syslogd System logging daemon. Configurable with the setup application.
smsgw WRAP SMS gateway server, described in detail in section 4.2.2. Note: By default this server
is not started at power-up.
Table 3. WRAP Servers.
16 (26)