Planon IoT Connector - fields
The following table lists the names and descriptions of fields specific to the Planon IoT connector.
Field
Description
Code
Enter a unique code for the connector.
Name
Enter a description for the connector.
Comment
Enter notes (optional). The notes that you enter will be visible to the Planon administrator only.
Data engine
Select the data engine to which you want to link the connector.
System status
Indicates the connector status:
Active – the connector is operational.
Inactive – the connector is not operational.
Immeasurable – the status of the connector cannot be resolved. The cause of the error (going from Active to Immeasurable) is printed in the event log.
Activate monitoring mode?
When set to Yes, a record will be added to the event log at the next polling. You can activate monitoring mode by clicking Monitor communication on the action panel.
* 
After a successful run, the application switches off the Activate monitoring mode? and Synchronize fields automatically. However, if encountering issues, the application will continue to try and do this for some time, clogging the process. To overcome this situation, you can inactivate the connector. By inactivating the connector, the Activate monitoring mode? and Synchronize fields will be switched off and the process is reset. After activating the connector again, you can manually enable these fields.
Polling count (time-out)
For Planon IoT connector: Polling count should be managed by the Planon IoT platform to avoid duplicate checks. Therefore, in this situation, leave the field empty.
For other connectors:
When a Polling count (time-out) is set, a time-out check is executed at the end of each polling cycle performed by the data engine.
This setting determines whether a connector or measurement point needs to be set to Immeasurable.
Specify the number of polling cycles for the connector to time-out (minimum value is 5).
If this field is available and a value is filled in, the AWM connector will be set to Immeasurable if AWM does not receive a response within x polls of the AWMDataEngine.
See also:
Polling offset
To balance the load of the polling cycle, you can use this field to fine-tune the polling cycles.
When specified, the connector will not be polled immediately in the first polling cycle, but it will wait for the polling cycle that matches the offset.
Example
If the Polling offset is 2, polling will only happen every second cycle.
Poll every x cycles
To balance the load of the polling cycle, you can use this field to fine-tune the polling cycles.
When specified, the connector will only poll every <value specified here> cycles.
Example
If the Polling interval on the data engine is set to 60 seconds and the Poll every x cycles is 5, then the polling will be done every 300 seconds.
Last polling response
Date time stamp of last polling response (heart beat) received by the connector or its measurement points (server time zone).
Email address for notification
When set to Yes, an email will be sent to the members of the Email address(es) (AlertEmailList) if the measurement point/connector is set to Immeasurable.
Email address(es)
Enter the email address of the person(s) who should receive an email alert when the connector is set to Immeasurable.
To enter multiple email addresses, use a comma (,) or semi-colon (;) as separator.