tmib2 user manual - smartmicro€¦ · 6hw xs 8055 vhqvru ,'v 8055 ) rqo\

$: TMIB2 User Manual - Smartmicro€¦ · 6hw xs 8055 vhqvru ,'v 8055 ) rqo\$
PROPRIETARY The information contained in this document may be subject to change without notice. The information contained in this document shall remain the sole exclusive property of s.m.s smart microwave sensors GmbH. TMIB2 User Manual.docx I Page 1 of 143 I April 11, 2018

Project Documentation | TMIB2 User Manual Project Title: Traffic Management Interface Board V2 Date: April 11, 2018 This manual is valid as of Version: FW_TMIB2_802 and later Status: Ready

Review done Approved Delivered Outdated/invalid


1.1 Contents

1.1 Contents .............................................................................................................. 2 2 List of figures ............................................................................................................. 5 3 List of tables .............................................................................................................. 8 4 Document Control ...................................................................................................... 9

4.1 Document History ................................................................................................ 9 4.2 Abbreviations ....................................................................................................... 9 4.3 Reference Documents .......................................................................................... 9

5 Overview ................................................................................................................. 10 5.1 TMIB2 Functionality ........................................................................................... 12 5.2 Connection Scheme ............................................................................................ 13 5.3 Connectors and Visual Elements.......................................................................... 15 5.4 Reset Button ...................................................................................................... 16

5.4.1 Factory Defaults Button ................................................................................ 16 5.5 Sensor Power Supply .......................................................................................... 17

5.5.1 Power supply select switch ........................................................................... 18 5.5.2 Sensor supply override ................................................................................. 18 5.5.3 Status LEDs ................................................................................................. 19

5.6 NEMA TS2 over SDLC: Behavior of TMIB2 in NEMA Cabinets ............................... 21 5.6.1 Physical Behavior ......................................................................................... 21 5.6.2 SDLC Frame ................................................................................................ 22 5.6.3 SDLC Request and Response ........................................................................ 22

6 Installation .............................................................................................................. 24 6.1 TMIB_AB V2 main assembly ............................................................................... 24

6.1.1 Connect TMIB_C V2 expansion modules ........................................................ 24 6.1.2 Putting the TMIB_AB V2 to operation ............................................................ 24

6.2 TMIB_C V2 Expansion cards ............................................................................... 25 6.2.1 TMIB_C V2 Configuration ............................................................................. 26 6.2.2 TMIB_C V2 Hardware installation .................................................................. 26

7 TMIB2 Configuration using TMConfigurator ................................................................ 27 7.1 Tools needed ..................................................................................................... 27 7.2 Easy Mode, Super Easy Mode and TMConfigurator Expert Mode ............................ 27 7.3 (Super) Easy Mode setup .................................................................................... 28

7.3.1 Setting up TS1 or TS2 functionality ............................................................... 32 7.4 Easy Mode: Modify TMIB2 settings ...................................................................... 35

7.4.1 Change the TMIB2 trigger / call assignments ................................................. 36 7.4.2 Change IP Address using Easy Mode ............................................................. 37 7.4.3 Synchronize Time using Easy Mode ............................................................... 38 7.4.4 Data Recorder ............................................................................................. 39

7.5 TMConfigurator: Configurations in Expert Mode ................................................... 40 7.5.1 Monitoring ................................................................................................... 40 7.5.2 Set up Basic Parameters – DEVICE MAPPINGS. .............................................. 41 7.5.3 IP Settings ................................................................................................... 52


7.5.4 Activate TS1 Outputs ................................................................................... 53 7.5.5 Activate TS2 SDLC / Detector BIUs ............................................................... 53 7.5.6 Number of UMRR sensors / Baud rates. ......................................................... 54 7.5.7 Finalize the set-up ....................................................................................... 55 7.5.8 Configure UMRR Sensors through TMIB2 ....................................................... 56 7.5.9 Setup the UMRR sensor network ................................................................... 56 7.5.10 Set up background image ............................................................................. 57 7.5.11 Set up UMRR sensor IDs (UMRR-0F only) ...................................................... 58 7.5.12 Set up UMRR sensor alignment and triggers .................................................. 60 7.5.13 Synchronize Date and Time .......................................................................... 61 7.5.14 Configure TS1 Loop Detector outputs ............................................................ 62 7.5.15 Status message configuration ....................................................................... 65 7.5.16 Test the Assignments ................................................................................... 65 7.5.17 Configure TS2 SDLC ..................................................................................... 66 7.5.18 Status message configuration ....................................................................... 69 7.5.19 Test the Assignments ................................................................................... 70 7.5.20 Commands .................................................................................................. 71

8 Advanced Usage of TMConfigurator Expert Mode ....................................................... 72 8.1 Advanced Commands in TMIB configuration ........................................................ 72 8.2 TMIB ID Change ................................................................................................ 73 8.3 Example of multiple TMIB2 use ........................................................................... 74

8.3.1 Principle Network Layout – TMIB2 Client Mode .............................................. 74 9 The WEB-GUI .......................................................................................................... 75

9.1 Access the WEB-GUI .......................................................................................... 75 9.2 Boot status and Version information .................................................................... 75 9.3 Navigation: Use the WEB-GUI ............................................................................. 77

9.3.1 General information ..................................................................................... 78 9.3.2 Default values and user settings ................................................................... 80

9.4 RS485 (EIA 485) Settings ................................................................................... 80 9.4.1 RS485 - Speed ............................................................................................. 80

9.5 Setup Ethernet addresses ................................................................................... 81 9.5.1 The Default Gateway of the system .............................................................. 81 9.5.2 IP-Address of the WEB-GUI Webserver ......................................................... 81 9.5.3 IP-Address and behavior of the TMConfigurator communication ...................... 82 9.5.4 IP-Address and behavior of the sensor network ............................................. 83

9.6 Setup CAN bus ................................................................................................... 84 9.7 System control ................................................................................................... 85

9.7.1 System settings ........................................................................................... 85 9.7.2 System control and monitoring tools ............................................................. 86 9.7.3 Ethernet service tools ................................................................................... 87 9.7.4 Set time and date ........................................................................................ 91 9.7.5 The TMIB2 config manager .......................................................................... 92 9.7.6 “DOWNLOAD” a restore point ....................................................................... 97 9.7.7 Factory reset ............................................................................................... 99 9.7.8 Reboot the TMIB2 ...................................................................................... 100


9.8 Debugging: The logfile mechanism of the TMIB2 ............................................... 101 9.8.1 Actions ...................................................................................................... 102 9.8.2 Download the Logfile ................................................................................. 103 9.8.3 Clean the log ............................................................................................. 103

9.9 Updating the TMIB2 via WEB-GUI ..................................................................... 104 9.10 Sensor Mapping ............................................................................................... 104

9.10.1 Sensor Connection Window ........................................................................ 105 9.10.2 Sensor Detail Box ....................................................................................... 106 9.10.3 TMIB2 Details Box...................................................................................... 108 9.10.4 Troubleshooting with the Sensor Mapping Window ...................................... 108

10 Firmware and Updating ....................................................................................... 112 10.1 Content and description of the TMIB Update Image (TUI) .................................. 112 10.2 Where to get such a TMIB2 Update Image? ....................................................... 112 10.3 Versioning ....................................................................................................... 112 10.4 Firmware components ...................................................................................... 113

10.4.1 The SDLC Subsystem ................................................................................. 113 10.4.2 The Main Application System ...................................................................... 113

10.5 STEP by STEP: How to update the TMIB2 .......................................................... 114 10.5.1 Purchase a firmware image ........................................................................ 114 10.5.2 How to check integrity of a firmware image ................................................. 114 10.5.3 Upload and automatic Firmware installation ................................................. 115

10.6 Boot management............................................................................................ 116 10.6.1 From which partition did the TMIB2 boot? ................................................... 117

10.7 Show TMIB2 firmware ID in TMConfigurator ...................................................... 118 10.7.1 Firmware Update using TMConfigurator ....................................................... 119

11 Remote connections to the TMIB2 through the WWW ........................................... 120 11.1 Infrastructure for safety TMIB2 remote installations ........................................... 120

12 Shelf mount version ............................................................................................ 121 13 Connections ........................................................................................................ 124

13.1 External power supply connector ...................................................................... 125 13.2 RS485 / CAN Sensor connector ......................................................................... 126 13.3 TMIB_AB Ethernet connector ............................................................................ 129 13.4 Layout cable TMIB_AB – TMIB_C ...................................................................... 131 13.5 Backplane Connector of TMIB_AB V2 ................................................................ 132 13.6 Backplane connector of the TMIB_C V2 expansion board .................................... 134 13.7 SDLC port (NEMA TS2 Port 1 connector) ........................................................... 135 13.8 USB Host ......................................................................................................... 136

14 Important Legal Disclaimer Notice ........................................................................ 137 15 MIT license of Yocto basis system ........................................................................ 138 16 GNU LGPL License V3 .......................................................................................... 139 17 Contact .............................................................................................................. 143


2 List of figures

