Kuka Nebbiolo NFN 300 Series fogNode User manual

Connectivity Guide

Back to TOC
KUKA Connect Connectivity Guide
2 Issued: 9.10.2018 Version: 3.2
© 2018 KUKA U.S. Holdings Company LLC. All rights reserved. Reproduction, modification, publication,
distribution, or display of this document, in whole or in part, is prohibited except with 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 the information in this document.
Disclaimer
Every reasonable effort has been made to ensure that the user experience provided in this document is
accurate. However, it may differ from the current KUKA Connect user experience due to continuous
improvements.

Back to TOC
KUKA Connect Connectivity Guide
3 Issued: 9.10.2018 Version: 3.2
Contents
Conventions 4
Documentation Feedback 4
Introduction 5
KUKA Connect Network Diagrams 7
Product Description 8
fogNode Overview 9
fogNode Specifications 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 14
Whitelisting 14
fogNode Location Planning 14
Cabling 15
Hardware Deployment Procedure 15
Receiving the Hardware 16
Deploying the Hardware 16
KUKA Connect in the Cloud 21
Deployment Troubleshooting 22
Customer Support 22

Back to TOC
KUKA Connect Connectivity Guide
4 Issued: 9.10.2018 Version: 3.2
Conventions
This document uses the following conventions for notes, cautions, and warnings:
Note A note provides a tip, emphasizes important information, or provides a reference to related
information.
A caution statement alerts you to situations 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 comments are valuable in helping us improve our technical documentation. Please send your
documentation suggestions or corrections to [e-mail] and reference
DOCUMENTATION FEEDBACK in the Subject line of the email. Specify the document title, page number,
section, and error/correction or suggestion.

Back to TOC
KUKA Connect Connectivity Guide
5 Issued: 9.10.2018 Version: 3.2
Introduction
The Nebbiolo NFN 300 Series fogNode™ (fogNode) is a supported connectivity solution for the KUKA
Connect software platform. You will deploy the fogNode using this guide. By leveraging 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 logging in to
KUKA Connect.
Note: KUKA Connect supports KUKA robots with KRC4 controllers and system software KSS 8.3.20 or
later, and KUKA LBR iiwa robots with Sunrise controllers and system software Sunrise.OS 1.11 or later.
Figure 1. The KUKA Connect platform diagram.

Back to TOC
KUKA Connect Connectivity Guide
6 Issued: 9.10.2018 Version: 3.2
This guide will help you successfully plan 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-deployment tasks with instructions
Hardware deployment procedure
KUKA Connect in the cloud
Deployment troubleshooting

Back to TOC
KUKA Connect Connectivity Guide
7 Issued: 9.10.2018 Version: 3.2
KUKA Connect Network Diagrams
A KUKA Connect software platform connectivity solution is the fogNode. The pre-configured fogNode can
hold up to three fogLets™. Each fogLet contains a port for robot network communication, a port for
internet network communication, and a port for additional configuration and onsite troubleshooting.
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, within the cloud,
so users can monitor their robots. Figure 2 and Figure 3 display typical KUKA Connect hardware setups
for consideration during pre-deployment. fogNode placement is near the LAN switch locations of your
robot networks.
Figure 2. A KUKA Connect network diagram for a robot network switch located in the IT
server room. The fogNode connects directly to the switch in the server room.

Back to TOC
KUKA Connect Connectivity Guide
8 Issued: 9.10.2018 Version: 3.2
Figure 3. A KUKA Connect network diagram for a robot network switch located near
the robot cell. The 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 storage systems with hardware support. Next sections provide an overview of the essential parts of
the fogNode and fogNode specifications that aid in pre-deployment setup.

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.

Back to TOC
KUKA Connect Connectivity Guide
10 Issued: 9.10.2018 Version: 3.2
Table 1. Names and definitions of essential parts of the fogNode labeled in Figure 4.
No. Item Description
1 fogLet™ card Device in fogNode consisting of S0, E0, and E1 ports that
provide integrated computing, storage, and networking
2 Slot 0 Slot for fogLet
3 Slot 1 Default slot for fogLet
4 Slot 2 Slot for fogLet
5 S0 port
Ethernet (1Gbe) port for LAN robot network
communication. 2 LAN IP addresses are necessary for this
port 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 switch Turns the fogNode On/Off
fogNode Specifications
The fogNode specifications are as follows:
Table 2. Specifications for the fogNode.
Specification Type Description
Power Supply 110 – 240V AC; 350W power supply unit
Power Consumption 100W to 300W (dependent on configuration)
Power cord 6 ft
Dimensions
10.5”(H) x 8.6”(W) x 7.7”(D)
26.5cm(H) x 21.7cm(W) x 19.5cm(D)
Cooling Forced air cooling with built-in redundancy
Operating Conditions 0° to 50°C
Weight 7.5kg to 9.5kg (dependent on configuration)
Protection IP 20

