Programming manual M238 | 3 MB - BERGER - POSITEC

AS-Interface Configuration
Software Setup Principles
At a Glance
Setup Principle
To respect the operating principles adopted in SoMachine software, the user should
adopt a step-by-step approach for creating an AS-Interface application.
The following table shows the software implementation phases of the AS-Interface
Fieldbus.
Mode Phase Description
Logged out Declaration of module
(see page 95)
Declaration of slave
devices (see page 116)
Logged out
or logged in
Programming
(see page 120)
Choice of the slot for the AS-Interface Master
module TWDNOI10M3 on the expansion bus.
Selection for each device:
of its address on the bus
of its profile
Programming diagnostic functions with the
IoDrvASI (see page 208) library.
Logged in Transfer Transfer of the application to the controller.
Diagnostic / Debugging
(see page 116)
Debugging the application with the help of:
the SoMachine interface to display slaves (address,
profile), and to assign them the desired addresses.
NOTE: The declaration and deletion of the AS-Interface Master module on the
expansion bus is the same as for other expansion modules. However, once two AS-
Interface Master modules have been declared on the expansion bus, SoMachine
will not permit any other AS-Interface Master modules to be declared.
Considerations Prior to Connection
You must ensure that all slaves have a unique address. In addition, the address of
0 is reserved for automatic addressing mode. If there is a slave with an address of
0 detected on the bus at start-up, the master will change to the offline phase and try
to restart. You must ensure that all addresses are unique and that none are 0.
WARNING
UNINTENDED EQUIPMENT OPERATION
Ensure that each slave has a unique address greater than 0.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
94 EIO0000000384 04/2012