GEN 2 - Communication Init Process

The below section explains which RS485 messages are used to add a module. Please note that the associate API and CLI instructions are not covered here.

To add modules to bus, the following steps are executed:

1. The bus must be placed in init mode (by using API or CLI command) resulting in the below RS485 broadcast message

Request M->S

The Modules will have the orange status led ON to indicate that these modules are in Init state

1. When pressing the init button of 1 module, below message will be sent

sent when init button is pressed S->M

3a. When Module NE="N", the Master controller will check in his module list if the requested ID (ID0..ID3) is unique. If unique, below message will be returned to the Slave to confirm that is ID is unique and that he can change his Module NE status from "N" to "E".

Response M->S

The appropriate API or CLI responses will be sent on the RS232 bus

3b. When Module NE="N", the Master controller will check in his module list if the requested ID (ID0..ID3) is unique. If not unique, the Master controller will indicate on his RS232 (API or CLI mode) interface with the appropriate message that a double ID event occurred and that the user must press the button again. The Master will automatically sent an Init message again which will generate new random ID's for all modules with Module NE="N".

Request M->S

Restart Step 3

3c. When Module NE="E", the Master controller will check his module list, if the module is in the list, an RS232 message (API or CLI) will be sent indicating this is an existing module which is in the list. No RS485 message will be sent to the slave module.

3d. When Module NE="E", the Master controller will check his module list, if the module is not in the list, an RS232 message (API or CLI) will be sent indicating this is new module added in the module list. No RS485 message will be sent to the slave module.

1. Restart at step 2 until all modules are done

1. Put the Bus in Live Mode again

Request M->S