Open SteveMacenski opened 4 months ago
This issue was likely to do with the setup_path
being passed in. The path resolution was naive and expected a directory to end with a /
in order to join the robot.yaml
file to the directory path. I'm assuming that this was the cause of your issues and why you were able to resolve it by getting rid of the requirement on the namespace
, and therefore did not need to use the opaque function to load the robot.yaml
. I have made the fix in #62.
Please provide the following information:
main
Real hardware or simulation: N/A
Expected behaviour
Works, but for some reason I cannot get that setup path to be respected and I get errors in launch about no YAML can be found. After about 15 minutes of playing around I just copy pasted its contents into my launch file and works fine. the battery updater/estimator seem to get the setup_path correctly, and I'm not 100% sure why it is that this launch file isn't quite working (perhaps the opaque function?)
Actual behaviour
Works: