2 hours ago
This bacnet client app is very limited and it can only handle arond 50 objects. If you use more then you will struggle. Make sure to not enable bacnet server on the device wher bacnet client is used.
I strongly reccomend to uninstall this app and do the integration in Script with direct connection mode. Use single resident script for reading and event scripts for writing.
https://kb.logicmachine.net/libraries/ba...ction-mode
You will need backnet package for this https://dl.openrb.com/lm-25-imx6/pkg/
If I understand your problem correctly that you have two LMs with exact same group structure and you must individually map them to 3rd LM as they can't overlap then the simplest solution which does not require any scripting is to use different aprouch.
You can use MQTT Client app (not MQTT cloud) and local Broker app and then you can just individually link objects to MQTT topic. This way you have 100% freedom how this will be linked between groups. In a Client app you just select a group and give it Topic name, This name must be used on another LM in Client app and mapped to another group. There is no need for any additional conversions. Between LMs this works out of the box.
Client app must be on all LMs and on one you need broker and all clients must be connected to this broker.
See this video, its super simple
https://app.screencast.com/898mWbafh0pdr
As you can see on the LM where broker is inslalled I'm using 127.0.0.1 as host IP as this is on the same device.
I strongly reccomend to uninstall this app and do the integration in Script with direct connection mode. Use single resident script for reading and event scripts for writing.
https://kb.logicmachine.net/libraries/ba...ction-mode
You will need backnet package for this https://dl.openrb.com/lm-25-imx6/pkg/
If I understand your problem correctly that you have two LMs with exact same group structure and you must individually map them to 3rd LM as they can't overlap then the simplest solution which does not require any scripting is to use different aprouch.
You can use MQTT Client app (not MQTT cloud) and local Broker app and then you can just individually link objects to MQTT topic. This way you have 100% freedom how this will be linked between groups. In a Client app you just select a group and give it Topic name, This name must be used on another LM in Client app and mapped to another group. There is no need for any additional conversions. Between LMs this works out of the box.
Client app must be on all LMs and on one you need broker and all clients must be connected to this broker.
See this video, its super simple
https://app.screencast.com/898mWbafh0pdr
As you can see on the LM where broker is inslalled I'm using 127.0.0.1 as host IP as this is on the same device.
------------------------------
Ctrl+F5
Ctrl+F5