Appendix¶
Technical specifications¶
The following table contains the technical specifications of Visual Flow Creator:
| Description | Limitations |
|---|---|
| Maximum number of flow tabs per user in the working area | 30 |
| Maximum number of nodes within a flow tab | 200 |
| Maximum project size limit | 3 MB |
| Maximum number of projects | 10 |
| Maximum calculation duration of a flow | 30 seconds |
| Maximum number of the node context variables in function node | 5 per node |
| Maximum number of the flow context variables in function node | 20 per tab |
| Maximum number of the global context variables in function node | 100 per user |
| Time period for saving data in the context of the "function" node after the last read/write access or system reboot | 6 months |
| Maximum number of context tags within the "function" node | 1 |
| Maximum file size for data transmission within the "read file" and "write file" nodes | 1 MB |
| Maximum number of time series values per read operation | 2000 |
| Maximum limit of global context variables | 100 |
| Maximum size of a global context for the Production / Start for Free environments | 5 MB / 128 KB |
| Maximum flow context variables | 20 |
| Maximum size of a flow context for the Production / Start for Free environments | 5 MB / 128 KB |
| Maximum node context variables | 5 |
| Maximum size of a each node context for the Production / Start for Free environments | 2 MB / 128 KB |
| Maximum size of a environment context for the Production / Start for Free environments | 5 MB / 128 KB |
| Maximum size for an email notification | 250 KB |
| Maximum size of a function node for all environments | 1 MB |
| Maximum limit of emails per day per environment | 1000 |
| Maximum limit of MQTT messages per environment in 1 minute | 10 |
| Maximum limit of MQTT messages per environment in 1 hour | 500 |
| Maximum number of HTTP-In requests per second per user | 2 |
| Maximum size of data that combine node can cache | 12KB |
Visibility of flows/ execution time of nodes
- All created flows are visible for all users of a environment. You cannot modify the flows of another user.
- The execution time of all nodes for a environment can be limited depended on the application and platform load.
Differences between Visual Flow Creator and Node-RED¶
The following table shows the difference between Visual Flow Creator and Node-RED:
| Visual Flow Creator | Node-RED |
|---|---|
| Maximum running duration of one flow is 30 seconds (or 2 minutes with the power mode option). | Maximum running duration of one flow is not limited. |
| Application runs on AWS and Azure. | Application runs on local system. |
| Maximum 5 custom modules can be uploaded for the custom nodes. | No limit to create custom modules using Node-RED library. |
| No palette manager for the additional nodes. | All nodes can be managed from the palette manager. |
| Industrial IoT authentication or private key is required to access the http endpoint using "Http-in" node. | No authentication is required to access the http endpoint with "Http-in" node. |
No access to msg.req and msg.res objects in function nodes. | Access to msg.req and msg.res objects in function nodes is available. |
| No authentication is required to access APIs. | Authentication is required to access APIs. |
| Name of the global context variable is "glob". | Name of the global context variable is "global". |
| "Tenant" context variable is available, in additional to "glob", "flow" and "context". | No "environment" context variable. |
| Many Industrial IoT specific nodes are available | No specific Industrial IoT nodes. |
| Dashboard nodes are extended to support multi-user functionality using "Only one browser" option in edit dashboard node properties. | No dashboard nodes are extended to support multi-user functionality |
| Dashboard Viewer is available. | No separate Dashboard Viewer. |
| Insights Hub Monitor plugin is available. | No Insights Hub Monitor plugin. |
| No keyboard settings. | Keyboard settings is available. |
Last update: January 22, 2024