Re: [Emc-users] estop writes to toolchange pin out? more testing

2007-06-15 Thread Dale
Oooops! forgot, the Machine On button also should not cause any machine 
motion. That is one function and only one function, to turn on the 
machine, NOT to cause any motion!

Alfred Smart wrote:
>   I have done more testing and found that when I put the machine in 
> estop it jumps to the next line of code to be executed.
> Then when I bring it out of estop and push the machine on button it 
> takes off to the next instruction and not finishing the previous line of 
> code,it could be a rapid move!
> If the next line of code happened to be a tool change than the machine 
> takes off without spindle rotation because of my relay logic is still 
> waiting for a toolchange but the axis still move.
> Abort fixes the trouble but its one more thing to remember to do to stay 
> out of trouble.
> It would be nice if abort was a must do or automatically done with 
> machine on.
> is this everyone's problem or is it something I'm doing
> She's a runaway!
>  
> 
> 
> 
> 
> -
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> 
> 
> 
> 
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] estop writes to toolchange pin out? more testing

2007-06-15 Thread Dale
Sorry to be so late in responding to this. When a machine is put in an 
E-stop condition (E = Emergancy) it's because there was some kind of 
problem or isbeing used in a normal shutdown procedure. No matter, 
coming out of E-stop the machine should not move anything or try to 
complete any function at all!!! That behavior could be very dangerous!

Dale

Alfred Smart wrote:
>   I have done more testing and found that when I put the machine in 
> estop it jumps to the next line of code to be executed.
> Then when I bring it out of estop and push the machine on button it 
> takes off to the next instruction and not finishing the previous line of 
> code,it could be a rapid move!
> If the next line of code happened to be a tool change than the machine 
> takes off without spindle rotation because of my relay logic is still 
> waiting for a toolchange but the axis still move.
> Abort fixes the trouble but its one more thing to remember to do to stay 
> out of trouble.
> It would be nice if abort was a must do or automatically done with 
> machine on.
> is this everyone's problem or is it something I'm doing
> She's a runaway!
>  
> 
> 
> 
> 
> -
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> 
> 
> 
> 
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] estop writes to toolchange pin out? more testing

2007-05-24 Thread Jeff Epler
Please make sure you are running the latest version of emc, which is
currently emc 2.1.5.  It includes "fix for bug 1701900 - spindle does
not turn off when going into machine-off state".

Information about changes in each release:
http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Released
How to install updates using the Ubuntu update manager:
http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?InstallingUpdates

Jeff

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] estop writes to toolchange pin out? more testing

2007-05-23 Thread Alfred Smart

The only difference is I us hardware estop force estop sense low, and when I 
release my estop button ,estop sense goes high and then I turn the machine on 
through the gui halui and off she goes ,I'm running EMC2.6.15 halui_halvcp 
configs My (standard pinout) file is below your response "Jon Elson responded 
and said he has seen this behavior" It happens every time for me no matter what 
GUI I use I still haven't wired my drives up  Also when I call for a toolchange 
M6 T5 the spindle signal doesn't drop ,my relay logic stops my spindle and 
coolant for me but I assumed that this signal got dropped when requesting a 
toolchange?





>Jeff Epler
>Wed, 23 May 2007 07:56:41 -0700

>Do you get this behavior with one of the "sim" configurations (e.g.,
>sim/axis.ini, sim/tkemc.ini)?  What is the exact sequence of operations
>you do (key presses, button clicks, etc) to make this happen?  If you
>are not running the newest version of emc2 (2.1.5), does the problem
>still occur after you have upgraded?

>Based on your description of the problem, I loaded sim/axis.ini and did
>the following actions:
>F1 F2   (turn machine on)
>o cds.ngc   (load gcode file)
>r   (begin running gcode file)
>F1  (estop)
>F1 F2   (turn machine on again)
>At this point, the machine is still not moving.  Is there some
>difference between these steps and the steps you are performing?

>Jeff


# standard pinout config file for 3-axis steppers# using a parport for I/O## 
first load the parport driverloadrt probe_parportloadrt hal_parport cfg="0x0378 
 0xDFE0"## next connect the parport functions to threads# read inputs firstaddf 
