Troubleshooting
Stop a PanelView Timed Write Corrupting SLC Clock Registers
Short answer
The PanelView's time-status write transmits a two-digit year, so S:37 drops from 2006 to 6 after every update. Point the time and date status tags at an integer file and let ladder logic add 16#2000 to the year before moving the set into S:37 through S:42, or clear the tag entries on the Status Tags tab of the Terminal Setup dialog to stop the write completely.
On this page
The overwrite comes from the PanelView's time-status function, not from the SLC program. PanelBuilder writes the terminal's time and date to whatever addresses its status tags point at, and it transmits the year as two digits: the setup screen displays 2006 while 16#0006 lands in the year register S:37, so about a minute after you set the clock the year falls back to 6. Route the time and date status tags into an integer file, add 16#2000 to the year in ladder, and move the validated set into S:37 through S:42. If the terminal should not set the controller clock at all, clear the tag entries on the Status Tags tab of the Terminal Setup dialog and the write stops.
What the timed write sends #
The PanelBuilder application configures terminal status tags on the Status Tags tab of the Terminal Setup dialog, where you enter or select a tag name for each status option. When the time and date options carry tag names, the terminal refreshes those tags on a fixed timed basis. The year goes out as two digits no matter how the setup screen displays it, which is why reloading the application with the four-digit year setting changed nothing on the controller.
The SLC 5/05 keeps its wall clock in the status file in binary-coded decimal:
| Register | Field | After a manual set | After the timed write |
|---|---|---|---|
| S:37 | Year | 16#2006 | 16#0006 |
| S:38 | Month | 16#0003 | 16#0003 |
| S:39 | Day | 16#0024 | 16#0024 |
| S:40 to S:42 | Hour, minute, second | Valid time | Terminal time |
| S:53L | Day of week | Friday | Saturday |
The day-of-week flip in the same update as the year rollback is the signature of this write: the terminal replaces the whole clock set, S:53L included. If this machine schedules the PLC by day of week from the HMI clock, the wrong date reaches that schedule too, so fix the tag mapping before touching the schedule logic.
Confirm the source before editing #
| Observation | What it tells you |
|---|---|
| Registers hold with the PanelView cable unplugged | The write reaches the SLC over that link; the terminal is the source. |
| Normal tags read and write through the AIC+ converter | The serial path is healthy; the fault is tag mapping, not communications. |
| Four identical machines roll the year back the same way | One shared PanelBuilder configuration causes it; one edit fixes the set. |
| Day of week flips with each write | The whole clock set is replaced, not just the year. |
Set the clock from the programming software's set-time function and watch the registers for one update interval. That single step reproduces the fault on demand without touching wiring, which is why replacing the terminal or the cable is the wrong first move.
Route the write through an integer file #
- In PanelBuilder, open the Terminal Setup dialog and select the Status Tags tab. Point each time and date status tag at words in a spare integer file instead of S:37 through S:42 and S:53L. Use a file dedicated to this transfer so nothing else writes those words.
- In the SLC program, add rungs triggered by a change in the received words. Check each field against its range in BCD: month 16#01 to 16#12, day 16#01 to 16#31, hour 16#00 to 16#23, minute and second 16#00 to 16#59. If any field fails, skip the transfer and leave the clock alone.
- Convert the year, then move the whole validated set into S:37 through S:42 in one scan using MOV instructions, so the clock never holds a half-updated date.
- Save and download the application to one machine, then verify before rolling it out.
The year arithmetic #
The terminal displays 2006; the integer word receives 6, which is 16#0006. Add 16#2000 to it: 16#2000 + 16#0006 = 16#2006, the BCD value the year register holds for 2006. Moving that result into S:37 leaves the year correct after every update. The same addition covers two-digit values 16#00 through 16#99, so the convention holds through 2099.
The received 6 is identical in BCD and binary; 39 is not, since 16#0039 reads as 57 decimal. The first time a two-digit year of 10 or more crosses this link, read the received word in both radices once and convert from the format the terminal actually sends.
Choose this fix when the terminal should stay the time master for the machine.
Disable the write instead #
If the SLC clock should stand on its own, clear the time and date tag entries on the Status Tags tab of the Terminal Setup dialog; a status option with no tag assigned has nothing to write. Download the edited application, set the clock once from the programming software, and the registers hold. The opposite job, setting HMI clock time from PC and PLC daily, applies when the terminal's display clock is the one that drifts. Pick the disable route when logs and schedules must follow the controller and the terminal is display-only for time.
Verify across a full update interval #
- Set the clock, then watch the integer words and S:37 through S:42 together across at least one timed update; the observed cadence here is about a minute.
- The year must still read 2006 after an update, not only right after the manual set, and the day of week must agree with the calendar.
- Confirm normal tag traffic still works between the terminal and the controller.
- If the year still rolls back, compare the integer words against the status registers as the update lands; that shows whether the terminal is still sending two digits or the rungs are moving the wrong word.
- Roll the same application and rungs to the other three machines.
If the program time-stamps alarms or runs shift schedules from these registers, treat the wrong year as a data fault to close before the next shift, not a cosmetic one.
What not to do #
- Do not keep re-setting the clock while the timed write is active; the next update overwrites it again.
- Do not move the raw two-digit year straight into S:37.
- Do not replace the terminal, cable, or converter first; the fault follows the write path and normal tags work.
Questions asked
Why does the PanelView show 2006 while the SLC register holds 6?
The setup screen displays a four-digit year, but the time-status write transmits two digits, and 16#0006 is what lands in S:37. Reloading the application with the year setting on four digits changes only the display, not the transmitted value. Watch the destination word to see what actually arrives.
Can I add decimal 2000 to the received year instead of 16#2000?
No. S:37 stores the year in BCD, so the register must receive 16#2006 for year 2006. Decimal 2006 is 16#07DE, which is not valid BCD, and the clock will read nonsense. Add 16#2000 to the two-digit value so the result is 16#2006 with no carry between digits.
How long does the two-digit year conversion hold?
Adding 16#2000 covers received values 16#00 through 16#99, which is full years 2000 through 2099. When the terminal starts sending 16#00 for 2100, the conversion needs a new rule, so record that limit in a rung comment while you are editing it.
Does changing the update interval solve it?
No. Stretching the interval makes the wrong year arrive less often, but S:37 still falls back to 6 at the next update. Either route the values through an integer file with ladder validation, or clear the time and date tag entries so nothing writes the clock at all.
Why does the day of week change too?
The timed write replaces the entire clock set, S:53L included, so the wrong date drags the day-of-week byte with it. Once validated values reach S:37 through S:42, check S:53L against a calendar; if it still disagrees, set the clock once from the programming software and check again after the next update.