Baldor Modbus Plus Instrukcja Użytkownika Pobierz pdf (Strona 19)

AN00174-001 Modbus TCP Fieldbus Option for MotiFlex e100.doc

1919

19 of

of of

of 22

2222

Now we’ve mapped the axis the Resource Mapping dialog will show a green tick against Axis 0

and indicate in brackets which axis this has been mapped to on the NextMove…

The dialog also indicates that some Process Data associated with Manager Profiled operation of

the axis has been configured (we don’t need to look at this in detail for this Application Note).

Scroll down the Resource Mapping dialog until you find the ‘Additional Process Data’ section. This

is the section we need to edit…

There are two elements to this section:

• Process Data (Controlled Node<-Manager Node) – this is the Process Data that is to be

passed from the NextMove e100 to the drive (in our case this corresponds to NetData

Channels 3 and 4 which we want to pass from the NextMove e100 to the client/PLC

ultimately – via the MotiFlex Fieldbus Option)

We can choose whether the drive is to be

manager profiled (the NextMove e100

provides the profile data – useful for

interpolated motion, CAMs, FLYs, etc..),

Controlled Node profiled (the drive

calculates its own position demands –

useful if the only motion required from

the drive is MOVEA, MOVER, INCA, INCR

and HOME), or Monitored only (no

motion).

We have selected the most common

profile method – Manager profiled.

We have also decided to map the drive’s

axis 0 as the NextMove’s axis 2 (it is

typical to match the axis number to the

EPL node ID as it makes tracking which

axis is which much easier!).

Click on ‘OK’.

1 2 ... 14 15 16 17 18 19 20 21 22

Brak uwag

Baldor Modbus Plus Instrukcja Użytkownika Strona 19