parport.0.read base-thread 1# write outputs lastaddf parport.0.write 
base-thread -1#read inputs firstaddf parport.1.read base-thread 1#write outputs 
lastaddf parport.1.write base-thread -1# finally connect physical pins to the 
signalslinksp Xstep => parport.0.pin-03-outlinksp Xdir  => 
parport.0.pin-02-outlinksp Ystep => parport.0.pin-05-outlinksp Ydir  => 
parport.0.pin-04-outlinksp Zstep => parport.0.pin-07-outlinksp Zdir  => 
parport.0.pin-06-out# create a signal for the estop force false# alternate for 
estop force false pin 13 only with no ewrite#linkpp parport.1.pin-13-in 
iocontrol.0.emc-enable-in# connect e-stop write/sense to I/O controllernewsig 
EstopSense bitnewsig EstopWrite bitlinksp EstopSense <= 
parport.1.pin-13-inlinksp EstopSense => iocontrol.0.emc-enable-inlinksp 
EstopWrite <= parport.1.pin-16-outlinksp EstopWrite => 
iocontrol.0.user-enable-out#estop may need to be inverted# create feedhold 
signalnewsig feedhold bit# connect signal to motion controllinkps 
motion.feed-hold => feedhold# conect feedhold to physical pinlinksp feedhold => 
parport.1.pin-11-in-not# or this works too#net feedhold parport.1.pin-11-in-not 
motion.feed-hold# create a signal for "spindle brake"# create a signal for 
"spindlefwd"# create a signal for "spindlerev"newsig spindle-brake bitnewsig 
spindle-forward bitnewsig spindle-reverse bit# connect the controller to 
itlinkps motion.spindle-brake => spindle-brakelinkps motion.spindle-forward => 
spindle-forwardlinkps motion.spindle-reverse => spindle-reverse# connect it to 
physical pinlinksp spindle-brake => parport.1.pin-17-outlinksp spindle-forward 
=> parport.1.pin-03-outlinksp spindle-reverse => parport.1.pin-02-out# create a 
signle for mist coolant# create a signle for flood coolantnewsig MistOn 
bitnewsig FloodOn bit# connect iocontroler to it# connect it to a physical 
pinlinksp MistOn <= parport.1.pin-08-outlinksp MistOn => 
iocontrol.0.coolant-mistlinksp FloodOn <= parport.1.pin-09-outlinksp FloodOn => 
iocontrol.0.coolant-flood# create signals for tool loading loopback# use sig 
for tool prep to tool prepedlinkpp iocontrol.0.tool-prepare 
iocontrol.0.tool-prepared# creat a signal for toolchangenewsig changetool 
bitnewsig toolchanged bit# connect iocontroler to it# connect it to pphyiscal 
pinslinksp changetool <= parport.1.pin-04-outlinksp changetool => 
iocontrol.0.tool-changelinksp toolchanged <= parport.1.pin-10-in-notlinksp 
toolchanged => iocontrol.0.tool-changed## You might use something like this 
to enable chopper drives when machineON### the Xen signal is defined in 
core_stepper.hal linksp Xen => parport.0.pin-01-out## If you want 
active low for this pin, invert it like this: setp 
parport.0.pin-01-out-invert 1## A sample home switch on the X axis (axis 
0).  make a signal,### link the incoming parport pin to the signal, then link 
the signal### to EMC's axis 0 home switch input pin newsig Xhome bit# 
linkps parport.0.pin-10-in => Xhome# linksp Xhome => axis.0.home-sw-in## 
Shared home switches all on one parallel port pin?### that's ok, hook the same 
signal to all the axes, but be sure to### set HOME_IS_SHARED and HOME_SEQUENCE 
in the ini file.  See the### user manual! newsig homeswitches bit# linkps 
parport.0.pin-10-in => homeswit

Re: [Emc-users] estop writes to toolchange pin out? more testing

2007-05-23 Thread Jeff Epler
Do you get this behavior with one of the "sim" configurations (e.g.,
sim/axis.ini, sim/tkemc.ini)?  What is the exact sequence of operations
you do (key presses, button clicks, etc) to make this happen?  If you
are not running the newest version of emc2 (2.1.5), does the problem
still occur after you have upgraded?

Based on your description of the problem, I loaded sim/axis.ini and did
the following actions:
F1 F2   (turn machine on)
o cds.ngc   (load gcode file)
r   (begin running gcode file)
F1  (estop)
F1 F2   (turn machine on again)
At this point, the machine is still not moving.  Is there some
difference between these steps and the steps you are performing?

Jeff

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] estop writes to toolchange pin out? more testing

2007-05-22 Thread Jon Elson
Alfred Smart wrote:
>   I have done more testing and found that when I put the machine in 
> estop it jumps to the next line of code to be executed.
> Then when I bring it out of estop and push the machine on button it 
> takes off to the next instruction and not finishing the previous line of 
> code,it could be a rapid move!
Yes, I have observed the same behavior, and had meant to report it.
> If the next line of code happened to be a tool change than the machine 
> takes off without spindle rotation because of my relay logic is still 
> waiting for a toolchange but the axis still move.
> Abort fixes the trouble but its one more thing to remember to do to stay 
> out of trouble.
> It would be nice if abort was a must do or automatically done with 
> machine on.
Actually, an abort should be done when the machine state goes to 
ESTOP.  Or, at least, it seems that it should be that way.

Jon

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


[Emc-users] estop writes to toolchange pin out? more testing

2007-05-22 Thread Alfred Smart
  I have done more testing and found that when I put the machine in estop it 
jumps to the next line of code to be executed.
Then when I bring it out of estop and push the machine on button it takes off 
to the next instruction and not finishing the previous line of code,it could be 
a rapid move!
If the next line of code happened to be a tool change than the machine takes 
off without spindle rotation because of my relay logic is still waiting for a 
toolchange but the axis still move.
Abort fixes the trouble but its one more thing to remember to do to stay out of 
trouble.
It would be nice if abort was a must do or automatically done with machine on.
is this everyone's problem or is it something I'm doing
She's a runaway!

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users