Figure 1: TMIB_AB V2 assembly ...................................................................................... 10 Figure 2: TMIB_C V2 assembly ........................................................................................ 11 Figure 3: TMIB_AB V2 fully connected ............................................................................. 12 Figure 4: TMIB_AB V2 connections .................................................................................. 14 Figure 5: TMIB_AB V2 front panel elements ..................................................................... 15 Figure 6: TMIB_AB V2 rear panel elements ...................................................................... 16 Figure 7: TMIB power supply switch location ................................................................... 17 Figure 8: Power supply select switch ............................................................................... 18 Figure 9: Sensor Supply Override .................................................................................... 18 Figure 10: LED status field .............................................................................................. 19 Figure 11: SDLC Clock and Data ..................................................................................... 21 Figure 12: SDLC physical parameters (EIA-485 // TMIB2) ................................................. 21 Figure 13: SDLC Framing ................................................................................................ 22 Figure 14: TMIB_C V2 extension card for TS1 .................................................................. 25 Figure 15: Signal flow scheme TMIB-C V2 ........................................................................ 26 Figure 16: Easy Mode mode selection .............................................................................. 28 Figure 17: File name of .TISF setup file ........................................................................... 29 Figure 18: Easy Mode Basic settings ................................................................................ 29 Figure 19: Easy Mode Check list ...................................................................................... 30 Figure 20: Easy Mode communication test ....................................................................... 31 Figure 21: Easy Mode TS1/TS2 configuration ................................................................... 32 Figure 22: Easy Mode save settings ................................................................................. 33 Figure 23: Easy mode send data info ............................................................................... 34 Figure 24: Easy Mode success info .................................................................................. 34 Figure 25: Choose "Tool Wizard" ..................................................................................... 35 Figure 26: Easy Mode Tool Wizard .................................................................................. 36 Figure 27: Change ETH settings using Wizard .................................................................. 37 Figure 28: Start the Tool Wizard ..................................................................................... 38 Figure 29: Sync RTC in the wizard ................................................................................... 38 Figure 30: Use simple data recorder of Wizard ................................................................. 39 Figure 31: Start monitoring TMIB2 action ........................................................................ 40 Figure 32: TMC hardware monitor ................................................................................... 41 Figure 33: Ethernet settings for TMIB2 ............................................................................ 42 Figure 34: Open Device Mappings ................................................................................... 43 Figure 35: Open TMConfigurator window ......................................................................... 46 Figure 36: TMConfigurator window .................................................................................. 46 Figure 37: Sensor Network ............................................................................................. 47 Figure 38: Configure SensorNetwork ............................................................................... 48 Figure 39: TMIB window ................................................................................................. 49 Figure 40: Sensor Mapping ............................................................................................. 49 Figure 36: TMIB generation selector ................................................................................ 50 Figure 42: TMIB property editor ...................................................................................... 51


Figure 43: TMIB IP settings ............................................................................................ 52 Figure 39: TMIB control settings ..................................................................................... 52 Figure 40: TMIB activation .............................................................................................. 53 Figure 41: TMIB invert GPIO output ................................................................................ 53 Figure 42: TMIB TS2 (SDLC) activation ............................................................................ 53 Figure 43: Detector BIU activation ................................................................................... 53 Figure 44: Select number of connected UMRR .................................................................. 54 Figure 45: UMRR sensor com parameters ........................................................................ 54 Figure 46: Save settings ................................................................................................. 55 Figure 52: Established TMIB2 connection ......................................................................... 56 Figure 53: Setup UMRR sensor network ........................................................................... 56 Figure 54: Get background image from the web ............................................................... 57 Figure 55: TMIB and sensor ID0 connected ..................................................................... 58 Figure 56: Configure sensor network ............................................................................... 59 Figure 57: Connection established to TMIB2 with two sensors ........................................... 60 Figure 58: Synchronize date and time .............................................................................. 61 Figure 59: Configure TS1 loop detector outputs ............................................................... 62 Figure 55: Relate a trigger to output ............................................................................... 63 Figure 56: Enable assigned TSI outputs ........................................................................... 64 Figure 57: Enable "send everything" feature .................................................................... 65 Figure 63: Example of actuated TS1 output ..................................................................... 66 Figure 64: Configure TS2 loops ....................................................................................... 67 Figure 65: UMRR trigger assignment to TS2 loop ............................................................. 68 Figure 66: Enable assignment TS2 - SDLC loop ................................................................ 69 Figure 57: Enable "send everything" feature .................................................................... 69 Figure 68: Example of actuated TS2 loop ......................................................................... 70 Figure 69: TMC - TMIB direct commands ......................................................................... 71 Figure 70: Advanced command dialog ............................................................................. 72 Figure 71: Advanced commands dialog ............................................................................ 73 Figure 70: TMIB2 Client Mode ......................................................................................... 74 Figure 72: WEB GUI menu .............................................................................................. 77 Figure 74: WEB GUI: example of guided error handling .................................................... 78 Figure 75: WEB GUI: example safety information ............................................................. 79 Figure 76: WEB GUI: Interactive buttons ......................................................................... 80 Figure 77: WEB GUI: RS485 settings ............................................................................... 80 Figure 78: WEB GUI: IP setting of TMIB web server ......................................................... 81 Figure 79: WEB GUI: Ethernet setup TMConfigurator communication ................................ 82 Figure 80: WEB GUI: Ethernet setup sensor network ........................................................ 83 Figure 80: WEB GUI: CAN settings ................................................................................. 84 Figure 82: WEB GUI: System settings ............................................................................. 85 Figure 83: WEB GUI: System control and monitoring tools ................................................ 86 Figure 84: WEB GUI: system performance monitor ........................................................... 86 Figure 85: WEB GUI: Useful Ethernet utilities ................................................................... 87 Figure 86: WEB GUI: Ethernet restart information ............................................................ 88 Figure 87: WEB GUI: Ethernet configuration reset ............................................................ 89


Figure 88: WEB GUI: IP routing table .............................................................................. 90 Figure 89: WEB GUI: Time and date setup site ................................................................ 91 Figure 90: WEB GUI: configuration management (empty) ................................................. 92 Figure 91: WEB GUI: config manager - how to use info fields ........................................... 94 Figure 92: Content of config file container ....................................................................... 95 Figure 93: WEB GUI: Config manager- finish rescue point generation ................................ 96 Figure 94: WEB GUI: Config manager - overwrite dialog ................................................... 96 Figure 95: WEB GUI: Config manager - reboot to use new config ...................................... 97 Figure 96: WEB GUI: config manager - upload dialog ....................................................... 98 Figure 97: WEB GUI: Factory reset main dialog ................................................................ 99 Figure 98: WEB GUI – factory default reset confirmation .................................................. 99 Figure 99: WEB GUI - confirmation of reset ................................................................... 100 Figure 100: WEB GUI - Logfile download dialog ............................................................. 102 Figure 101: Sensor Mapping Overview ........................................................................... 104 Figure 102: Sensor Connections Window ....................................................................... 105 Figure 103: Sensor Detail Box ....................................................................................... 106 Figure 104: TMIB2 Details Box ...................................................................................... 108 Figure 105: Get knowledge of boot processes ................................................................ 108 Figure 106: Over current CUT OFF ................................................................................ 109 Figure 107: Not connected sensors................................................................................ 109 Figure 108: Current Monitoring of each sensor (port) ..................................................... 110 Figure 109: Current monitoring of the whole device ....................................................... 111 Figure 110: WEB GUI - firmware ID............................................................................... 112 Figure 110: WEB GUI - step into the boot manager ........................................................ 116 Figure 112: WEB GUI - boot manager dialog .................................................................. 116 Figure 113: Examine which partition booted .................................................................. 117 Figure 114: open status view ........................................................................................ 118 Figure 115: Read firmware ID ....................................................................................... 118 Figure 115: WWW gateway solution .............................................................................. 120 Figure 117: TMIB2 shelf mounted ................................................................................. 121 Figure 118: Access Open Collector Outputs 1..16 ........................................................... 122 Figure 119: Connectors on the front side ....................................................................... 124 Figure 120: External power connector ........................................................................... 125 Figure 121: Pinout of sensor CAN/RS485/POWER connector (x4) .................................... 126 Figure 122: Ethernet pinning ......................................................................................... 129 Figure 123: TMIB_AB expansion port 1..4 connection to TMIB_C .................................... 131 Figure 124: Pinout TMIB_AB V2 rear connector .............................................................. 132 Figure 125: Rear connection of TMIB_C V2 .................................................................... 134 Figure 126: Port 1 SDLC connector ............................................................................... 135 Figure 127: USB connector ........................................................................................... 136


3 List of tables

Table 1: TMIB2 status LED field description ..................................................................... 19 Table 2: TS2 Display Page .............................................................................................. 20 Table 3: DET BIU Addresses ........................................................................................... 22 Table 4: SDLC Request/Response Matrix.......................................................................... 23 Table 5: Pinout sensor connectors RJ45 ......................................................................... 126 Table 6: Pinning of the expansion ports ......................................................................... 131


4 Document Control

4.1 Document History

Date Author Action 2016-12-05 Reppenhagen Initial version 2017-03-07 Waldmann Review 2017-05-12 Reppenhagen Added “sensor mapping” chapter 2017-08-25 Waldmann Review 2018-03-02 Waldmann

Reppenhagen Outdated information deleted; UMRR-11 introduced Review

2018-04-11 Waldmann Wiring Information for JBOX-01xxxx and JBOX-02xxxx UMRR-0F referenced deleted

4.2 Abbreviations

CAN Controller Area Network DC Direct current ESD Electrostatic Sensitive Devices GUI Graphical User Interface PC Personal computer RTC Real Time Clock TBD To be defined TOC Traffic Operations Center TMIB Traffic Management Interface Board TMIB2 Traffic Management Interface Board version 2 UMRR Universal Medium Range Radar smartWEB Webserver based Graphical User Interface (WEB-GUI)

4.3 Reference Documents

[RD1] Training Master Intersection CC


5 Overview

Welcome to your new TMIB Version 2 – the Traffic Management Interface Board V2. The TMIB2 connects UMRR sensors1 to Traffic Controller Cabinets or other Controllers, and provides extended functionality like Ethernet communication and many more. The TMIB2 comes as the main assembly, the TMIB_AB, providing most of its functionality.

1 Supported sensor families include UMRR-0C (available now) and UMRR-11 (future).

Figure 1: TMIB_AB V2 assembly


Figure 2: TMIB_C V2 assembly

For TS1 Loop Detector Output installations, TMIB_C extension cards are provided to route the Loop Detector Outputs to the contacts on the TS1 backplane, see chapter 13.6 )


5.1 TMIB2 Functionality

The TMIB provides the following functionality:

- Manages up to twelve UMRR sensors o 4x UMRR through RS485 (4-wire / full duplex), o 4x UMRR through Ethernet2 and o 2x UMRR through CAN3 bus

- Provides NEMA TS1 Loop Detector Outputs

- Provides NEMA TS2 SDLC interface

- Ethernet Interface for

o Remote Control of the TMIB2 o UMRR sensor setup, management and monitoring o Configuration with WEB-GUI

- Adds Real Time Clock time stamp to the UMRR sensor

data

The triggers / calls are generated by the UMRR sensors. The TMIB2 acts as a switch fabric which assigns the triggers / calls from the sensors to physical interfaces like TS1 Loop Detector Outputs or TS2 loops. For this purpose, the user has to perform three configuration steps on the TMIB:

1) Enable the relevant interfaces.

2) Enable the outputs actuated by the TMIB2.

3) Assign triggers / calls from the connected UMRRs to the outputs. The TMIB2 Configuration chapter 7 (page 27) will guide the user through this process.

2 Future ability 3 Future ability

Figure 3: TMIB_AB V2 fully connected


5.2 Connection Scheme

A UMRR sensor – TMIB2 system would be composed of the following items:

A) UMRR sensor(s) – a. Connect up to four sensors (RS485 4-wire) via the RJ45 terminals b. Connect up to four sensors (Ethernet) via the RJ45 Ethernet port c. Connect up to four sensors (CAN) via the RJ45 terminals

B) TMIB_AB V2 main assembly C) Cable to connect UMRRs and TMIB_AB V2 (see section 13.1) D) Controller Rack (not shown in image) E) Port 1 SDLC Cable F) TMIB_C V2 expansion cards (up to three cards) G) Cable to connect TMIB_AB V2 and TMIB_C V2 (see section 13.3) H) Ethernet Cable

This is a standard Cat.5 / Cat.6 cable with RJ45 connectors. I) External Sensor Power supply


Figure 4: TMIB_AB V2 connections

RS485 / CAN

ETHERNET

Relays

SD

LC

Remote Management

Update

I) B) A) A) C) H) F) G) E)


5.3 Connectors and Visual Elements

Reset Button

Status LEDs

4x UMRR Sensor Interface

RS485 4-wire

Port 1 NEMA TS2

SDLC Interface

External Power Supply

Ethernet USB

µSD Card cradle

4x4(16) Relays Expansion

Factory Defaults Button

Figure 5: TMIB_AB V2 front panel elements


Figure 6: TMIB_AB V2 rear panel elements

5.4 Reset Button

The TMIB can be reset (hardware reset) by pressing this button.

5.4.1 Factory Defaults Button

Please note:

By doing “factory reset” you erase every user defined data on the device: Logfiles, setups, IP-address changes… everything will return to the “clean” factory condition. You can reset the TMIB2 to its factory default setup following this sequence:

1. Press and hold down the “Factory default button” (use a paper clip, or a needle to do this) 2. While you hold down the “Factory default button” do a power cycle or Reset.

Continue to push “Factory default button”. 3. Now look to the LED-Matrix of the Front: After a short boot sequence, the LEDs starts

blinking fast for a few seconds. 4. When the blink interval of the LED slows down significantly, release the “Factory default

button” within 5 seconds. 5. If you changed your mind: Do not release the “Factory default button” while the LEDs are

blinking slow. 6. When the LEDs are getting dark, finally the reset will be done and a reboot happen with an

absolutely clean TMIB2, like fresh delivered out of factory. Note: the TMIB2 IP address will then be 192.168.11.1.


5.5 Sensor Power Supply

The TMIB2 offers provisions to source the UMRR sensors through the RJ45 sensor connectors. Note: UMRR-0C sensors should not use this ability because of limited current rating of the RJ45 connectors. For this purpose, external power has to be fed into the TMIB2 externally. The power supplied by the rack’s backplane cannot be used to feed the UMRR sensors since the current rating of the backplane may be exceeded depending on the rack manufacturer. Thus, the power to source the UMRR sensors can be fed into the TMIB2 through the 24V in External Power connector at the TMIB2 front. The UMRR-11xxxx sensors draw approx. 5W per unit. For other hardware, please refer to the UMRR data sheet. When sourcing the UMRR sensor through the TMIB2, the 24V in terminal has to be connected to the (DC) Power Supply. For ease of installation, the TMIB2 is fit with a terminal block here.

Figure 7: TMIB power supply switch location

Sensor supply override

Power supply select switch


5.5.1 Power supply select switch

There’s a switch to select between (i) external power supply (default setting) or (ii) rack power supply.

External power supply: The setting is used to power up to 4x UMRR sensors over TMIB2 Sensor connectors. Therefor you have to connect an external power supply of 24V to the external power input at the front panel (see chapter 5.1). Each UMRR-11 sensor requires a solid power of up to 5 Watt, one UMRR-0C needs up to 15W. Additional the power consumption of the TMIB2 is <4W typical. Rack power supply: In this position, only the TMIB2 is powered over NEMA rear panel power supply. It is not possible to power the sensors over TMIB2 when TMIB2 is fed over rear panel. The sensors have to be powered over a separate supply in this case.

5.5.2 Sensor supply override

You can turn off each sensor power manually for each of the four sensor ports of the TMIB2. If set to auto (default setting), the sensors will be automatically powered if connected. If you have self powered sensors and sensors powered by TMIB2 mixed, please be sure not to feed power over sensor ports. This may cause hardware damage. Be sure to switch the port of manually powered sensors to “OFF”.

Figure 8: Power supply select switch

Figure 9: Sensor Supply Override


5.5.3 Status LEDs

The Status LEDs provide feedback to the user about the functional status of the TMIB2.

The following table shows the meaning of the LEDs and their colors:

A B C D 6 TS2 Display Page 1 TS2 Display Page 2 ERROR Main SYS ERROR SDLC SYS 5 Power Good 5V Power Good 3.3V Heartbeat Main SYS Heartbeat SDLC SYS 4 Relay Nr. 13 Relay Nr. 14 Relay Nr. 15 Relay Nr. 16 3 Relay Nr. 09 Relay Nr. 10 Relay Nr. 11 Relay Nr. 12 2 Relay Nr. 05 Relay Nr. 06 Relay Nr. 07 Relay Nr. 08 1 Relay Nr. 01 Relay Nr. 02 Relay Nr. 03 Relay Nr. 04

