-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ACTION REQUIRED: Important update with version 0.6.0 or higher (March, 2015) #153
Comments
I cannot find /opt/jsk/etc/HIRONX/modes/main.wrl . Which package does include this file? ii ros-hydro-nextage-description 0.6.1-0precise-20150310-0207-+0000 ii ros-hydro-hironx-calibration 1.0.28-0precise-20150206-2221-+0000 |
OK, /opt/jsk/etc/HIRONX/models/main.wrl sould be the file in the QNX controller. omniORB: ERROR -- the application attempted to invoke an operation |
Thanks for clarification, and yes that's correct. I've updated my original post to clarify this.
Are you still able to operate the robot as intended despite the errors? Also, could you run the following script, and send back the resulted tarball to support[a-t]opensource-robotics.tokyo.jp? This script shouldn't be harmful to any corporate network (please take a look at the code in the URL if necessary). |
I'm very sorry that there was a critical mistake.
|
Sorry for late response. I have e-mailed diagnosis file which previously you asked.
|
Sorry for inconvenience, It seems we have bugs need to be fixed, please try this
to obrain
you can revert these patches (either intentionally or accidentally)
-- your friendly neighborhood TORK dev team |
Some warnings and errors (red text in console) remains, but are'nt they critical?
First warnings:
Second fail:
Third fails:
Forth fail is:
|
Warnings and errors are expected and critical for robots have force sensors, but if you does not have one, it is ok. |
Yes, it's working fine. Thank you for your effort. |
Closing since no major dispute has been heard for awhile. Thank you for the attention and feedback (esp. @longjie). |
why we have to change this? why we did not set default MODEL_FILE values? |
This is an important message for the NEXTAGE OPEN users (ie. Hironx users are NOT affected).
With the upcoming latest version of the software packages, you'll be required to take an action to apply the following changes.
If you are NOT planning to update the software by either one of the following commands, you can stop reading at this point:
apt-get
command of Ubuntugit pull
or equivalent commands if you're using the source code version of NEXTAGE OPEN packagesIf you have any questions regarding this, please contact us by either one of the followings:
Users affected
Affected users are those who fit into BOTH of these two conditions:
nextage_ros_bridge
0.6.0 or highernextage_moveit_config
0.6.0 or higherModifications required
Modification-a. Command to run ROS server on your Ubuntu machine needs an extra argument.
roslaunch nextage_ros_bridge nextage_ros_bridge_real.launch
roslaunch nextage_ros_bridge nextage_ros_bridge_real.launch MODEL_FILE:=/opt/jsk/etc/HIRONX/model/main.wrl
With
MODEL
argument, you're telling the location of 3D model file *inside * of ControllerBox/QNX (so that it's ok that the path you're passing doesn't exist on you Ubuntu machine). Note that you should keep usingHIRONX
for your NEXTAGE robot in this particular command.Modification-b. If your application uses any of the following method from
NextageClient
class in Python (which is introduced as "robot
" varibale onipython
console in the tutorials), make sure you add an argumentframe_name=None
.Example:
z
values differ.The affecting changes were primarilly made in order to compensate the different height between robots (in their model files,
Hiro
has no base whileNEXTAGE
has) so that uses who have both types of robots couldn't use same code for different robots. Actually these changes provide more solid API in general for Hiro and NEXTAGE, so we hope all users benefit from this. We appreciate any feedback from you.Isaac from your friendly neighbourhood TORK dev team
EDIT (3/26/2015): Purpose of this change is to ultimately enhance the usability and stability of the software, by eliminating rather robot-specific portion of codes and applying more common usage. We appreciate your understanding.
The text was updated successfully, but these errors were encountered: