Variables and fieldbus: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Category:LogicLab ==INTRODUCTION== This article gives an overview of the relationship between the variables of a PLC application and the different fieldbus either in maste...") |
No edit summary |
||
| Line 1: | Line 1: | ||
[[Category:LogicLab]] | [[Category:LogicLab]] | ||
== | ==Introduction== | ||
This article gives an overview of the relationship between the variables of a PLC application and the different fieldbus either in master or slave configuration. | This article gives an overview of the relationship between the variables of a PLC application and the different fieldbus either in master or slave configuration. | ||
The topics covered here mainly apply to the binary LLExec PLC runtime but can also be applied to most of the LogicLab PLC runtime portings. | The topics covered here mainly apply to the binary LLExec PLC runtime but can also be applied to most of the LogicLab PLC runtime portings. | ||
== | ==Fieldbus master== | ||
When the device is configured as a fieldbus master (Modbus, CANopen, EtherCAT etc.), the basic concept | When the device is configured as a fieldbus master (Modbus, CANopen, EtherCAT etc.), the basic concept relies on the mapping of PLC variables on the slave devices input and outputs datagrams. | ||
Revision as of 00:04, 23 February 2018
Introduction
This article gives an overview of the relationship between the variables of a PLC application and the different fieldbus either in master or slave configuration. The topics covered here mainly apply to the binary LLExec PLC runtime but can also be applied to most of the LogicLab PLC runtime portings.
Fieldbus master
When the device is configured as a fieldbus master (Modbus, CANopen, EtherCAT etc.), the basic concept relies on the mapping of PLC variables on the slave devices input and outputs datagrams.