IFM mobileIoT CR3145 User manual

Operating instructions
mobileIoT gateway
CR3145
11365922 / 0003 / 2021
GB

CR3145 mobileIoT gateway
2
Contents
1 Preliminary note.............................................................. 3
1.1 Symbols used........................................................... 3
1.2 Warnings used.......................................................... 3
2 Safety instructions............................................................ 4
2.1 Cyber security .......................................................... 4
2.2 Air traffic............................................................... 4
3 Intended use ................................................................ 5
4 Function.................................................................... 6
4.1 Mobile radio interface..................................................... 6
4.2 eSIM card.............................................................. 6
4.3 Connection modes....................................................... 6
4.3.1 Cloud logging mode .................................................. 7
4.4 Input/output functions..................................................... 7
4.5 Accelerometers and gyro sensors........................................... 8
4.6 GNSS (global navigation satellite system) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.6.1 Automatically send GNSS data to the mobileIoT platform. . . . . . . . . . . . . . . . . . . . . . 11
4.7 Energy management ..................................................... 11
4.8 Device status........................................................... 12
4.9 Compatibility mode....................................................... 13
5 Installation .................................................................. 15
5.1 Mounting the antennas.................................................... 15
6 Electrical connection .......................................................... 16
6.1 Connectors............................................................. 16
6.1.1 Operating voltage, CAN interface, inputs and outputs. . . . . . . . . . . . . . . . . . . . . . . . . 16
6.1.2 USB connection...................................................... 16
7 Light indicators............................................................... 17
7.1 ON LED............................................................... 17
7.2 STATUS LED........................................................... 17
7.3 Indication of the operating modes ........................................... 18
8 Set-up...................................................................... 19
8.1 Necessary components................................................... 19
8.2 Connect the unit......................................................... 19
8.3 Factory reset ........................................................... 19
9 Repair, maintenance and disposal................................................ 21
Glossary.................................................................... 22

mobileIoT gateway CR3145
3
1 Preliminary note
You will find instructions, technical data, approvals and further information using the QR code on the
unit / packaging or at www.ifm.com.
1.1 Symbols used
Requirement
Instructions
Reaction, result
[...] Designation of keys, buttons or indications
Cross-reference
Important note
Non-compliance may result in malfunction or interference.
Information
Supplementary note
1.2 Warnings used
ATTENTION
Warning of damage to property
CAUTION
Warning of personal injury
wSlight reversible injuries may result.
WARNING
Warning of serious personal injury
wDeath or serious irreversible injuries may result.
GB

CR3145 mobileIoT gateway
4
2 Safety instructions
• The unit described is a subcomponent for integration into a system.
– The system architect is responsible for the safety of the system.
– The system architect undertakes to perform a risk assessment and to create documentation in
accordance with legal and normative requirements to be provided to the operator and user of
the system. This documentation must contain all necessary information and safety instructions
for the operator, the user and, if applicable, for any service personnel authorised by the
architect of the system.
• Read this document before setting up the product and keep it during the entire service life.
• The product must be suitable for the corresponding applications and environmental conditions
without any restrictions.
• Only use the product for its intended purpose (Ò Intended use).
• If the operating instructions or the technical data are not adhered to, personal injury and/or damage
to property may occur.
• The manufacturer assumes no liability or warranty for any consequences caused by tampering with
the product or incorrect use by the operator.
• Installation, electrical connection, set-up, programming, configuration, operation and maintenance
of the product must be carried out by personnel qualified and authorised for the respective activity.
• Protect units and cables against damage.
• Replace damaged units, otherwise the technical data and safety will be impaired.
2.1 Cyber security
ATTENTION
Operating the machine in an unprotected network environment
wUnauthorised read or write access to data is possible.
wUnauthorised manipulation of the device function is possible.
uCheck and restrict access options to the device.
2.2 Air traffic
The device must not be operated on board aircraft.
Using it in an aircraft can affect the navigation and communication systems. An offence can lead to
legal action against the offender.

mobileIoT gateway CR3145
5
3 Intended use
The unit enables wireless transfer of CAN data of a vehicle or machine according to the GSM and
UMTS standards. GPRS, EDGE and HSPA are supported.
It is also possible to receive and transmit GNSS position data.
Available interfaces: GSM, UMTS
GB

