×
Forum Header
XYUV hotwire configuration
10 Sep 2015 00:40 #62339
by fannlow
Replied by fannlow on topic XYUV hotwire configuration
I just had the time to play with this.
I was using touch-off and it ask for some value.
so I tried to insert some values in it.
X touch-off = 5mm
Y touch-off = -100mm
U touch-off = 5mm
V touch-off = -100mm
G54 jumps to these values instead
Gcode is as follows to cut a SQUARE (50mm,50mm) and the hotwire is now just 2mm away from my block.
G1 F800 X47 U47 (cuts into the block to 50mm inside block)
G1 F800 Y-50 V-50 (cuts down the block to -50mm inside block)
G1 F800 X3 U3 (cuts away from the block 50mm still inside block)
G1 F800 Y0 V0 (cuts up the block to 0mm inside block)
G1 F800 X0 U0 (exits block to the X/U 5mm touch-off point)
am I understanding this correctly? or am I missing something?
because this ain't what my machine is doing though....
==========
another question I have is, after using touch-off, how do I ask my machine to go back to machine zero instead of touch-off zero?
confused right here...
==========
then I have another issue with either the gui or some here with the hal or ini...
1. I don't know where to place my U and V axis.. in the hal or ini? do I need to change something?
- i am still using Z and A axis...
2. while still caught in the Z and A axis of the original 4 axis supplied by the stepConf, my A axis is always in 360 degrees...
- even though I have copied my [Axis = 2] in the .ini file and replace the [Axis = 3] part, which I assume is now linear instead of radial...
- not sure how to confirm if my changes are correct, but I definitely see my machine run A as in degrees and not linear..
- this is also confirmed when i place the touch-off for A axis, it simply won't let me do the touch-off for some reason..
- running Gcode after touch-off success for A axis, will result in A axis moving first before Z axis.. when the code is F800 Z-100 A-100 (not sure why)?
3. I must be missing something in the HAL and INI settings or some other places where this confusion is happening...
- is there any where I can script through the HAL or INI so I can write or code what I need the machine to perform so that it performs right?
- I tried to re-write the HAL and INI a few times, but it always ends up with the linuxCNC crashing at program startup... unsure why.. but something must be INCORRECT.. hahaha >.<"
thanks for all the help... will continue to need more help =)
I was using touch-off and it ask for some value.
so I tried to insert some values in it.
X touch-off = 5mm
Y touch-off = -100mm
U touch-off = 5mm
V touch-off = -100mm
G54 jumps to these values instead
Gcode is as follows to cut a SQUARE (50mm,50mm) and the hotwire is now just 2mm away from my block.
G1 F800 X47 U47 (cuts into the block to 50mm inside block)
G1 F800 Y-50 V-50 (cuts down the block to -50mm inside block)
G1 F800 X3 U3 (cuts away from the block 50mm still inside block)
G1 F800 Y0 V0 (cuts up the block to 0mm inside block)
G1 F800 X0 U0 (exits block to the X/U 5mm touch-off point)
am I understanding this correctly? or am I missing something?
because this ain't what my machine is doing though....
==========
another question I have is, after using touch-off, how do I ask my machine to go back to machine zero instead of touch-off zero?
confused right here...
==========
then I have another issue with either the gui or some here with the hal or ini...
1. I don't know where to place my U and V axis.. in the hal or ini? do I need to change something?
- i am still using Z and A axis...
2. while still caught in the Z and A axis of the original 4 axis supplied by the stepConf, my A axis is always in 360 degrees...
- even though I have copied my [Axis = 2] in the .ini file and replace the [Axis = 3] part, which I assume is now linear instead of radial...
- not sure how to confirm if my changes are correct, but I definitely see my machine run A as in degrees and not linear..
- this is also confirmed when i place the touch-off for A axis, it simply won't let me do the touch-off for some reason..
- running Gcode after touch-off success for A axis, will result in A axis moving first before Z axis.. when the code is F800 Z-100 A-100 (not sure why)?
3. I must be missing something in the HAL and INI settings or some other places where this confusion is happening...
- is there any where I can script through the HAL or INI so I can write or code what I need the machine to perform so that it performs right?
- I tried to re-write the HAL and INI a few times, but it always ends up with the linuxCNC crashing at program startup... unsure why.. but something must be INCORRECT.. hahaha >.<"
thanks for all the help... will continue to need more help =)
Please Log in or Create an account to join the conversation.
10 Sep 2015 05:12 #62355
by cncbasher
Replied by cncbasher on topic XYUV hotwire configuration
2 questions
1 answer
1 what exactly is your machine doing that is wrong ?
2 archive your config folder and attach here
include your gcode.ngc file , so we can check that all is correct
1 check your ini file for angle rather than it set for linear
if thats the case then change to suit , and try again
once we know what is going wrong and see your files , no doubt all will become clear
once the machine is homes and touch off is done their is no real need to go back to any position
all you need to do is either re-home the machine , taking that home switches are fitted .
or for the next block manually move or jog the axis to a given start point and touch off again
1 answer
1 what exactly is your machine doing that is wrong ?
2 archive your config folder and attach here
include your gcode.ngc file , so we can check that all is correct
1 check your ini file for angle rather than it set for linear
if thats the case then change to suit , and try again
once we know what is going wrong and see your files , no doubt all will become clear
once the machine is homes and touch off is done their is no real need to go back to any position
all you need to do is either re-home the machine , taking that home switches are fitted .
or for the next block manually move or jog the axis to a given start point and touch off again
Please Log in or Create an account to join the conversation.
11 Sep 2015 02:38 #62414
by fannlow
Replied by fannlow on topic XYUV hotwire configuration
Let me run the machine later today, and see exactly what I meant by not running as expected...
Will attach some pictures as well.
For the gCode.ngc and config folder, I will attach them later today.
==========
I have yet to test on the horizontal rotary and vertical turn table.
reason is because I don't have any cam software or post processing software to do this..
I have checked in with a few foam software vendors and they don't currently offer these rotary features yet.
If anyone has come across this cam software, either with license, demo or freeware, kindly let me know.
I would be willing to try out something that runs for my system.
thanks for the help =)
Will attach some pictures as well.
For the gCode.ngc and config folder, I will attach them later today.
==========
I have yet to test on the horizontal rotary and vertical turn table.
reason is because I don't have any cam software or post processing software to do this..
I have checked in with a few foam software vendors and they don't currently offer these rotary features yet.
If anyone has come across this cam software, either with license, demo or freeware, kindly let me know.
I would be willing to try out something that runs for my system.
thanks for the help =)
Please Log in or Create an account to join the conversation.
11 Sep 2015 15:33 #62437
by cncbasher
Replied by cncbasher on topic XYUV hotwire configuration
in most cases for foam cutting you will need to modify a post processor for your cam program
to suit your needs .
using either vertical or horizontal makes no difference .
devcam is probably the best , which i believe your using
so modifying the post processor is a simple txt file to edit
to suit your needs .
using either vertical or horizontal makes no difference .
devcam is probably the best , which i believe your using
so modifying the post processor is a simple txt file to edit
Please Log in or Create an account to join the conversation.
12 Sep 2015 00:24 #62475
by fannlow
Replied by fannlow on topic XYUV hotwire configuration
quoting CNCBASHER:
"in most cases for foam cutting you will need to modify a post processor for your cam program
to suit your needs .
using either vertical or horizontal makes no difference .
devcam is probably the best , which i believe your using
so modifying the post processor is a simple txt file to edit"
devFoam uses a post processor called the planetCNC
from the LinuxCNC Gcode References, it seems to me pretty much everything runs the same as with other Gcode...
is there anything I should lookout for?
==========
devCam Pro ? (i use devFoam Pro demo for testing purposes)
I looked into the software for linear cutting and so far good job to say the least.
Kerf and everything else is easy to add onto the cut, even a 2-axis or 4-axis with the ability to choose the axis prior to doing any generation of codes so on..
however, as I spoke to the devFoam Pro representatives, they told me they do not currently support rotary.
not sure if this is the same cam software we are talking about?
i have attached my email conversation with devFoam Pro though..
==========
so if its different, where should I go about modifying this post processor in devCam?
thanks
"in most cases for foam cutting you will need to modify a post processor for your cam program
to suit your needs .
using either vertical or horizontal makes no difference .
devcam is probably the best , which i believe your using
so modifying the post processor is a simple txt file to edit"
devFoam uses a post processor called the planetCNC
from the LinuxCNC Gcode References, it seems to me pretty much everything runs the same as with other Gcode...
is there anything I should lookout for?
==========
devCam Pro ? (i use devFoam Pro demo for testing purposes)
I looked into the software for linear cutting and so far good job to say the least.
Kerf and everything else is easy to add onto the cut, even a 2-axis or 4-axis with the ability to choose the axis prior to doing any generation of codes so on..
however, as I spoke to the devFoam Pro representatives, they told me they do not currently support rotary.
not sure if this is the same cam software we are talking about?
i have attached my email conversation with devFoam Pro though..
==========
so if its different, where should I go about modifying this post processor in devCam?
thanks
Please Log in or Create an account to join the conversation.
14 Sep 2015 21:49 #62565
by fannlow
Replied by fannlow on topic XYUV hotwire configuration
Hi Guys,
so i am attaching my config folder.
within it are a few files.
I hope to shed some light to this and see what can be done.
many thanks!
so i am attaching my config folder.
within it are a few files.
I hope to shed some light to this and see what can be done.
many thanks!
Please Log in or Create an account to join the conversation.
29 Sep 2015 00:51 #63154
by fannlow
Replied by fannlow on topic XYUV hotwire configuration
Hi guys,
am trying to get the XY/UV in correct working linear motion.
and secondly, trying to fix the graphic plot of the XY/UV coordination.
the other day, i tried the touch-off .
as the machine was and still in in XYZA configuration.
X/Z horizontal, Y/A Vertical
after touch-off, I used the following Gcode to test.
G1 F500 Y-100 A-100
i was expecting it to move together as usual, but for some reason, A moved and Y didn't.
one possible reason I could think off, is I didn't touch-off for Y or something causing A to move instead of together.
the next thing I wanna learn is how to clear off touch-off so I can home the machine.
currently the hardware HOME isn't working... I have it, but not yet connect it to the board...
so I am still using software to HOME
If I am not able to clear off TOUCH-OFF, the following command will go to TOUCH-OFF and not the HOME position.
G1 F500 X0 Z0 Y0 A0
I am trying to write and edit the linuxCNC into a multi axis hotwire foam machine...
but still am not sure where else I can go look for more information...
thanks for all the help I can get.
cause now, everything is very manual...
including the G-codes...
am trying to get the XY/UV in correct working linear motion.
and secondly, trying to fix the graphic plot of the XY/UV coordination.
the other day, i tried the touch-off .
as the machine was and still in in XYZA configuration.
X/Z horizontal, Y/A Vertical
after touch-off, I used the following Gcode to test.
G1 F500 Y-100 A-100
i was expecting it to move together as usual, but for some reason, A moved and Y didn't.
one possible reason I could think off, is I didn't touch-off for Y or something causing A to move instead of together.
the next thing I wanna learn is how to clear off touch-off so I can home the machine.
currently the hardware HOME isn't working... I have it, but not yet connect it to the board...
so I am still using software to HOME
If I am not able to clear off TOUCH-OFF, the following command will go to TOUCH-OFF and not the HOME position.
G1 F500 X0 Z0 Y0 A0
I am trying to write and edit the linuxCNC into a multi axis hotwire foam machine...
but still am not sure where else I can go look for more information...
thanks for all the help I can get.
cause now, everything is very manual...
including the G-codes...
Please Log in or Create an account to join the conversation.
29 Sep 2015 01:35 #63155
by fannlow
Replied by fannlow on topic XYUV hotwire configuration
Attaching the "edited" version of the linear XY/UV 4-axis here.
When I compare to those other XY/UV ini's, they have
GEOMETRY = XY;UV
I do not have this. is this an issue or what does this do?
==========
# Generated by stepconf 1.1 at Wed Aug 19 22:58:49 2015
# If you make changes to this file, they will be
# overwritten when you run stepconf again
[EMC]
MACHINE = nai-hotwire
DEBUG = 0
[DISPLAY]
DISPLAY = axis
EDITOR = gedit
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
ARCDIVISION = 64
GRIDS = 10mm 20mm 50mm 100mm 1in 2in 5in 10in
MAX_FEED_OVERRIDE = 1.2
MIN_SPINDLE_OVERRIDE = 0.5
MAX_SPINDLE_OVERRIDE = 1.2
DEFAULT_LINEAR_VELOCITY = 50.80
MIN_LINEAR_VELOCITY = 0
MAX_LINEAR_VELOCITY = 508.00
DEFAULT_ANGULAR_VELOCITY = 36.00
MIN_ANGULAR_VELOCITY = 0
MAX_ANGULAR_VELOCITY = 360.00
INTRO_GRAPHIC = linuxcnc.gif
INTRO_TIME = 5
PROGRAM_PREFIX = /home/nai-hotwire/linuxcnc/nc_files
INCREMENTS = 5mm 1mm .5mm .1mm .05mm .01mm .005mm
[FILTER]
PROGRAM_EXTENSION = .png,.gif,.jpg Greyscale Depth Image
PROGRAM_EXTENSION = .py Python Script
png = image-to-gcode
gif = image-to-gcode
jpg = image-to-gcode
py = python
[TASK]
TASK = milltask
CYCLE_TIME = 0.010
[RS274NGC]
PARAMETER_FILE = linuxcnc.var
[EMCMOT]
EMCMOT = motmod
COMM_TIMEOUT = 1.0
COMM_WAIT = 0.010
BASE_PERIOD = 47000
SERVO_PERIOD = 1000000
[HAL]
HALFILE = nai-hotwire.hal
HALFILE = custom.hal
POSTGUI_HALFILE = custom_postgui.hal
[TRAJ]
AXES = 8
COORDINATES = X Y U V
LINEAR_UNITS = mm
ANGULAR_UNITS = degree
CYCLE_TIME = 0.010
DEFAULT_VELOCITY = 36.00
MAX_VELOCITY = 508.00
[EMCIO]
EMCIO = io
CYCLE_TIME = 0.100
TOOL_TABLE = tool.tbl
# X-AXIS [HORIZONTAL]
[AXIS_0]
TYPE = LINEAR
HOME = 0.0
MAX_VELOCITY = 168.372340426
MAX_ACCELERATION = 1016.0
STEPGEN_MAXACCEL = 1270.0
SCALE = 120.048019208
FERROR = 1
MIN_FERROR = .25
MIN_LIMIT = -0.001
MAX_LIMIT = 2974.6
HOME_OFFSET = 0.0
# Y-AXIS [VERTICAL - ON X]
[AXIS_1]
TYPE = LINEAR
HOME = 0.0
MAX_VELOCITY = 25.670212766
MAX_ACCELERATION = 1016.0
STEPGEN_MAXACCEL = 1270.0
SCALE = 787.401574803
FERROR = 1
MIN_FERROR = .25
MIN_LIMIT = -1550.0
MAX_LIMIT = 0.001
HOME_OFFSET = 0.0
# U-AXIS [HORIZONTAL - OPPOSITE OF X]
[AXIS_6]
TYPE = LINEAR
HOME = 0.0
MAX_VELOCITY = 168.372340426
MAX_ACCELERATION = 1016.0
STEPGEN_MAXACCEL = 1270.0
SCALE = 120.048019208
FERROR = 1
MIN_FERROR = .25
MIN_LIMIT = -0.001
MAX_LIMIT = 2974.6
HOME_OFFSET = 0.0
# V-AXIS [VERTICAL - ON U]
[AXIS_7]
TYPE = LINEAR
HOME = 0.0
MAX_VELOCITY = 25.670212766
MAX_ACCELERATION = 1016.0
STEPGEN_MAXACCEL = 1270.0
SCALE = 787.401574803
FERROR = 1
MIN_FERROR = .25
MIN_LIMIT = -1550.0
MAX_LIMIT = 0.001
HOME_OFFSET = 0.0
==========
thanks
When I compare to those other XY/UV ini's, they have
GEOMETRY = XY;UV
I do not have this. is this an issue or what does this do?
==========
# Generated by stepconf 1.1 at Wed Aug 19 22:58:49 2015
# If you make changes to this file, they will be
# overwritten when you run stepconf again
[EMC]
MACHINE = nai-hotwire
DEBUG = 0
[DISPLAY]
DISPLAY = axis
EDITOR = gedit
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
ARCDIVISION = 64
GRIDS = 10mm 20mm 50mm 100mm 1in 2in 5in 10in
MAX_FEED_OVERRIDE = 1.2
MIN_SPINDLE_OVERRIDE = 0.5
MAX_SPINDLE_OVERRIDE = 1.2
DEFAULT_LINEAR_VELOCITY = 50.80
MIN_LINEAR_VELOCITY = 0
MAX_LINEAR_VELOCITY = 508.00
DEFAULT_ANGULAR_VELOCITY = 36.00
MIN_ANGULAR_VELOCITY = 0
MAX_ANGULAR_VELOCITY = 360.00
INTRO_GRAPHIC = linuxcnc.gif
INTRO_TIME = 5
PROGRAM_PREFIX = /home/nai-hotwire/linuxcnc/nc_files
INCREMENTS = 5mm 1mm .5mm .1mm .05mm .01mm .005mm
[FILTER]
PROGRAM_EXTENSION = .png,.gif,.jpg Greyscale Depth Image
PROGRAM_EXTENSION = .py Python Script
png = image-to-gcode
gif = image-to-gcode
jpg = image-to-gcode
py = python
[TASK]
TASK = milltask
CYCLE_TIME = 0.010
[RS274NGC]
PARAMETER_FILE = linuxcnc.var
[EMCMOT]
EMCMOT = motmod
COMM_TIMEOUT = 1.0
COMM_WAIT = 0.010
BASE_PERIOD = 47000
SERVO_PERIOD = 1000000
[HAL]
HALFILE = nai-hotwire.hal
HALFILE = custom.hal
POSTGUI_HALFILE = custom_postgui.hal
[TRAJ]
AXES = 8
COORDINATES = X Y U V
LINEAR_UNITS = mm
ANGULAR_UNITS = degree
CYCLE_TIME = 0.010
DEFAULT_VELOCITY = 36.00
MAX_VELOCITY = 508.00
[EMCIO]
EMCIO = io
CYCLE_TIME = 0.100
TOOL_TABLE = tool.tbl
# X-AXIS [HORIZONTAL]
[AXIS_0]
TYPE = LINEAR
HOME = 0.0
MAX_VELOCITY = 168.372340426
MAX_ACCELERATION = 1016.0
STEPGEN_MAXACCEL = 1270.0
SCALE = 120.048019208
FERROR = 1
MIN_FERROR = .25
MIN_LIMIT = -0.001
MAX_LIMIT = 2974.6
HOME_OFFSET = 0.0
# Y-AXIS [VERTICAL - ON X]
[AXIS_1]
TYPE = LINEAR
HOME = 0.0
MAX_VELOCITY = 25.670212766
MAX_ACCELERATION = 1016.0
STEPGEN_MAXACCEL = 1270.0
SCALE = 787.401574803
FERROR = 1
MIN_FERROR = .25
MIN_LIMIT = -1550.0
MAX_LIMIT = 0.001
HOME_OFFSET = 0.0
# U-AXIS [HORIZONTAL - OPPOSITE OF X]
[AXIS_6]
TYPE = LINEAR
HOME = 0.0
MAX_VELOCITY = 168.372340426
MAX_ACCELERATION = 1016.0
STEPGEN_MAXACCEL = 1270.0
SCALE = 120.048019208
FERROR = 1
MIN_FERROR = .25
MIN_LIMIT = -0.001
MAX_LIMIT = 2974.6
HOME_OFFSET = 0.0
# V-AXIS [VERTICAL - ON U]
[AXIS_7]
TYPE = LINEAR
HOME = 0.0
MAX_VELOCITY = 25.670212766
MAX_ACCELERATION = 1016.0
STEPGEN_MAXACCEL = 1270.0
SCALE = 787.401574803
FERROR = 1
MIN_FERROR = .25
MIN_LIMIT = -1550.0
MAX_LIMIT = 0.001
HOME_OFFSET = 0.0
==========
thanks
Please Log in or Create an account to join the conversation.
29 Sep 2015 01:40 #63156
by fannlow
Replied by fannlow on topic XYUV hotwire configuration
attached is my corresponding HAL file.
I changed only the AXIS_# to match with the .ini file.
however, under each axis paragraph, there is a
net xpos-cmd...
net xpos-fb...
net xstep...
net xdir...
net xenable axis.0....
and there's the y, z, a..
I would like to know if I need to change the z and a to match u and v?
==========
# Generated by stepconf 1.1 at Wed Aug 19 22:58:49 2015
# If you make changes to this file, they will be
# overwritten when you run stepconf again
loadrt trivkins
loadrt [EMCMOT]EMCMOT base_period_nsec=[EMCMOT]BASE_PERIOD servo_period_nsec=[EMCMOT]SERVO_PERIOD num_joints=[TRAJ]AXES
loadrt probe_parport
loadrt hal_parport cfg="0x378 out"
setp parport.0.reset-time 3500
loadrt stepgen step_type=0,0,0,0
addf parport.0.read base-thread
addf stepgen.make-pulses base-thread
addf parport.0.write base-thread
addf parport.0.reset base-thread
addf stepgen.capture-position servo-thread
addf motion-command-handler servo-thread
addf motion-controller servo-thread
addf stepgen.update-freq servo-thread
net spindle-cmd <= motion.spindle-speed-out
net spindle-at-speed => motion.spindle-at-speed
setp parport.0.pin-02-out-invert 1
net xstep => parport.0.pin-02-out
setp parport.0.pin-02-out-reset 1
net xdir => parport.0.pin-03-out
setp parport.0.pin-04-out-invert 1
net ystep => parport.0.pin-04-out
setp parport.0.pin-04-out-reset 1
setp parport.0.pin-05-out-invert 1
net ydir => parport.0.pin-05-out
setp parport.0.pin-06-out-invert 1
net zstep => parport.0.pin-06-out
setp parport.0.pin-06-out-reset 1
setp parport.0.pin-07-out-invert 1
net zdir => parport.0.pin-07-out
setp parport.0.pin-08-out-invert 1
net astep => parport.0.pin-08-out
setp parport.0.pin-08-out-reset 1
setp parport.0.pin-09-out-invert 1
net adir => parport.0.pin-09-out
setp stepgen.0.position-scale [AXIS_0]SCALE
setp stepgen.0.steplen 1
setp stepgen.0.stepspace 0
setp stepgen.0.dirhold 70000
setp stepgen.0.dirsetup 70000
setp stepgen.0.maxaccel [AXIS_0]STEPGEN_MAXACCEL
net xpos-cmd axis.0.motor-pos-cmd => stepgen.0.position-cmd
net xpos-fb stepgen.0.position-fb => axis.0.motor-pos-fb
net xstep <= stepgen.0.step
net xdir <= stepgen.0.dir
net xenable axis.0.amp-enable-out => stepgen.0.enable
setp stepgen.1.position-scale [AXIS_1]SCALE
setp stepgen.1.steplen 1
setp stepgen.1.stepspace 0
setp stepgen.1.dirhold 70000
setp stepgen.1.dirsetup 70000
setp stepgen.1.maxaccel [AXIS_1]STEPGEN_MAXACCEL
net ypos-cmd axis.1.motor-pos-cmd => stepgen.1.position-cmd
net ypos-fb stepgen.1.position-fb => axis.1.motor-pos-fb
net ystep <= stepgen.1.step
net ydir <= stepgen.1.dir
net yenable axis.1.amp-enable-out => stepgen.1.enable
setp stepgen.2.position-scale [AXIS_6]SCALE
setp stepgen.2.steplen 1
setp stepgen.2.stepspace 0
setp stepgen.2.dirhold 70000
setp stepgen.2.dirsetup 70000
setp stepgen.2.maxaccel [AXIS_2]STEPGEN_MAXACCEL
net zpos-cmd axis.2.motor-pos-cmd => stepgen.2.position-cmd
net zpos-fb stepgen.2.position-fb => axis.2.motor-pos-fb
net zstep <= stepgen.2.step
net zdir <= stepgen.2.dir
net zenable axis.2.amp-enable-out => stepgen.2.enable
setp stepgen.3.position-scale [AXIS_7]SCALE
setp stepgen.3.steplen 1
setp stepgen.3.stepspace 0
setp stepgen.3.dirhold 70000
setp stepgen.3.dirsetup 70000
setp stepgen.3.maxaccel [AXIS_3]STEPGEN_MAXACCEL
net apos-cmd axis.3.motor-pos-cmd => stepgen.3.position-cmd
net apos-fb stepgen.3.position-fb => axis.3.motor-pos-fb
net astep <= stepgen.3.step
net adir <= stepgen.3.dir
net aenable axis.3.amp-enable-out => stepgen.3.enable
net estop-out <= iocontrol.0.user-enable-out
net estop-out => iocontrol.0.emc-enable-in
loadusr -W hal_manualtoolchange
net tool-change iocontrol.0.tool-change => hal_manualtoolchange.change
net tool-changed iocontrol.0.tool-changed <= hal_manualtoolchange.changed
net tool-number iocontrol.0.tool-prep-number => hal_manualtoolchange.number
net tool-prepare-loopback iocontrol.0.tool-prepare => iocontrol.0.tool-prepared
==========
I changed only the AXIS_# to match with the .ini file.
however, under each axis paragraph, there is a
net xpos-cmd...
net xpos-fb...
net xstep...
net xdir...
net xenable axis.0....
and there's the y, z, a..
I would like to know if I need to change the z and a to match u and v?
==========
# Generated by stepconf 1.1 at Wed Aug 19 22:58:49 2015
# If you make changes to this file, they will be
# overwritten when you run stepconf again
loadrt trivkins
loadrt [EMCMOT]EMCMOT base_period_nsec=[EMCMOT]BASE_PERIOD servo_period_nsec=[EMCMOT]SERVO_PERIOD num_joints=[TRAJ]AXES
loadrt probe_parport
loadrt hal_parport cfg="0x378 out"
setp parport.0.reset-time 3500
loadrt stepgen step_type=0,0,0,0
addf parport.0.read base-thread
addf stepgen.make-pulses base-thread
addf parport.0.write base-thread
addf parport.0.reset base-thread
addf stepgen.capture-position servo-thread
addf motion-command-handler servo-thread
addf motion-controller servo-thread
addf stepgen.update-freq servo-thread
net spindle-cmd <= motion.spindle-speed-out
net spindle-at-speed => motion.spindle-at-speed
setp parport.0.pin-02-out-invert 1
net xstep => parport.0.pin-02-out
setp parport.0.pin-02-out-reset 1
net xdir => parport.0.pin-03-out
setp parport.0.pin-04-out-invert 1
net ystep => parport.0.pin-04-out
setp parport.0.pin-04-out-reset 1
setp parport.0.pin-05-out-invert 1
net ydir => parport.0.pin-05-out
setp parport.0.pin-06-out-invert 1
net zstep => parport.0.pin-06-out
setp parport.0.pin-06-out-reset 1
setp parport.0.pin-07-out-invert 1
net zdir => parport.0.pin-07-out
setp parport.0.pin-08-out-invert 1
net astep => parport.0.pin-08-out
setp parport.0.pin-08-out-reset 1
setp parport.0.pin-09-out-invert 1
net adir => parport.0.pin-09-out
setp stepgen.0.position-scale [AXIS_0]SCALE
setp stepgen.0.steplen 1
setp stepgen.0.stepspace 0
setp stepgen.0.dirhold 70000
setp stepgen.0.dirsetup 70000
setp stepgen.0.maxaccel [AXIS_0]STEPGEN_MAXACCEL
net xpos-cmd axis.0.motor-pos-cmd => stepgen.0.position-cmd
net xpos-fb stepgen.0.position-fb => axis.0.motor-pos-fb
net xstep <= stepgen.0.step
net xdir <= stepgen.0.dir
net xenable axis.0.amp-enable-out => stepgen.0.enable
setp stepgen.1.position-scale [AXIS_1]SCALE
setp stepgen.1.steplen 1
setp stepgen.1.stepspace 0
setp stepgen.1.dirhold 70000
setp stepgen.1.dirsetup 70000
setp stepgen.1.maxaccel [AXIS_1]STEPGEN_MAXACCEL
net ypos-cmd axis.1.motor-pos-cmd => stepgen.1.position-cmd
net ypos-fb stepgen.1.position-fb => axis.1.motor-pos-fb
net ystep <= stepgen.1.step
net ydir <= stepgen.1.dir
net yenable axis.1.amp-enable-out => stepgen.1.enable
setp stepgen.2.position-scale [AXIS_6]SCALE
setp stepgen.2.steplen 1
setp stepgen.2.stepspace 0
setp stepgen.2.dirhold 70000
setp stepgen.2.dirsetup 70000
setp stepgen.2.maxaccel [AXIS_2]STEPGEN_MAXACCEL
net zpos-cmd axis.2.motor-pos-cmd => stepgen.2.position-cmd
net zpos-fb stepgen.2.position-fb => axis.2.motor-pos-fb
net zstep <= stepgen.2.step
net zdir <= stepgen.2.dir
net zenable axis.2.amp-enable-out => stepgen.2.enable
setp stepgen.3.position-scale [AXIS_7]SCALE
setp stepgen.3.steplen 1
setp stepgen.3.stepspace 0
setp stepgen.3.dirhold 70000
setp stepgen.3.dirsetup 70000
setp stepgen.3.maxaccel [AXIS_3]STEPGEN_MAXACCEL
net apos-cmd axis.3.motor-pos-cmd => stepgen.3.position-cmd
net apos-fb stepgen.3.position-fb => axis.3.motor-pos-fb
net astep <= stepgen.3.step
net adir <= stepgen.3.dir
net aenable axis.3.amp-enable-out => stepgen.3.enable
net estop-out <= iocontrol.0.user-enable-out
net estop-out => iocontrol.0.emc-enable-in
loadusr -W hal_manualtoolchange
net tool-change iocontrol.0.tool-change => hal_manualtoolchange.change
net tool-changed iocontrol.0.tool-changed <= hal_manualtoolchange.changed
net tool-number iocontrol.0.tool-prep-number => hal_manualtoolchange.number
net tool-prepare-loopback iocontrol.0.tool-prepare => iocontrol.0.tool-prepared
==========
Please Log in or Create an account to join the conversation.
29 Sep 2015 18:40 - 29 Sep 2015 19:23 #63204
by cncbasher
Replied by cncbasher on topic XYUV hotwire configuration
yes change y & z in your hal file
in your ini make the axis number's 7 & 8 ( axi's are numbered from 0 to 9 ) and in order are xyzabcuvw
then change the corresponding axis numbers to 7 & 8 in your hal file
iv'e modified the files as you posted earlier , although i have not had a chance to test them
so please ask if you find an error .
in your ini make the axis number's 7 & 8 ( axi's are numbered from 0 to 9 ) and in order are xyzabcuvw
then change the corresponding axis numbers to 7 & 8 in your hal file
iv'e modified the files as you posted earlier , although i have not had a chance to test them
so please ask if you find an error .
Last edit: 29 Sep 2015 19:23 by cncbasher.
The following user(s) said Thank You: fannlow
Please Log in or Create an account to join the conversation.
Time to create page: 0.212 seconds