BLUEGIGA - Downloads

BLUEGIGA - FAQ

CMEL - Downloads
GLYN - GSM/GPRS/GPRS Cards FAQ
MAXWELL - Ultracapacitors
TELIT - Downloads
TELIT - FAQ
UNIVISION - OLED FAQ
XMORE - Memory Cards FAQ

 

BLUEGIGA - FAQ

   

Frequenty Asked Questions:


WT11

Q - Is it possible to use one PCB with one common footprint that will be able to use either the WT11 or WT12 module?

A - Yes  a PCB designed for one module can be used with the other module provided the 3 extra pins  on the WT12 (pins 29-31) are not used. Also keep in mind that the PCB meant for both modules must be designed ensuring that there is no ground plane present below the antenna.

Q - If a Bluegiga module is in "PAGEMODE 2" (e.g. command = "SET BT PAGEMODE 2 2000 1"), then would I be correct in saying that no RF transmissions are sent from the module unless a CALL is made to it (e.g. "CALL 00:07:80:80:52:27 1 RFCOMM")? We believe that there will be no RF transmission from the device in "PAGEMODE 2" unless a "CALL" is made to it (completely silent over RF and only receiving data).

A - With PAGEMODE 2 iWRAP cannot be "seen" by other devices in an inquiry. The module is connectable and it can also establish connections of its own. In PAGEMODE 2 the module doesn't emit any RF unless link is opened. The radio is only listening to RF traffic between certain intervals.

Q - We have 3 units on a piconet, A, B and C:
(B) calls (A). (A) is master, (B) is slave on the link - this works.
(C) calls (A). (C) is master, (A) is slave on the link - this doesn't.

We know that we can manually change the link role using "SET {link id} SLAVE", but want to manage the roles automatically using the values set in the command "SET BT ROLE {ms_policy} {link_policy} {supervision_timeout}".

A - We have isolated this bug to the CSR firmware so we really cannot do anything about it immediately. The only workaround for this is that the A device needs to manually give "SET [link id] SLAVE" command after the connection with the C is established.

Q - Is there a Windows CE driver available for the HCI module?

A – Bluegiga do not provide a driver for the Windows CE platform as this should be provided with the operating system. There are alternatives in the market to Windows' own stack. You may have a look for example:

http://www.mindtree.com/randdservices/research/ethermind_stack_profile.html or http://www.stonestreetone.com/Products/Bluetopia/tabid/718/Default.aspx or
http://www.sybase.com/detail?id=1040278

You may also have a look at

http://channel9.msdn.com/wiki/default.aspx/Channel9.BluetoothDevelopment
http://www.bluesoleil.com

Q - Can you confirm back if the iWrap firmware for the WT11 does it support easy pairing, can you also advise back the commands or a simple example of how to set this up?

A - Secure Simple Pairing (SSP) is not supported by iWRAP 3.0.0. We've just implemented it, but there are still a few user interface considerations we'll need to improve to make it easier to use with mobile phones etc. Expect a public beta of iWRAP 4 in about months time. The beta will have SSP, Phone Book Access Profile and Health Device Profile.

Q - Can we use the serial port to upgrade from 2.0.0 to 3.0.0-165, or is the SPI upgrade required for this major release change?

A - It is indeed possible to upgrade from 2.2.0 to 3.0.0 over the UART interface using the DFUWizard utility, part of the Bluesuite application available at http://techforum.bluegiga.com/wt11?downloads#5.0

Q - If we *can* use the serial port for the upgrade, is the upgrade likely to fail if the Uart of the BlueGiga is not directly connected to the PC doing the upgrade, but is "soft" connected via a microprocessor and another UART ? (the baud rates may not be the same and any baud changes will not be reflected through).

A - Difficult to say as we never tested the upgrade in this conditions. The baud rate is supposed to stay the same during upgrade. In addition, when setting the DFUWizard for the BCSP protocol, three baudrates should be set with the same values for iWrap to automaticly switch to HCI_BCSP mode:
DFUWizard COM port, iWrap's SET CONTROL BAUD and PSKey "446 (0x01be) PSKEY_UART_BAUDRATE"

Q - Is the general approach of INQUIRY, SDP on each item, and PAIR to the ones of interest is this the proper way to go ? (perhaps with PIN change options too).

A - This is what has to be done if the devices in range are not known.

Q - SET CONTROL CONFIG LIST is also not in my 2.0.0 manual?

A - Adding the LIST at the end of the SET CONTROL CONFIG should report a more verbose reply, however the hex value representing the bitmask is the information that we are interested in.

Q - If I choose "DTE" in the SET CONTROL MSC command, can you please tell me if DCD and RI are inputs or outputs on the PIO port ?

