Python/NC routine just stops executing
24 Aug 2024 13:45 - 24 Aug 2024 17:31 #308532
by Aciera
Replied by Aciera on topic Python/NC routine just stops executing
Not sure if this is the root of your problem but it's certainly possible.
The problem with '.wait_complete()' is that it does not work the way many of us think it does. It's not as simple as just slapping it in after an '.mdi()' because it's purpose is not to actually ensure that the command has been executed. Also many are not aware that it works with a timeout that has a built in default value of 5 seconds.
linuxcnc.org/docs/stable/html/config/pyt...inuxcnc_command_code
So '.wait_complete()' actually returns a value (-1 if timed out, RCS_DONE if the command has been executed successfully or RCS_ERROR if not).
If you now look at this snippet in your code as an example:
It becomes clear that whenever you are calling '.wait_complete()' you are really not doing much at all because no matter the return value you just continue anyway and if the MDI command takes more then 5 seconds your code also just carries on and changes the mode. So if '.wait_complete()' is not used to actually receive its return value and make decisions upon that value it's basically nothing more than a timer with the benefit of allowing code execution to go on before the timeout occurs if the mdi command either executed successfully (RCS_DONE) or failed (RCS_ERROR).
Have a look at this example from '/lib/python/qtvcp/qt_action.py':
[edit]
In your case it may be as simple as extending the timeout of the second '.wait_complete()' to say 200s, depending on how long 'vacuum.ngc' takes to complete as it clearly does not seem to be as simple a task as switching on a vac:
The problem with '.wait_complete()' is that it does not work the way many of us think it does. It's not as simple as just slapping it in after an '.mdi()' because it's purpose is not to actually ensure that the command has been executed. Also many are not aware that it works with a timeout that has a built in default value of 5 seconds.
linuxcnc.org/docs/stable/html/config/pyt...inuxcnc_command_code
So '.wait_complete()' actually returns a value (-1 if timed out, RCS_DONE if the command has been executed successfully or RCS_ERROR if not).
If you now look at this snippet in your code as an example:
sCommand.mode(linuxcnc.MODE_MDI)
sCommand.wait_complete()
sCommand.mdi("o<vacuum> call")
sCommand.wait_complete()
sCommand.mode(saveMode)
print("vacuumTable finished")It becomes clear that whenever you are calling '.wait_complete()' you are really not doing much at all because no matter the return value you just continue anyway and if the MDI command takes more then 5 seconds your code also just carries on and changes the mode. So if '.wait_complete()' is not used to actually receive its return value and make decisions upon that value it's basically nothing more than a timer with the benefit of allowing code execution to go on before the timeout occurs if the mdi command either executed successfully (RCS_DONE) or failed (RCS_ERROR).
Have a look at this example from '/lib/python/qtvcp/qt_action.py':
[edit]
In your case it may be as simple as extending the timeout of the second '.wait_complete()' to say 200s, depending on how long 'vacuum.ngc' takes to complete as it clearly does not seem to be as simple a task as switching on a vac:
sCommand.mode(linuxcnc.MODE_MDI)
sCommand.wait_complete()
sCommand.mdi("o<vacuum> call")
sCommand.wait_complete(200)
sCommand.mode(saveMode)
print("vacuumTable finished")Attachments:
Please Log in or Create an account to join the conversation.
Time to create page: 0.098 seconds