User s Manual. Version 1.0 PAGE 1 OF 38

User s Manual Version 1.0 PAGE 1 OF 38

1 Table of Contents 2 Overview... 6 3 Launching Project Editor... 8 4 Creating a New Project... 9 4.1 Initial Vehicle validation... 9 4.2 Project Properties Screen... 9 4.3 Populating the fields... 10 4.3.1 Upfitter Company Name... 10 4.3.2 Customer Company Name... 10 4.3.3 Project Name... 10 4.3.4 Part Number... 10 4.3.5 Programmer... 10 4.3.6 Vehicle Make... 10 4.3.7 Vehicle Model... 10 4.3.8 Vehicle Year... 11 4.3.9 Program Description... 11 4.3.10 Revision Notes... 11 5 Configuring Inputs... 11 5.1 Inputs Screen... 11 5.2 Inputs... 12 5.3 Enable Input(s)... 13 5.4 Populating the Input fields... 13 5.4.1 Input #... 13 5.4.2 Pin #... 13 5.4.3 User Description... 13 5.4.4 Input Device Type... 13 5.4.5 Switch Active... 14 6 Configuring Outputs... 14 6.1 Outputs Screen... 14 6.2 Populating the Output fields... 15 6.2.1 Enable check-box... 15 6.2.2 Driver-Type... 15 6.2.3 No. (Number)... 15 6.2.4 Pin #... 15 PAGE 2 OF 38

6.2.5 User Description... 16 7 Setting Output Conditions... 17 7.1 Output Logic Screen... 17 7.2 Creating a logic equation... 18 7.2.1 Enable check-box... 18 7.2.2 Row Number... 18 7.2.3 Description... 18 7.2.4 Ignition Status... 18 7.2.5 Equation A, B, C, D, E, F, G, and H Dialog Boxes... 19 7.2.6 Input Types... 20 7.3 AND/OR Logic... 26 7.4 Output Dialog Box... 27 7.4.1 Digital Output... 28 7.4.2 Function Output... 28 7.5 Remain Activated... 29 7.6 Seconds... 29 8 Download Screen... 30 8.1 Connection Status... 31 8.2 Legal Disclaimer... 31 8.3 Program Button... 31 8.4 Progress Bar & Status Text... 32 9 Setting the UIM back to defaulted stated... 32 10 Debug / Diagnostics Screen... 33 10.1 Status of: Digital Switch Inputs... 33 10.2 Status of: Virtual I/O... 33 10.3 Status of Digital FET Outputs HighSide & LowSide Drivers... 33 10.4 Status of: DTC s (Active, History, & Masked)... 34 11 File Menu Items... 34 11.1 Save... 34 11.2 Save As... 34 11.3 New Project... 34 11.4 Open Project... 35 11.5 Exit... 35 12 Help... 36 12.1 About... 36 PAGE 3 OF 38

12.2 View Help... 37 13 Revision History... 38 PAGE 4 OF 38

