#linuxcnc | Logs for 2013-08-27

[00:41:38] <nspielbe> is there a way to figure out the encoder rev/inch empirically from unknown hardware
[00:47:45] <CaptHindsight> rotate the encoder one rev and count the number of pulses
[00:49:00] <nspielbe> no not pulses per revolution- revolutions per inch- it should be a factor of the motor gearing
[00:51:29] <CaptHindsight> yes
[00:52:12] <nspielbe> but i dont know how the motors are geared
[00:52:22] <CaptHindsight> why is it a mystery? you don't have access to the motor?
[00:52:34] <nspielbe> i do
[00:52:43] <nspielbe> but i dont have a datasheet or anything
[00:53:24] <CaptHindsight> can't you count the number of turns while moving it an inch?
[00:53:53] <kengu> that is what I would do
[00:53:56] <nspielbe> while moving what an inch?
[00:54:05] <CaptHindsight> what is actually moving an inch?
[00:54:20] <nspielbe> yeah sorry
[00:54:58] <CaptHindsight> whats the motor turning? a ball or lead screw? a rack?
[00:56:00] <nspielbe> a robot arm joint
[00:57:56] <CaptHindsight> this for the SCARA?
[00:59:27] <nspielbe> yeah
[00:59:41] <nspielbe> im trying to code the ini but i think its going to be super hard to calibrate the scaling
[02:27:12] <DJ9DJ> moin
[03:04:23] <Loetmichel> mornin'
[03:34:44] <RyanS> I don't get it.. What does the square block achieve? http://www.cnczone.com/forums/mini_lathe/113580-camlock_tail-stock-2.html#post834815
[03:39:56] <archivist> it raises the force to the cam
[03:40:08] <archivist> clamping force
[03:41:48] <RyanS> yeah but wouldn't the piston be sufficient by itself? it's not like the square block is attached to the tail stock
[03:42:42] <archivist> it has compressive force when clamped.
[03:43:36] <archivist> cam rotates and lifts the piston against the block
[03:43:38] <RyanS> oh, piston goes upward, and block goes down
[07:59:27] <exco> .
[08:00:00] <exco> I want my pyvcp meter to recognise the axis offset ... how?
[08:01:08] <archivist> define "recognise the axis offset"
[08:02:04] <exco> well my pyvcp meter shows 0 but I set an axis offset because home is at 105°
[08:02:25] <exco> so HOME_OFFSET = -105
[08:02:31] <exco> but the meter shows 0
[08:03:02] <archivist> touch off to 105
[08:03:04] <exco> which is connected to scale.0.in
[08:03:29] <exco> touch off?
[08:06:51] <archivist> but there is a home_offset in http://www.linuxcnc.org/docs/2.4/html/config_ini_homing.html#r0_1_3
[08:13:04] <exco> yes, but it doesn't show in the meter
[08:14:50] <cpresser> exco: i am not 100% sure i understand your problem. but basically, after homing (eg. home-switch-trigger), the control travels 105 units and then considers this position as zero
[08:15:17] <cpresser> if you dont want that behaviour, dont use an offset
[08:39:09] <exco> cpresser, no that's all good. I just want my pyvcp meter to show the correct position
[08:39:29] <exco> the cyvcp panel believes home is 0 though i have an offset of 105
[08:41:15] <cpresser> exco: does your pyvcp-meter show a different position than the regular DRO?
[08:41:41] <Jymmm> pcw_home: I picked up the 18650's =)
[08:42:19] <cpresser> if yes, you just neet to select a different pin. ' halui.axis.0.pos-relative' might do
[08:42:33] <exco> thanks, will check, cpresser
[08:51:36] <exco> cpresser, coarse-pos-cmd?
[08:52:15] <cpresser> exco: that does not sound like the current position
[08:52:49] <exco> that's what the number in the preview window shows
[08:54:25] <cpresser> type 'halcmd show | grep pos' and see which one you want to be displayed :)
[08:55:45] <exco> thanks, coarse-pos-cmd suits me fine (for the moment that is)
[08:56:54] <cpresser> the DRO in the preview window might show another number it you use G54 coordinate systems. depending on what you want the relative position is more usefull
[08:57:10] <cpresser> but that is up to you, i dont know your application
[08:59:50] <exco> thanks, I'll write that down and keep it in mind for later
[12:16:51] <c60> Any idea why an Axis would intermittently stop jogging with no error message?
[12:18:33] <archivist> sluggish feel to key presses?
[12:19:33] <archivist> keep running after release of a key for a bit?
[12:21:23] <IchGuckLive> hi all B)
[12:23:14] <c60> no, not sluggish, stops immediately upon release, but sometimes just stops while it's jogging.
[12:23:40] <c60> Seems to only be 1 axis though
[12:23:41] <archivist> accidently press another key?
[12:23:46] <c60> nope,
[12:24:30] <archivist> I have been seeing some jogging oddities on my 5 axis, worse if up for a few days
[12:24:43] <c60> I also have a joypad hooked in for jogging, and it doesn't exibit the same problem when I use it.
[12:24:59] <c60> mine seems to be worse first few hours, then it seems to go away
[12:25:04] <archivist> os version?
[12:25:17] <c60> 10.04 ubuntu, is there any other?
[12:25:54] <archivist> older machines are still on older OSs
[12:26:47] <IchGuckLive> i got a setup video on youtube for joypad
[12:27:09] <archivist> c60 from what mine is doing I suspect the OS screwing with key presses before axis sees stuff
[12:27:45] <archivist> c60 I also see errors on this non cnc box when the load is high
[12:28:21] <c60> hmm, I'm confused why it is only on the one axis, the side arrow keys, or numpad 4/6
[12:29:06] <archivist> probably the axis you use more so you notice it more?
[12:30:50] <c60> not really, it's the longer axis, and it won't move more than a few hundres mm's
[12:31:49] <c60> but it's not consistent, sometimes it moves 600mm sometimes 100mm, sometimes 35,
[12:33:21] <archivist> under high load on 8.04 when typing on irc I see multiple characters when I only type one. which is clearly OS related as there is no cnc on this box
[12:33:55] <Tom_itx> dirty key contact? key bounce?
[12:34:12] <archivist> no its only during high load
[12:34:46] <cradek> > I also have a joypad hooked in for jogging
[12:35:01] <cradek> this is surely your problem. turn on debug and you'll see abort messages.
[12:37:06] <cradek> if it only happens on X I predict you'll see spurious EMC_AXIS_ABORT ..., +0 coming from your joystick
[12:38:35] <c60> cradek: where do I turn on debug?
[12:39:08] <cradek> first run from a terminal, not an icon. then machine/set debug level, turn on Task Issue
[12:39:26] <c60> has to be run from terminal?
[12:39:36] <cradek> well if you want to see the output, yes
[12:41:55] <c60> so I have lots of EMC_AXIS_ABORT,
[12:42:17] <cradek> that message is what stops a continuous jog
[12:42:53] <c60> so how can I resolve? I thought having the joypad only activate when a button is pressed would do that,
[12:43:01] <c60> but apparently not.
[12:43:37] <cradek> well I'd unplug the joypad and toss it in the trash or give it to someone who plays video games. then I'd get a jogwheel.
[12:43:55] <cradek> but you might want to futz with the deadband settings etc and try to get it to behave
[12:45:24] <c60> It was more a novelty to get the joypad working, I'd rather just use my iphone.
[12:45:31] <cradek> hahaha
[12:46:16] <cradek> ok I have no idea what your setup is
[12:47:26] <c60> well I was using vlc, not ideal, but worked for dialing in my z's since it's on the other end of the table from the computer terminal
[12:47:59] <cradek> I don't know what vlc is
[12:48:08] <c60> oh, sorry, vnc
[12:48:14] <c60> screen sharing
[12:48:26] <cradek> how big is the mill?
[12:48:52] <cradek> for a very large mill it's nice to have a jogwheel pendant
[12:48:55] <c60> It's a 4x8 CNCRouter parts 80x20 build, 3hp water cooled spindle, just wood and plastics
[12:49:17] <c60> cradek: Oh I agree, just not on top of priority.
[12:49:23] <cradek> ah yeah, that can be hard to reach I bet
[12:49:35] <c60> iphone works fine,
[12:49:36] <cradek> I'd never use wireless to control a machine
[12:50:07] <jdh> wifi Estop!
[12:50:08] <archivist> use real wire TM
[12:50:48] <c60> it's just for dialing in the last few mm for my zero point before hitting go. What's a good jogwheel pendant solution?
[12:51:37] <cradek> I'd try to find one off a real machine tool. I've not spotted a hobby-market device that I like.
[12:51:45] <jdh> I have a Contour jog-shuttle thing. I'm not sure it qualifies as good, but it is workable.
[12:52:01] <cradek> failing that I'd probably make one using a real wheel
[12:52:31] <cradek> yeah, like the joypad, I think those kinds of devices are just not suited
[12:53:03] <jdh> I'd say it is much better than the joypad, but not near as good as a real mpg/pendant
[12:53:13] <cradek> they're for offices or rec-rooms
[12:53:35] <jdh> I'd like it better if Axis could update the Increment value based on what the shuttle is doing.
[12:53:52] <cradek> (I can imagine it being better than a joypad though)
[12:55:58] <c60> well, that definitely solved the problem,
[12:56:06] <cradek> yay
[12:56:19] <c60> one other question, where does one set the default jog speed and max velocity ?
[12:57:14] <cradek> http://www.linuxcnc.org/docs/html/config/ini_config.html#_display_section_a_id_sub_display_section_a
[13:01:10] <c60> Yeah, Thanks,
[13:03:11] <tjtr33> use a kinect & setup jog sensitive airspace ;)
[13:03:12] <tjtr33> ( like when Trillian threw a pencil through the radio's on/off sensitive airspace in HHG )
[13:04:03] <IchGuckLive> kinect for image control
[13:04:11] <IchGuckLive> show face mill 3D
[13:04:41] <tjtr33> i was kidding
[13:04:52] <IchGuckLive> why not
[13:05:19] <IchGuckLive> the pro versions of the chiese 3D scanners are doing it at Laser glas tubes
[13:06:26] <tjtr33> live control is different from acquiring data points
[13:07:44] <IchGuckLive> its justr a seconds record
[13:07:52] <IchGuckLive> and then a gcode move
[13:07:54] <skunkworks> hgg?
[13:08:47] <tjtr33> hitch hikers guide, where trillian threw a pencil thru the on/off airspace, stopping a news blurb about zaphod
[13:10:26] <skunkworks> heh - been a log day. I was thinking Hitchhikers Guide to the Galaxy
[13:10:33] <skunkworks> log day?
[13:10:43] <tjtr33> a verilog dar
[13:10:49] <tjtr33> day opps me too
[13:11:00] <tjtr33> bye 4 now
[13:11:04] <skunkworks> things have been going bad exponentially...
[13:17:43] <syyl-> uah
[13:17:54] <syyl-> friend asked me to shorten carbon arrows for him...
[13:18:44] <syyl-> rigged up the grinding motor with a cut off disc to the lathe ;)
[13:19:25] <syyl-> https://dl.dropboxusercontent.com/u/24396704/IMG_0073.JPG
[13:19:59] <syyl-> maybe time for a real mill/drill spindle for the lathe...
[13:20:57] <skunkworks> a chain wrench is holding grinder? cool
[13:21:13] <syyl-> light duty chain wrench thing
[13:21:50] <syyl-> its part of a laboratory stand to hold test tubes and stuff like that
[13:22:16] <syyl-> semed about to be the right thing for the job ;)
[13:28:20] <IchGuckLive> BY
[15:19:48] <Jymmm> TML: Tact; The art of being able to tell someone to go to Hell in such a way that they look forward to the trip.
[16:14:08] <DJ9DJ> gn8
[16:37:49] <Tom_itx> http://tom-itx.dyndns.org:81/~webpage/why/RR_index.php
[18:40:50] <JT-Shop> lol
[18:47:32] <JT-Shop> crap "set gap per vehicle specificatin (exception may apply)
[18:47:40] <JT-Shop> specification
[18:48:01] <JT-Shop> can't find crap for my 07 uplander on google except ads for buying spark plugs
[18:48:18] <Tom_itx> what crap did you need?
[18:48:35] <JT-Shop> plug gap for a 2007 Chevy Uplander
[18:48:56] <Tom_itx> electronic ignition?
[18:49:04] <Tom_itx> probably around .035"
[18:49:08] <JT-Shop> all are
[18:49:24] <JT-Shop> these are iridium's
[18:49:49] <JT-Shop> I've seen 60 44 40 and other guesses but nothig that really says what it should be
[18:50:21] <JT-Shop> my guess is 0.060"
[18:53:17] <Tom_itx> ....they come pre-gapped, although you can check the gap if you are very careful. The iridium electrode is very brittle and not hard to break off.
[18:54:19] <JT-Shop> ah ha I found it in the owners manual it is 0.040"
[18:54:30] <Tom_itx> well i was close
[18:54:40] <Tom_itx> just don't chip the electrode
[18:55:00] <Tom_itx> did you have to get them from the dealer?
[18:55:05] <JT-Shop> I heard that them suckers are $7 each
[18:55:08] <Tom_itx> or does 3rd party sell em
[18:55:11] <JT-Shop> no, acdelco
[18:55:19] <JT-Shop> can get them anywhere
[18:55:35] <Tom_itx> i could likely get em wholesale
[18:55:41] <Tom_itx> used to anyway
[18:56:13] <Tom_itx> a friend worked at an aircraft that rebuilt alot of delco parts
[18:56:25] <JT-Shop> can't wait to change the rear ones :(
[18:56:49] <Tom_itx> makes me wonder what mine has in it
[18:57:47] <JT-Shop> they are good for 100,000 miles but my gas mileage has dropped a few miles to the gallon so time to freshen up things
[18:57:58] <JT-Shop> I have 82,000 so close enough
[19:05:21] * JT-Shop puts on the chef hat now
[19:10:36] <JT-Shop> I just looked and I have only 270 miles of mountian biking in... I need to up the anti a bit and leave some fat along the trail
[19:13:55] <Tom_itx> don't need plugs for that
[19:18:28] <JT-Shop> nope, but I need the van to haul my butt and the bicycle to the trail head
[19:18:45] <JT-Shop> goodnight
[19:23:17] <RyanS> I'm going to make a tail stock cam lock. How do I work out how much offset the cam needs?
[19:39:08] <Tom_itx> probably not alot, you can make it adjustable at any rate
[19:50:16] <Tom_itx> http://bedair.org/9x20camlock/9x20camlock.html
[20:38:56] <nspiel> so ive got my hal and ini both working now for my scara but im having a hard time setting the correct input and output scale
[20:42:04] <Tom_itx> that's a bit of progress in a day
[20:42:31] <nspiel> so when i move my arm. the encoders track it on the scara ui but the scale is totally wrong
[20:43:00] <Tom_itx> so nail down what the scale is for each axis
[20:43:26] <nspiel> right. thats what i am trying to do only thing is i dont know the count per revolution or gearing?
[20:43:34] <nspiel> is the only other way empirically?
[20:46:31] <nspiel> this robot is too old to find the joint distances and all of that stuff
[20:46:46] <nspiel> because no datasheets
[20:50:31] <nspiel> anyone have any ideas about scara calibration for the ini file?
[20:56:20] <Tom_itx> what model is it?
[21:02:04] <nspiel> its a scara ssr h414
[21:02:07] <nspiel> i mean epson
[21:08:32] <Tom_itx> have you tried contacting epson?
[21:10:08] <nspiel> yeah they were so mean... they just sent me a message saying they wouldnt send it to me because its over 10 years old and they dont service it
[21:10:26] <nspiel> they definately have the manuals they just wont give them out
[21:11:04] <Tom_itx> tell them you don't want them to service it
[21:11:45] <Tom_itx> i can't see that it would be that hard to measure the lengths of the axis
[21:12:22] <Tom_itx> like someone here mentioned, they're very likely gonna be common dimensions
[21:15:06] <nspiel> right. that shouldnt be a hard part but the input and output scaling in the ini will be super hard because the robot itself is a super accurate peice of hardware but its only as accurate as my scaling is
[21:15:52] <Tom_itx> better get it right then
[21:17:57] <nspiel> any suggestions on it? should i jsut scale it. measure output in lcnc, scale repeat?
[21:18:09] <Tom_itx> i would
[21:19:12] <nspiel> ok, and as for the lengths i wish i had calipers that big
[21:19:14] <nspiel> all i have is a measuring tape
[21:19:36] <jdh> get a dial indicator or two
[21:19:50] <jdh> even a cheap HF one would be better than nothing.
[21:19:52] <Tom_itx> it'll only be as accurate as you can measure
[21:19:59] <nspiel> yeah i know...
[21:20:36] <Tom_itx> i would imagine once you get close the numbers will start to make sense
[21:20:46] <nspiel> yeah thats what i am hoping for.
[21:23:13] <Tom_itx> you get tired of it, feel free to send it to me
[21:23:30] <nspiel> the arm?
[21:23:37] <Tom_itx> :)
[21:24:50] <jdh> I have a system with an Epson scara at work. It's been running for about 2 years with no problems.
[21:25:09] <nspiel> awesome, what do you use it for?
[21:25:41] <jdh> it engraves serial numbers on fuel rod end plugs
[21:30:12] <skunkworks> as in nuclear fuel rods?
[21:30:21] <jdh> yeah
[21:30:30] <nspiel> whoa awesome
[21:31:43] <Tecan> ”Those people who think they know everything are a great annoyance to those of us who do.”
[21:34:05] <jdh> I just ignore them
[21:35:07] <nspiel> who was that comment in reference to
[21:35:26] <Tecan> was just reading a bunch of them found a smart one and posted here
[21:35:41] <nspiel> oh gotcha
[21:35:51] <jdh> don't take it personally :)
[21:36:37] <skunkworks> linux people are a bunch of snobs anyway..
[21:37:45] <skunkworks> ooh look at me - I have a realtime operating system...
[21:38:02] <Tom_itx> snob
[21:38:15] <skunkworks> ;)
[21:38:29] <jdh> I have two RT-11 systems.
[21:44:21] <nspiel> so i just realized but for some reason my z axis is inverted
[21:44:44] <jdh> de-invert
[21:45:44] <nspiel> where is that at
[21:46:00] <Tom_itx> take your pick
[21:46:04] <jdh> change the sign of the scale
[21:46:06] <Tom_itx> hardware or software
[21:46:12] <Tom_itx> software is easier
[21:46:41] <nspiel> software
[21:46:57] <nspiel> i know to do it in hardware but i dont feel like unwiring it
[21:49:28] <CaptHindsight> my real is more real time than yours :)
[21:51:02] <CaptHindsight> anyone else using the Vivado tools with Xilinx?
[21:54:43] <nspiel> tom how do you invert in software
[21:55:00] <nspiel> there are two inverts on the encoders in the hm2 part of the hal but i change them to true and no effect
[21:55:03] <jdh> change the sign of the scale
[21:55:20] <nspiel> in the ini? as in the input scale?
[21:55:35] <jdh> yes
[21:56:18] <Tom_itx> that's what i did on my stepper setup
[21:56:20] <nspiel> awesome thanks it worked
[21:56:32] <nspiel> im having trouble getting the scaling right still
[21:56:41] <nspiel> it seems like they are not mapped one to one as a multiplier
[22:13:01] <nspiel> when the z goes down now its positive but its the correct orientation on the scara ui
[22:14:44] <jp_> jdh you make nuke fuel?
[22:23:19] <nspiel> i got an error that said pyvcp does not exist?
[22:49:19] <Chemeleon> I had one person email me and say linuxcnc prefers gcode files to end with % for the last line, is that true?
[22:58:51] <nspiel> im kinda at a loss to determine the input scale
[23:13:22] <jesseg> nspiel, I may be able to help
[23:14:23] <jesseg> if you're still looking
[23:20:11] <jesseg> If possible, attach a small mirror to the output of your motor before any gearing, then use a laser pointer in the mirror, and shoot the reflected beam across the room onto a line on the wall.
[23:21:01] <jesseg> or better yet, set up a rifle scope on a solid mount and focus it (through the mirror) to a point on a distant wall.
[23:21:20] <jesseg> Then see how many counts/steps takes it a full turn
[23:23:19] <jesseg> Once you figure out an estimate for the number of steps per turn, then step the motor that many steps, and see if the laser lands in the same spot. Then step that many again, and keep doing that. Every time it turns, it should line up perfectly.
[23:23:38] <jesseg> If it's off even one step, that'll add up eventually. (You might have to disconnect from lead screw?)
[23:23:49] <nspiel> thats interesting
[23:24:29] <nspiel> i can scope the output to get counts per revolution but i ned to know the gearing
[23:24:40] <nspiel> its angular
[23:24:43] <jesseg> For example, even if you have a large number of steps per turn, even if you off only one step, after a thousand turns, you'll be a thousand steps off - and I bet you will notice that
[23:24:52] <nspiel> yeah true
[23:25:10] <jesseg> I don't know what a scara is - this is just general stuff
[23:25:37] <jesseg> oh I see.. I googled
[23:26:21] <jesseg> So for the gear ratios, just count the teeth and there is no guesswork at all then
[23:27:56] <nspiel> the teeth arent exposed only just on the output
[23:28:17] <nspiel> but not even on one
[23:28:21] <jesseg> No way to dissassemble for cleaning and greasing - and count teeth?
[23:29:13] <jesseg> Well, any axis that can rotate around and around any number of turns you can do the same as I described above, but I doubt the axis are that way on these
[23:29:23] <jesseg> since they have control wires going to motors
[23:29:50] <nspiel> i can get encoder counts per half revolution but the gearing is going to be really hard
[23:30:07] <jesseg> Do the axis all move 181 degrees?
[23:30:18] <nspiel> no
[23:30:25] <nspiel> they are limited with kill switchs
[23:30:25] <jesseg> half revolution of what - the motors?
[23:30:34] <nspiel> one moves more
[23:30:35] <jesseg> oh, at less than 180 degrees
[23:30:38] <jesseg> oh
[23:30:45] <nspiel> one also moves more
[23:31:02] <nspiel> but i can use a perfect square and get 180
[23:31:13] <nspiel> because the cast body is straight
[23:31:26] <jesseg> if one moves 181 degrees, then fasten a double sided mirror (like taken from photocopier or scanner) and do the laser beam thing, and when it's rotated exactly 180 degrees it'll line up
[23:31:44] <jesseg> All the geared angular axis are probably the same ratio
[23:32:06] <nspiel> hmm
[23:32:33] <nspiel> how will u be able to tell gear ratio from that
[23:33:14] <jesseg> Well, you would jog the motor around and around until the output axis had finally rotated exactly half a turn, due to the other side of the mirror shooting the laser beam in same place as first side
[23:33:26] <jesseg> then you notice how many turns the motor has taken in order to move the output 180 degrees
[23:33:29] <jesseg> and that's your ratio
[23:33:57] <nspiel> thats a good idea. how do you know how many turns the motor has gone through though
[23:34:02] <jesseg> Is there any way you could modify just one of the axes so that it had unlimitted rotation?
[23:34:03] <nspiel> from the encoder ticks?
[23:34:07] <jesseg> yes
[23:34:09] <nspiel> counting encoder ticks?
[23:34:14] <jesseg> yup
[23:34:24] <nspiel> oh ok thats a really good idea
[23:34:38] <nspiel> not really i would have to take it all apart and i dont really want to do that
[23:34:42] <jesseg> Ultimately, all you really care about anyway is how many encoder counts it takes per degree of final output
[23:34:52] <nspiel> right
[23:35:27] <jesseg> so you could even set the SCALE = 1 at first. Then degrees would equal encoder counts.
[23:35:53] <nspiel> wait but how do u know how many encoder tics there are per revolution of the motor
[23:36:01] <jesseg> Then just use the jog feature to move the output axis exactly half a turn, and then look at the degrees reading for that axis in LinuxEMC - and that'll be the number of ticks per half-output-turn
[23:36:06] <nspiel> i was just counting per revolution of the output
[23:36:46] <jesseg> Well, if you were able to count gear teeth to get ratio, then getting encoder count is helpful. That's why I suggested the mirror and multiple turns and the laser.
[23:37:25] <jesseg> But since you don't want to dissassembly for counting, then you don't care about encoder counts on the motor, you only care about how many counts on the final output
[23:37:33] <nspiel> the gear teeth arent exposed though
[23:37:40] <jesseg> All gear boxes come apart :D
[23:37:45] <jesseg> But that is work. :)
[23:37:58] <nspiel> so i can just gage x counts per 180 degrees of output
[23:38:05] <nspiel> yeah thatis work haha
[23:38:06] <jesseg> exactly
[23:38:13] <nspiel> and is that my scale then?
[23:38:16] <jesseg> yes
[23:38:32] <jesseg> in the ini file, scale is the counts per degree (or counts per inch, for linear axis.)
[23:38:35] <nspiel> so if i get 1000 tics per 180 deg output what is my input scale
[23:38:47] <jesseg> 1000/180
[23:39:14] <jesseg> 5.55555555555555555555
[23:39:30] <nspiel> oh ok awesome so one last question is it counts/mm if im in mm
[23:40:00] <jesseg> If LinuxCNC is set to MM then I would say it was counts/mm
[23:40:14] <jesseg> but degrees is degrees, I guess there's no metric angular measurement that I know of :P
[23:40:14] <nspiel> ok thank you!
[23:40:37] <jesseg> No problem. I hope it helps. I have only a little experience with LinuxCNC specifically
[23:40:50] <jesseg> But I have set one up
[23:41:21] <nspiel> i also need to figure out how to get the joint distances accurately since this thing is too old to have a datasheet
[23:42:02] <jesseg> To be honest, I'm not sure you'll get it exactly right with only half a turn of range to measure on the output. If you have 100 counts per degree, you may have trouble determining which count is right, but try and see.
[23:42:31] <nspiel> its almost the full range
[23:42:40] <nspiel> full range is prob 200 or so
[23:42:46] <jesseg> 200 what?
[23:42:52] <nspiel> degrees
[23:42:56] <jesseg> Ahh
[23:43:07] <nspiel> look up epson ssr h414
[23:44:10] <jesseg> Well, if a single step is too small to determine with the laser or scope, (Hmm. You could also just mount the scope on the arm!) anyway if a single step is too small to discern, the only way to know for sure you have it exactly is to rotate the axis many times to see if any error creeps in
[23:46:05] <jesseg> To measure arm length, I would get one of those little USB microscope cameras and mount it on the arm. Get the software running on a PC, and put a little sticker or some crosshairs signifier on the computer screen. Then put a ruler down, or some other standard distance measuring, and use the microscope like a crosshairs to perfectly line up to one mark by jogging, then swing the axis over to another inch or CM mark or whatever, and zero it in and find ou
[23:46:05] <jesseg> t how many degrees is between two points of a known distance, then work it backwards from there
[23:46:41] <jesseg> cute! (just looked it up)
[23:48:30] <jesseg> Hmm, it looks like the gear boxes are different for the two axis
[23:48:32] <jesseg> axes
[23:51:50] <jesseg> You could also put a pen in its hand and have it draw an arc, then measure the arc's diameter :P
[23:57:42] <jesseg> Oh, you couldn't mount the rifle scope on the axis since it'd have to turn 360 for that. You'd need a double sided mirror.