General information for using the fieldbus board.
This is part of the YRCP-MP4P EtherCAT quick start guide.
Yaskawa YRCP-MP4P fieldbus board.
Details
created: 2025-10-24
changed: 2026-03-31
files:
board:
firmware:
version: 2024.0.7.170010 # or newer
file: yrcp-mp4p-2024.0.7.170010.raucb
default_credentials:
user: admin
password: 00000000 # or see the board's sticker
default_ip_addresses:
X1_X2: 192.168.3.1
X3_X4: 192.168.1.1
robot_controller:
system_software:
YRC1000: YAS5.70 # or newer
YRC1000micro: YBS4.25 # or newer
driver:
version: 1.2.0.47 # or newer
file: TRITON.DRV
fieldbus_file:
type: esi
file: YASKAWA-YRCP-MP4P.xml
Firmware releases
Read more...
v2024.0.7.170010
2025-08-07
Fix for bug which could occasionally prevent the board to reach the
operational state after booting the robot controller. Remedy was to restart the
robot controller another time.
Adds support for EtherCAT slave (SubDevice). This requires at least robot system
software YAS5.70.00A for YRC1000 or YBS4.25.00A for YRC1000micro.
v2024.0.4.123413
2025-04-16
Initial release.
SKUs
We have created three SKUs (stock keeping unit) for the board, with each one
having specific features.
Below table helps to pick the right one for your application. SKUs are listed for
Yaskawa Nordic (YNR) and Yaskawa Europe (YEU).
Fieldbus
YNR
YEU
Feat: Master
Feat: Slave
Feat: Safety slave
PROFINET
347916210
11240436
✔️(“IO-Controller”)
✔️(“IO-Device”)
❌
PROFINET
347916212
11242717
✔️(“IO-Controller”)
✔️(“IO-Device”)
✔️(“PROFIsafe-Device”)
EtherCAT
347916120
11240437
❌
✔️(“SubDevice”)
❌
Note
SKUs with safety functionality are licensed and include a license sticker,
which gets applied to the inside of the robot controller cabinet’s door.
Configurations
The board supports the following EtherCAT configurations:
Slave (SubDevice)
Note
The slave can be configured as one of the following data packet sizes:
2b, 4b, 8b, 16b, 32b, 64b, 128b, 256b, 436b, 440b and 512b*.
* Depending on the type of robot controller, installed option boards and activated option functions,
some of the larger data packet sizes might be invalid for your robot setup.
Important
Master (MainDevice) or safety slave (FSoE) are currently not supported.
Mount the board
It is a PCIe (PCI express) board, and can be can be mounted in either the
left or right PCIe slot of the robot controller.
Connect the EtherCAT cable(s)
Important
The YRCP-MP4P board is having a 2x2 ports configuration.
This means that there are two physically separated networks
(each with 2-port switch).
The functionality for the two networks is defined as follows:
Port X1, X2 (upper ports): EtherCAT SubDevice. These are used for the network where the robot controller is a slave
(and connected to a master such as a PLC).
Port X3, X4 (lower ports): not used.
Board firmware
Note
It is advised to use the latest board firmware
(see version information at the
top
of this document).
Check version
Start the robot controller (maintenance mode).
Access the webserver of the board (web based management, WBM) by entering one
of the given IP addresses in a webbrowser (default IP addresses:
here
).
As it is not using encryption (using HTTP instead of HTTPS), it might get
blocked with a message like this:Browser security warning.
Proceed by clicking Continue to xxx.xxx.xxx.xxx (unsafe)
The actual firmware version is shown (in short notation) in the main screen’s
top right corner:Version info shown on the main screen.The more detailed notation of the firmware version is shown in
Menu Overview » General Data:Detailed version info.
Update process
Follow above steps for checking the firmware version.
Open the firmware page using menu Administration » Firmware update
Click Browse to select the new firmware file (.raucb) on your PC.
It will then show up:Firmware selection.
After clicking Start Update, the file will be uploaded to the board.Firmware transfer (upload) progress indicator.
After finishing the transfer, the board will install the new firmware.
During this process, the webserver is not accessible:Webserver connection lost.
The installation should take no more than five minutes.
If everything went well, the webpage will automatically reloaded and display
the login screen. Login and verify if the new firmware version is shown.
Troubleshooting
Factory reset
If you have the feeling the board is not behaving normally, you might want
to try a clean setup by doing a factory reset.
This is easy to do using the board’s webserver.
Read more...
Unplug all network cables from the board.
Connect a direct network cable from your PC to one of the board’s ports.
Start the robot controller (maintenance mode).
Access the webserver of the board (web based management, WBM) by entering
the IP address for the connected port in a webbrowser.
As it is not using encryption (using HTTP instead of HTTPS), it might get
blocked with a message like this:Browser security warning.
Proceed by clicking Continue to xxx.xxx.xxx.xxx (unsafe)
Open the cockpit screen:
Menu Overview » Cockpit:Reset the controller to factory defaults.
Click on the icon to perform the facory reset:Icon of factory reset button.
The reset should take less than one minute.
By trying to access the webserver (this time using the
default IP address
for the connected port), you can verify the board is back alive and the reset
process has completed.
Reboot the robot controller (maintenance mode).
Redo the robot settings for the board.
Replug all network cables.
Reboot the robot controller (online mode) and verify the communication is ok.
Note
If you are not able to access the board’s webserver you can also perform the
factory reset by using DIP switch S2 on the board. For more information please
refer to the board’s manual (HB170E_PCIe_YRCP32F0_xx-xx.pdf).
