@Ant1 We realized that after putting the U axis under tension using M17 U, there is an interference between the BL Touch's ground and the U motor phases... So we are now investigating this issue. So I think that the issue doesn't come from the firmware, so I guess we can close this topic and we will test our setup on our side... Thank you very much for your help !!

@chrishamm @stuartofmt I also find a bit dangerous / weird to use exec(...) to compare the versions, as it can very easily lead to code injection, even though it is probably not the intent of people writing plugins.
Edit: the allowed characters are limited (for example, no parentheses), so this is probably not possible.

@chrishamm Thanks a lot, that was the problem ! I was looking at an old documentation page that didn't show that this permission was possible... Thank you !

@Ant1 As a note, this issue happens with DSF 3.5.2. I tried to reproduce it with DSF 3.5.1, but the issue doesn't happen and the message gets shown properly on the PanelDue, so I think that the issue comes from the update.

@chrishamm I experience a similar issue, but when M291 is called from plugins... Here is the issue that I have opened to describe my problem: https://forum.duet3d.com/topic/36365/m291-issued-from-a-plugin-doesn-t-show-anything-on-the-paneldue

I am creating a plugin which intercepts a certain M-code (M1000 in my case), and then performs a bunch of things with the machine. At some point, it needs to open a message box using M291. It does so using CommandConnection.perform_simple_code('M291 ...').

Depending on how the plugin is called, the message box doesn't get showed on the PanelDue. Here is what I have observed:

• When I call M1000 from the command console on the PanelDue, which triggers the plugin, the message box is shown, as expected.
• If M1000 is wrapped in a macro, which is ran from the PanelDue, the plugin is triggered, but the message box isn't shown on the PanelDue - only in the web interface.

Expected:
M291 should open the message box on the PanelDue in all cases, otherwise it is annoying because I need to open a web interface to run this macro.

@chrishamm Thanks a lot, that was the problem ! I was looking at an old documentation page that didn't show that this permission was possible... Thank you !

Hello !

I am writing a plugin that uses a raspberry PI camera to calibrate print heads. I encounter an issue where the camera won't start when constructing the camera object:

from picamera2 import PiCamera2
cam = Picamera2()

Returns the following error:
[0:32:17.478523088] [4325]  INFO Camera camera.cpp:990 Pipeline handler in use by another process
Camera __init__ sequence did not complete.

I am pretty sure that this issue is due to the apparmor configuration because if I run the exact same script from another folder on the raspberry PI, I don't get any errors...

Do you have any experience using a Raspberry PI camera from the plugins ?

Thanks for your help !

@achrn
Thank you a lot ! This was indeed the problem, I didn't have launchProcesses. I removed it at some point because I didn't think it was necessary to run the python script, but since it depends on an external library, that might cause the issue

Thank you !

@chrishamm
Yes I have already done that. My plugin.json contains the following:

  "sbcPackageDependencies": ["libzbar0", "python3-picamera2"],
  "sbcPythonDependencies": ["opencv-python", "pyzbar", "Pillow", "numpy", "dsf-python>=3.5.0.2rc2"],

@chrishamm

I have tried to change the line ending with dos2unix but it still gives me the same error...

If I change the first line to #!/usr/bin/python3, as you suggested, I get the following error:

from pyzbar.pyzbar import decode, ZBarSymbol
...
ImportError: Unable to find zbar shared library 

Which is weird, because I have installed this library and all its dependencies, and I can get the import to work in a python3 interpreter, with no errors:

Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pyzbar
>>>  

So it seems to me that something is not quite right with the DSF environment or PATH... Any ideas ?

Hello ! I wrote a python plugin for my duet and I get the following error when I start the plugin from the web interface:

/usr/bin/env: ‘python3’: Permission denied

I have installed the same plugin on another duet board, and it starts without errors, but on this one it somehow doens't work... I have compared the python, dsf-python, duetsoftwareframework versions on both machines and they have the same packages.

Is there something that could be mis-configured on the raspberry PI ?

Thank you for your help !

Antoine Brunner

@chrishamm @stuartofmt I also find a bit dangerous / weird to use exec(...) to compare the versions, as it can very easily lead to code injection, even though it is probably not the intent of people writing plugins.
Edit: the allowed characters are limited (for example, no parentheses), so this is probably not possible.