Setting Ambient Suppression and Cam Exposure from ROS driver?

[ana-GT]

Hi! I am using a Photoneo M to detect some small pieces. Some of these pieces can only be detected by changing the Ambient Suppression / Cam Exposure variables from their default values. I'd like to be able to change those parameters from the phoxi_camera driver but, unless I am missing something, this does not seem possible with the current code. Would there be any plans of making the driver capable of setting these parameters?

For the time being, we are just changing the parameters aforementioned by directly changing them in the PhoXi control interface, however my detection task involves detecting different parts at different times, which means that for some parts I need to use the default parameter settings, whereas for more challenging parts I need to adjust a couple of parameters. Iideally I'd like to setup a launch file which could set the Phoxi parameters according to which part is being analyzed so the process is automatic.

Thanks for your time!

Ana

[najlepsiwebdesigner]

Hello Ana,

We are planning to add some configuration options to our PhoXiCamera node by the end of this year. Implementation will be ROS standard - you'll be able to define your params in yaml, or directly on param server. However, for change of params to be reflected, you'll have to restart the node.

The PhoXiControl team is well aware of fact that our customers need to switch different configurations of Photoneo quicky. For this reason, they are currently testing feature called scanner profiles. This feature will allow you to reconfigure the scanner on-the-fly. I do not have more information on this (release date etc.), if you want to know more, maybe try asking our customer care at support@photoneo.com.

I hope I helped :)

Peter,
Team Lead of ROS development

[ana-GT]

Hi Peter! That is good to hear, thanks! I took a look at the Github repository and I see that there is a branch named tests-update, that looks as if it is doing what you described (take a .yaml and use it to configure the Photoneo). I'd like to give it a try, so I am wondering if the only thing I have to do is to compile this branch and just use it? Or perhaps I'd also need a newer version of the PhoXi control library? Thank you very much for your help! Best, Ana 2018-08-13 13:39 GMT-05:00 Peter Beňo <notifications@github.com>:

…

Hello Ana, We are planning to add some configuration options to our PhoXiCamera node *by the end of this year*. Implementation will be ROS standard - you'll be able to define your params in yaml, or directly on param server. However, for change of params to be reflected, you'll have to restart the node. The PhoXiControl team is well aware of fact that our customers need to switch different configurations of Photoneo quicky. For this reason, they are currently testing feature called *scanner profiles*. This feature will allow you to reconfigure the scanner on-the-fly. I do not have more information on this (release date etc.), if you want to know more, maybe try asking our customer care at ***@***.*** I hope I helped :) Peter, Team Lead of ROS development — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAh5cz_3nZ3HikY9v4lWDHpcwYoeKhsWks5uQcfWgaJpZM4V4-l2> .

[najlepsiwebdesigner]

Hi Ana,

we do have a configuration file for some ROS params, they are located at https://github.com/photoneo/phoxi_camera/blob/master/config/phoxi_camera.yaml

This list is really short in comparison with number of parameters available in PhoXiControl application. Ambient Suppression / Cam Exposure are missing, yet. I'm sorry.

Branch tests-update was just obsolete feature branch, the current code can be found in latest release, 2.0.0. or default branch of this repo.

As I've stated before, we want to include more params in ROS node in next release by the end of this year, I'll make sure that Ambient Suppression / Cam Exposure will be included.

Regards,

Peter