Table 1: TMIB2 status LED field description

(Info: The table above is ordered exactly like the LED status field, so you can easily orient yourself.)

Figure 10: LED status field


Further details on the LEDs and their behavior:

- Relay: This LED relates to a TS1 Loop Detector Output and / or a TS2 SDLC loop. Whenever the trigger is TRUE, the corresponding LED will be ON.

- Error: ON or BLINKING in error state.

- TS2 Display Page 1 / 2: When TS1 functionality is deactivated and TS2 functionality is activated, the call states are displayed on the Relay No. 1 .. 16 LEDs. The 64 TS2 virtual loops are mapped to the 16 Relay LEDs as shown in Table 2: TS2 Display Page

below.

Display Page1

Display Page 2

TS2 Loop states on Relay LEDs

0 0 Relay 1.. 16 Loops 1 .. 16 1 0 Relay 1.. 16 Loops 17 .. 32 0 1 Relay 1.. 16 Loops 33 .. 48 1 1 Relay 1.. 16 Loops 49 .. 64

Table 2: TS2 Display Page

When TS2 functionality is deactivated, the TS2 Display Page LEDs are OFF.

- Heartbeat: LED shows utilization of the main processor: There are double flashes in intervals which indicate the utilization of the basis system. The shorter the interval, the more busy the system is.

- Heartbeat / Activity of SDLC subsystem: If there’s no outgoing SDLC data the blue LED will act like a heartbeat and blink in intervals of approx. 1 second. If TS2 data is send over SDLC the LED will display the transmit activity.

- Power Good: Diagnostics of the TMIB2 internal voltages.


5.6 NEMA TS2 over SDLC: Behavior of TMIB2 in NEMA Cabinets

The TMIB2 is not a thoroughbred BIU nor only a Detection Unit. It is a device needed to use modern detection solutions, but was not stipulated in the NEMA-TS2-2003 specification. You have to take this into account if you plan to test the conformity between the TMIB2 and the NEMA-TS2-2003 norm.

5.6.1 Physical Behavior

The SDLC of the TMIB2 is fully compliant to the physical specification of the NEMA-TS2-2003 specification:

Figure 11: SDLC Clock and Data

EIA-485 TMIB2 Maximum Cable Length 4000 FT. OK Maximum Data Rate (40ft. - 4000ft. for RS485) 10Mb/s-100Kb/s Fix: NEMA TS2 Maximum Driver Output Voltage -7V to +12V OK Driver Output Signal Level (Loaded Min.)

Loaded +/-1.5V OK

Driver Output Signal Level (Unloaded Max)

Unloaded +/-6V OK

Driver Load Impedance (Ohms) 54 OK Max. Driver Current in High Z State

Power On +/-100uA OK

Max. Driver Current in High Z State

Power Off +/-100uA OK

Slew Rate (Max.) N/A N/A Receiver Input Voltage Range -7V to +12V -14V to +14V Receiver Input Sensitivity +/-200mV OK Receiver Input Resistance (Ohms), (1 Standard Load for RS485)

>=12k = 12k

Figure 12: SDLC physical parameters (EIA-485 // TMIB2)


5.6.2 SDLC Frame

The SDLC Frame is defined in NEMA TS2-2003 as follows:

Figure 13: SDLC Framing

The TMIB2 is fully compliant to the SDLC framing defined by NEMA TS2-2003.

5.6.3 SDLC Request and Response

The TMIB2 will act in the NEMA cabinet like a detector BIU. Only Frames which are addressed to the DET BIU of the TMIB2 and which belongs to the DET BIU Frameset will be answered. Each response will be send directly after detecting a suitable request. There is only a short delay of about 150 ns to avoid leakage of data capture on some older traffic controllers. This does not affect the behavior of modern cabinets, but make immediate usage of existing controllers (e.g. ASC/2) possible. The TMIB2 has been designed to provide up to four Detection BIUs with up to 16 Detectors each. The NEMA TS2-2003 standard specifies the addresses of DET BIU #1..#4 as follows:

ADDRESS (8-bit, decimal) UNIT 8 Detector BIU #1 9 Detector BIU #2

10 Detector BIU #3 11 Detector BIU #4

Table 3: DET BIU Addresses


The TMIB2 will respond to the following request within the response time of max. 1 second after cold start in any case and fulfill the specification of NEMA TS2-2003.

REQUEST Frame:

ADDRESS TARGET RESPONSE Frame:

Info

9 255 ALL NO RESP. BCAST of time and date

20 8 DET BIU #1 148 CALL DATA 21 9 DET BIU #2 149 CALL DATA 22 10 DET BIU #3 150 CALL DATA 23 11 DET BIU #4 151 CALL DATA 24 8 DET BIU #1 152 DIAGNOSTIC 25 9 DET BIU #2 153 DIAGNOSTIC 26 10 DET BIU #3 154 DIAGNOSTIC 27 11 DET BIU #4 155 DIAGNOSTIC

Table 4: SDLC Request/Response Matrix

FROM Traffic

Controller

FROM TMIB2

CALL

RESPONSE


6 Installation

6.1 TMIB_AB V2 main assembly

Please note:

The TMIB_AB assembly is ESD rated. Handle with care. Installation The TMIB_AB V2 is installed in the cabinet by insertion of the card into the cabinet. For TS1 usage, the card slot must be capable of servicing four TS1 Loop Detector outputs. Gently push the card until card is inserted into the female multipoint connector. That is usually the case when the face plate aligns with the card file. The TMIB_AB V2 consumes two (2) slots in a NEMA rack.

6.1.1 Connect TMIB_C V2 expansion modules

TMIB_C V2 expansion modules can be connected by RJ50 terminated thru cables. Smartmicro supplies those cables in different lengths:

CABLE-0D0000 (1ft) CABLE-0D0100 (3ft)

6.1.2 Putting the TMIB_AB V2 to operation

The TMIB_AB V2 card is sourced from the rack backplane. The range of the backplane source voltage must be between 10 V and 32 V. When power is applied

- The LEDs 1..16 will light up for approx. one second; - The LEDs A..D will light up for approx. one second; - The Buzzer will sound.

The Power Good LEDs shall be on. The Heartbeat LED shall be blinking at approx. 1Hz frequency. The Relay LEDs may also be lit, depending on the configuration of the TMIB2. A factory default TMIB2 will show unlit Relay LEDs. For more details on the LEDs and their meaning, please refer to Table 1: TMIB2 status LED field description


6.2 TMIB_C V2 Expansion cards

Each TMIB_C V2 expansion card provides up to four Loop Detector channels. The TMIB_C V2 card is a passive device routing the contact closures to the right position in the cabinet backplane.

Figure 14: TMIB_C V2 extension card for TS1


6.2.1 TMIB_C V2 Configuration

There is no configuration necessary on the TMIB_C V2 cards. Usually, up to three TMIB_C V2 output expansion cards will be needed to provide full output range of 16 channels (together with the TMIB_AB V2 card).

6.2.2 TMIB_C V2 Hardware installation

The TMIB_C V2 is installed in the cabinet by insertion of the card into the cabinet. The card slot must be capable of servicing four TS1 Loop Detector outputs. Gently push the card until card is inserted into the female multipoint connector. That is usually the case when the face plate aligns with the card file.

Figure 15: Signal flow scheme TMIB-C V2

To NEMA Back plane


7 TMIB2 Configuration using TMConfigurator

7.1 Tools needed

You need the Easy Mode TMConfigurator software version 1.4 or greater to perform the installation steps. That software runs on a Windows 7 / Windows 10 based PC. When you download the TMConfigurator software from the above link, please install and perform first-time registration. The TMConfigurator software will guide you through this process. The TMIB2 is most easily configured through the IP interface. Your computer needs to be set to IP 192.168.11.1, subnet mask 255.255.255.0. Check your Firewall to allow connections on port 55555. You will need a Cat.5 RJ45 cable (straight) to connect to the TMIB2’s Ethernet port.

7.2 Easy Mode, Super Easy Mode and TMConfigurator Expert Mode

The TMConfigurator software supports three modes, for different user skills. By default, the PC software starts in Easy Mode. In that mode, your TMIB2 (at factory default settings) will be detected and managed by the TMConfigurator software. smartmicro strongly suggests using the Easy Mode or Super Easy Mode to set up your RADAR detection system including TMIB2. The installation process is easier to manage than the TMConfigurator Expert Mode. When using TMConfigurator Expert Mode, we recommend to pre-configure the following parameters prior to installation:

- Number of connected UMRRs - Activation of functions (TS1, TS2 SDLC, …) - Optional: Ethernet IP address and gateway


7.3 (Super) Easy Mode setup

This is the simplest way to get an installation working. You can configure the whole intersection installation in your office before installing the hardware in the field. Start your TMConfigurator program. You will get the following intro screen:

INFORMATION

If you need assistance, feel free to click “Show Video”. This will show you a step by step manual of how to use the Easy Mode setup of the TMConfigurator.

If you do not get this screen, push “ALT” and “L” key on your keyboard. Load the desktop called “TMConfigurator_EasyMode.dsk” and the screen will show up.

INFORMATION

The Super Easy Mode is a very simple method to connect ONE sensor and one TMIB to an intersection. If you want to configure more sensors, please use the “Easy Mode”, which is able to install more than one sensor. There’s a build in video manual also for the usage of the easy mode, so feel free to watch it. You can access the video manual by pressing the button. This manual will continue to show the Super Easy Mode.

Figure 16: Easy Mode mode selection


Choose “New Super Easy” and click “Next”.

Now enter a filename to archive your installation. In this case, I the filename is “example”.

Follow the instructions of this screen mask and click „Next“.

Figure 17: File name of .TISF setup file

Figure 18: Easy Mode Basic settings


Please notify the wiring of the installation and press “Next”.

Figure 19: Easy Mode Check list


The TMConfigurator now performs auto detection of the connected hardware. Allow a few seconds to search the hardware.

In this example, you can see the hardware found in your installation. In this example, it is: one TMIB With ID 48 one UMRR With ID 1 Both devices found over Ethernet4. Please press “Next” to start the installation process: .. define lanes and measurement lines.

On the following screens, you will adapt the lane settings and triggers (calls) configuration of the sensor, and perform a sensor alignment procedure. Finally, connect the sensor triggers / calls to your TMIB2 outputs.

4 The sensor is connected to the TMIB2 via RS485, the TMIB2 connected via Ethernet to the TMConfigurator.

Figure 20: Easy Mode communication test


Figure 21: Easy Mode TS1/TS2 configuration

7.3.1 Setting up TS1 or TS2 functionality

Once the sensor and its triggers are set up, you will reach the TMIB page. The options are:

(1) NEMA TS 1 configuration (TS1 outputs: Detector 1..4 = TMIB_AB, Detector 5..16 = TMIB_C)

(2) NEMA TS 2 configuration (SDLC, DET-BIU’s: 1..4, each 16 detectors)

(3) TS2 paging settings (see next page).

1 2

c

3

Map sensor trigger as NEMA detectors:

(a) Select the detectors of the NEMA DR-BIU (BIU 1..4, or TS1 Outputs) you want to use.

(b) Activate those sensor triggers, you wish to serve the corresponding BIU-Detector. (Mapping)

(c) Activate the TS2/TS1 subsystem


7.3.1.1.1 Monitor the triggering of the NEMA Detectors The TMIB2 offers 16 LEDs as call indicators. TS1 operation offers 16 outputs; TS2 operation offers 64 outputs. You can display the 64 output states in pages of 16 LEDs. On the previous page the LED settings have been marked in “red” and numbered with “3”. In this input mask, you can select the page you wish to monitor, which is corresponding to the DET-BIU. If you activated more than one BIU with 16 detectors each, you can “rotate” the monitoring by giving a “time” in seconds of the intervals the page will be shown. Two indicator LEDs will show you which page is actually monitored:

After clicking “Next”, you will receive the last window of the Super Easy Mode:

Figure 22: Easy Mode save settings

After all installations are done, you are able to Apply the settings to the TMIB2. Therefore, simply click “Apply Settings” and the transfer will be started:

LED „Page Index“ for TS2 action: 00 = Page1 = BIU1 01 = Page2 = BIU2 10 = Page3 = BIU3 11 = Page4 = BIU4

3


Figure 23: Easy mode send data info

If everything has been programmed correct, you will get an information about the success. Otherwise, the errors will be displayed.

Figure 24: Easy Mode success info

The setup process is finished now.


7.4 Easy Mode: Modify TMIB2 settings

You can change the settings of the TMIB2 by using the Easy Mode “Tool Wizard”.

Please note:

There must be a working *.tisf project file in place before you can open the wizard. Those files will be automatically created by starting an Easy Mode project. To open the Tool Wizard, please open your TMConfigurator and watch out for the small “Information Box” which is placed at the lower right:

Figure 25: Choose "Tool Wizard"


The following window will open.

Figure 26: Easy Mode Tool Wizard

Now you entered the Tool Wizard.

7.4.1 Change the TMIB2 trigger / call assignments

Select TMIB from the menu in the left.

Read the configuration from the TMIB2 by pressing “Load from TMIB”.

Now you can modify the trigger / call assignments. When done, press “Apply to TMIB”.


7.4.2 Change IP Address using Easy Mode

After opening the Tool Wizard, click on “Connections” and “Ethernet Settings” to open the following window:

Figure 27: Change ETH settings using Wizard

You can change the IP-Address of the TMIB2, which connect to the TMConfigurator PC, by modifying the field which is marked with the red arrow. If you are unsure what is meant with Subnet, Gateway or IP-Address, do not attempt to modify. To apply the changes made, click the “Apply All” button.


7.4.3 Synchronize Time using Easy Mode

You can synchronize the Real-Time Clock (RTC) of the TMIB2 using Easy Mode software.

Figure 28: Start the Tool Wizard

On the “Easy Mode” Desktop, there is a small sub window called “Information Box”. To start the Tool Wizard, we need to enter synchronizing the Time, press “Tool Wizard”. After clicking the Tool Wizard, please go to “Other” and select “Time Synchronization”. You should see the following mask:

Figure 29: Sync RTC in the wizard

Select which Device you like to synchronize (best: Sync them all to a unique timebase) and then press on the lower right side the button “Sync RTC” to start synchronization.


7.4.4 Data Recorder

The TMConfigurator offers the possibility to record specified and filtered data from the UMRR “on the fly”. After recording you can playback this data with twice the speed.

Figure 30: Use simple data recorder of Wizard

“Record, playback, stop and delete“ panel

Decide what your record shall contain (filtering)

Definitions of the recorded device

Limit recording bandwidth


7.5 TMConfigurator: Configurations in Expert Mode

Start TMConfigurator (TMC). Select File -> Load Desktop -> TMIB to start in Expert Mode. TMIB1 users: The configuration steps for TMIB1 and TMIB2 are almost identical.

7.5.1 Monitoring

Upon start of TMConfigurator software, you are asked if “MONITORING” should be activated: Yes, it should. This start connecting to TMIB2 and showing what is going on in the environment of the TMIB2.

Figure 31: Start monitoring TMIB2 action


7.5.2 Set up Basic Parameters – DEVICE MAPPINGS.

In this step, you will activate the individual TMIB2 features that are required for the intersection or cabinet installation. It is suggested to set up the basic parameters contained in this section before taking the TMIB2 to the intersection and before wiring the TMIB-sensor system together. 1. Start up the TMConfigurator. On the HW Monitor, please check the following settings:

Figure 32: TMC hardware monitor


2. Under Connection General Settings > select Connection Type and click the drop down menu to view and select the TMIBv2Mode.

Figure 33: Ethernet settings for TMIB2


3. Under “Settings for Devices in TCP Server Mode”, click the Device Mappings to view the Device Mapping Editor page.

Figure 34: Open Device Mappings


4. In the Device Mappings Editor page, the Bus no. / CAN no. of each device is uniquely defined in order to avoid CAN no. duplication.

4.1 Click Add button in the Device mapping editor.

4.2. Change the default Bus. No. – 1 to any no. Let’s say 31. Enter the serial number of the active sensor. On this sample, the serial no. of 0C-42 is 29494. Then, click OK.


6. Click reinit button in the Ethernet Settings page to update the CAN no.

7. The Ethernet indicator button shall go green. Connection to the TMIB2 is now established.

5. Click Set button in the Ethernet Settings page to effect the settings made.


8. Change to the TMConfigurator Window or Click the TMConfigurator Tab.

Figure 35: Open TMConfigurator window

Figure 36: TMConfigurator window


9. Read the Sensor Firmware.

9.1 Click Sensor Network> click Start Config for UMRR_0 On this sample, there is only one sensor connected.

Figure 37: Sensor Network


Figure 38: Configure SensorNetwork

10. In Configure Sensor Network, set the CAN Bus no., Device ID no. And the sensor type. Click the Read Firmware version + Serial Number to display the serial no. (On this sample, the sensor CAN bus no. is 31, Device ID is 0, and the sensor type is OC.)


11. Configure Sensor Mapping.

11.1 Click TMIB tab> click Start Config for TMIB_48. Click Sensor Mapping.

Figure 39: TMIB window

11.2 After clicking the Sensor mapping, a sub page will pop-up displaying the Sensor to TMIB. 11.3 Uncheck the UMRR that are not connected or not displaying its serial no. Check only the sensor that displays its serial no. 11.4 Then, click OK button.

Figure 40: Sensor Mapping

11.5 Sensor Device Mapping is now completed.


Press “Setup TMIB”.

The TMIB property editor will open, allowing you to change the basic settings.

Figure 41: TMIB generation selector


Figure 42: TMIB property editor


7.5.3 IP Settings

In case you wish to set IP (TMIB IP, Gateway, settings other than the default settings, please make your modifications in this section.

Figure 43: TMIB IP settings

By default, the TMIB acts as Connection Client, i.e. the TMIB will establish the TCP/IP connection. The TMIB Server Mode Setting changes this behavior to program the TMIB to accept TCP/IP connections. You can control the behavior of the Ethernet interface by changing the following field:

Options are:

User Interface: This is the default setting. User messages (such as TS1 Relay States and TS2 Loops States) as well TMIB as status messages will be transmitted.

Debug Interface: All messages will be transmitted. For Debug purpose. For enabling of the UMRR reports in the TMC displays. Set Debug Interface if you want to configure the UMRRs while connected to the TMIB2.

Figure 44: TMIB control settings


7.5.4 Activate TS1 Outputs

Skip this section if TS1 Outputs are not used. You can switch on the TS1 Relay or the TS2 SDLC Bus, if you set the corresponding state from False to True

As an option, the output logic of the TS1 Loop Detector outputs can be inverted. This is a software setting and does not change the behavior when the TMIB is powered OFF. It applies only when the TMIB is switched ON.

In addition to activation of the TS1 module, the User will have to activate and assign the TS1 outputs to physical channels in a later configuration step, see section 0.

7.5.5 Activate TS2 SDLC / Detector BIUs

Skip this section if SDLC is not used. Activate the TS2 module by setting TS2 SDLC Active to True:

Next, activate the Detector BIUs assigned to this TMIB2. All four Detector BIUs may be activated. Be sure to have no two components with the same Detector BIU activated in your controller assembly.

Figure 45: TMIB activation

Figure 46: TMIB invert GPIO output

Figure 47: TMIB TS2 (SDLC) activation

Figure 48: Detector BIU activation


7.5.6 Number of UMRR sensors / Baud rates.

Enter the number of connected UMRR sensors. The TMIB2 will monitor communication to the configured number of sensors. If UMRR sensors are not present in the assembly, the TMIB will report failure of communication to those missing UMRR sensor(s).

Default communication to the UMRR sensors is RS485 / half Duplex / 115kbps. You can modify these parameters in the following section:

Please note:

Only RS485 is tested and verified, Ethernet is working, but a new feature without being fully tested The baud rate shall not be changed, Only Full Duplex communication is supported.

Figure 49: Select number of connected UMRR

Figure 50: UMRR sensor com parameters


7.5.7 Finalize the set-up

Press the “Set” button on the TMIB2 PropertyEditor to apply the changes to the TMC software.

Figure 7-1: TMIB PropertyEditor

Next press to apply the parameters to the TMIB2. Upon IP parameter changes, the TMIB2 will be disconnected and reconnected after a few seconds; A reset and reconfiguration will be done on TMIB2 automatically. The settings can be stored in a desktop file. Please note that also the visual settings are stored, not only the TMIB2 settings.

With this configuration step the basic parameters are now set to the TMIB2. It can now be installed in the cabinet. Next step is to configure the sensors.

Figure 51: Save settings


7.5.8 Configure UMRR Sensors through TMIB2

This section describes the configuration of UMRR sensors which are connected to the TMIB, while the user is connected to the TMIB2 via Ethernet using TMC software. To perform this step, the TMIB2 must be completely configured. The UMRR sensor shall not be connected to the TMIB2 at this point. Start the TMC software. Verify on the HW Monitor that the TMIB2 connects.

Figure 52: Established TMIB2 connection

7.5.9 Setup the UMRR sensor network

Go to the Configure Bar. You need to set TMC Mode to “Full”. You can add / remove UMRR sensors from the network configuration by selecting the Sensor Network dialog.

Figure 53: Setup UMRR sensor network


7.5.10 Set up background image

If you have internet connection available, you can load the background image from the web. 1) Place: Type in the location , press “Find” 2) If the place is found, press “Go” 3) You can move the center of the image by using the “Change coordinates” field. 4) Select “Use loaded bitmap as background Image” 5) In the Image Setup dialog, you can fine tune the position and orientation. 6) Store the Desktop.

