IR-ETN is not a PLC, it is a bus coupler (part of an I/O system) that allows connecting I/Os to some fieldbus.
fieldbus nodes have specific role - master or slave.
in your case KRC is EthernetIP master and this device is EthernetIP slave.
each slave must have some sort of device description file. this file is fieldbus specific.
it need to be added into configuration of master so that master is aware of slave function, capabilities etc...
in this case you would import this file into WorkVisual.
if you have a PLC configured with Codesys, then this PLC would be master and you would have to import the file into Codesys to parametrize PLC. This could be Modbus.
but if robot still needs access to these I/Os, you would need to create another network between KRC and the PLC. This could be EthernetIP.