![NANOTEC ELECTRONIC N5 Technical Manual Download Page 29](http://html.mh-extra.com/html/nanotec-electronic/n5/n5_technical-manual_705153029.webp)
Technical Manual N5 (CANopen)
4 Commissioning
4 Commissioning
Described in this chapter is how you establish communication with the controller and set the necessary
parameters to make the motor ready for operation. You can configure the controller via Ethernet using
NanoIP – a browser-based user interface – or via the CANopen bus.
The Plug & Drive Studio software offers you an option for performing the configuration and adapting
the controller to the connected motor. You can find further information in document Plug & Drive
Studio: Quick Start Guide at us.nanotec.com.
Observe the following note:
Note
•
EMC: Current-carrying cables – particularly around supply and motor cables – produce
electromagnetic alternating fields.
•
These can interfere with the motor and other devices. Nanotec recommends the following
measures:
•
Use shielded cables and earth the cable shielding on both ends over a short distance.
•
Use cables with cores in twisted pairs.
•
Keep power supply and motor cables as short as possible.
•
Earth motor housing with large contact area over a short distance.
•
Lay supply, motor and control cables physically separate from one another.
4.1 Configuration via Ethernet
4.1.1 Overview
Interface
The controller is equipped with a 10/100 MBit Ethernet interface on connector X1. It can thereby be
operated with all common Ethernet components (switches, PCs) and configured via the NanoIP web
interface or the Plug & Drive Studio software.
Hardware address
The controller initially has no IP address, but is instead addressed via the printed hardware address
(MAC address). This address consists of 6 hexadecimal numbers in form44-AA-E8-xx-xx-xx.
The hardware address is unique and unchangeable and is assigned during production. In general,
this is only needed during a firmware update. As soon as the boot loader has ended and the actual
firmware begins to operate, subsequent communication takes place via the TCP/IP protocol.
IP address
The controller needs a valid IP address. This can be obtained in the following ways:
•
DHCP: A DHCP server assigns the IP address to the controller (default setting).
•
AutoIP: The controller automatically determines a suitable IP address. The prerequisite here is that
the communication partners are in the same physical subnet and also use AutoIP.
•
Static IP address: This is defined by the user.
Which method is used depends on the network environment and is defined by the network
administrator.
Version: 2.0.1 / FIR-v1650
29