List of Figures: Figure 1 Logical-OR of enumerated CAN signal... 7 Figure 2 Analog CAN signal basic comparison... 7 Figure 3 Analog CAN signal "In-Range" comparison... 7 Figure 4 Analog CAN signal "Out-of-Range" comparison... 8 Figure 5: Screen Splash... 8 Figure 6: Menu - Configure / Project Properties... 9 Figure 7: Screen - Project Properties... 10 Figure 8: Menu - Configure / Inputs... 11 Figure 9: Screen - Inputs... 12 Figure 10: Menu - Configure / Outputs... 14 Figure 11: Screen - Outputs... 15 Figure 12: Menu - Configure / Output Logic... 17 Figure 13: Screen - Output Logic... 17 Figure 14: Screen - Configure Logic - Ignition Status... 19 Figure 15: Screen - Configure Logic Buttons for Equations A, B, C, D, E, F, G, & H... 19 Figure 16: Dialog Box Configure Logic-Term... 20 Figure 17: Dialog Box - Input Conditions - Type - Digital Input... 21 Figure 18: Dialog Box - Input Conditions - Digital Input Signals... 21 Figure 19: Dialog Box - Input Conditions - Digital - Active/Inactive... 22 Figure 20: Dialog Box - Input Conditions - Type CAN SIGNAL... 23 Figure 21: Dialog Box - Input Conditions - CAN - Signals... 23 Figure 22: Dialog Box - Input Conditions - EnumCAN Logically OR-ed... 24 Figure 23: Dialog Box - Input Conditions Analog CAN comparisons... 25 Figure 24: Screen - Configure Logic AND / OR logic selection... 26 Figure 25: Logic Table... 26 Figure 26: Screen - Configure Logic Buttons for Output Dialog Box... 27 Figure 27: Dialog Box - Configure Logic Output... 27 Figure 28: Dialog Box - Configure Logic Output - Digital Output... 28 Figure 29: Dialog Box - Configure Logic Output - Function Output... 28 Figure 30: Screen - Configure Logic Remain Activated... 29 Figure 31: Screen - Configure Logic Remain Activated - Seconds... 29 Figure 32: Menu - Download... 30 Figure 33: Screen - Download - NOT connected... 30 Figure 34: Screen - Download - Connected... 31 Figure 35: Screen - Download Legal Disclaimer... 31 Figure 36: Screen - Download Program Button... 31 Figure 37: Screen - Download - Progress Bar & Status Text... 32 Figure 38: Screen Debug / Diagnostics... 33 Figure 39: Menu - File - Save Project... 34 Figure 40: Menu - File - New Project... 34 Figure 41: Menu - File - Open Project... 35 Figure 42: Menu - File - Exit... 35 Figure 43: Menu - Help - About... 36 Figure 44: Dialog Box - About... 36 Figure 45: Menu - Help - View Help... 37 Figure 46: Help Sub-system... 37 PAGE 5 OF 38

2 Overview The Upfitter Interface Module (UIM) (or CAN Interface Module in certain markets) Project Editor is an application program used by the UIM programmer to configure the UIM s internal logic. It should be noted that any reference to UIM is interchangeable with CIM, both terms refer to the same module. The UIM Project editor requires a minimum operating environment consisting of a Microsoft Windows (Windows 7 or 8) based computer (32-bit or 64-bit microprocessor, least 1MB of RAM, at least 300MB of free hard drive space, at least one unused USB 2.0 compatible port). Until configured with application logic, an Upfitter Interface Module will not perform any logic function, or drive any outputs. The UIM application is configured into the UIM by entering the application logic into the PC based UIM Project Editor, then downloading the application logic from the PC to the UIM through a USB connection. The UIM can evaluate the states of its de-bounced input pins and pre-specified vehicle data via CAN signals during its execution of the UIM application. Based on the result of the evaluation of the UIM application logic and CAN signals, as a function of the UIM input states, the UIM can drive its High-side and Low-side outputs to their active states, or perform pre-programmed functions (activate Panic Alarm, or initiate horn chirps) This application logic is defined in terms of 24 rows of logic equations. Each logic equation can evaluate up to eight (8) logic conditions, and drive one output or pre-programmed function. The UIM executes the user defined application logic frame every 50ms. The execution of the UIM application is as follows 1) SAMPLE: At the start of an execution frame, the UIM samples all UIM input pins, CAN signal states, and uses those sampled values exclusively during that evaluation of that frame of the UIM application logic. 2) EVALUATE: The UIM logic calculation engine evaluates each row of logic. Only enabled rows will be calculated. Disabled rows, even if they contain disabled (grayed out) logic, will not be evaluated. 3) OUTPUT: By the completion of the 50mS frame, all UIM Outputs will be set to their newly calculated states, and any pre-programmed functions initiated. At the next 50ms period, the UIM will begin another Sample/Evaluate/Output sequence. This execution will continue whenever the UIM is awake. The UIM will go to sleep within 10.5 seconds of the vehicle being turned off, AND all UIM outputs driven to their inactive states, AND all pre-programmed functions completed. The UIM will wake up and execute its application logic when the vehicle is awoken, or when a change in state of one of the UIM inputs is detected. WARNING: The UIM can remain powered and operational when the vehicle is asleep if any of the UIM outputs are left in the active state, potentially depleting battery vehicle charge. It is the Upfitter s responsibility to design their UIM application logic, such that it performs to requirements. PAGE 6 OF 38

