[Feature]: S7 asset to change load balacing with connection resource

[GoncaloEsi]

Tell us about your request

Add some mechanism to share resources so that a heavy loaded (high tag number) asset does not irretrievably crash.

Which component(s) is this request for?

• Coreflux Broker
• Coreflux Hub
• Flux Assets
• Flux Language
• Power Ups
• User Experience (UX)
• Documentation
• Conceptual Features

Is your feature request related to a problem? Please describe.

We have a case of an S7ToMqtt asset with 300(ish) tags that is crashing mid usage. Curiously, we have the exact same asset and asset config on running on another computer, but running Coreflux without GUI (Mqtt CLI). Even the computer and OS is the same (Ryzen 7).

These are the parameters (not including tags):

"MQTTParameters": {
"Port": 1883,
"Address": "127.0.0.1",
"IsAnonymous": true,
"Username": "",
"Password": "",
"EnableTLS": true,
"EnableDebugTopic": true,
"DebugTopic": "test/debugtopic"
},
"SiemensParameters": {
"IP": "192.168.10.1",
"PLCRack": 0,
"PLCSlot": 1,
"Retries": 0,
"RetryTimeInSeconds": 15,
"RefreshTimeInMs": 500,
"ConnectionResource": 3
},

I am not sure if the RefreshTimeInMs is the culprit here, because as I said, this is a replica of something that did not exhibit this problem.

Describe the solution you'd like

1 - Clarify on the documentation to experiment with different RefreshTimes and tune the asset

2 - Add some mechanism that takes care of a high tag number to prevent crashes

Describe alternatives you've considered

Install 2 asset instances and divide the load

Is this request for a new asset?

No.

Additional context

No response

[CarlosSous]

Same problem that i have, The solution was using 2 assets with 2000 ms in RefreshTimeInMs. But in my case i have 2500 tags with many strings variable.

[HugoAVaz]

Given this information, it's possible that the issue with the S7ToMqtt asset crashing could be related to the management of connection resources. If the asset is handling a large number of tags, it might be exceeding the available communication resources, especially if other services are also using resources. Adjusting the configuration to better align with the resource limitations of the specific CPU model in use could help mitigate this issue. Additionally, considering the allocation of resources between different types of communication (S7, HMI, OUC, etc.) and adjusting the setup accordingly might also be beneficial.

[GoncaloEsi]

Same problem that i have, The solution was using 2 assets with 2000 ms in RefreshTimeInMs. But in my case i have 2500 tags with many strings variable.

In my case, I need as low of a RefreshTime as possible mainly for the manual buttons of the Unity3D HMI, some of these buttons control motors and axes.

Maybe using these tags on one of the assets with the same RefreshTime I'm using now (500) and the things that are not as critical on the other asset instance, with a larger RefreshTime.

[HugoAVaz]

It would be good to have something like a load balacing. each tag on one connector we place a connection resource?