ifm DTM42 Series RF Identification System User Manual

ifm DTM42 Series RF Identification System

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.

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

Warnings used

ATTENTION
Warning of damage to property

Legal and copyright information

© All rights reserved by ifm electronic gmbh. No part of these instructions may be reproduced and used without the consent of ifm electronic gmbh.
All product names, pictures, companies or other brands used on our pages are the property of the respective rights owners.

Safety instructions

General

• 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, operation and maintenance of the product must be carried out by qualified personnel authorised by the machine operator.
• Protect units and cables against damage.

Radio equipment
In general, radio equipment must not be used in the vicinity of petrol stations, fuel depots, chemical plants or blasting operations.

• Do not transport and store any flammable gases, liquids or explosive substances near the unit. Interference of electronic and medical devices Operation can affect the function of electronic devices that are not correctly shielded.
• Disconnect the device in the vicinity of medical equipment.
• Contact the manufacturer of the corresponding device in case of any interference.

Intended use

The read/write head reads and writes ID tags without contact.
The data is made available as process data via the CAN-bus interface.

Items supplied

• Read/write head
• 2x hexagonal nut

The device is supplied without installation and connection accessories.
Available accessories: www.ifm.com.
The optimum function is not ensured when using components from other manufacturers.

Function

ID tags

The ID tags are passively operated without a battery. The energy required for operation is provided by the read/write head.
The energy is provided via an inductive coupling. The integrated antenna coil in the read/write head generates a magnetic field which partly penetrates the antenna coil of the ID tag. A voltage is generated by induction that supplies the data carrier with energy.
The device supports ID tags according to ISO 15693.

Device overview

DTM426

| Article number:| DTM426
---|---|---
Function:| Read/write head
Type designation:| DTMHF GBRWCJUS03
Type:| M18, flush mountable

DTM427

Installation

Notes on the unit installation

When mounting several RFID units adhere to the minimum distances between the systems.

Flush mounting of a read/write head in metal reduces the read/write distance.

Device performance can be affected if positioned in the immediate vicinity of powerful HF emission sources such as welding transformers or converters.

Avoiding interference

The device generates a modulated electrical field with a frequency of 13.56 MHz. Avoid interference with data communication:

• Do not operate any devices in the vicinity that use the same frequency band.
• Such devices are for example frequency converters and switched-mode power supplies.

If there are other devices in the same frequency band in the vicinity:

• The mounting distances between the devices should be as large as possible.
• Use the devices in alternating operation.
• Switch the HF field of the device on/off.

Mechanical design

DTM426Fig. 1: DTM426

1. Sensing face

DTM427 Fig. 2: DTM427

1. Sensing face

Install device

• Fix the device using the supplied nuts (M18).

DTM426

Fig. 3: Flush mounting

DTM427 Fig. 4: Non-flush mounting

Mounting distances

DTM426

DTM427

Positioning of the ID tags

The sensing face marks the center of the integrated antenna coil of the read/write head.

• Align the sensing face of the read/write head and the ID tag in the same way.

For installation in or on metal use the ID tags provided for this purpose.

Position the ID tag in the area of the sensing face. When doing so, the angle of aperture and the operating distance must be adhered to (→ Data sheet of the device).

DTM426

Fig. 5: Position the ID tag

• Align the ID tag on the central axis of the antenna of the device.
  • The distance “D” is indicated in the data sheet.

DTM427

• Align the ID tag on the central axis of the antenna of the device.
  • The distance “D” is indicated in the data sheet.

Electrical connection

The device must be connected by a qualified electrician. Device of protection class III (PC III).
The electrical supply must only be made via PELV/SELV circuits.

• Disconnect power before connecting the device.

Wiring

• Connect the device to the CAN bus using the M12 connector.
  • Voltage is supplied via the CAN bus.

M12 connector, A-coded, 5 poles
|

1. Shield
2. U+
3. GND

| 4: CAN high
| 5: CAN low

The CAN bus connection is almost trouble-free if the following points are considered:

• Use cables approved for CAN bus.
• Terminate the cables with 120 Ω terminating resistors.

Information on available sockets see: www.ifm.com.

Operating and display elements

1 LEDs green / yellow / red

Operation

J1939 interface

The RFID read/write heads have a standardised SAE J1939 interface. All measured values and parameters can be accessed via the J1939 protocol. The individual configuration can be saved in the internal permanent memory.

