This section explains how to handle the different errors that may occur during the ‘’’STM32cube Monitor’’’ experience. Error can occur either while designing ‘’flows’’ and ‘’nodes’’ or while executing ‘’dashboard’’.
1. Design mode errors
In design mode view, errors are notified in different ways, hereafter is listed how the errors or warning are managed.
1.1. Node configuration
If node configuration is erroneous, a red triangle icon is displayed on top right of the node and missing configuration parameter text box is rounded in red when editing the node.
In order to solve this issue, you need to fill the missing parameter.
1.2. Node status
Upon error on connection or configuration, both shape and text status information of the impacted node is updated to inform of the error and give some details in the text. See https://nodered.org/docs/creating-nodes/status to get more informations.
Depending on the impacted node and the status, the solution to the issue may differ. Hereafter are listed some examples and their possible solution.
| Node | Error | Possible solution |
|---|---|---|
| acq in or acq out | not connected ! Device not found (6) | Verify the physical connection of your board |
| processing | processing off - following outputs not valid : <expression> | Correct the non valid expression and/or statistic |
| processing | processing off - variable node not present or disabled | Verify the processing Group Name property |
| variable | snapshot - invalid trigger | Verify you have a snapshot capable firmware |
| variable | off - invalid frequency | Change the sampling frequency |
1.3. Parameter editing
During edition of a parameter, till the value is not valid (empty, to short, wrong type…) the editor box appears red rounded.
1.4. Notification
2. Dashboard errors
Both acq in and processing nodes have an error output where errors and warning messages will be sent. In order to be informed of those errors, those ports can be connected to a debug node or to notification node or both of them. Output messages topics can take two values error or warning depending on the level of issue, then thanks to switch node, topic can be filtered and be treated separately. Hereafter is an example of such flow.
See https://nodered.org/docs/user-guide/nodes#debug and https://nodered.org/docs/user-guide/nodes#switch to get more details on debug and switch nodes.