Each logic row will execute the logic (((((((Logic Term/Element A or/and Logic Term/Element B) or/and Logic Term/Element C) or/and Logic Term/Element D) or/and Logic Term/Element E) or/and Logic Term/Element F) or/and Logic Term/Element G) or/and Logic Term/Element H) and (Timer Value Enabled/Disabled) and (Ignition Status) Each logic term/element (A..H) is configurable to reference the current state of either digital inputs (switches), enumerated CAN signals, analog CAN signals, or virtual I/O, and perform the one of following comparison types ( =active, =inactive, <, <=, >=, >, In-Range, Out-of-Range), resulting in a Boolean logic output (True or False). These logical results are then combined in the logic equation (above) to provide a final logic value, which is used as a designated output (physical output, virtual I/O, or CAN function). Enumerated CAN signal (like Gear Position ) Config. Constant (like First ) = Config. Constant (like Second ) Logical OR Logic Element (A,B,C...H) = Config. Constant (like Third ) = Ignores other Config. Constants (like Neutral, Undefined, & Reverse ) Figure 1 Logical-OR of enumerated CAN signal Analog CAN signal (like Engine RPM ) Config. Constant (like 2000 ) <, <=, >=, > Logic Element (A,B,C...H) Figure 2 Analog CAN signal basic comparison Analog CAN signal (like Engine RPM ) Config. Constant (like 2500 ) <= Config. Constant (like 1200 ) Logical AND Logic Element (A,B,C...H) >= Figure 3 Analog CAN signal "In-Range" comparison PAGE 7 OF 38

Analog CAN signal (like Engine RPM ) Config. Constant (like 2500 ) > Config. Constant (like 1200 ) Logical OR Logic Element (A,B,C...H) < Figure 4 Analog CAN signal "Out-of-Range" comparison 3 Launching Project Editor When the UIM Project Editor is first launched, an initial Splash-Screen is displayed. Figure 5: Screen Splash Note that the UIM Project Editor version number will be identified on this screen. PAGE 8 OF 38

4 Creating a New Project In order to create and successfully flash a UIM program, a User must complete All the steps within the sections listed below: i. Project Properties ii. Inputs iii. Outputs iv. Outputs Logic v. Download 4.1 Initial Vehicle validation To ensure proper UIM operation, the module performs an internal validation to confirm proper vehicle support. This UIM vehicle validation is initiated by the user, by cycling the key (Off to Run). This validation must be done upon initial installation of the module, any time Connector (X) has been disconnected and reconnected, or after a UIM configuration has been downloaded from the Project Editor via USB. 4.2 Project Properties Screen Upon launching the UIM Project Editor, the typical first step is to edit the Project Properties screen. Any data entered into the fields in this screen, is purely for project documentation purposes, and in no way affects the operation of the corresponding application logic when download to the UIM module. This information is only saved in the project file, and a copy is not downloaded into the UIM module. Standard Windows editing commands such as Copy (Ctrl-C), Cut (Ctrl-X), and Paste (Ctrl-V) may be used on enabled text fields in the Project Properties screen. Figure 6: Menu - Configure / Project Properties PAGE 9 OF 38

Figure 7: Screen - Project Properties 4.3 Populating the fields Within the Project Properties Screen, the User is able to enter information into the various fields (detailed below) as they desire. 4.3.1 Upfitter Company Name User-supplied text. 4.3.2 Customer Company Name User-supplied text. 4.3.3 Project Name User-supplied text. 4.3.4 Part Number User-supplied text. 4.3.5 Programmer User-supplied text. 4.3.6 Vehicle Make Disabled drop-down menu with only Ford as an allowable option. 4.3.7 Vehicle Model User-editable drop-down menu which has the following options: { Unselected } (default) F250 F350 PAGE 10 OF 38

F450 F550 F650 F750 Transit Connect Transit Custom Transit Van Transit Mini-Bus Transit Tourneo Custom Transit Chassis Cab Econoline 4.3.8 Vehicle Year User-editable drop-down menu which programmatically provides a list of N (usually 5) number of years beginning with Y year. For example, Transit Custom will include in the drop-down menu the model years 2018 2022 in the drop-down menu with a default of 2018. 4.3.9 Program Description User-supplied text. 4.3.10 Revision Notes User-supplied text. 5 Configuring Inputs 5.1 Inputs Screen In this tab, the user can enable or disable various inputs. Figure 8: Menu - Configure / Inputs PAGE 11 OF 38