Structure of the SAE J1939 protocol
The SAE J1939 protocol uses a 29-bit CAN identifier (extended frame format CAN 2.0B). A J1939 message has the following structure:

J1939 message

29-bit CAN identifier| Data
Priority| Parameter Group Number (PGN)| Source address| User data of the message
28…26| 25…8| 7…0| 0…8 bytes

Parameter Group Number (PGN)

Ext. Data Page| Data Page| PDU Format (PF)| Target address / group exten- sion (PS)
25| 24| 23…16| 15…8

PDU format 1 (specific)

00h – EFh| Target Address (DA)
23…16| 15…8

PDU format 2 (global)

F0h – FFh| Group Extension (GE)
23…16| 15…8

PDU format 1
This format defines a message which is sent to a defined device. In this case the PDU-specific byte
(PS) is the target address (DA) of the device. If the value of the PDU format field (PF) is between 0x00 and 0xEF, it is a PDU format 1 message.
For proprietary messages (manufacturer-specific) the PDU format value 0xEF is defined.
Ext. data page bit = 0 and data page bit = 0.

PDU format 2
This format defines a message which is sent globally. In this case the PDU specific byte (PS) corresponds to the group extension (GE). If the value of the PDU format field (PF) is between 0xF0 and 0xFF, it is a PDU format 2 message.
For proprietary messages (manufacturer-specific) the area PDU format (PF) and group extension (GE) 0xFF00 – 0xFFFF is defined.
Ext. data page bit = 0 and data page bit = 0.

Proprietary protocol in PDU format 1
The parameters of the device are listed in a table that is accessed per 16-bit index. To access the sensor parameters in reading or writing the proprietary PDU format 1 message is used. PDU format (PF) corresponds to the value 0xEF. In this case the PDU-specific byte (PS) is the target address (DA) of the device which is to receive the message. If more than 4 bytes are transferred, the J1939 transport protocol must be used.

Example
Address target device (ECU): 0x3B Address control unit / master: 0x14 Priority of the message: 3

Requirement: Master → ECU

0xCEFEB1

4

| LSB| MSB| RW| 0| LSB| ..| ..| MSB

Response: Master ← ECU

Parameter index: 2-byte parameter index.
RW: Read parameter → 0x00 / write parameter → 0x01 SC: Status code

• 0x00: Ok
• 0x01: Parameter value too small
• 0x02: Parameter value too big
• 0x03: Parameter index does not exist
• 0x04: Parameter can only be read
• 0x05: Parameter can only be written
• 0x06: No access to parameter
• 0x07: Invalid data size
• 0x08: Parameter writing blocked
• (Example: The value to be written is already set in the sensor)
• 0x09: Invalid command
• 0x0A: Unknown error
• 0x0B: Error while reading or writing from ID tag

Configuration example

• Set block size of ID tag to 8, index 0x2800
• Address target device (ECU): 0xEB
• Address control unit / master: 0x14 Priority of the message: 3
• Requirement: Master → ECU

CA

N identi- fier

| 8-byte data frame
---|---
0xCEFEB14| 0x00| 0x28| 0x01| 0x00| 0x08| 0x00| 0x00| 0x00

Response: Master ← ECU

Parameter mapping

Device status

The parameter with the index 0x2080 represents the current device status:

Bit| 31| 30| 29| 28| 27| 26| 25| 24
---|---|---|---|---|---|---|---|---
Status| tag_err

Bit| 23| 22| 21| 20| 19| 18| 17| 16
---|---|---|---|---|---|---|---|---
Status| acc_err

Access error codes
Updated after each write or read access of the ID tag.

not in the field any- more.
0x02| ISO_COMMAND_ERROR_RX_ERROR| Error while receiving the answer from the ID tag (CRC error, framing error, collision, etc.).

ID tag error codes
Updated after each read or write access of the ID tag.

of blocks is too high. Example: format error.
0x03| ISO_TAG_ERROR_OPTION_NOT_SUP- PORTED| Option is not supported.
0x0F| ISO_TAG_ERROR_OTHER| Other error.
0x10| ISO_TAG_ERROR_BLOCK_NOT_USA- BLE| The specified block cannot be used (or was not found).
0x11| ISO_TAG_ERROR_BLOCK_AL- READY_BLOCKED| The specified block is locked and cannot be locked again.
0x12| ISO_TAG_ERROR_BLOCK_NOT_UP- DATEABLE| The specified block is locked and its contents cannot be up- dated.
0x13| ISO_TAG_ER- ROR_BLOCK_WRITE_VERIFY| The specified block cannot be programmed (a write verify error occurred).
0x14| ISO_TAG_ER- ROR_BLOCK_LOCK_VERIFY| The specified block cannot be locked (a lock verify error occurred).

