(Solved?) Feed override encoder reset

More
5 years 3 weeks ago #222712 by cmorley
Oh you mean qtpyvcp already supplies the pin to reset the overrides?

Please Log in or Create an account to join the conversation.

More
5 years 3 weeks ago #222779 by Joco
cmorley - yes.   There is a plug-in that needs to be enabled in either a UIs yaml config or the user can enable it by creating their own custom_config yaml file. 

In the “data_plugins” section add:
Code:
hal: provider: qtpyvcp.plugins.exported_hal:ExportedHal

Please Log in or Create an account to join the conversation.

More
5 years 3 weeks ago #222785 by cmorley
Ok that makes sense now :)

Please Log in or Create an account to join the conversation.

More
5 years 2 weeks ago #222981 by andypugh
I would support this as a new halui pin.

FWIW Axis has this as a GUI action when you press the zero key.

Please Log in or Create an account to join the conversation.

More
4 years 3 months ago #247202 by tightmopedman9
I'm having trouble setting up overrides as described in this topic. I'm getting an error that the pin(s) qtpyvcp.feed-override.reset and qtpyvcp.speed-override.reset don't exist. I've put nets to the signals in the custom_post_gui.hal and I have checked in halmeter that the aforementioned pins exist.

This is the relevant error code:
[qtpyvcp.app.launcher][[36mINFO[0m]  Loading POSTGUI_HALFILE: /home/aaron/linuxcnc/configs/PNCCONF-Probe Basic/postgui_call_list.hal (launcher.py:96)
custom_postgui.hal:5: Pin 'qtpyvcp.speed-override.reset' does not exist
Failed to load POSTGUI_HALFILE with error: 1

These are the lines in HAL:
net     feed-override-reset     qtpyvcp.feed-override.reset
net     speed-override-reset     qtpyvcp.speed-override.reset
 

Please Log in or Create an account to join the conversation.

More
4 years 3 months ago #247205 by spumco
Replied by spumco on topic Feed override encoder reset
The problem is probably in your custom_config.yml file.

For the qtpyvcp-specific pins to be available in HAL, you have to edit the .yml file.  Open your file (its just a text file) and make sure you have the following:
Code:
windows:   mainwindow:     kwargs:       confirm_exit: false data_plugins:   tooltable:     provider: qtpyvcp.plugins.tool_table:ToolTable     kwargs:         columns: TPZDR   exportedhal:     provider: qtpyvcp.plugins.exported_hal:ExportedHal

Specifically, the "exportedhal:..." stuff is what causes the qtpyvcp pins to become available, which you can then refer to and connect in a post_gui hal file.

Save the custom config with the exportedhal stuff and have another go.  Betcha all the cool spindle-load and FRO/RRO stuff shows up - you can verify in halshow under pins => qtpyvcp

Bonus: the "columns: TPZDR" line above it will change how the tool table appears in PB.  "T" is tool number, "P" is pockets, "Z" is Z-offset.  You can add/remove any of the columns by adjusting that little line.  It doesn't change the actual table, just what's displayed in PB.
The following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

Time to create page: 0.158 seconds
Powered by Kunena Forum