I’m having some strange behavior when trying to run URSim 3.6.1 when installing on a fresh install on 64 Bit Ubuntu 18.04.1: after a number of workarounds, I was finally able to install and start URSim, but there is some weird mismatch between the robot model selected (either by doubleclickign the URX file on desktop, or running bash start-ursim.sh UR10
), where the UR10 file opens a model that looks like the UR3, but with incorrect parameters such that joints are either floating in space far from one another, or overlapped over one another. My guess is that somehow it has a mismatch of settings and models from one robot vs. another. Has anyone faced this issue, and is there a simple solution?
Here’s what I’ve done so far, which can be summarized as my blindly fumbling around for a day and a half :
-Tried installing as described on the download page. Installed Java 8 after getting an error with Java 10, but then got URControl: no process found
. Tried installing older versions of URSim with similar problems.
-Realized URControl is 32 bit and I’m on a 64 bit system. Installed i386 architecture, and tried installing URSim again.
-Still same problem. When running ldd URControl
I get that most xmlrpc files aren’t found. Installed those again using sudo apt-get install libxmlrpc-c++8-dev:i386
(updated to libc6 in the process). ldd URControl
now finds all libraries.
-Running bash start-ursim
now open URSim, but I get an error “could not save file ‘default’: Ensure the selected save directory exists”
-When opening a specific robot model, I get “Polyscope: C203A0: Polyscope detected a mismatch between the shown and to be applied safety parameters”, and get the messed up robot model when restarting.
-Having experienced similar symptoms to Samuel.Paxton, I tried those fixes (including deleting the urtool3.0 directory) but still get the same strange behavior.
-When I run `bash start-ursim.sh’, a UR5 system starts that looks correct, but I still get the “could not save file ‘default’” error. Mostly it seems fine though, except the terminal printing:
** (java:22269): WARNING **: 16:23:06.368: jaw_impl_get_instance called from jaw_thread. If you are running a screen reader, this is expected
If you are not running a screen reader, please report this warning to the java-atk-wrapper package, explaining how to reproduce this warning
-Running the UR10/UR3 specifically gives me the fault and strange mismatch of model and parameters (UR10 looks like a funky UR3, and UR3 looks like a funky UR10).
-Running install.sh prints the following:
> Checking java version
> /usr/bin/java
> version 1.8.0_171
> java version accepted
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Note, selecting 'libjava3d-jni' for glob 'libjava3d-*'
> Note, selecting 'libjava3d-java-doc' for glob 'libjava3d-*'
> Note, selecting 'libjava3d-java' for glob 'libjava3d-*'
> Note, selecting 'ttf-dejavu-core' for glob 'ttf-dejavu*'
> Note, selecting 'ttf-dejavu-extra' for glob 'ttf-dejavu*'
> Note, selecting 'ttf-dejavu' for glob 'ttf-dejavu*'
> fonts-arphic-ukai is already the newest version (0.2.20080216.2-4ubuntu2).
> fonts-arphic-uming is already the newest version (0.2.20080216.2-7ubuntu3).
> lib32gcc1 is already the newest version (1:8-20180414-1ubuntu2).
> lib32stdc++6 is already the newest version (8-20180414-1ubuntu2).
> libc6-i386 is already the newest version (2.27-3ubuntu1).
> fonts-baekmuk is already the newest version (2.2-12).
> fonts-ipafont is already the newest version (00303-18ubuntu1).
> fonts-nanum is already the newest version (20170925-1).
> libjava3d-java is already the newest version (1.5.2+dfsg-14).
> libjava3d-java-doc is already the newest version (1.5.2+dfsg-14).
> libjava3d-jni is already the newest version (1.5.2+dfsg-14).
> ttf-dejavu is already the newest version (2.37-1).
> ttf-dejavu-core is already the newest version (2.37-1).
> ttf-dejavu-extra is already the newest version (2.37-1).
> The following packages were automatically installed and are no longer required:
> libasn1-8-heimdal:i386 libffi6:i386 libgmp10:i386 libgnutls30:i386
> libgssapi-krb5-2:i386 libgssapi3-heimdal:i386 libhcrypto4-heimdal:i386
> libheimbase1-heimdal:i386 libheimntlm0-heimdal:i386 libhogweed4:i386
> libhx509-5-heimdal:i386 libidn2-0:i386 libk5crypto3:i386 libkeyutils1:i386
> libkrb5-26-heimdal:i386 libkrb5-3:i386 libkrb5support0:i386
> libldap-2.4-2:i386 libnettle6:i386 libnghttp2-14:i386 libp11-kit0:i386
> libpsl5:i386 libroken18-heimdal:i386 librtmp1:i386 libsasl2-2:i386
> libsasl2-modules:i386 libsasl2-modules-db:i386 libsqlite3-0:i386
> libssl1.1:i386 libtasn1-6:i386 libunistring2:i386 libwind0-heimdal:i386
> Use 'apt autoremove' to remove them.
> The following packages will be REMOVED:
> libcurl4:i386 libxmlrpc-c++8-dev:i386 libxmlrpc-c++8v5:i386
> libxmlrpc-core-c3:i386 libxmlrpc-core-c3-dev:i386
> The following NEW packages will be installed:
> libcurl3
> 0 upgraded, 1 newly installed, 5 to remove and 0 not upgraded.
> Need to get 0 B/214 kB of archives.
> After this operation, 2,723 kB disk space will be freed.
> (Reading database ... 158420 files and directories currently installed.)
> Removing libxmlrpc-c++8-dev:i386 (1.33.14-8build1) ...
> Removing libxmlrpc-c++8v5:i386 (1.33.14-8build1) ...
> Removing libxmlrpc-core-c3-dev:i386 (1.33.14-8build1) ...
> Removing libxmlrpc-core-c3:i386 (1.33.14-8build1) ...
> Removing libcurl4:i386 (7.58.0-2ubuntu3.2) ...
> Selecting previously unselected package libcurl3:amd64.
> (Reading database ... 158253 files and directories currently installed.)
> Preparing to unpack .../libcurl3_7.58.0-2ubuntu2_amd64.deb ...
> Unpacking libcurl3:amd64 (7.58.0-2ubuntu2) ...
> Setting up libcurl3:amd64 (7.58.0-2ubuntu2) ...
> Processing triggers for libc-bin (2.27-3ubuntu1) ...
> (Reading database ... 158260 files and directories currently installed.)
> Preparing to unpack .../curl-dev-ur_7.18.2-1_amd64.deb ...
> Unpacking curl-dev-ur (7.18.2-1) over (7.18.2-1) ...
> Preparing to unpack .../libxmlrpc-c-dev-ur_1.33.14_amd64.deb ...
> Unpacking libxmlrpc-c-dev-ur (1.33.14) over (1.33.14) ...
> Preparing to unpack .../libxmlrpc-c-ur_1.33.14_amd64.deb ...
> Unpacking libxmlrpc-c-ur (1.33.14) over (1.33.14) ...
> Setting up curl-dev-ur (7.18.2-1) ...
> Setting up libxmlrpc-c-ur (1.33.14) ...
> Setting up libxmlrpc-c-dev-ur (1.33.14) ...
> Processing triggers for libc-bin (2.27-3ubuntu1) ...
> Install Daemon Manager
> Installing daemon manager package
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> runit is already the newest version (2.1.2-9.2ubuntu1).
> The following packages were automatically installed and are no longer required:
> libasn1-8-heimdal:i386 libffi6:i386 libgmp10:i386 libgnutls30:i386
> libgssapi-krb5-2:i386 libgssapi3-heimdal:i386 libhcrypto4-heimdal:i386
> libheimbase1-heimdal:i386 libheimntlm0-heimdal:i386 libhogweed4:i386
> libhx509-5-heimdal:i386 libidn2-0:i386 libk5crypto3:i386 libkeyutils1:i386
> libkrb5-26-heimdal:i386 libkrb5-3:i386 libkrb5support0:i386
> libldap-2.4-2:i386 libnettle6:i386 libnghttp2-14:i386 libp11-kit0:i386
> libpsl5:i386 libroken18-heimdal:i386 librtmp1:i386 libsasl2-2:i386
> libsasl2-modules:i386 libsasl2-modules-db:i386 libsqlite3-0:i386
> libssl1.1:i386 libtasn1-6:i386 libunistring2:i386 libwind0-heimdal:i386
> Use 'sudo apt autoremove' to remove them.
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Creating user daemon service directory
> Starting user daemon service
Any pointers would be very much appreciated, as I’m really starting to run in circles here…
Cheers,
Ryan