Figure 9: Screen - Inputs 5.2 Inputs There are a total of eleven (11) digital inputs available to the user. Depending on the specific switch input, individual switch inputs may be configurable as Active High (where the UIM activates an internal pull-down resistor, and the other side of the switch is connected to Power) or active low (where the UIM activates an internal pull-up resistor, and the other side of the switch is connected to Ground). For all switch inputs, the input can be configured to process the switch inputs (after de-bouncing) as a mechanical latching toggle switch, or a momentary pushbutton switch. When an input is configured for a mechanical toggle switch, the UIM samples the de-bounced switch input, and simply samples its current state when evaluating the application logic. This setting is to be used when using a switch which mechanically holds its current position, having specific open and closed positions. When an input is configured as momentary, the UIM assumes that the switch is a spring loaded, normally open momentary push button switch. When the pushbutton is pressed, the switch is electrically closed. When the pushbutton is released, the switch contacts revert back to its normally open state. The software interprets alternating switch closures as the closed and open states to the UIM application logic. The first pushbutton press (physical switch is closed) results in the internal UIM switch state to be interpreted as closed. Releasing the pushbutton (physical switch is now open) has no effect on the internal UIM switch state. Pressing the pushbutton, a second time (physical switch is closed) result in the internal UIM switch state to be changed to open. Releasing the pushbutton (physical switch is now open), again, has no effect on the internal UIM switch state. The UIM s internal momentary switch logic may be interpreted as a toggle function. PAGE 12 OF 38

Inputs 1 through 9 offer the following configurations: Mechanical-Latching (toggle-switch) or Momentary: software-toggle (push-on, push-off) Active High or Active Low Input 10 and 11 offers the following configurations: Mechanical-Latching (toggle-switch) or Momentary: software-toggle (push-on, push-off) Active Low (fixed) 5.3 Enable Input(s) Click on the check-box to enable or disable the selected digital input. When the digital input is disabled, no other user interaction is allowed. The switch may not be named or configured, and is not available for subsequent use in the Configure Logic screen. When disabled, previously configured logic will be un-editable, but will still execute within the Upfitter Interface Module. To prevent previously configured logic from executing, the Enable checkbox must be checked, and the logic deleted from the UIM project. When the digital input is enabled, the user may modify the User Description, Input Device Type and Switch Active for that particular input. 5.4 Populating the Input fields 5.4.1 Input # This is a reference to the logical output number, referenced elsewhere in the UIM design documentation. Input # is non-editable and for information/reference only. 5.4.2 Pin # The data in this field references the physical connector and pin number on the UIM, for wiring purposes. Pin # is non-editable and for information/reference only. 5.4.3 User Description User Description text field is user-editable. The Upfitter can use this field to assign meaningful names to their inputs which will then be referenced later throughout the application. Each input name defaults to the pre-set format: IN-#_conn-#_pin-#. If an input s name is edited, all references to the old name in the logic screen will automatically be updated to the new name. 5.4.4 Input Device Type Input Device Type drop-down menu is user-selectable. PAGE 13 OF 38

This setting selects how the state of the switch connected to an input pin is used within the UIM application logic. The options are: Mechanical-Latching (toggle-switch) - When a switch is configured in this mode, the UIM application logic will use the current state of the switch (open = Inactive or closed = Active ). Momentary: software-toggle (push-on, push-off) - When a switch configured in this mode, the logical state of the switch used by the UIM application logic will toggle between Active and Inactive each time the state of the switch changes from open to closed. 5.4.5 Switch Active Switch Active drop-down menu is user-selectable for digital inputs 1-9. This setting informs the UIM how the Upfitter has configured the switch connected to an input pin. The options are: Active High (signal is at battery voltage) - When a switch is configured in this mode, the switch will propagate the battery voltage to the UIM when the switch is closed. The UIM will also internally configure its input with a pull-down resistor to ground. Active Low (signal is at ground) - When a switch is configured in this mode, the switch will propagate a ground to the UIM when the switch is closed. The UIM will also internally configure its input with a pull-up resistor to battery voltage. For Inputs 10 and 11 Switch Active will be pre-configured as low and will not be editable. 6 Configuring Outputs In a new project, the High Side Driver and Low Side Driver outputs will initially be disabled. Each of the outputs will become functional once they have been enabled via the Outputs tab. 6.1 Outputs Screen This tab allows the user to define how many outputs will be applicable. Figure 10: Menu - Configure / Outputs PAGE 14 OF 38

