![]() |
Creating a KNx point for Modbus Device Communication Error Situation - Printable Version +- Logic Machine Forum (https://forum.logicmachine.net) +-- Forum: LogicMachine eco-system (https://forum.logicmachine.net/forumdisplay.php?fid=1) +--- Forum: Gateway (https://forum.logicmachine.net/forumdisplay.php?fid=10) +--- Thread: Creating a KNx point for Modbus Device Communication Error Situation (/showthread.php?tid=408) |
Creating a KNx point for Modbus Device Communication Error Situation - savaskorkmaz - 03.10.2016 Hello , When we have a communication problem in Logic Machine, In modbus section of LM, modbus device turns red color and we can understand there is a communication problem. I would like to transfer this information as a Bacnet point but I need first , I need to transfer this communication failure in to KNX data point. How could i do that ? Regards, RE: Creating a KNx point for Modbus Device Communication Error Situation - Erwin van der Zwart - 03.10.2016 Hi Savaskorkmaz, I don't know if there is a function for this in the system, but i solved it once with a little resident script. Put your actions on the position where the logging is now (replace them with your action). Code: -- Check all modbus meters for connection BR, Erwin van der Zwart RE: Creating a KNx point for Modbus Device Communication Error Situation - admin - 04.10.2016 For now Erwin's script is the only solution, but we have this feature in our to-do list ![]() RE: Creating a KNx point for Modbus Device Communication Error Situation - Erwin van der Zwart - 04.10.2016 Hi, Here is a version with writing to KNX objects: Code: -- Check all modbus meters for connection BR, Erwin |