I'm looking for a solution that might be a replacement of PLC in a home automation. As I'm fun of RPI, Arduino and other like that solution I thought that it can be interesting path. However I would like to have more stability and at least 12V connectors. That is like I found your device. Unfortunately I do not know german and on english pages it is hard to find one, quite important for me, information. How many modules I can stuck together. I'm planning the installation with about 100 DI and DO, come communication over MODBUS and data exchange over MQTT with ESP8266 like devices as sensors. Time is not crucial, however I would like to have the loop time reasonably short. Where I can find such an information?
Regards
Michał
Number of modules
Few minutes after writing the post I was able to find the answer at your blog. https://revolution.kunbus.com/pibridge/
Hi Michał;
sorry for the difficulties you've had finding information in English. We're still on our way sorting things and trying to get the best access to information we can manage. But this may take some time and of course some feedback from you. Maybe you've missed our English blog? Try reading that bunch of information at https://revolution.kunbus.com/
At https://revolution.kunbus.com/pibridge/#more-96 we've described our backplane bus "PiBridge". This bus accepts up to 10 additional IO modules and thus you may add 10 RevPi DIO modules each with 14 digital inputs (12 to 24 V) and 14 digital outputs (12 to 24 V and 500 mA in highside switch mode). Please find the discription here:
https://revolution.kunbus.com/io-module/
The PiBridge has a cycle time of 10 ms so this is the rate of information refreshment in your process image.
So you may end up with a maximum of 140 Inputs and 140 outputs or you go a step further and use multiple revPi Core systems and connect them by Ethernet. If you write your own sw you can easily use Python or C to exchange parts of the 4kB process immage of several RevPi Cores or snchronize processes using a messages and "post boxes".
You may use Modbus driver sw which is out there for Raspberry Pi. We will add a configurable Modbus TCP master very soon but right now you need to wait for this or choose to install sw to be found for free in many places in the Internet.
For MQTT you may go the sam eway and use freeware out there in the Web or you choose to use logi.cals' PLC software which is preinstalled and can be used in a trial mode. logi.CAD3 (the ST Editor for the PLC) comes along with MQTT function blocks.
Feel free to ask if there are still questions. Hope I could answer most of them
sorry for the difficulties you've had finding information in English. We're still on our way sorting things and trying to get the best access to information we can manage. But this may take some time and of course some feedback from you. Maybe you've missed our English blog? Try reading that bunch of information at https://revolution.kunbus.com/
At https://revolution.kunbus.com/pibridge/#more-96 we've described our backplane bus "PiBridge". This bus accepts up to 10 additional IO modules and thus you may add 10 RevPi DIO modules each with 14 digital inputs (12 to 24 V) and 14 digital outputs (12 to 24 V and 500 mA in highside switch mode). Please find the discription here:
https://revolution.kunbus.com/io-module/
The PiBridge has a cycle time of 10 ms so this is the rate of information refreshment in your process image.
So you may end up with a maximum of 140 Inputs and 140 outputs or you go a step further and use multiple revPi Core systems and connect them by Ethernet. If you write your own sw you can easily use Python or C to exchange parts of the 4kB process immage of several RevPi Cores or snchronize processes using a messages and "post boxes".
You may use Modbus driver sw which is out there for Raspberry Pi. We will add a configurable Modbus TCP master very soon but right now you need to wait for this or choose to install sw to be found for free in many places in the Internet.
For MQTT you may go the sam eway and use freeware out there in the Web or you choose to use logi.cals' PLC software which is preinstalled and can be used in a trial mode. logi.CAD3 (the ST Editor for the PLC) comes along with MQTT function blocks.
Feel free to ask if there are still questions. Hope I could answer most of them
Unser RevPi Motto: Don't just claim it - make it!
Oops, so we were cross editing...anyway, hope my answer helps...Velerad wrote:Few minutes after writing the post I was able to find the answer at your blog. https://revolution.kunbus.com/pibridge/
Unser RevPi Motto: Don't just claim it - make it!
Thanks for the reply. I started to read your blog and watch movies. The project looks really promising according to my needs. Definitelly I'll be looking forward for any new stuff and informations.
