-
Notifications
You must be signed in to change notification settings - Fork 2
Controller Setup Verifying
戴梓恆 (TAI TZU-HENG) edited this page Aug 31, 2026
·
1 revision
netstat -ano | findstr "18735 18736"
Both should show LISTENING (only 18735 if you're only using S8). The
PID corresponds to the virtual controller's process, checkable against
Robot_1\services.txt to confirm it's the same workcell.
fanuc status
Seeing driver: fanuc-driver 0.2.0 means the extended driver is
active, not just an upstream connection. If typing connection
parameters (--host/--port etc.) every time is annoying, save them
with fanuc connect set first, see the command-line section in
README.md.
| Symptom | Cause |
|---|---|
WinError 10061 |
port not LISTENING. ROBOGUIDE isn't open, MAPPDK isn't running, or the tag number doesn't match the driver, see server tags |
PROG-048 Released [SHIFT] key |
running in T1/T2, switch to AUTO |
INTP-106 Cannot execute program |
the program is stuck PAUSED with an uncleared error; ABORT first, then RESET
|
MCTL-003 System is in error state |
press RESET; if it persists, check the e-stop and fault state |
| TP shows started but the port isn't open | the tag number doesn't match SERVER_TAG_NUM in the driver source |
| 18735 reachable, 18736 isn't | S7 wasn't configured or started, or line 2 (RUN MAPPDK_LOGGER) was deleted from MAPPDK
|
No KAREL Programs under Type
|
the R632 option isn't installed, see prerequisites |
fanuc status shows the upstream version (not fanuc-driver x.x.x) |
an old or upstream .pc got loaded; reload the files from driver/upload/
|
Something's stuck, or the Python side just isn't responding:
AUX → ABORT, then rerun MAPPDK following running it.
Last updated: 2026-08-31
Controller Setup
Protocol
- Overview
- Commands (Upstream)
- Commands (Extended)
- Wire Format
- Connections
- Errors
- Driver Limits
- Reserved Resources
- Extending the Driver
- Debugging Notes
控制器設定
協定