iPod IWIP3G User Guide - Page 120

iPod IWIP3G - IWRAP - IPHONE 3G Manual

Page 120 highlights

normal mode, the data is stored to small iWRAP buffers and received when the connections become active (data mode of the connection enabled). The next figure illustrates the host-iWRAP-host communications in multiplexing mode. Host UART Figure 4: Host-iWRAP-Host communication The figure below illustrates host-iWRAP-remote device communication when multiplexing mode is in use. The key thing is that the remote device does not need to know anything about the multiplexing communication and frame format, but it sees the connection as a standard Bluetooth connection. Host UART Data Bluetooth link Data Figure 5: Host-iWRAP-remote device communications At the moment, four (4) simultaneous connections can be used in multiplexing mode. Tips: In MUX mode the processor of the module is highly utilized and on the edge of its performance. This may be seen as a instability of Bluetooth connections, especially if 3 or more connections are used or data rate is high. There are however a few tricks how the stability of the Bluetooth connections can be improved: 1. Use SNIFF mode: Using sniff mode reduces the rate the master device needs to poll the active connections are leaves more time for the processor to parse or generate the multiplexing protocol. Therefore as aggressive as possible sniff mode should be used. 2. Optimize Bluetooth packet size by using MTU option in CALL command: Using smaller Bluetooth packet size improves the multiplexing performance. On the next page, there is a simple C-code example on how to create a simple multiplexing frame containing an iWRAP command. 120

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211

120
normal mode, the data is stored to small iWRAP buffers and received when the
connections become active (data mode of the connection enabled).
The next figure illustrates the host-iWRAP-host communications in multiplexing mode.
Host
UART
<0xBF> <0xFF> <0x00> <2> <AT> <0x00>
<0xBF> <0xFF> <0x00> <2> <OK> <0x00>
Figure 4:
Host-iWRAP-Host communication
The figure below illustrates host-iWRAP-remote device communication when multiplexing
mode is in use. The key thing is that the remote device does not need to know anything
about the multiplexing communication and frame format, but it sees the connection as a
standard
Bluetooth
connection.
Host
UART
Bluetooth link
<0xBF> <0x00> <0x00> <len> <Data> <0xFF>
<0xBF> <0x00> <0x00> <len> <Data> <0xFF>
Data
Data
Figure 5:
Host-iWRAP-remote device communications
At the moment, four (4) simultaneous connections can be used in multiplexing mode.
Tips:
In MUX mode the processor of the module is highly utilized and on the edge of its
performance. This may be seen as a instability of
Bluetooth
connections, especially if 3 or
more connections are used or data rate is high. There are however a few tricks how the
stability of the
Bluetooth
connections can be improved:
1.
Use SNIFF mode: Using sniff mode reduces the rate the master device needs to poll
the active connections are leaves more time for the processor to parse or generate
the multiplexing protocol. Therefore as aggressive as possible sniff mode should be
used.
2.
Optimize
Bluetooth
packet size by using MTU option in CALL command: Using
smaller
Bluetooth
packet size improves the multiplexing performance.
On the next page, there is a simple C-code example on how to create a simple
multiplexing frame containing an iWRAP command.