7.1.2. Administration


Administration interface and TANGO support might not be present in your version of the device. You can update the device firmware using our instruction.


The 8SMC4-USB-Eth adapter has been renamed 8Eth1 [1]. All available instructions in our manual are relevant and applicable to both devices. Network configuration

Connecting the controller via a local network:

  • You must have a DHCP server that supports an automatic distribution of IP addresses. The simple DHCP server that satisfies all requirements can be downloaded here.
  • Server and your computer must support IPv4 protocol.
  • Port 49150 should not be blocked. The cause of blocking can often be the presence of antivirus software, or program which monitors and filters network traffic (firewalls).


The Ethernet controller uses the multicast and UDP requests so make sure that such requests are enabled in your local network. The most common cause for the problem with the Ethernet controller detection is the blocking of such requests by Windows Firewall or managed network equipment.

The Ethernet controller can also be used with the direct connection to the PC with working DHCP-server. The example of configuring the local connection for Windows OS:

  • Download the simple DHCP server.
  • Use the default config file for that server (lines 19 to 31 may be different) or configure the DHCP by yourself.
  • Use revealer to find the given controller’s IP and open it in the web browser.


If necessary, you can use a static IP address. You can download the manual and image with a static IP address here. Automatic device detection

As a convenience we provide a small dedicated utility called “Revealer” in order to help you instantly identify all the Standa 8Eth1 adapters connected to your local network. You can download it from our software page.


“Revealer” utility interface

The Graphical User Interface of the “Revealer” is a simple one. In order to start search click Search button - the scan takes approximately 3 seconds. After that all Standa 8Eth1 devices found in your local network will be listed on Legacy Protocol Devices panel as clickable links. When clicked, the link opens your defaul system browser and redirects it to Administartion interface web page.


“Revealer” uses UDP and SSDP broadcasts. When you click on the Search button, both broadcasts are used. For example:
To search Standa 8Eth1 adapter in your LAN uses UDP broadcasts. To search other devices, such as printers, MFU, network drives, video cameras, etc. uses SSDP broadcasts. You can read more about SSDP here.
It is important to note that “Revealer” might be unusable in the environments where UDP/SSDP broadcasts are forbidden or unwanted. Overview

Standa 8Eth1 and Multi-Axis Motion Controller 8SMC4-ETHERNET/RS232-B19 devices is equipped with web-based Administration interface which enables the end user to control devices services and monitor system state.


Administration interface login page

In order to get access to the Administration panel, navigate your browser to http://[address] URL (where [address] should be replaced with IP address of the device in your local network and can be obtained with the help of “Revealer” utility). If you are doing this for the first time (or you’ve disabled cookies/password storage in your browser) you’ll need to authenticate yourself.


Use “admin” as login and password


It’s highly recommended to enable javascript in your browser while using Administration interface to get the best user experience.


Web-interface is compatable with MS IE 9, MS IE 10, MS IE 11, MS Spartan, Firefox, Chrome browsers and might not work as expected in others.

Administration interface is split into three functional sections. “Common” section


Common section page

This section contains generic system information and decimal serial numbers of all controllers connected to the device. “Motion control” section


Motion control section page

This section is dedicated to motion control services supported by the device. “Motion Control services” panel contains a list of all currently available motion control services. Clicking on services’ title opens an appropriate settings panel (or none if service has no alterable settings). Clicking “Apply” button in settings panel will persist settings in database and restart corresponding service.


Motion control services are mutually exclusive - only one can be active at any given moment. Starting one of the services will automatically stop previous active if any. “Cameras” section


Cameras section page

In this section there is a list of all connected cameras. Each camera is associated with streaming server instance, which exposes settings, status indicators and controls. Service control

The Administration panel enables you to control all available device services. There is a common management metaphor for all services independent of its’ actual functionality and aim. Each service has an associated Indicator button on the left of its title which shows current services’s status and enables changing it:

  • Red color with “Stopped” label indicates that service is completely stopped; pressing the button will run service startup.
  • Orange color with “Starting” label indicates that service is in interruptible start sequence; pressing the button will revert service to stopped state.
  • Green color with “Stop” label shows that the service is up and running; pressing the button will trigger service stop sequence.
  • Orange color with “Stopping” label indicates uninterruptible stop sequence.


Many services have settings which can be altered. After changing any of such settings the corresponding process will be automatically restarted shortly - the Indicator button will show it dynamically. Getting started with XILab

