SICK RFH6 Series Technical Information
  1. Manuals
  2. Brands
  3. SICK Manuals
  4. Controller
  5. RFH6 Series
  6. Technical information

SICK RFH6 Series Technical Information

Pndp function block for siemens s7-controls
Hide thumbs
Table of Contents

Advertisement

Quick Links

Technical Information
SICK
RFH6xx Function Block
SICK RFH6XX PNDP Function Block for
Siemens S7-Controls (Step7 V5.5)
Version V2.X

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the RFH6 Series and is the answer not in the manual?

Questions and answers

Related Manuals for SICK RFH6 Series

Summary of Contents for SICK RFH6 Series

  • Page 1 Technical Information SICK RFH6xx Function Block Version V2.X SICK RFH6XX PNDP Function Block for Siemens S7-Controls (Step7 V5.5)

  • Page 2: Table Of Contents

    Table of Content 1 About this document ......................3 1.1 Function of this document .................... 3 1.2 Target group ........................ 3 2 General Information ......................4 3 Hardware configuration ....................5 3.1 Supported PLC ......................5 3.2 Supported fieldbus gateways / sensors ................ 5 3.3 Configuration in Step7 ....................

  • Page 3: About This Document

    SICK RFH6XX function block. 1.1 Function of this document This operation manual describes how to use SICK RFH6XX PNDP Function Block. It is used for guiding technical personnel working for the machine manufacturer / operator in project planning and commissioning.

  • Page 4: General Information

    Communication via free selectable CoLa commands (CoLa-A protocol) Addressing of devices which communicate via CAN-Bus The Command Language (CoLa) is an internal SICK protocol for the communication with SOPAS devices SOPAS-ET is an engineering tool for the configuration of SICK sensors...

  • Page 5: Hardware Configuration

    3.2 Supported fieldbus gateways / sensors The SICK sensor communicates via fieldbus (Profibus/Profinet) with the PLC. If the sensor cannot support the fieldbuses mentioned above, Gateway modules can be used. The following Gateways are supported from the function block: CDM 425 (Profinet), starting with firmware version V3.31...
  • Page 6 RFH6xx PNDP Function Block Technical Information Image 2: Step7 Example of hardware configuration Date: 12.06.2014...

  • Page 7: Description Of Function Block

    Therefore it is necessary that the function block is called up cycli- cally in the user program. The RFH function block encapsulates “SICK CCOM PNDP” (FB10), which allows the com- munication between PLC and sensor. FC10 (SICK COLA ACCESS) is used internally for the interpretation of CoLa-telegrams. 4.1 Function block specification...

  • Page 8: Operation Mode

    RFH6xx PNDP Function Block Technical Information 4.2 Operation Mode In order to use the RFH function block, the following communication parameters have to be set: IN_ADDR: Projected entry point address of the used input modules of the input area. The entry point address is fixed by the projecting of the hardware (see chapter 3.3).
  • Page 9 RFH6xx PNDP Function Block Technical Information Image 3: SOPAS output format Date: 12.06.2014...

  • Page 10: Behavior In The Case Of An Error

    RFH6xx PNDP Function Block Technical Information 4.3 Behavior in the case of an error If there is a wrong input value or a wrong input circuit of the function block, an error bit (ERROR) is set and an error code (ERRORCODE) will be given out. In this case there is no further processing.

  • Page 11: Value Transfer

    Technical Information 4.5 Value transfer The data function block “SICK RFH DATA” (DB73) contains input and output parameters of all supported function block actions. The data function block can be re-named according to the user program. The data structure is pre-defined and must not be changed (except for the last entry (ReadingResult.arrResult) (see chapter 4.6: Receipt of read results >...

  • Page 12: Mode

    RFH6xx PNDP Function Block Technical Information 4.5.1 Mode The RFH can communicate only with one transponder at the same time. Therefore, reading and writing orders are always executed in an address. In order to identify the transponders, the UID (Unique Identifier) is being used. In order to determine with which transponder the UID should communicate, the function block supports two modes: Mode 1: It is always communicated with the transponder that is actually in the reading field.

  • Page 13: Lock Block

    RFH6xx PNDP Function Block Technical Information 4.5.2 Lock block With the help of the Lock Block Action you have the possibility to save any block on the RFID tag from re-writing. The block number has to be inserted via the parameter iLockBlock before carrying out the function block action.

  • Page 14: Read Tag

    RFH6xx PNDP Function Block Technical Information 4.5.4 Read Tag The Read Tag action reads a defined data area of the tag. This action can only be done for one tag. With which transponder should be communicated, depends on the selected mode (see chapter 4.5.1).

  • Page 15: Free Command

    RFH6xx PNDP Function Block Technical Information 4.5.6 Free Command With the help of a free command you have the possibility to communicate via a valid CoLa command with the RFH. Hence it is necessary to store the command in the parameter “arrCommand”...

  • Page 16: Receipt Of Read Results > 200 Byte

    500 bytes, but it has to be larger or equal to the length of the “ReadingResult.arrResult”. Image 7: Receipt of read results > 200 Bytes (change in the FB declaration) The new defined array lengths have to be inserted into the network 3 of SICK RFH6XX PNDP function block. Date: 12.06.2014...
  • Page 17 RFH6xx PNDP Function Block Technical Information Image 8: Receipt of read results > 200 bytes (change in the UDT code) After the change the instance of the function block has to be updated. Afterwards the changed UDT as well as the function block have to be transferred to the PLC together with the updated instance.

  • Page 18: Parameter

    RFH6xx PNDP Function Block Technical Information 5 Parameter Parameter Declara- Data Storing Description tion type area INPUT BOOL I,M,D,L, Enable entry (KOP and FUP) Const. IN_ADDR INPUT WORD I,M,D,L, Projected starting address of the E-area Const. of the chosen module. IN_LEN INPUT I,M,D,L,...
  • Page 19 RFH6xx PNDP Function Block Technical Information Parameter Declara- Data Storing Description tion type area WR_TAG INPUT BOOL I,M,D,L, Writing tag contents. Const. Therefore it is necessary that the pa- rameters of the structure „WriteTag“ are assigned with valid values (see chapter 4.5.5).
  • Page 20 RFH6xx PNDP Function Block Technical Information Parameter Declara- Data Storing Description tion type area RESET INPUT BOOL I,M,D,L, Resets the communication to the de- Const. vice. DATA INPUT BLOCK_ Const. Transfer of the respective UDT which is necessary for the configuration of the function block and for storing the read results (DB73).

  • Page 21: Error Codes

    RFH6xx PNDP Function Block Technical Information 6 Error Codes The parameter ERRORCODE contains the following error information: Error code Short Description Description W#16#0000 No error No error W#16#0001 Timeout error Order has not been finished within the chosen timeout. This could be because of: - Device is not connected with PLC - Wrong communication parameter - CAN-Bus participant is not available...
  • Page 22 RFH6xx PNDP Function Block Technical Information Error code Short Description Description W#16#000C Reserved Reserved – W#16#000F W#16#0010 Tags in the field > 5 Inventory cannot be carried out since more than (Inventory) 5 transponders are in the reading field of the RFH.
  • Page 23 RFH6xx PNDP Function Block Technical Information Error code Short Description Description W#16#XX19 Transponder error A transponder error has come up. XX = Transponder- / Device errors Transponder errors: 16#00: No error 16#01: Command not supported 16#02: Command nor recognized 16#03: Option not supported 16#0F: Unknown error 16#10: Block not available 16#11: Block already locked...

  • Page 24: Examples

    Byte 258 (W#16#102). The length of the module projected in the hardware config- uration is 32 Bytes. Since the RFH is not in a CAN network, a zero is fixed as CAN-ID. Program selection: Image 9: Example of a SICK RFH6XX PNDP function block Image 10: Step7 Hardware projecting Date: 12.06.2014...

  • Page 25: Reading Out Tag Contents

    RFH6xx PNDP Function Block Technical Information 7.1 Reading out tag contents First of all it has to be decided with which transponder you want to communicate with. If the bit “Mode.bMode = FALSE” it is communicated with the transponder which is in the reading area of the RFID sensor.

  • Page 26: Writing Of Tag Contents

    RFH6xx PNDP Function Block Technical Information The reading action is finished as soon as the bit “bReqDone = TRUE” is signalized. The read tag contents are available in the array “ReadTag.arrData” of the function block. The variable “ReadTag.iDataLength” indicates, how many bytes were received resp. are valid. Image 14: Read tag contents 7.2 Writing of tag contents First of all it has to be decided with which transponder you want to communicate.
  • Page 27 RFH6xx PNDP Function Block Technical Information Start Block: Number of blocks: 3 (Number of blocks to be written) Block size: 4 (depends on the transponder) ’Hello World ’ Data: Image 16: Write Block Parameter The writing action (bWrTag) is carried out as soon as the bit “bRequest” is triggered with a positive edge.

Table of Contents