IFM CR3158 User manual

Operating instructions
mobileIoT gateway
CR3158
HW version: AB (Rev. 3.0.1)
11365928 / 0102 / 2023
GB

CR3158 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 Real-time mode..................................................... 7
4.3.2 Cloud logging mode ................................................. 7
4.4 Input/output functions.................................................... 7
4.5 Accelerometers and gyro sensors........................................... 8
4.6 GNSS (global navigation satellite system). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
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
4.10 CAN-CAN-Bluetooth/WLAN bridge.......................................... 14
4.11 CAN-Bluetooth/WLAN interface ............................................ 14
4.12 CAN-Bluetooth interface.................................................. 14
4.13 CAN-WLAN interface .................................................... 15
5 Installation.................................................................. 16
5.1 Mounting the antennas................................................... 16
6 Electrical connection.......................................................... 17
6.1 Connectors............................................................ 17
6.1.1 Operating voltage, CAN interface, inputs and outputs . . . . . . . . . . . . . . . . . . . . . . . . 17
6.1.2 GNSS antenna connection............................................ 17
6.1.3 GSM antenna connection............................................. 18
6.1.4 USB connection .................................................... 18
7 Light indicators.............................................................. 19
7.1 ON LED .............................................................. 19
7.2 STATUS LED.......................................................... 19
7.3 Indication of the operating modes........................................... 20
8 Set-up..................................................................... 21
8.1 Necessary components................................................... 21
8.2 Connect the unit........................................................ 21
8.3 Factory reset........................................................... 21
9 Repair, maintenance and disposal ............................................... 23
Glossary................................................................... 24

mobileIoT gateway CR3158
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.

CR3158 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 CR3158
5
3 Intended use
The unit enables wireless transfer of CAN data of a vehicle or machine according to the GSM, UMTS
and LTE standards. GPRS, EDGE and HSPA are supported.
It is also possible to receive and transmit GNSS position data.
Available interfaces: Bluetooth, WLAN, GSM, UMTS, LTE

CR3158 mobileIoT gateway
6
4 Function
The device has a buffer capacitor to store the time in the real time clock (RTC).
The device provides access to CAN data in various operating modes.
Function CR3158
CAN-CAN-Bluetooth/WLAN bridge ●
CAN-Bluetooth/WLAN interface ●
Antenna external
Mobile communications 4G worldwide (certified countries only)
Real-time mode ●
Cloud logging mode ●
Input/output functions 3/1
Acceleration sensor ●
Gyro sensor ●
GNSS ●
CAN connections 3
ifm e-SIM ●
● = applicable
4.1 Mobile radio interface
The unit has a mobile radio interface for mobile data transmission.
The unit supports the 4G mobile network. In order to achieve higher network coverage, the unit has a
fallback function, allowing it to switch to the 2G or 3G 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 device can be operated in the following connection modes:
• Real-time mode
• Cloud logging mode
The connection mode is set as follows:
Object Index Subindex Type Default Description
DeviceMode 0x5353 0x00 U8 0x03 0X00 = cloud logging mode
0x01 = reserved
0x02 = real-time mode

mobileIoT gateway CR3158
7
Restart the device to update to the newly configured mode.
When bit 7 is written, the device restarts.
4.3.1 Real-time mode
In real-time mode, bidirectional transmission of CAN messages occurs.
The unit can send/receive process data (e.g. machine parameters) via CAN interfaces during
operation via Bluetooth/WLAN, the mobile network and the mobileIoT platform. Depending on the
design, it can transmit data from the GNSS receiver and the input/output functions and forward them
via the CAN bus. Alternatively, the unit can receive the data from an external receiver (e.g.
CANwireless) via a WLAN or Bluetooth connection and send it to the mobileIoT platform.
The data is continuously transmitted and can be evaluated in near real-time. For this function, there
must be a permanent connection between the unit and the user software or the mobileIoT platform.
This mode also supports a real-time connection from Codesys 2.3. This requires appropriate software
and a mobileIoT data contract.
The real-time mode can be set locally via an SDO or via the mobileIoT suite in the machine properties.
In real-time mode, no data or messages are stored on the mobileIoT platform.
4.3.2 Cloud logging mode
The cloud logging mode allows GNSS position data to be sent automatically to the mobileIoT platform.
In this mode, metrics can be actively generated and sent by the application controller and also allow
the gateway to autonomously log data available on the CAN bus.
Data linking to the application controller is configured in the mobileIoT suite. There the corresponding
source code will be automatically generated, which can be loaded into the controller programme.
No data is sent to the mobileIoT platform during real-time connection. As soon as the real-time
connection is terminated, data is captured again and sent to the mobileIoT platform.
4.4 Input/output functions
The device 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)

CR3158 mobileIoT gateway
8
Object Index Subindex Type Default Description
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 device can send this data via the CAN interface. The configuration is made via the following
objects:
Object Index Subindex Type Default Description
CANMode 0x4001 0x02 U8
rw
— Bit 0: compatibility mode with device
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 0x05 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.

mobileIoT gateway CR3158
9
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)
Gyroscope – Z-
axis
0x544D 0x05 R32
ro
— Current acceleration Z-axis (unit: °/second)
The device can send this data via the CAN interface. The configuration is made via the following
objects:
Object Index Subindex Type Default Description
CANMode 0x4001 0x02 U8
rw
— Bit 0: compatibility mode with device
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 0x06 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
4 4 R32 Gyroscope – Z-axis

CR3158 mobileIoT gateway
10
4.6 GNSS (global navigation satellite system)
The device has a GNSS receiver. The device 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
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 device 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 current GNSS position of
the device starts.
If the device 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 device can send this data via the CAN interface. The configuration is made via the following
objects:
Object Index Subindex Type Default Description
CANMode 0x4001 0x02 U8
rw
— Bit 0: compatibility mode with device
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)