Figure 54: Get background image from the web


7.5.11 Set up UMRR sensor IDs (UMRR-0F only)

Note: Do not perform ID change with UMRR-0C or UMRR-11 sensors. The UMRR sensor comes with factory default setting ID0. In a sensor network on one TMIB2, the UMRR sensor needs to be programmed its sensor ID. Numbers range from 0 to 3. In order to set the sensor IDs, perform the following steps:

1) Plug in one sensor to any UMRR port of the TMIB. The sensor will now show up on the HW monitor.

Figure 55: TMIB and sensor ID0 connected

2) Set the correct Sensor ID. Refer to UMRR documentation section 6.2

(How to change the sensor ID).

3) Select that sensor ID on the Configure Bar.

4) Set the sensor position and orientation on the Configure SensorNetwork dialog.


Figure 56: Configure sensor network

a. Press Start Config for UMRR_IDx to start the configuration

Note: The display will turn so that the activated UMRR ID is pointing to the top. b. Request firmware version + serial number c. Note down / compare these numbers with installation plan d. Do the position and orientation settings e. When done, press Stop Config for UMRR_IDx

5) Unplug this sensor and proceed with the next one, until all sensor IDs have been set.

Please proceed with the alignment and set up of the triggers, see next section.


7.5.12 Set up UMRR sensor alignment and triggers

Now each sensor needs to be aligned and its triggers have to be set up. Connect all sensors to the TMIB2. In this example, four sensors are parameterized in the network, and two are not responding (ID2 and ID3 are marked orange and show no data throughput).

Figure 57: Connection established to TMIB2 with two sensors

For every sensor, please perform the following steps:

1) Perform the alignment (see also [RD1] Section 11 and 11b).

2) Set up the lanes and Measurement Lines (see also [RD1] Section 11). There is also a step-by-step instruction available for Stop Bar Presence Detection trigger set-up in [RD1] Section 23).

3) Set up the Triggers (see also [RD1] Sections 11, 12, and 13). There is also a step-by-step instruction available for Stop Bar Presence Detection trigger set-up in [RD1] Section 23). Note: Besides Presence Detection, the UMRR’s Event Trigger Module allows for many sorts of triggers (Speed trigger, One-time ETA, …). Please refer to [RD1] Sections 11, 12, and 13 or to the UMRR documentation. Note: Each UMRR reports up to 16 Relay triggers. The user makes references of the UMRR’s triggers to the physical relay and SDLC loop outputs in the Assignment Matrix later in the configuration process.

4) Test and optimize the quality of the triggers.

5) Store this UMRR setting by making the parameter permanent.

6) Proceed with the next UMRR sensor.


7.5.13 Synchronize Date and Time

To set the TMIB2’s Real Time Clock (RTC), push the Sync Time button.

Figure 58: Synchronize date and time

Please note:

Date and Time are retrieved from the host PC as local time. The RTC backup battery is maintenance free. It has the capacity for one day without external

power. After that time, the RTC has to be synchronized anew.


7.5.14 Configure TS1 Loop Detector outputs

This section requires that - The sensors and its communication with the TMIB2 have been successfully configured. - In particular, TS1 has to be activated there or else no TS1 configuration can be performed. - UMRR sensors are set up by their positions and their triggers (section 7.5.12).

After this is made sure, make the following steps:

Figure 59: Configure TS1 loop detector outputs

To save space on your screen, several elements can be minimized using the [-] button, and maximized by pressing the [+] button. In the example, the following configuration has been made:

(4) Activate the TS1 outputs

(3) Relate trigger to outputs

(2) … for each sensor connected

(1) Open (+) to see more sensor fields


Figure 60: Relate a trigger to output

a. 4 UMRR sensor network b. TS1 Loop Detector outputs active. c. TS2 SDLC loops inactive. d. No TS1 Loop Detector output assigned.

Note: It is required to enable the TS1 outputs on the “Assignment” matrices. The TMIB will only set such assigned outputs.

e. UMRR ID0 TS1 assignment matrices have been set to default. The user will have to change the assignment setting to clear any unused assignments.

