Each slave will receive the packet and check to see if the "address" matches. If it does, the slave device acts on the data that it received. The other slaves will ignore it and go back to whatever it was they were doing.
Thanks for this idea - it's quite easy and straight forward, so I'll give it a shot for sure.
Sorry for the amateur question, but I failed to see the advantages of 1487 against the 485. Can you, please, elaborate? Maybe I missed something important
If you have any Cat5 cable around, you can use one TP for data and then run power over the remaining 6 wires.
Exactly my idea. I know the recommendations for power transfer over Cat-5 cable, it's way more than I really need for my project.
attiny44,84,85, 2313?: The comparison chart shows that only the 2313 has a hardware UART. The 84 and 85 do have a USI, but EasyTransfer uses the UART. BUT...the EasyTransfer library now has a software EasyTransfer, so you can use the 44, 84 or 85 if you have enough program space.
As the only purpose of these chips will be to receive data and set one output according the data, or, in special cases, act as a counter using HW interrupt and on request send the number of counts as an answer, I assume there will be a lot of space left on all of the chips.
The number of pins is not a limitation, quite the opposite (I can make the design smaller), again considering the usage, so I am just fine with 8-DIP package (my only concern was the UART, but it seems to be handled by the EasyTransfer, as you pointed out).
I don't want to make free advertising, but the shop I am using has a better price for ATtiny85 and are quite fast as of delivery (http://www.tme.eu/sk/details/attiny85-20pu/mikroprocesory-atmel-avr-tht/atmel/#
However, I have to thank all of the people here - within 2 days I have been guided and provided with information I would have to gather manually for weeks using trial-and-error approach.