Table of Contents Introduction Ordering Information TT Series Transceiver Carrier Board TT Series Transceiver Carrier Board Objects TT Series Transceiver Carrier Board Pin Assignments Programming Dock Programming Dock Objects Remote Control Demo Board Remote Control Demo Board Objects Prototype Board...
The Master Development System provides a designer with all the tools necessary to correctly and legally incorporate the TT Series into an end product. The boards serve several important functions: •...
MDEV-DEMO-RC-A Development System Remote Control Demo Board, Type A MDEV-DEMO-RC-B Development System Remote Control Demo Board, Type B MDEV-PGDOCK Development System Programming Dock Figure 4: TT Series Transceiver Carrier Board Pin Assignments (Top View) MDEV-PROTO Development System Prototype Board CON-SOC-EVM...
Board A has the buttons on the right column and board B has them on the left column. These accept the Carrier Boards and are used to demonstrate the remote control functionality of the TT Series. They can also be used for range testing. These boards use hardware configuration, so if any changes have been made to the modules using the software then they may not operate correctly.
Using the Remote Control Demo Board Range Testing Several complex mathematical models exist for determining path loss in Snap a Carrier Board onto the socket on each Remote Control Demo many environments. These models vary as the transmitter and receiver are Board as shown in Figure 9.
Using the Prototype Board Supply for the module is connected through R17. This can be removed and replaced by another supply or used to measure the current consumption of Snap a Carrier Board onto the socket on the Prototype Board as shown in the module.
Programming Dock. The software defaults to the to the prototype board. The TT Series uses the pull-down resistor. Do Demo & EZConfiguration tab when opened (Figure 13). This window offers not populate both resistors at the same time as this results in a direct basic configuration and demonstration of the module’s functionality with the...
Page 10
The modules are shown with three identifiers as shown in Figure 14. Figure 14: The Master Development System Software Module Identifiers 1. The type of module (TT Series) 2. The module’s local address. 3. A custom name that can be given to the module. Type a name into the box and press Enter to apply it.
Page 11
7. The Set Module button adds the address and Permissions Mask to The Command Set tab (Figure 17) allows specific commands to be written the list. If a current module is selected, then the Permissions can be to the module. updated.
Page 12
6. The structure of the selected command and its response is shown connected module’s status is reflected in the software. in the main window. Please see the TT Series Transceiver Command Data Interface Reference Guide for definitions of each value.
Development Kit Demonstration Software Example This example shows how to configure two modules to work with each other. The software defaults to the Demo & EZConfiguration tab when opened (Figure 21). Figure 23: The Master Development System Software Pairing Modules Once the module is dropped into the Given Permissions window it is written to the active module’s memory.
Page 14
Changing the active module is accomplished by dragging a module from This tab shows the advanced configurations enabled by the module’s the Available list to the Active spot, as shown in Figure 25. Command Data Interface. Any changes are highlighted in red. In the example in Figure 27 the output mask has been changed to all inputs, S0 is latched, the Paired module is given full permissions, the status line direction is set by the mask and the outputs are latched by the Latch Mask.
Page 15
Figure 28: The Master Development System Software Demo and EZConfiguration Tab with Changes Figure 30: The Master Development System Software Transmitting Module The buttons have all changed to LEDs. The symbol next to each LED indicates if it is latching or momentary (Figure 29). S0 is latching, the rest are momentary.
Page 16
Full system operation is demonstrated by clicking on the Sandbox tab (Figure 32). Figure 34: The Master Development System Software Save Profile Once saved, the profile appears in the window, as shown in Figure 35. Figure 32: The Master Development System Software Sandbox These configurations can be saved as a profile for recalling or programming into other modules.
Page 20
MICROCONTROLLER AREA USB AREA POWER SUPPLY AREA RF MODULE CARRIER AREA POWER SUPPLY AREA RF MODULE CARRIER AREA 5VUSB VCCU 5VUSB VCCU TPS2552 TPS2552 LM3940IMP 3.3V LM3940IMP 3.3V Vout Vout VCCP 0 Ohm ICSPDAT ILIM ILIM ICSPCLK MCLR 100uF 100uF 0.47uF PWREN# FAULT...
USB AREA POWER SUPPLY AREA MICROCONTROLLER AREA USB AREA USB AREA POWER SUPPLY AREA Prototype Board Schematic 100mil Header 5VUSB FAULT VCCP Battery Input 0 Ohm ICSPDAT 100mil Header 5VUSB FAULT ICSPCLK Battery Input MCLR CMD_DATA_IN 5VUSB Vout ILIM 5VUSB Vout PIC16F1825-I/ST 100uF...
Page 22
POWER SUPPLY AREA PROTOTYPE AREA USB AREA POWER SUPPLY AREA 100mil Header 5VUSB FAULT Battery Input 100mil Header 5VUSB FAULT Battery Input 5VUSB Vout 5VUSB Vout ILIM ILIM 100uF 0.47uF FAULT 100uF 0.47uF FAULT TPS2553 53.6k 53.6k TPS2553 53.6k 53.6k 5VUSB 5VUSB BCD Charger...
Page 23
Products. Under no conditions will Linx Technologies be responsible for losses arising from the use or failure of the device in any application, other than the repair, replacement, or refund limited to the original product purchase price.
Need help?
Do you have a question about the TT Series and is the answer not in the manual?
Questions and answers