Resolving RF380R Gen2 E6FE_0300 Error on S7-1200 TIA Portal V14

Problem Summary

A Siemens S7-1200 DC/DC/Rly CPU is configured with an RF180C communication module and an RF380R Gen2 RFID reader. The project is built in TIA Portal V14 SP1 using the SIMATIC Ident technology object SIMATIC_IDENT_1. After loading the hardware configuration, adding the IO device, and triggering the Reset_RF300 instruction once with default parameters, the technology object raises the error identifier E6FE_0300 (hex) and the reader never transitions to a ready state. The same behavior occurs with the general Reset_Reader block, and the project is on recently purchased hardware (≤ 2 months from shipment).

The fault is not a wiring or power problem (LEDs are functional and the reader is recognized once plugged in), but a parameter profile mismatch between the technology object configuration and the physical RF380R Gen2 firmware. Selecting the RF300 general reader profile instead of the explicitly named RF380R Gen2 profile restores normal operation. The remainder of this document explains the fault code, the configuration path that produced it, and the diagnostics that confirm the fix.

System Topology and Hardware Configuration

The complete physical and logical topology is shown below. The CPU exchanges identification data with the RF380R Gen2 over an RS422 point-to-point link carried through the RF180C communication module, which itself appears as a PROFINET IO device on the CPU's PROFINET interface.

The submodule structure reported by the device configuration must match the topology. The expected assignment in this case is:

Error Code E6FE_0300: Definition and Causes

The error identifier 0xE6FE_0300 is reported by the SIMATIC Ident technology object / FB error interface. The high word 0xE6FE is the IDENT technology object class, the low word 0x0300 is the offset that maps to "reader initialization failed / parameter set rejected" in the SIMATIC Ident Function Manual. In practical terms the reader handshake never completes because the controller and the reader do not agree on the parameter profile (MOBY mode, air-interface parameters, channel selection, antenna power).

When 0xE6FE_0300 is raised, the technology object stops the handshake and never transitions to STATE_RUN. Calling Reset_Reader clears the bit but the next Ident_Start reproduces the same fault because the underlying parameter block is still wrong. You must fix the configuration, not just the fault state.

Technology Object Configuration in TIA Portal V14 SP1

The technology object is created with Add new technology object → SIMATIC Ident → SIMATIC_IDENT_1. The default parameter page forces the engineer to pick a reader family that maps to a parameter profile stored in the technology object. The parameter values that produced the fault in the original case were:

The single change that resolved the fault was the reader family selection. RF300 general is the more permissive profile that does not assert Gen2-specific air-interface timing; it allows the firmware on a Gen2 reader to negotiate the parameter set successfully and lets the user keep the MOBY mode, the 115.2 kbaud rate, the 1.25 W power, and the locked RF300 transponder mode. With the working profile, the D400 transponders respond correctly because D400 is fully ISO 15693-compliant and the RF300 profile family includes ISO 15693 support.

Root Cause Analysis

Three pieces of evidence converge on the profile mismatch:

1. Fault appears immediately on the first Reset_RF300 call. A wiring or power fault would either not raise an E6FE code at all (the technology object would remain in STATE_STARTING) or would raise 0xE6FE_0200 (reader not reachable). The fact that the reader is recognized once plugged back in (after the user briefly disconnected it) rules out cabling and confirms the link layer is healthy.
2. The hardware identifiers are all valid. HW IDs 272–277 are within the range the technology object expects for an RF180C; the technology object accepts them and proceeds to parameter negotiation. The handshake fails at the parameter stage, which is exactly where 0xE6FE_0300 is reported.
3. Changing the reader family clears the fault without changing any other parameter. Baud rate, power, MOBY mode, and continuous-mode flags were kept identical. Only the family selector changed. This is the classic fingerprint of a profile mismatch: the lower-level transport works, the upper-level parameter block does not.

