...
Reset Configuration
Factory Reset
Or delete a device from the Building X portal and re-activate it using the Activation key when moving it from one subscription to another.
Apps out of sync message may occur when onboarding a F200
If you encounter this error message perform one of the following steps
Click the Synchronize button.
Delete the device out of Building X and then re-add it again.
Connect to the gateway and perform a reset configuration.
NOTE: When selecting reset configuration, general settings, such as network connection mode, password and device name are deleted. Only certificates for cloud communication and registration will stay. During reset, the device will stay online.
If all the above steps fail, contact your local support channel.
Gateway FAQs
What happens if I do a factory reset?
Doing a factory reset, all configuration data and installed apps will be deleted. The activation ID doesn't change and the device will still be registered in the portal. After the reset has been completed, you can remotely access the device logging in to the gateway with the default username and password. You’ll then need to re-install the applications.
How to Perform a Factory Reset on a F200?
Remove power from the F200.
Press and hold the SCV button.
Apply power to the F200.
The lights will be on for about 5 seconds and then turn off.
When the run light turns on about 20 seconds later, release the SVC button.
The lights will turn back on for approximately 10 seconds and then turn off.
Wait until the run light turns on solid. The controller has been factory reset, which should take about 20 seconds.
Note: If you can connect locally to the gateway, you can click on the Maintenance and click the Reset to Factory button as an alternative method.
What Endpoints needed to be whitelisted on the firewall?
The following is a list of endpoints that needed to be whitelisted.
MQTT
mqtts://mqtt.connectivity.siemens.com:443
Firmware Update Service
Container Image Registry
Bootstrap
Authentication Proxy
NTP Server
0.siemens.pool.ntp.org:123(TCP/UDP) (Main Server)
1.siemens.pool.ntp.org:123(TCP/UDP) (Backup Server)
2.siemens.pool.ntp.org:123(TCP/UDP) (Backup Server)
3.siemens.pool.ntp.org:123(TCP/UDP) (Backup Server)
How do you check to see if the F200 can communicate with the endpoints?
Connect to the F200 gateway.
Click on Network and select IP.
At the bottom of the screen there is a network diagnostic button.
How to check the Internet Bandwidth and latency?
Service performance is based on the Internet Bandwidth and latency.
A speed of at least 1 Mbit/s is recommended for best user experience.
With 500Kbit/s, firmware download could take an hour with possible retries and firmware update my take up to two hours.
Recommended latency is less than 2 seconds.
Test is between Building X cloud servers and the device, not to internet speed test of the device on the network.
Connect to the F200 gateway.
Click on Network and select IP.
Towards the middle of the screen there is a network speed button.
Can you change port 8090 that the F200 uses?
You cannot change port 8090 that the F200 currently uses.
FIN Project FAQs
Ways to prevent a Disk Full Emergency Shutdown Error Message
The "disk full" error indicates that there are too many files exceeding the device storage capacity. Numerous combinations of factors could contribute to this issue, such as:
Excessive log files: Logs may be growing in size. You can reduce the maximum age of the files via the Host → Settings under the Log section.
Accumulated histories: F200s have limited space and therefore histories should be cleared after a certain time. Refer to the following article for steps on clearing histories: Clearing Histories.
Exceeding the point limit (5K points).
Snapshot accumulation: Ensure there aren't too many snapshots. You can control the number of snapshots on the F200 controller by enabling purge settings. For instructions on setting up purge settings, see this article: Purge Settings.
Adding large files: Large images, zips or any other file types to a project can reduce space on the device. Don't go above 90% cumulative. Look at the Disk Space in the Host → Debug.
Run the following queries in Folio → Launch to help clean up some zip files to reduce space.
To delete failed snapshot zip files:
| Code Block |
|---|
readAll(file and finFileUpload).findAll(x => x->file.toStr == "application/x-zip-compressed").finHardDelete |
To delete backed zip files:
| Code Block |
|---|
readAll(file and bak and finBackup).findAll(x => x->file.toStr == "application/zip").finHardDelete |
To delete other zip files:
| Code Block |
|---|
readAll(file and finFileUpload).findAll(x => x->file.toStr == "application/zip").finHardDelete |
If there are unused or not needed template .fst files, be sure to delete those as well. They can be found in DB Builder → Templates tree to delete.
How to re-register to Edge2Cloud on a F200?
...
The HTTPS Timeout property can be found in the Host → Settings → under the HTTP section.
I can’t restore a snapshot on F200?
This will typically occur when the database is has one or more large files over 30MB. If this occurs you can perform the following.
Upgrade to version 5.1.5.154 and higher
Upload the snapshot via a local web browser connection. Don’t use Building X or Edge2Cloud.
Change the HTTPs Timeout Property to 300,000. The HTTPS Timeout property can be found in the Host Settings in the HTTP Section.
If all else fails, contact your local support channel.
How to delete a project on an F200?
...
The Host page will appear and the project will no longer exist. A reboot of the F200 is not required.
Cannot access the WAN Ip Address locally.
If you have configured your F200 for a separate network and your internet connection is on the WAN port, you cannot access the IP address assigned to the WAN port locally. You can only access it through Building X portal.
How to Export Diagnostic Log Files of a FIN instance for troubleshooting purposes
Diagnostic log files can be useful for troubleshooting and may be requested by your support channel.
Connect to the project
Open Folio → Launch
Query for:
logRead(toSpan("today"))
Note: You can switch "today" with other date spans such as yesterday, thisWeek, lastWeek, etc. or use a custom range in this format YYYY-MM-DD..YYYY-MM-DD. A specific day would be YYYY-MM-DD.
For example, to view the diagnostic log information from all of June 2023, enter the following query command: logRead(toSpan(2023-06-01..2023-06-30))
Then toggle from Grid view to Zinc view at the top right of the window.
You can then select everything [Ctrl+A] and copy [Ctrl+C] and paste [Ctrl+V] in a notepad or spreadsheet.
How to fix a locked user on a F200?
If Max Failed Login Attempts is enabled and exceeded, a user may be locked out for the following reasons:
Incorrect password attempts by a colleague or unauthorized user trying to access FIN.
A connector repeatedly attempting to connect with the same username but an incorrect password.
An external instance trying to access FIN with the same username and an incorrect password.
Exceeding the max limit of failed login attempts will disable the user. To prevent regular users from being locked out, it is advisable to create separate users for connectors and external sources. For the F200, registering the devices to Edge2Cloud is highly recommended to avoid a complete lock out.
To resolve a locked-out user on an F200 controller, you can:
If the device is registered to Edge2Cloud, the cloud user can log in and enable and/or create a new user to access the instance.
Perform a "Reset Configuration" in the gateway settings of the device. This action will delete the app data such as the project, users, and gateway settings. After the device reboots, the user must reconfigure the gateway network settings and re-onboard the F200 using Building X.