Communication protocols and architectures in iPMCC: Difference between revisions
From Electrical Installation Guide
(update_2018) |
Migrate2019 (talk | contribs) (removed empty lines at the beginning of wiki pages) |
||
| Line 1: | Line 1: | ||
{{Menu_Characteristics_of_particular_sources_and_loads}} | {{Menu_Characteristics_of_particular_sources_and_loads}} | ||
Lots of data are managed in an iPMCC application. An iPMCC application is typically made of 50 to 1000 motor starters. In order to supervise the system, it is necessary to send the motors’s information such as motor status, current value, alarm, etc. | Lots of data are managed in an iPMCC application. An iPMCC application is typically made of 50 to 1000 motor starters. In order to supervise the system, it is necessary to send the motors’s information such as motor status, current value, alarm, etc. | ||
Revision as of 17:36, 20 December 2019
Lots of data are managed in an iPMCC application. An iPMCC application is typically made of 50 to 1000 motor starters. In order to supervise the system, it is necessary to send the motors’s information such as motor status, current value, alarm, etc.
The traditional wire-to-wire connection is not an efficient and cost-effective way when there is a lot of data to be transmitted.
Today, communications via a network is the preferred way.
For an introduction on communication media, topologies, protocols ... please refer to Introduction to communication networks for electrical distribution.
