- HMI Model: cMT3102xV2
- EasyBuilder Pro Version: 6.09
I am trying to setup a connection between a cMT3102xV2 and an Epson VT6L robot using the Epson Robot Controller device driver in EBPro. If any objects on the screen are reading from/writing to addresses from the controller, the communication fails.
The controller gets assigned as local device 4 and displaying LW-9403 shows error code 2.
IP address and port number in Epson RC+ and EBPro match, and I have tried with and without a password set. I’m not really sure what else I am missing.
Only thing that I haven’t look into yet is the memo for the login bit in the connection guide which says “Set 1 (Initialization)”. There is documentation from Epson showing a login process from remote ethernet control, but I’m not sure how i can set the bit to 1 if I’m not connected to the device.
The step-by-step communication settings in EPSON Software may be the following:
- In the software, create a project
- Go to [Setup] menu on the toolbar → [System Configuration]
- Go to [controller]→ [Configuration] in the tree view
- Set up the settings as follows
Name: Input the project name
IP address: in this case, 192.168.1.131
IP mask: 255.255.255.0
IP gateway: 0.0.0.0
USB speed: Auto
Control device: Select Remote Ethernet
Click [Apply] to confirm.
- Go to [Controller]→[Remote Controller]→ [Ethernet] in the tree view
- Set up the settings as follows
TCP/IP Port: 5000
Terminator: CRLF
Timeout: 60.00
Password: Input the password you want. You will enter the same password in EasyBuilder Pro
Use only for monitoring: clear the check box. (disabled)
Click [Apply] to confirm.
- Click [Close] and restart the controller.
Regarding the “login” bit in the connection guide which says “Set 1 (Initialization)”, I guess you will create a Set Bit object addressed to this controller bit in your EBpro project. Then at runtime you will touch the Set Bit button to turn it on.
Thank you for the reply.
I had these setting near exact (just a different IP address), and still couldn’t get a response.
I switched to using Modbus TCP/IP which the Epson controllers natively support and this seems to work as expected after getting the right addresses. This is more the behavior I wanted anyways so this should work fine for my application.
A note for anyone finding this thread and like me, has not used Modbus before: The addresses for the fieldbus IO is the same as the IO numbers shown in RC+ e.g. Starting at 512. Looks like the are also addresses to read/write the IO as a 16 bit word, these start at address 32 which covers bits 512 to 527.
