Skip to content
This repository has been archived by the owner on Jan 14, 2023. It is now read-only.

Read all the width as reported by the laser #8

Open
wants to merge 2 commits into
base: obsolete/master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -105,11 +105,16 @@ sensor_msgs.LaserScan toLaserScanMessage(String laserFrame, LaserScan scan,
"Number of scans in configuration does not match received range measurements (%d > %d).",
numberOfConfiguredRanges, scan.getRanges().length));
float[] ranges = new float[numberOfConfiguredRanges];
int scannedRanges = scan.getRanges().length;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this change necessary? Is numberOfConfiguredRanges computed incorrectly?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will avoid painful debugging and unnecessary crashes in favor of a clear warning message if, for any unanticipated reason, numberOfConfigured ranges doesn't match scan.getRanges().length - as it happened to us when trying to use this code.

The reason numberOfConfiguredRanges could be different than scan.getRanges().length is because the former is calculated at configuration time (FF command) but the number of ranges on each scan can technically be different for each distance acquisition request (MD).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In that case, just set numberOfConfiguredRanges = scan.getRanges().length.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm ... are you sure about that? In most cases both should match. A mismatch between them might indicate a higher-level logic error. I think this will end up being a useful check, it does provide additional information about what's going on to the programmer. And in most circumstances, both numbers should match anyway, particularly with the change below

for (int i = 0; i < numberOfConfiguredRanges; i++) {
int step = i + configuration.getFirstStep();
// Select only the configured range measurements and convert from
// millimeters to meters.
ranges[i] = (float) (scan.getRanges()[step] / 1000.0);
if(step>=scannedRanges) {
ranges[i] = 0;
} else {
ranges[i] = (float) (scan.getRanges()[step] / 1000.0);
}
}
result.setRanges(ranges);
result.setTimeIncrement(configuration.getTimeIncrement());
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -117,6 +117,8 @@ private void waitUntilReady() {
boolean ready = false;
while (!ready) {
ready = true;
// NOTE(Julian Cerruti) At this moment, the sent command does not matter much.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please use your username in NOTEs and TODOs. In this case though, I think you can just write a comment. No one needs to track you down to understand the motivation here.

// Currently fixed to (0; 768)
write("MD0000076800001");
try {
checkMdmsStatus();
Expand Down Expand Up @@ -260,8 +262,9 @@ public void startScanning(final LaserScanListener listener) {
@Override
public void run() {
while (true) {
String command = "MD00000768000%02d";
write(String.format(command, 99));
String command = String.format("MD%04d%04d000%02d", configuration.getFirstStep(),
configuration.getLastStep(), 99);
write(command);
checkMdmsStatus();
checkTerminator();
String scansRemaining = "99";
Expand Down