Tech Firma Making Technology Accessible

Transcription

1 Give your microcontroller a face Add a sunlight-readable display that s ready to rock. Connect with a data cable, our Bluetooth module, or plug it right in to your Arduino. Just send your sensor values serially and our graphic displays handle the rest. Complete program is available for use with our Scooterputer product. Compatible with the Arduino IDE Open source hardware and software. Modify, adapt, make it your own. Overview The compact Graphic LCD 128x64 Display uses an ATmega328P AVR chip as a dedicated graphics controller, fully compatible with the Arduino IDE for easy programming. Three silicon button pads are provided for data entry and making screen selections. Connect to a microcontroller using your choice of a 6 pin mini-din data cable, wireless Bluetooth, or headers for plugging directly into an Arduino. Power can be supplied via the data cable, the FTDI programming connector, the DC barrel jack, or directly from an Arduino when used as a shield. The GLCD library provides an API of low-level primitives for drawing graphic objects and text. Only 2 wires/pins are needed for efficient serial transfer of sensor data values and user input. Start with our sample code to create your own customized display solution. Complete, fully functional code is available for use with our Scooterputer product. Features Sunlight-readable graphic LCD display 128 x 64 pixel resolution Bright LED backlight Manual contrast control and reset button Three silicon rubber buttons (removable) Three ways to connect: data cable, as Arduino shield, or wireless Bluetooth ATmega328P AVR RISC-based MCU On-board 6 pin ICSP connector Fully compatible with the Arduino IDE FTDI USB-TTL converter connector for programming with a personal computer Power via data cable, Arduino headers, FTDI connector, or DC barrel jack Compact low-profile design Availabe in yellow/gray or blue/white LCD 1

2 Specifications Physical Dimensions - Active Display Area - Power (LCD back light off) LCD Back Light Current - (at full brightness) 3.8 w x 2.9 h x 0.8 d (96.5mm x 73.7mm 20.3mm) Note: 0.92 d (23.4mm) with optional DC power jack installed 2.62 w x 1.30 h (66.5mm x 33.2mm) 28mA typical (via data cable, FTDI connector, or Arduino header) - or - 38mA typical (+7v to +14v external VDC to on-board regulator) Yellow/Gray LCD: 330mA typical Blue/White LCD: 80mA typical Operating Temperature - -4 F to 158 F (-20 C to 70 C) LCD Type (direct sunlight readability) Processor - Yellow/Gray: STN Positive, Transflective (excellent) Blue/White: STN Negative, Transmissive (very good) Atmel ATMega328P 8-bit AVR RISC-based microcontroller ICSP 6 pin connector (bootloader installed) 2

3 Connectors Pin Connectors LCD Liquid Crystal Display; 20-pin (2x10) low profile through-board female connector ICSP In-Circuit Serial Programming; 6-pin (2x3) right-angle male header DATA CABLE 6-pin MiniDIN cable connector FTDI USB-to-Serial TTL (5v) cable; 6-pin male header WIRELESS Wireless (optional Bluetooth Module); 6-pin right-angle female socket Pin Connectors (Optional) DC PWR 7.5VDC Power Jack; 2.1mm / 5.5mm center positive ARDUINO SHIELD HEADERS Arduino Shield; 6-pin / 8-pin male headers BUTTON STANDOFF HEADERS Silicon rubber button standoffs; 5-pin female sockets 3

4 Jumpers and Solder Pads Jumper Setting Pins/Shunt Comments PWR In* Power Source External or On-Board Regulator Jumper 1-2 5V for 5v from data cable or Arduino Shield 5v (power supplied from external source). Jumper 2-3 VREG for 7.5v (min) from data cable, Arduino Shield Vin, or DC PWR Jack (power in to onboard +5v regulator). PWR Out* Power Output to Display External or On-Board Regulator Jumper 1-2 5V for 5V from data cable or Arduino Shield 5v (power supplied from external source). Jumper 2-3 VREG for 7.5v (min) from data cable, Arduino Shield Vin, or DC PWR Jack (power out from on-board +5v regulator). SJ1 DTR from Data cable or Wireless connector Normally Open Short solder pads to connect DTR line from Data cable / Wireless to the display controller s RESET. SJ2 Power to Wireless module. 3v3 or 5v Normally 3.3v from on-board regulator (Note: optional Bluetooth Module is powered by 3.3v). Cut trace between 3v3 and Center pad and short 5V and center pads to provide 5v to Wireless module. (Settings in bold denote as shipped. Refer to PCB silkscreen for locations, and schematic for operation). (*Note: PWR In and PWR Out jumpers should always mirror each other. In other words, if one has 1-2 jumpered so should the other, and if one has 2-3 jumpered so should the other). 4

