Manual Install Of PolySync

To manually install PolySync, a tarball (tar.gz) release package─as opposed to the binary (.bin) release installer─will be necessary. Please contact support for access to the tarball package. ### 1. Remove previous installation It's important that any previous version of PolySync is removed before continuing. This will prevent data model collisions within libraries and header files. If desired, create a backup of the existing install and remove the existing instance of `PSYNC_HOME`: ```bash $ echo $PSYNC_HOME /usr/local/polysync $ tar cfz /opt/polysync-backup-xx-xxx.tar.gz /usr/local/polysync $ rm -rf /usr/local/polysync ``` ### 2. Download and extract the archive After obtaining a PolySync release package, extract the archive: ```bash $ cd ~/Downloads/ $ tar xf polysync-release-2.0.0-x86_64.tar.gz ``` Move the PolySync directory to the desired location. The default location is **/usr/local**. If this is the first installation, please export the `PSYNC_HOME` environment variable: ```bash $ mv polysync/ /usr/local $ export PSYNC_HOME=/usr/local/polysync ``` ### 3. Install dependencies You will need to install dependencies before PolySync can be configured and run properly. ```bash $ cd $PSYNC_HOME $ sudo ./utils/ ``` The full list of PolySync dependencies can be found in the **polysync/README.txt** file. ### 4. Configuration The following steps are performed by the `` script: * Update shared library files with PolySync includes and libraries for developing and running PolySync applications * Append the PolySync environment script to the global bashrc file to place binaries within the shell's path * Update udev rules specifically for the Xsens MTi-G USB interface * Change permissions for the PolySync home directory (/usr/local/polysync/) * Install Kvaser linuxcan drivers for current kernel to enable CAN communication with USB and PCI hardware * Install Flycapture package required for PointGrey GigE cameras * Set up PolySync Studio and SDF Configurator Ubuntu Icons for application quick start Start the script by passing in two arguments: * Installation directory * This must match **PSYNC_HOME** from the step above * Username * Must provide the username for the account that will access the PolySync directory and run PolySync applications * It is not recommended to use **root** as the PolySync user ```bash $ cd $PSYNC_HOME/ $ sudo ./utils/ $PSYNC_HOME dev ``` An absolute path can also be provided: ```bash $ cd /usr/local/polysync ; sudo ./utils/ /usr/local/polysync dev ``` It is necessary to close and reopen the terminal before starting PolySync applications. This acts to ensure the environment has been sourced. Alternatively, the environment can be manually sourced: ```bash $ source $PSYNC_HOME/utils/ ``` ### 5. Retrieve an existing license After performing an upgrade, the license will need to be re-downloaded from the server. Use the following to call the license tool to retrieve an existing license: ```bash $ polysync-license-tool -a ``` To check to see if a license is valid, use the following: ```bash $ polysync-license-tool ``` ### 6. PolySync IP address Lastly, you will need to set the PolySync IP address. All nodes will publish and subscribe data to this location. ```bash $ polysync-manager -s ``` On a single host system, the developer can use the IP address: ``. Start the SDF Configurator to ensure that the network is properly set up. ### Conclusion Congratulations! You have now successfully manually installed PolySync software.