IFM DTE8 5 Series Device Manual
  1. Manuals
  2. Brands
  3. IFM Manuals
  4. Rfid Systems
  5. DTE8 5 Series
  6. Device manual

IFM DTE8 5 Series Device Manual

Rfid compact device iot protocol
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Device manual
RFID compact device
IoT Protocol
UK
DTE105
DTE605
DTE8x5
DTE9x5

Advertisement

Table of Contents
loading

Related Manuals for IFM DTE8 5 Series

Summary of Contents for IFM DTE8 5 Series

  • Page 1 Device manual RFID compact device IoT Protocol DTE105 DTE605 DTE8x5 DTE9x5...

  • Page 2: Table Of Contents

    Contents Licenses and trademarks ......................4 Preliminary note ..........................5 Symbols used ........................... 5 Safety instructions ..........................5 Functions and features ........................5 RFID evaluation unit DTE105 ....................5 RFID compact devices DTE605, DTE8x5, DTE9x5 ..............6 Configuration via Ethernet interface ..................6 Functions for commissioning ....................
  • Page 3 IoT Core general informations ....................35 HTTP protocol format ......................35 TCP Port of the RFID devices with IoT Core ................35 Access the ifm IoT Core ......................... 36 JSON objects .......................... 37 JSON requests ........................37 JSON Response ........................38 HTTP request call ........................

  • Page 4: Licenses And Trademarks

    First possibility, call of request over URL and POST method ..........41 Second possibility, direct call of request over URL ..............42 First steps ..........................43 General IoT Core services ......................44 Get Identity of the device ......................44 Read diagnostics from the IO channel ................... 45 Subscribe to event ........................

  • Page 5: Preliminary Note

    Preliminary note Symbols used ► Instruction > Reaction, result […] Designation of pushbuttons, buttons or indications → Cross-reference, Important note Non-compliance can result in malfunction or interference Information Supplementary note Safety instructions Please read the operating instructions prior to setup of the device. Ensure that the device is suitable for your application without any restrictions.

  • Page 6: Rfid Compact Devices Dte605, Dte8X5, Dte9X5

    RFID compact devices DTE605, DTE8x5, DTE9x5 The RFID Compact device integrates UHF Read-/Write head and a TCP/IP interface to communicate with a PC or Controller with integrated Ethernet interface. Additionally, 2 IO channels are available which can be configured as input/output to IEC 61131.

  • Page 7: Function

    Function RFID evaluation unit DTE105 The evaluation unit processes data of up to 4 read/write heads (type ANT51x/ANT41x/ANT60x) or IEC 61131 inputs / outputs . The mode of operation for each port can be set individually via the Ethernet controller . Connection...

  • Page 8: Aux" Voltage Supply

    Please note that the total current consumption of the device must not exceed 3 A . You can find information about the matching read/write heads on our website at: https://www.ifm.com → Data sheet search → e.g. ANT4, ANT5 or ANT6...

  • Page 9: Factory Setting Of The Ethernet Parameters

    Factory setting of the Ethernet parameters The following values are preset on delivery of the device: Parameters Factory setting IP address 192 .168 .0 .79 Gateway address 192 .168 .0 .100 Subnet mask 255 .255 .255 .0 Auto-negotiation DHCP The settings can be changed via the web server of the device or via the Ethernet host. Reset to factory settings The Ethernet parameters and the pass wor d of the dev ice can be reset to the factory settings.

  • Page 10: Rfid Compact Devices Dte605, Dte8X5, Dte9X5

    RFID compact devices DTE605, DTE8x5, DTE9x5 1: Voltage supply 5: Sensor 2: DTE8x4/DTE9x4 device unit 6: Ethernet host 3: Actuator 4: ID tag The device processes data from the integrated Read-/Write head and the two IEC 61131 inputs / outputs. The mode of operation for the two IO channels can be set individually via the Ethernet host or the integrated Webserver.

  • Page 11: Pwr" Voltage Supply And Process Connections C/Qi Or C/Qo

    "PWR" voltage supply and process connections C/Qi or C/Qo ► Connect the device to the voltage supply using an M12 connection cable. Connection 24V DC Switching output (C/Qo) or input (C/Qi) 2 Switching output (C/Qo) or input (C/Qi) 1 not used Please note that the total current consumption of the device must not exceed the value of 0,5 A.

  • Page 12: Reset To Factory Settings

    Reset to factory settings The Ethernet parameters and the pass wor d of the dev ice can be reset to the factory settings. Take the following steps: ► Remove all cable connections from the device. ► Insert an electrically conductive bridge between pin 2 and pin 4 on the process connection voltage supply PWR.

  • Page 13: Allowed Network Infrastructure

    Allowed network infrastructure The devices can be integrated in the Ethernet network infrastructures described below if the following safety instructions are implemented and observed Operating of the devices in an unprotected Ethernet network structure Check and restrict access options to the device: Restrict access to authorized persons.

  • Page 14: Star Structure

    Star structure C = Controller D = Device...

  • Page 15: Installation

    Installation You can find information about installation and electrical connection in the operating instructions for the devices at https://www.ifm Devices DTE8x5/DTE9x5 To avoid malfunctions of the UHF functions, do not place any electrically conductive objects within 10 cm of the built-in UHF antenna.

  • Page 16: Operating And Display Elements

    Operating and display elements LED indicators DTE105 The device indicates the current status of the interfaces via the status LEDs . LED AUX LED green LED yellow Status Note No voltage supply UAUX < 5 V Flashes at 2 Hz Voltage supply too low 5 V ≤...

  • Page 17: Leds Io1

    LEDs IO1 ... IO4 The LED indications of the process connections are different for each connection configuration . Use as input to IEC 61131 LED green LED yellow Status Note Interface via Ethernet host not Interface deactivated configured Interface activated, input on L level (0 V) Interface activated, input on H level (24 V) Flashes at 8 Hz Flashes at 8 Hz...

  • Page 18: Led Indicators Dte605, Dte8X5, Dte9X5

    LED indicators DTE605, DTE8x5, DTE9x5 The device indicates the current status of the interfaces via the status LEDs . LED PWR LED PWR State Note (1x green) Voltage supply OK 18 V ≤ U ≤ 36 V Flashing at 2 Antenna (HF field) is deactivated In this case the LED Signal DTE605...

  • Page 19: Special Device Led Indicators

    Special device LED indicators State Note PWR LED (green) ON Device is in the service A firmware update is necessary and can be LEDs of signal bar (yellow) mode “emergency system executed via the web server flashing at 8 Hz started”...

  • Page 20: Putting Into Operation

    Putting into operation ► Connect the device according to the operating instructions. After connecting the operating voltage, the device is ready for use. The green LED • AUX for DTE105 device • PWR LED for DTE605, DTE8x5, DTE9x5 devices with LED LINK/ACTIVITY will light up after the device is ready and connected to the Ethernet network.

  • Page 21: Web Interface

    Web interface The devices are equipped with an integrated web server that allows to • read and write data of the ID tag • read from the User data area of the ID tag • write to the User data area of the ID tag •...

  • Page 22: Tab Home

    Tab Home This page slightly differs in its appearance depending of the device. This is the main menu from where all functions of the device can be accessed. The user can select • the language of the device web interface.

  • Page 23: Tab "Network

    Tab "Network" This menu allows different settings Ethernet interface the device to be changed. Ask what settings for the integration of the device into the existing network needed your network administrator. If the device is connected directly to the PC, a static IP address setting is recommended. Check →...

  • Page 24: Tab "Firmware - Firmware Update

    Tab "Firmware – firmware update" This page slightly differs in its appearance depending of the device. Please update the Read-/Write head firmware always before update the device firmware ! This menu allows to update the firmware of the device. ► Open the “Firmware”...

  • Page 25: Tab "Firmware - Read-/Write Head Update

    Please note that the device needs up to 2 minutes to restart after a firmware update. During this time the LEDs of the device are switched off. Tab "Firmware – Read-/Write head update" This page slightly differs in its appearance depending of the device. This menu shows under section “Read-/Write head information”...

  • Page 26: Update Of The Read-/Write Head Or The Uhf Module

    Update of the Read-/Write head or the UHF module Button Function Browse Select the firmware file for the update process Note: For update of the Read-/Write firmware only files with extension “.afw” are accepted. For update of the UHF module firmware only files with extension “.rfw” are accepted. Transfer Start the firmware update process After the firmware update process is finished following information is displayed.

  • Page 27: Tab "Io-Port

    Example of URL for ANT513 connected at IO port 1 at DTE105 : http://192.168.0.79/rwhupdate?ioport=1&anttype=ANT600&fwVersion=1&setLng=en Example of URL for DTE605 : http://192.168.0.79/rwhupdate?ioport=1&anttype=DTE60X&fwVersion=1&setLng=en Example of URL for DTE805 : http://192.168.0.79/rwhupdate?ioport=1&anttype=DTE80X&fwVersion=1&setLng=en Example of URL for DTE905 : http://192.168.0.79/rwhupdate?ioport=1&anttype=DTE90X&fwVersion=1&setLng=en After finishing the firmware update of the Read-/Write head, enter the URL of the device to return to the main menu (→...

  • Page 28: Io-Port Io-1 And Io-2

    IO-PORT IO-1 and IO-2 The IO-channels can be configured to mode “Off”, “Input” or “Output”. Mode Function No function, inactive Input IEC 61131 input, payload size 20 bytes Output IEC 61131 output, payload size 20 bytes Input (2 bytes) IEC 61131 input, payload size 2 bytes Output (2 bytes) IEC 61131 output, payload size 2 bytes Parameter “Data hold time”...

  • Page 29: Tab "System

    Tab "System" This menu allows to define a password to protect the device against unauthorized access. To enable the password protection the button "New settings" has to be set to "on". Parameter Setting Note Username admin User name could not be changed Old password XXXXXX Default password is "admin".

  • Page 30: Tab "Sntp

    Tab “SNTP” If an SNTP server is present in the Ethernet network the internal clock of the device can be synchronized with the external time server. ► Click on button [Submit] to transmit the settings to the device.

  • Page 31: Tab "Info

    Time gone since device powered up. In case of setting time by SNTP service, the System date and System time is set automatically. • Show the ifm article and production number. Version PermData is used for compatibility checks if newer software is installed...
  • Page 32 • Shows the information about the integrated Read-/Write head and the UHF module. Additionally, the firmware update of both units can be done here. Details see → Update of the Read-/Write head or the UHF module...

  • Page 33: Open Source License Information

    The licensed free software information is displayed and can be downloaded from the device. Extract of the license text file: DTEXxX Open Source licenses information ifm electronic GmbH Sections included in this document: List of licenses included in cJSON by package List of copyrights included in cJSON by file List of licenses included in newlib 1.14.0 (ARM syscalls) by package...

  • Page 34: Rfid Iot Core Protocol

    RFID IOT Core protocol General information about the different RFID devices with IoT Core The devices DTE105, DTE605, DTE805, DTE9x5 have different hardware versions so that the physical access to HF and UHF ID tags are possible. For this reason, there are also different IoT core services when accessing the data of the ID tags.

  • Page 35: Iot Core General Informations

    IoT Core general informations The IoT Core allows the user to address the devices from IT networks via a REpresentational State Transfer APplication Interface ( REST API ) and to integrate it into Internet-of-Things (IoT) applications. A device description is stored in the devices and can be obtained via the command getree(). This device description is a structured, machine-readable data object in JSON format.

  • Page 36: Access The Ifm Iot Core

    Access the ifm IoT Core The user can access the ifm IoT Core of the RFID devices over Port 8080 via HTTP requests. The requests itself are send and received as JSON objects. http://ip/name/data_point/service Parameter Description Remark IP address of the IoT interface IPV4 address of the target device e.g.: 192.168.0.79...

  • Page 37: Json Objects

    JSON objects JSON requests The ifm IoT Core interact with services. Each interaction is a "request" from the host over a URL with a service element of the device. JSON request object "code" : "request", "cid" : number, "adr" : service_adr, "reply"...

  • Page 38: Json Response

    JSON Response Every service will answer with a response from the device. This is the JSON object for the response: JSON response object "cid" : number, "adr" : service_address, "reply" : "reply_data" "data" : "serialized_data", … "code" : number(see http_codes) Field explanation This is the very number that was given in the request.

  • Page 39: Http Request Call

    IoT Core is behind the URL http://192.168.0.79:8080/getidentity Response data: "cid":-1, "data": {"iot": {"name": "DTE105-0000034652", "version": "1.3", "catalogue": {"name": "ifm-std", "version": "1.2"}, "namespace": "JSON", "deviceclass": "device"}, "security": {"securityMode": "disabled", "authScheme": "standard", "isPasswdSet": "FALSE"} "code":200...

  • Page 40: Post Request

    POST request Using a POST request the user has read and write access to a data point. Method: POST URL: http://ip/data_point/service The syntax of the request to the IoT Core is: "code":"code_id", "cid":id, adr":"data_point/service", "data":{req_data}, "auth":{"user":"usr_id","passwd":"password"} } Field Parameter Description code code_id Service class...

  • Page 41: Iot General Functions

    IoT general functions The device itself has the type "device". IoT Services The following services can be used on the root element of the type device: Service Description Provide the complete tree or subtree of the device description ../gettree Reading device information ../getidentity Search device description for specific elements ../querytree...

  • Page 42: Second Possibility, Direct Call Of Request Over Url

    Second possibility, direct call of request over URL URL: http://192.168.0.79:8080/deviceinfo/productcode/getdata Response data: {"cid":-1,"data":{"value":"DTE105"},"code":200} URL: http://192.168.0.79:8080/deviceinfo/serialnumber/getdata Response data: {"cid":-1,"data":{"value":"0000034652"},"code":200} URL: http://192.168.0.79:8080/deviceinfo/swrevision/getdata Response data: {"cid":-1,"data":{"value":"V4.1.6"},"code":200} Response data: http://192.168.0.79:8080/deviceinfo/hwrevision/getdata Response {"cid":-1,"data":{"value":"00005"},"code":200} Request: http://192.168.0.79:8080/deviceinfo/swrevision/getdata Response {"cid":-1,"data":{"value":"V4.1.6"},"code":200}...

  • Page 43: First Steps

    First steps First the HTTP server need to read the device description of the device. With the received information the applicable services and data points can be accessed. ► Send the following POST request to the DEVICE: URL: http://192.168.0.79:8080/gettree Method: POST Request body data: "code":"request", "cid":1,...

  • Page 44: General Iot Core Services

    "reply text" Optional: Text to be send back in the response. If not needed, this element can be removed from the request. Response data: {"cid":1234,"data":{"iot": {"name": "DTE905AB-0000047712","version": "1.3","catalogue": {"name": "ifm-std", "version": "1.2"},"namespace": "JSON","deviceclass": "device"}},"adr":"XYZ","code":200} Response Value Remark element <Number>...

  • Page 45: Read Diagnostics From The Io Channel

    Read diagnostics from the IO channel With this service the diagnostics of the IO channels can be read. Service available: All devices This service is supported in all channel modes Method: POST URL: http://192.168.0.79:8080 Request body data: {"code": "request", "cid": 9000, "adr": "diagnostics/port[1]/list", "reply": "reply text"} Request Value Remark...

  • Page 46: Subscribe To Event

    Subscribe to event With this service an event can be subscribed by the host to get automatically a notification by the device if the data of the event has changed. One event can be registered by different subscribers, but each need must use a unique "cid". Before the TCP connection is closed the host must unsubscribe all active events ! The active subscribed events can be read out over the IoT core service ->...
  • Page 47 Response data: {"cid":<Number>,"adr":"reply text","code":200} Response Value Remark element <Number> Correlation identifier. Same as send in request Optional. <string> Text sent in element "reply" of the service request e.g. "reply text" code Response code of the IoT core See chapter -> IoT Core: HTTP status codes, e.g.

  • Page 48: Unsubscribe From Event

    Unsubscribe from event With this service an already registered event via subscribe service can be unsubscribed by the host from the device. Before the TCP connection is closed the host must unsubscribe all active events ! The active subscribed events can be read out over the IoT core service -> Get subscription information Method: POST URL:...

  • Page 49: Get All Subscriptions Of The Device

    Get all subscriptions of the device With this service the state of all registered events via subscribe service can be read by the host from the device. Method: POST URL: http://192.168.0.79:8080 Request body data: {"code": "request", "cid": 9999, "adr":"getsubscriberlist","reply": "reply text", Request Value Remark...

  • Page 50: Connect The Iot Webserver With The Device

    Connect the IoT Webserver with the device Start a HTTP Webserver server on the host. Open and listen at free selectable TCP port. Following message is sent from the device to the IoT Webserver via TCP protocol. TCP payload data chunk 1: Host: 192.168.0.61:12345 Content-Type: application/json Transfer-Encoding: chunked...

  • Page 51: Rfid Iot Core Profile

    RFID IoT Core profile In addition to the generally applicable IoT core data points, RFID devices also have special ones that allow to communicate with the LF / HF / UHF ID tags. Configure IO-Ports Service available: DTE105, DTE605, DTE805, DTE9x5 This service is supported in the channel mode "RWH"...
  • Page 52 Request element "datatoset" Value Remark dte/temperature_unit 0 = [°C] For DTEx05 valid 1 = [F] port 1 = IO-1 For DTEx05 valid 2 = IO-2 For DTEx05 valid 3 = IO-3 For DTEx05 valid 4 = IO-4 Only for DTE105 valid mode 0 = RFID For DTE605,DTE805,DTE9x5 fix set on IO-1...
  • Page 53 Parameter settings: Request element Value Remark port 1 = IO-1 For DTEx05 valid 2 = IO-2 For DTEx05 valid 3 = IO-3 For DTEx05 valid 4 = IO-4 Only for DTE105 valid mode 0 = RFID 1 = INPUT 2 = OUTPUT 3 = OFF data_hold_time 0 …...

  • Page 54: Access Data Of The Io Ports

    Access data of the IO ports The following services allow the access to the IO ports. Read input C/Qi of the IO channel Service available: DTE105, DTE605, DTE805, DTE9x5 This service is supported in the channel mode "Input". Method: POST URL: http://192.168.0.79:8080 {"code": "request", "cid": 2002, "adr": "data/port[2]/input/cqi/getdata","reply": "reply text"}...

  • Page 55: Receive C/Qi From Io Port Automatically

    Receive C/Qi from IO port automatically Method: POST URL: http://192.168.0.79:8080 Request body data: {"code": "request", "cid":2012, "adr": "data/port3]/input/cqi/datachanged/subscribe", "reply": "reply text", "data": {"callback": "http://192.168.1.1:34003/dte-io2-cqi-changed"}} Request Value Remark element code "request" <CorrID> Multiple subscriptions from one source are allowed, but each will need a unique "cid". e.g.
  • Page 56 Data sent from the device to the IoT Webserver: {"code":"event","cid":2012,"adr":"/io3-cqi-changed","data":{"eventno":"45","srcurl":"DTE105AA- 0000032653/data/port[3]/input/cqi/datachanged","payload":{"/data/port[3]/input/cqi":{"code":200,"data":1}}}} Response Value Remark element code "event" Type of response, here "event" <CorrID> Correlation identifier. Same as send in subscribe request e.g. 2012 "<event_name>" Name of the event under which this is registered in the device.

  • Page 57: Read Input I/Q Of The Io Channel

    Read input I/Q of the IO channel Service available: DTE105, DTE605, DTE805, DTE9x5 This service is supported in the channel mode "Input" and "Output". Method: POST URL: http://192.168.0.79:8080 {"code": "request", "cid": 2001, "adr": "data/port[2]/input/iq/getdata","reply": "reply text"} Request Value Remark element code "request"...

  • Page 58: Write Output C/Qo Of The Io Channel

    Write output C/Qo of the IO channel Service available: DTE105, DTE605, DTE805, DTE9x5 This service is supported in the channel mode "Output" . Method: POST URL: http://192.168.0.79:8080 {"code": "request","cid": 4711,"adr": "/data/port[4]/output/cqo/setdata","reply":"reply text", "data": {"newvalue": Request Value Remark element code "request" <CorrID>...

  • Page 59: Access Data Of The Hf Id Tag

    Access data of the HF ID tag The following services allow the access to the HF ID tags. Read UID of HF ID tags Service available: DTE105, DTE605 This service is supported in the channel mode "RWH" Method: POST URL: http://192.168.0.79:8080 Request body data: { "code": "request","cid": 1001,"adr": "data/port[1]/rfid/id_tag/uid/getdata", "reply": "reply text"}...
  • Page 60 Method: GET URL: http://192.168.0.79:8080//data/port[1]/rfid/id_tag/uid/getdata Response data: {'cid':-1,'data':{'value':'e008010c38325124'},'code':200} Response Value Remark element <CorrID> Correlation identifier. Same as send in request e.g. -1 data {"value":"e008010c38325124"} value: UID coded in HEX, 2 characters per HEX number e.g. "e008010c38325124" code Response code of the IoT core See chapter ->...

  • Page 61: Receive Uid From Hf Id Tag Automatically

    Receive UID from HF ID tag automatically Service available: DTE105, DTE605 This service is supported in the channel mode "RWH" Method: POST URL: http://192.168.0.79:8080 Request body data: {"code":"request","cid":1010,"adr":"data/port[1]/rfid/id_tag/uid/datachanged/subscribe","reply":"reply text","data":{"callback":"http://192.168.1.1:34003/io1-uid-nw"}} Request Value Remark element code "request" <CorrID> Correlation identifier. Multiple subscriptions from one source are allowed, but each will need a unique "cid".
  • Page 62 Data sent from the device to the IoT Webserver: {"code":"event","cid":1010,"adr":"/io1-uid-nw","data":{"eventno":"17579","srcurl":"DTE105AA- 0000032653/data/port[1]/rfid/id_tag/UID/datachanged","payload":{"/data/port[1]/rfid/id_tag/UID":{"code":200,"data":" e008010c38325124"}}}} Response Value Remark element code "event" Type of response, here "event" <CorrID> Correlation identifier. Same as send in subscribe request e.g. 1010 "<event_name>" Name of the event under which this is registered in the device.

  • Page 63: Read User Memory Of Hf Id Tags

    Read User memory of HF ID tags Service available: DTE105, DTE605 This service is supported in the channel mode "RWH" Method: POST URL: http://192.168.0.79:8080 Request body data: { "code":"request","cid": 1002,"adr": "data/port[1]/rfid/id_tag/user_data/getblobdata","reply": "reply text", "data": { "pos": 0, "length": 16 } } Request Value Remark...

  • Page 64: Write User Memory Of Hf Id Tags

    Write User memory of HF ID tags Service available: DTE105, DTE605 This service is supported in the channel mode "RWH" Method: POST URL: http://192.168.0.79:8080 Request body data: {"code": "request", "cid": 1010, "adr": "data/port[1]/rfid/id_tag/user_data/setblobdata", "reply": "reply text", "data": {"pos": 0, "data": "QmFzZTY0IGNvZGVkIHN0cmluZw=="}} Request Value Remark...

  • Page 65: Access Data Of The Uhf Id Tag

    Access data of the UHF ID tag The following services allow the access to the UHF ID tags. Read EPC data of UHF ID tags Service available: DTE805, DTE9x5 This service is supported in the channel mode "RWH" Method: POST URL: http://192.168.0.79:8080 Request body data:...
  • Page 66 Method: GET URL: http://192.168.0.79:8080//data/port[1]/rfid/id_tag_list/epcs/getdata Response data: {"cid":-1,"data":{"value":"["eb80b0443c00001a"]"},"code":200}...

  • Page 67: Receive Epc Data Of Uhf Id Tags Automatically

    Receive EPC data of UHF ID tags automatically Service available: DTE805, DTE9x5 This service is supported in the channel mode "RWH" Method: POST URL: http://192.168.0.79:8080 Request body data: {"code": "request", "cid": 3010, "adr": "data/port[1]/rfid/id_tag_list/epcs/datachanged/subscribe", "reply": "reply text", "data": {"callback": "http://192.168.1.1:34003/io1-epcs-changed"}} Request Value Remark...
  • Page 68 Response data: {"cid": 3010, "adr": "reply text", "code": 200} Response Value Remark element <CorrID> Correlation identifier. Same as send in request e.g. 3010 "<UTF-8 string>" Text sent in element "reply" of the service request e.g. "reply text" code Response code of the IoT core See chapter ->...

  • Page 69: Read Memory Bank Of The Uhf Id Tags Tags

    Read memory bank of the UHF ID tags tags Service available: DTE805, DTE9x5 This service is supported in the channel mode "RWH" Method: POST URL: http://192.168.0.79:8080 Request body data: {"code":"request","cid":3002,"adr":"data/port[1]/rfid/id_tag/user_data/read","reply":"reply text", "data":{"epc":"e2004080711100000000003018305855","bank":3,"pos":0,"length":16}} Request Value Remark element code "request" <CorrID> Correlation identifier. Can be set from 0…32767 e.g.

  • Page 70: Write User Memory Of The Uhf Id Tags

    Write User memory of the UHF ID tags Service available: DTE105, DTE605 This service is supported in the channel mode "RWH" Method: POST URL: http://192.168.0.79:8080 Request body data: {"code": "request", "cid": 3010, "adr": "data/port[1]/rfid/id_tag/user_data/setblobdata", "reply": "reply text", "data": {"pos": 0, "data": "QmFzZTY0IGNvZGVkIHN0cmluZw=="}} Request Value Remark...

  • Page 71: Iot Core Http Status Codes

    IoT Core HTTP status codes The http status code only shows whether the IoT Core command request was correct, not whether the execution of the service was successful. Code Text Description The service could be process correctly Bad request: <Reason> The service request is invalid or malformed Authentication is required and has failed or has not been Access denied: <Address>...

  • Page 72: Error Codes Of The Device

    Error codes of the device Device error codes can be received from device by running service -> Read diagnostics from the IO channel. The device error codes are transferred in the "data" element of the service. ,"data": {"count": 2,"codes": ["F4FE9005","F4FE9005"]} Subelement "count"...

  • Page 73: Error Group Compact Device (F4Fe)

    Error group compact device (F4FE) Error group Error Code Description Compact device F4FE0100 Power supply failure Ident Unit F4FE0200 Hardware failure , short circuit and overload Compact device F4FE0201 Allowed temperature exceeded Compact device F4FE0300 Read-/Write head not operating cause time out occurred Command buffer overflow IO-Server Queue Compact device F4FE0400...

  • Page 74: Error Group Communication User - Compact Device (F5Fe )

    Compact device F4FE9405 Over temperature at front end detected Compact device F4FE9406 R/W head error detect reverse power to high Compact device F4FE9407 Reset of R/W head detected Compact device F4FE9408 R/W head HAL error detected Compact device F4FEA000 Invalid command code detected Compact device F4FEA001 Invalid command parameter detected...

  • Page 75: Error Group Command Error - Compact Device (F6Fe )

    Communication User F5FE8500 Module size to short to execute commands - Compact device Error group Command error – compact device (F6FE ) Error Error group Description Code Communication User Invalid command parameter (e.g. data range) F6FE0300 - Compact device (indicated by compact device)

  • Page 76: Glossary

    Glossary Definition Remark Antenna RFID antenna built in a Read-/Write head. Data of the command response is updated after the compact device detects Asynchronously a state change of the ID tag from “not present” to “present” or vice versa. Block size Size of one block of the ID tag, for UHF ID tags always 2 bytes.
  • Page 77 Receive Signal Strength Indicator. Reflect the received signal quality of the RSSI ID tag. Higher values mean a better reception of the ID tag signal. Data of the command response is updated immediately with the currently Synchronously detected state of the ID tag. Transponder Identifier.

This manual is also suitable for:

Dte9 5 seriesDte105Dte605

Table of Contents