5 Cable Pin-Outs Data Cable 6-pin Mini-DIN Pin Connection 1 GND (ground) 2 GND (ground) 3 VCC (+5v or +7.5v min) 4 RXD (data going TO display) 5 TXD (data coming FROM display) 6 DTR (normally not used) FTDI Cable 6-pin USB-to-Serial TTL (5v) Programming Pin Connection 1 GND (ground) 2 GND (ground) 3 VCC (+5v) 4 RXD (data going TO display) 5 TXD (data coming FROM display) 6 DTR (used for programming RESET) - or USB-to-Serial Converter Module 5

6 ICSP Cable 6-pin In-Circuit Serial Programming (Needed only for re-programming the on-board AVR processor, such as burning a new bootloader) Pin Connection 1 MISO (master input, slave output) 2 VCC (+5v) 3 SCK (serial clock) 4 MOSI (master output, slave input) 5 RESET 6 GND (ground) (Pocker AVR Programmer shown) DC PWR Cable 2-wire external power (Needed only for using external power source, when DC PWR jack is installed) Pin Connection VDC minimum, center pin 2 Ground 6

7 Setup And Programming Downloading Programs Choose one of the following two methods for connecting a USB cable to the Graphic LCD Display: 1. USB-to-Serial Converter Module (available from Tech Firma, LLC) Plug the USB-to-Serial Converter Module into the 6-pin right angle male connector labeled FTDI Cable on the GLCD controller board. Connect the converter module to a USB port on your computer using a compatible USB cable. (see for more information). 2. FTDI USB-to-Serial TTL (5v) Converter Cable Connect the FTDI programming cable to the 6-pin right angle male connector labeled FTDI Cable on the GLCD controller board, matching the wire colors with the colors silkscreened on the PCB. Plug the USB cable connector into a USB port on your computer. (see for drivers and more information) The computer provides power to the Graphic LCD Display via the USB cable, and assigns a virtual COM port upon detection. Run the Arduino IDE and open the program (sketch), then select the Arduino Pro or Pro Mini (5V, 16MHz) w/atmega328 option from the Tools > Board menu as shown below: 7

8 Using the Tools > Serial Port menu, select the virtual COM port that is assigned to the USB connection. The Arduino IDE is now ready to download programs to the Graphic LCD Display. Refer to the Arduino web site for more information on programming and Language Reference. Development Tips It is acceptable to connect an Arduino microcontroller, such as one with the Scooterputer Shield attached, to one USB port while at the same time having the Graphic LCD Display connected via another USB port. Each will have a unique virtual COM port assignment, allowing two instances of the Arduino IDE running side-by-side simultaneously. This makes it easy to develop and test both ends of the application together. As you switch between IDE instances, be sure to make the proper Board and Serial Port selections prior to downloading program updates to their respective board. For instance, if you are using an Arduino UNO microcontroller you will want to select that in the Board menu, and the assigned COM port in the Serial Port menu, for the IDE instance that has the Arduino program loaded. Likewise, you will want to make the selections described above in the instance of the IDE that has the Graphic LCD Display program loaded prior to downloading its program updates. While connected to the computer, the Graphic LCD Display may also be connected to the microcontroller, via the Scooterputer Sensor Shield, with a data cable. Optionally, the Bluetooth Module may be used at both ends for a wireless data connection. 8

9 ICSP Programming The Graphic LCD Display is provided with a bootloader from the factory. If you wish to download your own bootloader, connect an AVR programmer (such as the Pocket AVR Programmer from Sparkfun) to the 6-pin ICSP connector on the Graphic LCD Display board. Be sure the connector is plugged into the ICSP header using the correct pin orientation. Choose the programmer from the Tools > Programmer menu in the Arduino IDE then select the Burn Bootloader option. If using the Pocket AVR Programmer, choose USBtinyISP from the Tools > Programmer menu. See the Arduino web site for more information. 9

