TOOTHPIC RF Solutions, TOOTHPIC Datasheet - Page 83

• Manufacturer Part Number: TOOTHPIC
• Description: MODULE, BLUETOOTH, DATA ACQUISITION
• Manufacturer: RF Solutions

Specifications of TOOTHPIC

• Svhc: No SVHC (15-Dec-2010)

Notes:
BMTC_Inquire: Inquiry time is a tradeoff between speed and finding all devices. Searching for other
devices using the BMTC_Inquire command will not necessarily find all available devices if the inquiry time is
too short.
Bluetooth ID: The Bluetooth ID structure unsigned char[6] contains the non-significant address part
(2 bytes, MSB first), followed by the upper address part (1 byte), followed by the lower address part (3 bytes,
MSB first). Big-endian format (i.e. MSB first) is used in a departure from the C18 standard so that the array
linearly matches the 01:23:45:67:89:AB form of Bluetooth address notation.
BMTC_Slave: In slave mode, BlueMatik becomes discoverable and it waits for a remote device to connect to
it. When a master connects, a BMTE_Connect event occurs and the ToothPIC public data pRemoteBTAddr
will contain the Bluetooth address of the master.
generated, the contents of pRemoteBTAddr will be cleared and BlueMatik the exits slave mode. To stay in
slave mode and await another connection from a remote device, it is necessary to re-enter slave mode. You
will need to use a semaphore to do this. See the Reset State
The following macros are defined to help you determine what caused the last reset. If none are true, the last
reset was a hardware reset applied to the NMCLR pin.
Semaphores section for this exact example. Don’t send any data to BlueMatik until you get confirmation that
the connection was successful using AwaitBMTConnect and ConnectSuccess.
ToothPIC also uses the term ‘slave mode’ in a different sense, where theToothPIC module is controlled by a
host processor which via a conventional TTL serial connection. The firmware solution always referred to by its
full name, ‘ToothPIC Slave’.
BMTC_Master: In master mode, BlueMatik actively attempts to connect to the remote device specified by the
remote device ID. When connection is complete, a BMTE_Connect event occurs and the ToothPIC public
data pRemoteBTAddr will contain the Bluetooth address of the remote device. Then when master or slave
disconnects, a BMTE_Disco event is generated, the contents of pRemoteBTAddr will be cleared and
BlueMatik then exits master mode. Don’t send any data to BlueMatik until you get confirmation that the
connection was successful using AwaitBMTConnect and ConnectSuccess.
BMTC_Hold, BMTC_HoldX, BMTC_Sniff, BMTC_SniffX:
saving modes, Hold and Sniff, as described in the section Power Saving. They apply only when a connection
exists. To change from the default Hold and Sniff settings, consult the BlueMatik documentation and set the
required values using the BMTC_General command.
BMTC_Signal, BMTC_LinkQ: The BMTC_Signal and BMTC_LinkQ commands give an idea of the signal
strength and quality. The return values via the BMTE_Signal and BMTE_LinkQ BlueMatik events. The
BMTE_Signal return value indicates the signal strength as follows:
Page 83
AwaitBMTOK;
ResetOrWakeEventWasPowerOn
ResetOrWakeEventWasStackOverflow
ResetOrWakeEventWasStackUnderflow
ResetOrWakeEventWasSoftwareReset
ResetOrWakeEventWasInterrtuptOrNMCLRDuringSleep
ResetOrWakeEventWasWDTReset
ResetOrWakeEventWasWDTWakeup
ResetOrWakeEventWasBrownOut
9-Apr-06
Toothpick 3.0.00007
DS380-8
© FlexiPanel Ltd
If the master disconnects, a BMTE_Disco event is
The BlueMatik module supports two power
Patents apply and/or pending
www.FlexiPanel.com