Back
[01:08:39] <automata_> hi PCW
[01:09:46] <automata_> I was wondering if I were to run two stepgens in velocity mode and have their velocity commands be equal, then will their positions be aligned after say 1/2 hour of running?
[02:09:04] <DJ9DJ> moin
[02:36:55] <Loetmichel> mornin'
[05:32:58] <automata> I was wondering if I were to run two stepgens in velocity mode and have their velocity commands be equal, then will their positions be aligned after say 1/2 hour of running?
[05:36:24] <automata> hi
[05:38:25] <jthornton> try and see
[05:42:22] <Jymmm> automata: do they START or END aligned?
[07:03:08] <automata> I want the start an end aligned
[07:04:16] <automata> I guess I am going to try it out .. will report back with resulsts and details...
[08:36:12] <cncbasher_> can anyone confirm when using axis if you move under manual control 1mm the readout shows 25.4
[08:36:32] <cncbasher_> i.e 1mm is equaling 1"
[08:36:39] <cradek> more details please
[08:36:44] <cradek> what do you mean manual control?
[08:36:54] <cncbasher_> i've just try'd it and i get the same error
[08:37:19] <cncbasher_> under manual control as opposed to gcode
[08:37:36] <cradek> what do you mean manual control? are you jogging? using mdi? wheel?
[08:37:44] <cncbasher_> use the drop down an select 1mm
[08:37:56] <cradek> ok, using incremental jog
[08:38:00] <cradek> what linuxcnc version?
[08:38:16] <cncbasher_> then do a move and the display then shows a move of 25.4 rather than 1mm
[08:38:27] <cncbasher_> although machine only moves 1mm
[08:38:46] <cncbasher_> 2.6 git master
[08:38:54] <cradek> is your ini file in inches or mm?
[08:38:58] <cncbasher_> mm
[08:39:06] <cradek> can you put your ini up on pastebin please
[08:39:21] <cncbasher_> had a post on the forum , so i went and checked it
[08:39:26] <cradek> also let us know your exact git version (git describe)
[08:39:30] <cncbasher_> and i get the same result
[08:39:59] <cradek> have a url of the thread?
[08:40:41] <cncbasher_> http://linuxcnc.org/index.php/english/forum/38-general-linuxcnc-questions/25890-git-linuxcnc-26pre-problem-mm#27050
[08:41:48] <cradek> thanks for info, brb
[08:41:59] <cncbasher_> ok
[08:42:34] <cncbasher_> it's treating 1mm as 1inch somewhere i think
[08:43:15] <cradek> did you happen to test 2.5 too?
[08:43:24] <cradek> darn, gotta run, bbl
[08:43:46] <cncbasher_> not as yet
[09:01:33] <mrsun> http://blog.cnccookbook.com/2012/11/27/clearing-welded-on-aluminum-from-endmills-drill-bits-and-inserts/?utm_source=CNCCookbook+Blog+Posts&utm_campaign=be023125ae-RSS_EMAIL_CAMPAIGN&utm_medium=email
[09:22:35] <cradek> well yeah it sure does look broken
[09:23:01] <cradek> the BIG DRO showing over the backplot is new behavior I don't recall discussing
[09:23:07] <cradek> I wonder if it was an accident.
[09:23:09] <cncbasher_> cradek:do you get the same result
[09:23:53] <cradek> yeah, something's wrong with it, not sure what yet
[09:24:13] <cradek> I'm going to check 2.5, although I'm sure it's fine
[09:24:39] <cncbasher_> he says 2.5 worked fine in his messages
[09:25:13] <cradek> ok
[09:25:16] <cradek> I agree 2.5 is fine
[09:37:40] <awallin> mrsun: wow that's really abusing the endmill. no coolant at all and slow rpm or something ?
[10:21:03] <mrsun> humm
[10:21:24] <mrsun> haha they must have done that
[10:21:30] <mrsun> but the thing was about getting it off :P
[10:50:27] <mrsun> http://www.cnccookbook.com/img/OthersProjects/Machines/DynaMax2.jpg thats actualy quite clever .. tho doesnt some machines use springs to hold the motor against the racks ?
[11:00:10] <IchGuckLive> awallin: ?
[11:00:51] <IchGuckLive> PCW ?
[11:01:39] <archivist> mrsun, no mention of the motor rocking on its mount :)
[11:02:02] <IchGuckLive> someone can give me a clue on what this cable may look like there is no /RXD /TXD on the serial connector and also the pin numbers are wrong
[11:02:05] <IchGuckLive> http://www.bilder-upload.eu/show.php?file=982d8d-1354121202.png
[11:03:55] <IchGuckLive> pcw_home: ?
[11:04:34] <pcw_home> ? not sure what the question is, Is that the suggested cable for setting up your drive?
[11:05:11] <IchGuckLive> yes the yaskawa service told me to look into the Divice PDF and ifound the xable layout
[11:05:39] <IchGuckLive> but it gives me a question as there is no NOT port on the PC end
[11:05:51] <IchGuckLive> look at the screenshot
[11:08:01] <ve7it> not a problem... just the way they have them labeled... just build the cable like shown on page c12
[11:08:39] <pcw_home> Yeah the PC end is labled wrong
[11:08:49] <IchGuckLive> i did it and still got no connection
[11:09:22] <ve7it> 2,3,and pin 5 are the standard 9 pin pc cable .... did you add the jumpers shown on the pc end of the cable?
[11:09:43] <IchGuckLive> yes
[11:10:32] <IchGuckLive> can a messure somthing with the oscilloscope if it thansfers data ?
[11:10:38] <ve7it> are you using their software setup package or a generic terminal emulator?
[11:10:50] <IchGuckLive> software
[11:11:32] <IchGuckLive> Xtraware press connect online and it goes sandtimer for 10sec and returns with no fault and no connection
[11:11:59] <pcw_home> You can verify correct cabling of the txd/rxd with a voltmeter or a scope
[11:12:03] <ve7it> hmmm... you could check the pins 2 and 3 on the pc end of the cable
[11:12:37] <IchGuckLive> what shoudt i messure there
[11:12:46] <pcw_home> can you measure the voltages at pin 2 and 3 at the PC end?
[11:12:57] <ve7it> signals should swing at least 0 to +5, but more correctly +-3 to +-15
[11:13:23] <IchGuckLive> i will set the osci up
[11:13:50] <IchGuckLive> 2to GND and 3 to Gnd or 2-3
[11:14:05] <pcw_home> they should both idle at at a negative voltage but maybe close to 0V (to gnd)
[11:19:59] <ve7it> scope ground to pin 5 and then look at signals on pin 2 and 3 of pc connector
[11:21:11] <IchGuckLive> no ther is nothing
[11:21:39] <pcw_home> 0V?
[11:23:17] <IchGuckLive> -6.35V on 3 to Gbd
[11:23:26] <IchGuckLive> GND
[11:24:33] <pcw_home> PC pin 3?
[11:24:35] <pcw_home> what about pin 2
[11:25:00] <IchGuckLive> 6.35 between 3 and 2 +- depeding on dir of messurment
[11:25:13] <IchGuckLive> nothing on 2 to GND
[11:25:44] <pcw_home> 0V?
[11:26:52] <IchGuckLive> yes
[11:28:03] <pcw_home> that sounds plausible if the drive is faking RS-232 with TTL level outputs so nothing obvious wrong
[11:29:29] <tjb1> http://www.youtube.com/watch?v=QHaVc5i-Dzs
[11:35:06] <IchGuckLive> yesterday the servo has moved even with errors today after yaskawa told me to reset to factory default and start over with the servo setupfile it is worth
[11:35:35] <IchGuckLive> no communication to the divice means no paramer settings
[11:36:02] <IchGuckLive> and this is the new error Servo parameter wrong
[11:37:39] <IchGuckLive> the driver gives me a sowtware version of 003C the type field gives a 3.23
[11:38:21] <IchGuckLive> the software let me choos lots of divices
[11:43:57] <IchGuckLive> if i check the driver for Servomotor Model it gives me a number that is not in the list
[11:44:17] <IchGuckLive> 08 is the display the list goes to 06
[11:44:33] <IchGuckLive> but the servo motor is not in the list
[11:45:14] <IchGuckLive> i did parameter manuelll input of all 185 listet in the motor file yaskawa provided
[11:48:48] <IchGuckLive> pcw_home: what if i change the 2 and 3 wire <-> maybe it is wrong in the numbers
[11:52:42] <IchGuckLive> pcw_home: this is the connector on the Drive
[11:52:45] <IchGuckLive> http://foengarage.de/rs232-omron.jpg
[11:54:46] <IchGuckLive> isent it in standard that TXD connects to RXD and RXD to TXD
[11:55:01] <IchGuckLive> so the comunication goes Tranciver Reciver
[12:11:47] <pcw_home> Hmm thats RS-422
[12:24:50] <IchGuckLive> pcw_home: here are the manuels if you want to have a look
http://industrial.omron.us/en/misc/search/default.html?q=xtradrive
[12:25:17] <IchGuckLive> first one is the software second one is the manuel for the drive
[13:04:44] <jdh> I want to scale a 0-90VDC tach down to 0-5VDC. Does the overall magnitude of the voltage divider resistors really matter that much as long as the ratio is correct?
[13:07:24] <skunkworks> wow - 0 to 5 volts... that seems
[13:07:30] <skunkworks> a bit extreme
[13:07:38] <pcw_home> You need them high enough so they dont dissipate too much power or represent too much load for the tachometer but low enough so the low end tap is not too high impedance
[13:07:38] <jdh> why?
[13:07:41] <cradek> what are you doing?
[13:08:14] <pcw_home> also that will only work one direction (unless you have -5 to +5V
[13:08:28] <pcw_home> inputs)
[13:08:37] <jdh> I want to read a tach with an avr and compute an average rpm
[13:09:15] <cradek> for what purpose?
[13:09:59] <jdh> verification of a tube welder
[13:10:01] <pcw_home> so 85K and 5K...
[13:11:02] <pcw_home> well 84.5k
[13:12:42] <jdh> the tach is 0-90, but it will never see more than 55V or so
[13:15:17] <pcw_home> so 49.9K and 4.99k... (or 10K and 1 K if you want a < 1K source impedance for the AVR A-D)
[13:16:48] <pcw_home> 10K 1/2 W in this case since it will dissipate 1/4 W at 55V into the divider
[13:17:19] <automata> Hi PCW
[13:17:33] <pcw_home> Hi
[13:18:00] <automata> I wanted to implement an electronic gear using a mesa stepgen with 7i43
[13:18:27] <pcw_home> OK
[13:18:39] <automata> I got the obvious solution out of the way...
[13:19:09] <automata> Put the two stepgens in velocity mode and provided a scaled velocity command to both
[13:19:41] <automata> I measured the position-fb pin from both and all is good.
[13:20:14] <automata> If the two stepgens have started from 0 then they scale together and not a moment out of sync
[13:20:30] <automata> But this is an open loop system.
[13:21:00] <automata> There is no feedback from the position pulses to ensure position synchronization
[13:21:26] <pcw_home> well they will stay reasonably in alignment but there will be long term drift (if for no other reason than the limited accuracy of specifying the rates)
[13:21:35] <automata> So this system may miss a few pulses and be out of sync in position..
[13:21:47] <automata> that is what I thought...
[13:22:11] <automata> So what follows is how to prevent that...
[13:22:41] <pcw_home> you could lock them together with a PID loop (and the scale/offset comp)
[13:23:22] <automata> Yes.. that is one way
[13:23:45] <pcw_home> for integer ratios it can stay in sync
[13:23:50] <automata> but another requirement is the ability to change the gear ratio
[13:24:33] <pcw_home> Yeah the gear ration would be specified as an input to the scale comp
[13:24:40] <automata> if the gear ratio changes how would the offset work?
[13:25:10] <automata> yup.. and how to use the offset in this scenario? when to set the offset?
[13:25:35] <automata> I am guessing it should be set when the gear ratio changes
[13:26:21] <pcw_home> If you need to change the gear ration dynamically you wouldneed to set the offset so they is no output step
[13:27:00] <pcw_home> the scale comp has both scale (gear ratio) and offset
[13:27:15] <automata> yes
[13:28:43] <automata> Is there a way to set the position-fb pin in the hostmot2 component to 0 ?
[13:29:01] <automata> then I would not need the offset...
[13:29:07] <pcw_home> I dont think so
[13:29:38] <automata> also would there be a hal example for setting the offset on change of the gear ratio?
[13:29:58] <pcw_home> I think that also dangerous output step wise
[13:30:15] <pcw_home> (clearing the position)
[13:30:23] <automata> hmm
[13:31:18] <pcw_home> so better done with an offset (sort of same situation with encoder counters, you never really want to clear them when moving, just grab an offset)
[13:31:24] <automata> Well to further complicate matters, I want to operate both stepgens in position mode sometimes too...
[13:32:11] <pcw_home> Can you use a LinuxCNC axis for these? (so its always position mode)
[13:32:28] <automata> I tried the control-type pin on the hostmot2 component and it works... I can switch between position and velocity quiet well
[13:33:17] <automata> I could use the axis from linuxcnc... but then I also want to operate the axis for a threading like operation
[13:33:27] <pcw_home> Yeah as long as you deal with control loop glitches/steps when changing modes
[13:33:35] <jdh> pcw: thanks!
[13:34:01] <automata> I thought of disabling the pulse outputs from the FPGA during changes
[13:34:15] <pcw_home> the mux component and the right offsets should make it possible
[13:34:16] <automata> Further also disable the motor drives
[13:35:11] <pcw_home> that OK as long as this is not done while moving (the stepgen enable input does this)
[13:36:37] <automata> any idea how to set the offset on change of gear ratio or control type?
[13:36:37] <pcw_home> you can also use the limit component to ramp velocities up and down
[13:37:09] <automata> i did that too... I used limit2 for controlling velocity slew
[13:37:12] <automata> rate
[13:38:03] <automata> I think I can ensure that the gear ratio is not changed while moving or when in position control mode
[13:38:43] <automata> Also I am using the spindle speed output from motion.spindle-speed to set the speed of the electronic gear
[13:38:59] <pcw_home> its a simple subtraction
[13:40:49] <automata> So just use an edge trigger when the control mode changes and cache the current position in offset with a sample and hold type component?
[13:41:25] <pcw_home> at least I think it is...
[13:41:27] <pcw_home> offset is -NxP
[13:41:28] <pcw_home> where N is the ratio and P is the current position
[13:41:30] <pcw_home> (since master is 1xP)
[13:42:10] <automata> I think I will also have to account for the position-scale for both the axes... but that can be accounted for in N
[13:43:14] <automata> The master will also need an offset applied right?
[13:43:50] <pcw_home> I was assuming there a master (1x) and a slave (Nx) so the master never needs a offset
[13:43:57] <pcw_home> theres
[13:44:37] <automata> but on changing the gear ratio, the master postiion will also be required to be offset else we will still see a glitch
[13:45:14] <automata> glitch/step in output
[13:45:17] <pcw_home> not if its its always the master (ist ratio never changes)
[13:45:25] <pcw_home> always 1x
[13:46:09] <automata> Yup... time to write down the math on a piece of paper...
[13:47:21] <pcw_home> you could do both (parametric) with Nx and Mx, then you would have to offset both
[13:47:23] <pcw_home>
[13:47:56] <automata> ok.. that is a good suggestion...
[13:48:41] <automata> there is no float sample and hold component? I guess it is time to write one...
[13:49:50] <pcw_home> If you could actually write the FPGA registers with data you could do integer ratios exactly (not practical but illustrates how the frequency generator works)
[13:50:38] <automata> I generally envision only integer ratios
[13:51:08] <pcw_home> and there would be errors during ramp up and down
[13:51:16] <automata> but it is safe and easy to make a complete solution while I am at it...
[13:52:26] <automata> Now for the PID .. I should be using the scaled velocity command as a velocity feedforward command right?
[13:53:56] <pcw_home> I think so (feed forward has to be 99.999% of this)
[13:53:57] <automata> and use the position error as ( Master_pos*M - master_offset) - (slave_pos*N - slave_offset)
[13:54:23] <automata> nope... that is wrong
[13:54:31] <pcw_home> _scaled_ slave position
[13:55:15] <automata> i think error = (MasterPos - master_offset) * M - (slavePos - slave_offset) *N
[13:55:21] <automata> Does that sound right?
[13:55:57] <pcw_home> yeah something like that anyway
[13:56:38] <automata> cool ...
[13:57:10] <automata> Another question... how do I test if this works right? and how would I start to tune the PID?
[13:57:43] <automata> any test case scenarios or corner cases I could try?
[14:00:34] <pcw_home> Since it is a simple first order system I would just start with FF1 and a little P
[14:01:03] <automata> Ok
[14:03:30] <pcw_home> FF1 comes from the command input so needs to reflect the ratio
[14:06:02] <automata> the output of the PID is velocity of the slave right?
[14:06:19] <pcw_home> Hmm I think I need to think about this some more...
[14:06:21] <pcw_home> the output of the PID loops need to be the correct velocity even with no feedback
[14:06:41] <automata> That is what I was going to say next...
[14:07:19] <fragalot> how can you have a PID loop if you don't have feedback?
[14:07:25] <fragalot> sorry I missed the first half of the conversation :P
[14:07:28] <pcw_home> (ust FF1)
[14:07:35] <pcw_home> just ff1
[14:09:37] <automata> fragalot: pcw is helping me with setting up a electronic gear using stepgens with the ability to change the gear ratio on the fly
[14:09:55] * fragalot slowly backs away
[14:09:56] <pcw_home> so command input to both PID loops is a position profile
[14:09:58] <pcw_home> FF1s are scaled so the correct velocities are output on each
[14:10:00] <pcw_home> feedback is scaled as well so a little P term keep them from wandering apart
[14:10:31] <pcw_home> (scaled and offset-ed)
[14:11:11] <automata> Both PID loops??
[14:11:31] <pcw_home> (assuming parametric)
[14:11:44] <pcw_home> master slave does the same with just one
[14:12:24] <automata> MAster would not need a PID... if there is an error in the master velocity the slave should still follow it...
[14:12:34] <pcw_home> yep
[14:12:39] <automata> so I was thinking that only the slave gets a PID...
[14:13:28] <pcw_home> so you can try it open loop with just FF1 doing the scaling
[14:15:33] <automata> Yup.. No PID on master at all. just connect the velocity-cmd pin of the stepgen to the spindle-speed passed through a limit2
[14:16:52] <automata> slave PID gets pid.command = (masterpos-masteroffset)*M
[14:17:27] <automata> pid.feedback = (slavepos - slaveoffset)*N
[14:19:13] <automata> and the velocity-cmd to the slave stepgen = pid.output + master.vel_cmd *N/M
[14:19:52] <automata> add the vel_cmd from outside the PID... not sure if it a good idea though...
[14:24:16] <automata> I now see that FF1*N is the same as master.vel_cmd*N/M
[14:25:43] <pcw_home> Yeah there are enough different places to do the same thing its easy to get confused
[14:25:51] <automata> for the slave PID connect the pid.command-deriv pin tooo
[14:26:16] <automata> as the commanded velocity.
[14:27:03] <automata> This is getting complicated enough to deserve its own special component...
[14:29:03] <automata> the sample and hold for the offset + parametric scaling + pid... i think it would make a neat component.. for an electronic gear
[14:31:02] <automata> any ideas on how to test this whiz-bang?
[14:32:03] <automata> how would I find a missing pulse (if there were one)?
[14:32:41] <automata> I guess monitoring the PID.error would help
[14:33:37] <pcw_home> well if you had encoders you could check all the way to the mechanics, but the stepgens do not lose or gain steps (the position register is an accurate representation of generated pulses)
[14:34:50] <pcw_home> yes your PID error will check you tuning, but tuning _should_ be minimal (like I said this is 99.999% feed forward)
[14:35:25] <automata> That is what I thought... that the position-fb for the stepgen uses the subcounts too and that would give a very accurate description of the current position.
[14:36:08] <pcw_home> Yeah the PID comp should never see significant errors. its just to correct long term drifts
[14:36:49] <pcw_home> 'phase locking'
[14:37:05] <automata> that is the term I was looking for...
[14:38:52] <automata> I think using the position-scale and position-fb and M, N values we could arrive at a theoretical limit for pid.error in case of a one pulse error
[14:39:14] <automata> then monitor the pid.error for excursions outside this range
[15:01:21] <andypugh> I couldn't resist at less than £1 each:
http://www.ebay.co.uk/itm/SELECTION-OF-LATHE-TOOL-HOLDERS-33-IN-TOTAL-/140889925131
[15:01:59] <andypugh> (Though it is anyone's guess what they all are)
[15:02:12] <tjb1> You couldn't resist huh…
[15:02:36] <cradek> that's for a weird lathe
[15:03:00] <andypugh> I <heart> badly advertised auctions.
[15:03:04] <Tom_itx> andypugh you still after those tool holders?
[15:03:16] <andypugh> Tom_itx: Not any more, I just paid.
[15:03:21] <Tom_itx> ahh
[15:04:11] <cradek> those are for at least 4 different machines
[15:04:35] <Tom_itx> see then he'll have the tooling so all he needs to do is hunt down those machines and bid on em
[15:04:52] <andypugh> Yes, BT30, 30Int, 40Int, and the one with the semi-cylindrical slot in the side
[15:05:15] <cradek> does int = nmtb?
[15:05:23] <andypugh> I figure on keeping the ones that fit my machine (the 30 taper) and selling/giving away the rest.
[15:05:37] <andypugh> cradek: Not quite.
[15:05:39] <cradek> I think they're cat30, not bt30
[15:06:17] <andypugh> The pull-stud ones?
[15:06:42] <cradek> the long skinny pull stud ones are cat
[15:07:15] <andypugh> I reckon I can use any 30-taper.
[15:07:35] <cradek> if you don't have a tool changer that depends on the flange, yes, IF you can find the right pull stud
[15:07:44] <cradek> cat have an inch thread, bt have metric
[15:08:17] <cradek> there's a bt40 (50?) in there
[15:08:52] <andypugh> I make my own pull-studs for my own drawbar ;-)
[15:09:01] <mrsun> http://sphotos-c.ak.fbcdn.net/hphotos-ak-snc7/598467_10151260931403648_451078537_n.jpg a little machine ive had standing in the basement for a couple of years and totaly forgot about :P
[15:09:40] <andypugh> mrsun: It's a death trap. No guards. Let me take it off your hands.
[15:09:48] <mrsun> haha :P
[15:10:27] <mrsun> with allt he stuff i bought at the same time i think i gave about 55usd for it =)
[15:10:58] <mrsun> some damage to the table and some greace thingies i need to fix up but other then that a quite nice machine, just a belt and replace motor cable and im golden =)
[15:11:02] <mrsun> 2 jaw chuck etc :P
[15:14:52] <andypugh> Is a 2-jaw chuck much use?
[15:17:48] <mrsun> dont know :P
[15:17:56] <mrsun> its what is on it and i dont know how its put in there =)
[15:21:45] <andypugh> Ah, 2-jaw drlll-chuck? I think those are normally for this style of drill shank:
http://www.leevalley.com/us/images/item/woodworking/drilling/50j0501s3.jpg
[15:24:22] <mrsun> mm
[15:24:25] <mrsun> i guess they are
[15:24:33] <mrsun> dont know, can they hold round drills? :)
[15:24:39] <mrsun> i want to get this machine working =)
[15:25:01] <mrsun> just need to fix a big chunk that is damaged on the table ... else its in mint condition
[15:25:09] <mrsun> maybe check the bearings for the motor, might just need new greace
[15:26:11] <mrsun> and a cleanup/rust removal and it will be very nice =)
[15:29:11] <andypugh> I have held round drills in them, but not well.
[15:29:48] <mrsun> hmm ok =)
[15:30:14] <andypugh> The firt thing to do is probably to unscrew the outer shell all the way, swear when you lose the springs, decide that next time you will hold a plastic bag over the chuck when unscrewing it, and then see if the threads are integral with the drill spindle.
[15:33:27] <mrsun> springs ?
[15:34:02] <andypugh> There are always springs if you assume otherwise, and an absence if you take precautions.
[15:34:04] <skunkworks> You have to be a programmer/guru to use linuxcnc...
http://groups.yahoo.com/group/mach1mach2cnc/message/137669
[15:35:42] <andypugh> I bet there is a file, though.
[15:36:15] <andypugh> (or a database to be queried in a more elegant way than that)
[15:36:34] <cradek> some in our midst think it's a silly anachronism to have the tool table be a normal text file.
[15:37:16] <andypugh> I do.
[15:37:48] <andypugh> I think that anyone who thinks they need a printout of their tool table is probbaly wrong.
[15:39:02] <andypugh> A plain-text file is one way to do it, though. But that should be the "live copy" not some artificially-limited structure embedded in NML messages.
[15:39:03] <cradek> it would be interesting to know what problem he was trying to solve
[15:41:05] <andypugh> I think I might build a Mach machine, just to prove something. I am not sure what. Perhaps kissing a man would prove the same thing and be easier to forget?
[15:47:55] <andypugh> cradek: I am going to suggest that 30INT and NMTB30 might differ subtly, as I believe NMTB30 defines a second max diameter under the flange, and this 30-INT doesn't have that:
http://www.ebay.co.uk/itm/ER32-Collet-chuck-30-int-taper-with-spanner-/251189974173?pt=LH_DefaultDomain_3&hash=item3a7c16d49d
[15:51:34] <andypugh> (random observation. eBay searches for 30 INT turn up a fair bit of gay paraphenalia, whereas my more regular search for BT30 turns up bow ties.) Err, that should not be read in conjunction with my previous comment.
[15:53:06] <Guest____> Hey guys, I'm new to Linux CNC and I am trying to get my MLE-40 laser cutter working with it. Anyone around to give me a small helping hand?
[15:53:16] <seb_kuzminsky> what's your question, Guest____
[15:53:35] <Guest____> seb_kuzminsky: Is there already a configuration made for the device?
[15:53:50] <Guest____> their documentation references linuxcnc but then I don't see any matching configuration file
[15:54:03] <seb_kuzminsky> not that i know of. certainly it's not one of the configs we distribute
[15:54:13] <seb_kuzminsky> ooh! can you send a link to their docs?
[15:54:39] <Guest____> http://www.fullspectrumengineering.com/files/FSL_40w_Hobby_Laser_Manual.pdf
[15:54:43] <Guest____> seb_kuzminsky ^^
[15:54:48] <Guest____> see page 25
[15:54:52] <Guest____> they reference linuxcnc directly
[15:54:54] * seb_kuzminsky clicks
[15:55:42] <icee> Guest____: how's your experience with the FSL guys been?
[15:55:56] <cradek> they need a thicker string between their dixie cups
[15:55:59] <icee> Guest____: have you used retinaengrave and how is that?
[15:56:09] <Guest____> icee: First day with the laser, it was donated to me :)
[15:56:19] <andypugh> Cute machine, but seems to have absolutely no distance between the table and the tool.
http://www.ebay.co.uk/itm/Centec-2A-Universal-Milling-Machine-/321028440026
[15:56:22] <Guest____> So, no I didn't get retnaengrave with it
[15:56:29] <icee> cradek: you have experience with them?
[15:57:03] <icee> i'm actually in the kickstarter for their next gen hobby laser.. i knew they were a kinda-crummy vendor going into it, but have heard mostly good stuff about their actual product
[15:57:04] <cradek> no
[15:57:35] <Guest____> icee: do you use a FSL?
[15:57:43] <icee> Guest____: waiting for mine
[15:57:47] <Guest____> oh nice
[15:58:03] <andypugh> Eeew! They can't kern. Repulsed by page 1
[15:58:12] <Guest____> ya, I didn't get retina engrave because the person who gave us the laser didn't give us the disk
[15:58:30] <icee> this one
http://fslaser.com/products/lasers/newhobby
[15:58:30] <seb_kuzminsky> Guest____: yeah, i see that they say to come talk to us, but i've never heard of their product before
[15:58:45] <Guest____> seb_kuzminsky: that's quite odd :/
[15:59:05] <Guest____> seb_kuzminsky: any configuration you can think of that might work for the laser?
[15:59:09] <Guest____> Or should I contact them?
[15:59:24] <cradek> they pretty clearly disclaim any responsibility for helping you
[15:59:31] <Guest____> (well rather… continue waiting for them to get back to me)
[15:59:38] <andypugh> How hard can it be?
[16:00:03] <Guest____> andypugh: I'm a big unix guy, but I haven't touched linuxcnc before now. So a bit of a learning curve
[16:00:32] <andypugh> Sorry, I was being sarcastic
[16:00:46] <Guest____> haha alrighty :)
[16:01:47] <andypugh> It would be fairly easy if the manual hinted at the connector pinout
[16:02:11] <andypugh> it doesn't seem to.
[16:02:53] <cradek> that is certainly information you should expect to receive with the machine
[16:03:40] <andypugh> It is possible to work it out, by a brute-force exploration in stepconf.
[16:03:47] <seb_kuzminsky> the manual says you can control the machine through its parallel port, but it lacks pinouts and timing information
[16:04:20] <seb_kuzminsky> if you get that from the vendor we can try to set up a linuxcnc config for it, but without that information it's going to be annoying and time consuming
[16:04:25] <andypugh> Which might not be that hard, one axis at a time, initially assuming that step and direction for any one axis are on adjacent pins.
[16:05:02] <AlJaMa> Back, I was guest
[16:05:37] <AlJaMa> Jumped on the phone and got a nick
[16:05:57] <seb_kuzminsky> AlJaMa: if i were you, i would contact the hardware manufacturer and ask for the pinout & timing information for the parallel port
[16:06:10] <andypugh> <stalk> You appear to be a student, so perhaps have the time for the logic-puzzle of guess-the-pinout?
[16:06:57] <andypugh> On the plus side, you can't break anything. Unless they have been very careless with the laser-tube PWM input, I guess.
[16:07:37] <DJ9DJ> gn8
[16:07:43] <AlJaMa_> Alrighty
[16:07:47] <seb_kuzminsky> AlJaMa: hey, i just noticed you're at colorado.edu
[16:07:51] <seb_kuzminsky> i live in boulder
[16:07:53] <AlJaMa_> Yep :)
[16:08:05] <AlJaMa_> Oh incredible! Ya I'm a student here
[16:08:11] <seb_kuzminsky> cool!
[16:08:29] <seb_kuzminsky> if you get the pinout & timing info from the vendor, i'd be happy to meet with you some time and help you get the laser running
[16:08:54] <andypugh> Bingo!
http://www.fullspectrumengineering.com/laser%20connection.html
[16:09:15] <seb_kuzminsky> thanks andypugh :-)
[16:10:13] <AlJaMa> Incredible! So is anyone willing to help me to write a config for it?
[16:10:20] <andypugh> (Who says support sucks with Open Source?)
[16:10:20] <seb_kuzminsky> yeah, i'll help
[16:11:05] <seb_kuzminsky> is the machine at CU somewhere? or somewhere else in boulder?
[16:11:23] <seb_kuzminsky> AlJaMa_: you keep bouncing and probably missing messages
[16:11:37] <AlJaMa> I'm still here :)
[16:11:43] <AlJaMa> Had to transfer buildings
[16:11:48] <seb_kuzminsky> ok
[16:11:50] <AlJaMa> The machine is at CU
[16:12:03] <AlJaMa> there we go
[16:12:04] <seb_kuzminsky> in the engineering center somewhere?
[16:12:28] <AlJaMa> no actually it's part of a new program, currently sitting in a closet unused
[16:12:37] <AlJaMa> soooo I was tasked with getting it running
[16:12:42] <seb_kuzminsky> cool
[16:12:58] <seb_kuzminsky> do you have a computer with linuxcnc installed? does the laser have power?
[16:13:04] <AlJaMa> yep, and yep :)
[16:13:46] <seb_kuzminsky> do you have the parallel port cable?
[16:14:03] <AlJaMa> I currently do not have it connected, I actually just ran to class
[16:14:12] <AlJaMa> (thus the reason i was jumping so much)
[16:14:34] <seb_kuzminsky> do you mean you have the parallel cable but it's not plugged in?
[16:14:41] <AlJaMa> not on me, but I have it
[16:14:46] <seb_kuzminsky> ok yeah
[16:14:53] <seb_kuzminsky> sounds like you're 90% done then ;-)
[16:15:09] <seb_kuzminsky> plug the cable in, poke those numbers andypugh found into stepconf, and hit the test button
[16:15:14] <AlJaMa> great! ya it was just the configuration and setup that got me.
[16:15:17] <AlJaMa> agh alright :)
[16:15:33] <mrsun> http://media.photobucket.com/image/recent/satxrod/IMGP1882.jpg heh .. "arc of shame" =)
[16:15:54] <andypugh> I saw somewhere else in their forum that laser PWM was pin 15.
[16:16:46] <andypugh> But that says 17.
[16:18:23] <AlJaMa> andypugh: for the laser I have?
[16:18:29] <andypugh> Yes
[16:19:52] <andypugh> Get it moving first, though. Their advice on the pinout page is sound, you probably want to boot the PC before the laser
[16:20:19] <AlJaMa> andypugh: the picture you found… I'm trying to figure out if the labels are are showing the pin above it or below it
[16:20:38] <AlJaMa> what do you think?
[16:20:49] <andypugh> Yes, so am I :-)
[16:21:18] <andypugh> It's probably easy enough to work out, several pins are obligate grounds.
[16:22:33] <AlJaMa> what would the machine units be?
[16:22:40] <AlJaMa> (I'm using stepconf
[16:23:01] <andypugh> Your choice
[16:23:14] <AlJaMa> ah alright
[16:24:22] <seb_kuzminsky> just don't tell anyone what you choose, or they'll tell you you chose wrong
[16:24:57] <andypugh> 1000 steps per inch is the number they give, bit you could choose to base the machine in a rational and absolute measurment system if you preferred :-)
[16:27:05] <andypugh> Though as the inch is now defined in terms of the meter, defined in a universe where the speed of light is exactly 299792458m/s it is all a bit moot.
[16:27:33] <seb_kuzminsky> indeed
[16:27:40] <tjb1> Inch or go home :)
[16:28:17] <AlJaMa> hah this pinout is bad....
[16:28:25] <AlJaMa> I have no clue if it's pin above or pin below
[16:28:25] <seb_kuzminsky> how so?
[16:28:36] <andypugh> AlJaMa: If you don't know, it is a simple G-code instruction to switch units, so not that critical.
[16:29:15] <seb_kuzminsky> compare to this pic:
http://www.mr-d.ca/Tutorials/Turing/interfacing.html
[16:29:39] <andypugh> Pins 18 to 25 are always GND. That probably removes the ambiguity
[16:30:49] <AlJaMa> ah yes that does
[16:31:07] <seb_kuzminsky> the number and the label are just above the line leading to the pin location
[16:31:19] <AlJaMa> yep
[16:31:24] <andypugh> As is so often the case, Wikipedia is a good reference:
http://en.wikipedia.org/wiki/Parallel_port
[16:31:53] <AlJaMa> hmmm so if this laser has their USB interface card, any idea if it would be worth trying to interface linuxcnc with that?
[16:31:59] <AlJaMa> or should I for sure go with the parallel port?
[16:32:05] <seb_kuzminsky> go with the parllel port
[16:32:19] <seb_kuzminsky> usb doesnt work well for motion control with linuxcnc
[16:32:24] <andypugh> Yes, I have a very good idea that it would be a total waste of your time to try to use the USB prt :)
[16:33:55] <andypugh> However, if you can find the original USB driver system (which may be specialist hardware) then it might well work better with that particular machine than LinuxCNC does. It pains me to say it, but LinuxCNC isn;t optimal for laser rastering.
[16:35:28] <Jymmm> chinese laser?
[16:35:30] <seb_kuzminsky> andypugh: do you know what the issues are that make it suboptimal? is there a wiki page on this stuff somewhere?
[16:36:28] <seb_kuzminsky> Jymmm: it's by "Full Spectrum":
http://fslaser.com/
[16:37:11] <andypugh> The main issue is maintaining a constant scan speed while modulating laser power. Dither patterns will generally have to be a white move then a black move, all rather short, and that gets into the lookahead limit.
[16:37:16] <Jymmm> seb_kuzminsky: Yeah, chinese laser =)
[16:37:46] <tjb1> Isnt FSL the one that imports chinese garbage and then resells it
[16:38:09] <tjb1> Pay a bunch of money for "support" and "US help" and its chinese garbage
[16:38:31] <Jymmm> tjb1: There are some good chinese lasers now.
[16:38:49] <PCW> Probably a job for halsampler and a comp that doles out the data based on the current position
[16:38:58] <tjb1> Gweike seems pretty popular
[16:39:08] <PCW> halstreamer I should say
[16:39:25] <andypugh> I did make a start on a specialist rastering setup, with a userpace GladeVCP panel loading image data into shared memory for a realtime specilaist movement/laser component to read. Then I got distracted by trying to make the raster generator finite-jerk, and then I did something else...
[16:39:59] <seb_kuzminsky> the difficulty is in getting a correct raster pattern out of the laser as you scan it?
[16:40:10] <PCW> probably easier to just use trapezoidal and over scan
[16:40:10] <andypugh> It wasn't looking very difficult at all, actually.
[16:40:48] <andypugh> PCW: It was going to over-scan anyway, it has to. The speed when the laser is on needs to be absolutely constant
[16:40:57] <tjb1> JT-Shop: Have you done any wiggle piercing?
[16:41:01] <PCW> Generic gcode for raster
[16:41:03] <PCW> halstreamer--> comp
[16:41:51] <andypugh> PCW: Graster is a setup rather like that, but it seemed over-complex to me. Why would there be any G-code involved at all?
[16:42:16] <andypugh> seb_kuzminsky: The laser speed needs to be constant, that's where the fun starts.
[16:42:42] <PCW> Just because the exact same system can do modulated line graphics
[16:42:45] <seb_kuzminsky> the speed with which you move the laser across the work piece?
[16:43:19] <seb_kuzminsky> that's what needs to be constant, so that the delivered power is what the laser pwm is trying to do
[16:43:22] <seb_kuzminsky> makes sense
[16:43:58] <seb_kuzminsky> what if you treat the laser pwm as another axis, it would ramp up and down along with travel speed...
[16:44:21] <Jymmm> seb_kuzminsky: more like rpm
[16:44:25] <PCW> for raster though, overscan is probably better
[16:44:35] <andypugh> seb_kuzminsky: Yes. Otherwise you tend to get an over-burn at the points where the speed stutters. Using the motion-synched analogue out (M66?) should help, but Z and S are a problem.
[16:44:39] <Jymmm> PCW: what do you mean by 'overscan'?
[16:45:40] <PCW> enough ramp up and ramp down distance so the laser spot is moving at a constant speed when burning
[16:45:51] <tjb1> andypugh: M67
[16:45:55] <tjb1> http://linuxcnc.org/docs/html/gcode/m-code.html#_m67_synchronized_analog_output_a_id_sec_m67_analog_output_a
[16:46:56] <andypugh> X and Y are forced to pause while Z accellerates (even if i isn't a real Z). I think spindle speed has a different problem. But even with M67 (thanks tjb1) any change in intensity is a new move, and put too many inside your decel distance and things slow down.
[16:47:03] <Jymmm> PCW: Using MY laser as example... It's NEVER consistant; the PWM changes according to the artwork, for say things like greyscale 3D engraving.
[16:47:35] <andypugh> Jymmm: Are you interested in developing the rasterer that I lost interest in
[16:47:39] <AlJaMa> hey, because I am only doing output with the serial port, am I not going to be able to see a realtime display or what the laser is doing?
[16:47:45] <AlJaMa> Or is that based off of the gcode?
[16:47:53] <AlJaMa> and not actual machine position?
[16:48:00] <seb_kuzminsky> AlJaMa: you'see see exactly what the laser is doing
[16:48:06] <PCW> just saying thats not optimum for pictures (nonlinearities)
[16:48:25] <AlJaMa> seb_kuzminsky: through G-code interpretation?
[16:48:32] <seb_kuzminsky> based on what the gcode is asking for, not based on actual feedback from the machine, since yes, you're only doing output through the parallel port, not input
[16:48:32] <Jymmm> andypugh: My laser acts like a printer; I just print to it from whatever application I'm working from atm.
[16:48:38] <seb_kuzminsky> AlJaMa: yep :-)
[16:48:44] <AlJaMa> great :)
[16:48:59] <Jymmm> andypugh: It's the print driver that controls the settings.
[16:49:11] <AlJaMa> Jymmm: what laser do you have?
[16:49:18] <Jymmm> ULS M-300
[16:49:55] <tjb1> Couldnt you get around this by having the laser work in one direction like some of the engravers?
[16:50:01] <tjb1> Fire it when needed
[16:50:04] <Jymmm> Except I have it on a ethernet print server.
[16:50:34] <AlJaMa> does intensity of color/bitmap determine intensity of laser?
[16:51:35] <Jymmm> bitmap, as is in raster graphics? (JPG, PNG, BMP, etc)
[16:52:11] <andypugh> AlJaMa: Get the machine working first. If LinuxCNC doesn't do exactly what you want, that doesn't mean that it never will. There is definitely work ongoing to improve lookahead. And somebody (maybe even me) might finish the rastering system I was working on. I just don't have a laser to practice with.
[16:52:15] <Jymmm> I do very very little raster graphics; I primarily stay with/use vector graphics.
[16:52:41] <AlJaMa> andypugh: Oh I was just asking for Jymmm's
[16:52:50] <tjb1> I mean run the laser like this -
https://www.youtube.com/watch?v=vrFD5h4U408
[16:54:04] <Jymmm> AlJaMa: You might look to see what they offer...
http://www.lightobject.com/Commerical-DSP-CO2-Laser-Engraving-Cutter-Controller-Support-CorelDraw-AutoCad-P321.aspx
[16:55:01] <Jymmm> It's a controller in one with ethernet
[16:55:41] <AlJaMa> and the last question I can think of right now is how do you use a Parallel Port driver from USB? (I mean… no computers have parallel ports anymore :) )
[16:56:23] <andypugh> You need a real parallel port. And Lots of PCs still have them.
[16:56:50] <andypugh> Or you can use a PCI card.
[16:57:27] <andypugh> (Though, if you want to go PCI, then there are better/faster options than parallel port that can emulate the same pinout)
[16:57:36] <Jymmm> AlJaMa: look at the link I provided, even has a video
[17:00:17] <Jymmm> AlJaMa: If I was retrofitting a laser, that is what I would use.
[17:02:58] <Jymmm> poof!
[17:14:01] <tjb1> Jymmm: Now make him reappear
[17:33:02] <JT-Shop> poof
[17:41:21] <tjb1> Anyone in here use Draftsight?
[17:44:35] <jdh> sometimes
[17:44:37] <Jymmm> tjb1: You'll have to purchase to the next show to see that.
[17:44:52] <tjb1> I cant get a setting to stay...
[17:44:59] <jdh> like what
[17:46:06] <tjb1> Drawing Settings - > Display - > Coordinate System Icon, it resets back to displaying it when I restart
[17:46:44] <jdh> which version?
[17:46:59] <tjb1> V1R3
[17:47:08] <tjb1> I just updated it
[17:48:21] <jdh> bummer.
[17:48:33] <tjb1> Does it stick on yours?
[17:48:34] <jdh> does the same here, file a bug report.
[17:51:02] <jdh> open the default template, turn it off, save the template
[17:54:06] <tjb1> Turn it off?
[17:54:08] <tjb1> oh
[17:54:11] <tjb1> Got it...
[18:03:18] <ssi> well dammit... I have a broken HNC again
[18:03:47] <ssi> my air lines on that side of the shop are black iron, and they're rotting... I've been out of the shop for awhile, and the air lines are blowing clouds of black dust
[18:03:55] <ssi> and I think it contaminated the pneumatics on the HNC... the turret isn't working
[18:04:01] <ssi> it's like the air motors don't have enough power to move it
[18:04:14] <ssi> anyone have any thoughts on how I can go about decontaminating the pneumatics?
[18:06:28] <tjb1> Filters are probably in the valves
[18:06:52] <ssi> in the solenoids you mean?
[18:07:12] <ssi> there's a master air filter/oiler on the machine, but it's ancient. I obviously need to put a better filter on it
[18:08:40] <tjb1> Yes, you may be able to find a screen on the input to the solenoid valves
[18:09:16] <tjb1> I saved over top of the standard template and it worked jdh
[18:09:19] <ssi> I'll look into it
[18:33:42] <t12> swin 4
[18:53:08] <tjb1> What do you cut the hobbed sections with Tom_itx ?
[18:53:31] <tjb1> A tap?
[18:53:33] <Tom_itx> i used a 3mm tap
[18:53:56] <tjb1> Did you make the diameter so they overlap perfect?
[18:54:18] <Tom_itx> i tried
[18:54:30] <Tom_itx> ghetto calculations
[18:54:43] <tjb1> Heh, have you seen the qu-bd? It drives with a gear
[18:54:50] <Tom_itx> nope
[18:55:25] <tjb1> http://www.qu-bd.com/gallery/
[18:56:26] <Tom_itx> easy way to make one for sure
[18:59:03] <tjb1> I wish I had a lathe and mill
[19:02:50] <hdokes> say tjb1 ... yo know if there is any video showing that head in operation?
[19:03:02] <hdokes> I have a mill and two lathes
[19:03:19] <hdokes> actually... guess if I had to count... I have 3 mills and 3 lathes
[19:03:55] <tjb1> Here is their old kickstarter -
http://www.kickstarter.com/projects/qu-bd/open-source-universal-3d-printer-extruder-dual-ext
[19:05:03] <tjb1> http://www.youtube.com/watch?v=-5g3K6ivM1I
[19:07:44] <tjb1> Good video showing it and their cube -
http://www.youtube.com/watch?v=Kjy9ykduN5E
[19:13:38] <hdokes> cool
[19:14:42] <gmouer> trying to setup a M168 code but it does not seem to function, does not throw any errors, can somebody peek and see what I did wrong perhaps?
http://pastebin.com/5TYWEuSc
[19:16:15] <gmouer> it just disconnects the spindle fwd and rev and reconnects them flipped (for rear mounted tuning tools on lathe)
[19:18:22] <andypugh> That seems like an elaborate way to do it.
[19:18:41] <tjb1> Why can't you call M4?
[19:19:34] <gmouer> Its a gang tool lathe, I implemented G68/G69 to flip the coordinate system for rear mounted tooling, it would be nice to have the spindle reverse function at the same time
[19:20:06] <gmouer> that way I can use bigJohns ngcgui routines unmodified
[19:20:47] <andypugh> I think you could do it all in HAL.
[19:21:14] <gmouer> after I get M168 and M169 working I plan on putting that in the G58/G69 subroutine so its automatic
[19:21:37] <andypugh> Or just setp the scalemin and scalemax of the analog pins the other way round
[19:22:14] <gmouer> but I need to switch back and forth during a gcode program, when I go from front to rear tuning tools
[19:22:33] <andypugh> Aye, I got that part.
[19:22:38] <gmouer> I don't understand why the code I did does not work?
[19:23:07] <andypugh> Neither do I, but I don't like rewiring HAL if it is avoidable.
[19:24:21] <andypugh> You could set up a mux2 into the pwm scale, and setp the input in an M100
[19:24:22] <gmouer> the M code example in the doc writes to a hal pin to actuate a collet closer, I followed that example
[19:25:13] <andypugh> Yes, writing a value to a HAL pin (or even a parameter) is fine. Actually rewiring is fine too, mainly, but the pins might point at random memory briefly during the swap.
[19:25:54] <gmouer> wouldn't that require rewiring within the hal again when I switch front/rear tools?
[19:26:52] <gmouer> the spindle is off when I issue the M168, and then a few seconds later I try a M3 and the spindle goes the same direction it did before the M168 call
[19:27:15] <andypugh> Maybe. I guess you are using a VFD with forward/reverse contacts
[19:27:17] <gmouer> its like the signal delete and then the net pin connections are not happening
[19:27:24] <gmouer> yes, a vfd
[19:28:07] <gmouer> what is strange is the M168 takes on the MDI line, no errors, but M3 remains unchanged, same direction
[19:28:31] <gmouer> I called M170 for kicks, (M170 not assigned), and that does throw a error
[19:28:35] <andypugh> Does Machine->Show HAL Config show the old wiring or the new wiring?
[19:28:45] <gmouer> old
[19:29:09] <andypugh> Try #!/bin/bash ?
[19:29:56] <gmouer> I am not familiar with bin/bash at all, I just copied that line from the sample file
[19:30:31] <gmouer> I have no idea what bin/bash is all about, searched for about a hour the other night with no luck
[19:30:41] <andypugh> It's the terminal
[19:31:12] <andypugh> (technically the Bourne Again SHell)
[19:31:16] <gmouer> I haee #!/bin/bash as the first line in my M168 file
[19:31:45] <andypugh> No, you have #!bin/bash
[19:32:03] <andypugh> (Not that I know which is correct)
[19:32:36] <gmouer> isn't that the same as you typed a few lines back just now?
[19:33:07] <andypugh> Absolute v relative path
[19:33:51] <r00t4rd3d> fuck I just got called back to work
[19:34:44] <gmouer> oooooooooooo !!! ok,, you have a / character just before bin and I don't
[19:34:49] <gmouer> I am going blind LOL
[19:36:26] <andypugh> I just tried it, and the / helped
[19:36:35] <gmouer> I bet you hit it Andy! I just relooked at the M code docs and their sample, it does indeed have the / ahead of bin and I left it out
[19:36:57] <andypugh> You also need the file to be in the right place, and to be executable
[19:37:30] <gmouer> I did that, its in the NC_files folder and set as executable
[19:37:47] <andypugh> bash is a program, it lives in /bin/ Not sure if you realise that?
[19:37:57] <gmouer> it does see the file because it does not throw a error, if I type the nonexistant M170 it throws a error
[19:38:11] <gmouer> no, I did not realize that
[19:38:31] <andypugh> It's also what interprets your command line entries (unless you choose to use something else, like sh or tcsh
[19:39:04] <gmouer> but, doesn't the # on the start of that line make it a comment that is ignored anyways
[19:39:36] <r00t4rd3d> you probably dont even need #!/bin/bash in there.
[19:39:43] <andypugh> Yes, but then #! is a "magic comment" that means "run this file using this interpreter"
[19:39:53] <gmouer> ahhhhhhh
[19:40:23] <gmouer> great, I have enough trouble doing easy things, now we are getting into magic LOL
[19:40:36] <andypugh> You can use #!/bin/python for Python code, or #!/bin/octave for Matlab scripts..
[19:41:12] <gmouer> boy, I hunted for a long time the other night for such information and didn't find a hint
[19:42:30] <andypugh> http://en.wikipedia.org/wiki/Shebang_(Unix)
[19:44:03] <tjb1> Can you unlink and relink them?
[19:44:23] <andypugh> I think it will work with an absolute path
[19:44:25] <tjb1> I dont know that much about HAL but can you delete a pin that is/was currently in use?
[19:44:34] <andypugh> With delsig, yes
[19:44:42] <gmouer> I think you are right andy, the missing / is causing all the trouble
[19:47:00] <r00t4rd3d> in your terminal type echo $0
[19:47:04] <r00t4rd3d> thats a zero
[19:47:19] <r00t4rd3d> whats the output?
[19:48:21] <andypugh> I was testing with an M101 that says: #!/bin/bash
[19:48:21] <andypugh> echo Hello
[19:48:22] <andypugh> exit 0
[19:49:39] <gmouer> so /bin/bash is the terminal console as a command intreperter correct?
[19:49:46] <andypugh> Yes
[19:50:10] <r00t4rd3d> and is a redundant line on most machines
[19:50:11] <andypugh> So anything that works in the terminal will work in that script.
[19:50:22] <gmouer> I am learning, coming from Mach3 its a steep curve, but sooooooooo worth it
[19:50:48] <r00t4rd3d> if echo $0 tells you your using bash, no need for #!/bin/bash
[19:51:11] <andypugh> Well, this is the Linux equivalent of Mach Basic macros
[19:51:38] <gmouer> yea, but ooooo so much more power
[19:51:44] <andypugh> r00t4rd3d: It does no harm though, and might save problems if you wanted to change your default shell.
[19:51:52] <r00t4rd3d> the only time you need to define a shell is when you use something other then default
[19:52:06] <gmouer> I am constantly amazed at the power of linuxcnc and its ability to handle different hardware
[19:52:24] <r00t4rd3d> put a EA game in the dvd drive
[19:52:33] <gmouer> and, the terminal is the default?
[19:52:57] <r00t4rd3d> no the terminal is access to the shell
[19:53:07] <r00t4rd3d> the shell being bash
[19:56:09] <gmouer> I got the gangtool lathe all retrofitted and happy with it, this is just some finishing touches
[19:56:19] <andypugh> I just ran sh inside tcsh inside bash. Just for fun :-)
[19:56:37] <r00t4rd3d> lol
[19:57:22] <andypugh> I would have done it all by ssh-ing to the linuxCNC machine and back again, but I just shut them all down to go to sleep.
[19:57:27] <gmouer> thanks so much once again, andy
[19:57:53] <andypugh> No problem, I learned something by answering the question :-)
[19:58:21] <andypugh> Goodnight chaps.
[19:58:29] <gmouer> night Andy
[20:12:00] <tjb1> Hello r00t4rd3d
[20:32:46] * r00t4rd3d Quits: r00t4rd3d (connection rest by peer)
[20:40:44] <tjb1> Liar.
[20:40:48] <tjb1> I see you r00t4rd3d
[20:44:12] <r00t4rd3d> my reset typo didnt help me any
[20:44:50] <tjb1> And its usually like this "servos4ever left the chat room. (Quit: ChatZilla 0.9.85 [SeaMonkey 2.0.11/20101206162726])"
[20:45:20] <r00t4rd3d> probably on garbage clients
[20:45:38] <r00t4rd3d> i dont see any join/parts/quits :D
[20:48:45] <tjb1> Thats the problem with android...
[21:39:39] <tjb1> 1 more program to write for java!
[21:41:41] <jdh> woohoo!
[21:41:51] <jdh> I wrote some python this weekend. It was interesting.
[21:44:41] <tjb1> There is probably a reason this is the last one out of 12...
[21:46:59] <tjb1> I heard python is easy compared to java
[21:47:04] <tjb1> How true is that?
[21:49:22] <jdh> I thought it was
[21:49:48] <jdh> but, my python was kind of hacky... no classes, just straight code.
[21:50:01] <jdh> no self.anything
[23:50:12] <tjb1> How does this happen?
http://sphotos-b.xx.fbcdn.net/hphotos-ash3/542592_4666208209167_1518896048_n.jpg compare the R in simulator