10 Software Overview First, it s important to know that the GLCD can be used for any application that requires a graphic or text display. Using the Arduino IDE (Integrated Development Environment), it is easy to write your own programs or make changes to the ones we provide to adapt it to your specific needs. The basic steps for using the GLCD are simple to understand and easy to implement: 1) Draw the display with screen objects using the provided graphics library 2) Receive sensor data serially from the microcontroller 3) Determine which screen objects need to be updated with data values that have changed 4) Update the screen objects with the new data 5) Detect button presses and perform an action such as sending the presses to the microcontroller For simple applications with one screen, Step 1 is usually performed one time and Steps 2 5 are performed quickly and continuously in a loop. As you ll see in our example program, it isn t difficult to add more screens and allow the user to switch between them. The Scooterputer_GLCDMono128x64.ino program (sketch) is provided by Tech Firma to run on the GLCD board. It executes the software display tasks needed for a fully operational Scooterputer. The program can be downloaded from our site at In this section, we will be reviewing the Scooterputer program to illustrate how to program the GLCD. But keep in mind that you can write your own programs or adapt this one to other purposes. The following sections provide a brief overview on the workings of the program: Libraries Fonts Setup( ) Loop( ) Exchanging Data Serially With A Microcontroller Drawing And Updating Screen Objects User Configuration Settings Simulation And Debugging It s best if you are at least somewhat familiar with the Arduino microcontroller and the IDE used to program it. We recommend you follow along the source code using the Arduino IDE or a text editor of your choice as you read through these sections. Further information and downloads for Arduino and the IDE can be found at 10

11 Libraries Several libraries are used for drawing the graphics, interfacing with the microcontroller, and to manage tasking. These libraries must be present in the IDE libraries folder and the header files must be included at the start of the program. See for more information. Library Description Where To Find TimedAction Manages the timed execution of certain GLCD tasks (see the Loop( ) section). techfirma.com/downloads arduino.cc/playground/code/timedaction SoftwareSerial Support for interrupt-driven serial communication, modified for use on Scooterputer.* techfirma.com/downloads (modified version for Scooterputer*) Original version provided with Arduino 1.0 IDE. GLCD Support for the Graphic LCD, modified for use on Scooterputer**. Functions for drawing primitives such as pixels, lines, circles, rectangles, and text. techfirma.com/downloads (modified version for Scooterputer**) Original version: *NOTE: The Scooterputer software installs interrupt handlers for the Speed (pin D8) and RPM (pin A1/D15) signals. These require control of the PCINT0 and PCINT1 vectors. The SoftwareSerial library used for serial communication takes control of all pin-change interrupt vectors (PCINT0 through PCINT3) by default. To avoid conflicts, we ve modified the SoftwareSerial library to not install handlers for the PCINT0 and PCINT1 vectors, leaving the PCINT2 vector controlled by SoftwareSerial. The modified library is available for download on our web site. For details on the SoftwareSerial library refer to the main Arduino site **NOTE: The GLCD library has a simple modification to the glcd_device.cpp file to uncomment the #define TRUE_WRITE line. This is necessary to ensure proper updating of the display pixels for the Scooterputer application. The modified library is available for download on our web site. Fonts The GLCD uses three fonts for displaying screen objects, which must be included at the start of the program. These fonts were generated using the GLCDFontCreator2 utility which can be downloaded from This is a very useful Java program for editing font files and for creating your own specialized fonts. 11