CR3145 mobileIoT gateway
6
4 Function
The unit provides access to CAN data in various operating modes.
Function CR3145
CAN-CAN-Bluetooth/WLAN bridge —
CAN-Bluetooth/WLAN interface —
Antenna internal
Mobile communications 3G
Real-time mode —
Cloud logging mode ●
Input/output functions 1/1
Acceleration sensor ●
Gyro sensor ●
GNSS ●
CAN connections 1
ifm e-SIM ●
● = applicable
4.1 Mobile radio interface
The unit has a mobile radio interface for mobile data transmission.
The unit supports the 3G mobile network. In order to achieve higher network coverage, the unit has a
fallback function, allowing it to switch to the 2G network.
The unit detects the mobile network with the best transmission speed and automatically switches to it.
The mobile radio interface supports bidirectional data exchange in the mobile network.
4.2 eSIM card
The unit is equipped with an embedded SIM (eSIM) card. The eSIM card is delivered with an eSIM
profile that contains all the necessary communication settings.
The eSIM card of the unit is not activated on delivery. After registering the unit, activation of the
eSIM card can take up to 4 hours.
4.3 Connection modes
The unit can be operated in the following connection modes:
• Cloud logging mode
The connection mode is set as follows:
Object Index Subindex Type Default Description
DeviceMode 0x1011 0x01 U8 0x03 0X00 = cloud logging mode
0x01 = reserved
0x02 = real-time mode
0x03 = IoT mode
Restart the unit to update to the newly configured mode.
When bit 7 is written, the unit restarts.

mobileIoT gateway CR3145
7
4.3.1 Cloud logging mode
In cloud logging mode, selected CAN messages are sent to the cloud, processed and stored. In this
case, the unit operates autonomously and does not have to be actively controlled by an application.
The configurations for this mode are made in the mobileIoT suite, which can send the data in CAN
messages. An OTA (over-the-air) configuration of the units is carried out via the mobileIoT suite.
4.4 Input/output functions
The unit has additional input/output functions (3 analogue inputs, 1 digital output). For example, the
input function can be used to collect device or machine status information or to directly detect and
monitor switch states. The data determined via the input/output functions can be visualised or
transferred via the CAN bus.
The input/output functions are accessed via the following objects:
Object Index Subindex Type Default Description
Analogue input 1 0x546F 0x14 R32
ro
— Pin 4 of the 14-pin Micro Timer II connector
Raw value of the analogue input measure-
ment (Volt)
No filtering applied
Analogue input 2 0x546F 0x15 R32
ro
— Pin 5 of the 14-pin Micro Timer II connector
Raw value of the analogue input measure-
ment (Volt)
No filtering applied
Analogue input 3 0x546F 0x16 R32
ro
— Pin 6 of the 14-pin Micro Timer II connector
Raw value of the analogue input measure-
ment (Volt)
No filtering applied
IO – clamp 30
voltage
0x3333 0x67 R32
ro
— Terminal 30
Raw value of the analogue input measure-
ment (Volt)
IO – clamp 15
voltage
0x3333 0x66 R32
ro
— Terminal 15
Raw value of the analogue input measure-
ment (Volt)
IO – clamp 15
(ignition) state
0x3333 0x01 U8
ro
— Terminal 15
0 = input signal low (< 2.5 V)
1 = input signal high (> 5.5 V)
IO = digital out-
put
0x3333 0x0F U8
rw
— Pin 7 of the 14-pin Micro Timer II connector
Bit 0: (0 = output signal low, 1 = output sig-
nal high)
Bits 1...7: reserved, set to 0
IO – digital out-
put status
0x3333 0x10 U8
ro
— Pin 7 of the 14-pin Micro Timer II connector
Bit 0: (0 = output signal error, 1 = output sig-
nal OK)
Bits 1...7: reserved, set to 0
IO – device tem-
perature
0x3333 0x0E S16
ro
— Device temperature in °C
The unit can send this data via the CAN interface. The configuration is made via the following objects:
GB