f. UMRR ID1 and ID2 have been hidden (see [+] Sensor 1 / [+] Sensor 2). The user will have to change the assignment setting to clear any unused assignments.

g. UMRR ID3 TS2 assignment matrix has been set to default. The user will have to change the assignment setting to clear any unused assignments.

The user can enable individual outputs (see Assignment section) and route UMRR triggers to TS1 outputs. Sensor Trigger denotes the UMRR trigger input here, TS1 Output denotes the TS1 Loop Detector output.


Please note:

Check the Assignments for the other sensors also. There are Sensor 0 through Sensor 3. There should be assignments defined for sensors that are present only. The TMConfigurator standard desktop may contain assignments for all four sensors. The user would have to clear assignments for sensors that are not present. Otherwise, the TMIB may report error condition because of missing sensor reports for assigned channels. After setting the Assignments, enable the assigned outputs. In the example above, enable TS1 Output 8 on the Assignment..

When done, press to make the parameters permanent to the TMIB.

Attention:

The TMIB2 will reboot after pressing and will reconnect a few seconds later.

Figure 61: Enable assigned TSI outputs


7.5.15 Status message configuration

The TMIB2 have been shipped with compatible configuration of the TMIB V1 for easier replacement or building on known issues. But it is more powerful! To enjoy the full power of the TMIB2 in the TMConfigurator you should enable all features to be send. Therefor you have to send a command to the TMIB2 which let him fill the status message with all available information (e.g. the onboard temperature, the NEMA output status information and so on…) Fill the “command” mask with the following values: Parameter 37 Action 260 Value 0xffff Enable UAT (UAT V1)

7.5.16 Test the Assignments

Whenever a trigger / call is actuated, the corresponding input/output in the assignment matrix goes red. In the example, UMRR ID0 generates a trigger on its Trigger Output #11 (see the red line in the matrix), and the assignment translates this trigger into a call on TS1 Loop Detector output #11 (see red rectangle in the Activate line). Please note: To see these red lines in the matrix, the Ethernet configuration must be set to Debug Interface, see section 7.5.6. Otherwise, you will see the TMIB Loop Detector output trigger as a red rectangle in the Assignment field only.

Figure 62: Enable "send everything" feature


Figure 63: Example of actuated TS1 output

INFORMATION

To see the trigger affecting the NEMA TS1/TS2 Outputs, you have to switch ON the transmission of ALL messages to be send from TMIB2. Refer to chapter 7.5.15.

7.5.17 Configure TS2 SDLC

This section requires that the TMIB2 has been successfully setup with the Easy Mode. In particular, TS2 has to be activated there or else no TS2 configuration can be performed. Verify that the Detector BIUs have been activated also. UMRR sensors are set up by their positions and their triggers (section 7.5.12). Go to the Configure Bar, select the TMIB button. The TMIB configuration dialog will open.


Figure 64: Configure TS2 loops

To save space on your screen, several elements can be minimized using the [-] button, and maximized by pressing the [+] button.


In the example the following configuration has been made: a. 4 UMRR sensor network b. TS1 Loop Detector outputs inactive. c. TS2 SDLC loops active. d. No TS1 Loop Detector output assigned

Note: It is required to enable the TS2 outputs on the “Assignment” section. The TMIB2 will only set such assigned outputs.

e. No TS2 Loop assigned f. UMRR ID0 TS1 and TS2 assignment matrices have been set to default. The user will

have to change the assignment setting to clear any unused assignments. g. UMRR ID1 and ID2 have been hidden (see [+] Sensor 1 / [+] Sensor 2). The user will

have to change the assignment setting to clear any unused assignments. h. UMRR ID3 TS2 assignment matrix has been set to default. The user will have to change

the assignment setting to clear any unused assignments. The user can enable individual outputs (see Assignment section) and assign UMRR triggers to TS2 outputs.

Figure 65: UMRR trigger assignment to TS2 loop

Sensor Trigger denotes the UMRR trigger input here, TS2 SDLC Loop denotes the TS2 loop output.

Please note

Check the Assignments for the other sensors also. There are Sensor 0 through Sensor 3. There should be assignments defined for sensors that are present only. The TMConfigurator standard desktop may contain assignments for all four sensors. The user would have to clear assignments for sensors that are not present. Otherwise, the TMIB may report error condition because of missing sensor reports for assigned channels. After setting the Assignments, enable the assigned outputs. In the example above, enable TS2 SDLC Loop 11 on the Assignment.


Figure 66: Enable assignment TS2 - SDLC loop

When done, press to make the parameters permanent to the TMIB2.

7.5.18 Status message configuration

The TMIB2 have been shipped with compatible configuration of the TMIB V1 for easier replacement or building on known issues. But it is more powerful! To enjoy the full power of the TMIB2 in the TMConfigurator you should enable all features to be send. Therefor you have to send a command to the TMIB2 which let him fill the status message with all available information (e.g. the onboard temperature, the NEMA output status information and so on…) Fill the “command” mask with the following values: Parameter 37 Action 260 Value 0xffff Enable UAT (UAT V1)

Figure 67: Enable "send everything" feature


7.5.19 Test the Assignments

Whenever a trigger / call is actuated, the corresponding input/output in the assignment matrix goes red. In the example below, UMRR ID0 generates a trigger on its Trigger Output #2 (see the red line in the matrix), and the assignment translates this trigger into a call on TS2 loop #2 (see red rectangle in the Assignment line).

Please note:

To see these red lines in the matrix, the Ethernet configuration must be set to Debug Interface, see section 7.5.6. Otherwise, you will see the TMIB2 TS2 SDLC loop trigger as a red rectangle in the Assignment field only.

Figure 68: Example of actuated TS2 loop

INFORMATION

To see the trigger affecting the NEMA TS1/TS2 Outputs, you have to switch ON the transmission of ALL messages to be send from TMIB2. Refer to chapter 7.5.15.


7.5.20 Commands

Selecting the TMIB tab on the Configure Bar brings up the following screen:

Figure 69: TMC - TMIB direct commands

The Commands and their Meanings are:

- Sync Time: Set the TMIB Date and time according to the PC clock.

- Re-detect Sensors: This button will no longer be used.

- Rest TMIB: Perform a software Reset.

- Advanced Commands: For the Experienced User only.


8 Advanced Usage of TMConfigurator Expert Mode

8.1 Advanced Commands in TMIB configuration

For the Experienced User only. Don’t play.

Selecting the Advanced Commands from the Commands field brings up the following dialog:

Figure 70: Advanced command dialog

The Advanced Commands are:

- Change ID: Please refer to section 0.

- Reset EEPROM: Erase all user data and return to factory default settings. You will also clean up the logfile and the configuration management (all restore points will be lost! Be sure to download those you wish to keep).


8.2 TMIB ID Change

For the Experienced User only. Don’t play.

Each TMIB2 has a Communication Device ID. The factory default is 48. You can set the Communication Device ID to other values, i.e. if more than one TMIB2 is present in an installation. Please pre-set the Communication Device IDs before operating more than one TMIB2 on the same (CAN or Ethernet) data connection. Selecting the Advanced Commands from the Commands Bar brings up the following dialog:

Figure 71: Advanced commands dialog

To change the TMIB2 Communication Device ID, select the new ID from the dropdown list. Then press Change ID. The TMIB2 will restart with the new Communication Device ID. You will then receive a permitted error message, because the TMIB2 establishes communication under the new set ID.

ATTENTION

Changes will appear immediately and result a TMIB2 Reset. After such a change, the TMIB2 comes up again with the new TMID-ID, chosen in the mask above.


8.3 Example of multiple TMIB2 use

The following two examples show the principle network layout if you use multiple TMIB2s or multiple PCs at the same time.

8.3.1 Principle Network Layout – TMIB2 Client Mode

To monitor multiple TMIBs over one PC, the default connection mode Client Mode can be used for establishing a TCP/IP connection to the TMConfigurator. Each TMIB has to be configured with the same Target IP and Target Port but with different TMIB2 device IDs (ID48 to ID52) and different TMIB IP Addresses (see chapter 7 for details). [BW1] Please check your network adapter settings (Windows – Control Panel) and add the IP address 192.168.11.1 for your PC. Once the IP address has been added, restart TMConfigurator and select this IP address in the Setting List.

Figure 72: TMIB2 Client Mode


9 The WEB-GUI

This great new feature of the TMIB2 is the operation upon the embedded Linux operating system on a powerful Microcontroller and the possibility to use a webserver for much more comfortable user communication. On the next pages we introduce the WEB-GUI of the TMIB2 and how to take advantage of it.

9.1 Access the WEB-GUI

To access the WEB-GUI called “smartWEB” you have to type in the IP-Address of the TMIB into the address bar of your web browser. To get knowledge, what the IP-Address of your TMIB is, please refer to chapter 7.4.2.

9.2 Boot status and Version information

The homepage of the TMIB2 shows all versioning information and selected setup parameters.

Figure 9-1: Homepage TMIB2 WEB GUI Server


Web GUI name Item TMIB ID Identifier of the TMIB in TMC network Connected UMRR Count of connected Sensors as parameterized )5 Serial Number Unique serial number of this TMIB Ethernet MAC Unique MAC address of this TMIB Generation This is the versioning of the TMIB2:

New generation TMIB starts generation: V2. If there are some changes, Revision or Modification will specify significant or less significant changes.

Modification Revision

Processor Name and model of the used processor Software release ID ID of the firmware release (FW version) )6 Linux Kernel Name & Version of the kernel used in this FW release Linux Bootloader Name & Version of the boot loader used in this FW release ATX Mega firmware Version of the ATX Application used in this FW release ATX Mega iface Smartmicro Interface Version used between ARM/ATX Booted partition Please take a look at chapter 10 for explanation )7

5 Software value will not represent real connected sensors. Only those who are parameterized to work in the current configuration. 6 This identify the number of the concerted package of firmware components, incl. Linux bootloader, Linux Kernel, ATX Firmware. This is also the ID of the TMIB2 App. 7 We can hold two independent, bootable firmwares in two partitions on the flash of the TMIB2.


9.3 Navigation: Use the WEB-GUI

Go to status page

Configure RS485 settings (see chapter: 9.4 )

Configure IP settings of the WEB GUI (See chapter 9.5.2)

Configure IP settings and mode of the TMC Ethernet connection (see chapter 9.5.3)

Configure IP settings and mode of the sensor Ethernet connection (see chapter 9.5.4)

OPTIONAL: Configure CAN bus (see chapter 9.6)

Configure error logging and protocoling of the system (see chapter 9.7.1.1.1)

Access some control features (see chapter 9.7.2)

Ethernet utilities (see chapter 9.7.3)

Set RTC and System time and date (see chapter 9.7.4)

Save and restore configurations (see chapter 9.7.5)

Reset everything to factory defaults (see chapter 9.7.7) 9.7.7)

Reboot the TMIB (see chapter 9.7.8)

Show (download) Logfile (see chapter 9.8)

Update firmware of TMIB2 (see chapter 10)

Figure 73: WEB GUI menu

Status overview connected sensors (see chapter 9.10)

Reset configurations to factory default settings


9.3.1 General information

It is important to know exactly how to change the parameters in the masks of the WEB GUI and how to make the system take care of the changed parameters: Please change the values you wish to change and always click submit and check. After this click your settings will be checked and if there’s something wrong or your changes can’t be set, there will be an information and often a tip how to correct the mistake. After you submitted and checked your changes, you can press the button “SAVE and APPLY” to save the data and reboot the TMIB to let changes take effect. When a reboot is required after an action, the TMIB the WEB GUI will suggest a reboot. Please follow that suggestion to make changes take effect. 9.3.1.1.1 Example of guided error handling Some well-known errors and those which often happen are intercepted by the checking system of the WEB-GUI. Let’s take a look what will happen if you try to set an invalid IP-Address:

Figure 74: WEB GUI: example of guided error handling


If you try to set an IP address out of the reach of an entire network, the GUI will also warn:

Figure 75: WEB GUI: example safety information

If such an error will affect the integrity of the system, you are not able to save the values until the problem is solved.

HINT:

This check will ensure that you do not lock yourself out of the device by entering invalid configurations in the network settings. Even after a factory reset you have a chance to get in contact with the TMIB2 is you have lost the access data shown on the GUI site: Simply use the TMC Easy Mode to get in contact with the TMIB2 again. If you have the Serial Number, the TMC will show you the resulting IP address.


9.3.2 Default values and user settings

Figure 76: WEB GUI: Interactive buttons

You can load the last user settings (if you did not click the „save“ button) by simply click on the “reload” button. In this case the last stored user settings will fill the mask. If you wish to load the factory default settings, please click the button called “defaults”. In some cases it is possible to “APPLY” settings without a restart or saving into the confguration file. These settings (e.g. on the WEB-GUI IP configuration site) will not survive a reboot.

9.4 RS485 (EIA 485) Settings

Figure 77: WEB GUI: RS485 settings

9.4.1 RS485 - Speed

