Re: [Emc-users] Show us your pics of unobtanium!
I need to start cnc'ing metal. Anders, how long (machine time) did it take to cut the mould in the first picture? Also, were there tool changes used, i.e., roughing, finishing? - Original Message - From: "Anders Wallin" <[EMAIL PROTECTED]> > aluminium rudder mould (rudder is made with carbon fiber skins + balsa > or epoxy/microballoon core: > http://www.anderswallin.net/wp-content/2005_12/formar.jpg > > MDF deck plug (painted and sanded and then a mould in glassfiber is > laminated on top of this) > http://www.anderswallin.net/wp-content/2006_04deck/adeck2.jpg > > aluminium keel bulb mould (bulb is cast in lead) > http://www.anderswallin.net/wp-content/2003_05/cncmoldst.jpg > - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Joypad problem with version 2.1.4
John Kasunich wrote: I should proofread before I hit send, not after: > If countX looks OK, then its time to look at the motion controller. > "show pin axis.0.jog" will show you the jogging related pins. > jog-counts should have the same value as countX. jog-enable should > be TRUE. jog-vel-mode should be FALSE, and should be whatever you > have set as the "jog distance per count". The last sentence should read: "jog-vel-mode should be FALSE, and jog-scale should be whatever you have set as the jog distance per count." Regards, John Kasunich - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Joypad problem with version 2.1.4
Kirk wrote: > I attached the hal file on the last message. I am also attaching it > again here. The link to the file on the wiki is > http://wiki.linuxcnc.org/uploads/joypad.hal Oops... I apologize, I missed the attachment. The hal file shows that you are NOT using halui for jogging, only for some on/off stuff like machine on, pause, and resume. That explains how you were able to get analog jogging to work without using CVS head. So, lets figure out what isn't working. Start EMC, then open a shell (terminal window), and start halcmd using "halcmd -kf". That will get you an interactive session with a halcmd prompt: halcmd: start two halmeters: halcmd: loadusr halmeter halcmd: loadusr halmeter halcmd: On one of the meters, click the select button. When the dialog comes up, click the signals tab. Select the signal "velX" from the list, then click OK. That signal is the output from the joypad, going to a simulated encoder. On the other meter, click select, then the signals tab, then select the signal "countX" and click OK. That signal is the counts from the encoder, going into EMC's motion controller. Now try jogging with the joypad. When you move the stick away from center, VelX should become non-zero. The farther you go, the larger the value. Full deflection on the stick should give you plus or minus one. If that is not what happens, the problem is in the joypad or the joystick driver, or the connections to the driver. "show sig vel" should show you the signals, so you can verify that the right pins are connected. If velX looks OK, then check the other meter. countX should be constant (not neccessarily zero) when the stick is centered. As you move the stick away from center, countX should start changing. With the scaling you have in your file, countX should change by about 500 counts per second with full stick deflection. If you center the stick again, countX should stop changing. If that is not what happens, the problem is between the joypad output and the encoder output. Use "show sig X" to verify signals XA and XB are connected properly, "show sig countX" to make sure that countX is connected to the output of the encoder block. If countX looks OK, then its time to look at the motion controller. "show pin axis.0.jog" will show you the jogging related pins. jog-counts should have the same value as countX. jog-enable should be TRUE. jog-vel-mode should be FALSE, and should be whatever you have set as the "jog distance per count". In your case, it is either 0.1 or 0.01, as selected by two joypad buttons. You can check that by clicking select on one of the halmeters, clicking the "pins" tab, then selecting "axis.0.jog-scale" and clicking OK. The value on the meter should be either 0.1 or 0.01, and should change when you push the appropriate joypad buttons. I think I see the problem... (maybe). You have the scaling set up so that it will move either 0.1 or 0.01 units per count, and it will generate 500 counts per second at full deflection. Are your units inches or mm? If they are mm, then 0.1mm per count and 500 counts per second means 50mm/sec, or 3 meters/minute. If it is inches, 0.1 inches per count means 50 inches per second or 3000 inches per minute. A moderately fast machine can move at 3 meters per minute, but I doubt any machine can move 3000 inches per minute. If the scaling results in a ridiculously high jog rate, the position commanded by the jog is going to get way ahead of the machine. So when you let go of the stick, the machine is going to keep going, trying to catch up. There are two ways to deal with this problem. First, set more realistic scaling. If this is an inch machine, with rapid speed of 180 inches/min (3 inches per second), then set the high scale to 0.006. 0.006" per count times 500 counts/second = 3 inches/sec. Set the low scale factor ten times smaller, 0.0006 in this example. The other thing you might want to do is switch the jogwheel input into velocity mode. Unlike a real jogwheel, a joystick doesn't deal with position anyway. If you set axis.0.jog-vel-mode to TRUE (setp axis.0.jog-vel-mode 1), then the commanded position will not be allowed to get far ahead of the machine. When the counts stop changing, the machine will stop moving right away. Please let us know what you find! Regards, John Kasunich - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Pics and Examples
Hi Dean, It's good to hear that there are still some that do that! Dale Dean Hedin wrote: > Believe it or not, I "hand roll" most of my g-code. > I have a written a lot of custom programs to deal with each task as I come > upon it. > > > > - Original Message - > From: "Mike :0)" <[EMAIL PROTECTED]> > To: > Sent: Tuesday, March 27, 2007 12:02 PM > Subject: Re: [Emc-users] Pics and Examples > > > >>Guys, those are all some great examples. >>What software was used to generate the toolpaths? >>Thank you all for the hard work. >>Mike >> >> >> >> >> >>Don't pick lemons. >>See all the new 2007 cars at Yahoo! Autos. >>http://autos.yahoo.com/new_cars.html >> >>- >>Take Surveys. Earn Cash. Influence the Future of IT >>Join SourceForge.net's Techsay panel and you'll get the chance to share >>your >>opinions on IT & business topics through brief surveys-and earn cash >>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >>___ >>Emc-users mailing list >>Emc-users@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/emc-users > > > > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Show us your pics of unobtanium!
Hi Dean, Gene, This is coming from a Toolmaker and I also make guitars. If it were metal I'd say yes all but the final finish could be done on the machine. Knowing wood the way I do I have to say Dean is right about the tearout. As a toolmaker and woodworker I understand first hand that just need to be done by hand with a file. If you look closely at Deans picture you can see little bits of tearout with just that small cut. Dale Dean Hedin wrote: >>My guess is that with that, you could >>cut every groove the the checkering file will finish at 24 tpi if you >>wanted to go that fine, > > > No Gene, can't do it. Lord knows I've tried. > Too much tear out occurs even with the tiniest of bits. The net result is > lost diamonds. > > The best I have been able to achieve is every other checkering line. The > picture I posted > is a grid of every thrid line. > > It's not as bad as it seems. It takes about a half hour to fully checker > the grip with > the basic cross hatch done by the machine. Without the grid and done > manually; hours... > > > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Joypad problem with version 2.1.4
I attached the hal file on the last message. I am also attaching it again here. The link to the file on the wiki is http://wiki.linuxcnc.org/uploads/joypad.hal Kirk On Tue, 2007-03-27 at 19:57 -0400, John Kasunich wrote: > Kirk wrote: > > I am using the joypad.hal file located on the wiki. I have of course > > modified it for my machine. I am loading halui and using it to control > > various functions via buttons on the joypad. The previous version of > > EMC was 2.1.3 which I obtained via Ubuntu Synaptic Package Manager. I > > also updated to 2.1.4 the same way. > > There are 246 pages on the wiki. You could make it easier for us to > help you by posting the URL of the one you used. > > You could also post your hal file, as two different people have > asked. > > At least we know you are using halui now. But unless this page: > http://cvs.linuxcnc.org/cgi-bin/cvsweb.cgi/emc2/src/emc/usr_intf/halui.cc?graph=1 > is lying to me, halui.cc did NOT change from 2.1.3 to 2.1.4, and more > importantly, it did not support analog until version 1.39, which > is NOT included in the 2.1.4 release. > > You are going to have to give some details! > > Regards, > > John Kasunich > > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > # joypad.hal -- hal configuration file to move a cnc machine using a joypad # [JOG] # Components # We will use hal_joystick to read the axis value (float) for X Y Z, we will send these values to the # speed pin of a sim-encoder component, for X Y Z, this component outputs Phase-A and Phase-B signal, # just like a real quadrature rotary encoder. We will decode those signals with an encoder component for X Y Z # and will send the result counts value to the axis jog pin for X Y Z. # Load the hal_joystick component that creates joypad.axis. and joypad.button. pins loadusr hal_joystick -d /dev/input/js0 -p joypad # Load three encoder and three sim_encoder components loadrt encoder num_chan=3 loadrt sim_encoder num_chan=3 # Create links between the axis pins and the speed pin of the sim-encoder for X Y Z net velX joypad.axis.0 => sim-encoder.0.speed net velY joypad.axis.1 => sim-encoder.1.speed net velZ joypad.axis.3 => sim-encoder.2.speed # Create links between sim-encoder Phase-A and Phase-B and encoder Phase-A and Phase-B for X Y Z net XA sim-encoder.0.phase-A => encoder.0.phase-A net XB sim-encoder.0.phase-B => encoder.0.phase-B net YA sim-encoder.1.phase-A => encoder.1.phase-A net YB sim-encoder.1.phase-B => encoder.1.phase-B net ZA sim-encoder.2.phase-A => encoder.2.phase-A net ZB sim-encoder.2.phase-B => encoder.2.phase-B # Create links between encoder counts and jog counts for X Y Z net countX encoder.0.counts => axis.0.jog-counts net countY encoder.1.counts => axis.1.jog-counts net countZ encoder.2.counts => axis.2.jog-counts # Set parameter values setp encoder.0.position-scale1 setp encoder.0.x4-mode TRUE setp encoder.1.position-scale1 setp encoder.1.x4-mode TRUE setp encoder.2.position-scale1 setp encoder.2.x4-mode TRUE setp encoder.capture-position.tmax0 setp encoder.update-counters.tmax0 setp sim-encoder.0.ppr 0500 setp sim-encoder.0.scale1 setp sim-encoder.1.ppr 0500 setp sim-encoder.1.scale-1 setp sim-encoder.2.ppr 0500 setp sim-encoder.2.scale-1 setp sim-encoder.make-pulses.tmax0 setp sim-encoder.update-speed.tmax0 # Enable jog for X Y Z setp axis.0.jog-enable TRUE setp axis.1.jog-enable TRUE setp axis.2.jog-enable TRUE # Attach realtime functions to threads addf encoder.capture-position servo-thread addf sim-encoder.update-speed servo-thread addf encoder.update-counters base-thread addf sim-encoder.make-pulses base-thread # [BUTTON-SAMPLES] # Here are two examples on how to attach some functions to joypad buttons. We will use Halui pins for the # second example. # Scale button # we set two buttons (1 and 0) to choose the jogscale value. Pressing button 1 will set the scale to 0.01 # while pressing button 0 will set it to 0.1. # Components # We will use a two values selector and a flipflop component loadrt mux2 loadrt flipflop # Link between buttons and flipflop, flipflop will output TRUE when rising edge is detected on set pin, FALSE # when rising edge is on reset pin. net button0 joypad.button.0 => flipflop.0.reset net button1 joypad.button.1 => flipflop.0.set # Link between flipflop and mux2, mux2
Re: [Emc-users] Pics and Examples
Believe it or not, I "hand roll" most of my g-code. I have a written a lot of custom programs to deal with each task as I come upon it. - Original Message - From: "Mike :0)" <[EMAIL PROTECTED]> To: Sent: Tuesday, March 27, 2007 12:02 PM Subject: Re: [Emc-users] Pics and Examples > Guys, those are all some great examples. > What software was used to generate the toolpaths? > Thank you all for the hard work. > Mike > > > > > > Don't pick lemons. > See all the new 2007 cars at Yahoo! Autos. > http://autos.yahoo.com/new_cars.html > > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Show us your pics of unobtanium!
> My guess is that with that, you could > cut every groove the the checkering file will finish at 24 tpi if you > wanted to go that fine, No Gene, can't do it. Lord knows I've tried. Too much tear out occurs even with the tiniest of bits. The net result is lost diamonds. The best I have been able to achieve is every other checkering line. The picture I posted is a grid of every thrid line. It's not as bad as it seems. It takes about a half hour to fully checker the grip with the basic cross hatch done by the machine. Without the grid and done manually; hours... - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Joypad problem with version 2.1.4
Kirk wrote: > I am using the joypad.hal file located on the wiki. I have of course > modified it for my machine. I am loading halui and using it to control > various functions via buttons on the joypad. The previous version of > EMC was 2.1.3 which I obtained via Ubuntu Synaptic Package Manager. I > also updated to 2.1.4 the same way. There are 246 pages on the wiki. You could make it easier for us to help you by posting the URL of the one you used. You could also post your hal file, as two different people have asked. At least we know you are using halui now. But unless this page: http://cvs.linuxcnc.org/cgi-bin/cvsweb.cgi/emc2/src/emc/usr_intf/halui.cc?graph=1 is lying to me, halui.cc did NOT change from 2.1.3 to 2.1.4, and more importantly, it did not support analog until version 1.39, which is NOT included in the 2.1.4 release. You are going to have to give some details! Regards, John Kasunich - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Joypad problem with version 2.1.4
I am using the joypad.hal file located on the wiki. I have of course modified it for my machine. I am loading halui and using it to control various functions via buttons on the joypad. The previous version of EMC was 2.1.3 which I obtained via Ubuntu Synaptic Package Manager. I also updated to 2.1.4 the same way. Kirk On Tue, 2007-03-27 at 00:40 -0400, John Kasunich wrote: > Kirk wrote: > > I just updated my system with the latest EMC 2.1.4. Prior to that I had > > installed a USB joystick controller and it worked fine. After the > > upgrade, the analog axes joysticks no longer work properly. If I jog an > > axis it continues in the same direction as started and does not stop > > when the control is released. Also the axis velocity is not > > proportional to the joystick movement. It runs at the current programmed > > manual velocity scaled by the override. > > > > I ran the test specified in the wiki for checking out the joystick > > controller using Hal Meter. The Joypad works the same as it did before. > > The analog controls output a zero in the neutral position and vary > > between 0..1 as a joystick is moved. > > > > Does anybody know what I am missing? The joypad.hal file is the same > > file that I used in version 2.1.3. > > > > Are you using halui to do the joystick jogging? Or are you using the > motion controller's jog wheel inputs (axis.N.jog-counts and related pins)? > > (Those are two completely different approaches, and without knowing > which one you are using there isn't much we can do to help.) > > If you are using the halui approach, keep in mind that joystick jogging > was added to halui in CVS head only. 2.1.4 does not support it. > Perhaps when you had it working before you were using a CVS checkout? > > Please post your hal file, in a message if its short, or on > http://pastebin.ca if it is very long (post the pastebin URL here). > It's late now, but I'll take a look at it tomorrow. > > Regards, > > John Kasunich > > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > # joypad.hal -- hal configuration file to move a cnc machine using a joypad # [JOG] # Components # We will use hal_joystick to read the axis value (float) for X Y Z, we will send these values to the # speed pin of a sim-encoder component, for X Y Z, this component outputs Phase-A and Phase-B signal, # just like a real quadrature rotary encoder. We will decode those signals with an encoder component for X Y Z # and will send the result counts value to the axis jog pin for X Y Z. # Load the hal_joystick component that creates joypad.axis. and joypad.button. pins loadusr hal_joystick -d /dev/input/js0 -p joypad # Load three encoder and three sim_encoder components loadrt encoder num_chan=3 loadrt sim_encoder num_chan=3 # Create links between the axis pins and the speed pin of the sim-encoder for X Y Z net velX joypad.axis.0 => sim-encoder.0.speed net velY joypad.axis.1 => sim-encoder.1.speed net velZ joypad.axis.3 => sim-encoder.2.speed # Create links between sim-encoder Phase-A and Phase-B and encoder Phase-A and Phase-B for X Y Z net XA sim-encoder.0.phase-A => encoder.0.phase-A net XB sim-encoder.0.phase-B => encoder.0.phase-B net YA sim-encoder.1.phase-A => encoder.1.phase-A net YB sim-encoder.1.phase-B => encoder.1.phase-B net ZA sim-encoder.2.phase-A => encoder.2.phase-A net ZB sim-encoder.2.phase-B => encoder.2.phase-B # Create links between encoder counts and jog counts for X Y Z net countX encoder.0.counts => axis.0.jog-counts net countY encoder.1.counts => axis.1.jog-counts net countZ encoder.2.counts => axis.2.jog-counts # Set parameter values setp encoder.0.position-scale1 setp encoder.0.x4-mode TRUE setp encoder.1.position-scale1 setp encoder.1.x4-mode TRUE setp encoder.2.position-scale1 setp encoder.2.x4-mode TRUE setp encoder.capture-position.tmax0 setp encoder.update-counters.tmax0 setp sim-encoder.0.ppr 0500 setp sim-encoder.0.scale1 setp sim-encoder.1.ppr 0500 setp sim-encoder.1.scale-1 setp sim-encoder.2.ppr 0500 setp sim-encoder.2.scale-1 setp sim-encoder.make-pulses.tmax0 setp sim-encoder.update-speed.tmax0 # Enable jog for X Y Z setp axis.0.jog-enable TRUE setp axis.1.jog-enable TRUE setp axis.2.jog-enable TRUE # Attach realtime functions to threads addf encoder.capture-position servo-thread addf sim-encoder.update-speed serv
Re: [Emc-users] axis homing
Stuart Stevenson wrote: > Gentlemen, > I had read the manual about the axis.N.index-enable. I had tried > these commands. I have updated the sample config file set that is on my web pages at http://jelinux.pico-systems.com/codes/ppmc/ These are the actual files off my Bridgeport conversion, and the axis home position is refined by the encoder index pulse. Sorry that what I had on there was so far out of date. Jon - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Emc-users Digest, oh my!
that video made my pu**y wet... and i am male! truly amazing... i'm building a 3 axis CNC engraver/mini-mini mill currently. i'm using a SP3 controller board. anyone set this baby up with emc yet? i think it came from CNCZONE.COMi haven't turned it on yet because i am lacking my limit switches. anyone know a cheap source for some lever action type switches? > -- > > Message: 8 > Date: Tue, 27 Mar 2007 08:41:17 +0200 > From: "Svenne Larsson" <[EMAIL PROTECTED]> > Subject: Re: [Emc-users] Video of CNC Lathe in Action > To: "Enhanced Machine Controller (EMC)" > > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > Hello, > > My jaw dropped when I saw this clip. Wait until you see the threading > cycle. > > http://video.google.com/videoplay?docid=-2285657714531903438 > > Amazing machine. :) - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Pics and Examples
Guys, those are all some great examples. What software was used to generate the toolpaths? Thank you all for the hard work. Mike Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. http://autos.yahoo.com/new_cars.html - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] axis homing
John Kasunich wrote: > > there should be a HAL pin from the driver called > > ppmc.N.encoder.M.index-enable > > index-enable, not index. Looking at the code, I see that older versions of the PPMC might not export the index-enable pin. If you load the driver and "show pin ppmc.0.encoder.02" shows an index pin but no index-enable pin, your board is an old version that doesn't properly support indexing. You should contact Jon Elson for an upgrade in that case. Looking at the code also leaves me rather convinced that the index pin should be removed. But I'll leave that decision to Jon, its his product. Regards, John Kasunich - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] axis homing
Stuart Stevenson wrote: > Gentlemen, > I had read the manual about the axis.N.index-enable. I had tried > these commands. I am working with my Z axis as this is the easiest to > reach. > > ### > > linkpp axis.2.index-enable ppmc.0.encoder.02.index OK, first thing - never ever EVER use linkpp. It is evil! I know that seems harsh, and its not your fault that you are using it, so please don't take that the wrong way. Let me explain: The linkpp command was added as a shortcut to easily link two pins together. The normal way to do that was (and still is): # create a signal newsig some-meaningful-name whatever-type-the-pins-are # use the signal to connect the pins linksp some-meaningful-name the-first-pin linksp some-meaningful-name the-second-pin The result of those three commands is a signal with a name that means something, connecting the two pins. The linkpp version of that is much shorter and more convenient: linkpp the-first-pin the-second-pin That is equivalent to: # create a signal newsig the-first-pin whatever-type-the-pins-are # use the signal to connect the pins linksp the-first-pin the-first-pin linksp the-first-pin the-second-pin You still wind up with a signal connecting the two pins, but now the signal is named after the first pin. Having a signal and a pin with the same name is legal, but very confusing. In hindsight, 'linkpp' is an abomination that should never have been invented. We now have a much better "shorthand" way to connect two (or more) pins, the 'net' command: net some-meaningful-name the-first-pin the-second-pin The above line is equivalent to the very first example - it results in a new signal with a name that means something, connecting the two pins. > this gives me the error as follows > > HAL: ERROR: signal 'axis.2.index-enable' already has output or I/O > pin(s)HAL:14: linkpp failed > > halshow shows the axis.2.index-enable pin connected to axis.2.index-enable > halshow shows nothing connected to ppmc.0.encoder.02.index > > ### > > linksp Zindex axis.2.index-enable > linksp Zindex ppmc.0.encoder.02.index > > ### > > linksp Zindex ppmc.0.encoder.02.index > linksp Zindex axis.2.index-enable > > ### You get points for persistence - you've tried three different ways of connecting those two pins. Unfortunately ppmc.0.encoder.02.index is not the pin you want. In my last email I wrote: > there should be a HAL pin from the driver called > ppmc.N.encoder.M.index-enable index-enable, not index. Connect the ppmc index-enable to the axis index-enable (use newsig + linksp, or net, not linkpp). I have no idea what the ppmc 'index' pin does. Jon Elson, do you know? It is not part of the "canonical encoder interface", and it is just causing confusion. If there is no good reason for it, it should be deleted. > What am I missing, besides gray matter and a clue? :) No, you were led astray by a confusingly named pin. Regards, John Kasunich - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
[Emc-users] axis homing
Gentlemen, I had read the manual about the axis.N.index-enable. I had tried these commands. I am working with my Z axis as this is the easiest to reach. ### linkpp axis.2.index-enable ppmc.0.encoder.02.index this gives me the error as follows HAL: ERROR: signal 'axis.2.index-enable' already has output or I/O pin(s)HAL:14: linkpp failed halshow shows the axis.2.index-enable pin connected to axis.2.index-enable halshow shows nothing connected to ppmc.0.encoder.02.index ### linksp Zindex axis.2.index-enable linksp Zindex ppmc.0.encoder.02.index this gives me the error as follows HAL: ERROR: signal 'Zindex' already has output or I/O pin(s)HAL:21: link failed the first command is successfull and halshow shows the axis.2.index-enable pin connected to Zindex. The next command fails, gives me the error feedback and doesn't connect ### linksp Zindex ppmc.0.encoder.02.index linksp Zindex axis.2.index-enable this gives the error as follows HAL: ERROR: signal 'Zindex' already has output pinHAL:21: link failed the first command is successful and halshow shows the ppmc.0.encoder.02.index pin connected to Zindex. The next command fails, gives me the error feedback and doesn't connect reversing the second command to "linkps axis.2.index-enable Zindex" gives me the error HAL: ERROR: signal 'Zindex' already has output pinHAL:28: link failed ### I restarted EMC between each test to make sure I had no carry over and I have been unable to find a combination that works. Maybe I should have asked this question more specifically the first time but I thought I was missing something and didn't want to lead the answer to the conclusion. What am I missing, besides gray matter and a clue? :) thanks Stuart - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Joypad problem with version 2.1.4
Uhm, mine did not work with 2.1.2 and 2.1.3 but now with the 2.1.4 works fine. Please post your hal file. Manfredi My website: www.m24-pro.com >From: Kirk <[EMAIL PROTECTED]> >Reply-To: "Enhanced Machine Controller (EMC)" > >To: "Enhanced Machine Controller (EMC)" >Subject: [Emc-users] Joypad problem with version 2.1.4 >Date: Mon, 26 Mar 2007 21:52:41 -0600 > >I just updated my system with the latest EMC 2.1.4. Prior to that I had >installed a USB joystick controller and it worked fine. After the >upgrade, the analog axes joysticks no longer work properly. If I jog an >axis it continues in the same direction as started and does not stop >when the control is released. Also the axis velocity is not >proportional to the joystick movement. It runs at the current programmed >manual velocity scaled by the override. > >I ran the test specified in the wiki for checking out the joystick >controller using Hal Meter. The Joypad works the same as it did before. >The analog controls output a zero in the neutral position and vary >between 0..1 as a joystick is moved. > >Does anybody know what I am missing? The joypad.hal file is the same >file that I used in version 2.1.3. > >Thanks, >Kirk > > > >- >Take Surveys. Earn Cash. Influence the Future of IT >Join SourceForge.net's Techsay panel and you'll get the chance to share >your >opinions on IT & business topics through brief surveys-and earn cash >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >___ >Emc-users mailing list >Emc-users@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/emc-users _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users