8.1. No device found / Can’t open device

8.1.1. Connect via USB

XiLab or other software can not find the controller.

  • The PC does not detect the controller via USB:
../../_images/HW.png

Comment to the scheme:

The most common cause for such type of problem is bad work of the usb-hub, cables or the virtual COM-port identification problem of the operation system on the used PC. Try to reproduce the problem on the another PC or another usb-hub if it is used.

Warning

“Can’t open device” error or “open_device()” function returns -1. Libximc library opens the controller in exclusive access mode. Any controller opened with libximc (XiLab also uses this library) needs to be closed before it may be used by another process. So at first check that you have closed XiLab or other software dealing with the controller before trying to reopen the controller.

Below are the action maps for the not found controller.

Windows:

../../_images/Win.png

Comments to the scheme:

  • Check whether the COM-port corresponding to your controller presents in the Device manager. It should be displayed as “XIMC Motor Controller (COMn)”. In case the controller has not been recognized, try to reinstall the driver for the controller manually.
  • Try to open the COM-port of the controller in any simple serial emulator (Putty for example) and just send the simple command to the controller (like “stop”, “sstp”, “zero”, “GETS”, “GETI”). The connection parameters are described here. The absence of errors means that the controller is operating correctly and the problem should be caused by the used software.

Video guide for reinstalling the driver

Linux:

../../_images/direct_usb_connection.png
../../_images/network_adapter.png
../../_images/to_usb_adapter.png

Comment to “Can’t open device” problem solution:

When working with USB-UART converter (as well as USB-Ethernet, USB-Bluetooth etc.) in Linux it appears as /dev/ttyUSB device. XiLab shows it in a list, but when you try to open it, an error “can’t open device” occurs due to the lack of permissions to the device.

To solve this problem, create a file: /etc/udev/rules.d/31-ximc.rules and add the next line into it:

SUBSYSTEM=="usb", ATTR{idVendor}=="067b", MODE="0666"

idVendor identifier can be found by executing lsusb command.

Note

One possible solution to the “device not found” problem is to add a user to the dialuot group. Important: after adding it, you must restart your computer.

Mac OS:

../../_images/Mac.png

8.1.2. Connect via ETHERNET

8.1.2.1. If the 8Eth1 adapter is not found on the local network

Note

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

../../_images/not_found_eth(revealer).png

Disable “Windows Defender Firewall” and click the “Search/Restart” button in “Revealer” program. 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 using “admin” as login and password.

If the control panel opens, your 8Eth1 adapter works fine. After that, don’t forget enable firewall.

8.1.2.2. The controller serial number is not displayed on the “Common” tab

../../_images/not_found_serial_numbers.png
  • Reboot your controller and 8Eth1 adapter
  • Connect the controller to your computer via USB and make sure it works correctly.
    We recommend using xilab for verification
  • Try to reproduce the problem on another computer

Note

Send your questions with a detailed description of the problem to tech support:

[1]The vendor code was changed in 2020, earlier this product had the vendor code 8SMC4-USB-Eth.