Default is 115200. There are three RS485 speed settings which our connected sensors may be connected with. Usually 115200 (the default setting) will be the right one.

RS 485 speed selection -> chapter 9.4.1


9.5 Setup Ethernet addresses

The Ethernet connectivity is defined through these parameters: - IP address, - subnet mask (IP-mask) and - optional a gateway in the same network range the TMIB2 is.

9.5.1 The Default Gateway of the system

You can enter a default gateway which will be used for routing porposes of the TMIB2. Use the “Gateway” entry in the WEB-GUI maskto set the default gateway of the entire system. If unsure, enter nothing here. The default gateway has to be in the same network the WEB-GUI is accessible in order to grant access to the WEB GUI.

9.5.2 IP-Address of the WEB-GUI Webserver

Figure 78: WEB GUI: IP setting of TMIB web server

9.5.2.1.1 Temporary changes and persistent changes Only for the WEB-GUI IP (accessibility of the WEB GUI) it is possible to change the IP address temporarily by pressing “take and check”. Only if you “APPLY”, after a reboot the old values will be used instead of these temporary settings.


9.5.3 IP-Address and behavior of the TMConfigurator communication

Figure 79: WEB GUI: Ethernet setup TMConfigurator communication

9.5.3.1.1 IP address, mask and gateway Ask the administrator of your network about the settings you have do here. The IP address is the address you have to type in the “URL”-field of your browser to connect the web GUI of the TMIB in this case. If your PC is located in another network than the TMIB2, you have to use a gateway. This gateway has to be in the same network the TMIB is. The range of the network is defined by the IP-mask. For unusual networks, smartWEB tells you the NetIP, too. The current settings are also printed. 9.5.3.1.2 Port Default: 55555. This value has to fit with the Port setting of the TMConfigurator. 9.5.3.1.3 Mode selection Default: TCP Client. The four modes have to correlate with the settings in the TMConfigurator and your requirements: Note: UDP is not supported yet. TCP Client: The TMIB2 will establish the IP connection. TCP Server: The TMIB2 will wait for an IP connection to be established.


9.5.4 IP-Address and behavior of the sensor network

Figure 80: WEB GUI: Ethernet setup sensor network

These settings are for sensors connections over Ethernet. 9.5.4.1.1 IP address, mask and gateway To access an Ethernet device, a unique identifier called: “IP address” has to be assigned. This number is valid in a special context which is defined by the “netmask”. There are several classes of possible nets… In our example (which is the default setting by factory) we use a so called “Class C” network, which is defined by a netmask: 255.255.2555.0. A gateway is used to access addresses outside such a network, e.g. 159.21.23.5… in such a case you have to install a gateway (This is usually a router) and tell the TMIB about its local IP which have to be in the same network as the TMIB is. If this explanation is all “Greek” to you, please do not modify the settings. 9.5.4.1.2 Port Default: 55555. This value has to match the Port setting of the sensors. 9.5.4.1.3 Mode selection Default: TCP SERVER. Note: UDP is not supported yet, but will make things more performing in the future.


9.6 Setup CAN bus

The CAN module is not approved. It is possible to connect a sensor over CAN bus, but it is only barely tested yet. The values to set explains are self-explanatory: There a speed to select according to the data sheet of the sensor to connect with. Usually you have to use the MOXA interface type to connect to a sensor over CAN bus. Please refer to the pinout of the “UMRR” connectors to find out how to connect the sensors to the CAN bus: Take a look to chapter 13.1.

Please note:

CAN Bus functionality is not yet an approved connection mode. Use RS485 or Ethernet as recommended connection type.

Figure 81: WEB GUI: CAN settings


9.7 System control

This is a collection of useful tools to interact with the TMIB and control or monitor the behavior of the system.

9.7.1 System settings

Figure 82: WEB GUI: System settings

9.7.1.1.1 Verbose level of TMIB2 logging system You are able to set the verbose level of the TMIB Application Logging System. In case of serious failures, it might be necessary to log as much data as possible: Only in those cases it is a good idea to set the verbose level on “DEBUG”. There will be so much data, that this action should be limited to a short time and outside productive environments. The more data have to be logged, the more system performance it will take. So only logging “errors” or up to “warnings” is a good idea in high reliable environments.


9.7.2 System control and monitoring tools

Figure 83: WEB GUI: System control and monitoring tools

9.7.2.1.1 Restart TMIB2 App This is a developer feature. Do not play. 9.7.2.1.2 System Performance health By clicking on this button, you will get a performance monitor and see how busy the TMIB2 is at the moment (with “MAX” indicator). To see the processor load, take a look to this monitor. This is the way on which unlimited possibilities meets the natural limitations of a system based on limited resources. If 100% is reached, a separate window is opened in your browser to inform you about the inconsistency of the system.

Figure 84: WEB GUI: system performance monitor


9.7.3 Ethernet service tools

Figure 85: WEB GUI: Useful Ethernet utilities

The Ethernet tool collection is a collection of useful tools which is self-explanatory.


9.7.3.1.1 Restart all interfaces After clicking the “Restart all interfaces” button, all Ethernet interfaces will immediately be restarted. These are the protocols of the restart process:

Figure 86: WEB GUI: Ethernet restart information

After a stabilization phase of the Ethernet connection you will return to the “Useful ETHERNET utility” page.


9.7.3.1.2 Reset interface configuration A click on the “Reset interface” button will show the following page:

Figure 87: WEB GUI: Ethernet configuration reset

If you wish to stop changing anything, simply click the green “BACK without reset” button and you will be send back to the “Useful ETHERNET utilities”- page. With the radio-buttons you can select which interface will be reset to factory defaults: Choose one of the devices, or select: “all” and press the red “RESET chosen configuration” button. Without another prompt, the files will be restored.

Information

You can also do a single reset to factory defaults, if you use the “default” button followed by “save!” in the configuration pages of each of the three Ethernet configurations.


9.7.3.1.3 Show current routing table To show the current routing table, click on “Show current routing table”. You will get a list of the active routing table of the entire system:

Figure 88: WEB GUI: IP routing table

At this moment, you are not able to change any configurations, because in the most environments, only one default gateway is necessary. Remember that “*” means there’s no gateway set. Otherwise a gateway will be prompted. 9.7.3.1.4 Manual reconnect To manually reconnect your Browser for measurement or maintenance purposes, click the “manual reconnect” button.


9.7.4 Set time and date

There are several alternatives to set the date and time of the internal TMIB2 system and power failure resistant real time clock. One of them is to use the WEB GUI, which gives you two mechanisms:

1. Sync the time of the TMIB2 with the browser time of your PC. 2. Change all values manually.

Figure 89: WEB GUI: Time and date setup site

As you can see in the figure above, your browser will specify the format of date and time (displayed green) in order to fit your local preferences. The time displayed on the TMIB is indeed fixed to the international time standard, so given in GMT. This makes it easier to correspondent with partners in other time zones. 9.7.4.1.1 Sync with PC The easiest way is to sync the time and date with the PC browser time. Just click on “SYNC from PC” and the internal clocks will be update automatically. There will be an information to click on to go back to the time displaying site:


9.7.4.1.2 Sync manually If you wish to type in every single value by your own, you have to open the manual setting mask by clicking on “MANUAL setup”.

You will get a setup mask like this: Simply overwrite the greyed numbers:

dd is the day mm is the month yyyy is the year don’t forget the “/” between day, month and year. After that, fill out the Time in 24h mode (8 pm will be 20:00). If you would leave the mask without changing the clock, “GO BACK”… otherwise click on “Check

and set”.

9.7.5 The TMIB2 config manager

One of the new features of the TMIB2 is the possibility to checkout up to five separate configuration settings, upload, download them from/to your Laptop, create and restore them at a glance. One of the most used settings will be a regular operation setting, a backup of this setting and a setting for maintenance purposes.

Figure 90: WEB GUI: configuration management (empty)


9.7.5.1.1 What will be stored/restored? If you generate a restore point the following settings and configurations will be saved/restored:

Ethernet, CAN and RS485 settings Filter information ID’s (TMIB2 ID, BIU IDs) Output assignments, GPIO assignments Power over Rack config, verbose level of debugging BIU LED mode and configuration No. of connected UMRR Configuration of statistics, objects, etc.

9.7.5.1.2 How the configuration management works There are five slots which can carry up to five configuration sets. Each slot can be given a description in a “Notice” field. This description will not be saved in the configuration package, but remain to explain for what purpose the slot shall be used.


Example

A customer needs two sets of configuration, one for normal operation and the other one is for maintenance. Then it is a good idea to use two restore points called the same in every TMIB2 used in its company:

Figure 91: WEB GUI: config manager - how to use info fields

These slots can be filled and updated with settings which are proven in the lab and have to be used at the crossroads outside. If changes are requested, maintenance worker know where to store the settings and what setting to activate. The name of the setting in the WEB GUI will be the timestamp of the last access. So if a file have been uploaded this time and date will be shown as the name. If a timestamp is generated, this time will be used, and so on. The name of the download file will be: configuration0.tgz through configuration4.tgz (Numbers are the number of the slot stored.) You can rename the file after download for better organisation, that do not affect the upload capability. 9.7.5.1.3 EXPERT TIP: Manual manipulation of settings If you have downloaded the settings, you see that they are contained into a “tar” package, which easily can be un-packed (untar). The famous “7-zip” program (also available and running under win7 or win10) will do the job fine. After this, you see a directory named: “configs”. Please note: Do not rename any file: in case of a corrupt setting the TMIB2 functionality may go back to default settings and not use your modification.


Take a look into the folder, you will see the configuration files:

Figure 92: Content of config file container

For an exact handling of how to make your own changes, please contact smartmicro. We will offer a workshop or a hand-out which explain the details for this expert usage. The use case of this feature is to give experts the possibility to adapt low layer settings to very special environments. The files contain self explained entries which easily can be modified and give you the possibility to make your changes direct, without TMConfigurator. All you need is an unpack programm (7-ZIP), a browser and a test editor like wordpad. Example: You wish to change the RS485 settings in order to use a third party product which use different connecticity settings. Open “RS485_sensor.conf”:

baud_rate: 4 Options are (0)9600 (1)19200 (2)38400 (3)57600 (4)115200 (5)230400 (6)460800 (7)500000 (8)576000 (9)921600 (10)1000000 interface: 1 Options are (0)MOXA (1)SMS_Transport

A look into the datasheet of the 3d party sensor show: Use a speed of 57600 baud with a common MOXA interface. Simply change “baud_rate” setting from “4” to “3” and “interface” from “1” to “0”. Save the file and the work is done (on the communication layer).


9.7.5.1.4 CREATE a restore point By clicking on the “GENERATE” button you create a restore point. This will take a few seconds until the data is packed. If you select a non-empty restore point, you will be asked if you like to overwrite its content. After successful generation you have to click a button to refresh the page:

Figure 93: WEB GUI: Config manager- finish rescue point generation

After this the date and time will characterize the new restore point and new feature-buttons will appear:

9.7.5.1.5 RESTORE a restore point If you like to reactivate the settings of a restore point, simply click on the “RESTORE” button. You will be asked, if you really want to overwrite the current settings:

Figure 94: WEB GUI: Config manager - overwrite dialog

Yes, we want to use the stored settings, so click: OK.


After successful restoration you will be advised to reboot the TMIB to make changes work:

Figure 95: WEB GUI: Config manager - reboot to use new config

Please press “Reboot now”.

ATTENTION

If you use the TMConfigurator program, please “LOAD” the restored settings from the TMIB2 after you have restored a configuration. Only if you load the TMIB2 settings bot TMIB2 and TMConfigurator will be synchronized.

9.7.6 “DOWNLOAD” a restore point

To download a restore point in order to archive it on your PC, just press the “DONWLOAD” button and follow the guided process (this depends on how the download process is configured in your browser).


9.7.6.1.1 “UPLOAD” a restore point If you wish to upload a restore point from your PC into a restore point of the TMIB, please click on the “UPLOAD” button of the slot. The following mask will be shown:

Figure 96: WEB GUI: config manager - upload dialog

First choose a file, then upload it into the restore point. (At the pictore, uploading into restore “1” is shown). If do not want to overwrite the chosen slot, please click “CANCEL”.

Attention

After uploading a configuration into a slot, this slot is NOT automatically activated. You have to subsequently click “RESTORE” at the main mask of the configuration manager. Because it is possible to restore a whole configuration set at once and after loading those sets you have to decide what configuration you would like to activate. 9.7.6.1.2 One line “Notice” You can give a short description of the “SLOT” (Meaning: The slot, not the file itself. So after uploading a file the notice will remain the same like before.) 9.7.6.1.3 “HELP” me! If you need some help, feel free to press the “HELP” button.


9.7.7 Factory reset

After a click on “Factory reset” you will access the following mask:

Figure 97: WEB GUI: Factory reset main dialog

A lot of warnings and red security advises will guide you through the process.

ATTENTION

