OBLAC Drives Installation Guide

System Requirements

  • OBLAC Drives has been successfully tested with the following 64-bit Operating Systems:

    • Windows 7 or newer
    • Ubuntu 16.04 or newer
    • macOS 10.12.6 or newer
  • Intel Core i5 or similar and at least 8GB of RAM

  • VMware Workstation 14 Player (Windows or Linux)

  • VMware Fusion 10 (macOS)

  • (RECOMMENDED) Install Google Chrome (Tested with Version 63.0.3239.132 )

Getting started

  1. Download the latest OBLAC Drives image

Download OBLAC Drives

If you have trouble downloading from Amazon webservice, please try our Baidu server:

Download OBLAC Drives from Baidu

WindowsmacOSLinux
  1. Install and open VMware Workstation Player

Note

ANY version of VMWare Workstation Player starting from 14.0 can be used for OBLAC Drives.

  1. Open a virtual machine
  2. Select the downloaded OBLAC Drives image (OVA file) and import it to VMware Player

Note

If you get a warning that the import failed, just click “Retry” and it will run.

You may also check “Do not show this message again”

  1. Go to Virtual Machine Settings and set the following (if not already set)

    1. Processors

      1. Set the number of processor cores to 2
      2. Check if the “Virtualize Intel VT-x/EPT or AMD-V/RVI” option is set
      ../../_images/Screen_VM_Processor.PNG

      Note

      This feature requires that the Virtualization is enabled in the BIOS. If you get an error message that the machine can’t be started, please restart your PC and enable the Virtualization Technology in the BIOS.

    2. There should be two network adapters available - one set to NAT and one set to bridged

      1. Add them if any of them are missing
      1. NAT
      • Just add a network adapter and select the NAT option
      1. Bridged network adapter

        1. Set it to bridged and check the “Replicate physical network connection state” option

        2. Click on “Configure Adapter”

          1. Select the physical hardware adapter to which the slaves are connected to - THERE SHOULD BE ONLY ONE ADAPTER SELECTED
      1. Press OK to save changes
      ../../_images/OBLAC_Drives_VMware_manual_1.png
  2. Power up and connect the slaves

  3. Play the virtual machine

  1. Install and open VMware Fusion

Note

ANY version of VMWare Fusion starting from 10.0 can be used for OBLAC Drives.

  1. Open the OBLAC Drives image (OVA file) in VMware Fusion

Note

If you get a warning that the import failed, just click “Retry” and it will run.

You may also check “Do not show this message again”

../../_images/OBLAC_Drives_VMware_manual_2.png
  1. Edit the Virtual Machine Settings and set the following (if not already set)

    ../../_images/OBLAC_Drives_VMware_manual_3.png
    • Set the number of processor cores to 2

    • Check the “Enable hypervisor application” option

      ../../_images/OBLAC_Drives_VMware_manual_4.png
    • There should be two network adapters set:

    • “Share with my Mac”

      ../../_images/OBLAC_Drives_VMware_manual_5.png
    • Ethernet adapter

      ../../_images/OBLAC_Drives_VMware_manual_6.png
  2. Power up and connect the slaves

  3. Play the virtual machine

  1. Install and open VMware Workstation Player

Note

ANY version of VMWare Workstation Player starting from 14.0 can be used for OBLAC Drives.

  1. Open a virtual machine
  2. Select the downloaded OBLAC Drives image (OVA file) and import it to VMware Player

Note

If you get a warning that the import failed, just click “Retry” and it will run.

You may also check “Do not show this message again”

  1. Edit the Virtual Machine Settings and set the following (if not already set)

    1. Processors

      1. Set the number of processor cores to 2
      2. Check the “Virtualize Intel VT-x/EPT or AMD-V/RVI” option
      ../../_images/ubuntu-virtualization.png
    2. There should be two network adapters set - NAT and bridged, add them if any of them are missing

      1. NAT (Just add a network adapter and select the NAT option)
      2. Bridged network adapter (Set it to bridged and check the “Replicate physical network connection state” option)
      ../../_images/OBLAC_Drives_VMware_manual_7.png
  2. Network settings

    1. Execute
    sudo /usr/lib/vmware/bin/vmware-netcfg
    
    1. Select the bridged network adapter and bridge it to the system network adapter to which the slaves are connected to

      1. The network adapter has to be an Ethernet connection, so it likely starts with “eth”
    2. Save changes

    ../../_images/OBLAC_Drives_VMware_manual_8.png
  3. Power up and connect the slaves

  4. Play the virtual machine

  5. In case your systems hints that a swap partition is needed:

    ../../_images/swap_needed.png
    instead of creating such a partition you can also use this workaround:
    • Close the VMware Player

    • Run
      sudo gedit /etc/vmware/config
      
    • Add
      prefvmx.minVmMemPct = "100"
      

      at the end of the file and save

    • Restart the VMware Player

Connecting to OBLAC Drives

Once your virtual machine is powered up, you will find the IP address of OBLAC Drives at the top of the screen.
Enter this IP address in your browser and wait for OBLAC Drives to show the connected drives.
../../_images/browser.png

Please check in you browser that the Drive is connected:

../../_images/no_firmware1.png

Now you are ready to use the features of OBLAC Drives!

NEXT STEP: Proceed to Commissioning Guide.

Shutting down the Virtual Machine

Please note that after using OBLAC Drives it is necessary to shut down the Virtual Machine, otherwise your local network might get flooded with EtherCAT commands.
To shut down the VM please use the VMware shutdown button.

Troubleshooting

  1. Always give OBLAC Drives up to a minute to detect the available Drives after they have been powered on or connected
  2. If the Drives aren’t found, or anything else seems to be wrong, please try refreshing the web page first and then power cycling the drive(s)
  3. If you are running Windows, please ensure that the power-saving functionality for LAN is turned OFF
../../_images/win-power-save.png

There are more issues listed in our Troubleshooting Guide.