Explainer
Selecting and starting a DX200 robot job from an HMI
Short answer
A DX200 selects a job for an HMI only through its documented Job Select command, 0x87, covering tasks 0 through 15 on the high-speed Ethernet server function; if the installed driver does not expose that service, a robot-side job must interpret the request. Gate every start request on reading back the accepted job, because selection and execution are separate controller conditions.
On this page
- What the controller side provides
- Why a working link proves nothing
- Check one: prove the transport with data
- Check two: choose the selection route
- Check three: meet the start conditions
- The read-back handshake
- Worked example: selecting one job on task 0 from a GP-Pro EX v4.0 screen
- Commissioning order, and the one safety rule
- When neither route is documented
- Questions asked
Yes, an HMI can select and start a job on a DX200 — but only through the controller's documented job-select service, and execution is a separate controller condition on top of that. The DX200 interface lists a Job Select command, 0x87, that sets the executing job and the master job for tasks 0 through 15, reached over the high-speed Ethernet server function. A screen can use that service only if the installed driver actually issues it: a working Ethernet connection and a button that animates prove neither the selection path nor the start conditions. Commission the job as three separate checks — transport, selection interface, remote-start conditions — and gate every start request on reading back the job the controller accepted. Where the driver exposes no job-selection function, the selection runs inside a robot-side job that interprets a request word, because writing a number into ordinary data never selects a job by itself.
What the controller side provides #
Third-party communication with a DX200 runs on the high-speed Ethernet server function. Mitsubishi's MELSEC iQ-R simple device communication manual, written for its own PLCs, sends DX200 traffic to that same server function — a useful third-party confirmation that this is the documented entry point.
The Yaskawa robot-controller interface documentation for the DX100/DX200/FS100/YRC1000 family lists a Job Select command, 0x87, whose instances set the executing job and the master job across tasks 0 through 15. The controller offers the service; the question is who is able to issue it.
One version gate applies before anything else. Yaskawa's sample project for connecting a DX200 to GP4000/SP5000 series panels requires "High-speed Ethernet" functionality version DS1.00-00 or later. Read the installed version first: below DS1.00-00, the documented panel route is off the table and only the controller-resident route remains.
Why a working link proves nothing #
A driver that reads status, alarms, and I/O is not automatically an implementation of every service the interface offers. The pattern is common across controllers: this same DX200 offers an EtherNet/IP path whose adapter side requires a Class 1 implicit connection, and drivers exist that cannot form one — they exchange data elsewhere and never connect there. "The connection works" and "the HMI can select a job" are different claims.
The test is binary and takes minutes: open the driver's device documentation and read its function list. Either a job-selection function for this controller family is listed with its arguments, or it is not. If it is not, register guessing produces nothing supported; the legitimate routes are a driver that documents the service, or controller-side logic. Get written confirmation from the HMI vendor's and the robot vendor's support channels, and treat the answer as an interface specification, not as codes to paste into a screen.
Check one: prove the transport with data #
Ping proves IP reachability and stops there. Prove the transaction layer with items the documentation names:
- Read a documented status item onto a temporary screen, change its condition through a normal operating action, and watch the value move.
- Write a documented writable item that commands no motion, and confirm the value at the controller, not only on the screen.
- Classify every failure by layer: a timeout is an endpoint or service-setting problem; a value that changes in the controller but stays stale on the screen is a binding, data-type, or addressing problem; a write that succeeds and changes nothing about the job is a command-semantics problem.
That layer separation is the same discipline as diagnosing intermittent HMI to PLC Ethernet comms hangs: name the layer that failed before touching the next one. Move on to job selection only when both the read path and the write path are proven.
Check two: choose the selection route #
| Route | What it needs | When to take it |
|---|---|---|
| Direct selection | The driver exposes the job-select service — command 0x87 over high-speed Ethernet — with its task and instance arguments, and the controller functionality is DS1.00-00 or later | The driver's function list names job selection |
| Controller-resident selection | A documented writable request item plus a robot-side job that reads it, performs the selection, and presents the accepted job for readback | The driver only exchanges data — the common case |
Take the direct route when it is documented: one command, one result, no controller changes. Otherwise commit to the controller-resident sequence instead of hunting for undocumented codes. Map every operator choice to a commissioned job, define how an out-of-range number is rejected, and decide how the controller reports the job it accepted. That mapping is an integration change owned with the robot integrator, and it works with any panel that can read and write two items.
Check three: meet the start conditions #
Job selection sets the job; it does not run it. Expect a correctly selected job to sit idle until the controller is in a state that permits an external start: the operating-mode selection, the remote or local selection, and servo power, as the controller's operating documentation defines them. Those are controller settings — no screen logic substitutes for them, and the start object stays inhibited until controller status says execution is permitted.
Sequence the two requests separately: selection accepted first, start request second, then a controller status that shows execution. A screen that reports success because a button was pressed tells the operator three things that may all be false: that the link worked, that the job was accepted, and that motion began.
The read-back handshake #
Use two design words and nothing else: REQ, an HMI word where 0 means no request and 1 through N name the commissioned jobs, and FBK, the readback of the job the controller reports as selected.
- The operator picks from a restricted list; the HMI writes REQ.
- The selection acts on REQ — the driver's job-select service, or the robot-side job — and returns its command result.
- The HMI reads FBK. The start object enables only when FBK = REQ and REQ is not 0.
- Clear REQ on the documented acknowledgment sequence, and define the timeout behavior so a retry cannot repeat an action unnoticed.
Give the operator five distinct indications: communication failed, selection rejected, selection accepted, start inhibited, executing. One indication per decision is the separation that designing HMI screens for clear operator decisions is about, and it is what tells the operator whether to look at the link, the request, or controller readiness.
Worked example: selecting one job on task 0 from a GP-Pro EX v4.0 screen #
Inputs, with where each comes from:
- HMI project: GP-Pro EX v4.0 with a high-speed Ethernet connection to the DX200 — the configuration being commissioned.
- Controller function: the DX200 high-speed Ethernet server function; the documented panel route requires "High-speed Ethernet" functionality version DS1.00-00 or later.
- Selection service: the same Job Select command described above, applied here to a single target job on task 0.
- Target: one particular job, requested as REQ = 1, applied to task 0 — inside the documented task range.
The rule in words: direct selection is available only when the functionality version is DS1.00-00 or later and the driver exposes the job-select service; the start object enables only when the readback equals the request.
The arithmetic:
- The command number is hexadecimal: 0x87 = 8 × 16 + 7 = 135, the service identifier the interface documentation lists for job selection.
- The task range spans 15 − 0 + 1 = 16 slots, and task 0 is the lowest-numbered one.
- Acceptance: REQ = 1 with FBK = 1 gives 1 = 1, so the start object enables; REQ = 1 with FBK = 0 fails the match, so the screen reports selection rejected and the start stays inhibited.
Decision: at DS1.00-00 or later with a driver-documented job-select function, take the direct route — one command, then readback. With either condition missing, take the controller-resident sequence: the HMI writes REQ = 1, a robot-side job performs the selection, and FBK = 1 is the gate. The threshold is the same either way: no start while FBK does not equal REQ.
Commissioning order, and the one safety rule #
- Read the "High-speed Ethernet" functionality version against the DS1.00-00 floor.
- Prove the read path with a documented status item.
- Prove the write path with an item that commands no motion.
- Prove selection and readback with servo power off.
- Prove the start with the integrator present, in the operating state that permits external start.
Prove steps 2 through 4 with servo power off or the cell guarded at reduced speed, and never use a start request as a communications test: the HMI requests, hardwired safety decides.
When neither route is documented #
Ask both vendors in writing whether the installed driver issues the DX200 job-select service, and at which functionality version; the two documents that answer it are the driver's device documentation and the robot-controller interface manual for the family. Switching HMI brand changes nothing unless the new driver documents the service for this controller — that single line in the function list is the whole question. The controller-resident sequence, agreed with the integrator, works with any panel that can read and write the request and feedback items, and it is the faster documented path.
Questions asked
Does a ping to the DX200 prove the HMI can select a job?
No. Ping proves IP reachability, nothing more. Job selection rides on the controller's high-speed Ethernet server function and needs the driver to issue the documented Job Select command, 0x87, for tasks 0 through 15, and the controller to accept it. Prove the path by reading a documented status item and writing a harmless non-motion item before any command test.
Which functionality version does the DX200 need for the documented panel route?
Read the installed "High-speed Ethernet" functionality version before anything else: the requirement stated above, DS1.00-00 or later, is the floor. Below that level the documented panel route is not available, and selection has to run through a robot-side sequence that interprets a request word instead.
Can I select a job by writing a job number into a controller register?
Not by itself. A value in an ordinary data item stays data until controller logic passes it to the job-select service. Map the number in a robot-side job that reads the request, performs the selection through the supported service, and presents the accepted job for readback, so the screen can prove acceptance before any start request exists.
Why does the job select but not run?
Selection and execution are separate. The Job Select command sets the executing or master job; motion begins only when the controller is in the state that permits an external start, which its operating documentation ties to the mode selection, the remote or local selection, and servo power. Those are controller settings, and the start object should stay inhibited until controller status confirms them.
Would changing HMI brand make job selection work?
Only if the new driver documents a job-select service for this controller family. That single line in the driver's function list is the whole question: a different brand with the same data-only driver reproduces the same limitation, while a controller-resident selection sequence works with any panel that can read and write the request and feedback items.