The factory default reset will set back the device’s IP address to standard. Write down that IP address to access the WEB-GUI after factory default reset. All RESTORE POINTS of the configuration manager, logs etc. will be lost! Download them to your PC if you wish to use them again. To proceed with resetting to factory defaults, click on the red long button under “Please click:” … and again:

Figure 98: WEB GUI – factory default reset confirmation


Last chance to go out without data loss: Click on green „GO BACK“ button. If you are really sure you want the cleanup: Press the red “DO the final RESET now” button. After cleanup the TMIB2 will be restartet automatically and the default values will be set.

9.7.8 Reboot the TMIB2

After a click on the “reboot” button you will be asked once, if you really want to do this:

Figure 99: WEB GUI - confirmation of reset

Press “OK” to reset, or “CANCEL” to cancel the reset.


9.8 Debugging: The logfile mechanism of the TMIB2

With the new TMIB2 comes a new logging and information system: The TMIB2 has only one logfile in which everything will be logged in chronological order. So it will know, if a “Reboot” is caused by a leak of memory, a driver crash or corrupt data. You can take a quick look into this global logfile if you click “Logfile” in the category “Debug and Update” of the WEB GUI.

INFORMATION

You can specify the “depth” of logging by setting the “loglevel” explained in chapter 9.7.1 of this manual.


9.8.1 Actions

Figure 100: WEB GUI - Logfile download dialog

In this first version of logfile handler there are only three buttons, which represents three actions you can choose:


1) Go Back to your last called WEB GUI site,

2) Download the Logfile to your PC or

3) Empty the logfile.

9.8.2 Download the Logfile

Depending on the settings of your browser a well-known Download dialog will guide you through the download process. The browser may be configured to “quick download” files, then please take a look into your “Downloads” directory of your PC to find the downloaded files.

9.8.3 Clean the log

If you press the “clean” button, the logfile will be emptied without any further query. (Depending on your browser settings, this button will be reached by scrolling down the page using the right handed slider in your browser window.)

ATTENTION

If you click “clean” your log will be cleaned immediately without any further request.


9.9 Updating the TMIB2 via WEB-GUI

Please take a look at chapter 10: Firmware update.

9.10 Sensor Mapping

On only one web page you can view… … which sensor is connected to which port … the serial numbers of connected sensors … the type of the sensors … the current flowing to each sensor (if powered via TMIB) and a useful “level meter”

showing you low, high or too high power consumption. (short circuit debug, etc.) … if there are any problems (power cut off, permanent reboot, etc.) … the connection state of each sensor (useful for debugging) … an overview of TMIB power consumption and if the TMIB powered by Rack or external

power supply. … input Voltage of TMIBs power supply.

You can also turn on/off the power of each sensor which is powered via TMIB2.

Figure 101: Sensor Mapping Overview


9.10.1 Sensor Connection Window

[V2] Figure 102: Sensor Connections Window

Power Control You can switch off or on the Power by simply clicking the switch beneath the sensor you wish to switch off or on. The power is on if the knob is in right position an off if it is on the left side. Also, the background of the switch will turn to “red” if the power is off, or “green” if power is on. Remember: You can only control sensors which are powered over the front ports of the TMIB2.

Representation of connected sensors All connected sensors are displayed in this window with their serial numbers and connection type (RS485, Ethernet, CAN). If they are connected via RS485 direct to the front port of the TMIB2, you can easily see on which one, because this connection type is used for a Point-to-Point connection in this case. (Follow the orange arrows). If the sensors are connected over Ethernet, they will be listed on the right side of the window, just follow the green arrow. Sensors listed yellow in the lower third of the window are


connected via CAN Bus. (This option is deprecated). The small markers which shows the serial number in the Figure… are called “ribbons”; They are multifunctional. Look at chapter 9.10.2

9.10.2 Sensor Detail Box

Figure 103: Sensor Detail Box

All connected sensors will be listed in the “Sensor Details Box”. The color of its header will lead to its connection type and this type and e.g. the port will be shown, too. Under the header the detail information of the sensor will be shown (in sequence): If the sensor has booted, the TMIB2 knows its serial and it will be displayed. If not, the note “booting…” is displayed. In case of an error, you will be informed about the cause. The “Current” entry shows you the actual current which is flowing into the power line of the sensor connection if this if powered over the front panels of the TMIB. There is a “PWR supply load” indicator which guides you about the health of the TMIB used as a power supply for the sensors. Be careful if a high or very high load is recognized: To be sure the connected sensor is working in all environmental conditions, use a stronger, external power supply for this sensor. The sensor type will be displayed if the sensor has booted. The boot-and-error-state will be displayed in the last entry of this field. If a CAN or Ethernet Sensor has been connected, you will be informed about the IP-Address (Ethernet) or Can ID (CAN), too.


Ethernet Sensors If Ethernet attached sensors are connected (and configured correctly), you can see the following information:

Attention…

The TMIB2 is the server for Ethernet sensors. In factory default, it is configured to IP-Address 192.168.11.2 and the sensors will to connect to 192.168.11.1 in factory default state. Attaching Ethernet based sensors, you have to use the TMConfigurator first, before you can connect Ethernet sensors to the TMIB2. [V3] First the sensors want to connect to the TMConfigurator tool, after setting them in to TMIB2 Mode, they are able to connect the TMIB2.


9.10.3 TMIB2 Details Box

Figure 104: TMIB2 Details Box

At this moment, the smartWEB interface is only able to display some information about the Power Supply Unit of the TMIB.

9.10.4 Troubleshooting with the Sensor Mapping Window

Detect Infinite Rebooting

In some rare cases, sensor malfunction may result an infinite rebooting. In the most user software sensors are only shown if they left the bootloader and entered the application. On the “Sensor Mapping” page of the TMIB2 you can easily take care of malfunctions, where the sensor stays in bootloader: If this picture remains for minutes or will be shown repeated in short intervals, it is a good idea to reinstall the sensor firmware, update it or reset its configuration to the factory default values, because there´s something wrong with the main application.

Figure 105: Get knowledge of boot processes


Over Current Protection There are many reasons why too much current flow will cause the output stage of a port to cut off the power supply of a sensor. The most common reason is surely a short circuit.

Figure 106: Over current CUT OFF

Connected, but not powered? Even the TMIB2 has no chance to detect a connected, but not powered sensor. The sensor will not send any data and when there´s no flowing current to be detected, you see the following picture:

Figure 107: Not connected sensors

So if you are sure the sensor have been wired and you see the picture above, take care about broken cables, loose connections and so on. Please refer to chapter 1.1 to find out how to power sensors over front panels or separate power supplies. Again: Those cases cannot be detected and are shown as sensors are not connected.


Simple Power Supply Health Monitoring In the “Sensor Details” Box you can see how much current will flow over the belonging port:

Figure 108: Current Monitoring of each sensor (port)

PWR supply load index Behavior Low Large power reserves, everything is fine. Raised There is no problem, but also not much reserves. Heavy! The TMIB2 Power Supply of the port is on the edge to fail Much too high! Current beyond specifications. Over current protection is at

the edge of cutting off.

Protection CUT OFF! The Hardware Shortcut-Prevention have CUT OFF the power supply.


TIP

If you would like to take care about the total power consumption of the TMIB2 (and may be connected sensors), you have to look at the “TMIB2 Details Box”:

Figure 109: Current monitoring of the whole device

The power load of the TMIB2 in the cabinet (Rack) will be displayed as “Current obtain from rack” and in this case, the TMIB2 is powered completely over a separate supply without loading the rack.

Attention!

To reset the hardware shortcut prevention (“Protection CUT OFF!”) you have to reboot the TMIB2.


10 Firmware and Updating

Another new feature of the TMIB2 is the new, all-in-one update mechanism over the WEB GUI.

10.1 Content and description of the TMIB Update Image (TUI)

The TMIB Update Image (TUI) is an encrypted and signed container, which is compressed for better handling on the customer side. The all-in-one image has a size of less than 30 MByte.

10.2 Where to get such a TMIB2 Update Image?

Every time a new release TMIB2 firmware have been released, a TUI will be presented on the “DOWNLOAD” section of the smartmicro homepage.

10.3 Versioning

Every TUI has a unique identity which is published in several ways: You can take a look to the homepage of your TMIB2 to see which Version has been installed:

Figure 110: WEB GUI - firmware ID

The firmware release ID characterizes the “version” of the firmware and is generated automatically during the build process. It’s a matter of quality that we can reconstruct the detailed processing of the firmware in every detail and all we need therefore is this number. On the other hand, the filename contains this ID, too: tmib_673.img To be sure, this image can be used to update a TMIB and is not corrupted during download, we offer the md5 checksum of the image, too: tmib_673.md5. Size, signing and integrity checks will secure the updating process as well. Last not least, you can switch back to the last installed firmware, because there is a second partition on which the firmware be installed alternatively.


10.4 Firmware components

The TMIB2 has two processors in use, which control its behavior:

1. A SDLC controller (ATXMega design) 2. An MAIN application processor (ARM design with embedded Linux OS)

10.4.1 The SDLC Subsystem

After powering up, the bootloader of the SDLC controller will immediately check the integrity of the controller firmware and boot. If there is any doubt in functionality of the SDLC firmware, the will controller stay in bootloader mode until the Application of the Main Application processor is up. Then an automatic update will repair the SDLC functionality. This will take less than one minute to complete the process.

10.4.2 The Main Application System

After power on the Main Application processor will boot in three steps: 1. Setting up the hardware 2. Decide which firmware to boot and check hardware 3. Boot the updatable firmware

INFORMATION

To store the firmware, we use two partitions which are identical in size and both are bootable. We have a bootmaker to control which of these two partitions will boot. Usually it’s the one with the latest, or just installed firmware. But in some cases, manual “fall backs” are needed, so we have the build in the possibility of user decided boot. We call this “boot management”. A boot until network activity of the TMIB2 will be done in less than 20 seconds. The application will be up in approx. 8 seconds after power up. However, SDLC will be serviced in less than 4 seconds after power up.


10.5 STEP by STEP: How to update the TMIB2

To update your TMIB2, you have to follow this workflow: 1. Get a firmware image and a checksum file. 2. OPTIONAL: proof if download is correct by comparing MD5 sum of downloaded file and provided

checksum. (Mismatch repeat image purchase) 3. Upload and start automatic update process. 4. RECOMMENDED: second reboot

10.5.1 Purchase a firmware image

There are two ways to obtain a firmware image and a checksum file: 1. Download a released image and md5 from our homepage. 2. Ask our customer support and get one via email.

10.5.1.1.1 Download from Website Go to: http://www.smartmicro.de/traffic-radar/downloads/ Under “Software” you will find what you are looking for. 10.5.1.1.2 Email If you wish to get a firmware and checksum file over email, you have to be able to receive emails with attachments approx. 30 MByte of size. This way is reserved for special features only. If you have to use an individualized firmware, the mailing will be a good way to purchase your firmware image without using a “public” way. Otherwise be advised to download a regular published and tested file from our website.

10.5.2 How to check integrity of a firmware image

Together with each TMIB2 firmware we provide a MD5 checksum. If you are working under Windows and wish to generate a MD5 sum for safety compares, please take a look at the following information:

https://support.microsoft.com/de-de/kb/841290


10.5.3 Upload and automatic Firmware installation

We call the image you can purchase an “all-in-one” update image, because we contain the firmware of each involved subsystem into this single file. If there’s an update of the SDLC subsystem necessary, it will be done automatically. So, each firmware version will contain a harmonious software of each subsystem.


10.6 Boot management

How to call the “Boot manager”?

Simply click: FW-Update and lookout for the small, orange button at the bottom of the

dialog:

Now you can see which partition carries which version of firmware, what is the booted partition and you can boot into the other partition or do not change anything:

Figure 112: WEB GUI - boot manager dialog

Figure 111: WEB GUI - step into the boot manager


INFORMATION

If you see a very long number of 10 digits as a FW-Version, this is a “not regular released” firmware for testing purposes or special use only.

10.6.1 From which partition did the TMIB2 boot?

Take a look at the homepage of the TMIB2:

Figure 113: Examine which partition booted

In this case the first partition is the selected boot device. In case of an firmware update, the second partition will be overwritten.


10.7 Show TMIB2 firmware ID in TMConfigurator

Please prepare your computer and the TMIB2 as described in sections 7.1, until you made the IP settings (section 7.5.3). The next steps take for granted that you can communicate via Ethernet to the TMIB2. Determine the firmware version programmed to your TMIB2. You can read the firmware version from an active connection to that TMIB2 using TMConfigurator software:

Figure 114: open status view

Figure 115: Read firmware ID

Firmware_Version: e.g. “0,678” means a firmware with ID 678 is installed. SW_Version_ATX: This is the firmware version of installed SDLC Software (ATX Coprocessor.) Product_Number: e.g. 871 this is the serial number of the device as a decimal value Lifetime: This is the time in action since first usage Temperature: Here you can read the current temperature of your cabinet (sensor on TMIB2

board).


