TM172PBG42RI: ERROR reading protection presence

[HuyDinh11]

I have some issue while using this TM172. When the program is clear, the program can download normally. But when I add some status variables, the download start to error like in the photo. What should I do to fix this?

also when I read all parameter in the commissioning tab the variable have this error

[FedericoM]

Hello,

if you can share a project with this error I can have a look at it

[StevenCho]

I am also facing same issue.

But I can't share the program file, because the customer don't share even with me.

I received requests for related verification from two different companies today alone.

[StevenCho]

I wanted to share a temporary workaround for a recent issue I encountered, in hopes it might help others facing a similar situation. Please note that this is based on my personal test results on-site, so I welcome any further insights from the experts here.

Observations:
There seems to be a potential compatibility issue between the built-in firmware version (596.13) of the recently shipped TM172 and previous software versions. Based on my findings, it appears to be a firmware-related behavior that might be resolved by upgrading to the latest software version (1.10.0).

The reasoning behind this assumption:

1. No changes were made to the program file itself.

2. The system worked properly when tested with the previous BIOS version (596.8).

3. The same behavior occurred across two different units on-site.

Temporary Fix : 

Update the Software to 1.10.0, and upgrade both the Target and BIOS to 596.17.

*Note: If you enable 'Run-time check...' in the Project options, a system error WDT:111 may appear after the 'Download All' process is complete.

Troubleshooting Tip during BIOS Upgrade:
When downloading the BIOS on the target device (during 'DOWNLOAD ALL' or 'Write all' on commissioning), I initially couldn't proceed due to a System fault WDT:0 (likely caused by an interruption during the download).

To bypass this, I used the following steps:

1. Downloaded a new, empty project to the device first.

2. Then, proceeded with the BIOS upgrade.

Test Results for Reference

Issue Occurred:

• ESME-HVAC 1.5.0 / 1.6.0 / 1.9.0 → Bios 596.13 / 596.16

Resolved (No Error):

• ESME-HVAC 1.6.0 → Bios 596.08

• ESME-HVAC 1.10.0 → Bios 596.17

If anyone has a deeper understanding of this situation or a better solution, please help.

[FedericoM]

Hello,

I guess the reading protection presence Error is related to a feature added in MSK 596.14 and MSK 668.14.

The library sysProtectionFunction.pll available at C:\Program Files (x86)\Schneider Electric\EcoStruxureMachineExpertHVAC\Catalog\FreeAdvance\PLC allows to define a password to connect to TM172.

If you use a project target >= .14 and you connect to a firmware version <= .13, you might have this error.

Firmware version should be always >= project target version.

Run-time check... should be used only in simulation for debugging purposes, if they are used on a real target they might stop plc execution or a watchdog

At the end of a bios upgrade there is always a WDT:0, it is an expected watchdog, application will restart after 30sec during which all leds will be on.

[StevenCho]

Is it true that the problem I experienced and the problem he experienced are the same?

Based on my test, [ESME-HVAC 1.6.0 → Bios 596.08] was no problem.

[Project target < Firmware version]

Somehow, Issue on 596.13 was solved after update the latest firmware and target.

[StevenCho]

The same issue occurred at another client's site.

80 units of TM172PDG42RI were delivered to the site, and the problem occurred in 5 of them.

Commonly, a System Fault (WDT:0) occurred, just as it did previously (except for one unit, which experienced an infinite reboot).

Temporary fix were taken using the following method.

*Since BIOS updates cannot be performed while WDT:0 is active, the following steps are performed first.

1. Create a new project (Empty Project File) and select Download PLC Code / Download ALL.

2. Download BIOS (From 596.13 to 596.13) - Same version.

3. Download existing program PLC Code → [Commissioning] Write All.

4. Download All.

The current conclusion is that the problem was resolved after Download the firmware of the same version.

By the way, the ESME-HVAC Version is 1.7.0 and Targer project & Firmware are 596.13.

[FedericoM · Accepted solution]

Hello,

I suggest to move to ESME HVAC 1.10, no reason to stay on an older version.

Production line is going to be updated to 596.17

[StevenCho]

I recommend using the latest version, but it seems the update is being delayed because all team members (about 20) need to update for version compatibility.

By the way, is there any additional information available regarding these symptoms?

Additionally, it does not appear to be related to the production lot.

(Occurred in Week 15 of 2024 / Week 25 of 2025)

If this symptom occurs again, I will try to retrieve the product.