12 Setup( ) The Setup( ) function is called once at startup, and is normally used to initialize variables, I/O pin modes, libraries, and attached sensors and devices. The GLCD Setup( ) function begins by invoking the Init( ) function of the GLCD graphics library, then sets the button pin modes to input. Performing a digital write to these enables the internal pull-up resistors on the processor inputs. The brightness pin is configured as an output then set low which turns on the LCD backlight to full brightness. The button debounce timers are initialized with the current value of milliseconds. At this point, the opening Tech Firma Scooterputer splash screen is drawn and displayed for 3 seconds, then the main rider screen is drawn. In the DrawRiderScreen( ) function, the refresh flag is set equal to true which is checked by the UpdateDisplayTask( ) to force the drawing of all screen objects. This flag is reset in Loop( ), afterwhich UpdateDisplayTask( ) will then draw only those screen objects which have changed data values. The remainder of Setup( ) starts the serial port used for exchanging data with the connected microcontroller, initializes the timed action tasks, and initializes debugging if enabled. These are looked at in more detail in the following sections. Loop( ) The Loop( ) function is the heart of nearly all Arduino programs, and does what its name suggests it loops continuously. The most important job of the GLCD Loop( ) function is to sequentially execute all tasks to receive sensor data values (time, temperature, GPS, RPM, battery level, etc.) sent serially by the connected microcontroller, update the screen with that data, and process button presses. The SENSOR_ReceiveDataPacket( ) is invoked at the start of Loop( ). This function checks the serial port connected to the microcontroller to see if a packet of data has been received and, if so, stores the data values in their respective variables. See the next section, Exchanging Data With A Microcontroller, for more information. GCLD uses the TimedAction library to manage the periodic execution of tasks for updating screen objects. This makes processing more efficient as it allows screen objects to be updated with fresh data at varying rates and at a regular interval. The interval at which a task is executed and the function name of the task are specified at the beginning of the program where the TimedAction tasks are declared and intialized. The Check( ) methods of each TimedAction task are then called within Loop( ) to see if the respective task s time has elapsed and if so, the task is executed. Task Task Period Description UpdateDisplayTask BatteryAlertTask 2ms 500ms Evaluates all sensor data variables for a change in value and updates the associated screen objects. Flashes the Battery Monitor Display red zone when the battery level falls below the specified value. 12

13 Finally, each of the three buttons are checked at the end of Loop( ) to see if they are pressed. If so, the current button handler is invoked to perform some type of action. The handler that will be invoked is kept in curr_btnhandler, which is set based upon the screen context and location of the cursor while navigating the screen. Exchanging Data With A Microcontroller Receiving Data The microcontroller must send out a packet containing all sensor and configuration values continuously at a regular interval. The microcontroller uses a very simple protocol for transmitting the packet to the GLCD: [STX] datavalue1, datavalue2, datavalue3, [ETX] Refer to the Scooterputer Sensor Shield datasheet and the Scooterputer_Sensors.ino program as an example of how this is implemented by Scooterputer. The SENSOR_ReceiveDataPacket( ) function receives incoming data. Each data value is sent as either 2 bytes or 4 bytes depending on its data type, and the SENSOR_ReadInt( ) and SENSOR_ReadLong( ) functions assemble the incoming bytes accordingly. These are stored in variables used to represent the current value of the sensor data (i.e. valrpm, valspeed, valodo, etc.). These variables will be used asynchronously by the UpdateDisplayTask( ) function for updating the screen as covered in the section, Drawing And Updating Screen Objects. The receiver, GLCD, needs to be aware of the order and data type of each data value and the size in bytes of a packet, in order to sync up and assemble a complete data packet. Once a packet of the expected size has been received, the GLCD just needs to look for the STX character, read in and store each value using the anticipated data type, then check to ensure the last byte is an ETX character. Sending Data The GLCD sends back two different types of data to the microcontroller: certain button presses and configuration settings. Button presses are the simplest. A single ASCII character, or command code, representing an action based on the selected screen object at the time of the press, is sent immediately by the button handlers: ASCII A = the TripA meter was selected and therefore must be reset ASCII B = the TripB meter was selected and therefore must be reset ASCII R = the Ride Time display was selected and therefore must be reset ASCII L = the Backlight icon was selected to toggle the backlight ON ASCII D = the Backlight icon was selected to toggle the backlight OFF In addition to displaying sensor information, the GLCD has a screen for making Scooterputer settings. When the settings have changed and are ready to be sent down to the Scooterputer, a special character, Z, is sent from the GLCD Display. When the Scooterputer receives this character it sets an internal flag called valsynccfg to a value of SYNC which is checked at the beginning of its Loop( ) so that Scooterputer knows to go into a mode to receive the settings from the GLCD. After all the setting values 13