CR3145 mobileIoT gateway
8
Object Index Subindex Type Default Description
DeviceMode 0x4001 0x02 U8
rw
— Bit 0: compatibility mode with unit CR3114
(1s cycle)
Bit 1: forward device status via CAN bus (1s
cycle)
Bit 2: forward complete GNSS data via CAN
bus (1s cycle)
Bit 3: forward input/output data via CAN
bus (1s cycle)
Bit 4: forward acceleration and gyroscope
data via CAN bus (100ms cycle)
IO BaseID 0x4005 0x07 U16 0x400 COBID start address for input/output data
transmission (1s cycle)
The exact index and subindex can be found in the corresponding EDS file.
All data available in the respective device mode are sent via the CAN1 interface.
The data of the input/output functions are mapped to the following CAN messages:
COB ID Start byte Length
(bytes) Type Object
IO BaseID + 0x00 0 4 R32 IO – clamp 30 voltage
4 4 R32 IO – clamp 15 voltage
IO BaseID + 0x01 0 4 R32 Analogue input 1
4 2 S32 IO – device temperature
4.5 Accelerometers and gyro sensors
The accelerometers measure acceleration along the X, Y and Z axes. The 3-axis gyro sensor
determines the angular velocity on the X, Y and Z axes. This data is evaluated and can be forwarded
to the controller via CAN bus.
The data of the acceleration/gyro sensors is accessed via the following objects:
Object Index Subindex Type Default Description
Acceleration – X-
axis
0x544D 0x00 R32
ro
— Current acceleration X-axis (unit: g)
Acceleration – Y-
axis
0x544D 0x01 R32
ro
— Current acceleration Y-axis (unit: g)
Acceleration – Z-
axis
0x544D 0x02 R32
ro
— Current acceleration Z-axis (unit: g)
Gyroscope – X-
axis
0x544D 0x03 R32
ro
— Current acceleration X-axis (unit: °/second)
Gyroscope – Y-
axis
0x544D 0x04 R32
ro
— Current acceleration Y-axis (unit: °/second)

mobileIoT gateway CR3145
9
Object Index Subindex Type Default Description
Gyroscope – Z-
axis
0x544D 0x05 R32
ro
— Current acceleration Z-axis (unit: °/second)
The unit can send this data via the CAN interface. The configuration is made via the following objects:
Object Index Subindex Type Default Description
DeviceMode 0x4001 0x02 U8
rw
— Bit 0: compatibility mode with unit CR3114
(1s cycle)
Bit 1: forward device status via CAN bus (1s
cycle)
Bit 2: forward complete GNSS data via CAN
bus (1s cycle)
Bit 3: forward input/output data via CAN bus
(1s cycle)
Bit 4: forward acceleration and gyro-
scope data via CAN bus (100ms cycle)
Movement Ba-
seID
0x4005 0x05 U16 0x500 COBID start address for acceleration and
gyroscope data transmission (100 ms cycle)
All data available in the respective device mode are sent via the CAN1 interface.
The exact index and subindex can be found in the corresponding EDS file.
The acceleration and gyroscope data are mapped to the following CAN messages:
COB ID Start byte Length
(bytes) Type Object
Movement BaseID +
0x00
0 4 R32 Acceleration – X-axis
4 4 R32 Acceleration – Y-axis
Movement BaseID +
0x01
0 4 R32 Acceleration – Z-axis
4 4 R32 Gyroscope – X-axis
Movement BaseID +
0x02
0 4 R32 Gyroscope – Y-axis
0 4 R32 Gyroscope – Z-axis
4.6 GNSS (global navigation satellite system)
The device has a GNSS receiver. The unit can forward the position data determined by the GNSS
receiver via the CAN bus or send it via the mobile network.
The device can evaluate signals from GPS, GLONASS and BeiDou satellites. Data from two
navigation systems can be evaluated simultaneously. This enhances the accuracy.
The GNSS data is accessed via the following objects:
Object Index Subindex Type Default Description
Positioning – an-
tenna status
0x3333 0x13 U8
ro
— 0 = antenna damaged or missing
1 = antenna OK
Positioning – po-
sition data valid
0x3333 0x14 U8
ro
— 0 = position data invalid (no position detec-
tion)
1 = position data valid (position detection)
Positioning – ac-
tive satellites
0x5220 0x00 U8
ro
— Number of currently active satellites
Positioning –
mode (GNSS)
0x5200 0x00 U8
rw
— 0 = GPS only
1 = GPS + GLONASS
2 = GPS + BEIDOU
3 = GLONASS + BEIDOU
GB

