PlcConsoleSafety and Troubleshooting
Use this page before controlling live equipment and when a PLC command does not behave as expected.
Operating Notes
PlcConsole is for Fatek PLC FBs Series devices with a reachable network adapter. Keep the iPhone or iPad and PLC on a network path that permits TCP access, use the PLC IPv4 address, configured port and correct station ID, then run Test Connection Info before activating a new or edited profile.
PlcConsole uses short-lived PLC sessions and serializes normal commands. It is not a permanent connection monitor. Do not issue the same operation from other software at the same time when the PLC Ethernet module has limited socket capacity.
Troubleshooting Flow
When a command fails, read the PLC Command Failed popup and the screen's Last Error section. Check PLC power, IP address, port, station ID, local network routing and whether the Ethernet module is responding. A timeout means the endpoint did not respond in time; wait for socket resources to clear or power-cycle the Ethernet module if repeated attempts have left it unresponsive.
Use Diagnostics Loopback when an active profile needs a small end-to-end echo check. Use PLC Status for flags and capacity. Disconnect before switching to another PLC profile; this resets command results and errors from the prior profile.
Control Safety
Read commands are observational; write, control, batch and Site Automation actions can change PLC state. Confirm the selected register, value and target equipment before sending a command. PlcConsole does not add an automatic readback after a write.
Keep physical safety, output interlocks, motor protections, timers and safe failure behavior in PLC ladder logic. Site Automation action mappings are intended for M and S helper registers, not direct physical-output control.
Watchlist and sensor auto-refresh run only while the relevant screen and app are active. They do not provide background supervision or alarm delivery.