Detailed reason of error message "invalid robot type"

edit

Hello all, Using ros-indigo-denso (vs-060), I want to move denso robot VS-068. After I started to launch ros-package "denso_robot_bringup", error message "invalid robot type" appeared. My question is , what does "invalid robot type" message mean? Lack of robot-configuraion file? I want to know the detailed reasons and/or conditions of the error.

Searching the description "Invalid robot type" in my computer directory, I was able to find "denso_robot_control" binary file in /opt/ros/indigo/lib/denso_robot_control/ directory. Part of binary file is shown below.

Computer environment is shown on below

Ubuntu 14.04 LTS
ROS package: ROS-indigo-denso

Part of binary file is shown on below:

(...)
/usr/include/boost/exception/detail/exception_ptr.hpp
boost::exception_ptr boost::exception_detail::get_static_exception_object() [with Exception = boost::exception_detail::bad_exception_]
boost::exception_ptr boost::exception_detail::get_static_exception_object() [with Exception = boost::exception_detail::bad_alloc_]
N5boost9exceptionE
N5boost16exception_detail10clone_baseE
N5boost6detail15sp_counted_baseE
N5boost6system12system_errorE
N5boost16exception_detail10bad_alloc_E
N5boost16exception_detail14bad_exception_E
N5boost16exception_detail10clone_implINS0_10bad_alloc_EEE
N5boost16exception_detail10clone_implINS0_14bad_exception_EEE
N5boost6detail17sp_counted_impl_pINS_16exception_detail10clone_implINS2_10bad_alloc_EEEEE
N5boost6detail17sp_counted_impl_pINS_16exception_detail10clone_implINS2_14bad_exception_EEEEE
@call to empty boost::function
Cannot create handle '
ros.denso_robot_control
@TYPE_NAME
vector::_M_fill_insert
std_msgs/Int32
int32 data
' in '
denso_robot_core/UserIO
Write_HandIO
Write_MiniIO
Write_SendUserIO
Read_HandIO
Read_Current
std_msgs/Float64MultiArray
Read_MiniIO
Write_RecvUserIO
Read_RecvUserIO
Change to mode %d.
Failed to change mode. (%X)
Failed to write. (%X)
robot_name
robot_joints
arm_group
joint_
It was assumed revolute type.
Could not find resource '
Use arm group 0.
send_format
recv_format

Invalid robot type.

@ERROR_CODE
Failed to clear error. (%X)
@SERVO_ON
Failed to motor on. (%X)
ChangeMode
CurMode
'. Position data pointer is null.
'. Velocity data pointer is null.
'. Effort data pointer is null.
boost unique_lock has no mutex
boost unique_lock owns already the mutex
boost: mutex lock failed in pthread_mutex_lock
boost: mutex unlock failed in pthread_mutex_unlock
(...)