CEOS RD022 TIRTL V3 Firmware User Manual v2.9
CEOS RD022 TIRTL V3 Firmware User Manual v2.9
Version: 2.9
References
Document Number Description
Revision History
Revision Description Approval Date
2.0 Updated for latest 3.2.9 UI layout, various minor changes Greg Robinson 25 Nov 14
2.2 Included Login description, new L2TP functionality, Greg Robinson 15 Dec 14
clarification of ethernet availability on Rev E Hardware.
Addition of further class scheme, hv scheme and toll
scheme details.
2.8 Additions to vehicle log fields for 3.17.0 release David Cureton 15 May 17
Correction to tag/sequence fields
2.9 Update overheight CSV output definitions David Cureton 8 Oct 2018
1.1. Disclaimer
The information presented in this document is believed to be accurate and is subject to change without notice.
No liability is accepted by CEOS Industrial Pty Ltd for any use of this document. Acquisition of this document
does not convey nor imply a right or licence to TIRTL.
WARNING
Warning boxes display very important information that you must read.
NOTE
General information notes, advice and links will be displayed in these boxes.
TIP
Tip boxes will be used to tell you about tips or tricks that might save time or effort.
When you are instructed to click a button, it will be shown like this: Button
Clickable links on the page or label text will be shown in bold: Add New Forum
This shows when you could or should enter text: Enter this text
Menu hierarchies will be shown like this: Top menu -> Sub menu
URLs will be shown like this: http://www.example.com
This shows a reference to another document: Site Selection Manual
2.1. Login
You access the TIRTL user interface using a standard web browser such as Internet Explorer or Chrome.
To access the TIRTL user interface you must first establish network connectivity from your PC to the TIRTL
receiver. This network connection can be via the serial interface, ethernet interface or mobile data interface.
The ethernet port and/or mobile data interface require configuration before they can be used. Initial
configuration of the TIRTL must be carried out via the serial interface which will allow you to configure these
other communication ports.
All configuration of the TIRTL and downloading/deletion of log files is conducted via the TIRTL web based user
interface.
NOTE
Initial configuration of the TIRTL must be done via the serial interface. This will allow you to configure
the other network interfaces of the TIRTL.
Connect to the TIRTL’s IP address in your browser. The Authentication Required popup will be displayed to
enter the User Name and Password.
User Allows status, traffic monitoring, configuration changes and data downloading
and deletion.
View Allows status, traffic monitoring, data downloading, but does not allow
configuration changes nor data deletion.
The General Status page presents information about the TIRTL and its sub-systems such as the system,
alarms, mobile, GPS, time, serial and ethernet.
The Traffic status page presents the real time traffic as detected by the TIRTL.
The Height status page is used during TIRTL installation and troubleshooting to determine how the TIRTL is
installed in relation to the road surface.
The Tilt status page is used during TIRTL installation and troubleshooting to determine how the TIRTL is
installed in relation to the road surface.
The Beam Levels status page presents (in real time) the current infra-red beam levels to assist in alignment
and troubleshooting of TIRTL installations.
The General Status section shows the current state of the TIRTL and the status of the TIRTL alarms.
Status
Time Current TIRTL system time (includes date, time and timezone offset).
Beam Levels Difference between the actual level and the expected level of the optical signal
received by the TIRTL receiver from the transmitter.
The expected level is dependent upon the distance between the TIRTL
transmitter and receiver and is calculated by the TIRTL based on the width of the
regions as configured in the “Installation” configuration page.
The beam level values will be zero for a correctly installed and configured TIRTL.
Negative values indicate the TIRTL is receiving less than the expected optical
signal, possibly due to dust/dirt in the optical path or an incorrectly configured
region widths or misalignment of the TIRTL transmitter or receiver or both.
Positive values indicate that more optical signal than expected in being received,
probably because of an incorrectly configured regions widths.
Supply Voltage Current power supply voltage as measured by the TIRTL receiver.
Log Space Amount of storage space remaining for the storage of TIRTL log files.
Uptime Time since the last power down or reboot of the TIRTL receiver hardware.
The alarms section displays the current status of the TIRTL alarms. There are 3 alarms states:
1001 Beam.Degraded One or more beam levels below expectations for a significant
period of time. Alarm activated by beam degradation of 7dB
(warning) or 10dB (critical) for at least 2 hours. TIRTL more
than likely requires cleaning.
1002 Beam.Unbalanced One or more beam levels askew. Alarm activated by beam
degradation of 4.5dB (critical) for at least 2 mins. TIRTL more
than likely has debris, and requires close monitoring of the
situation.
1302 Configuration.Site_Information Site_info tcf parsing and inconsistency errors. Contact your
TIRTL representative for assistance.
1303 Configuration.Other All other tcf parsing and inconsistency errors (except mobile,
GPS, POTS). TIRTL may not be operating correctly. Contact
your TIRTL representative for assistance.
1403 Power.Receiver.Internal_Battery Internal battery voltage outside limits set by user or in dead-
zone. (Alarm unused on Rev D hardware onwards).
1404 Power.Receiver.External_Supply External supply voltage outside limits set by user. Check the
power supply.
1406 Power.Transmitter.External_Supply External supply voltage outside limits set by user. Check the
power supply.
1902 Time.Discontinuity Discrete set time jump occurred, meaning that time
synchronisation could not be maintained and a discrete time
offset had to be inserted.
1904 Time.NetworkServerConnectivity Raised if the time synchronisation is either not synched to any
network server, or three consecutive failed network time reads
occur. Investigate the network issues.
2301 Internal_Error.RTC_Battery Internal battery used to maintain system time when unit is
unpowered has a low voltage. Contact your TIRTL
representative for assistance.
3.1.3 Mobile
Status Operational status of the mobile communication module installed in the TIRTL
receiver.
Signal Strength Signal strength as detected by the mobile module. The bar graph graphically
indicates the signal strength (out of 5 bars).
Network Type of mobile service that the mobile module is utilising – i.e. 2G, 3G.
Mobile Module Model number of the mobile module installed in the TIRTL receiver.
LAC Code identifying the 3G location area (group of base stations communicating to
receiver).
Cell ID Identity of the base transceiver station communicating with the TIRTL.
IMEI Identity of the Mobile Station Equipment – i.e. the 3G module within the TIRTL.
ICCID Identity of the Integrated Circuit Card – i.e. the sim card within the TIRTL.
PPP Status Current status of the mobile packet data link for remote IP communications.
3.1.4 GPS
Coordinates GPS latitude/longitude coordinates of the site as measured by the GPS receiver.
Signal Quality List of satellites being detected by the GPS receiver. Each detected satellite is
listed along with the satellite number, CNR (Carrier to Noise ratio), and a signal
strength bar graph. The bar graph is colour coded to indicate its signal strength
status (green=good).
3.1.5 Time
Synchronisation Displays the synchronisation status of the GPS receiver. Synchronisation Status
Status fields are detailed below.
Daylight Savings Describes the previous and next scheduled /daylight saving changes.
Synchronisation Description
Status Field
Stratum How many hops the source is from a primary time reference.
Poll Period The time period between polling reference for time updates.
Delay The round trip travel time of the query when polling the time source.
Offset The time difference (secs) between the TIRTL current time and the time source.
Dispersion The variation in the time difference between the TIRTL current time and the time
source.
3.1.6 Serial
3.1.7 Ethernet
Link Details Description of the ethernet link speed and communication protocols.
WARNING
3.1.8 L2TP
3.1.9 Overheight
3.1.10 Traffic
The Traffic section displays the details of the traffic as detected by the TIRTL in real time. The Last Updated:
field indicates that last time that the traffic display was refreshed. The beam events generated by the traffic
are presented in the bottom portion of the screen.
Class Name Name of the class in which the vehicle was classified.
Extended Data Further detected axle and wheel edge data used for detailed classification
analysis including:
Each axle – [speed (km/h), beam chord width (mm), number of detected edges]
Between axles - axle separation (m)
Selecting “Auto scroll” will cause the window to automatically scroll up as new vehicles or beam events are
detected. Clicking “Clear” clears the list of detected vehicles in the current window. Each time the traffic page
is opened it is cleared (the vehicles are not cached and redisplayed). Opening the traffic page on a separate
browser tab allows continual updating of detected vehicles.
The Beams section displays the details of the beam break and make events of the 4 individual infra-red TIRTL
beams.
Each ‘pulse’ represents a beam make/break event and is analogous to a vehicle axle
passing the beams. Each of the TIRTL’s beams are represented as a separate colour
(green/yellow/red/blue). Vehicles may be travelling in separate lanes, and as such beam
events may overlap.
Examples
Beam events for a typical 2 axle short vehicle passing the TIRTL will look as such:
Beam events for a six axle articulated heavy vehicle (following a short vehicle travelling in another lane) will
look as such:
The Height section presents the height of the optical beams above the road surface as measured by the
TIRTL. Passing traffic is utilised to measure the beam heights, therefore the height graph cannot be generated
without passing traffic.
The black line in the red bar represents the road surface. The black line in the green region represent the ideal
TIRTL beam height above the road. The dots represent the beam heights as measured by the TIRTL. The
TIRTL should be installed such that the dots are in the green region.
The number of groups of dots will depend on the number of lanes that the TIRTL has been configured to
monitor. For example, when the TIRTL is monitoring a 2 lane road, there are 2 groups of dots.
Dark colour dots indicate multiple measurements of height at the same point on the road. This
average height measurement therefore represents the most reliable indications on the display.
Light coloured dots may be ignored.
The “Clear Height Data” button will clear the cached height data the TIRTL has accumulated. After clearing the
height data, the TIRTL will rebuild the height graph based on new vehicle data. Clearing the height data is
recommenced after you have made adjustments to the TIRTL alignment.
The Tilt section presented the “tilt” of the TIRTL optical beams in relation to the road surface. Passing traffic is
utilised to measure the tilt and therefore the TIRTL tilt graph cannot be generated if there is no passing traffic.
The number of groups of dots will depend on the number of lanes that the TIRTL has been configured to
monitor. For example, when the TIRTL is monitoring a 2 lane road, there are 2 groups of dots.
Dark colour dots indicate multiple measurements of height at the same point on the road. This
average height measurement therefore represents the most reliable indications on the display.
Light coloured dots may be ignored.
The “Clear Tilt Data” button will clear the cached tilt data that the TIRTL has accumulated. After clearing the
cached tilt data, the TIRTL will rebuild the tilt graph based on new vehicle data. Clearing the tilt data is
recommenced after you have made adjustments to the TIRTL alignment.
The Beam Levels section shows the level of optical power as received via each of the four channels of the
TIRTL. The beam level graph presents the expected optical beam level as a black horizontal line. The difference
between the current beam level and the expected beam level for each channel is plotted as a black bar in real
time.
The expected beam level is dependent on the distance between the TIRTL transmitter and receiver. The
distance between the TIRTL transmitter and receiver is calculated by the TIRTL with reference to the
“Installation” section of the TIRTL configuration pages.
The alignment of the TIRTL transmitter and receiver with respect to each other will affect the beam levels.
Objects that fully or partially block the beams between the TIRTL units will also affect the current beam levels.
The TIRTLs should be installed so that the current beam levels are as close to the expected level as possible.
Thus you should install and align the TIRTL units so that the black bars are as small as possible.
The four channels, LP, LD, RD, RP referred to in the graph, are the “left parallel”, “left diagonal”, “right
diagonal”, “right parallel” optical beam levels respectively.
The Logs section presents the log files that are currently on the TIRTL and available for download and/or
deletion. The TIRTL has a number of different log file types for TIRTL sub-systems. Enabling or disabling of
specific log file types is achieved via the TIRTL configuration section.
You may download any of the available logs by clicking on the log file you wish to download. Your browser will
download the log file to its download area. You may delete any of the available log files by selecting the log
WARNING
Log files are deleted immediately on pressing the “Delete Selected” button – there is no confirmation.
3.4.1 Installation
The Installation configuration section allows you to configure the TIRTL with the details of the site at which
the TIRTL devices are installed.
NOTE
The top most entry in the list of regions describes the region closest the TIRTL receiver.
Site Name An alphanumerical text identifier for the site that the TIRTL is installed. All logs
generated by the TIRTL will be prefixed with this identifier in this field.
Site Description A longer description of the site that usually includes road name(s) and suburb.
TIRTL Orientation The physical orientation of the TIRTL device as installed on site. The flat surface of
the TIRTL is referred to as the “lid”, therefore “lid down” refers to the flat surface of
the TIRTL being towards the ground.
Use Diagonal Beams Enables the use of the diagonal optical beams. Distances of less than 4m between
the TIRTL transmitter and receiver (in most cases, this is a single lane installation)
requires the diagonal beams to be disabled. With diagonal beams disabled, the
TIRTL will not be able to determine in which lane a passing vehicle traffic was
located.
Transmitter Offset This field is used if the TIRTL beams are not perpendicular to vehicle direction of
travel.
It is used to specify the offset distance of the transmitter in relation to a line draw
across the road from the receiver that is perpendicular to the direction of travel of
passing vehicles. See appendix for further details.
You may disable detection of traffic for a region by turning off the “detect” flag.
Generally detection is disabled for areas that do not carry traffic such as the
medians and verges of the road.
The “Vehicle Detection” configuration page allows you to select the required vehicle detection parameters for
the TIRTL. Selection of the Class scheme, HV scheme and Toll scheme is independent of each other. A TIRTL
must have a Class scheme selected, whereas it is optional to select an HV scheme and Toll scheme.
Regional Profile Allows the vehicle detection routines to be optimised to account for variations
in vehicle types based on region. If there is a specific regional profile for the
TIRTL location then use that setting, otherwise use default.
Class Scheme The vehicles detected by the TIRTL are classified against one of a number of
pre-loaded class schemes for the purpose of describing the type of vehicle. The
class scheme describes the class name and other specifics of each class of
vehicle.
The TIRTL will compare detected vehicles against the selected class scheme for
the purpose of determining a class name and class number.
The class name and class number will be recorded in the TIRTL CSV logs and
asynchronous data interface based on the result of classification in the
“class_name” and “class_number” columns respectively.
Differing jurisdictions name and describe vehicles in different ways. Select a
class scheme from the list of pre-loaded class schemes that is appropriate for
your jurisdiction.
HV Scheme The vehicles detected by the TIRTL are classified against the HV scheme for the
purpose of heavy vehicle classification. The HV scheme describes the class
name and other specifics of heavy vehicles classes.
The TIRTL will compare detected vehicles against the selected HV scheme for
the purpose of determining a HV class name and HV class number.
The class name and class number will be recorded in the TIRTL CSV logs and
asynchronous data interface in the “hv_class_name” and “hv_class_number”
columns respectively.
Select the heavy vehicle class scheme that best suits your requirements.
Toll Scheme The vehicles detected by the TIRTL are classified against the Toll Scheme for
the purpose of identifying different vehicle tolling classes. The toll scheme
describes the class name and other specifics of tolling vehicles classes.
Maximum axle spacing This configuration item specifies the maximum spacing between axles on a
vehicle.
The TIRTL cannot classify a vehicle until it has detected that all axles
associated with that vehicle has passed. Once the last detected axle of a
vehicle has travelled “maximum axle spacing” past the TIRTL, the TIRTL will
consider that there are no further axles for this vehicle and finalises the vehicle
classification.
The default configuration of this setting is 12 meters.
Traffic conditions This configuration item optimises vehicle detection for different traffic
conditions. TIRTL installed at traffic lights should be configured for “Stop Start”
traffic conditions, elsewhere “free flowing” traffic conditions should be used.
The Regional Profile allows optimisation of the vehicle detection and classification routines for local
conditions.
Region Description
The Class Scheme pulldown menu allows selection of a class scheme for the TIRTL to use to classify detected
vehicles.
NorSIKT Custom class scheme developed for Nordic countries (Denmark, Finland,
Iceland, Norway, Sweden)
The HV Scheme pulldown menu allows selection of a heavy vehicle class scheme for the TIRTL to use to
classify detected heavy vehicles.
GVM Australia The heavy vehicle class scheme based upon the Australian Gross Vehicle Mass
standards. See www.nhvr.gov.au for details.
The Toll Scheme pulldown menu allows selection of a tolling class scheme for the TIRTL to use to classify
detected vehicles.
IHMCL The Indian Highways Management Company Limited tolling scheme used in
Indian toll stations.
3.4.3 Serial
Baud Rate Specifies the baud rate of the TIRTL serial port.
TIRTL Address Specifies the IP address of the TIRTL when using PPP.
Remote Address Specifies the IP address of the peer when using PPP.
Auto Login Selects whether to automatically establish a PPP or tirtl_control session via
the serial interface.
PPP Script If “PPP” auto login is enabled, a PPP session will be initiated by the TIRTL
using this PPP CHAT script.
TIRTL Control Script If auto login is enabled, a tirtl_control session is established and the TIRTL
control commands specified in this configuration item are executed.
3.4.4 Modem
This page allows you to configure the PSTN modem of the TIRTL (the PSTN modem is fitted to REV B/C/D
TIRTL hardware). If a modem is not fitted to the TIRTL these settings are ignored.
Country Selects the country applicable for modem. This setting adjusts the country
specific setting of the PSTN modem.
TIRTL Address Specifies the IP address of the TIRTL when using PPP.
Remote Address Specifies the IP address of the peer when using PPP.
3.4.5 Mobile
Open Packet Session Selects whether the modem should establish a packet data session with the
mobile network. If this setting is not enabled, the modem will only attempt to
register with the mobile network.
Credentials Selects which credentials to use to establish the mobile packet data session.
You may choose from the pre-configured TIRTLnet credentials or specify your
own custom set of credentials (APN, username, and password).
Your mobile service provider will be able to assist you as to what credentials
you use.
APN When using custom credentials use this APN for establishing a mobile data
packet session. If required, this is usually provided by the Service Provider.
Username When using custom credentials use this username for establishing a mobile
data packet session. If required, this is usually provided by the Service
Provider.
Password When using custom credentials use this password for establishing a mobile data
packet session. If required, this is usually provided by the Service Provider.
TIRTL Address Use this IP address for the mobile interface when establishing a mobile packet
data session. If required, this is usually provided by the Service Provider.
NOTE
Ensure that a mobile antenna is mounted to the TIRTL receiver to ensure reception.
3.4.6 Ethernet
Enable/disable and configure the ethernet with the specified address/netmask/gateway for TIRTL hardware.
Netmask The netmask of the local subnet that the TIRTL is connected.
Gateway The gateway router for the subnet that the TIRTL is connected.
TIP
You will need to get suitable configuration values for these field from your network administrator.
WARNING
3.4.7 L2TP
This section allows you to configure connectivity with an L2TP access concentrator. This can be used to set
up a tunnel between a TIRTL anda L2TP access concentrator. This is used to allow access to TIRTLs that
cannot be contacted directly via the mobile due to dynamic IP allocation or firewall issues.
WARNING
TIP
Ensure that the routing has been configured such that the TIRTL can connect to the L2TP peer via the
desired interface (serial, ethernet or mobile).
This section allows you select which interface the TIRTL should use as the default route and allows you to
specify additional routes.
Default route Specifies which network interface the TIRTL should use if the destination IP
address is neither a directly connected local network nor falls within the
address ranges any routes configured in the “Routes” section.
Routes Specifies which network interface to route packets that comprise the
configured the address/ netmask.
You can specify as many additional routes as required.
3.4.9 GPS
Selects whether the TIRTL GPS module in enabled. GPS must be enabled for the TIRTL to determine the
current time and position.
NOTE
Ensure that a GPS antenna is mounted to the TIRTL receiver to ensure reception.
TIRTL logs are periodic and the period may be configured as 1 day, 1 hour, 15 minutes, 5 minutes or 1 minute
periods.
CSV Log Period TIRTL Logs are periodic with the period configurable to be one of the following
options: 1 day, 1 hour, 15 minute, 5 minute, or 1 minute periods.
Select the CSV log period that best matches your application.
The 1 day period starts at midnight and ends at midnight.
The 1 hour period starts at the beginning of each hour and runs for a
duration of 1 hour.
The 15 minute period starts at each 15 minute interval during the hour.
For example 12:00, 12:15, 12:45 and runs for a duration of 15 minutes.
The 5 minute periods start at each 5 minute interval during the hour. For
example 12:00, 12:05 … 12:55, 13:00 and runs for a duration of 5
minutes.
The 1 minute period starts at the beginning of each minute and runs for a
duration of 1 minute.
Compress CSV logs Enabling compression enables more efficient storage of logs on the TIRTL and
faster transfer during download. CSV logs are compressed once the CSV log
period has completed.
You may configure which time zone the TIRTL uses and how the TIRTL synchronises its system clock. All times
presented by the TIRTL are local time based on this time zone setting.
TIP
Version 2 TIRTLs used the UTC time zone and this was not configurable. Set the time zone to “UTC” for
operation equivalent to version 2 firmware.
Timezone Specifies the time zone from the available list of time zones.
Use GPS Enables the use of GPS to synchronise the TIRTL system clock.
Use NTP Enables the use of Network Time Protocol (NTP) to synchronise the TIRTL
system clock.
NTP Servers Specifies a list of NTP server IP addresses that the TIRTL can use as a time
reference to synchronise the TIRTL system clock.
Time Zone
All printed times in the TIRTL user interface and the CSV data outputs represent the local time as per the
configured time zone. All printed times presented by the TIRTL are accompanied by the offset in hours and
minutes from Universal Co-ordinated Time (UTC) as determined by the TIRTL from the configured time zone.
For example:
Time/date presentation in CSV log file when configured with UTC time zone
date, time, zone,…
2014-08-22,02:10:07,+0000,…
Time/date presentation in CSV log file when configured with Australia/Adelaide time zone.
date, time, zone,…
2014-08-22,12:10:07,+1030,…
The TIRTL will automatically adjust for daylight savings when configured with a time zone.
Time Synchronisation
The TIRTL can synchronise its system clock to the GPS network and/or via the network time protocol (NTP).
TIP
The GPS module must be enabled for the TIRTL to synchronise the system clock via GPS.
Once powered on, the GPS may take up to 12.5 minutes to determine the correct time before time
synchronisation can occur. The GPS must wait for the leap-second information broadcast from the GPS
satellites.
NTP operates on the UDP port 123. You may need to add additional routes to the TIRTL routing configuration to
ensure that the TIRTL queries the NTP server via the correct network interface (Ethernet, Serial, or Mobile).
You may need to make changes to your network firewalls to allow the TIRTL to access the configured NTP
server IP address.
TIP
You may need to add additional routes to routing configuration of the TIRTL to ensure that the NTP
packets are sent via the correct network interface (Ethernet, Serial, or Mobile).
TIP
You may need to make changes to your network firewalls to allow the TIRTL to access the configured NTP
server IP address. NTP operates on the UDP port 123.
RX Warning Voltage If the input voltage drops below this threshold, the TIRTL will activate the RX
External Supply warning (yellow) in the system alarms.
Rx Critical Voltage If the input voltage drops below this threshold, the TIRTL will activate the RX
External Supply alarm (red) in the system alarms.
Beam Level Loss If the optical beams are attenuated more than this amount, the TIRTL will
activate the beam level alarms in the system alarms.
Time Accuracy Tolerance When synchronised to NTP or GPS, the TIRTL will estimate what the error in
time the system clock is from its time reference. If this error exceeds the value
set here the TIRTL will activate the time accuracy alarm.
3.4.13 Triggering
A trigger is an event generated at a time that a detected vehicle is predicted to have travelled a configurable
distance past a TIRTL. The TIRTL is able to generate triggers with very accurate timing related to the detection
of vehicles. You can use the TIRTLs triggering feature to emulate other vehicle detection technology detectors
or to trigger cameras to capture images/video of detected vehicles.
Triggering configuration allows you to describe a target location on the road for which the TIRTL will generate a
trigger when a vehicle is predicted to be at the target; this could be used to activate a still-image camera
taking a vehicle’s license plate image.
The TIRTL can be selective about the types of vehicles for which it can generate triggers. You may select to
generate triggers on only heavy vehicles or on all vehicles. The trigger scheme settings determine which
vehicles types will generate triggers.
Min Axles The minimum number of axles of a vehicle the TIRTL must detect before a
trigger related to the vehicle can be generated. The default is 2 axles.
Trigger Scheme Selects whether to generate triggers on no vehicles, all vehicles or only heavy
vehicles greater than 4.5 tonnes.
Dividing Line Generates triggers for vehicles that are straddling two of the regions (as
defined in the TIRTL installation configuration section).
TIRTL can be used to emulate vehicle detection loops, allowing for integration of TIRTL into existing loop based
systems.
The TIRTL uses the triggers as an input to the loop emulation software. The characteristics of a generated loop
pulse is based on the dimensions of the emulated loop and the speed and vehicle length associated with the
input trigger. The result of the loop emulation is sent to an output device to generate electrical output pulses.
Device type Selects the type of loop emulation output device. Rabbit or Modbus.
Loops A list of the emulated loops and their configuration. The parameters of the loop
are described in the table below.
Name An identifying name for the loop being emulated which is present in the loop
emulation CSV output.
Target Select which of the targets defined in the triggering configuration section that
results in this loop generating a loop pulse.
Length The length of the emulated loop in the direction of vehicle travel. This is used
for calculating the duration of the emulated loop pulse base on the duration the
vehicle is within the loop perimeter.
Duration A fixed time component added to the calculated loop pulse duration.
Front Overhang A length added to the vehicle wheelbase representing the overhang of the
vehicle over the front axle. This effects the duration of the loop pulses that are
dependent on vehicle length.
Read Overhang A length added to the vehicle wheelbase representing the overhang of the
vehicle over the rear axle. This effects the duration of the loop pulses that are
dependent on vehicle length.
Output Which output on the output device to use when emulating this loop.
Active low Make the loop outputs normal state the high state and drive it low for the
duration of the pulse.
When mounted in an elevated position, the TIRTL can be used for overheight vehicle detection and to generate
a contact closure output pulse on a Modbus based I/O device.
Direction Selects which direction of vehicle travel the TIRTL will generate overheight
events.
Output Device Selects the type of CEOS device interfaced to the TIRTL.
Device Address The IP address of the Modbus contact closure output device.
Rules A list of the modbus rules and their configuration. The parameters of the
modbus rules are described in the table below.
Name An identifying name for the modbus rule, which will appear in the overheight
logs.
All Regions Enables a rule for when an overheight vehicle is detected in any region.
Region Determines which Region that this rule is valid for. If you require one output
triggered for multiple regions then create a rule for each region.
Degraded Enables the rules when the TIRTL is operating in degraded mode (i.e. when a
beam is determined as failed).
Output Selects the Output Device IO module of the Modbus external contact closure
system.
The TIRTL supports Metric or Imperial unit systems. This setting affects the presentation of Distances, Speeds
and Temperatures in accordance with the following table:
WARNING
Changing the TIRTL unit system will requires the TIRTL to be rebooted. Rebooting of the TIRTL is
automatic once the updated configuration is applied. You will be asked to acknowledge that a reboot is
going to occur when applying the updated configuration.
WARNING
Changing the TIRTL unit system results in the removal of all logs currently stored on the TIRTL. Ensure
that you first download any log files you require before changing the TIRTL unit system.
3.4.17 Security
A username and password is required to access the web interface pages of the TIRTL. The default passwords
for each username are listed below. You may change the password of these accounts via this section of the
configuration pages.
user user
view view
You may change the user password to another password by entering the desired password in the “New User
Password” field. Once the configuration has been applied you will require the new password to access the
TIRTL web interface.
WARNING
In the event you have forgotten or do not know the user password, you will have to contact your TIRTL
supplier to restore the TIRTL back to factory default.
For each TIRTL control session established with the TIRTL on IP port 5010, you can have a pre-defined series
of TIRTL control commands that execute as if they were requested of the TIRTL directly. You can specify the
commands that you wish to run in the Session Init Script.
This facility allows the easy integration of the TIRTL with other equipment by allowing the TIRTL control
session to be established with a specific configuration. The device to which the TIRTL is being integrated does
not need to understand the TIRTL control protocol to be integrated with the TIRTL.
This feature is a legacy feature and is not the recommended approach for integrating the TIRTL with other
equipment. The recommended approach is to use the asynchronous CSV output directly.
Apply any configuration changes to the TIRTL by clicking the Apply button. The configuration changes are
effective immediately.
Some configuration change require the TIRTL to reboot. A reboot will be required if you change the unit system
of the TIRTL. If a reboot is required, the TIRTL will warn you with a pop-up dialog box requiring your
confirmation.
You can download the current TIRTL configuration via this administration page. Downloading the current TIRTL
configuration allows you to store the configuration as a file. All configuration settings are recorded in the TIRTL
configuration file. Log files that are present on the TIRTL will not be preserved in the configuration file. They
must be downloaded separately.
To download the current TIRTL configuration settings click the “Download Config”. Your browser will
download the current TIRTL configuration to a file and store it in the download area of the browser.
NOTE
A TIRTL configuration files downloaded from a TIRTL may be uploaded to a TIRTL of the same or newer
software version. Configuration files downloaded from a TIRTL new software version cannot be uploaded to a
TIRTL with an older software versions.
You can upload a previously saved TIRTL configuration file to the TIRTL to restore its previous configuration.
This feature is useful to transfer a TIRTL configuration from one TIRTL to another.
To upload an existing configuration click the “Restore” button. In the pop-up file selection window, select the
TIRTL configuration file you wish to restore onto the TIRTL.
Uploading an invalid TIRTL configuration file will generate an error message indicating the TIRTL was unable to
apply the uploaded configuration file. The result of a failed configuration upload is that the TIRTL will not
change any of its existing configuration settings.
You can reset the TIRTL to its factory default configuration via this page. Resetting the TIRTL to factory
defaults configuration results in the following:
Removes all log files
WARNING
Resetting a TIRTL to factory default configuration will remove all customer configuration settings and log
files.
All networking configuration settings will be reset to the default settings which may result in losing
connectivity to the TIRTL.
This process generally should not be done on remote TIRTLs.
You can synchronise the TIRTL system clock to the clock of the computer your web browser is running using
the “set time now” button. The TIRTL will not allow you to set the time when NTP or GPS synchronisation is
enabled in the “Time” configuration pages.
TIP
It is recommended that GPS or NTP time synchronisation be employed via the TIRTL configuration pages as
these methods results in better and more consistent time synchronisation.
3.5.5 Shutdown
You can shut down a TIRTL via this administration page. Clicking the “Shutdown Now” button will cause the
TIRTL to start the shutdown sequence, after which the TIRTL will power off. It will remain in a powered off
state until the power button on the back panel of the TIRTL is pressed or TIRTL supply power is removed and
re-applied.
WARNING
If you shut down the TIRTL it will remain unpowered until you press the power button on the back of the
TIRTL, or remove and re-apply the supply power to the TIRTL.
If you shut down the TIRTL remotely you will NOT be able to start it without visiting the TIRTL site.
3.5.6 Reboot
You can reboot a TIRTL via the administration page. Clicking the “Reboot Now” button will cause the TIRTL to
shut down completely and then initiate the start-up process.
NOTE
A reboot can take several minutes to complete. During a reboot all communication interfaces of the TIRTL
are disabled.
After a reboot the TIRTL will attempt to re-establish communication interfaces as per its configuration. The
mobile interface can take some minutes to register with the mobile network and re-establish network
connectivity.
The first line of each CSV log file contains a header to be used as the title for each column of the log file data.
zone The offset of the above date and time from UTC in
hh:mm format.
heading The direction (north, south, east, west etc) that the
vehicle was travelling.
hv_class_name The name of the class from the heavy vehicle class
scheme that this vehicle matches.
toll_class_number The number of the class from the toll class scheme
that this vehicle matches.
toll_class_name The name of the class from the toll class scheme
that this vehicle matches.
trigger_class_name The name of the class that this vehicle matches from
the trigger scheme.
width(units) The distance from the near side to the far side of the
vehicle. This measurement is only accurate in
specific circumstances, please discuss its use with
your vendor prior to use.
wheelbase(units) The distance from the first axle to the last axle.
headway (units) The time from the front of the previous vehicle in
the same lane to the front of this vehicle.
zone The offset of the above date and time from UTC in hh:mm format.
timestamp Estimate of the time of arrival of vehicle at the trigger target represented as the
number of seconds since 1970-01-01 00:00:00 UTC.
target The ID of the target for which this trigger was generated.
Tag The tag of the vehicle for which this trigger is generated.
vehicle_timestamp The time that the first axle of the vehicle was detected.
Lane The name of the lane in which this vehicle was detected.
type The end of the vehicle that generated this trigger, front or rear.
axle_count The number of axles detected at trigger time for this vehicle.
axle_spacing_#(units) The distance between two adjacent axles. (repeated for multiple axle spacings).
Field Description
zone The offset of the above date and time from UTC in hh:mm format.
timestamp The time of the event represented as the number of seconds since 1970-01-01
00:00:00 UTC.
lane The name of the region in which this vehicle was detected.
Rule The name of the overheight rule that caused this overheight event to be
generated.
distance(units) The distance, in units, that the detected overheight object is from the TIRTL
receiver.
length(units) The length of the object detected. If the TIRTL is unable to determine the length
of an object then this field will be empty.
degraded Beam level is reduced which may have an impact on the performance of the overheight
detection.
failed Beam level below that which is required for acceptable performance of the overheight
detection system.
Field Description
Zone The offset of the above date and time from UTC in hh:mm format.
Timestamp The time of the event represented as the number of seconds since 1970-01-01
00:00:00 UTC.
Please refer to the TIRTL control protocol manual for further information regarding these commands.
There are three steps required to connector to the TIRTL via the serial interface
Install drivers for USB to RS232 serial adapter
Install the modem driver for a “Connection between two computers”
Configure a “Dial up network” interface
Parameter Value
Bits 8
Parity None
Stop Bits 1
Select “Don’t detect my modem; I will select it from a list.” And press Next
4. Choose the port that corresponds to the port of the USB Serial adapter. (COM4 in this example) and
select Next.
6. Select the “Communications cable between two computers” modem that you have installed and select
Properties.
4. Enter 1234 in the “Dial-up phone number field” and “TIRTL Serial PPP” in the “Connection Name” field and
click Connect.
15. Click “OK” three times to return to the Network Connections panel.
16. Double click the “TIRTL Serial PPP” connection to establish a network session with TIRTL.
Upon successful establishment of a connection to the TIRTL you will now be able to access the TIRTL via TCP.
If using the default IP addresses you will now be able to access the TIRTL user interface at the following URL:
http://192.168.100.1
TIRTL Rx
b b
NOTE
- End of Document -