We have Robot and it works with local connection. Its communicating other equipments. I dont want to all eqipments involve global network. Is it possible to involve global network only robot except other equipments. Which network port can I use and how can I configure it ?
It is not possible to give you any advice without knowledge of:
1. Robot brand
2. Controller model (including network port availability)
3. Controller OS version
4. Existing network configuration
Hello
There are servel way base on IT network level.
1. Use MAC Address Filtering on the Router. Add whitelsit
2. Use IP Binding and Firewall Rules
3. Use VLANs to Isolate Other Devices
It is not possible to give you any advice without knowledge of:
1. Robot brand
2. Controller model (including network port availability)
3. Controller OS version
4. Existing network configuration
Kuka KRC4
KSS 8.2.0.6
Now it works locally with other equipments. I want to also involve global network like PC to this robot for MQTT broadcasting. Which port can I use or possible to use for 2nd network
Hello
There are servel way base on IT network level.
1. Use MAC Address Filtering on the Router. Add whitelsit
2. Use IP Binding and Firewall Rules
3. Use VLANs to Isolate Other Devices
I only want to involve robot, there is a station and there are many scalance and other equipment. If I insert the cable scalance all device will be up on the global network.Because of this reason I only want to add kuka robot thats all.
Kuka KRC4
KSS 8.2.0.6
Now it works locally with other equipments. I want to also involve global network like PC to this robot for MQTT broadcasting. Which port can I use or possible to use for 2nd network
IIRC, the early KRC4s that used KSS 8.2 only supported one physical ethernet port, the KLI. It's possible to create multiple virtual NICs on that port, but there are limitations.
"Works locally with other equipment" -- how, exactly? EKX? ProfiNet? Ethernet/IP? EtherCat? What do you have currently connected to the KLI port, and how is the KLI configured?
MQTT? How do you plan to do that with the KRC4? As far as I am aware, KSS does not support MQTT.
"Global network." What kind of network? Static IP, DHCP, other? To do what? The virtual NICs on the KLI port support only one "Windows" NIC, if I recall correctly, and the other virtual NICs connect to KSS, usually dedicated to specific functions (one for Ethernet/IP, one for EKX, etc). You need to define your goal in much greater detail.
For more recent KSS versions there is a KUKA.DeviceConnector. not sure if similar exists for KSS8.2
IIRC, the early KRC4s that used KSS 8.2 only supported one physical ethernet port, the KLI. It's possible to create multiple virtual NICs on that port, but there are limitations.
"Works locally with other equipment" -- how, exactly? EKX? ProfiNet? Ethernet/IP? EtherCat? What do you have currently connected to the KLI port, and how is the KLI configured?
MQTT? How do you plan to do that with the KRC4? As far as I am aware, KSS does not support MQTT.
"Global network." What kind of network? Static IP, DHCP, other? To do what? The virtual NICs on the KLI port support only one "Windows" NIC, if I recall correctly, and the other virtual NICs connect to KSS, usually dedicated to specific functions (one for Ethernet/IP, one for EKX, etc). You need to define your goal in much greater detail.
Hi dear friend. Im quite new robotic system and dont have too much experience.
It works like standalone and has own ring system--> Control PC - Mastic system-Barrel Pump- Main s7300 PLC - drives and pump PLC system and all tihs connect each other with scalance.
KLI port connected to harting switch and harting switch not configured like basic switch. One cable going from harting switch to main scalance.
Actually MTQQ package installed on the robot by Kuka, I think there is no problem using MQTT.
I mean global network like this (192.168.1.20)
Local network is (172.21.39.143)
If I change rbot IP then I have to change almost 30 device IP therefore I asked is there any way to create other port to robot then I only configure new port and involve robot to global network.
It works like standalone and has own ring system--> Control PC - Mastic system-Barrel Pump- Main s7300 PLC - drives and pump PLC system and all tihs connect each other with scalance.
Still no mention of what protocol you're using, but since it's a Siemens PLC, that strongly suggests you're using ProfiNet.
KLI port connected to harting switch and harting switch not configured like basic switch.
No idea what that "not configured like basic switch" means. If the Harting switch is managed, it might be simplest to configure it to re-route any traffic on the MQTT port to a different IP range.
Actually MTQQ package installed on the robot by Kuka, I think there is no problem using MQTT.
Well, that makes success more likely. But you will need to study the manual for the KUKA MQTT option carefully. I've never tried MQTT on a KRC, so I don't know what unique requirements it has.
I mean global network like this (192.168.1.20)
Local network is (172.21.39.143)
So, two static-IP networks on very different subnets.
The KRC4 has three subnet ranges limited to internal use only, meaning the KLI cannot be set to anything in these ranges: 192.168.0.x, 172.17.x.x, and 172.16.x.x. Your IP ranges fall outside these subnets, so it should be okay.
Before making any changes to the network settings, make a project backup and a full hard drive KSR image. Also, DO NOT EVER go into Windows on the KRC and make network changes there. ONLY make network setting changes via the KUKA HMI, under STARTUP>NETWORK CONFIGURATION:
The list of Interfaces is under the ADVANCED button:
This is where things get tricky, and you will need to study the KUKA MQTT manual. Installing the MQTT option may have automatically installed an additional dedicated interface, or it may be your responsibility to do so manually.
In this screenshot, you can see that there is Virtual5, and Virtual6, which has the Windows Interface box checked. Virtual6's IP is the IP used to access the KRC via WorkVisual, SMB, and (usually) FieldBus interfaces like ProfiNet.
It may be possible to create an additional interface, with a different IP address, dedicated to MQTT, but that depends on how KUKA built the MQTT option. The KUKA MQTT manual should have instructions that relate to this. Unfortunately, I don't know much about doing exotic network configurations on KRC4s, as most of my networks were usually quite simple.
