OpenPnP: Camera light actuators and more

There is a new testing version available featuring new built-in camera light actuation (no more scripting). It can support new Profile actuators, so you can control multi-channel lights like RGB etc. A pipeline can optionally control the light actuation, so different light profiles can be used on different pipelines.

In the course of this, actuators have been enhanced and unified across the Gcode/Http/Script implementations.

Likewise, camera classes have been enhanced and unified across the implementations. All camera implementations can now configure Preview FPS. The 0 fps mode (“stills mode”) is fully supported, only the vision-captured images will then be shown. Live preview can also be suspended during jobs/machine tasks, giving a clean shot-by-shot camera view.

In single camera preview, the camera can now be automatically switched when it is active by vision or by user action. You can now have one large preview window to really see the details. Tip: Use right-click/Rendering Quality High on all cameras. Together with suspended live preview in jobs/tasks, a whole new experience is available (see video).

A SwitcherCamera will no longer duplicate the wrong channel, instead the switched-off camera preview is frozen.

Read the Pull Request with extensive Instructions for Use
Download the OpenPnP 2.0 Testing Version
Join the discussion.
Watch the Video

Neugieriger says:

2022-06-23 at 16:27

Can you tell the reason why you have do that , and by the way dropped legacy scripting code (moveTo inside bsh scripting) . Scripting worked fine, the scripts including support for having multiple uplooking cameras was available for downloading, that for using multiple uplooking cameras at the same time too. Now after the change, it’s impossible to customize openPnP for using different cameras/lighting actuators and lightning profiles, unfortunatly. I’m curious.

mark says:

2022-06-23 at 18:04

Hi Neugieriger,

for the vast majority of users, the new way is just much easier to setup and use.

And you can do elaborate lighting profiles.

But if you don’t like it, scripts are still supported!

Most scripts should just work as before, without changing anything in your machine.

But: there have been some other changes, unrelated to lighting, in exception handling. If your scripts cause errors that are “normal”, you must now catch the exceptions in the script, or they will interrupt OpenPnP, as they should.

Please go to the discussion group and post a log, then we can see what is amiss.

_Mark

2022-06-24 at 05:47

Thanks for the explaination.Yes the exception was the problem, not having defined the light actuators.Multiple cameras works, but there are several other things that simply are not working at all. Just as example the TravelSalesman cost me 8 hours of troubleshooting to find out why nothing work. Missing moveTo another 4 hours. Opencv >= 3.5 , 6 days.Need to downgrade machine in order to test out a new version, need to check when it`s possibile.

mark says:

2022-06-24 at 07:03

Hi Neugieriger,

ask on the discussion list, before getting frustrated.

Not only is this better for you, it might also help the next guy when the problems you solve are openly documented. That’s the spirit of Open Source!

Furthermore, it is valuable feed-back for me as a developer of many of the new things. I might learn where to be more careful for not to break things.

Finally, if I hear “OpenCv”, chances are you should be trying out new/improved features in OpenPnP, as an alternative to “porting” an old custom solution.

Du solltest ja dem Namen nach “gierig auf Neues” sein! 😉

_Mark

Leave a Reply Cancel reply