Topics created by Ant1

@chrishamm Okay thanks for all the pointers ! I switched all my machines to 3.5.3 and made the changes with the connections that you suggested, and it solves most of my problems.

For the problem that I mentionned due to the machine being shifter along the Z axis after executing a macro from the plugin, I found something that might have caused the issue:

When intercepting a command inside the plugin, I was always starting by sending G90 and M83 to the machine to make sure that whatever mode it is in, I can always perform moves and extrusions in absolute and relative mode, respectively. I suspect that those two commands might have caused the machine to shift position along Z due to synchronization issues because I removed them and the issue never happened again...

@chrishamm Sorry for the later reply on this, I forgot about it and got no notifications!

Here is a minimal setup that reproduces my issue. In this setup, I use a separate connection to intercept and to send commands. If I use a single intercept connection, the issue still happens, but less often.

Also, note that the message box shows up on the PanelDue in about 50% of the cases when sending M2000. But in the the other cases, the message box only pops up in the web interface. I didn't manage to see if it was correlated to something else, as it seemed pretty random to me.

#!/usr/bin/python3 from dsf.connections import InterceptConnection, InterceptionMode, CommandConnection from dsf.object_model.messages import MessageType if __name__ == "__main__": try: intercept = InterceptConnection(InterceptionMode.PRE, filters=['M2000']) command = CommandConnection() command.connect() intercept.connect() while True: code = intercept.receive_code() try: if code.short_str() == 'M2000': command.perform_simple_code('M291 S2 P"Test" X1 Y1 Z1') print(command.perform_simple_code('M409 K"state" F"d99fn"')) intercept.resolve_code(MessageType.Success) except Exception as e: intercept.resolve_code(MessageType.Error, str(e)) finally: intercept.close() command.close()

The output of M409 K"state" F"d99fn" is the following:

{"key":"state","flags":"d99fn","result":{"currentTool":2,"gpOut":[],"laserPwm":null,"msUpTime":646,"status":"idle","time":"2024-10-14T11:27:13","upTime":2238}}

I don't see any messageBox value inside it.

@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 !

@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 !

@Ant1 You can now install the python3-dsf-python Debian package or reference it in your plugin provided you're on v3.5 or newer. This package was gratefully provided by @Falcounet.

@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 !!