MDI calls from qtvcp

Hi all. I ran into an obscure issue when calling MDI on a button click.
there is a method in which MDI is called:

if you send commands such as G92X0Y0Z0 they work instantly and do not cause any problems.

The first version of the problem:
if you send something like G0X2000Y6000, then the command works for 10 seconds and the interface seems to freeze: gcode_graphic does not display anything, the coordinates do not change, no buttons respond to pressing. but after 10 seconds ("complete_time") everything hangs but the command is not executed to the end.

second version of the problem:
If you specify a long time for complete_time, for example equal to 180, and issue the G0X2000Y6000 command, then everything will happen the same as in the first option, except that the axis will reach the command executor.

third option:
if everything is done as in the second option, except that you set the time for complete_time not as an int, but as a list, i.e. complete_time = [180] then the interface does not freeze, everything works fine, except for one BUT. there is a qtvcp warning that the value for complete_time must be specified as a real number, not as a list!

how to solve such a problem?

P.S.: I understand that the question is too confusing, maybe I will shoot a video on 3 senarias and stick it in the following posts, however, if someone came across and understood what was happening and could tell me, I would be grateful

I'm not a code guy, like at all but I had help with a custom interface I needed. When I issued MDI through Python I had the program probing for a status to confirm completion. Like after a movement the program checked for the "in-position" flag or something like that. There's probably some other flag to check for the finish of an MDI execution but I'm not sure that waiting based on time is the greatest way to go about it.

Look in qtvcp's ACTION library:
github.com/LinuxCNC/linuxcnc/blob/master...cp/qt_action.py#L172

From memory the problems are:
asking for a mode linuxcnc is already in can cause a long pause.
using wait_complete will always cause the python program to freeze till the command ends.
monitoring the error status (if you need to) is a race condition

It's actually a difficult problem to work around.
What kind of MDI command do you wish to run?

cmorley wrote:

Look in qtvcp's ACTION library:
github.com/LinuxCNC/linuxcnc/blob/master...cp/qt_action.py#L172

.....

It's actually a difficult problem to work around.
What kind of MDI command do you wish to run?

 

thank you for your responses. the actions from qtvcp are based on the actions of linuxcnc.py and inherit all of its problems and even multiply them in some cases. in view of which the actions from qtvcp do not simplify the task in any way.

the code that I need to execute is just "G0X2000Y6000" so that the portal goes to the end of the working field

well qtvcp's action library checks the mode linuxcnc is in before trying to change it so that is an improvement from your example.

You need to use wait_complete just so you can change the mode to manual?
maybe you could completely define what behavior you want/need.

cmorley wrote:

well qtvcp's action library checks the mode linuxcnc is in before trying to change it so that is an improvement from your example.

You need to use wait_complete just so you can change the mode to manual?
maybe you could completely define what behavior you want/need.

without using wait_complete, waiting for mdi execution is critically small and only enough to execute something like "g92x0y0z0"

Wait complete only tells the python program to stop running until the command is completed, it doesn't stop the machine controller. If there are commands after mdi that will stop the machine controller (like mode changes) and you don't use wait complete, then the first command will be cut short.

So again, do you need to switch the mode back to manual? Remember I have little idea what you are ultimately trying to do.

There may be another way.
If you can get the serial number of the command, then check status to see if the serial number has past, then that should get you the same as wait_compleye without blocking.

Looks like command has 'serial' and status has echo_serial. Some testing will be needed.

cmorley wrote:

Wait complete only tells the python program to stop running until the command is completed, it doesn't stop the machine controller. If there are commands after mdi that will stop the machine controller (like mode changes) and you don't use wait complete, then the first command will be cut short.

So again, do you need to switch the mode back to manual? Remember I have little idea what you are ultimately trying to do.

 

hi. I just want to get the G0X2000Y6000 command executed.
the method by which I call the execution of the command: