Difference between revisions of "Mitsubishi"
(Created page with "The MITSUBISHI air-conditioning system equipped with one of the centralized controllers among G-50, GB-50, or AG-150 allows for remote control and supervision, via Ethernet co...") |
|||
Line 12: | Line 12: | ||
This I/O Server complies with the XML API for the Mitsubishi M-NET proprietary protocol. | This I/O Server complies with the XML API for the Mitsubishi M-NET proprietary protocol. | ||
− | {{ | + | {{note|In order to connect the Mitsubishi controller with HSYCO, the Web Monitor and Annual Schedule pin codes activation is required. On request, Mitsubishi will provide a document to be compiled for the activation.}} |
All the devices comprising the M-NET architecture are assigned an address ranging from 0 to 250. | All the devices comprising the M-NET architecture are assigned an address ranging from 0 to 250. | ||
Line 19: | Line 19: | ||
Further, it is possible to expand the system using up to three ECs which allow to replicate a full M-NET architecture under each EC. In this case, modules are addressed specifying both the EC and the group they belong to. | Further, it is possible to expand the system using up to three ECs which allow to replicate a full M-NET architecture under each EC. In this case, modules are addressed specifying both the EC and the group they belong to. | ||
− | |||
== HSYCO Configuration == | == HSYCO Configuration == |
Revision as of 14:55, 13 March 2014
The MITSUBISHI air-conditioning system equipped with one of the centralized controllers among G-50, GB-50, or AG-150 allows for remote control and supervision, via Ethernet communication, of the whole framework.
Contents
Communication
The Mitsubishi controller replies on the port 80 (10 sockets) or 1025 (4 sockets) of its IP address.
M-NET Configuration
This I/O Server complies with the XML API for the Mitsubishi M-NET proprietary protocol.
All the devices comprising the M-NET architecture are assigned an address ranging from 0 to 250.
Conditioners and lossnay modules can be associated to 50 different groups (indexed from 1 to 50). The control of these modules is thus performed addressing the group they belong to.
Further, it is possible to expand the system using up to three ECs which allow to replicate a full M-NET architecture under each EC. In this case, modules are addressed specifying both the EC and the group they belong to.
HSYCO Configuration
Options
ID | Default | Values | Description |
---|---|---|---|
gui | true | true | enable support for the UI object, UISET actions and USER commands |
false | disable UI support | ||
startupevents | false | true | generate IO events also during the driver’s start-up phase |
false | start generating events only after HSYCO is aligned with the current status of the system | ||
pollinterval | 20 | n > 0 | the data acquisition interval, in seconds |
ec | 0 | 0 - 3 | specifies the number of ECs connected to the main controller. A value of 0 indicates that no EC is used |
Datapoints
ID | Value | R/W | Description |
---|
User Interface
In the following tables, replace <n> with a group number ranging from 1 to 50, and replace <m> with an address from 0 to 250. If one or more ECs are used (i.e. the option field “ec” is set to a value greater than 0), it is necessary to specify the EC number we are addressing. To this end, prepend the string “ecS.” (with S ranging from 1 to the specified value of ECs) to the target group or the address.
For instance, when an EC is used the following ID or name is not correct:
mits.g1.power
The correct one to be used is the following:
mits.ec1.g1.power
UISET Actions
USER Commands
ID | Attribute | Set to |
---|
Name | Param | Action |
---|
Release Notes
3.0
- initial release versione
Mitsubishi and M-NET are registered trademarks of MITSUBISHI ELECTRIC, Inc.