Skip to content
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

Incorrect message #2

Open
aeksiri opened this issue Mar 8, 2019 · 1 comment
Open

Incorrect message #2

aeksiri opened this issue Mar 8, 2019 · 1 comment

Comments

@aeksiri
Copy link

aeksiri commented Mar 8, 2019

Hi, I have cloned your sicknav350 repo.
And I've changed the sicknav350.launch as shown bellow.
......
......
<launch> <node pkg="sicknav350" type="sicknav350_node" name="sicknav350" output="screen" > <param name="scan" value="scan" /> <param name="publish_tf" value="true" /> <param name="publish_odom_" value="true" /> <param name="publish_scan" value="true" /> <param name="port" value="2111" /> <param name="ipaddress" value="192.168.0.10" /> <param name="inverted" value="false" /> <param name="fram_id" value="front_laser" /> <param name="fixed_frame_id" value="front_mount" /> <param name="laser_frame_id" value="map" /> <param name="laser_child_frame_id" value="reflector" /> <param name="resolution" value="1.0" /> <param name="start_angle" value="0.0" /> <param name="stop_angle" value="360.0" /> <param name="scan_rate" value="5.0" /> </node> </launch>
.......
.......
Then, I've got error "Incorrect message" as shown bellow

... logging to /home/denso/.ros/log/9dccace4-4169-11e9-89ac-144f8adee130/roslaunch-agccontrolpanel-12971.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://agccontrolpanel:38549/

SUMMARY

PARAMETERS

  • /rosdistro: kinetic
  • /rosversion: 1.12.14
  • /sicknav350/fixed_frame_id: front_mount
  • /sicknav350/fram_id: front_laser
  • /sicknav350/inverted: False
  • /sicknav350/ipaddress: 192.168.0.10
  • /sicknav350/laser_child_frame_id: reflector
  • /sicknav350/laser_frame_id: map
  • /sicknav350/port: 2111
  • /sicknav350/publish_odom_: True
  • /sicknav350/publish_scan: True
  • /sicknav350/publish_tf: True
  • /sicknav350/resolution: 1.0
  • /sicknav350/scan: scan
  • /sicknav350/scan_rate: 5.0
  • /sicknav350/start_angle: 0.0
  • /sicknav350/stop_angle: 360.0

NODES
/
sicknav350 (sicknav350/sicknav350_node)

auto-starting new master
process[master]: started with pid [12981]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to 9dccace4-4169-11e9-89ac-144f8adee130
process[rosout-1]: started with pid [12994]
started core service [/rosout]
process[sicknav350-2]: started with pid [13008]
*** Attempting to initialize the Sick Nav350...
Attempting to connect to Sick Nav350 @ 192.168.0.10:2111
Connected to Sick Nav350!
Attempting to start buffer monitor...
Buffer monitor started!
Attempting Login as Authorized Client ...
Login Successful
Synchronized!
set operating_mode_command
Set operating mode
Incorrect message
*** stack smashing detected **: /home/denso/sicknav350_ws/devel/lib/sicknav350/sicknav350_node terminated
[sicknav350-2] process has died [pid 13008, exit code -6, cmd /home/denso/sicknav350_ws/devel/lib/sicknav350/sicknav350_node __name:=sicknav350 __log:=/home/denso/.ros/log/9dccace4-4169-11e9-89ac-144f8adee130/sicknav350-2.log].
log file: /home/denso/.ros/log/9dccace4-4169-11e9-89ac-144f8adee130/sicknav350-2
.log
^C[rosout-1] killing on exit
^C[master] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done

....
....
....

@aeksiri
Copy link
Author

aeksiri commented Mar 14, 2019

It's work. I've just turned it off then turn it on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant