Aust's profile - activity

overview network karma followed questions activity

2020-07-23 04:34:29 -0500	received badge	● Famous Question (source)
2020-05-20 08:26:16 -0500	received badge	● Famous Question (source)
2019-12-16 13:36:55 -0500	received badge	● Notable Question (source)
2019-12-16 08:25:22 -0500	received badge	● Supporter (source)
2019-12-16 08:25:22 -0500	marked best answer	hector_slam Install Question Sorry for asking a simple question but I am new to using ROS and Linux and want to make sure that I install the package correctly to use. I am wanting to install hector_slam to use with a Tim 561 LiDAR, I already have ROS and sick_scan installed and working to be able to visualize the LiDAR data. After reading through the hector_slam documentation I found a line to use for installing the package shown bellow. sudo apt-get install ros-indigo-hector-slam When using this to install the package do I need to be within a specific working directory like the catkin work space I have made for my project? Also I have Kinetic not indigo so I should replace that with the word kinetic to install the correct version right?
2019-12-16 07:06:53 -0500	received badge	● Notable Question (source)
2019-12-16 05:40:36 -0500	received badge	● Popular Question (source)
2019-12-15 09:33:23 -0500	asked a question	hector_slam Install Question hector_slam Install Question Sorry for asking a simple question but I am new to using ROS and Linux and want to make sur
2019-12-15 09:32:06 -0500	asked a question	hector_slam Install Question hector_slam Install Question Sorry for asking a simple question but I am new to using ROS and Linux and want to make sur
2019-12-12 13:38:16 -0500	marked best answer	sick_scan Launch error I am new to using ROS and am trying to use a Tim561 lidar with sick_scan. When I run the command below I obtain the following output error. roslaunch sick_scan sick_tim_5xx.launch ... logging to /home/austin/.ros/log/8adb6048-1c48-11ea-a1ae-b94bf9e35c82/roslaunch-austin-Precision-5520-5563.log Checking log directory for disk usage. This may take awhile. Press Ctrl-C to interrupt Done checking log file disk usage. Usage is <1GB. started roslaunch server http://austin-Precision-5520:46695/ SUMMARY ======== PARAMETERS * /rosdistro: kinetic * /rosversion: 1.12.14 * /sick_tim_5xx/cloud_topic: cloud * /sick_tim_5xx/frame_id: cloud * /sick_tim_5xx/hostname: 169.254.172.71 * /sick_tim_5xx/intensity: True * /sick_tim_5xx/max_ang: 2.35619449 * /sick_tim_5xx/min_ang: -2.35619449 * /sick_tim_5xx/port: 2112 * /sick_tim_5xx/range_max: 100.0 * /sick_tim_5xx/scanner_type: sick_tim_5xx * /sick_tim_5xx/timelimit: 5 * /sick_tim_5xx/use_binary_protocol: True NODES / sick_tim_5xx (sick_scan/sick_generic_caller) ROS_MASTER_URI=http://localhost:11311 process[sick_tim_5xx-1]: started with pid [5580] [ INFO] [1576090913.600026808]: sick_generic_caller V. 001.003.020 [ INFO] [1576090913.600070064]: Program arguments: /home/austin/ros_catkin_ws/devel/lib/sick_scan/sick_generic_caller [ INFO] [1576090913.600079721]: Program arguments: __name:=sick_tim_5xx [ INFO] [1576090913.600104200]: Program arguments: __log:=/home/austin/.ros/log/8adb6048-1c48-11ea-a1ae-b94bf9e35c82/sick_tim_5xx-1.log [ INFO] [1576090913.608229162]: Found sopas_protocol_type param overwriting default protocol: [ INFO] [1576090913.608254610]: Binary protocol activated [ INFO] [1576090913.608266937]: Start initialising scanner [Ip: 169.254.172.71] [Port: 2112] [ INFO] [1576090913.634351789]: Publishing laserscan-pointcloud2 to cloud 1576090913.6374 ERROR: Tcp::open: Failed to open TCP connection to 169.254.172.71, aborting. [ INFO] [1576090913.639255645]: Parameter setting for <active_echo: 0> [ INFO] [1576090913.839928764]: Sending : <STX><STX><STX><STX><Len=0023>sMN SetAccessMode 0x03 0xf4 0x72 0x47 0x44 CRC:<0xb3> 1576090913.8401 Warning: Tcp::write: Failed to send data to socket. [ERROR] [1576090919.908813399]: no answer received after 5000 ms. Maybe sopas mode is wrong. [ INFO] [1576090919.908940549]: sendSOPASCommand: no full reply available for read after 5000 ms [ INFO] [1576090919.909188489]: Receiving: <STX><ETX> [ INFO] [1576090919.909267448]: SOPAS Communication -Error unexpected Sopas Answer for request <STX><STX><STX><STX><Len=0023>sMN SetAccessMode 0x03 0xf4 0x72 0x47 0x44 CRC:<0xb3> [ INFO] [1576090919.909547112]: Sending : <STX>sMN SetAccessMode 3 F4724744<ETX> 1576090919.9096 Warning: Tcp::write: Failed to send data to socket. [ERROR] [1576090926.000694232]: no answer received after 5000 ms. Maybe sopas mode is wrong. [ INFO] [1576090926.000826998]: sendSOPASCommand: no full reply available for read after 5000 ms [ INFO] [1576090926.001042284]: Receiving: <STX><ETX> [ INFO] [1576090926.001114041]: SOPAS Communication -Error unexpected Sopas Answer for request <STX>sMN SetAccessMode 3 F4724744<ETX> [ERROR] [1576090926.001280456]: Error Access Mode [ INFO] [1576090926.201903159]: Sending : <STX>sWN EIHstCola 1<ETX> 1576090926.2020 Warning: Tcp::write: Failed to send data to socket. [ERROR] [1576090932.263198941]: no answer received after 5000 ms. Maybe sopas mode is wrong. [ INFO] [1576090932.263299494]: sendSOPASCommand: no full reply available for read after 5000 ms [ INFO] [1576090932.263501296]: Receiving: <STX><ETX> [ INFO] [1576090932.263565671]: SOPAS Communication -Error unexpected Sopas Answer for request <STX>sWN EIHstCola 1<ETX> [ERROR] [1576090932.263724024]: Command or Error message not defined [ INFO] [1576090932.263905386]: Failed to init scanner Error Code: 1 Waiting for timeout... If the communication mode set in the scanner memory is different from that used by the driver, the scanner's communication mode is changed. This requires a restart of the TCP-IP connection, which can ... (more)
2019-12-12 13:38:16 -0500	received badge	● Scholar (source)
2019-12-12 13:38:06 -0500	answered a question	sick_scan Launch error The problem was a networking error with the LiDAR and the PC. The IP Address was slightly off and was found by using SOP
2019-12-12 13:38:06 -0500	received badge	● Rapid Responder (source)
2019-12-12 10:02:58 -0500	commented answer	sick_scan Launch error I have configured the device in SOPAS with an IP Address of 169.254.181.101 , Subnet-mask of 255.255.0.0, and a Gateway
2019-12-12 09:51:12 -0500	commented answer	sick_scan Launch error I have configured the device in SOPAS with an IP Address of 169.254.181.101 , Subnet-mask of 255.255.0.0, and a Gateway
2019-12-12 08:16:39 -0500	received badge	● Popular Question (source)
2019-12-11 16:44:10 -0500	edited question	sick_scan Launch error sick_tim_5xx launch Errors I am new to using ROS and am trying to use a Tim561 lidar with sick_scan. When I run the comm
2019-12-11 14:35:49 -0500	asked a question	sick_scan Launch error sick_tim_5xx launch Errors I am new to using ROS and am trying to use a Tim561 lidar with sick_scan. When I run the comm
2019-12-08 02:21:52 -0500	marked best answer	ROS kinetic Instulation Error (Ubuntu 16.04 LTS) I am new to ROS and Ubuntu so apologies for asking a question on probably a simple fix. I am trying to install the ROS full Desktop with the following command on a dual booted dell precision 5520 with Ubuntu 16.04 LTS. sudo apt-get install ros-kinetic-desktop-full After running this command I get the following end message. 53 upgraded, 838 newly installed, 0 to remove and 244 not upgraded. Need to get 529 MB/530 MB of archives. After this operation, 2,453 MB of additional disk space will be used. Do you want to continue? [Y/n] What do i need to do in order to fix the issue? If i say yes will this mess anything up?
2019-12-08 02:21:22 -0500	answered a question	ROS kinetic Instulation Error (Ubuntu 16.04 LTS) The dialog is just asking if I would like to continue. Found a good answer to the question at the following website link
2019-12-08 02:21:22 -0500	commented question	ROS kinetic Instulation Error (Ubuntu 16.04 LTS) how to do I perform moderation to the question?
2019-12-08 02:21:22 -0500	asked a question	ROS kinetic Instulation Error (Ubuntu 16.04 LTS) ROS kinetic Instulation Error (Ubuntu 16.04 LTS) I am new to ROS and Ubuntu so apologies for asking a question on probab
2019-12-07 19:48:06 -0500	received badge	● Rapid Responder (source)