XILab is capable of interacting with remote controllers via Ethernet. However you need an 8SMC5 controller with Ethernet support, or a special XIMC server, which can be either obtained as a standalone program and installed on any appropriate device, or as one of the services of 8Eth1 adapter.

  • If working with 8Eth1, connect controllers to the device with XIMC server. At the same time, it is assumed that the motor can be connected to the controllers and power supply is supplied (see Overview and getting started for more details).
  • Connect the device with XIMC server to the same subnet that contains the control computer, DHCP server. In case of 8Eth1 adapter supply it with power adapter (via 5 V, 2 A connector) and wait for a minute to finish Linux boot on the onboard computer.
  • Launch XILab and make the following.

At first start, XILab opens controller detection window with two virtual devices.


Click Settings, check Enumerate network devices in the right tab and click Rescan button in the left tap, XILab will find all axes connected to the system. XILab will use broadcast request to find available XIMC servers in your LAN.
You can also edit address list manually if desired.


In controller detection window choose an axis you need. You can control it in single-axis mode or in multi-axis mode if more than one axis was chosen. For additional information please refer to Getting started with XILab software and XILab application User’s guide.


Once the device IP address has been found, it should be understood that moving the device to another location may lead to a change in its IP.

Working with multiple adapters may cause a problem when the same board responds in a broadcast requests. You can find a new device by two different ways:

  • Disconnect other 8Eth1 adapters, find the device on the network, connect all again.
  • Press Rescan button until you find sought-for device. Firmware upgrade


During the update MicroSD content and 8Eth1 device flash memory will be wiped out. Make sure that you’ve made necessary backups.

  1. Download an appropriate firmware version from software page.

  2. Get a 4GB (or larger) MicroSD card.

  3. Download and upack an autoinstaller image archive. On Windows family operating system you might have no apropriate archiver — in this case you may use 7-Zip (official site).

  4. Put the image onto the MicroSD card:

    • Unix family OS:

      1. You can do it via dd utility (e.g.

        dd if=autoinstall_image_2015-12-17.bin of=/dev/sdX bs=4M; sync

        but remember to substitute the device names with yours).

    • Windows family OS:

      1. Download Win32 Disk Imager (official site) and start it.
      2. Specify autoinstaller image path in “Image File” field.
      3. Select your MicroSD drive in “Device” list.
      4. Press “Write” button and wait till progressbar completes.
  5. Insert the microSD card with the image into your 8Eth1 and turn it on (or reboot).

  6. Wait approximately 10 minutes to let the firmware be installed. You may check the progress of installation by looking at LED indicator inside the case of the device through USB plugs:

    1. LED is stable green or emits periodic single green pulses - autoinstaller is initializing.
    2. LED periodically emits green double pulses - installation is in progress.
    3. LED is stable green - installation is complete.
  7. Power off the device (just plug the power cable off) and extract MicroSD card.

  8. Power on the device and wait another 2-7 minutes to let the device initialize itself.


On some rare occasions the device might not be visible through the revealer (and have its services and administration interface unavailable either) even well after estimated initialization period. In this case try to reboot the device. If it doesn’t help try to redo steps from 5 to 8.

Now you should have your 8Eth1 device updated and fully operational. Troubleshooting


If your device won’t work properly, leds don’t blink as described above during flashing and your device manufactured after 2017 October, please, contact support. Uninitialized Cubieboard2 bootloader

In some rare cases the steps described in Firmware upgrade instruction might not succeed. One of the possible reasons is that due to some technical failure the Cubieboard2 singleboard computer bootloader (on which 8Eth1 is based on) was not properly initialized. However bootloader initialization isn’t very complicated:

  1. Download PhoenixSuit (official site) and unpack it;
  2. Download Lubuntu server image with bootloader supporting SoC A20 rev. for PhoenixSuit (official site, “Firmwares” -> “Cubieboard2” -> “Lubuntu Server”) and unpack it.
  3. Start PhoenixSuit. In case of update request, confirm it and wait till it’s done.
  4. Switch to “Firmware” tab and specify unpacked Lubuntu server image path.
  5. Power off the device. Press and hold FEL button (it’s near LAN and USB-OTG connectors). While still holding the button, connect USB-OTG to your PC and then release the button.
  6. You might need to explicitly install driver for the device on Windows family OS.
    1. Navigate to the Device Manager.
    2. Locate “Unknown Device” and right click on it.
    3. In the context menu press “Update driver software…”.
  7. Specify “PhoenixSuit1.0.7\PhoenixSuit\Drivers\AW_Driver” as driver search directory.
  8. After that a popup in PhoenixSuite will appear. Press “YES (Full install)” and wait for the completion.
  9. Continue to autoinstall instruction. Other

  • 220V socket should be available.
  • Ethernet cable, USB cable.
[1]The vendor code was changed in 2020, earlier this product had the vendor code 8SMC4-USB-Eth.