Have shifted gears from use of hector slam and this discussion is for ROS Kinetic so it is 'common ground'.
This is standard stuff below so I hope somebody will offer up a clue. I thank anyone in advance for tips here. Really hit a wall so had to ask the board. Thanks.
Am able to run my bot with lidar and then run rosrun gmapping slam_gmapping scan:=scan.
Then run rviz and the bot, the laserscan and even the map shows up because this bot can see all walls in just one place.
I start with a map file that is all grey and have tried all white as well and sure enough Rviz when running gmapping does show me the map that I 'think' I want saved to a file later.
I don't move the bot at all so odom remains completed fixed and never changing.
Then while gmapping is running I use rosrun map_server map_saver -f robo-mag-ils and it appears to be very 'happy' and generates a pgm and yaml map file.
This all seems really nice but then when I open the pgm file it is totally blank yet Rviz is really nicely showing /map as an area that is grey right under my lidar scan boundaries.
The grey area is not fully surrounded with black as a few areas just end in gray but end right where the lidar is showing.
The rosrun tf view_frames offers up a picture where top to bottom I see map -> odom -> base_link -> laser
So my question is perhaps self answered but I ask anyway because it all looks very nice in Rviz the code has made a map visually, I just cannot save it.
I run rviz on a VM also on Kinetic that has worked very well for me so far visually and the bot is on same linux, ubuntu mate 16.04
So it looks really nice BUT some of the darn tf errors for timestamps show up so here is a diagnostic 'rosrun tf tf_monitor'
RESULTS: for all Frames
Frames:
Frame: /laser published by unknown_publisher Average Delay: -0.0191184 Max Delay: 0
Frame: /odom published by unknown_publisher Average Delay: -0.0191513 Max Delay: 0
Frame: /sensor_axis published by unknown_publisher Average Delay: -0.0190958 Max Delay: 0
Frame: base_link published by unknown_publisher Average Delay: 0.00096508 Max Delay: 0.00184041
Frame: odom published by unknown_publisher Average Delay: -0.0493939 Max Delay: 0
And 'finally' here is what gmapping shows with a key 'clue' I think of the TF_OLD_DATA yet the dang map shows really nicely in Rviz
Since I don't know how this is 'supposed' to look maybe it is obvious to others. If it is the timestamp thing I have no idea how to 'loosen up' the window because the times above don't strike me as insane, just non zero yet the message comes out.
rosrun gmapping slam_gmapping scan:=scan
Warning: TF_OLD_DATA ignoring data from the past for frame base_link at time 1.49016e+09 according to authority unknown_publisher
at line 260 in /tmp/binarydeb/ros-kinetic-tf2-0.5.13/src/buffer_core.cpp
Warning: TF_OLD_DATA ignoring data from the past for frame sensor_axis at time 1.49016e+09 according to authority unknown_publisher
at line 260 in /tmp/binarydeb/ros-kinetic-tf2-0.5.13/src/buffer_core.cpp
[ INFO] [1490157882.056171892]: Laser is mounted upwards.
-maxUrange 4.99 -maxUrange 4.99 -sigma 0.05 -kernelSize 1 -lstep 0.05 -lobsGain 3 -astep 0.05
-srr 0.1 -srt 0.2 -str 0.1 -stt 0.2
-linearUpdate 1 -angularUpdate 0.5 -resampleThreshold 0.5
-xmin -100 -xmax 100 -ymin -100 -ymax 100 -delta 0.05 -particles 30
[ INFO] [1490157882.142816158]: Initialization complete
update frame 0
update ld=0 ad=0
Laser Pose= -0.03 0 -3.14159
m_count 0
Registering First Scan
ANOTHER QUESTION: Is it a clearly 'bad' sign that gmapping stops right here after above line? Maybe it is?
I'm about ready to fire up my neato stuff and try to see what working map looks like on gmapping screen and I have not noted that level of detail on one of Camp's 20000 demos ... (we love the demos Camp)