6.2 Populating the Output fields In this section we will describe how to populate the Output fields. Thus allowing the User to then proceed with the next step i.e. Configuring the Output Logic. Figure 11: Screen - Outputs 6.2.1 Enable check-box Click on the check-box to enable or disable the selected digital output. When the digital output is disabled, no other user interaction is allowed. When the digital output is enabled, the user may modify the User Description. 6.2.2 Driver-Type Driver Type is non-editable and for information/reference only. The user must ensure that they have correctly chosen the output type (High-side or Low-side driver) for the specific circuit they are connecting to that output. 6.2.3 No. (Number) This is a reference to the logical output number, referenced elsewhere in the UIM design documentation. No. is non-editable and for information/reference only. 6.2.4 Pin # The data in this field references the physical connector and pin number on the UIM, for wiring purposes. Pin # is non-editable and for information/reference only. PAGE 15 OF 38

6.2.5 User Description User Description text field is user-editable. The Upfitter can use this field to assign meaningful names to their outputs which will then be referenced later throughout the application. Each output name defaults to the pre-set format; OUT-#_conn-#_pin-#. If an output s name is edited, all references to the old name in the logic screen will automatically be updated to the new name. PAGE 16 OF 38

7 Setting Output Conditions 7.1 Output Logic Screen The UIM Project Editor provides a screen, known as the Output Logic Screen, to allow the user to configure the logic equations which drive the output pins and/or the output CAN functions. This is the screen where most of the user-interactions take place. To navigate there: select the Configure menu, then the Output Logic selection. Figure 12: Menu - Configure / Output Logic Figure 13: Screen - Output Logic Digital inputs are sampled at the beginning of a loop. PAGE 17 OF 38

7.2 Creating a logic equation 7.2.1 Enable check-box Before the user can edit any specific row of logic, the Enable check-box must be selected. If there is data in a logic row and the Enable check-box is DISABLED, then that logic row will NOT be executed after being downloaded to the module. All relay outputs which are not explicitly controlled by an enabled line of logic will always remain INACTIVE. 7.2.2 Row Number The row number is non-editable and only for reference. 7.2.3 Description The Description text field is user-editable for naming the logic line/row. The name should be meaningful as it relates to either the relay output and/or the CAN function output for that line of logic, such as; Engage motor, Turn On Siren, or Flash Safety Light & Honk Horn. It is recommended to begin the Description with a VERB, which reflects what is going to happen WHEN the logic equation evaluates to TRUE. The logical output of any enabled logic line can be used as a logic term (A-H) for any other logic line/row. It is recommended to define your virtual logic lines/rows first, then use those common outputs as inputs to other logic equations. This can reduce effort by consolidating common logic into a virtual output rather than re-entering the same data for multiple rows of logic. The Description for all enabled logic lines appears in the drop-down list when selecting Virtual Feedback as a signal type. 7.2.4 Ignition Status The user s selection of the Ignition Status parameters is a precondition to allow the subsequent logic within the row to be satisfied (the Ignition Status field is effectively AND d with the rest of the row s logic). PAGE 18 OF 38

Figure 14: Screen - Configure Logic - Ignition Status When the user choses element Ignition Status the UIM Project Editor prompts the user to choose one of the following from a drop-down menu: Off Accessory (keyed vehicle only) Accessory or Off Start or Run Start or Run or Off Start or Run or Accessory Start or Run or Accessory or Off IGNORE Note: The option [ Start or Run is the default value showing in the drop down]. This menu item allows the user to select which ignition status conditions must be TRUE in order for the logic output for that logic row to be activated. This condition is logically AND d with the rest of the logic equation, thus, if the Ignition Status condition is FALSE, then the output will be INACTIVE (off). If the row of logic should always run, regardless of the Ignition Status, IGNORE should be selected. 7.2.5 Equation A, B, C, D, E, F, G, and H Dialog Boxes In order to configure the individual logic elements or terms for a row of logic, the user must first click on the associated edit button for that element. Figure 15: Screen - Configure Logic Buttons for Equations A, B, C, D, E, F, G, & H PAGE 19 OF 38