10.7.1 Firmware Update using TMConfigurator

ATTENTION

We do not longer support updating the TMIB2 firmware over TMConfigurator. Go to chapter 10 on how to update the TMIB2 firmware using the WEB GUI.


11 Remote connections to the TMIB2 through the WWW

It is possible to use the TMIB2 with its Ethernet connections in remote environments.

Please note:

The TMIB2 is NOT designed to be connected to the WWW directly. The usage of a protecting Gateway (VPN featured) is strongly recommended.

11.1 Infrastructure for safety TMIB2 remote installations

In the world “wild” web your data is permanently under attack. To make them as safe as possible, you have to communicate over high security, strong encrypted channels. This is called “Virtual Private Network”, short: VPN. The gateways you want to use have the following two features:

1. VPN tunneling: SSL-VPN (Gateway-to-Gateway high security tunneling) 2. SPI – Stateful Packet Inspection Firewall (DPI: Deep packet inspection)

There are a hand full of producers which are able to the job as well as needed:

Securepoint, with its “black dwarf” VPN gateway. Cisco for bigger environments or spread components: Based on ASA5505 router Otherwise: Cisco Small Business, e.g. the Cisco SB RV042 may be a good solution.

Never be careless by leaving your infrastructure undefended. A good doorkeeper is a “must have” in remote accessible solutions. Never use WLAN (WiFi) Gateways without the features of strong secured connections.

WORLD „WILD“ WEB

Ethernet Switch Ethernet Switch

TMIB2 TMConfigurator PC

Figure 116: WWW gateway solution


12 Shelf mount version

The shelf mount TMIB2 comes with the TMIB_AB V2 card and an enclosure:

Figure 117: TMIB2 shelf mounted


All signals and features of the rack mount version are available for the shelf mount version also. The “shelf mount” enclosure provides access to the TMIB_AB backplane connector. For the signal assignments to pins please refer to section 3). The shelf mount version comes with an approx. 1ft power cord with banana plugs. All connections, esp. the relay channels 5-16, can be accessed via the front panel, see chapter 5 Connector and pin assignments are detailed out in section 13.3.

Figure 118: Access Open Collector Outputs 1..16

Access to Open Collector Outputs 1-4 is granted via the (rack) backplane connector of the sheltered TMIB_AB unit, too.


INFORMATION

Open Collector outputs 1..4 are also provided by TMIB_AB V2 itself and can be connected at the rear of the shelf mount connector. For further information, please take a look to the chapter 13.


13 Connections

Figure 119: Connectors on the front side

External Power supply connector chapter 13.1

RS485 (CAN) Sensor connector chapter 13.2

Ethernet connector chapter 13.3

USB host connector chapter 13.8

External relays output connector chapter 13.4

SDLC (NEMA TS2) connector chapter13.7


+ VCC

GND

13.1 External power supply connector

Figure 120: External power connector

WHEN TO USE EXTERNAL POWER?

You can use either rack power supply or external power supply. You can use external power supply whenever it is useful for you. You have to use external power supply, if you wish to power Sensors over the RJ45 sensor connectors, without using an own power supply for each sensor (Let TMIBV2 power all sensors instead of powering each sensor with a stand-alone power supply).


13.2 RS485 / CAN Sensor connector

Use a RJ-45 connector.

Figure 121: Pinout of sensor CAN/RS485/POWER connector (x4)

13.2.1.1.1 Layout (RS485 full-duplex) This layout is relevant if you ordered UMRR-11 or UMRR-0C sensors.

Table 5: Pinout sensor connectors RJ45

(Coloring of the wires: In Figure 121 the cable use an EIA 568A coloring. If your cable is configured in EIA568B scheme, please take a look in the table above to assign color to signal correct.)

RJ-45 pin

Signal description JBOX pin

Wire color EIA/TIA 568B

(World)

Wire color EIA/TIA 568A

(Europe) 1 Sensor RS485 RX Low 5 White/orange White-green 2 Sensor RS485 RX High 6 Orange green 3 CAN_H 11 White/green White-orange 4 SENSOR_VCC 8 Blue Blue 5 SENSOR_GND 7 White/blue White-blue 6 CAN_L 12 Green Orange 7 Sensor RS485 TX High 4 White-brown White-brown 8 Sensor RS485 TX Low 3 Brown Brown


13.2.1.1.2 Connection Diagram RJ-45 & JBOX-02 (UMRR-0C, UMRR-11) Full-Duplex, RS-485


13.2.1.1.3 Connection Diagram RJ-45 & J-BOX-01 (UMRR-0C, UMRR-11) Full-Duplex, RS-485


13.3 TMIB_AB Ethernet connector

Pin Signal 10/100 Gigabit 1 TX + DA+ 2 TX - DA- 3 RX+ DB+ 4 DC+ 5 DC- 6 RX- DB- 7 DD+ 8 DD-

Figure 122: Ethernet pinning


(Coloring of the wires: Please check assignments in pre-configured plugs)


13.4 Layout cable TMIB_AB – TMIB_C

Use a RJ50 connector.

Figure 123: TMIB_AB expansion port 1..4 connection to TMIB_C

To connect up to four TMIB_C with the expansion ports of the TMIB_AB you need a simple 1:1 wired 10p10c cable (sometimes known as RJ50). You can purchase a cable called:

CABLE-0D0000

The pins are connected like shown in the following table:

PIN Signal 1 Channel X Out 2 Channel X+1 Out 3 Channel X+2 Out 4 Channel X+3 Out 5 Common (GND) 6 NC 7 Status X Out 8 Status X+1 Out 9 Status X+2 Out

10 Status X+3 Out

Table 6: Pinning of the expansion ports

ATTENTION

For high current applications, you need to install a downstream power unit. The flow resistant is low enough to capture full NEMA compliance, but it is greater than the resistant of a real relay.

1

10


13.5 Backplane Connector of TMIB_AB V2

The Backplane Connector is located at the rear end of the shelf mount TMIB. The pin assignments are a 1:1 copy of the NEMA TS1 / TS2 backplane multipoint socket. An example connector to match the Backplane pins is part # 307-044-500-202 from EDAC Inc.; equipped with 3 polarizing keys part # 306-240-318.

Figure 124: Pinout TMIB_AB V2 rear connector


Pin Signal description Signal description Pin A Logic Ground N.C. 1 B Detector Unit DC Supply N.C. 2 C External Reset N.C. 3 D N.C. N.C. 4 E N.C. N.C. 5 F Channel 1 Output (+) N.C. 6 H Channel 1 Output (-) Channel 1 Status Output 7 J N.C. N.C. 8 K N.C. N.C. 9 L Chassis Ground N.C. 10 M N.C. N.C. 11 N N.C. N.C. 12 P N.C. N.C. 13 R N.C. N.C. 14 S Channel 3 Output (+) N.C. 15 T Channel 3 Output (-) Channel 3 Status Output 16 U N.C. N.C. 17 V N.C. N.C. 18 W Channel 2 Output (+) N.C. 19 X Channel 2 Output (-) Channel 2 Status Output 20 Y Channel 4 Output (+) N.C. 21 Z Channel 4 Output (-) Channel 4 Status Output 22

Backplane Connector Pin Assignments


Figure 125: Rear connection of TMIB_C V2

13.6 Backplane connector of the TMIB_C V2 expansion board

(Orientation: Watch out for the “gaps” of the connector)


13.7 SDLC port (NEMA TS2 Port 1 connector)

Figure 126: Port 1 SDLC connector

PIN Signal 1 RX_P 9 RX_N 2 GND

10 n.c. 3 CLK_RX_P

11 CLK_RX_N 4 GND

12 EARTH (shield) 5 TX_P

13 TX_N 6 GND

14 n.c. 7 CLK_TX_P

15 CLK_TX_N 8 GND


13.8 USB Host

Figure 127: USB connector

ATTENTION

The power is limited to 2.5 Watt as mentioned in USB standard. (5V up to 500 mA). It is not possible to use USB-Hubs to expand this port, because it is based on the USB-OTG standard.

PIN Signal 1 +5V VCC 2 DATA - 3 DATA + 4 GND

4

1


14 Important Legal Disclaimer Notice All Product, Product specifications and data in this project documentation are subject to change without notice to improve reliability, function,

design or otherwise.

The statements, technical information and recommendations contained herein are believed to be accurate as of the date hereof. Smartmicro

disclaims any and all liability for any errors, inaccuracies or incompleteness contained in this datasheet or in any other disclosure relating to

the Product.

To the extent permitted by applicable law, Smartmicro disclaims (i) any and all liability arising out of the application or use of the Product or

the data contained herein, (ii) any and all liability of damages exceeding direct damages, including - without limitation – indirect, consequential

or incidental damages, and (iii) any and all implied warranties, including warranties of suitability of the Product for a particular purpose.

Statements regarding the suitability of Products for certain types of applications are based on Smartmicro’ knowledge of typical requirements

that are often placed on Smartmicro’ Products in generic/general applications. Such statements are, however, not binding statements about

the suitability of Products for a particular/specific application. It is the customer/user’s own responsibility to validate that the Product with the

specifications described herein is suitable for use in its particular/specific application. Parameters and performance of the Products may due

to particular/specific applications and due to particular/specific surroundings deviate from the statements made herein. Therefore, it is

important that customer/user has thoroughly tested the Products and has understood the performance and the limitations of the Products

before installing the Products for the final applications or before commercialization. Although Products are well optimized to be used for the

intended applications stated herein, it must also be understood by the customer/user that the detection probability may not be 100 % and the

false alarm rate may not be zero.

The information provided herein, relates only to the specific Product designated and may not be applicable when such Product is used in

combination with other materials or in any process not defined herein. All operating parameters, including typical parameters, must be validated

for each customer application by the customer/user’s technical experts. Customers using or selling Smartmicro products not expressly

indicated for use in such applications do so at their own risk.

This Product specification or data sheet does not expand or otherwise modify Smartmicro terms and conditions of purchase, including but not

limited to the warranty expressed therein.

Except as expressly indicated in writing by Smartmicro, the Products are not designed for use in medical, life-saving, or life-sustaining

applications or for any other application in which the failure of the Product could result in personal injury or death.

No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document or by any conduct of

Smartmicro Product names and markings noted herein may be trademarks of their respective owners.

Please note that the application of the Product may be subject to standards or other regulations that may vary from country to country.

Smartmicro does not guarantee that the use of Products in the applications described herein will comply with such regulations in any country.

It is the customer/user’s responsibility to ensure that the use and incorporation of Products complies with the regulatory requirements of their

markets.

If any provision of this Disclaimer is, or is found to be, void or unenforceable under applicable law, that will not affect the validity or enforceability

of the other provisions of this Disclaimer.


15 MIT license of Yocto basis system

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

This license describes the licensing situation of the pre compiled binaries and the root of the linux basis system, which have been modified. The modifications of the basis system left it’s privacy as mentioned by the MIT license and will be provided together with the sources of the whole project called “basis” system on a media (“GPL DVD”) charging only the cost, which really occur. Unaffected by the copyleft licensing the TMIB2 application stays in strong copyright © 2016 of smartmicro (only using linked stuff in userland of the free operating system): Any unauthorized copying and/or modification of the provided Application running on the TMIB2 and it’s free operating system will stay prohibited according to the LGPL v3 licensing system of GNU. Contraventions will be prosecuted under civil and criminal law. (For further information, please refer to the GNU LGPLv3 license of the next chapter.)


16 GNU LGPL License V3

GNU LESSER GENERAL PUBLIC LICENSE

Version 3, 29 June 2007

Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below.

0. Additional Definitions.

As used herein, “this License” refers to version 3 of the GNU Lesser General Public License, and the “GNU GPL” refers to version 3 of the GNU General Public License.

“The Library” refers to a covered work governed by this License, other than an Application or a Combined Work as defined below.

An “Application” is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library.

A “Combined Work” is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined Work was made is also called the “Linked Version”.

The “Minimal Corresponding Source” for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for


portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version.

The “Corresponding Application Code” for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work.

1. Exception to Section 3 of the GNU GPL.

You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL.

2. Conveying Modified Versions.

If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version:

a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or

b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy.

3. Object Code Incorporating Material from Library Header Files.

The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following:

a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License.


b) Accompany the object code with a copy of the GNU GPL and this license document.

4. Combined Works.

You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following:

a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License.

b) Accompany the Combined Work with a copy of the GNU GPL and this license document.

c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document.

d) Do one of the following:

0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.

1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version.

e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.)

5. Combined Libraries.


You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following:

a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License.

b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.

6. Revised Versions of the GNU Lesser General Public License.

The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation.

If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.


17 Contact

Address: smart microwave sensors GmbH In den Waashainen 1 38108 Braunschweig Germany Phone / Fax numbers: Phone: +49-531-39023-0 Fax: +49-531-39023-599 Web / Email address: Web: www.smartmicro.de www.smartmicrogroup.com Email: [email protected]