
RN Commands Version 4.25, 11/1/2007 Page 16 of 25
www.rovingnetworks.com
The default profile is Serial Port Profile (SPP). The firmware also supports the DUN profile in both master and
slave modes. To change the profile, use the “S~,<num>” command.
Profile:
0 - Default SPP. (no modem control)
1 - DUN DCE (slave or gateway).
2 - DUN DTE ( master or client).
3 - MDM SPP with modem control signals.
The most common use of DUN profile is to enable a BT client to connecti to a dialup modem. For this mode, use
profile 1 (DUN DCE) via command “S~,1” . You may also want to set the Class Of Device so that clients can
recognize the device as a Bluetooth modem. The correct COD for a Bluetooth modem is 0x040210. This can be
set using the commands below:
“SC,0004”
“SD,0210”
A number of modem control signals are supported when in DUN or MDM modes and their use is described below.
4.2 PIOs used as modem control signals
The Firefly and RN-XX modules have the ability to replicate the required modem control hardware signals
automatically once a connection is made. These signals are transferred outside the data channel (using
RFCOMM control channels) and are automatically updated. The default SPP profile (profile=0) does NOT drive
these signals or report back inputs. If DUN or MDM profiles are enabled (pofile =1,2, or 3), the following
signals are automatically driven and received.
Inputs: (read and sent back over Bluetooth to the remote host).
PIO3 = DCD ( switch 2)
PIO6 = DSR (switch 3)
PIO7 = CTS (switch 4)
Inputs are ACTIVE LOW.
Outputs: (sent from the remote Bluetooth host, and driven out )
PIO10 = DTR - this is ACTIVE HIGH
PIO11 = RTS - this is ACTIVE LOW.
On the Firefly, the DIP switches can also be used to set/clear the DCD, CTS, and DSR signals. DTR and RTS are
available on the 9 pin header as well.
Kommentare zu diesen Handbüchern