Checklist for beginners and expirienced users

1. How many inputs and outputs are required?

   The number of inputs and outputs tells you how many AS-Interface networks you need.

2. How much power do the I/Os require?

   The total power requirement of the respective modules determines which AS-Interface power supply unit you need. As it is not possible to connect power supply units in parallel, a power supply unit sized to the requirement must be used.

3. Are special cables required?

   Any combination of profiled and round cables is possible. External conditions determine whether rubber, TPE or PUR cables should be used. Repeaters or extenders have to be used for cable lengths exceeding 100 m.

4. Have the addresses been correctly assigned?

   A plan should definitely be drawn up making it clear which addresses have been assigned to which slaves. Double addressing will not be identified as an error by the master!

5. Which modules belong to which addresses?

   The modules, or rather, the slaves which are addressed, should be carefully labelled.

6. When are the modules mounted?

   Only when points 4 and 5 have been dealt with. Cables can be routed in any way.

7. How is it all configured?

   The configuration is simply read in by entering the AS Interface profile for each slave in the master. This usu- ally happens automatically, but can be done manually in the controller software.

8. Are the slaves detected?

   First you must check whether the master has recognised all its slaves. Only then can you switch to protected operation and switch the controller to RUN.

9. How is testing done?

   Input/output tests are performed by the familiar PLC method, i. e. the sensors are activated locally and then checked in the PLC.

10. How do you get it up and running?

    You can either create your own controller software in the usual way, or use existing software. In the latter case, you might have to adapt the symbolic assignment of addresses.