Back to TOC
KUKA Connect Connectivity Guide
11 Issued: 9.10.2018 Version: 3.2
Prerequisites
The following hardware and software requirements must be met before using KUKA Connect:
Table 3. The KUKA Connect hardware and software requirements.
Hardware Operating System Additional Software
KRC4 controller with KUKA
robot KSS 8.3.20 or later
KUKA LBR iiwa robot with
Sunrise controller Sunrise.OS 1.11 or later
*Complimentary KUKA
Sunrise.Connect Option
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-deployment planning must be completed before you receive and deploy your KUKA Connect
hardware. Executing planning beforehand ensures quick deployment once your fogNode arrives.
Pre-deployment planning consists of:
Reviewing the pre-deployment checklist
Reviewing the equipment list
Completing a robot connection plan
Selecting static IP addresses, if applicable
Whitelisting, if applicable
fogNode location planning
Completing cabling requirements

Back to TOC
KUKA Connect Connectivity Guide
12 Issued: 9.10.2018 Version: 3.2
Pre-deployment Checklist
Use this checklist and the sections that follow to review and complete your pre-deployment tasks well
before you receive your fogNode to make the hardware deployment process is quick and easy.
Robot Connection Plan
How many robots will you connect?
How many robot networks will you connect?
How many fogNodes and fogLets will you need? Each fogNode can support up to 3 robot networks since each fogLet placed
in the fogNode can support a robot network (S0 port) and a maximum of three fogLets can be placed in a fogNode. Each
fogLet supports up to 20 robots.
KUKA Customer Support Contact
Have you contacted KUKA customer support at [e-mail] to tell them how many fogNodes and fogLets you
will need so they can send the correct hardware?
IP Addresses (skip this section if you have DHCP WAN and LAN)
Have you selected and documented two static LAN IP addresses for each robot network you will connect to each S0 fogNode
port? Two IP addresses are necessary for the LAN for the S0 port because two virtual machines correspond with each S0
port. It is necessary to have the IP addresses documented for configuration during fogNode deployment.
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 firewall?
Do you have a proxy?
Do you have static WAN IP addresses and do you typically whitelist items? If yes to both, whitelist each static WAN IP
address.
fogNode Location Planning
Where can the power supply be physically accessed? Requirements are 110 – 240V AC.
Where can the WAN and LAN networks be physically accessed?
Is there a location to place the fogNode with close access to the LAN, WAN, and proper power supply? If not, create a
location plan that can work by determining how these items can be brought closer together for the fogNode to access (e.g.,
if the fogNode’s power cord is too short to plug into the nearest electrical outlet, add an extension cord to the outlet that will
allow for plug in from the fogNode to the outlet).
Where will you place the fogNode?
Will the fogNode fit in the place you have selected (fogNode dimensions are 10.5” x 8.6” x 7.7”)?
Do you need a small table for the fogNode?
Have you determined if you need an extension cord to plug the fogNode into the proper power supply (power cord is 6 ft)? If
yes, have you set this up?
Cabling
Have you measured the length of Ethernet cable you need to run for each LAN and WAN from the fogNode to each switch?
Have you made the cabling and physically routed it to the fogNode location?

Back to TOC
KUKA Connect Connectivity Guide
13 Issued: 9.10.2018 Version: 3.2
Equipment List
The following equipment is necessary during KUKA Connect pre-deployment planning for one fogNode,
one fogLet:
LAN switch for the robot network
WAN switch
2 Cat5, Cat 5e, or Cat6 Ethernet cables. Length determined during pre-deployment planning
stage.
110 - 240V AC power supply with electrical outlet
Extension cord may be necessary to plug fogNode into outlet
Small table or shelf to hold fogNode if not placed in cabinet
Robot Connection Plan
A documented robot connection plan is important as a first step in your pre-deployment planning. It
serves as a foundation for completion of the rest of your pre-deployment tasks and helps you determine
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 will connect.
The total number of fogNodes and fogLets you will need.
Note: Each fogNode can support up to three robot networks since each fogLet placed in the
fogNode can support one robot network (through the S0 port) and a maximum of three fogLets
can be placed in a fogNode. Each fogLet supports up to 20 robots.
Contacting KUKA Customer Support
Since hardware needs are unique to each facility, KUKA Customer Support sends your fogNode and
fogLets order based on your robot connection plan information. Once you complete this plan, contact
KUKA customer support at [e-mail] and give them your robot plan information.
After the support team receives the information, they will send your hardware order for deployment.