CR3145 mobileIoT gateway
10
Object Index Subindex Type Default Description
Positioning – lon-
gitude
0x5208 0x00 R32
ro
— Longitude as a 32-bit floating point number
(decimal degrees)
Positioning – lati-
tude
0x5209 0x00 R32
ro
— Latitude as a 32-bit floating point number
(decimal degrees)
Positioning – alti-
tude
0x520A 0x00 R32
ro
— Height above mean sea level as a 32-bit
float (in mm)
Positioning –
speed over
ground
0x520B 0x00 R32
ro
— Speed over ground as a 32-bit float (in m/s)
Positioning –
GPS odometer
0x520B 0x02 U32
ro
— Total GNSS based distance as a 32-bit un-
signed integer (100 metres per bit)
Positioning – trig-
ger distance for
GPS odometer
0x520B 0x03 R32
ro
— Distance in metres that the unit has to be
moved to start the odometer count
Positioning –
heading
0x520C 0x00 R32
ro
— Course with respect to north as a 32-bit float
(decimal degrees)
Logging – cur-
rent GNSS posi-
tion
0x5200 0xF0 U8
rw
— If this object is set to any value other than 0,
recording of the unit’s current GNSS position
starts.
If the unit has no GNSS reference point, it
waits for a reference point before logging the
position.
The flag remains on the written value until
the position has been recorded. It is then re-
set to 0.
The unit can send this data via the CAN interface. The configuration is made via the following objects:
Object Index Subindex Type Default Description
DeviceMode 0x4001 0x02 U8
rw
— Bit 0: compatibility mode with unit CR3114
(1s cycle)
Bit 1: forward device status via CAN bus (1s
cycle)
Bit 2: forward complete GNSS data via
CAN bus (1s cycle)
Bit 3: forward input/output data via CAN bus
(1s cycle)
Bit 4: forward acceleration and gyroscope
data via CAN bus (100ms cycle)
Position BaseID 0x4005 0x06 U16 0x300 COBID start address for input GNSS data
transmission (1s cycle)
All data available in the respective device mode are sent via the CAN1 interface.
The exact index and subindex can be found in the corresponding EDS file.
The GNSS data is mapped to the following CAN messages:
COB ID Start byte Length
(bytes) Type Object
Position BaseID +
0x00
0 1 U8 Positioning – position data valid
1 1 U8 Positioning – active satellites
2 1 U8 Positioning – mode (GNSS)
Position BaseID +
0x01
0 4 R32 Positioning – longitude
4 4 R32 Positioning – latitude
Position BaseID +
0x02
0 4 R32 Positioning – altitude
0 4 R32 Positioning – heading

mobileIoT gateway CR3145
11
COB ID Start byte Length
(bytes) Type Object
Position BaseID +
0x03
0 4 R32 Positioning – speed over ground
4 4 R32 Positioning – GPS odometer
4.6.1 Automatically send GNSS data to the mobileIoT platform
The device can automatically determine the GNSS position and send it to the mobileIoT platform.
The configuration is made via the following objects:
Object Index Subindex Type Default Description
GNSS-interval 0x4009 0x02 U32
rw
900,000 Interval of the GNSS position logging (in
ms). Set to 0xFFFFFF to deactivate this
function. Min. value = 60,000
GNSS-distance 0x4009 0x03 U32
rw
0xFFFFFFFF Distance between the most recent position
determined and the current position (linear
distance). The minimum distance is 3 me-
tres.
Logging – file up-
load period
0x3333 0x1C U16 0x01 Period in minutes. When this time has
elapsed, the logged file is closed and trans-
mitted to the server.
Set this value to 0 to deactivate the period.
All data available in the respective device mode are sent via the CAN1 interface.
The exact index and subindex can be found in the corresponding EDS file.
4.7 Energy management
Different energy modes control the energy consumption of the unit. In addition to the standard mode,
the unit also features a sleep mode. In this mode, some functions are deactivated to save energy.
Specific events cause the unit to return to the standard mode.
No mobile radio connection is possible in sleep mode.
Energy management is accessed via the following objects:
Object Index Subindex Type Default Description
Power manage-
ment – deep
sleep flag
0x3333 0xF3 U8
wo
— If this flag is set, the unit can only be woken
up from sleep mode via clamp 30, clamp 15
or CAN1.
The unit will not make up from sleep mode
cyclically or on a vibration event.
Use e.g. during transport
uSet this flag before changing to sleep
mode.
GB