A - Please, see the msc directions pdf with direction of the signals and one example.

Q - If the local interface in used in MUX mode, if there is more than one connection, which connection are the MSC controls lines used with/for?

A - The SET CONTROL MSC is not working in MUX mode. You need to use "LIST" and "SET {link_id} MSC"

Q - If I ignore RTS/CTS from 'over the air', and only use the local host RTS/CTS, does Bluetooth inherently have throttling such that overflows cannot occur at either end ? (eg. USB does have inherent flow control).

A - Bluetooth implements flow control over the air independently from the one between module and host controller; on the other side the flow control between host and controller is influenced by the Bluetooth communication, for example the modules firmware will arrange for no more data to be sent to module when buffer is filled if data for some reason cannot be forwarded over the air.

Q - I have succeeded in pairing with a Bluetooth earpiece, but the only way I could find in iWRAP to achieve this is to issue an INQUIRY command, observe the results and attempt to CALL each device in turn. CALL seems to be the only way to establish a PAIRing. Is this correct?

A - It is possible to pair two devices also with the PAIR command (you need to know anyway the Bluetooth address of the remote device). The PAIR command is being documented in user guide for 3.0.0 release (see attached the chapter about this command). Let me already here recommend you to upgrade to latest firmware 3.0.0 build 165.

Q - The SET BT PAIR XX NNN command appears to need a NNN = 32 bit link_key number that I don't know anyway. It really only seems to be useful for clearing out PAIRings?

A - The link key is normally generated automatically upon pairing. The full SET BT PAIR command is useful when you want to define your own link key to be used for example between two iWrap devices, or when you want to create an entry in the database of paired devices to be used by the AUTOCALL feature (in this case link key can be fake and given a suitable PIN code a new one will be generated upon next automatic call.)

Q - Do I need to implement a "pairing" mode of operation where I attempt to CALL all devices resulting from an INQUIRY till I find one that has the (SDP) capabilities I need ? I've found the manual a bit confusing here.

A - After an inquiry you may use the SDP command to look for services in devices in range. Of course, if a remote device requires encrypted connection, the PIN code of both must match

Q - Why does SET CONTROL CONFIG not appear in "SET" command list?

A - This is normal way of operation; to display configuration you have to enter separately the SET CONTROL CONFIG LIST

Q - In Table 9 on page 131, there is a list of Commands supported in HFP-AG mode, but these commands are generally not documented in the main part of the manual. What is "STATUS" command ? I just get SYNTAX ERROR.

A - Again here I would like you to consider the 3.0.0 version (and see the attached pdf for probably better manual pages). Try to use "status service 1" (corresponding to "+ciev=1,1") and you'll get "HFP 0 STATUS "service" 1" at the HFP side

Q - With full hardware handshaking, as setup by SET CONTROL MSC, I assume the RTS and CTS fields should not be used as these are already present on dedicated UART_NRTS and UART_NCTS pins on the WT11?

A - The SET CONTROL MSC is not meant for the UART interface used for communication between module and host; it is used to link the modem status signals passed over the air to the GPIOs. Modem status signals are exposed by the LIST command and can be also set via software with the "SET {link_id} MSC"

Q - To get the audio SCO link working I need to configure the clocking and framesync. The Datasheet mentions PSKEY_PCM_CONFIG32 register to set this up. Is the only way to do this using a PC program? The BlueGiga module is embedded on our board. I can connect to the serial port indirectly via another config serial port on our device, but not directly. Will the BlueSuite PCTool in BSCP mode still cope with this, even if the baud rate differs?

A - To configure the PCM interface to work with your codec you need to consider the "435 (0x01b3) PSKEY_PCM_CONFIG32" and "438 (0x01b6) PSKEY_PCM_FORMAT" PSKeys. You need the PSTool utility to configure them, however in the newer release they can be configured from within the iWrap with the command SET CONTROL PCM.

 

WT12

Q - I wish to use the WT12 module with an external antenna on my PCB I note in the data sheet that PIN 30 is available for antenna connection when chip antenna not in use!

Can you advise if it is required that the dielectric antenna be removed from the WT12 module in order to attach an external antenna?

A – You can just remove the two matching components and add one zero Ohm resistor between the antenna signal line and the rfpin via.

Q - Do you sell the WT12 without internal antenna?

A - we can sell the WT12 without internal antenna with product name WT12-N. It requires MOQ of 5000pcs.

 

WT32


Q - Can you advise back how to tell which version of the WT32 module we have in stock the version with or without the VREG_ENA pin 1?

A - If the antenna is in the upper left corner and it's white then the module does not have VREG_ENAp pin. The attached data sheet has a picture of a module like this. In the production version, the antenna is almost in the middle of the PCB and the colour is metallic.