LED panel light for probe

More
5 years 6 months ago #207310 by russkinch
Replied by russkinch on topic LED panel light for probe
hi,
here is my ini file
Code:
# General section ------------------------------------------------------------- [EMC] VERSION = 1.1 MACHINE = 6040 Tool sensor DEBUG = 0 # for details see nc_files/subroutines/maco_instructions.txt [MACROS] MACRO = i_am_lost MACRO = halo_world MACRO = jog_around MACRO = increment xinc yinc MACRO = go_to_position X-pos Y-pos Z-pos # Sections for display options ------------------------------------------------ [DISPLAY] DISPLAY = gmoccapy # We do explicit give an preference file here, because otherwise # the sim may not work on other computers. That is also the reason # we use the prefix para, so it will not be ignored from git PREFERENCE_FILE_PATH = gmoccapy_tool_sensor.para EMBED_TAB_NAME = Tool Sensor EMBED_TAB_LOCATION = box_right EMBED_TAB_COMMAND = gladevcp -x {XID} tool_sensor.glade EMBED_TAB_NAME = Part Probe EMBED_TAB_LOCATION = ntb_preview EMBED_TAB_COMMAND = gladevcp -x {XID} gmoccapy2.glade # Cycle time, in milliseconds, that display will sleep between polls CYCLE_TIME = 100 # Highest value that will be allowed for feed override, 1.0 = 100% MAX_FEED_OVERRIDE = 1.5 MAX_SPINDLE_OVERRIDE = 1.2 MIN_SPINDLE_OVERRIDE = 0.5 # Prefix to be used PROGRAM_PREFIX = /home/linuxcnc/linuxcnc/nc_files # Introductory graphic INTRO_GRAPHIC = linuxcnc.gif INTRO_TIME = 5 # list of selectable jog increments INCREMENTS = 1.0 mm, 0.1 mm, 0.01 mm, 0.001 mm [FILTER] PROGRAM_EXTENSION = .png,.gif,.jpg Grayscale Depth Image PROGRAM_EXTENSION = .py Python Script png = image-to-gcode gif = image-to-gcode jpg = image-to-gcode py = python # Task controller section ----------------------------------------------------- [RS274NGC] PARAMETER_FILE = sim.var SUBROUTINE_PATH = macros # optional features - a bit mask to selectively turn on experimental/dubious features # see # RETAIN_G43 0x00000001 # OWORD_N_ARGS 0x00000002 # INI_VARS 0x00000004 # HAL_PIN_VARS 0x00000008 # NO_DOWNCASE_OWORD 0x00000010 # turn on all optional features # turn on optional features in this case just INI reading FEATURES=12 ON_ABORT_COMMAND=O <on_abort> call # parameters exposed by change_prolog/evaluated by change_epilog: # #<tool_in_spindle> # #<selected_tool> # #<current_pocket> # #<selected_pocket> REMAP=M6 modalgroup=6 prolog=change_prolog ngc=change epilog=change_epilog # accessible in interp as #<_[section]name> # start of tool length touchoff probe [EMCMOT] EMCMOT = motmod COMM_TIMEOUT = 1.0 BASE_PERIOD = 35000 SERVO_PERIOD = 1000000 # Hardware Abstraction Layer section -------------------------------------------------- [TASK] TASK = milltask CYCLE_TIME = 0.001 # Part program interpreter section -------------------------------------------- [HAL] HALFILE = 6040_Tool_sensor.hal HALFILE = tool-sensor.hal # Single file that is executed after the GUI has started. POSTGUI_HALFILE = gmoccapy_postgui.hal HALUI = halui # Trajectory planner section -------------------------------------------------- [HALUI] #No Content [TRAJ] COORDINATES = X Y Z LINEAR_UNITS = mm ANGULAR_UNITS = degree DEFAULT_LINEAR_VELOCITY = 29.0 MAX_LINEAR_VELOCITY = 29.0 POSITION_FILE = position.txt [EMCIO] EMCIO = io CYCLE_TIME = 0.100 # tool table file TOOL_TABLE = tool.tbl [KINS] KINEMATICS = trivkins coordinates=xyz JOINTS = 3 [AXIS_X] MAX_VELOCITY = 31 MAX_ACCELERATION = 220.0 MIN_LIMIT = -0.1 MAX_LIMIT = 370.0 [JOINT_0] TYPE = LINEAR HOME = 0.0 MIN_LIMIT = -0.1 MAX_LIMIT = 370.0 MAX_VELOCITY = 31 MAX_ACCELERATION = 220.0 STEPGEN_MAXACCEL = 500 SCALE = 319 FERROR = 1 MIN_FERROR = .25 HOME_OFFSET = -2 HOME_SEARCH_VEL = 31 HOME_LATCH_VEL = 1.500000 HOME_SEQUENCE = 1 [AXIS_Y] MAX_VELOCITY = 31 MAX_ACCELERATION = 220.0 MIN_LIMIT = -580 MAX_LIMIT = 1 [JOINT_1] TYPE = LINEAR HOME = 0.0 MIN_LIMIT = -580 MAX_LIMIT = 1 MAX_VELOCITY = 31 MAX_ACCELERATION = 220.0 STEPGEN_MAXACCEL = 500 SCALE = 320 FERROR = 1 MIN_FERROR = .25 HOME_OFFSET = 2 HOME_SEARCH_VEL = -31 HOME_LATCH_VEL = 5.500000 HOME_SEQUENCE = 2 [AXIS_Z] MAX_VELOCITY = 15 MAX_ACCELERATION = 200.0 MIN_LIMIT = -120.0 MAX_LIMIT = 0.001 [JOINT_2] TYPE = LINEAR HOME = 0 MIN_LIMIT = -120.0 MAX_LIMIT = 0.001 MAX_VELOCITY = 15 MAX_ACCELERATION = 200.0 STEPGEN_MAXACCEL = 500 SCALE = 400 FERROR = 1 MIN_FERROR = .25 HOME_OFFSET = 2 HOME_SEARCH_VEL = -29 HOME_LATCH_VEL = 1.500000 HOME_SEQUENCE = 0 # section for main IO controller parameters ----------------------------------- [TOOLSENSOR] X = 22 Y = -517 Z = -80 # abort change if no toolsensor contact after this probe distance MAXPROBE = -11 # this is not named TOOL_CHANGE_POSITION on purpose - canon uses it and will # interfere [CHANGE_POSITION] X = 22 Y = -517 Z = 0 # the Python plugins serves interpreter and task [PYTHON] PATH_PREPEND = python TOPLEVEL = python/toplevel.py LOG_LEVEL = 8 # Motion control section ------------------------------------------------------