Back to TOC
KUKA Connect Connectivity Guide
14 Issued: 9.10.2018 Version: 3.2
Creating Static IP Address List
Select and document your static LANs so that each fogNode can communicate with your robot networks.
Select and document your WAN IP addresses for auto discovery and so that each fogNode can
communicate with your internet connection.
Note: Skip this section if you will use DHCP for both your WAN and LAN.
To complete a static IP address list for one fogNode and one fogLet:
1. Select and document two LAN IP addresses for the robot network you will connect.
Note: Two LAN IP addresses are necessary for the robot network because two virtual machines
correspond with the S0 port of the fogNode.
Each static LAN IP address must be within the same subnet as its corresponding robot network
for auto discovery to occur.
Correct: 10.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
[e-mail] for assistance.
2. Select and document one static WAN IP address for your fogNode.
3. Keep the IP address list handy during the deployment process.
Whitelisting
To ensure connectivity to the cloud, you may need to create a whitelist as part of pre-deployment
planning.
To determine if you need to whitelist, answer these questions:
Do you have a firewall?
Do you have a proxy?
If you do have a firewall, do you typically whitelist items?
Do you have static WAN IP addresses?
If a whitelist is needed, contact the KUKA support team at [e-mail] to receive the
correct items to whitelist.
fogNode Location Planning
You are now ready to determine the permanent location for the fogNode. The hardware requires
connection to your WAN and LAN networks via Ethernet cables and connection to power via an electrical
outlet. Because of this, the ideal location for your fogNode is near:

Back to TOC
KUKA Connect Connectivity Guide
15 Issued: 9.10.2018 Version: 3.2
The LAN switches
The WAN switches
A 110 - 240V AC power supply electrical outlet
To determine the permanent location:
1. Review the network diagrams to see the typical network setups and fogNode placements.
2. Review the LAN switch locations.
3. Review the WAN switch locations.
4. Find a 110 – 240V AC power outlet near the switches.
5. Find a location close to the switches and power outlet to place the fogNode. If there is not a
location that is suitable, create a location plan that will work. For example, if the fogNode’s
power cord is too short to plug into the nearest electrical outlet, add an extension cord to the
outlet that will allow for plug in from the fogNode to the outlet.
6. Measure the dimensions of the fogNode location to ensure the hardware will fit in the space. The
dimensions are 10.5” x 8.6” x 7.7” (26.5cm x 21.7cm x 19.5cm).
7. Add shelving or a small table for the fogNode 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 cabling from the LAN and
WAN to your permanent fogNode location for network communication during fogNode deployment.
To complete the cabling process for one fogNode and one fogLet:
1. Measure the distance from the LAN switch to the fogNode.
2. Measure the distance from the WAN switch to the fogNode.
3. Measure the lengths of cable so they match the measurements you took in Steps 1 and 2.
4. Make each of the Ethernet cables.
5. Run each of the cables from the switches to the fogNode location.
Hardware Deployment Procedure
After completing the pre-deployment tasks, KUKA Connect hardware deployment consists of:
1. Receiving the fogNode hardware.
2. Deploying the hardware.
Once these steps are completed, your company’s employees, granted access by an organizational
admin, can view robot data through KUKA Connect.
Note: The hardware deployment procedure assumes one fogNode and one fogLet.
Note: Read through the rest of this information before deploying the hardware.

Back to TOC
KUKA Connect Connectivity Guide
16 Issued: 9.10.2018 Version: 3.2
Receiving the Hardware
Once you complete the pre-deployment tasks and receive your hardware, unpack the fogNode that
comes with the preinstalled fogLet. The fogLet can support up to 20 robots and one robot network and
provides integrated computing, storage, and networking.
Install the hardware in a static-safe workstation. Discharge static electricity and wear anti-static
wrist wraps until the fogNode is assembled and connected to a power outlet.
Deploying the Hardware
KUKA Connect fogNode deployment is simple because it is zero-touch. Plugging into the correct
networks and turning the device on is all that is required when using a DHCP server for WAN and LAN. If
no DHCP server is available, a simple configuration is all 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.11 or later.
Follow safety procedures while handling 110 - 240V AC.
Risk of electric shock exists. Do not open up the back plate of the chassis. There are no
serviceable parts inside.
The fogNode must be connected using the supplied power cord with a grounded neutral power
supply system. If a substitute power cord is used, it must be of at least # 20 AWG wire.
Install the hardware in a static-safe workstation.
Discharge static electricity and wear anti-static wrist wraps until the fogNode is assembled and
connected to a power outlet.
Placement of fogNodes in environments that may cause damage by liquids, excessive heat,
barrier or blockage of cooling fans, or blunt damage to the hardware is forbidden. Deploying
the fogNode in any of these environments may cause damage to the hardware and/or loss of
data.

