+- Smart Home Automation Forum (https://www.kincony.com/forum)
+-- Forum: Technical Support (https://www.kincony.com/forum/forumdisplay.php?fid=1)
+--- Forum: Suggestions and feedback on KinCony's products (https://www.kincony.com/forum/forumdisplay.php?fid=39)
+--- Thread: E16V3 - Documentation issues (/showthread.php?tid=9071)
E16V3 - Documentation issues - ldebacker - 02-22-2026
Hello,
There are 2 issues with the documentation of the 4 dip switches to set the slave ID on the bus.
Let's call, from left to right, the 4 dip switches respecively A0 A1 A2 A3.
1/
The documentation mentions that when A3 is in OFF state, this means the outputs are controlled by the input terminals (and when in ON state, it is controlled by MODBUS).
It is actually the reverse: When A3 is in OFF state, the device is controlled by MODBUS.
2/
The documentation specifies that when identifying the slave id, the value of the slave id is: (A0 * 1 + A1 * 2 + A2 * 4) + 10.
so: A0=ON A1=OFF A2= OFF should give slave ID (1 * 1 + 0 * 2 + 0 * 4 ) + 10 = 11 (according to the table in the documentation)
It is actually the reverse: from trials/errors, the formula to apply seems to be (A0 * 4 + A1 * 2 + A2 * 1) + 10
so: A0=ON A1=OFF A2= OFF is, in reality slave ID (1 * 4 + 0 * 2 + 0 * 1 ) + 10 = 14 (from experience).
RE: E16V3 - Documentation issues - admin - 02-25-2026
thanks for your suggesiton. we will update it.
RE: E16V3 - Documentation issues - bergerb - 07-24-2026
I guess it concerns all ExxV3 Models, since the documentation is the same. I was really scratching my head yesterday.
What exactly does the SW4 Switch (A3) do?
The Documentation states in 4.2:
The output control mode is determined by the 4th DIP switch (see Section 5 for DIP switch settings):
- Local Control Mode: When the 4th DIP switch is set to "OFF", the output terminals are controlled by the input terminals directly.
- Remote I/O Mode: When the 4th DIP switch is set to "ON", the entire output terminals work as remote I/O, controlled via the MODBUS RTU protocol.
Then it also states in 5.1:
Local Control = ON = Outputs are controlled by the input terminals
Remote I/O Control = OFF = Outputs are controlled via MODBUS RTU
which is directly contradicting to what is stated above
You also have this info in the product page: https://www.kincony.com/rs485-modbus-din-rail-relay-module-e24v3-16a-removable-relay.html
and here: https://www.kincony.com/forum/showthread.php?tid=8965&highlight=e24v3
4 bit DIP switch:
bit 1-2-3: set RS485 address
bit 4: ON: disable RS485 communication OFF: enable RS485 communication
RS485 protocol: standard MODBUS protocol. default baud rate: 38400bps
It also states:
5.2 Slave ID:
- If no DIP switches (A0-A2) are toggled (all OFF), the default SLAVE ID is 1 (only when the 4th DIP switch is NOT set to ON).
- When the 4th DIP switch is set to ON, the SLAVE ID is determined by A0-A2 (calculated as above), and the default ID (1) is not applied.
General assumptions by me:
A DIP switch is "ON", when its position is closer to the label "ON" on the DIP-Switch-Block - in the case of this board, in the UP-Position
So - now to what I have observed:
Once you switch on SW4, all Relais go high, and there is no longer ANY control over the inputs. Not via RS485, not via Digital Inputs and not via the manual override inputs.
The board seems to only work when SW4 is OFF.
Additionally, the text "If no DIP switches (A0-A2) are toggled (all OFF), the default SLAVE ID is 1 (only when the 4th DIP switch is NOT set to ON)." seems to be incorrect.
The Slave ID is 10, when all 4 switches are off (which I only found out by your Youtube-Video)
you also wrote in a Youtube-comment, that the DIP switch settings are only checked on power up, is this really true for all 4 switches? Because I can Switch SW4 on, while everything is running, and all the relais still go to high.
-> The Info that DIP Switch settings are only checked on power up would be really helpful in the documentation.
All the sample frames also send to Slave ID 1, which I never got to work.
The checksums also seem to be incorrect in the sample frames.
Last question - how does the reset actually work? If I long press the RST button, nothing seems to happen? I'd expect the board to start rapdily blinking again - the microcontroller booting again?