This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| cubloc:monitorling:index [2026/03/04 21:14] – admin | cubloc:monitorling:index [2026/03/04 21:18] (current) – [Observing D-Area Double Words] admin | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| You can enter or exit the monitoring mode by clicking the Monitoring ON/OFF switch on the toolbar at the top of the screen. Alternatively, | You can enter or exit the monitoring mode by clicking the Monitoring ON/OFF switch on the toolbar at the top of the screen. Alternatively, | ||
| - | {{ :cubloc:laddermonitoring: | + | {{ :cubloc:monitorling: |
| The following is a screen capture during monitoring. Contacts in the ON state are displayed with a "Green Block," | The following is a screen capture during monitoring. Contacts in the ON state are displayed with a "Green Block," | ||
| - | {{ :cubloc:laddermonitoring: | + | {{ :cubloc:monitorling: |
| The status of I/O ports is displayed at the bottom of the screen. Ports that are ON are displayed in blue bold text. Only ports from 0 to 63 are shown. | The status of I/O ports is displayed at the bottom of the screen. Ports that are ON are displayed in blue bold text. Only ports from 0 to 63 are shown. | ||
| Line 20: | Line 20: | ||
| When you want to view the contents of a specific relay or memory address, use **WATCH POINTS**. In an empty area of the LADDER, type two consecutive " | When you want to view the contents of a specific relay or memory address, use **WATCH POINTS**. In an empty area of the LADDER, type two consecutive " | ||
| - | {{ :cubloc:laddermonitoring: | + | {{ :cubloc:monitorling: |
| ===== Observing D-Area Double Words ===== | ===== Observing D-Area Double Words ===== | ||
| Line 26: | Line 26: | ||
| A Double Word represents two words as a single value. By typing **'' | A Double Word represents two words as a single value. By typing **'' | ||
| - | {{ :cubloc:laddermonitoring: | + | {{ :cubloc:monitorling: |
| ===== Forced I/O ===== | ===== Forced I/O ===== | ||
| Line 36: | Line 35: | ||
| Disabling the force mode returns the ladder to its original logic execution. All Forced I/O settings are cleared when the power is turned OFF. | Disabling the force mode returns the ladder to its original logic execution. All Forced I/O settings are cleared when the power is turned OFF. | ||
| - | {{ :cubloc:laddermonitoring: | + | {{ :cubloc:monitorling: |
| The Forced I/O function can be used when operation is hindered due to a sensor failure. By forcibly setting the problematic port to ON or OFF, you can continue to verify the PLC's operation. | The Forced I/O function can be used when operation is hindered due to a sensor failure. By forcibly setting the problematic port to ON or OFF, you can continue to verify the PLC's operation. | ||
| Line 46: | Line 45: | ||
| During online monitoring, if you double-click (or right-click) a location displaying a D-area value, as indicated by the arrow in the figure below, the **MODIFY** window will appear. | During online monitoring, if you double-click (or right-click) a location displaying a D-area value, as indicated by the arrow in the figure below, the **MODIFY** window will appear. | ||
| - | {{ :cubloc:laddermonitoring: | + | {{ :cubloc:monitorling: |
| You can change the contents of the D-area at will during operation. If another part of the ladder logic is updating that specific D-area, the changed value will not be maintained. This operation is executed only once and does not forcibly hold the value. | You can change the contents of the D-area at will during operation. If another part of the ladder logic is updating that specific D-area, the changed value will not be maintained. This operation is executed only once and does not forcibly hold the value. | ||