Connect HAL_LED to probe_in

More
11 Oct 2017 18:43 - 11 Oct 2017 18:46 #100223 by wedlocki
wedlocki created the topic: Connect HAL_LED to probe_in
HELLO

I'm not a good programmer and I do not understand English very well. That's why I am writing Google translate: D

I can not connect the HAL_LED to the probe sensor pin. Of course the probe works and is connected to the correct pin in the LPT port.

The second problem is to configure the milling movement after the measurement. Where and what to write to the measurement after the cutter moved to the top position (in my machine is G53 Z0) and only after the milling cutter to the material. Currently, all X Y and Z moves are executed simultaneously, which can cause the cutter to hit the clamp.


Here are my files.
Attachments:
Last Edit: 11 Oct 2017 18:46 by wedlocki.
More
11 Oct 2017 20:35 #100233 by newbynobi
newbynobi replied the topic: Connect HAL_LED to probe_in
Please change

net buttons buttons.led_tool_sensor

To
net probe-in buttons.led_tool_sensor

Norbert
More
12 Oct 2017 16:38 #100275 by wedlocki
wedlocki replied the topic: Connect HAL_LED to probe_in
Im change "net buttons buttons.led_tool_sensor" to "net probe-in buttons.led_tool_sensor" and gmoccapy take me a error (listed below) . But when im run a gmoccapy without this line im see in halmeter/pins all my buttons pins. Pin named buttons.led_tool_sensor have IN directory. All other have OUT




Debug file information:
.
/usr/bin/gmoccapy:237: GtkWarning: Invalid icon size 48

self.widgets.window1.show()

(gmoccapy:8857): GtkSourceView-CRITICAL **: gtk_source_language_manager_set_search_path: assertion `lm->priv->ids == NULL' failed
custom_postgui.hal:22: Pin 'buttons.led_tool_sensor' does not exist
Traceback (most recent call last):
File "/usr/bin/gladevcp", line 45, in <module>
import gladevcp.makepins
File "/usr/lib/pymodules/python2.7/gladevcp/__init__.py", line 1, in <module>
from hal_pythonplugin import *
File "/usr/lib/pymodules/python2.7/gladevcp/hal_pythonplugin.py", line 30, in <module>
from overridewidget import Override
File "/usr/lib/pymodules/python2.7/gladevcp/overridewidget.py", line 17, in <module>
import sys,os,pango
KeyboardInterrupt
More
12 Oct 2017 21:20 - 12 Oct 2017 21:30 #100283 by rodw
rodw replied the topic: Connect HAL_LED to probe_in
This is your error.
custom_postgui.hal:22: Pin 'buttons.led_tool_sensor' does not exist
I'm guessing you have not installed a component with loadrt or there is a non standard Hal component used that needs to be halcompiled

For your gcode error, it is up to you to retract to a safe Z height to clear your clamps. Maybe something like
G0 Z25 (move above clamp)
G53 Z0
Last Edit: 12 Oct 2017 21:30 by rodw.
More
13 Oct 2017 21:05 #100334 by newbynobi
newbynobi replied the topic: Connect HAL_LED to probe_in
Rod, in this case a am pretty sure, that you are not rigth. The behavior is relatavely shure caused due to a race conflict. The glade panel is not ready, whiele postgui hal is allready feaded an processed.

He will have to transfer the line to a separate hal file and load that file from his ini file including it in the gladevcp line in his ini. I am not on my PC, so i can not public the complete line right now, i will do this weekend.

Norbert
More
14 Oct 2017 09:50 - 14 Oct 2017 09:52 #100345 by newbynobi
newbynobi replied the topic: Connect HAL_LED to probe_in
@wedloki,

please make a new hal file, i.e. my_panel.hal with following content:
net probe-in buttons.led_tool_sensor

Erase the named line from your postgui.hal file!

than change your INI file, where you load your panel to be something like:
(I do not know how you load your panel, so the command may differ, the important part is the -H my_panel.hal)

EMBED_TAB_COMMAND = gladevcp -x {XID} -H my_panel.hal buttons.glade

(you need to adapt the names to fit your file naming!

does it work now?

Norbert
Last Edit: 14 Oct 2017 09:52 by newbynobi.
The following user(s) said Thank You: wedlocki
More
17 Oct 2017 17:24 #100487 by wedlocki
wedlocki replied the topic: Connect HAL_LED to probe_in
thx newbynobi. it works !!!! And u have right , this is a race condition.


The second problem is to configure the milling movement after the measurement. Where and what to write to the measurement after the cutter moved to the top position (in my machine is G53 Z0) and only after the milling cutter to the material. Currently, all X Y and Z moves are executed simultaneously, which can cause the cutter to hit the clamp. I think in custom GMOCCAPY file change.gnc but i dont know where
Moderators: newbynobi
Time to create page: 0.080 seconds
Powered by Kunena Forum