Closed andsmith closed 8 years ago
Same problem here. Therefore, I do not think it is a malfunctioning device.
To better manage data rates for a wide variety of customers, the TiM does not output RSSI data by default. It must first be enabled in the configuration software by downloading SOPAS-ET 3.2.0, connecting to the sensor using USB or Ethernet, logging in (UID: Authorized Client, PWD: client), and clicking the checkbox shown below:
Although your line <param name="intensity" type="bool" value="True" />
should perform the same function. Running the configuration software may be a good way to double-check that the parameter is properly set.
The parameter intensity
only works if the device is already configured to output RSSI. If the datagrams don't include RSSI data, the parameter does nothing. So the solution is to enable RSSI output in SOPAS, as described by @SICK-NorthAmerica . I'll add it to the ROS wiki page!
Thanks guys! It was the configuration indeed. It's working now.
Actually, I've checked the code again. The intensity
param didn't do anything in the TiM551/571 parser, only for the other scanners. I've changed that and added a (hopefully helpful) warning.
What I said before remains valid: Intensities are only output if intensity = true
(this is the default) and RSSI output is enabled in the scanner.
thanks, it worked!
The .intensities attributes of the LaserScan messages is empty, even though the parameter is true:
And my launch file explicitly sets it:
(the ranges & other data look correct, though)
I did some poking around in the ROS node source, and it appears the RSSI data aren't even in the datagrams it's getting from the device.
Could this be a malfunctioning device, or maybe incorrectly configured?