14 are received, valsynccfg is reset back to zero and its Loop( ) function gets back to the main job of getting and sending sensor information. Sending configuration settings to the microcontroller uses the same STX ETX protocol as described in the section, Receive Data, and is implemented by the SENSOR_SendCfgSettings( ) function. Each setting is sent out sequentially, and the microcontroller must be aware of the data type to expect for each value, and the overall size of the packet. Drawing And Updating Screen Objects There are essentially 3 screens for the Scooterputer GLCD application: Splash Screen Main Rider Screen Settings Screen The Splash screen is the simplest and is drawn in the DrawSplashScreen( ) function when called from within Setup( ). This function clears the screen by filling it with all black pixels, draws a white border just within the outer edges of the screen, then draws text to display Scooterputer and the Tech Firma name and web site. Finally, it delays for 3 seconds before returning to allow time for viewing before the main rider screen is drawn. There are several functions for drawing the various screen objects, all of which call graphic primitive routines provided by the GLCD graphics library. A few basic objects have the object s location, size and value information passed as arguments to a single draw function. Draw Function DrawTextLabel( ) DrawSeparators( ) FillChevron( ) Description Draws static text at a location using the specified color and font. Draws the horizontal and vertical lines that section off the screen areas. Draws a triangular shaped object, for example as used by the Battery Display. Most screen objects employ a data structure for specifying the object s location, size, color, and other information specific to the object. These objects typically provide a function for drawing their static representation on the screen, and possibly an update function that redraws the object with new data values. The following table lists the screen objects used for the Scooterputer application: Screen Object Numeric Display Status Display Description Draws a number representing a data value, such as for example temperature. Draws a simple text object, for example the COMM error indicator. 14

15 GPS Pulse Display Speed Display ODO Display Temperature Display Time Display Ride Time Display Trip Meter Battery Display RPM Display Heading Display Buttons Updates a flashing icon indicating ongoing GPS activity. Draws and updates the current and maximum speed values. Draws and updates the odometer value. Draws and updates the displayed temperature value. Draws and updates the displayed time-of-day value. Draws and updates the displayed ride time value. Draws and update the TripA and TripB values. Draws and updates the battery voltage value, and indicates low level. Draws and updates the RPM bargraph and text display values. Draws and updates the compass heading value. Draws areas on the screen that can be selected using the buttons. Updating Screen Objects Once the screen has been initialized by drawing the static portions, the screen objects are continuously updated with new data values coming from the Scooterputer microcontroller. This is accomplished by the UpdateDisplayTask( ) function which is a timed action routine invoked from within Loop( ) every 2ms. As explained in the section, Exchanging Data With A Microcontroller, SENSOR_ReceiveDataPacket( ) saves the current values of sensor data in variables as they are received (i.e. valrpm, valspeed, valodo, etc.). The UpdateDisplayTask( ) function uses these variables when invoking the screen object s draw and update routines to keep the screen updated with new values. For optimal performance, the data values are saved in variables that mirror the sensor value variables, and calls the draw or update function only when those values are different. Doing this ensures that the screen objects are updated only when the data has changed in value, avoiding unnecessary redundant painting of the screen. UpdateDisplayTask( ) processes configuration setting data first, which changes very infrequently, followed by processing of the sensor data which changes often during the normal mode of operation. Since data may be changing at a rapid rate and taking time to perform screen updates, calls to SENSOR_ReceiveDataPacket( ) are sprinkled throughout UpdateDisplayTask( ) to help minimize any disruptions to receiving the incoming data packets. At times it is necessary to paint the entire screen with new data, such as when it is first initialized in DrawRiderScreen( ) or when returning from the Settings screen. The refresh flag is set to TRUE to force UpdateDisplayTask( ) to draw all screen objects regardless of whether or not their data values have changed. This flag is reset to FALSE after the screen has been completely refreshed. 15