Reviewing the broader Siemens Ident documentation, RF380R Gen2 readers ship with a newer firmware that no longer fully matches the original "RF380R Gen2" profile slot inside TIA Portal V14 SP1's technology object (the slot was authored against an earlier Gen2 firmware revision). When V14 SP1 pushes the legacy parameter block, the Gen2 firmware rejects one or more fields (typically antenna multiplexing timing) and returns the E6FE_0300 condition. Selecting the more conservative RF300 general profile pushes a smaller, accepted parameter block and the reader initializes cleanly.

HW ID Assignment Diagnostics

Before changing the profile, capture the HW ID map from the device configuration. This is essential because the technology object's IO data tab must reference HW ID 277 (2x_RS422_channels_RFID_1), and the user program may also reference IDs directly.

1. Open the PLC in Devices & Networks.
2. Select the RF180C in the network view; the device view lists all submodules and their automatic HW IDs.
3. Open Properties → System constants on each submodule and confirm the symbol is usable from the user program. The expected symbols are HWID_RFID_1_Interface (273), HWID_RFID_1_Port_1 (274), HWID_RFID_1_Port_2 (275), HWID_RFID_1_Head (276), and HWID_RFID_1_Channel (277).
4. Open the technology object SIMATIC_IDENT_1, go to Configuration → Hardware assignment, and select HW ID 277 as the connected module.

If the technology object was accidentally assigned HW ID 276 (rf180c~Head) the same E6FE class of fault appears, but with 0xE6FE_0100 rather than 0x0300. Verify the assignment before assuming the profile is wrong.

Reset_RF300 Block and RF_POWER Parameter

The Reset_RF300 (or Ident_Reset) block is called once at startup to bring the reader to a defined state. The block has the following input interface (SCL):

Reset_RF300_DB(
    REQ        := bStartReset,        // rising edge triggers reset
    ID         := HWID_RFID_1_Channel, // HW ID 277
    LADDR      := 16#0000,            // optional alternative to ID
    GROUP      := 1,                  // reader group
    RESET_TYPE := 0,                  // 0 = reset, 1 = factory reset
    RF_POWER   := 16#05,              // antenna power 0x02..0x08
    BUSY       => bBusy,
    DONE       => bDone,
    ERROR      => bError,
    STATUS     => wStatus);           // 0xE6FE_0300 reported here

The RF_POWER input controls the radiated RF power in discrete steps. The valid range is 0x02 (low) to 0x08 (max). The default value pushed by the technology object is 0x05 (1.25 W). If you observe a related but different fault such as 0xE6FE_0400 after the profile change, the cause is usually an out-of-range RF_POWER value written from the user program. Clamp the parameter to 0x02–0x08 before re-running the reset.

Resolution: Reader Profile Selection

Apply the following steps to clear 0xE6FE_0300 on this hardware combination:

1. Open the project in TIA Portal V14 SP1 and go online to the CPU to read the current STATUS of the technology object. Confirm the value is 16#E6FE_0300.
2. Go offline. Open SIMATIC_IDENT_1 in the project tree.
3. Navigate to Configuration → Interface → Reader.
4. Change the reader family from RF380R Gen2 to RF300 general. Keep the channel on Channel 1, the profile on RFID Standard Profile, the MOBY mode on RF200/300 etc MOBY mode, the baud rate on 115.2 kbaud, continuous mode On, single-tag mode Off, and RF power at 1.25 W.
5. Compile the project (HW + SW) and download to the CPU.
6. Restart the CPU (STOP → RUN) or call Reset_RF300 with RESET_TYPE = 0.
7. Monitor STATUS for a transition to 16#0000_0000 (no error) and the technology object's state field to STATE_RUN.

The transition state diagram for the fix is shown below.

Library Version Migration Path

TIA Portal V14 SP1 ships with the SIMATIC Ident library that contains both the technology object type and the classic function blocks (FB) Ident_Profile, Ident_Read, Ident_Write, and Reset_Reader. Two parallel usage models are supported:

