camera config error

[ifm]

camera config error

[tpanzarella]

A few things:

1. That version of the firmware has not yet been tested. Please see the software compatibility matrices on both the o3d3xx-ros and libo3d3xx github pages. Next week, I will be releasing version 0.2.0 of libo3d3xx which is compatible with IFM's 1.1.288 firmware. By association, I'll be releasing o3d3xx-ros version 0.1.7.
2. When calling the ROS Dump service and redirecting the output to a file, realize that rosservice annotates the return data in that file, so, the file is not proper JSON. You should remove the rosservice markup before pumping it into the Config service and try again. OR, stop your ROS framegrabber and just use the libo3d3xx tools: o3d3xx-dump and o3d3xx-config which will dump/load pure (non-annotated) JSON.

I re-emphasize, point 1 above. I have not even looked at that version of the firmware yet.

[bsbc]

On point 2. Yes, I did remove the annotations in the settings.json file -- Othewise the roslaunch o3d3xx config.launch infile:=settings.json the returns with an error.

On 1. Ok. Reverted to an older version of the firmware, so everything is working fine now. Will look for the update.

[tpanzarella]

New code will be released early next week. I'm hoping on Monday. All that is left is a little documentation.

In the meantime, if you want to work in "unsupported mode", I just pushed out my dev branches to github. For libo3d3xx you can build the dev-0.2.0 branch. For o3d3xx-ros you can build the dev-0.1.7 branch. You can then flash your camera with the 1.1.288 firmware available here.

[tpanzarella]

@bsbc Thinking about your original post from above, the behavior you describe is symptomatic of loading up a camera configuration but not having an application marked as active. Two easy ways to check if that were the case: 1) o3d3xx-dump (or call the ROS Dump service), 2) o3d3xx-ls. In the second case, the active application will be marked with an asterisk -- if there is an active application.

Just a thought, if you really wanted to try again. However, the fact remains that I have not had the opportunity to look at the 1.3.x firmware.

[bsbc]

Not having any of the applications marked active might have been a problem. I will double-check that.

For now, we are using Goldeneye-C3_1.1.288-288.swu firmware and updating the configuration (as described originally) works fine.

We will update the firmware once you'll have an official release. Thanks,