AMCI SD17060E-K, Руководство пользователя

Страница: 36 / 110

M
OTION
C
ONTROL
Networked Indexer/Driver User Manual
ADVANCED MICRO CONTROLS INC.
36
Assembled Move Programming (continued)
Saving an Assembled Move in Flash
The Networked Driver also contains the Save_Assembled_to_Flash bit that allows you to store the Assembled
Move in flash memory. This allows you to run the Assembled Move right after power up, without having to go
through a programming sequence first. To use this bit, you follow the above programming routine with the
Save_Assembled_to_Flash bit set. When you reach step 9 in the sequence, the Networked Driver responds by
resetting the In_Assembled_Mode and Transmit Blend Move Segments bits as usual and then flashes the Error
LED. If the LED flashes green at 4 Hz (fast blink), the write to flash memory was successful. If it flashes green
at 1 Hz (slow blink), then there was an error in writing the data. In either case, power must be cycled to the Net-
worked Driver before you can continue. With a limit of 10,000 write cycles, the design decision that requires
you to cycle power to the Networked Driver was made to prevent an application from damaging the module by
continuously writing to it.
Indexed Moves
All of the moves that have been explained in the chapter up to this point can be started by a transition on one
of the inputs instead of a command from the network. If the
Indexed Move bit is set when the command is
issued, the Networked Driver will not run the move until the configured input makes an inactive-to-active
transition. This allows you to run time critical moves that cannot be reliably started from the network because
of messaging time delays.

The input must be configured as a Start Indexed Move Input.

The move begins with an inactive-to-active transition on the input. Note that an active-to-inactive tran-
sition on the input will not stop the move.

The move command must stay in the Network Output Data while performing an Indexed Move. The
move will not occur if you reset the command word before the input triggers the move.

The move can be run multiple times as long as the move command data remains unchanged in the Net-
work Output Data. The move will run on every inactive-to-active transition on the physical input if a
move is not currently in progress. Once a move is triggered, the Start Indexed Move Input is ignored by
the Networked Driver until the triggered move is finished.

As stated above, a move can be run multiple times as long at the move command data remains
unchanged. If you wish to program a second move and run it as an Indexed Move type, then you must
have a 0

1 transition on the move command bit before the new parameters are accepted. The easiest
way to accomplish this is by writing a value of 16#0000 to the command word between issuing move
commands.

A Jog Move that is started as an Indexed Move will come to a controlled stop when the command bit in
the Network Output Data is reset to zero.

It is possible to perform an indexed Registration Move by configuring two inputs for their respective
functions. The first input, configured as a
Start Indexed Move Input , starts the move and the second,
configured as a Stop Jog or Registration Move Input causes the registration function to occur.

You cannot issue a Hold Command with the Indexed Bit set and have the Hold Command trigger on the
inactive-to-active transition of a physical input. Hold Commands are always acted upon as soon as they
are accepted from the Network Output Data.

You cannot issue an Immediate Stop Command with the Indexed Bit set and have the Immediate Stop
Command trigger on the inactive-to-active transition of a physical input. Immediate Stop Commands
are always acted upon as soon as they are accepted from the Network Output Data. If you need this
functionality, consider programming the physical input as an E-Stop Input.

You cannot issue a Clear Error Command with the Indexed Bit set and have the Clear Error Command
trigger on the inactive-to-active transition of a physical input. Clear Error Commands are always acted
upon as soon as they are accepted from the Network Output Data.