16 Screen Navigation Some screen objects can be selected by pressing the buttons. These are used to reset the TripA, TripB, Ride Time, and Max Speed displays, turn the LCD backlight ON or OFF, and for changing to the Settings screen and making setting changes. A cursor is used to highlight the currently selected object, which can be moved using the LEFT and RIGHT buttons. Once the cursor is highlighting the desired object, the SELECT button is pressed to perform an action for that object. Buttons are checked for presses in the CheckButtonSELECT( ), CheckButtonLEFT( ), and CheckButtonRIGHT( ) functions. As the cursor is moved from object to object using the LEFT and RIGHT button, a pointer to the associated button handler is written to the curr_btnhandler variable. Each selectable screen object has its own button handler to perform the action specific to that object. When the SELECT button is pressed, the button handler function stored in curr_btnhandler is invoked allowing the action to be carried out. A null button handler is also present. This is used for navigating the cursor off screen to remove the highlighting from the screen objects once navigation is no longer needed. While the Settings screen is displayed, the BtnHandlerCfg( ) function manages button presses in a similar fashion allowing configuration setting options to be selected and changed. User Configuration Settings The Tech Firma GLCD Display provides a Settings screen to configure Scooterputer. The settings are sent down to the Scooterputer to be stored and used by the program for various calculation parameters and for setting time and odometer values. User Setting Default Description GPS Installed Yes GPS Installed: No or Yes. Set to Yes if the GPS Module is installed. Dist Units US (Miles) Distance Units: US (Miles), or Metric (KMs). Sets display of MPH or KM/H for speed, and miles or kilometers for distances. Dist Sensor GPS Distance Sensor: Magnetic, or GPS. Specifies whether to use the Hall Effect magnetic sensor or the GPS for obtaining speed and distance values. Wheel Dia. 12 Wheel Diameter: 0 to 999 (inches if US, mm if Metric). Used in calculations of speed and distances when using the Hall Effect magnetic sensor. Not applicable if Dist Sensor is set to GPS. Max RPM 10,000 Maximum RPM: 10,000, or 20,000. (NOTE: Testing of RPM above 10,000 has not been completed and may produce unexpected results). Ignition PPC 2.0 Ignition Pulses Per Cycle: 0.5, 1.0, or 2.0. Used for calculating RPM. The pulses per cycle will vary between 2-stroke and 4- stroke engines. 2 ppc is typical for 4-stroke. Temperature F Temperature Units: F (Fahrenheit), or C (Celsius). Trips TripA + RideT Trip Meters: 0 = TripA + RideT, or TripA + TripB. Time Format 12 Hr Time Format: 12 Hr (1 12 am/pm), or 24 Hr (0 23) 16

17 Time MM 0 Time Minutes: 0 to 59. Used to set the clock minutes. Time HH 0 Time Hours: 0 to 23. Used to set the clock hour. ODO 100s 0 Odometer 100s: 0 to 999. Used to set odometer 100s value. ODO 1000s 0 Odometer 1000s: 0 to 99. Used to set odometer 1000s value. Set Defaults? No Reset to Defaults: No or Yes. Set to Yes to reset all settings to their default values on Exit. Debugging Some #define statements appear at the very beginning of the program to aid debugging. These are commented out by default so they don t affect normal operation, but can be enabled when needed. //#define DEBUG_BTNS //#define DEBUG_HEADING The #define DEBUG_XXX statements are typically uncommented one or two at a time as needed. These enable code in the GLCD functions for sending data out to the primary serial port, which can be reviewed using the IDE s Serial Monitor. Refer to each function to see what data is sent. The serial port is initialized in Setup( ) to operate at 9600 baud and Serial Monitor will need to be set to the same rate. Note that Setup( ) makes use of the primary COM1 serial port for debugging only if one or more of the #define DEBUG_XXX statements are uncommented. Otherwise this serial port is not used by the GLCD. More #define statements may be added as needed to aid in debugging. 17

18 Open Source Downloads available at Scooterputer Sensor Shield Sketch Arduino Libraries Eagle CAD Schematic Eagle CAD PCB Layout Component s Copyright 2012 Tech Firma, LLC. All rights reserved. Tech Firma, LLC reserves the right to make corrections, modifications, and other changes to its products, documentation and services at any time. Customers should obtain the latest relevant information before placing orders and should verify that such information is current and complete. Tech Firma, LLC makes no warranty, representation or guarantee regarding the suitability of its products for any particular purpose, nor does Tech Firma, LLC assume any liability arising out of the application or use of any product or circuit, and specifically disclaims any and all liability, including without limitation consequential or incidental damages. Tech Firma, LLC assumes no liability for applications assistance or customer product design. Customers are responsible for their products and applications using Tech Firma, LLC components. Parameters which may be provided in Tech Firma, LLC datasheets and/or specifications can and do vary in different applications and actual performance may vary over time. All operating parameters must be validated for each customer application by the customer. Tech Firma, LLC products are not designed, intended, or authorized for use as components in applications in which the failure of the Tech Firma, LLC product could create a situation where personal injury or death may occur. Should Buyer purchase or use Tech Firma, LLC products for any such unintended or unauthorized application, Buyer shall indemnify and hold Tech Firma, LLC and its officers, employees, subsidiaries, affiliates, and distributors harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of personal injury or death associated with such unintended or unauthorized use, even if such claim alleges that Tech Firma, LLC was negligent regarding the design or manufacture of the part. 18