my tool-sensor.hal is blank as it was the example off linuxcnc and had a button instead of the probe. But here it is.
Code:
net tool_sensor tool_sensor.btn_tool_sensor_sim net tool_sensor motion.probe-input net tool_sensor tool_sensor.led_tool_sensor

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

More
5 years 5 months ago #208078 by guido-52
Replied by guido-52 on topic LED panel light for probe
Has your problem already been solved?

I don't see a reference to the hal file in your ini file

I also had this problem and finally (with help from the forum) solved it as;

In the ini-file
- EMBED_TAB_COMMAND = gladevcp -x {XID} -H paneel.hal ./GLADE/paneel1.glade
(glade file in folder "GLADE")

connections in paneel.hal
(no reference to hal file in other hal's)

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

More
5 years 5 months ago #208159 by newbynobi
Replied by newbynobi on topic LED panel light for probe
That's exactly what I mentioned in my first post in this thread.
I did ask if the - H option is used and there is no reference in the inin file

Norbert

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

More
5 years 3 months ago - 5 years 3 months ago #214412 by IronBones
Replied by IronBones on topic LED panel light for probe
Maybe you can't change it at all. Often companies do not add such settings, although it seems to us that they should definitely be. It's like having a camping lantern and hoping that you can change its color.
Of course, I don't really understand these programs, and I'm still learning this. But I hope that the options that are written above worked. I'm even interested.
It also would be fantastic if you would add some photos of the result. I'm sure some people would like to see this. And I guess it looks pretty good.
Last edit: 5 years 3 months ago by IronBones.

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

More
5 years 3 months ago #214609 by andypugh
Replied by andypugh on topic LED panel light for probe
Ah, but this is Open Source software, where anything that is possible, is possible.

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

More
5 years 3 months ago #214625 by guido-52
Replied by guido-52 on topic LED panel light for probe
As I mentioned in my previous post, of course it is possible.
Hereby the two photos of the "led" with not activated and activated probe.

You report in the ini-file in which hal-file you will place the connection.

By me is it "paneel.hal" and in it the line "net probe-in => paneel1.probe" because in Glade I named the rectangle "probe".
 

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

Moderators: newbynobi, HansU
Time to create page: 0.074 seconds
Powered by Kunena Forum