Figure 16: Dialog Box Configure Logic-Term The figure above shows an un-configured Configure Logic-Term dialog box, with no logic information entered. Clicking the CLEAR ALL button resets the dialog box to its initial state. To begin: select the TYPE drop-down menu, which will provide the following selections: DIGITAL INPUT CAN SIGNALS FEEDBACK: VIRTUAL OUTPUTS 7.2.6 Input Types Each logic element (A-H) within a logic row performs a comparison against a sampled data item. The actual comparison is dependent on the type of data specified by the user in the Input Type drop down. 7.2.6.1 Input Type - DIGITAL INPUT When DIGITAL INPUT type is selected in the Input Type drop down, the logic element (A-H) will compare the state of a switch input, specified by the user, against some comparison value. PAGE 20 OF 38

Figure 17: Dialog Box - Input Conditions - Type - Digital Input 7.2.6.1.1 Digital Input Signals Figure 18: Dialog Box - Input Conditions - Digital Input Signals This drop-down menu presents the User Descriptions as entered in the Inputs screen (see: section 8.4). Inputs which are disabled (Configure Inputs Screen) are greyed out and non-selectable in this drop down menu. PAGE 21 OF 38

7.2.6.1.2 ACTIVE or INACTIVE Figure 19: Dialog Box - Input Conditions - Digital - Active/Inactive For Digital Inputs (switches), the user can select either: Inactive meaning the switch is an Open state Active meaning the switch is a Closed state 7.2.6.1.3 OK Button In the above instance, the OK button will be selectable once the SIGNAL and DIGITAL STATE have been selected. If no SIGNAL TYPE has been selected, clicking OK will simply close the window i.e. same action as Cancel button. 7.2.6.1.4 Cancel Button In the above scenario (7.2.6.1.2) selecting the Cancel button would clear the current session and close the window. This means any data entered into the fields will be lost. Note: Pressing the ESC key will have the same effect as selecting Cancel. PAGE 22 OF 38

7.2.6.1.5 Clear All Button In general, within the Project Editor program, if the user selects the CLEAR ALL function, then any data that has been inputted up to that point will be lost. The data fields will then revert to default values. 7.2.6.2 Input Type CAN SIGNAL When CAN SIGNAL type is selected in the Input Type drop down, the logic element (A-H) will compare the value of a CAN signal, specified by the user, against some comparison value. Figure 20: Dialog Box - Input Conditions - Type CAN SIGNAL 7.2.6.2.1 CAN SIGNALS The CAN SIGNAL selection within a logic element (A-H) allows the user to select the CAN signal to be used within the logic comparison. Figure 21: Dialog Box - Input Conditions - CAN - Signals PAGE 23 OF 38

There are two basic types of vehicle CAN signal: enumerated and analog. Enumerated CAN signals have a specific list of pre-defined options. For example, the Ignition Status CAN Signal has the following potential data values: Off Auxiliary Run Start 7.2.6.2.1.1 Logically OR d Enumerated CAN signals Enumerated CAN signals may be simultaneously compared against multiple selections within the enumerated list. These comparisons are logically OR d together, i.e. if any one selection is True, then this logical term evaluates to True. Figure 22: Dialog Box - Input Conditions - EnumCAN Logically OR-ed In this case, the UIM will compare the sampled Ignition Status CAN signal to both values, Run and Start. If either case is True, then this logic-term returns True. PAGE 24 OF 38

7.2.6.2.1.2 Analog CAN Signals Analog CAN signals are numeric in nature and are compared to other fixed numeric values. Analog values use real numbers (1, 2, 3.1416, etc). These signals may be compared to fixed values, such as: "Vehicle Speed" < ( 5.00 km/h) "Battery Voltage" NOT BETWEEN ( 10.50 AND 13.75 volt) The Project Editor rounds the user s raw values to two decimal places. Analog CAN values may be compared using the following comparisons: < less than <= less than or equal to >= greater than or equal to > greater than In-Range if ( (value >= MIN) AND (value <= MAX) ) Out-of-Range if ( (value < MIN) OR (value > MAX) ) Analog signals may never be compared to exactly equal to or not equal to a comparison value. Figure 23: Dialog Box - Input Conditions Analog CAN comparisons PAGE 25 OF 38

