Skip to main content

Licenses

A summary of which terms apply to what. This page is guidance; for interpreting the agreement, the agreement you signed prevails.

WhatTerms that applySection
PLEM software (except the packages in the drive layer section)The PLEM license agreement you signed and the license issued to the devicePLEM software
Drive layer plem-drive and plem-cli (the /usr/bin/plem command)Apache License 2.0Drive layer
Third-party open source components distributed with PLEMEach component's own licenseThird-party open source notices
ROS 2 and Ubuntu packages that apt installs from upstream repositoriesEach package's own licenseDependencies installed by the package manager
frpc for remote supportApache-2.0 (Go modules linked into it keep their own licenses)Dependencies installed by the package manager
Camera SDK (ZED SDK), NVIDIA Isaac ROS, cuMotionTerms set between each vendor and the customerVendor software installed separately

PLEM software​

PLEM is proprietary software copyrighted by WIM Inc. It is not open source and is supplied under a separate license agreement. The exception is the "Drive layer" section below.

The scope and term of the license are set by that agreement and by the license issued to the device. The license is issued bound to a device and works only on the device it was issued for. Unless the agreement expressly permits it, copying, redistribution, rental, sale, sublicensing and reverse engineering are not allowed.

The copyright notice and a license summary are on the installed device. The full agreement is the license agreement you signed, not this file.

cat /usr/share/doc/plem-core/copyright

Drive layer (Apache License 2.0)​

WIM Inc. provides the drive layer package plem-drive under the Apache License 2.0. This covers the five drive layer packages (plem_core, plem_fieldbus, plem_drive, plem_drive_msgs, plem_rt_msgs) and the files the package installs (the /usr/bin/plem-drive launcher, /etc/profile.d/plem.sh, /etc/security/limits.d/99-plem-realtime.conf and the install scripts). The Apache License 2.0 applies to them, not the PLEM license agreement. plem-cli (the /usr/bin/plem command), which plem-drive installs with it, is also under the Apache License 2.0 (/usr/share/doc/plem-cli/). The copyright and license summary is in /usr/share/doc/plem-drive/copyright, and the attribution notice is in /usr/share/doc/plem-drive/NOTICE.

Data collection​

The drive layer is not covered by the license agreement. Its setup wizard asks once whether to share device data with WIM, and nothing is sent unless you answer Yes. What is sent and how it is kept is in docs/telemetry.md of the public repository. The rest of this section applies to the PLEM software under the license agreement.

Article 10 of the license agreement sets the scope of information the company may collect. The items actually collected, the purposes of use and the retention periods are set by the agreement's Schedule (collected items). The full agreement is on the installed device at /usr/share/doc/plem-core/PLEM-SOFTWARE-LICENSE-ko.md; its Korean text is the authoritative version (Article 19). When the collected items change, we announce it in the release notes or by another usual means.

Collection under item 6 of the Schedule (robot operation records) can be turned off by adding the following to ~/.plem/settings.yaml on the device. It takes effect the next time the robot stack launches, and at that point any records still on the device that were not yet sent are deleted.

telemetry:
enabled: false

plem code (beta) conversations are not used to retrain models and are deleted after the retention period set in the Schedule (backup copies expire with the backup cycle). Do not paste credentials or personal information into a conversation.

Third-party open source notices​

PLEM is distributed with open source components. Each component keeps its own license terms, and those terms take precedence over the PLEM license agreement (Article 8).

The list and the license texts are installed on the device with each package.

ContentsFile on the device
Copyright summary per package (Debian machine-readable format)/usr/share/doc/<package>/copyright
Third-party license texts/usr/share/doc/<package>/THIRD-PARTY-NOTICES

Both files are generated from the build output for every release. A component whose license text could not be included is listed with its declared license only, and the file says so.

Dependencies installed by the package manager​

The ROS 2 and Ubuntu packages that PLEM packages depend on are not contained in the PLEM packages. apt installs them from their upstream repositories (packages.ros.org and the Ubuntu archive), so they are not in the THIRD-PARTY-NOTICES above, and each package follows its own license terms. For example, PlotJuggler is a recommended package of plem-drive, so it is installed by default during install and update when the ROS apt repository is reachable. Its licenses are:

  • plotjuggler: MPL-2.0
  • plotjuggler-ros: AGPL-3.0

License information is in each package's copyright file (for example /usr/share/doc/ros-$ROS_DISTRO-plotjuggler-ros/copyright) and in the upstream repository. The copyright file of a ROS 2 package often gives only the license name and points to the upstream repository for the full text.

frpc, used for remote support, is the upstream frp release packaged separately by WIM and provided from the PLEM package repository. The copyright holder and the full Apache-2.0 text are in /usr/share/doc/frpc/copyright. The Go modules linked into that binary follow their own licenses, which you can check in their upstream repositories.

Source code offer​

Devices on which WIM installed and delivered the software also have open source components installed whose licenses require source code to be made available, such as GPL, LGPL and AGPL. On request from anyone, WIM provides the corresponding source code of those components, for a fee no more than the cost of providing it, for three years from the device's delivery date or for as long as WIM provides support for that device model, whichever is longer. Send requests to the address under "Contact" below.

Native code in Python wheels​

Notices for the third-party code in the native library of the Python package coacd, used by plem-server, are in /usr/share/doc/plem-server/BUNDLED-NATIVE-NOTICES. coacd is WIM's modified build of CoACD (MIT), with the Sobol generator replaced by WIM's own implementation.

Use of LGPL libraries​

Some PLEM libraries dynamically link IgH EtherCAT libethercat (LGPL-2.1) and Orocos KDL (LGPL-2.1 or later). The LGPL-2.1 text is in /usr/share/common-licenses/LGPL-2.1.

Vendor software installed separately​

PLEM does not redistribute the camera SDK (Stereolabs ZED SDK) or the NVIDIA Isaac ROS and cuMotion components. The install scripts download them directly from each vendor's distribution channel, and the terms of use for that software are set between each vendor and the customer.

Contact​

Send questions about license terms, purchasing and the scope of the agreement to william@wimcorp.co.kr.