qtpyvcp stored parameters

More
6 years 1 month ago #182012 by anfänger
Hi,,

maybe this is stupid question again, but where can I din a list of stored parameters qtpyvcp ist using?
The reason is simple I want to know what tool was in the spindle before shutdown.
qtpyvcp ist restoring the the tool after homing. But I would like to know the tool number before homing.
And I think qtpyvcp is doing this with a parameter.

I have a m-code restoring the tools in atc after startup and I want to know if one of the tools is in the tool changer.
The reason for this is, I need to cool the bearings if my tool changer and want to set the signal while powering up.
I can manage already when changing tools, but not on startup.

Thanks Patrick

Please Log in to join the conversation.

More
6 years 1 month ago #182017 by TurBoss
Replied by TurBoss on topic qtpyvcp stored parameters
persistent data is stored with the "data_manager" plugin

read: github.com/kcjengr/qtpyvcp/blob/master/q...s/tool_table.py#L156
write: github.com/kcjengr/qtpyvcp/blob/master/q...s/tool_table.py#L205



kudos go to @KCJ

Please Log in to join the conversation.

More
6 years 1 month ago #182053 by anfänger
Replied by anfänger on topic qtpyvcp stored parameters
Thanks,
can I access the „data_manager“ from M-Code?
Or otherwise fill the widget from python?
At the moment I am filling my atc widget this way:

Code:
#1 = 0 o130 while [#1 LT 12] #1 = [#1+1] #2 = #[5189+#1] (DEBUG, EVAL[vcp.getWidget{"dynatc"}.store_tool{#1, #2}]) o130 endwhile

And I want something like this (it‘s happening before homing, so qtpyvcp did not set the tool in spindle yet):
Code:
#1 = 0 o130 while [#1 LT 12] #1 = [#1+1] #2 = #[5189+#1] o135 if [#<tool_in_spindle]> eq #2] M135 P1 o135 endif (DEBUG, EVAL[vcp.getWidget{"dynatc"}.store_tool{#1, #2}]) o130 endwhile

As an alternative to M135 I can manipulate a hal button

Please Log in to join the conversation.

Time to create page: 0.464 seconds
Powered by Kunena Forum