eHouse 1 - Home Automation - state controller in binary form @ Home Automation eHouse.Pro
eHouse Home Automation, ysc Building Management ysc version 1 - the frame of the image controller system Home Automation. They create a fully functional, efficient software for own control panels requiring them to apply direct visualization decode eHouse 1 driver status in binary form. Depending ysc on the choice of mode in normal or extended address (Extended_address), frames sent status of the driver is as follows (in brackets marked difference in street mode extended). This mode is required to work under the supervision of drivers CommManager and send messages events destination location, location Neat destination device can tell the sender receives events (hand - shaking). If the Rs interface - 485 definitely ysc not recommend direct attempts to connect to the driver, such as sending some commands can cause memory cleaning program (firmware) controllers which could end their lives. Other commands or random signals in RS - 485 can undermine the stability of the system or definitely slowing his work. Native eHouse Automation Controllers should be working under the supervision of producer application "eHouse. exe ". For security, you can read the status of drivers without connecting to the eHouse application. Exe (UDP protocols and LAN). This is - successful readers, by loading both software and controllers, and what is more, not intrusive in any way transfer protocol via RS - 485. The situation is different when eHouse_1 controllers working under supervision CommManager. CommManager controller can send status (1 and CommManager eHouse integrated in a package), the UDP LAN and access to this data connection and non - invasive as well as directly from CommManager or other Ethernet ysc controllers eHouse. Q receives data on UDP status we can not hurt the driver, with a maximum of incoming data entry misrepresented. EHouse system does not send anything to secure the UDP driver, a driver does not matter if the customer receives the data sent over UDP or not, or if the customer ysc count is 0 or 250. Q receives data from eHouse home automation systems, UDP is safe and not packed in any way or software controllers eHouse, send broadcasts (UDP_broadcast) in the LAN. Status box has the following format: <; ; data_size>; ; (<;; The_destination_address_H>; <;; The_destination_address_L>;;) ysc <; ; Local_addres_H>; ; <; ; Local_address_L>; ; <; ; order>; ; <; ; data_1>; ; . . . . . <; ; Data>; ysc ; <; ; Data_N>; ; <; ; data_size>; ; (<;; The_destination_address_H>; <;; The_destination_address_L>;;) <; ; Local_address_H>; ysc ; <; ; Local_address_L>; ; <; ; order>; ; <; ; data_1>; ; . . . . . <; ; Data>; ; <; ; Data_N>; ; <; ; 0>; ; Normal Mode / VS. (School of the longest Address) 1. size of the data (the data size) 2. Address_H_target (Address_H_target) 3. Address_L_target (Address_L_target) 4. Control_command (Address_H_of_local_controller_return_path) 5. Data_1_byte (Address_L_of_local_controller_return_path) 6. Data_2_byte (Control_Command) 7 Data_3_byte (Data_1_byte) 8. . rest of the data for a given order. If you send the status of the driver; ysc s control orders 's'. Continue monitoring the data in binary form to minimize the transfer of information across a range of RS - 485. For security, the data are attached check - reports incorrect number eliminate emissions do. Send order status is 's', frame Statue of drivers Home Automation eHouse 1 and a description of the byte number (index changes depending on the operating mode (normal or extended_address). ysc This constant shifting shown below TCP_INDEX_INC. Both Depending on the mode, it can adopt a value of 3 for the location extended or 0 normal transmission. When writing software, you might consider this variable as a parameter, because it allows us to easily manipulate data in later versions if the frame is moved in one way or another. index each image frame byte of eHouse driver 1 (the start of the frame): = 1 + +2 STATUS_ADC TCP_INDEX_INC; / / Value of MSB = A/D_converters_2_bytes_1B, 2B = lsb!. STATUS_OUT = 17 +2 + TCP_INDEX_INC; ysc / / output first digital state index
/ / Each output 1 lsb least bit number, MSB largest STATUS_IN = 20 +2 + TCP_INDEX_INC; / / Digital D 'state lsb smaller number, MSB largest STATUS_INT = 21 +2 + TCP_INDEX_INC; / / United States of digital inputs (Interrupt) lsb smaller number, MSB largest STATUS_OUT25 = 22 +2 + TCP_INDEX_INC; / / Èkstran state from 25. . 32 same way as production STATUS_LIGHT = 23 +2 + TCP_INDEX_INC; / / A message for one dimmer dimmer STATUS_ZONE_PGM 1B = 26 +2 + TCP_INDEX_INC; / / Name of area
eHouse Home Automation, ysc Building Management ysc version 1 - the frame of the image controller system Home Automation. They create a fully functional, efficient software for own control panels requiring them to apply direct visualization decode eHouse 1 driver status in binary form. Depending ysc on the choice of mode in normal or extended address (Extended_address), frames sent status of the driver is as follows (in brackets marked difference in street mode extended). This mode is required to work under the supervision of drivers CommManager and send messages events destination location, location Neat destination device can tell the sender receives events (hand - shaking). If the Rs interface - 485 definitely ysc not recommend direct attempts to connect to the driver, such as sending some commands can cause memory cleaning program (firmware) controllers which could end their lives. Other commands or random signals in RS - 485 can undermine the stability of the system or definitely slowing his work. Native eHouse Automation Controllers should be working under the supervision of producer application "eHouse. exe ". For security, you can read the status of drivers without connecting to the eHouse application. Exe (UDP protocols and LAN). This is - successful readers, by loading both software and controllers, and what is more, not intrusive in any way transfer protocol via RS - 485. The situation is different when eHouse_1 controllers working under supervision CommManager. CommManager controller can send status (1 and CommManager eHouse integrated in a package), the UDP LAN and access to this data connection and non - invasive as well as directly from CommManager or other Ethernet ysc controllers eHouse. Q receives data on UDP status we can not hurt the driver, with a maximum of incoming data entry misrepresented. EHouse system does not send anything to secure the UDP driver, a driver does not matter if the customer receives the data sent over UDP or not, or if the customer ysc count is 0 or 250. Q receives data from eHouse home automation systems, UDP is safe and not packed in any way or software controllers eHouse, send broadcasts (UDP_broadcast) in the LAN. Status box has the following format: <; ; data_size>; ; (<;; The_destination_address_H>; <;; The_destination_address_L>;;) ysc <; ; Local_addres_H>; ; <; ; Local_address_L>; ; <; ; order>; ; <; ; data_1>; ; . . . . . <; ; Data>; ysc ; <; ; Data_N>; ; <; ; data_size>; ; (<;; The_destination_address_H>; <;; The_destination_address_L>;;) <; ; Local_address_H>; ysc ; <; ; Local_address_L>; ; <; ; order>; ; <; ; data_1>; ; . . . . . <; ; Data>; ; <; ; Data_N>; ; <; ; 0>; ; Normal Mode / VS. (School of the longest Address) 1. size of the data (the data size) 2. Address_H_target (Address_H_target) 3. Address_L_target (Address_L_target) 4. Control_command (Address_H_of_local_controller_return_path) 5. Data_1_byte (Address_L_of_local_controller_return_path) 6. Data_2_byte (Control_Command) 7 Data_3_byte (Data_1_byte) 8. . rest of the data for a given order. If you send the status of the driver; ysc s control orders 's'. Continue monitoring the data in binary form to minimize the transfer of information across a range of RS - 485. For security, the data are attached check - reports incorrect number eliminate emissions do. Send order status is 's', frame Statue of drivers Home Automation eHouse 1 and a description of the byte number (index changes depending on the operating mode (normal or extended_address). ysc This constant shifting shown below TCP_INDEX_INC. Both Depending on the mode, it can adopt a value of 3 for the location extended or 0 normal transmission. When writing software, you might consider this variable as a parameter, because it allows us to easily manipulate data in later versions if the frame is moved in one way or another. index each image frame byte of eHouse driver 1 (the start of the frame): = 1 + +2 STATUS_ADC TCP_INDEX_INC; / / Value of MSB = A/D_converters_2_bytes_1B, 2B = lsb!. STATUS_OUT = 17 +2 + TCP_INDEX_INC; ysc / / output first digital state index
/ / Each output 1 lsb least bit number, MSB largest STATUS_IN = 20 +2 + TCP_INDEX_INC; / / Digital D 'state lsb smaller number, MSB largest STATUS_INT = 21 +2 + TCP_INDEX_INC; / / United States of digital inputs (Interrupt) lsb smaller number, MSB largest STATUS_OUT25 = 22 +2 + TCP_INDEX_INC; / / Èkstran state from 25. . 32 same way as production STATUS_LIGHT = 23 +2 + TCP_INDEX_INC; / / A message for one dimmer dimmer STATUS_ZONE_PGM 1B = 26 +2 + TCP_INDEX_INC; / / Name of area
No comments:
Post a Comment