6.1. Terms

Bluetooth address (bdaddr) is six hex digits separated by a colon. For example, "00:07:80:80:bf:01". With commands requiring Bluetooth address, you can also use Bluetooth friendly name instead.

Bluetooth channels are numbered from 1 to 30. In Access Server, the Serial Port Profile is assigned to channel number two, the Object Push Profile and File Transfer Profile to channel number three and the LAN Access Profile is on channel number four. The other channels are free for user applications.

Link Identifier (link_id) is a number from 0 to 99 used to identify established Bluetooth connections.

6.2. Starting the iWRAP Servers

Normally, the iWRAP servers are started automatically upon power-up. You can restart the servers manually (for example, to apply the changes made to the iWRAP settings with setup application without rebooting the system). To restart the servers manually, execute the startup script with option restart:

[root@wrap /] /etc/init.d/bluetooth restart

When the iWRAP servers start up, it uses the settings configured with the setup application. You can put your extra iWRAP commands in the /etc/bluetooth.conf file. The commands in that file are processed as the last task every time iWRAP server is started.

6.3. Writing iWRAP Applications

There are two approaches when writing a iWRAP server program (a program accepting incoming calls) for the Access Server, both having different pros and cons:

1. Forklistener

2. iWRAP Client

When writing a client program (a program making an outgoing call), you have to use iWRAP.

6.4. Commands Controlling iWRAP

6.5. Finding Bluetooth Devices

6.6. Making a Bluetooth Connection

6.7. Service Discovery

This section describes the commands used for Bluetooth service discovery and local SDP record manipulation. The commands and their replies make use of SDP UUID and attribute values, which are listed in the Bluetooth Assigned Numbers documentation. In the commands documented below, the most useful UUID and attribute values can, however, be replaced with keywords listed in Table 6-3. The same keywords are used in the command replies instead of numeric values, if the parameter SET BLUETOOTH READABLE is set to 1.

6.8. Example Sessions

Outgoing RFCOMM Call:

      READY.
      CALL 00:07:80:80:bf:01 1 RFCOMM
      CALL 2
      RINGING 2
      CONNECT 2 RFCOMM 1042
      STATUS 2 MSC 8d
      <Client opens socket connection to port 1042 and transfers data>
      CLOSE 2
      NO CARRIER 2 ERROR 000
    

Incoming RFCOMM Call:

      READY.
      RING 2 00:07:80:80:bf:01 1 RFCOMM 1042
      STATUS 2 MSC 8d
      <Client opens socket connection to port 1042 and transfers data>
      NO CARRIER 2 ERROR 000
    

6.9. Error Codes

Some commands may reply with an error code. The human-readable name of the error is displayed as well, if the SET BLUETOOTH READABLE setting has a value of 1. Error code 8 indicates that the iWRAP server is busy executing any number of commands; there can be several client applications using the stack. Just wait a few seconds and try again. Other error codes indicate unexpected, but often only temporary, communication problems.

You can analyze the error from the numeric code. Values bigger than or equal to 900 are iWRAP errors, described in Table 6-5.

Other error codes can be analyzed as follows. For example NO CARRIER ERROR 465: The number 465 is hexadecimal, sum of 0x400 and 0x65, where 0x400 is a mask which means this is an RFCOMM level error and 0x65 (decimal 101) that the RFCOMM error was connection timeout.

The error codes for each mask are listed in the following tables.

If the problems persist after restarting the communication parties, please contact Bluegiga Technologies as instructed in Section 1.2.