Hello, thanks for creating a post 
Before you start, be sure to search here in the forums, and in the Losant Documentation. There are a lot of helpful answers already there waiting just for you, and we are constantly improving them each day.
If you’re having difficulty with the platform, please include the relevant resource ID with your question so we can quickly look it up. IDs can be found on the URL:
/applications/:applicationId
/dashboards/:dashboardId
/applications/:applicationId/devices/:deviceId
/applications/:applicationId/workflows/:workflowId
IDs can be safely shared, but never share an access key or access secret.
Hi,
How many modbus sessions can handled by Edge Modbus master per second?
is there any limit for modbus master to connect slaves(actual limit is 247)?
Thanks,
Chandra.
So @Chandhu_Dangudubiyya, I did some research for you and here is what I discovered:
While Modbus RTU is limited to 247 slaves. The Modbus/TCP protocol itself has no limit for the number of slaves (source: here and here).
So, this means that the limitation for the Edge Agent, which is serving as the Modbus TCP client (or Modbus Master), is a software and hardware limit.
In terms of software, the only limit is a workflow timeout. Edge Workflows have a timeout of 60 sections. The Modbus Node will open and close the TCP per node. The limit would be the number of TCP connections you can open/close within 60 seconds, which brings us to the hardware limit.
Since Edge Workflows run on gateway hardware you can define, how quickly and how many workflows the Edge Agent can run is directly tied to the resources (CPU, memory, etc.) on the Gateway.
To sum things up, there no define limits here for the Edge Agent; it’s dependent on your environment. All things considered, you should be able to make many connections using an average gateway. As far as we know, no one has hit any limit yet. If you do, let us know and we’d be happy to help resolve.