After the user has entered all appropriate data, click on the OK button to return to the Configure Output Logic screen. 7.2.6.2.2 Input Type FEEDBACK: VIRTUAL OUTPUTS When FEEDBACK: VIRTUAL OUTPUTS type is selected in the Input Type drop down, the logic element (A-H) will compare the value of a VIRTUAL OUTPUT signal, predefined by the user, against some comparison value. 7.3 AND/OR Logic In between each logic element (A-H) there is a drop down function containing an AND or OR choice, which connects each of the logic elements together. This value must be specified to allow configuration of logic elements further to the right, within the logic row. If a user has configured multiple logic elements (A-H), connecting them using either AND or OR, then if at some later time the user clears any AND/OR connection back to - -, then all logic elements to the right of the - - will be disabled (grayed out). Figure 24: Screen - Configure Logic AND / OR logic selection In this example, the user s selection in the And/Or dropdown, either logically AND s or logically OR s the logical results of Equation A with Equation B. This concept applies equally to all logic elements (A-H). If you disable AND/OR after Equ A all proceeding equ will be grayed-out Equation Logical A B AND OR False False --> False False False True --> False True True False --> False True True True --> True True Figure 25: Logic Table PAGE 26 OF 38

The drop-down menu located between Equation B and Equation C, either logically AND s or logically OR s the logical results of (Equation A AND/OR Equation B) with Equation C, performing the first AND/OR operation between Equation A with Equation B PRIOR to applying that result with Equation C. This step-wise process is carried out for all remaining Logic-Terms (D-H). This conforms to the parenthetical order of operations for the overall equation: (((((((Logic Term/Element A or/and Logic Term/Element B) or/and Logic Term/Element C) or/and Logic Term/Element D) or/and Logic Term/Element E) or/and Logic Term/Element F) or/and Logic Term/Element G) or/and Logic Term/Element H) and (Timer Value Enabled/Disabled) and (Ignition Status) 7.4 Output Dialog Box In order to configure the output which is intended to be driven by the logic line, the user must first click on the associated button for that line. Figure 26: Screen - Configure Logic Buttons for Output Dialog Box Figure 27: Dialog Box - Configure Logic Output The figure above shows the Configure Logic Output(s) dialog box when there is no information entered. The user may select EITHER a Digital Output OR a Function Output, or BOTH. PAGE 27 OF 38

7.4.1 Digital Output The Digital Outputs actively drive the (FET) transistors, which in turn activate external relays, which then drives whatever electronic device (light, alarm, motor, etc.) when their associated logic line evaluates to True. Figure 28: Dialog Box - Configure Logic Output - Digital Output 7.4.2 Function Output Figure 29: Dialog Box - Configure Logic Output - Function Output The CAN Function Outputs send specific CAN signals and/or patterns of signals when their associated logic line evaluates to True. After the user has made a selection of either a Digital Output AND/OR a Function Output, click on the OK button to return to the Configure Output Logic screen. If the user has previously selected a Digital Output for a specific logic line, then its timer settings will be enabled. The user can choose to apply a timer to the output or to simply drive the output in lock-step with the evaluated row of logic. PAGE 28 OF 38

The Remain Activated drop-down menu allows the user to select one (1) of three (3) options: drive the output While Logic = True (lock-step) drive the output for a Fixed Specified Time (ignore changes while timing) drive the output for a Specified Time OR Until Logic = False (turn off if logic = OFF) 7.5 Remain Activated Figure 30: Screen - Configure Logic Remain Activated If the user has selected a Remain Activated other than While Logic = True, then the number of seconds is enabled and the user can enter an integer from 1 to 99,999. 7.6 Seconds Figure 31: Screen - Configure Logic Remain Activated - Seconds When a logic line has an associated timer, the Digital Output, AND the logical value (True/False) of the Virtual Signal will be driven in accordance with the result of the timer. For example, if logic line #1 uses a switch as an input and drives output #1 with a Fixed Specified Time of 10 seconds, and logic line #2 is the inverse (= FALSE) of logic line #1 and drives output #2, then, when switch #1 is turned on output #1 will turn on and stay on for 10 seconds, while output #2 will turn off and stay off for 10 seconds irrespective of the subsequent state the switch. PAGE 29 OF 38

8 Download Screen In order for the user to send the logic configuration to the UIM module, a download process is required via the USB connection. Important note: First, make sure the module is connected to the computer/laptop via a USB cable. Then, insure that Windows has sufficient time to register the device and load the USB device driver. Then Figure 32: Menu - Download Figure 33: Screen - Download - NOT connected PAGE 30 OF 38