ID tag data access

Read data from ID tag
The data is read by the ID tag by sending a “read parameter” frame with the following information:

• Data address
• Data length

ID

29 bits

| Parameter index 2 bytes| Read/Write 1 byte| Status 1 byte| ID tag

Data address

| ID tag

Data length

 | 0x01| 0xA0| 0x00| 0x00| LSB| MSB| LSB| MSB

Example
Read 8 bytes of data from ID tag address 4.
Requirement: Master → ECU

Response: Master ← ECU

For successful reading and writing, the ID tag must be in the detection range of the read/write head. In the event of data read and write errors, the status byte responds with 0x0B.

Write data to ID tag
The data is written to the ID tag by sending a “write parameter” frame with the following information:

• Data address
• Data length
• Data

CAN

identifier

| x-byte data frame
---|---
ID

29 bits

| Parameter index 2 bytes| Read/ Write

1 byte

| Status 1 byte| ID tag

Data address

| ID tag

Data length

| ID tag Data
 | 0x01| 0xA0| 0x00| 0x00| LSB| MSB| LSB| MSB| Data[0]| Data[x]

Example
Write 4 bytes of data (0xAA,0xBB,0xCC,0xDD) to ID tag address 2.
Requirement: Master → ECU

CAN

identifier

|

x-byte data frame

---|---
0xCEF EB14| 0x01| 0xA0| 0x01| 0x00| 0x02| 0x00| 0x04| 0x00| 0xAA| 0xBB| 0xCC| 0xDD

Response: Master ← ECU

For successful reading and writing, the ID tag must be in the detection range of the read/write head. In the event of data read and write errors, the status byte responds with 0x0B.

Settings

Device address (0x2000) and baud rate (0x2001)
Valid values for the device address are: 0 to 253.
Preferably use the preset device address. Via “address claiming” the device address can be changed. Valid values for the baud rate are: 250 kBits/s, 500 kBits/s.

Default settings of the device:

• Device address (ECU): 235
• Baud rate: 250 kBits/s

Use the set device address only once in the CAN network.

• Use “address claiming” in the CAN network to avoid conflicts. (Ò Address claiming / 19)

Use “address claiming” in the CAN network to avoid conflicts. (Ò Address claiming / 19)

• Reset the read/write head with the reset command or hardware reset. (Ò Reset read/write head / 19)

Address claiming
The read/write head supports “dynamic address claiming”.
By default, the device address is 235. With the device address, the sensor logs in to the network during start-up. Unless there is an address conflict with other network participants, the sensor starts communication automatically.
Arbitrary address capable (CA)
If the set address of the device is already used in the network, the participant with a higher priority will be accepted by the network. The rejected network participant with a lower priority will be assigned another valid device address.

Reset read/write head
By writing the value “1” to the parameter index 0x2002 the read/write head is reset.

After writing the value, the read/write head is reset immediately. No response frame is sent from the read/write head.

Maintenance, repair and disposal

The unit is maintenance-free.

• Contact ifm in case of malfunction.
• Do not open the housing as the unit does not contain any components which can be maintained by the user. The unit must only be repaired by the manufacturer.
• Clean the device using a dry cloth.
• Dispose of the unit in accordance with the national environmental regulations.

Approvals/standards

For approvals and standards, the following information is available:

• Test standards and regulations: documentation.ifm.com
• EU declaration of conformity and approvals: documentation.ifm.com
• Notes relevant for approval: package inserts of the device

Glossary

CAN
Controller Area Network, bus system for use in mobile applications.

ID tag
An ID tag is used to identify objects. A read/write device is used to read the ID tag via a high-frequency radio signal. An ID tag consists of an antenna, an analogue circuit for receiving and transmitting (transceiver), a digital circuit and a non-volatile memory.

References

• Online documentation of your product - ifm
• ifm - automation made in Germany
• Online documentation of your product - ifm
• Online documentation of your product - ifm

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>