Schedule scripts are not synchronized from node to portal. If local schedule should be used in node/portal the script needs to be created in both Web Port systems.
In System settings/Server/Schedule there is a setting for how often Web Port will synchronize local schedules in the background. Default is 10 minutes.
When opening a local schedule in the portal the latest synchronized value is shown and a background read operation is started to update the values.
If there are problems synchronizing files, trends or values, check that the portal has the same or newer version of Web Port compared to the node, and that the system times are synchronized in the same time zone and time format.
Certificate problems in portal
If the Portal has e.g. a self-signed certificate the node will not allow connection to the portal. This can be turned off under System settings/Communication/Drivers/DrvNode and check Disable certificate validation.
Resetting a node in the portal works like this:
The portal sends a list of all the node files it has. This list is matched with the files available on the node and a list of changed files (new, changed, removed) is created. The files in this list is sent to the portal, and the no longer valid ones are removed from the portal.
Alarm and trend history, as well as set times for these, are not touched. If you want to re-sync historic data, change current trend synchronization <- to the current time.
The node and the portal will set status Connecting if no contact for more than 60 seconds.
New connection attempts are normally done every second (if no ongoing transactions).
If a node is removed in the portal, it will reconnect from the node and will appear again within 60 seconds.
Changing tag prefix
Tag prefix can be changed until the node has been activated in the portal. To change it after it has already been activated, the node needs to be removed from the portal. It will be reconnected again and a new tag prefix can be set before activating.