If signals are allocated to dedicated signals, then these are automatic, otherwise you have to program it in the same way you would usually program IO signals.
The relative manuals usually help called General Fieldbus IO Usage Manuals for the setup and then using BLOCK or AS language programming as the medium to monitor and control IO.
- PULSE, SIGNAL, BITS are usual AS commands but not limited to.
Networking is just the 'transport method' that is used.
You allocate signals in 16bit slices of IO to the combination of your configuration.
Local, Master, Slave usually in consecutive slices.
Correct LOCAL is termed as the physical interfacing of the controller.
Local can be described as controller interface such as:
- Digital IO boards.
- Klogic (Software Kawasaki PLC which interfaces between internal and external IO).
- Arm ID IO (if installed it is located on the arm itself allowing for local interfacing with EOAT).
Master and Slave are for the selected fieldbus protocols and respective installed fieldbus boards.
Current Kawasaki controllers also offer built in software ethernet/ip which does not require any additional hardware to use.
This is dedicated to the LAN Port 2 on the CPU board if selected and AFAIK have a single adapter (Master) and 3 scanners (Slaves) available (unless this has changed siince I last looked).
You're welcome...............
