ElmoMC Multi-Axis Motion Controller-Maestro User Manual

Page 144

Advertising
background image

Maestro

Software Manual

The CANopen Configurator

MAN-MASSW (Ver. Q)

9-10

ƒ

CAN bus baud rate (for bus 0 and bus 1) defines the baud rate for the
LSS master initialization during auto connection with the device. The
property is available only if the auto connect property is set to YES.

Auto identification after connection to Maestro device defines the program

behavior when communication with the target Maestro device is established.

ƒ

Enable auto identification by DS301 makes it possible to use the NMT
service of the DS301 protocol to automatically recognize a CAN node. If
the CAN bus is not configured, this option does not work correctly.

ƒ

Enable auto identification by DS305 this feature makes it possible to use
the DS305 protocol to automatically recognize a specified CAN node. This
option can be used for CAN nodes with a unique LSS address. DS305
CAN node auto identification may not work correctly with a large CAN
bus (i.e., where there are more than 16 nodes).

If a CAN node is not located, the user can add the node manually, or
load it from a file. The new configuration must be stored with the File
> Node Set Import
feature.

Disconnect from Maestro device defines how the program behaves when it

disconnects from the Maestro device.

Figure

9-17: Disconnect from a Maestro Device

ƒ

Change Maestro resources after disconnect defines possible
changes to the resource file of the Maestro device. The changes
can be performed during the LSS master disconnection. The
user can choose either YES or NO. (See Figure

9-17).

• If the user selects YES and changes the Node ID, the Maestro

restarts with an empty resource file. The Configurator gets the
current baud rate for CAN bus initialization.

• If the user selects NO, the Maestro restarts with the previous

resource file.

Configuration process parameters define the program behavior during the

CAN network configuration.

ƒ

Immediate store configuration data defines the order of data
saved in the CAN nodes. This process is more time consuming
because it saves each node's data individually during the
configuration process.

Advertising