CR3145 mobileIoT gateway
12
Object Index Subindex Type Default Description
Power manage-
ment – time to
sleep
0x3333 0x08 U8
wo
— Time in seconds until switching to sleep
mode.
The unit only changes to sleep mode if
clamp 15 is set to low and no CAN message
is present at the corresponding CAN inter-
face.
A CAN message can wake the unit from
sleep mode.
Depending on the device design, a level
change at clamp 15 or the detection of a
certain acceleration force can wake the unit
from sleep mode.
With this setting, CAN messages are sent if
clamp 15 is set to high.
Power manage-
ment – sleep tim-
er status
0x3333 0x29 U8
ro
— 0: sleep timer deactivated
1: sleep timer activated
The object can be read if clamp 15 is set to
high.
Power manage-
ment – shutdown
delay time
0x3333 0x32 U16
rw
— Delay time in seconds
After detecting the ignition input (clamp 15)
and the CAN off state, the unit continues to
operate for the specified time and then goes
to sleep mode.
Power manage-
ment – cyclic
wake-up time
0x3333 0x35 U32
rw
— Time in seconds
After the specified time period in sleep
mode, the unit automatically wakes up and
changes to standard mode.
This function is only active with a value > 0.
Power manage-
ment – accel.
wake-up force
0x3333 0x36 R32
rw
— Force in g
If the accelerometer detects an acceleration
force greater than this value, the unit wakes
up and changes to standard mode.
This function is only active with a value > 0.
Power manage-
ment - CAN
sleep time
0x3333 0x41 U32
rw
— Time in milliseconds
If the unit does not receive any CAN mes-
sages within the specified time period, it
changes to sleep mode.
This function is only active with a value > 0.
4.8 Device status
The unit can send this data via the CAN interface. The configuration is made via the following objects:
Object Index Subindex Type Default Description
DeviceMode 0x4001 0x02 U8
rw
— Bit 0: compatibility mode with unit CR3114
(1s cycle)
Bit 1: forward device status via CAN bus
(1s cycle)
Bit 2: forward complete GNSS data via CAN
bus (1s cycle)
Bit 3: forward input/output data via CAN bus
(1s cycle)
Bit 4: forward acceleration and gyroscope
data via CAN bus (100ms cycle)
Status BaseID 0x4005 0x05 U16 0x200 COBID start address for device status
transmission (1s cycle)
All data available in the respective device mode are sent via the CAN1 interface.

mobileIoT gateway CR3145
13
The exact index and subindex can be found in the corresponding EDS file.
The device status data are mapped to the following CAN messages:
COB ID Start byte Length
(bytes) Type Object
Status BaseID +
0x00
0 1 U8 Network state
0: not connected
1: registered with home network
2: not registered, searching for network
3: registration refused by network provider
4: Unknown
5: registered in external network
1 1 U8 Signal quality
0: -115dBm or less
1: -111 dBm
2…30: between -110 and -54dBm
31: -52 dBm or more
99: unknown
2 1 U8 Modem result
8: fatal error
9: initialisation
10: Internet connection active
11: mobileIoT server TCP connection active
3 1 U8 Current network mode
4 2 U16 State machine error code
6 1 U8 Current connection mode
0x00: cloud logging mode
0x01: reserved
0x02: real-time mode
0x03: IoT mode
Status BaseID +
0x01
0 4 U32 CMS error number
0 4 U32 CME error number
Status BaseID +
0x02
0 4 U32 Device time (Unix format)
4 4 U32 Total operation time in seconds
4.9 Compatibility mode
In compatibility mode, the unit transmits the data via the CAN bus in the same way as the CR3114
unit.
The compatibility mode data is mapped to the following CAN messages:
COB ID Start byte Length
(bytes) Type Object
0x180 + NodeID 0 1 U8 Network state
0: not connected
1: registered with home network
2: not registered, searching for network
3: registration refused by network provider
4: Unknown
5: registered in external network
GB