8.1 Connection Status Once the UIM Project Editor recognizes a valid USB connection with the module, the Connection Status LED indication will light (green) and will show OK. Figure 34: Screen - Download - Connected 8.2 Legal Disclaimer The user will need to read, agree to, and verify the Legal Disclaimer (by clicking the check-box) as shown below. Downloading the logic configuration is suspended until the Legal Disclaimer is accepted. Figure 35: Screen - Download Legal Disclaimer 8.3 Program Button Once the user has acknowledged the Legal Disclaimer AND the system has found and connected to the USB port of the module, click on the Program Module with Current Opened File button. Figure 36: Screen - Download Program Button PAGE 31 OF 38

8.4 Progress Bar & Status Text During the download process itself, the Download Progress bar will display the relative percentage of the data to be sent from the computer to the module. A text-field will also display the step within the download process and well as the status. Figure 37: Screen - Download - Progress Bar & Status Text When complete, the status indicator will either show SUCCESS or a specific error. 9 Setting the UIM back to defaulted stated It should be noted that once a program has been downloaded to the UIM, it will remain there until the next Download session. If the User wishes to revert the module back to its factory state, then a Blank configuration file should be created and downloaded to the module. This can be done by: A. Selecting File -> New Project B. Do not input anything into the data fields i.e. keep it blank C. Click on Save Project As and enter an appropriate name for reference (this file can then be used for future purposes) D. Next proceed to the Download screen, ensure the Connection status is green and shows connected E. Flash the newly created blank.uim file by clicking on Program Module with Current Opened File. F. The module should now be in a factory state, a quick check to ensure no Outputs are enabled would also confirm, this PAGE 32 OF 38

10 Debug / Diagnostics Screen In the event that the user would like to diagnose specific hardware issues, the Project Editor provides a screen to allow the user to actively monitor the state of digital inputs, outputs, virtual outputs, and DTC s of the connected UIM. Figure 38: Screen Debug / Diagnostics 10.1 Status of: Digital Switch Inputs This section displays real-time information for each of the digital switch inputs, including: ON; OFF; input number; and name. 10.2 Status of: Virtual I/O This section displays real-time information for each of the Virtual Input/Outputs, including: ON; OFF; virtual I/O number; and name 10.3 Status of Digital FET Outputs HighSide & LowSide Drivers This section displays real-time information for each of the digital FET outputs, including: ON/OFF, output number, and name. PAGE 33 OF 38

10.4 Status of: DTC s (Active, History, & Masked) This section displays real-time information for each of the module s DTC s, based on: A = Active; H = History; M = Masked; 11 File Menu Items 11.1 Save The Project Editor has a menu item within the menu-bar with a path of File Save Project which enables/shows the save dialog box. Figure 39: Menu - File - Save Project 11.2 Save As The Project Editor has a menu item within the menu-bar with a path of File Save Project As which enables/shows the save dialog box. 11.3 New Project The Project Editor has a menu item within the menu-bar with a path of File New Project which, when selected, clears all resident data then shows the Project Properties screen. Figure 40: Menu - File - New Project PAGE 34 OF 38

11.4 Open Project The Project Editor has a menu item within the menu-bar with a path of File Open Project which opens a Load/Open dialog box pointing to the default folder. Figure 41: Menu - File - Open Project 11.5 Exit When the user modifies an existing project and attempts to exit the Project Editor application, without a subsequent save, the Project Editor prompts the user to either save changes or discard. Figure 42: Menu - File - Exit PAGE 35 OF 38

12 Help 12.1 About Figure 43: Menu - Help - About Figure 44: Dialog Box - About By clicking on the Copy to Clipboard button, the following text is copied and available to pasting into an email or other document. =================================================================================== Software_Path: C:\Ford_UIM\Project_Editor_2_12\Ford_UIM_Project_Editor_2_12.exe Software_Version: v 2.12 LabVIEW_Runtime: LabVIEW.exe Application_Version_Year: 2017 Application_Version_Number: 17.0 PAGE 36 OF 38

12.2 View Help Figure 45: Menu - Help - View Help Figure 46: Help Sub-system PAGE 37 OF 38

13 Revision History Rev. No Approved Date Affected Sections/ Pages Description 1.0 07/03/2018 All Initial document PAGE 38 OF 38