disable home button while running
Bear in mind that you name the pyvcp pins.
When are you trying to connect the pin? Pyvcp pins don't exist until Axis is loaded, so they need to be in the postgui hal file.
If you can see the button that must mean Axis has loaded. Then you can look for the pin in machine->show hal config.
Please Log in or Create an account to join the conversation.
checked the ini and all are HOME = 0 and XYZ = 0 0 0
i removed the POSITION_FILE. no change.
if i home again, (any axis) from 1600 goes to 3200.000.
i didn't try again.
Thanks for any and all help )
MACHINE = EMC-MY-AXIS
# Debug level, 0 means no messages. See src/emc/nml_int/emcglb.h for others
#DEBUG = 0x7FFFFFFF
DEBUG = 0
# Sections for display options
[DISPLAY]
#pyvcp
PYVCP = pyvcp.xml
# Name of display program, e.g., xemc
DISPLAY = axis
# Cycle time, in seconds, that display will sleep between polls
CYCLE_TIME = 0.100
# Path to help file
HELP_FILE = doc/help.txt
# Initial display setting for position, RELATIVE or MACHINE
POSITION_OFFSET = RELATIVE
# Initial display setting for position, COMMANDED or ACTUAL
POSITION_FEEDBACK = ACTUAL
# Highest value that will be allowed for feed override, 1.0 = 100%
MAX_FEED_OVERRIDE = 2.5
MAX_SPINDLE_OVERRIDE = 1.0
MAX_LINEAR_VELOCITY = 2.5
DEFAULT_LINEAR_VELOCITY = .25
# Prefix to be used
PROGRAM_PREFIX = /home/emc2/emc2/
# Introductory graphic
INTRO_GRAPHIC = emc2.gif
INTRO_TIME = 5
EDITOR = gedit
TOOL_EDITOR = tooledit
INCREMENTS = 1 in, 0.1 in, 10 mil, 1 mil, 1mm, .1mm, 1/8000 in
[FILTER]
PROGRAM_EXTENSION = .NGC, .ngc, .png,.gif,.jpg Grayscale Depth Image
PROGRAM_EXTENSION = .py Py,thon Script
png = image-to-gcode
gif = image-to-gcode
jpg = image-to-gcode
py = python
# Task controller section
[TASK]
# Name of task controller program, e.g., milltask
TASK = milltask
# Cycle time, in seconds, that task controller will sleep between polls
CYCLE_TIME = 0.001
# Part program interpreter section
[RS274NGC]
# File containing interpreter variables
PARAMETER_FILE = sim.var
# Motion control section
[EMCMOT]
EMCMOT = motmod
# Timeout for comm to emcmot, in seconds
COMM_TIMEOUT = 1.0
# Interval between tries to emcmot, in seconds
COMM_WAIT = 0.010
# BASE_PERIOD is unused in this configuration but specified in core_sim.hal
BASE_PERIOD = 0
# Servo task period, in nano-seconds
SERVO_PERIOD = 1000000
# Hardware Abstraction Layer section
[HAL]
# The run script first uses halcmd to execute any HALFILE
# files, and then to execute any individual HALCMD commands.
#
# list of hal config files to run through halcmd
# files are executed in the order in which they appear
HALFILE = core.hal
#HALFILE = core_sim.hal
#HALFILE = axis_manualtoolchange.hal
#HALFILE = simulated_home.hal
#HALFILE = gamepad.hal
# list of halcmd commands to execute
# commands are executed in the order in which they appear
#HALCMD = save neta
# Single file that is executed after the GUI has started. Only supported by
# AXIS at this time (only AXIS creates a HAL component of its own)
#POSTGUI_HALFILE = test_postgui.hal
#HALUI = halui
# Trajectory planner section
[TRAJ]
AXES = 3
COORDINATES = X Y Z
HOME = 0 0 0
LINEAR_UNITS = inch
ANGULAR_UNITS = degree
CYCLE_TIME = 0.010
DEFAULT_VELOCITY = 1.9
#POSITION_FILE = position.txt
MAX_LINEAR_VELOCITY = 1.9
Please Log in or Create an account to join the conversation.
Did you type it as home_all in the XML file?
Bear in mind that you name the pyvcp pins.
When are you trying to connect the pin? Pyvcp pins don't exist until Axis is loaded, so they need to be in the postgui hal file.
If you can see the button that must mean Axis has loaded. Then you can look for the pin in machine->show hal config.
Thanks, but i can't get pass the homing XYZ. 1 homr all go to 1600, 2nd home they all go to 3200....6400..
..so on so on
never zeros
Please Log in or Create an account to join the conversation.
"pyvcp.home-all doesn't exist" in the debug wind
so i disabled net connection i made and try to zero "any" axis
Please Log in or Create an account to join the conversation.
Are you in "Machine" coordinates?Thanks, but i can't get pass the homing XYZ. 1 homr all go to 1600, 2nd home they all go to 3200....6400..
..so on so on
never zeros
I suspect that you have an offset in the G54 coordinate system (of 1600) and that every time you home it (with no actual axis movement) that is the required offset to set the home.
Are you homing, or touching off?
The suggestion on the IRC is to delete the .var file.
Please Log in or Create an account to join the conversation.
deleting the var file...no change. and i'm using home not g54.
Thanks
tried using touchoff and error "can't use mdi til homed"
Please Log in or Create an account to join the conversation.
this one also(simulated_home.hal). homes now
THANKS
Please Log in or Create an account to join the conversation.
xyz z goes to 1600
zyx x goes to 1600
yzx x ' '1600
yxz z ' '1600
i deleted the var and var.bak
no change
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.