Skip to main content
Version: 4.11.0

Fuzzy RTOS web dashboard

From version 3.6 onwards, Fuzzy RTOS is packaged with cockpit, a web dashboard that can be used to manage system settings as well as perform various connection tests.

The administration page can be found at https://address-of-the-ipc:9090.

The WAN interface is configured as a DHCP client by default. If your setup requires a static IP address (to integrate it with already configured devices for instance), it is possible to set it up in the dashboard.

tip

If you don't have a router or DHCP server available, there are software options available, like http://www.dhcpserver.de/cms/download/. See this page for a tutorial.

Login

Untitled

The user name is “root” and the default password is “FuzzyLogic!”.

Connection and configuration of Fuzzy RTOS

On the left side bar, select the Fuzzy RTOS tab to access Fuzzy RTOS configuration and controls. This section can be useful to manage licensing and system configuration or troubleshoot connection issues. Among the different tabs, you can notably find:

  • The Manager tab which allows you to manually load and unload drivers by selecting the robot and controller models, as well as manage licensing.
  • The Jogger tab allows you to enable jogging mode to test out proper connection
  • You can check for proper connection with the robot controller by pinging it in the Tools tab.

fuzzy_rtos_dashboard

Network settings

Under the Networking tab, you should see two interfaces:

  • enp6s0: Real-time link to the robot controller
  • enp7s0: WAN

The WAN interface is configured as a DHCP client by default but you can change this behavior by clicking on the interface name:

networking_enp7s0

You can then click on edit next to IPv4 or IPv6.

To specify a static IPv4 config, choose Manual IP setting instead of Automatic and then enter the IP adress you wish to use. Your settings should look similar to this:

IPv4_settings

Finally, click on Apply

note
  • Make sure the laptop communicating with the configured Fuzzy RTOS also has an IP address in the same subnet
  • Be careful to not specify the same subnet as the RT interface (connected to the robot controller) unless you also specify custom routes.