Back to TOC
KUKA Connect Connectivity Guide
17 Issued: 9.10.2018 Version: 3.2
Many repairs may only be done by a certified service technician. You should perform only
simple troubleshooting steps as directed by online or telephone support personnel. Your
warranty does not cover any damage due to unauthorized service.
All slots in the system must be populated at all times either with a module or with a blank card
to ensure proper cooling of the system.
To deploy the 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 your LAN switch into the S0 port on the fogNode.
Note: Data is collected via the KLI ports of your KUKA robots. Please ensure the fogNode’s S0 port
is on the same network as your robots’ KLI ports.
Note: Each fogLet can communicate with a robot network, 20 robots, and one internet network.
Figure 5. Ethernet cables plugged into the fogNode for deployment.
2. Plug an Ethernet cable from the WAN network into the E0 port on the fogNode so it can
communicate with the cloud.

Back to TOC
KUKA Connect Connectivity Guide
18 Issued: 9.10.2018 Version: 3.2
3. Plug one end of the fogNode power cord into the fogNode and the other end to the electrical
outlet.
4. Turn the power switch On.
After five to ten minutes, the fogNode is online and collecting robot data.
If your dual network WAN and/or LAN has/have no DHCP server, you must configure the static IP
addresses you selected during pre-deployment planning. A quick configuration must be performed to set
up the addresses.
Note: Save a copy of the network configuration settings in case you need it for reconfiguration.
To configure the WAN network:
1. Plug an Ethernet cable from your laptop to the fogNode’s E1 port.
2. Connect to 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
to 20.20.20.2 (unsafe) link.
3. Enter default user-id nbtguest and the default password letmein in the Username and
Password fields. The Dashboard displays.
4. Click Configuration on the left side menu bar.
5. Click WAN Configuration. The WAN Configuration screen displays.
Figure 6. The WAN Configuration screen in the fogNode portal.
6. Change the Time Server name or its IPV4 address to the appropriate value if your network
cannot connect to the default time server.
7. Enter the DNS Server IPV4 address in the DNS Server field.
Note: When a static IPV4 address is configured, the DNS Server field cannot be blank. If you do
not have a DNS Server IPV4 address, configure the address with the default 8.8.8.8.

Back to TOC
KUKA Connect Connectivity Guide
19 Issued: 9.10.2018 Version: 3.2
8. Enter the proxy server IPV4 address in the Proxy Host field and the port in the Proxy Port field if
the WAN network requires a proxy server to reach the internet.
9. Select Use Static.
10. Enter the IPV4 address that you selected during pre-deployment planning in the IPV4 Address
field.
Note: Use an unassigned IP address within your network.
11. Enter the IP netmask in the Subnet Mask field.
12. Enter the IPV4 address 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 display as Connected.
Note: If the connection is not successful, review the configuration steps as well as the
Deployment Troubleshooting section.
Figure 7. The fogNode portal Dashboard screen with a WAN Connection Status of Not Connected.
15. If this completes your entire configuration setup, reboot the system. Otherwise, configure the
LAN network next.
To configure the LAN network:
1. Click Configuration on the left side menu bar.
2. Click LAN Configuration. The LAN Configuration screen displays.

Back to TOC
KUKA Connect Connectivity Guide
20 Issued: 9.10.2018 Version: 3.2
Figure 8. The LAN Configuration screen in the fogNode portal.
3. Change the Time Server name or its IPV4 address to the appropriate value if your network
cannot connect to the default time server.
4. Enter the DNS Server IPV4 address in the DNS Server field.
Note: When a static IPV4 address is configured, the DNS Server field cannot be blank. If you do
not have a DNS server IPV4 address ,configure the address with the default 8.8.8.8.
5. In the Admin VM section, 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 the Subnet Mask field.
8. If needed, enter the IPV4 address in the Default Gateway field.
9. In the OT VM section, select Use Static.
10. Enter the IPV4 address you selected during pre-deployment planning in the IPV4 Address field.
Note: Use an unassigned IP address within your network.
11. Enter the IP netmask in the Subnet Mask field.
12. If needed, enter the IPV4 address 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. Reboot the system.