Currently, when running a full system test, nav never makes it past the first step of its solution because comm returns movement feedback of 0.0. Since that's not within nav's acceptable error margin, it re-runs SBPL to find a new path, feeds another movement command to comm, is returned 0.0 again and this process repeats forever. If comm would return the value sent to it, as if the move had completed perfectly, I would be able to do testing past this stage. I would also be able to write logic to parse the data structure returned by comm, as I'll have a realistic return value.
Currently, when running a full system test, nav never makes it past the first step of its solution because comm returns movement feedback of 0.0. Since that's not within nav's acceptable error margin, it re-runs SBPL to find a new path, feeds another movement command to comm, is returned 0.0 again and this process repeats forever. If comm would return the value sent to it, as if the move had completed perfectly, I would be able to do testing past this stage. I would also be able to write logic to parse the data structure returned by comm, as I'll have a realistic return value.