CR3145 mobileIoT gateway
14
COB ID Start byte Length
(bytes) Type Object
0x180 + NodeID 1 1 U8 Signal quality
0: -115dBm or less
1: -111 dBm
2…30: between -110 and -54dBm
31: -52 dBm or more
99: unknown
2 1 U8 Modem result
8: fatal error
9: initialisation
10: Internet connection active
11: mobileIoT server TCP connection active
3 1 U8 File transfer receive indication
4 1 U8 File transfer transmit command
5 1 U8 SMS transmit request
6 1 U8 SMS receive indication
7 1 U8 Device mode
Status BaseID +
0x01
0 4 U32 GNSS – latitude
0 4 U32 GNSS – longitude
Status BaseID +
0x02
0 4 U32 Fixed to 1
4 4 U32 Device time (Unix format)

mobileIoT gateway CR3145
15
5 Installation
uDisconnect the power of the machine before installation.
The unit can be mounted in a horizontal position or with the connectors facing downwards.
Installation with the connectors facing upwards is not permitted.
The unit must be fixed with the rear facing the mounting surface.
ATTENTION
Higher shock > IK07
wDamage possible
Protection rating and electrical protection might be impaired
uIf necessary, the system creator must take external measures to protect the device
depending on the requirements of the corresponding application.
uReplace damaged units, otherwise the technical data and safety will be impaired.
74
Fig.1: Holes for mounting
uUse 2 M5x30 cylinder head bolts to fix the unit on an even surface.
Tightening torque: 2.2 Nm
5.1 Mounting the antennas
uWhen mounting the antennas in vehicles avoid the vicinity of fuel tanks, vessels with explosives or
insufficiently screened electronic components (→ 2 Safety instructions).
uPosition the antennas so that a permanent distance of min. 0.2 m from people is ensured during
operation.
uDo not install the antennas in closed metal constructions such as the driver's cab.
uTo reliably receive the GPS signals, position the GPS antenna with unrestricted access to the sky.
uPlease observe the antenna manufacturer’s notes.
Stable data transmission requires a good antenna signal. In case of problems change the
position of the antennas or the mobile equipment if necessary.
GB

CR3145 mobileIoT gateway
16
6 Electrical connection
6.1 Connectors
2
1
1: Micro Timer II connector, 14-pin
(CAN, supply, inputs, outputs)
2: USB socket (Micro-AB type)
6.1.1 Operating voltage, CAN interface, inputs and outputs
1
2
13
14
Fig.2: Micro Timer II connector, 14-pin
1: VCC/ clamp 30 (supply)
2: factory setting 1 (input)
3: GND/ clamp 31 (supply)
4: analogue input 1
5: analogue input 2
6: analogue input 3
7: digital output
8: digital output/ clamp 15 (input, ignition signal)
9: factory setting 2 (input)
10: Not connected
11: Not connected
12: Not connected
13: CAN1_H (CAN interface 1 (high) bidirectional)
14: CAN1_L (CAN interface 1 (low) bidirectional)
6.1.2 USB connection
The USB connection (Micro-AB) is used for diagnostics and updates of the bootloader and firmware.
Protection rating IP6K7 is also guaranteed without the connected USB cable.
Always protect the USB connection with the matching protective plug to prevent soiling.

mobileIoT gateway CR3145
17
7 Light indicators
2
1
1: ON LED
2: STATUS LED
7.1 ON LED
The ON LED indicates the status of the power supply.
Colour State Meaning
- Off Unit switched off or in sleep mode
Green On Unit switched on, clamp 30 voltage in permissible range
Red On Unit switched on, clamp 30 voltage outside the permissi-
ble range or unit in battery mode
Green Flashing Unit in diagnostic or update mode
Tab.1: ON LED
7.2 STATUS LED
The STATUS LED indicates the operating status of the active connections. The different colours are
displayed according to priority, from 5 (low) to 1 (high). If several operating states are active at the
same time, the STATUS LED always indicates the state with the highest priority.
Colour State Connect Priority Meaning
- Off - - If ON LED is also off:
The unit is switched off.
Green On Various - Connected with the ifmmobileIoTserver.
Blue On Mobile radio/ Inter-
net
1 Not connected with the ifmmobileIoTserver.
Orange On CAN1 2 Connection faulty.
Red On CAN2 3 Connection faulty.
Magenta On GNSS 4 No position/antenna detected.
- Off Bluetooth/WLAN 5 Not connected to a network/device.
Tab.2: STATUS LED
GB

