Hello
I have a problem with the connection of two robots rs 50, using the Ethernet / IP protocol.
The documentation only describes how to connect the Robot with another device that has an EDS file. Unfortunately, Kawasaki controllers do not have these files. Does anyone know what should be set in the settings AUX.0608-9-4-1.
I have an error all the time # 0315
thank you for any suggestions
EtherNet/ip two robots rs50
- Guccio
- Thread is marked as Resolved.
-
Can you clarify:
- Have you read the General Fieldbus Manual (See this section - General Fieldbus Manual for D/E Controller
- Connect 2 robots - Connect them to each other or connect them individually to other equipment.
- Are you using Software Ethernet/IP or Hardware Ethernet/IP.
- What are you looking at Robot as Scanner=>Adapter or Robot as Adapter=>Scanner.
- Have you looked at the EDS for Kawasaki, what steps have you taken to obtain EDS - Have you contacted Kawasaki, what did they send you.
- The following post had some good information regarding Ethernet/IP - ESAB interfacingError Code #315 normally points to incorrect setting of TargetConfigConnInstance value - but not always exclusively to this.
-
Display More
Can you clarify:- Have you read the General Fieldbus Manual (See this section - https://www.robot-forum.com/ro…manual-for-de-controller/)
Yes I read
- Connect 2 robots - Connect them to each other or connect them individually to other equipment.
I had the opportunity to connect only robots, I did not have any other device to check the connection
- Are you using Software Ethernet/IP or Hardware Ethernet/IP.
- What are you looking at Robot as Scanner=>Adapter or Robot as Adapter=>Scanner.
- Have you looked at the EDS for Kawasaki, what steps have you taken to obtain EDS - Have you contacted Kawasaki, what did they send you.
NO
- The following post had some good information regarding Ethernet/IP - https://www.robot-forum.com/ro…-robots/esab-interfacing/Error Code #315 normally points to incorrect setting of TargetConfigConnInstance value - but not always exclusively to this.
The solution was "TargetConfigConnInstance" in master robots
Thx
-
Excellent, thanks for the feedback and also the screen shot of your values, this will assist others in the future.
Ethernet/IP values need to all be correct or link errors occur and sometimes can be simply set or studying of the EDS values.
Looking at the EDS for Kawasaki in the Connection Manager Section for Exclusive Owner (Includes the Connection and IO exchange configuration).
Code
Display More[Connection Manager] Connection1 = 0x04030002, $ 0-15 = supported transport classes $ 16 = trigger: cyclic $ 17 = trigger: change of state $ 18 = trigger: application $ 19-23 = trigger: reserved $ 24 = transport type: listen-only $ 25 = transport type: input-only $ 26 = transport type: exclusive-owner $ 27 = transport type: redundant-owner $ 28-30 = reserved $ 31 = Client = 0 / Server = 1 0x44640405, $ 0 = O->T fixed size supported $ 1 = O->T variable size supported $ 2 = T->O fixed size supported $ 3 = T->O variable size supported $ 4-5 = O->T number of bytes per slot (obsolete) $ 6-7 = T->O number of bytes per slot (obsolete) $ 8-10 = O->T Real time transfer format $ 11 = reserved $ 12-14 = T->O Real time transfer format $ 15 = reserved $ 16 = O->T connection type: NULL $ 17 = O->T connection type: MULTICAST $ 18 = O->T connection type: POINT2POINT $ 19 = O->T connection type: reserved $ 20 = T->O connection type: NULL $ 21 = T->O connection type: MULTICAST $ 22 = T->O connection type: POINT2POINT $ 23 = T->O connection type: reserved $ 24 = O->T priority: LOW $ 25 = O->T priority: HIGH $ 26 = O->T priority: SCHEDULED $ 27 = O->T priority: reserved $ 28 = T->O priority: LOW $ 29 = T->O priority: HIGH $ 30 = T->O priority: SCHEDULED $ 31 = T->O priority: reserved Param3,Param1,Assem150, $ O->T RPI, size, format Param3,Param2,Assem100, $ T->O RPI, size, format ,, $ config #1 size, format ,, $ config #2 size, format "Exclusive Owner", $ Connection Name "", $ help string "20 04 25 00 00 04 2C 96 2C 64"; $ PathLooking at $Path:
Target Config is 04 (hex to decimal = 4)
Target Produce is 64 (hex to decimal = 100)
Target Consume is 96 (hex to decimal = 150)- Welcome to the forum........
-
Dear kwakisaki,
Unfortunately, the communication between the Robots does not work very well with these settings.
One is a robot scanner and the other is an adapter.
However, nothing is done when activating the inputs and outputs.
All right, according to the photos.
Scanner: RA010L
Adapter: BX200L
The Kawasaki in Germany does not give us in merit help.
Please help!
-
You'll have to improve the images and also provide some backup data of the configuration and io allocations.
-
I take photos of other (I/O) settings?
-
You mentioned in earlier posts that you had successfully configured this, so I am wondering what has changed.
Can you not provide some full file saves from the controllers?
- Send them to me via conversation (if you need to protect company ip)
-
.
Display MoreExcellent, thanks for the feedback and also the screen shot of your values, this will assist others in the future.
Ethernet/IP values need to all be correct or link errors occur and sometimes can be simply set or studying of the EDS values.
Looking at the EDS for Kawasaki in the Connection Manager Section for Exclusive Owner (Includes the Connection and IO exchange configuration).
Code
Display More[Connection Manager] Connection1 = 0x04030002, $ 0-15 = supported transport classes $ 16 = trigger: cyclic $ 17 = trigger: change of state $ 18 = trigger: application $ 19-23 = trigger: reserved $ 24 = transport type: listen-only $ 25 = transport type: input-only $ 26 = transport type: exclusive-owner $ 27 = transport type: redundant-owner $ 28-30 = reserved $ 31 = Client = 0 / Server = 1 0x44640405, $ 0 = O->T fixed size supported $ 1 = O->T variable size supported $ 2 = T->O fixed size supported $ 3 = T->O variable size supported $ 4-5 = O->T number of bytes per slot (obsolete) $ 6-7 = T->O number of bytes per slot (obsolete) $ 8-10 = O->T Real time transfer format $ 11 = reserved $ 12-14 = T->O Real time transfer format $ 15 = reserved $ 16 = O->T connection type: NULL $ 17 = O->T connection type: MULTICAST $ 18 = O->T connection type: POINT2POINT $ 19 = O->T connection type: reserved $ 20 = T->O connection type: NULL $ 21 = T->O connection type: MULTICAST $ 22 = T->O connection type: POINT2POINT $ 23 = T->O connection type: reserved $ 24 = O->T priority: LOW $ 25 = O->T priority: HIGH $ 26 = O->T priority: SCHEDULED $ 27 = O->T priority: reserved $ 28 = T->O priority: LOW $ 29 = T->O priority: HIGH $ 30 = T->O priority: SCHEDULED $ 31 = T->O priority: reserved Param3,Param1,Assem150, $ O->T RPI, size, format Param3,Param2,Assem100, $ T->O RPI, size, format ,, $ config #1 size, format ,, $ config #2 size, format "Exclusive Owner", $ Connection Name "", $ help string "20 04 25 00 00 04 2C 96 2C 64"; $ PathLooking at $Path:
Target Config is 04 (hex to decimal = 4)
Target Produce is 64 (hex to decimal = 100)
Target Consume is 96 (hex to decimal = 150)- Welcome to the forum........
Hello Kwakisaki
"20 04 25 00 00 04 2C 96 2C 64"; $Path
Where can I see what the above says in order?
20 04 25 00 00 Target config 2C Target Consume 2C Target Produce
If so, what does that mean in order?
-
See attached files to learn from.
-
Thank you so much Kwakisaki
Advertising from our partners
