background image

Back to TOC

KUKA Connect Connectivity Guide

22

Issued: 9.10.2018

Version: 3.2

Deployment Troubleshooting

Review the troubleshooting table below for solutions to the most common issues that occur during
deployment.

Table 4.

Solutions to common problems that may occur during hardware deployment.

Problem

Cause

Solution

No
communication
between
networks and
fogNode

Loose network cable

Nonfunctional network
cable

fogNode is set to DHCP
when static IP addresses
are being used

Only one static LAN IP
address selected for a
robot network

Reinsert the cabling into its ports then check both
LED lights on each port to see if they are on

Replace the cable with a new cable then check both
LED lights on each port to see if they are on

Review the

WAN and LAN configuration

sections

Generate two static LAN IP addresses for each S0
port on the fogNode because each S0 port
corresponds to two virtual machines. See the

IP List

section

in the KUKA Connect Help Center.

fogNode not
able to auto
discover robot
networks

One or more static LAN IP
addresses are not on the
same subnet as its robot
network

Only one static LAN IP
address selected for a
robot network connected
to an S0 port

Review the

IP List section

in the KUKA Connect Help

Center

Generate two static LAN IP addresses for each S0
port on the fogNode because each S0 port
corresponds to two virtual machines. See the

IP List

section

in the KUKA Connect Help Center

Webadmin
Dashboard

does not
display as
connected

Loose network cable in E0
port

Nonfunctional network
cable in E0 port

A whitelist configuration
may be incomplete

Something other than the
WAN needs to be
whitelisted

Reinsert the cabling into its port

Replace the cable with a new cable

See the

Whitelisting section

in the KUKA Connect

Help Center

Contact KUKA support at

[email protected]

Customer Support

For help with KUKA Connect, please contact us at

[email protected]

.

Summary of Contents for Nebbiolo NFN 300 Series fogNode

Page 1: ...Connectivity Guide...

Page 2: ...ith the prior written permission of KUKA U S Holdings Company LLC The information in this document may change without notice KUKA U S Holdings Company LLC assumes no liability related to the use of th...

Page 3: ...ecifications 10 Prerequisites 11 Pre deployment Planning 11 Pre deployment Checklist 12 Equipment List 13 Robot Connection Plan 13 Contacting KUKA Customer Support 13 Creating Static IP Address List 1...

Page 4: ...tions that could result in equipment damage or loss of data A warning statement indicates conditions or situations that are potentially lethal or extremely hazardous to you Documentation Feedback Your...

Page 5: ...the latest in Fog Computing technology the fogNode is able to pull data from your KUKA robots encrypt it then send the data through a secure connection to the cloud From there you can view the data by...

Page 6: ...for and deploy the necessary hardware by explaining KUKA Connect network diagrams Hardware product overview Hardware requirements Pre deployment planning Pre deployment checklist Equipment list Pre d...

Page 7: ...leshooting The fogNode receives robot data through network communication encrypts it then sends it securely to the cloud where the data is decrypted and relevant robot data is sent to KUKA Connect wit...

Page 8: ...he fogNode connects directly to the switch in the cabinet near the robot cell Product Description The fogNode works as a network fog device that combines the capabilities of computation networking and...

Page 9: ...Back to TOC KUKA Connect Connectivity Guide 9 Issued 9 10 2018 Version 3 2 fogNode Overview The essential parts of the fogNode are as follows Figure 4 The Nebbiolo NFN 300 Series fogNode with fogLets...

Page 10: ...because it contains two virtual machines 6 E0 port Ethernet 1Gbe port for WAN internet network communication 7 E1 port Ethernet 1Gbe port for LAN and WAN configuration and technician use 8 Power switc...

Page 11: ...n package Nebbiolo NFN 300 Series fogNode with fogLet s fogOS As the technical contact you received the KUKA Sunrise Connect Option package link via email with instructions Pre deployment Planning Pre...

Page 12: ...yment Are the two static LAN IP addresses for each S0 port within the same subnet as its corresponding robot network Have you selected one static IP address for the WAN Whitelisting Do you have a fire...

Page 13: ...mine the number of fogNodes and fogLets you will need for deployment To complete your robot connection plan document The total number of robots you will connect The total number of robot networks you...

Page 14: ...0 79 168 xxxx where 168 is the subnet Note If it is not possible to create IP addresses in the same subnet contact support at connect support kuka com for assistance 2 Select and document one static W...

Page 15: ...de to sit on if needed 8 If the power outlet is more than 6 ft from the fogNode add an extension cord to the location Cabling The last pre deployment planning step is to measure make and run Ethernet...

Page 16: ...that is needed Note KUKA Connect supports KUKA Robots with KRC4 controllers with system software KSS 8 3 20 or later and KUKA LBR iiwa robots with Sunrise controllers with system software Sunrise OS 1...

Page 17: ...e hardware in a dual network with DHCP server for WAN and LAN or a combined networking setup 1 network Note The deployment instructions assume one fogNode and one fogLet 1 Plug an Ethernet cable from...

Page 18: ...the fogNode portal at https 20 20 20 2 10000 via your browser The Nebbiolo Admin login screen displays Note Click Advanced if the Your Connection is not Private screen displays then click the Proceed...

Page 19: ...s in the Default Gateway field Note When a static IPV4 address is configured the DNS Server IPV4 address must also be configured 13 Click Save 14 Click Dashboard The WAN Connection Status field should...

Page 20: ...ection select Use Static 6 Enter the IPV4 address you selected during pre deployment planning in the IPV4 Address field Note Use an unassigned IP address within your network 7 Enter the IP netmask in...

Page 21: ...es and robot groups in KUKA Connect will receive a separate email with instructions on signing in to KUKA Connect to begin configuring the product for your company s users To get started in KUKA Conne...

Page 22: ...ch S0 port corresponds to two virtual machines See the IP List section in the KUKA Connect Help Center fogNode not able to auto discover robot networks One or more static LAN IP addresses are not on t...

Reviews: