Hi all,
We are still trying to configure how we could use a generic HMI (has Ethernet IP) to communicate with the KRC4 Compact controller (with Profinet option). Also we don't have the EIP package installed - we only have Profinet.
Our Application: Use generic HMI (EIP, No eds file) to run the program.
Our workaround was trying to use the Anybus X-gateway (AB7650) as an intermediate converter for Profinet/Modbus TCP server handling.
My questions are:
1. Is there a way we could use this as i read in the documentation that Profinet doesnot suppport multimaster support along with EIP?
2. The generic HMI doesnot come with an eds files, but the HMS x gateway should be able to generate the file right? Do we still need to map IO handling between gateway device and HMI?
3. The HMI comes with webserver functionality and we only wish to run a single program for our welding application in a loop. Is there anyway we could plug in the HMIs Ethernet port to the KRc4 controller X69 port (service network port) ? where the controller should assign an IP to the HMI and use the webserver functionality to make small changes to the program, is this possible?
5. Can someone advice/suggest a suitable approach to our communication interface ( HMI(generic,EIP,MODBUS) - ANYBUS - KRC4(Profinet) )?
Regards
nar
Using generic HMI (EIP) to communicate with KRC4(ProfiNET)?
-
n0909 -
February 7, 2018 at 3:23 AM -
Thread is marked as Resolved.
-
-
I just went through this -- the Anybus gateway requires that you buy additional software from Anybus to configure the Profinet side of the Gateway. It might also require another piece of additional software to configure the EIP side.
The KUKA implementation of PN does not support allowing the robot to be a slave to multiple masters. This should not be an issue -- the robot can be a master to the Gateway. However, unless the HMI can be configured as an EIP Master, I don't see any way to connect the HMI to the gateway.
#3... not unless you have KUKA EKI option, or have extreme KRL programming skills. And while the robot can act as a DHCP server, I believe that's only for laptops running WorkVisual.
5. Depends entirely on the HMI. Frankly, this entire setup sounds unworkable unless you add a PLC to act as an EIP master to the HMI and the Gateway, and make the PN side of the Gateway a slave to the robot.
-
Hi SkyeFire,
Thanks for your response.
But i thought the Anybus software was free and included in the price of the module.
But we were thinking about using the anybus in this way.Generic HMI <-MODBUS TCP SERVER/SLAVE-> Anybus X-Gateway <-PROFINET DEVICE/SLAVE-> KRC4 Controller
So would you still consider the above arrangement unworthy to give it a shot?
Please advice
Thanks
nar -
No, the Anybus software is not free -- I discovered this the hard way, after buying the Gateway and finding myself unable to configure it. This was specific to the Profinet and EIP sides of the Gateway -- possibly the other busses don't need the extra expenditure. This little fact is not very well shown on AnyBus's web site.
As to your proposed configuration: first, it depends on the HMI -- can it even use ModBus? I thought it only had EIP. Second, if the HMI and Gateway are both Slave devices, this can't work -- you can't connect two slaves to each other.
-
Hi skyefire,
Thanks for your response.
Yes the HMI supports MODBUS, please have a look at the pdf attached for datasheet.
Thats not cool on anybus not to mention anything about their paid software, and maybe you're right because the website does not at all mentions any software tools and all they offer is some free tools for ipconfig and stuff and some of them are even not downloadable.
Anyway pls look throught the datasheet and let us know the best plan of attack.
Regards
N -
That PDF does not mention ModBus anywhere. The DB-9 port obviously supports RS232, 422, and 485, although that pinout appears non-standard. But as to whether the HMI can act as a ModBus Master is left a mystery.
If the Anybus gateway can act as a Master on the ModBus side (unlikely, but not impossible), then this may be a moot point. But at the end of the day, one device on the ModBus must act as a Master, and the others must be slaves. Any configuration between the HMI and Gateway that satisfies this criteria should work, but you'll have to research both devices thoroughly.
-
i am still unclear what is the actual goal here?
do a science project and see how many conversions can take place or ... get the job done?
if the first case is true, you would need to know yourself what avenues to explore as this will require some hair loss and a lot of time for experimentation. this would be valid investment if there is opportunity to repeat this many times. it would be poor choice for one time installation.
if the second case is true, why not choose things the way they are normally used? For example normal path is to get PLC instead of gateway and have PLC communicate with KRC over some common network (ProfiNet or EtherCat or whatever). Then use some HMI to talk to PLC. Unlike Gateway, PLC can be used for many more things as well...