CR3145 mobileIoT gateway
18
7.3 Indication of the operating modes
LED State Meaning
ON A configuration update is carried out via the CAN inter-
face.
STATUS
ON Active file transfer in logging mode. A configured CAN
message is received (orange flashing) and sent to the
ifm mobileIoT data portal (blue flashing).
STATUS
ON Active data transfer in real-time mode.
STATUS
ON Initialisation after power on.
STATUS
ON A configuration update is carried out via the ifm mobileI-
oT data portal.
STATUS
ON A remote firmware update is carried out via the ifm mo-
bileIoT data portal.
STATUS
ON Reset of the unit via the slide switch on the D-Sub con-
nector (CAN1).
STATUS
ON Reset (0x1011 0x64) of the unit via CAN.
STATUS
ON Transmission of the GPS position and the keepalive
message. Display varies depending on the configured
polling interval.
STATUS
Tab.3: Operating modes

mobileIoT gateway CR3145
19
8 Set-up
8.1 Necessary components
The following components are needed to configure and set up the device:
• Hardware
– CR3145
– suitable antennas/ combined antenna for navigation and mobile radio
– connection cable
– voltage supply 8…32 V DC
– PC
– for further configuration (optional):
CAN/PC interface (e.g. CAN/RS232 USB interface CANfox, art. no.: EC2112) and adapter
cable for CANfox (art. no.: EC2113)
CAN bus terminating resistors (2x 120Ω)
• ifm mobileIoT suite
To register and activate the unit, access to the mobileIoT suite is required. You will receive the
access data from your local ifm contact. The documentation for the mobileIoTsuite and for
activating the unit can be found in the mobileIoTsuite.
After you have activated the unit, an mobileIoT data contract will be concluded.
After successful registration and activation, the unit establishes a connection to the
ifmmobileIoTdata portal and enables bidirectional data transfer.
• Configuration software
– ifm Maintenance Tool
–mobileIoT device configuration addin for ifm Maintenance Tool
For details on how to configure the unit, see the ifm Maintenance Tool documentation.
8.2 Connect the unit
uProvide the CAN bus with 120Ω terminating resistors.
uConnect the CAN/PC interface with the CAN adapter cable to the unit and connect it to the PC.
uApply the supply voltage.
The following table provides an overview of some CAN baud rates in relation to the cable length:
CAN baud rate Cable length CAN bus
800 kbit/s 50 m
500 kbit/s 100 m
250 kbit/s 250 m
125 kbit/s 500 m
50 kbit/s 1000 m
Tab.4: CAN baud rate
8.3 Factory reset
The following reset variants can be triggered via the CAN interface:
GB

CR3145 mobileIoT gateway
20
Function Index Subindex Description
Revert to factory configuration 0x1011 0x01 The factory configuration is restored. All recorded data is de-
leted.
Delete all log files 0x1011 0x62 All recorded data is deleted.
Revert to firmware defaults
remote
0x1011 0x63 The default configuration of the current firmware is restored.
All recorded data is deleted.
CAN, WLAN, Bluetooth and mobile radio settings as well as
the factory configuration are retained.
Revert to firmware defaults
plus format remote
0x1011 0x64 The default configuration of the current firmware is restored.
All recorded data and the factory configuration are deleted.
CAN, WLAN, Bluetooth and mobile radio settings are re-
tained.
Revert to firmware defaults lo-
cal
0x1011 0x65 The default configuration of the current firmware is restored.
All recorded data and settings are deleted.
The factory configuration is retained.
To carry out the factory reset via the CAN interface, CANopen software (e.g. maintenance tool) and a
communication gateway (e.g. CANfox, part no. EC2112) are required. The CANopen software writes
the value 0x64616F6C into the CANopen object index 0x1011 to trigger a specific reset variant.
The following example shows the factory reset via the sub-index 0x65 (restoration of the default
configuration):
uConnect the unit with a PC. Connect the unit (Ò/19).
uStart the CANopen software.
uWrite the value 0x64616F6C into the object index 0x1011, subindex 0x650 via the CANopen
software.
uWrite the value to the object dictionary of the unit.
uWait until the unit sends the CANopen boot-up message on COB-IDs 0x727 and 0x728.
wThe unit is reset to the firmware default settings (object 0x1011 0x65).
wThe ON LED lights green.
wThe STATUS LED lights blue.
wThe unit has adopted the firmware defaults (baud rate 250 kbit/s, node ID 39 etc.).