Getting Started - Laird Technologies
Contents
1. You can also automate sending the Connection Drop command by clicking Disconnect in the terminal emulation window as per the illustration below es WNL iy CnihtLy SAT AN IASC L lf ATS DTA DCD RI Disconnect AS RIvORs a S is Wace _ Figure 17 Disconnect button in main window In either case at the connection drop initiating end the log window shows packet traffic as follows gt 70 473 292 06 00 OB FF 80 05 CMD DROP CONNECTION lt 70 000 109 06 00 OB 7F 00 80 RSP DROP CONNECTION MPSTATUS OK lt 70 000 172 06 00 86 7F 05 03 EVT_ DISCONNECT At the peer side the packet traffic will be similar to Si A7 3 401 06 00 g0 TF 05 03 BVT DISCONNECT At both ends the connection drop Is confirmed by the evr pisconnect event packet which contains the channel number most likely 05 Note that at the initiating end the response to CMD_DROP_CONNECTION is sent virtually immediately with an MPSTATUS_OK status It signifies that the module has successfully begun dropping the connection CONVERT PROTOCOL You may have purchased a BTM44x Dev kit with either AT or MP protocol set as default which is based on the part number A BTM440 or BTM442 by default operate in AT mode at 9600 baud and a BTM441 and BTM443 by default operate in MP mode at 115200 baud rate Americas 1 800 492 2320 Option 3 12 Laird Technologies Europe 44 1628 858 940 Hong Kong 852 2923 0610 www lairdtech com wireless BT2. The OK response is indication that the operation is complete and each line between at bti and the OK displays the Bluetooth address of a responding device You should see the address of the other dev kit appear in that list Given that an inquiry process has a random element to it if the other device does not appear in the list because your location is saturated with discoverable Bluetooth devices submit the same at bti lt cr gt command again to this module You should not see activity on the other UwTerminal to indicate that it responded to an inquiry from a peer Pair Devices Before pairing ensure that the trusted device databases are empty in both modules by typing in the command at btd lt cr gt in both instances of UwTerminal You should see the following Americas 1 800 492 2320 Option 3 3 Laird Technologies Europe 44 1628 858 940 Hong Kong 852 2923 0610 www lairdtech com wireless BTM44X Getting Started Application Note at tbtd OK Ensure the trusted device database is empty in both devices by entering at btt lt cr gt in both instances of UwTerminal You should see the following at tbtt OK Initiate pairing from one module to the other by entering at btw0016a4xxxxxx lt cr gt where 0016a4xxxxxx is the bluetooth address of the other module After roughly ten seconds the initiating instance of UwTerminal should display the following at btw0016a4fef005 OK PAIR O OO1L6A4FEFOOS5 At the peer end you shoul
3. Device Database Wizard If both Rolling Database and Persistent Database list boxes are empty then the databases are empty Otherwise if like the example above there are Bluetooth addresses in the list boxes then select each line and click on the appropriate Delete until both list boxes are empty and then hit the Quit button to close the Trusted Device Database Wizard dialog box Clear the log window in both instances of MpBtHost by clicking the paintbrush button Select Pair Initiate trom the dropdown box Confirm that the CMD and DATA fields update Figure 9 Americas 1 800 492 2320 Option 3 8 Laird Technologies Europe 44 1628 858 940 Hong Kong 852 2923 0610 www lairdtech com wireless BTM44X Getting Started Application Note LEN CHN CMD FLW DATA FLOW_RTS 7 lw 6 jw 5 lw 4 iw 3 iw 2 w10 7 UH BI 07 loc 10 TE tt OOLE6A4FEFOO1 31323334 00000000 00000000 00000000 00 Figure 9 CMD and DATA field updated with Pair Initiate Change the value tt to say 10 which signifies the pairing process should not take more than 16 seconds to complete and change the text O016A4FEFOO1 to the Bluetooth address of the BT module you wish to pair with All the other parameters can remain Then click Tx When the pairing process successfully completes after a few seconds at the initiating side activity appears very similar to the following gt 70 483 884 1C 00 10 7F 10 0016A4FEFO0O1 313233
4. Note To make a connection in one instance of MpBtHost select Connection Make and confirm the CMD and DATA fields are as follows LEN CHN CMD FLW DATA FLOW RTS W 7 WEWSW4 ile SM 2 M 17TUTT Ue UY iy jac foo fon 7F fas OOLGA4FEFOO1 1101 00 Figure 11 CMD and DATA updated by Connection Make The AB value is a host handle that is echoed back by the module Change 0016A4FEFOO1 to the address of the other module and 1101 is the UUID universal unique ID for SPP Click Tx and after a successful connection which takes a few seconds a new dialog box appears at both sides of the connection as follows RTS DTR Iv DCD RI Disconnect RSSI NORMAL Sniff al Connect to f Bode Send f 2 53 Send Figure 12 Data terminal This new dialog box is a helper dialog box which enables data to be sent back and forth in a terminal emulation window fashion The log activity at the connection initiating end resembles the following gt 70 428 503 OF 00 OD 7F AB 0016A4FEF001 1101 00 CMD MAKE CONNECTION lt 70 002 262 07 00 OD 7F 00 AB 05 RSP_MAKE CONNECTION MPSTATUS OK At the peer end it resembles the following lt 71 422 840 OD 00 88 7F 05 0016A4FEFOOO 1101 EVT_INCOMING_CONNECTION Launched TermEmu GUI for incoming connection At both ends the module has asserted the DCD modem status line The virtual LED goes green as follows IESEL atal LiIiQSE CTS DSR OCO RI DTR RTS tetty lw Fig igure 13 DC D asserted vir
5. the OEM transceiver at their discretion If the product is replaced it may be a new or refurbished product Americas 1 800 492 2320 Option 3 14 Laird Technologies Europe 44 1628 858 940 Hong Kong 852 2923 0610 www lairdtech com wireless
6. 3400000000000000000000000000 CMD PAIR INITIATE lt 70 007 690 OF 00 95 7F 0016A4FEF001 00 00000001 EVT SIMPLE PAIRING lt 70 000 110 0B 00 89 7F 0016A4FEFO01 00 EVT LINK KEY lt 70 000 998 05 00 10 7F 00 RSP PAIR INITIATE MPSTATUS_ OK At the receiving side activity appears very similar to the following lt 71 056 363 OF 00 95 7F 0016A4FEF000 00 00000001 EVT SIMPLE PAIRING lt 71 000 109 0B 00 89 7F 0016A4FEF000 00 EVT_LINK KEY In both cases the EVT_LINK_KEY event signifies that a successful pairing happened and in addition for the initiating side the RS_PAIR_INITIATE response message has an MPSTATUS_OK status value too To check that at both ends the pairing information has updated the non volatile trusted device database first power cycle each module and then select Trusted Device Database Wizard in both instances of MpBtHost and confirm that one address appears in the Rolling Database listbox similar to the snapshots below Trusted Device Database Wizard Trusted Device Database Wizard in Rolling Database Persistant Database Rolling Database Persistant Database 001644FEFO01 001644FEFO00 Max 12 Delete Make Serial Port Profile Data Connection Clear the log window in each instance of MpBtHost by clicking the paint brush button Americas 1 800 492 2320 Option 3 9 Laird Technologies Europe 44 1628 858 940 Hong Kong 852 2923 0610 www lairdtech com wireless BTM44X Getting Started Application
7. 628 858 940 Hong Kong 852 2923 0610 www lairdtech com wireless BTM44X Getting Started Application Note Ensure the check boxes labelled RTS and DTR are ticked and BREAK LocalEcho and LineMode are not ticked You can check that the modules are ready by ensuring that the CTS and DSR virtual LEDs are green and DCD and RI are red as shown in the snapshot shown above Subsequent sections illustrate how to Obtain Version amp Bluetooth Address Make an Inquiry Pair Devices Make a Serial Port Profile Data Connection Send Data in Both Directions Drop a Connection Obtain Version amp Bluetooth Address In both instances of UwTerminal windows type in the command ati3 lt cr gt where lt cr gt Is the enter key to get the firmware version number The results are as follows atio 1 141 215 0 OK The 1 1 1 215 0 string reflects the current firmware version The same displays in each window and may vary To obtain the Bluetooth address type in the command ati4 lt cr gt and you should result in the following atid 0016A4FEF004 OK The 0016A4FEF004 string is the current Bluetooth address of the connected module and will vary Make an Inquiry In one instance of UwTerminal window enter at bti lt cr gt where lt cr gt is the enter key to initiate an inquiry This results in the following attbti OO16A4FEFO72 0016A4FEF000 0016A4FEF073 0016A4FEF001 OK The command takes up to ten seconds to complete
8. Laird gt BTM44X Getting Started Application Note v1 0 INTRODUCTION There are four variants of the BTM44x Enhanced Data module which interface with a host via a UART and one of two logical protocols The 440 and 442 require an external antenna and the 441 and 443 have a built in antenna All variants have the same firmware image but are configured at production time to have different logical protocols and UART communication parameters by default There are two logical protocols called AT attention and MP multipoint AT is very similar to the Hayes AT protocol found in traditional modems which allows control of one Bluetooth connection at a time MP is a multipoint packet based protocol which manages multiple simultaneous connections The 442 amp 443 both startup by factory default in AT mode with communications setting of 9600 N 8 1 and the 440 amp 441 both startup by factory default in MP mode with communications setting of 115200 N 8 1 Detailed description of both protocols is provided in the BTM44x User Manual available on request The communication settings allow baud rates to be set in the range 1200 to 921600 parity to be none odd or even and either 1 or 2 stop bits In addition CTS RTS handshaking is provided and cannot be disabled The modules are surface mount modules so development kits are available to help learn and prototype with As there are 4 variants of the module there are 4 development kits However i
9. M44X Getting Started Application Note If you have the wrong protocol for your prototyping it is very easy to convert the module so that it operates the protocol of your choice The procedure is described in the next two sub sections You need two free utilities from Laird called UwTerminal and MpBtHost Convert from AT to MP mode You need a Laird utility called UwTerminal or any terminal emulation utility of your choice for example HyperTerminal which may be present in your version of Windows If you do not have UwTerminal contact Laird for a free copy Launch UwTerminal and set the communications parameters as follows COM as per your setup Baudrate 9600 Parity none Stopbits 1 Handshaking CTS RTS Leave all other values as per the defaults and then click OK Once the terminal emulator appears ensure that the LocalEcho and LineMode checkboxes are not ticked In the window type at lt cr gt where lt cr gt Is the enter key Confirm that you see activity as follows at OK Type at amp t mp lt cr gt where lt cr gt is the enter key and confirm you see activity as follows ate mp OK Finally power cycle the module It wakes in MP mode which is managed with MpBtHost a free Laird utility Convert from MP to AT mode You need a Laird utility called MpBtHost If you do not have it contact Laird for a free copy Launch MpBtHost and set the communications parameters to COM
10. Send button BS er E EE EE EE 2 Mii LOTI Laird Figure 15 Data Terminal Send button This results in traffic as follows gt 70 369 504 07 05 4C61697264 Americas 1 800 492 2320 Option 3 11 Laird Technologies Europe 44 1628 858 940 Hong Kong 852 2923 0610 www lairdtech com wireless BTM44X Getting Started Application Note Alternately enter the string Laird in the main screen change the value in CHN field to 05 as per the illustration below and then click the button labeled Tx DATA LEN CHN CMD FLW DATA lov os op ve Figure 16 Changed CHN value The log displays traffic as follows gt 70 156 437 U7 05 4C61697264 The channel number is 05 if this is the first connection after a power cycle It increments for subsequent connections and cycles in the range 01 to 07 inclusive These are channel numbers associated with SPP Drop Connection Assuming that a data connection exists using the steps shown in previous sections and confirmed by the fact that the DCD virtual LED is green you can drop the Bluetooth connection from either instance of MpBtHost It is not necessary for the side initiating the connection to drop it To drop the connection select any instance of MpBtHost and select Connection Drop In the DATA field change the value cc to 05 channel number ensure that the CHN field is OO and not 05 which you may have changed in the previous section and then click Tx
11. TR and RTS checkboxes checked Messages in red text in the log window are commands from the host to the module Messages in blue are responses to those commands trom the module Asynchronous event messages trom the module to the host are in green Messages in grey are information added by the utility and do NOT constitute any UART traffic For command packets red lines note an extra spacing after the fourth character That is to highlight the fact that the first 4 bytes of a multipoint command packet is the header with the 3rd byte corresponding to the CMD_ID as described in the user manual and all bytes after the 4th byte constitute data fields as defined for that particular command For responses blue lines note the extra spacing after the fifth byte That is to highlight the fact that the first 5 bytes is the header and the fifth byte as described in the user manual is the status byte 00 signifies MPSTATUS_OK Everything after the 5th byte constitutes data as defined for each response in the user manual Asynchronous event messages green lines consist of a 4 byte header and data as defined in the user manual The 3rd byte of the message is the EVT_ID The following subsections show how to Drop Connection Obtain Firmware Version and Bluetooth Address though the startup sequence does it automatically ake an Inquiry from one module and see the other respond Pair Devices Make a Serial Port Profile Data Connection Se
12. address and will vary For each line command response or event the first character which is either lt or gt signifies the direction of the packet A gt signifies an outbound command from host to module and a lt signifies an incoming response or event trom the module to the host After the lt or gt character is the COM port number The next field here 364 465 and 000 125 Is the time elapsed in sec milliseconds format since the last packet regardless of direction Make an Inquiry In one instance of the MpBtHost window click the paint brush icon to clear the log and then select Inquiry Req from the dropdown box The CMD and DATA textboxes are updated as follows a a Fi LEN CHN CMD FLW DATA FLOW _RTS v 7 Iv 6 v 5 v 4 v 3 iw 2 v 1 ee ealy i joa joo 08 7F 05 08 od Figure 7 CMD and DATA fields updated with Inquiry Req The Inquiry Request command has a 3 bytes data field corresponding to MaxResponses Timeout_sec and flags respectively Leave the default values as suggested and click Tx This operation takes 8 seconds to complete or if there are many Bluetooth devices nearby then as soon as 5 responses are available Communications activity in the log window appears similar to the following Bluetooth addresses will vary Americas 1 800 492 2320 Option 3 7 Laird Technologies Europe 44 1628 858 940 Hong Kong 852 2923 0610 www lairdtech com wireless BTM44X Gett
13. as per your setup Baudrate 115200 Parity none Stopbits 1 Handshaking CTS RTS Leave all other values as per the defaults and then hit the OK button In MpBtHost click the paint brush button to clear the log Click the dropdown and select SReg Write scnpt Lonhg About A Configuration Wizard f Figure 18 Paintbrush button and dropdown Confirm that you see a window similar to that in Figure 19 Americas 1 800 492 2320 Option 3 13 Laird Technologies Europe 44 1628 858 940 Hong Kong 852 2923 0610 www lairdtech com wireless BTM44X Getting Started Application Note LEN CHN CMD FLW DATA FLOW RTS 7 Vb WwW 5W 4 Figure 19 Result of SReg Write Change the two rr characters to FF and change vvvvvvvv to 00000002 and click Tx Contirm that the log window resembles the following F gt l ee ee PA A A A gt 70 023 961 09 00 04 7F FF 00000002 CMD WRITE SREG lt 70 000 141 OA 00 04 7F 00 FF 00000002 RSP WRITE SREG MPSTATUS_OK Figure 20 SReg Write log Finally power cycle the module It wakes in AT mode which can be managed using a utility called UwTerminal or any standard terminal emulation application CONCLUSION FIRMWARE UPGRADE If you find that your module does not have the latest firmware you can download the latest firmware over the UART port by requesting the new firmware from Laird The firmware is bundled with an upgrade utility The procedure
14. atus bar Figure 4 displays the Bluetooth address IF the module is powered and responding at the COM port you specified Americas 1 800 492 2320 Option 3 5 Laird Technologies Europe 44 1628 858 940 Hong Kong 852 2923 0610 www lairdtech com wireless BTM44X Getting Started Application Note BDADDR 00 16 44 FE FO 00 Figure 4 Status bar populated with current Bluetooth data If the Bluetooth address does not display you most likely will not see any red blue green lines in the main log window as follows CONN DISC CTS OSA DCO Rl OTR ARTS LEN CHH CMD FLW DATA FLOW _BTS 7 Iw EMW 5 fw 4 fw oie 2 iv DEE 8 8 Bly fy eefe feo Pe uuum RSP READ BDADDR MPSTATUS OF gt 70 000 015 05 00 17 FF 00 CMD INFORMATION a e a oo eT Pr m f aLate E i ml o L a Sal e 751i lt 70 000 078 oz 00 17 TF 00 00 8101011101070601 RSP INFORMATION MPSTATUS OF m Ws eres rea Weraol mri m 4 1 4 4 4 4 Poo Le f LiDiaa te LSLOLL x 4L L L L L LL LELA A a ON eo ee PBPlattormid CclVer AppVer Dew r F do i r De at a m e m lt 70 001 810 o8 00 61 7F 00 01 01 OC EVT STATUS ti i i 4 iri bs mW be 2s Tras hes at re Se sr bee eS Se Figure 5 UwTerminal log Only proceed if you see the information as above Note the four virtual LEDs which show the status of the modem lines on the UART In normal operating conditions CTS amp DSR should be green and DCD amp RI should be red Leave the D
15. d see the following PAIR O OO16A4FEFOO04 Notice that the module sends the OK confirmation to the at btw command almost immediately The PAIR O responses appear about ten seconds later at both ends almost simultaneously The PAIR O xxx message at one end has the 12 digit Bluetooth address of the peer trusted device Now check that the pairing information has been added to the trusted device database in both modules by entering at btt lt cr gt in both instances of UwTerminal You should see ONLY one address line in between at btt and the OK response as follows at btt 0O016A4FEF0O05 OK You can power cycle each module type in the at btt lt cr gt command and the device displays in the trusted device database given that the database is stored in non volatile memory Make a Serial Port Profile Data Connection To make a connection in one instance of UwTerminal window type in the command atd001 6a4xxxxxx lt cr gt where lt cr gt is the enter key and 0016a4xxxxxx Is the address of the module in the other devkit You should see something similar to the following atd0016a4fef005 CONNECT UULGCGAAFEFOUOUS 101 gt In the UwTerminal instance of the peer device you should see the following RING 0016A4FEF004 CONNECT 0016A4FEF004 1101 lt The Bluetooth address after the CONNECT string is the Bluetooth address of the peer device and the 1101 is a unique identifier corresponding to serial port profile SPP and is a value set by the B
16. g Started Application Note UwTerminal v3 10 Terminal Script Contig About cTs DSR pco RI RTSiv DTRiv BREAK LocalEcho LineMode Clear ClosePort LUiwFlash Bluetooth Data Module 44x COM34 115200 N 8 1 Kcr Figure 1 UwTerminal main window The MpBtHost main window is as follows H MultPoint Bluetooth Host ZT Tx Bal S Configuration Wizard vil BREAK Ver Reset Stats Close CTS OSR OCOD RI OTRAT CONN DISC LEN CHN CMD FLW DATA FLOW_RTS v 7 v 6 Iv 5 Iv 4 Iv 3 Iv 2 Iv 1 el iv ppp o CMD READ BDADDR lt 70 000 078 OB 00 02 7F 00 0016A4FEF000 RSP READ BDADDR MPSTATUS_OK 70 000 016 05 0017 FF 00 CMD INFORMATION 078 OE 00 17 7F 00 00 8101011100D70601 RSP COM70 115200 N 8 1 BDADDR 00 16 A4 FE F0 00 Figure 2 MpBtHost main window In both windows there are small LED emulation graphics labelled CTS RTS DCD RI RTS which reflect the actual state of the modem control lines as asserted by the module QUICK START AT MODE By factory default the BTM440 or BTM442 are shipped in AT mode and the BTM441 or BTM443 are shipped in MP mode See Convert Protocol for instructions on converting your modules to AT mode Assuming that both dev kits are plugged into the PC start UwTerminal twice For each specify the COMxx as per your installation and communications parameters as 9600 N 8 1 with handshaking set to CTS RTS Americas 1 800 492 2320 Option 3 2 Laird Technologies Europe 44 1
17. ing Started Application Note iQ 299 999 07 VO 06 7F 0S 08 00 CMD INQUIRY REQ lt 70 000 140 OD 00 84 7F 0016A4FEF001 001F00 EVT INQUIRY RESULT lt 70 000 359 OD 00 84 7F OO16A4FEFO76 001F00 EVT INQUIRY RESULT lt 70 000 031 OD 00 84 7F 0016A4FEFO72 001F00 EVT INQUIRY RESULT lt 70 000 187 OD 00 84 7F 0016A4FEFO73 001F00 EVT INQUIRY RESULT lt 70 000 109 OD 00 84 7F 0016A4FEF077 001F00 EVT INQUIRY RESULT lt 70 000 000 07 UU 08 JF UU O05 QO RSP INQUIRY REQ MPSTATUS OK In each green event packet the 6 bytes after the double spacing e g 0O016A4FEFO72 is the Bluetooth address Check that you see a line corresponding to the other modules If not try the inquiry again Since inquiry has a random element to it you will eventually be able to pick up a response You can increase the probability of getting a response from your other module by increasing the MaxResponses and Timeout_sec data bytes of the command The final blue line signifies that the inquiry procedure is complete and the module is ready for another command You should not see any activity on the other MpBtHost utility to indicate that it had responded to an inquiry trom a peer device Pair Devices Before pairing ensure that the trusted device databases are empty in both modules by selecting Trusted Device Database Wizard in both instances of MpBtHost which results in a dialog box Figure 8 Rolling Database O01 6A4FEFOO5 Figure 8 Trusted
18. ironmental requirements such as military medical life support or life sustaining equipment are specifically not recommended without additional testing for such application Limited Warranty Disclaimer Limitation of Liability For a period of one 1 year from the date of purchase by the OEM customer Laird Technologies warrants the OEM transceiver against defects in materials and workmanship Laird Technologies will not honor this warranty and this warranty will be automatically void if there has been any 1 tampering signs of tampering 2 repair or attempt to repair by anyone other than an Laird Technologies authorized technician This warranty does not cover and Laird Technologies will not be liable for any damage or failure caused by misuse abuse acts of God accidents electrical irregularity or other causes beyond Laird Technologies control or claim by other than the original purchaser In no event shall Laird Technologies be responsible or liable for any damages arising From the use of product From the loss of use revenue or profit of the product or As a result of any event circumstance action or abuse beyond the control of Laird Technologies whether such damages be direct indirect consequential special or otherwise and whether such damages are incurred by the person to whom this warranty extends or third party If after inspection Laird Technologies determines that there is a defect Laird Technologies will repair or replace
19. is described in a separate application note called BTM44x AppNote Firmware upgrade REVISION HISTORY 1 0 10 June 2013 Initial Release Jonathan Kaye Copyright 2013 Laid Technologies Inc All rights reserved The information contained in this manual and the accompanying software programs are copyrighted and all rights are reserved by Laird Technologies Inc Laird Technologies Inc reserves the right to make periodic modifications of this product without obligation to notify any person or entity of such revision Copying duplicating selling or otherwise distributing any part of this product or accompanying documentation software without the prior consent of an authorized representative of Laird Technologies Inc is strictly prohibited All brands and product names in this publication are registered trademarks or trademarks of their respective holders Information furnished by Laird Technologies in this specification is believed to be accurate Devices sold by Laird Technologies are covered by the warranty and patent indemnification provisions appearing in its Terms of Sale only Laird Technologies makes no warranty express statutory and implied or by description regarding the information set forth herein Laird Technologies reserves the right to change specifications at any time and without notice Laird Technologies products are intended for use in normal commercial and industrial applications Applications requiring unusual env
20. luetooth SIG At this stage you should see that in both instances of UwTerminals there should now be three green virtual LEDs which show that the module has asserted the DCD modem status line to signify that at least one Bluetooth connection exists in that module Send Data in Both Directions Assuming that a data connection exists using the steps shown in the previous section and confirmed by the fact that the DCD virtual LED is green you should be able to type a message in one instance of UwTerminal Americas 1 800 492 2320 Option 3 4 Laird Technologies Europe 44 1628 858 940 Hong Kong 852 2923 0610 www lairdtech com wireless BTM44X Getting Started Application Note and see it being echoed in the other instance Likewise type in a message in the other UwTerminal instance and confirm that the message gets displayed in the other instance Drop a Connection Assuming that a data connection exists using the steps shown in previous sections and confirmed by the fact that the DCD virtual LED is green you can drop the Bluetooth connection from either instance of UwtTerminal It is not necessary for the side initiating the connection to drop it To drop the connection select any instance of UwTerminal and type the three character ensuring that there is at least half a second delay between each character As you type each character it echoes at the other instance of UwTerminal After typing in the third character at the U
21. nd Data in Both Directions Drop Connection Americas 1 800 492 2320 Option 3 6 Laird Technologies Europe 44 1628 858 940 Hong Kong 852 2923 0610 www lairdtech com wireless BTM44X Getting Started Application Note Obtain Firmware Version and Bluetooth Address In both instances of MpBtHost windows click the paintbrush icon to clear the log window then click on the dropdown box Figure 6 and select Information and then click on the button labeled Tx script Lonhg About g Configuration Wizard zir Figure 6 Paintbrush clear log and dropdown box You should see the following activity in the log window YU 95 211 05 00 17 FF OD CMD INFORMATION lt 70 000 125 OF 00 17 7F 00 O00 8101011100D70601 RSP INFORMATION MPSTATUS_ OK Module Firmware Version 1 1 1 1 1 215 0 PlatformId CclVer AppVer Dev perlId BranchId Build Twig The final part of the blue line 8101011100D70601 is the firmware version and will vary The format of the version information is described in the user s manual and is also interpreted and displayed in grey font above Clear the log window by clicking the paintbrush button then click on the dropdown box and select Read BD_ADDR Finally click Tx and should see the following activity gt 70 364 465 04 00 02 7F CMD READ BDADDR lt 70 000 125 0B 00 02 7F 00 0016A4FEFO0O RSP READ BDADDR MPSTATUS_ OR The field 0016A4FEFOOO is the 6 byte unique Bluetooth
22. t should be noted that from a hardware perspective the 440 amp 442 dev kits are exactly the same and likewise for the 441 amp 442 devkits Only the default settings are different This application note assumes you have access to two BTM44x development kits and the rest of this document describes how to quickly get started for AT and MP modes If you have kits which are by default set to a different protocol mode than you want to try see Convert Protoco which describes how to convert a module to the alternate protocol mode and then resume to the relevant quick start section PREPARATION Plug both development kits into tree USB ports on your Windows PC XP or later and allow the USB to Virtual comport drivers to be installed The dev kits use an FTDI chip and if your PC cannot locate the drivers you can download them from http Awww ftdichip com FTDrivers htm After successful install you should see two new comports under Ports COM amp LPT in Device Manager Note the COMxx numbers allocated for the two boards Contact Laird to obtain two PC utilities One is a custom developed terminal emulator called Uwterminal and the other is a custom developed application to drive the module in MP mode called MpBtHost The main window for UwTerminal is shown in Figure 1 Americas 1 800 492 2320 Option 3 1 Laird Technologies Europe 44 1628 858 940 Hong Kong 852 2923 0610 www lairdtech com wireless BTM44X Gettin
23. tual LED green WSC Americas 1 800 492 2320 Option 3 10 Laird Technologies Europe 44 1628 858 940 Hong Kong 852 2923 0610 www lairdtech com wireless BTM44X Getting Started Application Note Send Data in Both Directions Assuming that a data connection exists using the steps shown in the previous section and confirmed by the green DCD virtual LED at both ends you should be able to type a message in one instance of the terminal emulation window and see the data appear at the other end For example type hello as shown w ATS DIR DCD RI Disconnect BASSI NORMAL Sniff Connect to 52598 Send 253 Send hello Figure 14 Data terminal Confirm that hello appears in the other modules window In addition at the module where you typed hello the log window shows packets as follows gt 70 421 109 03 05 68 PID UN0 z205 05 VS 63 gt 70 000 265 03 05 6C Pro DUG LL Ds Uo pC gt 10 00U 187 US 0S GF At the receiving end traffic appears as follows lt 71 421 234 03 05 62 71 UUl US Ya oa lt 71 U00 296 03 05 6C ji UU0 078 Us a BC S71 QUU Z05 US OS oF In either case the COM port number will be as per your settings In each case you should see five data packets each consisting of 3 bytes where the payload is 1 bytes corresponding to the 5 ASCII characters in the string hello To send multiple data bytes per data packet enter the string as per the illustration below and then click the
24. wTerminal instance where you typed in that character the module confirms and responds with OK At this stage the DCD virtual LED turn green to signify that the data connection Is still up Type in the command ath lt cr gt At both ends the terminal displays NO CARRIER Confirm that at both ends the DCD virtual LED is no longer green but has reverted to red to signify that a data connection no longer exists QUICK START MP MODE The BTM441 or BTM443 are programmed by factory default in multipoint mode If your modules are not BTM441 or BTM443 but instead are BTM440 or BTM442 so are in AT mode then refer to a later section called Convert Protocol for instructions to convert your modules to MP mode Assuming that both dev kits are plugged into the PC start the utility MpBtHost exe twice and for each specify the COMxx as per your installation and communications parameters as 115200 N 8 1 with handshaking set to CTS RTS A small dialog box appears as shown below Reset Module Wizard Hit Quit to abort RESET within the next 4 seconds Ca Figure 3 Reset module wizard dialog Either wait for around 10 seconds for the dialog box to timeout and then proceed normally or click on the Go button to bypass that timer The utility sends a few MP commands to identify the module and its Bluetooth address so that appropriate sections of the main window can display that information Specifically the bottom right of the st
Download Pdf Manuals
Related Search