• Technology object (recommended) — easier diagnostics, automatic HW ID linking, but requires the parameter profile in the TO to match the reader.
• Classic FB interface — manual command/response handling, but more tolerant of mixed firmware because each parameter is set individually.

If the technology object path keeps producing faults (e.g. after a TIA Portal upgrade or after a reader firmware upgrade), migrate to the classic FB interface. The migration steps are:

1. Install the matching SIMATIC Ident library version in TIA Portal. Library v4 of the Ident blocks is the version that pairs reliably with the RF380R Gen2 firmware used in this case.
2. Open the library and drag Ident_Profile, Ident_Read, Ident_Write, and Ident_Reset into the project. Each block instantiates its own background DB.
3. Set HWID on each block to the system constant HWID_RFID_1_Channel (HW ID 277).
4. Call Ident_Profile once at startup to push the profile (channel, MOBY mode, baud rate, RF power). The profile word matches the same parameters previously set in the technology object.
5. Use Ident_Read / Ident_Write in OB1 to handle transponder access.

With the classic FB interface, a profile mismatch is reported as a per-block STATUS value rather than as a technology object fault, and the engineer can iterate on individual parameter words without deleting the technology object. This is the recommended fallback when the TIA Portal V14 SP1 technology object cannot negotiate with a new reader firmware revision.

Transponder Compatibility with D400

The application uses Siemens D400 transponders. D400 transponders are ISO 15693-compliant 16 KB memory tags (organized as 64 blocks of 4 bytes). They are fully supported by the RF300 family readers and by RF380R Gen2 readers operating in RF300 / ISO 15693 mode.

Selecting the RF300 general profile does not restrict the application to RF300-only tags; it simply selects the air-interface protocol that the RF380R Gen2 reader will negotiate. D400 transponders continue to work. If at a later point the project needs to read MOBY E tags or other families, a separate profile is required.

LED Status Verification

Once the profile change has been downloaded, the LED pattern on the RF180C and RF380R reader must be verified. The following table lists the expected status:

Any red LED on the RF180C, or a flashing MT LED on the RF380R, indicates the parameter profile is still in negotiation or has been rejected. Repeat the reset sequence and re-check STATUS.

Verification Procedure

Run the following verification after the profile change to confirm the fix is durable:

1. Online status check. In TIA Portal, go online with the CPU, open Watch table with the technology object tags. Confirm STATUS = 16#0000_0000, STATE = 5 (STATE_RUN).
2. LED check. All RF180C and RF380R status LEDs green as listed above.
3. Presence check. Place a D400 transponder inside the RF field and call Ident_Read (or READ on the technology object). Confirm a non-zero UID is returned and STATUS remains 16#0000_0000.
4. Power cycle test. Power down the RF180C and the RF380R reader for at least 10 seconds, then power up. Confirm the technology object reaches STATE_RUN automatically without a manual reset call. If a manual reset is still required, the issue is the user program, not the profile.
5. Cold restart of the CPU. Run MRES on the S7-1200 CPU. After restart, the reader must reach STATE_RUN within 3 seconds. If 0xE6FE_0300 returns, repeat the profile change and recompile.

Troubleshooting Matrix

Use the following matrix to triage similar faults in the same family of components.

Long-Term Recommendations

To avoid repeating this issue on future RF380R Gen2 deployments:

• Use the classic FB interface for new projects where the reader firmware is unknown or may change. The FB interface is more explicit and decouples the application from the technology object's profile assumptions.
• Pin the SIMATIC Ident library version in the TIA project archive and document the matching TIA Portal service pack and the reader firmware revision. Siemens periodically updates the library; upgrades can shift the default profile slot for RF380R.
• Document the working profile in the project HMI / SCADA help so that maintenance engineers know to keep the "RF300 general" family selected unless the application explicitly requires RF380R Gen2 features.
• Build a startup test in OB100 that checks STATE = 5 within 5 seconds and raises a maintenance alarm if the technology object is still in STATE_STARTING. This catches profile mismatches at commissioning instead of in production.