Back
[00:17:49] <BigJohnT> hmmm
[11:04:09] <BigJohnT_> the jogwheel thing from yesterday that has absolute and velocity mode which component is that?
[11:06:27] <alex_jon1> motion
[11:06:34] <alex_jon1> it's already in the manual
[11:08:18] <BigJohnT_> ok
[11:11:20] <BigJohnT_> * BigJohnT_ wonders why folks want to use a MPG for a jog button...
[11:21:18] <BigJohnT_> should the EMC2 and HAL chapter be moved from the Configuration section to the EMC Related HAL part and be with the rest of the HAL information?
[11:21:46] <BigJohnT_> it seems out of place where it is...
[11:35:11] <CIA-36> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/gui/halui.lyx:
[11:35:11] <CIA-36> EMC: add foot to
[11:35:11] <CIA-36> EMC: halui.mdi-command
[11:36:33] <CIA-36> EMC: 03bigjohnt 07v2_2_branch * 10emc2/docs/src/gui/halui.lyx: added foot to halui.mdi-command
[11:38:56] <BigJohnT_> wow this is the first time I've been able to download the live cd on dialup...
[11:40:39] <BigJohnT_> BigJohnT_ is now known as BigJohnT
[11:54:43] <skunkworks> did that take days?
[12:01:14] <alex_jon1> was it ADSL?
[12:04:02] <skunkworks> morning alex
[12:08:05] <alex_jon1> that counts as dial-up
[12:11:24] <skunkworks> isn't that 128/128 usually?
[12:13:37] <alex_jon1> that isn't asynchronous
[12:14:13] <alex_jon1> ADSL2+M is 24 Mbit/s down, 3.5Mbit/s up
[12:21:10] <skunkworks> alex_jon1: could you check my account on sourcforge? I seem to be failing in sending emails to the list
[12:22:25] <skunkworks> or maybe it is me
[12:25:30] <skunkworks> http://www.pastebin.ca/1184185
[12:25:56] <skunkworks> odd - I changed my domain to mumblemumble
[12:33:25] <alex_jon1> skunkworks: you need to have an postmaster account on your domain too
[12:33:52] <skunkworks> really? when did that change?
[12:34:12] <alex_jon1> http://alexandria.wiki.sourceforge.net/Mail+Problems+-+Spam,+Bounced+Mail,+Unreceived+Mail#s_no_postmaster
[12:34:36] <alex_jon1> couple weeks ago I think
[12:34:45] <skunkworks> ah
[12:36:46] <alex_jon1> alex_jon1 is now known as alex_joni
[12:41:28] <skunkworks> alex_joni: that worked ;)
[12:54:01] <CIA-36> EMC: 03jepler 07TRUNK * 10emc2/docs/src/lyxdep.py: indicate the problem early when lyx file versions other than 221 are encountered
[13:54:44] <jepler> I'm considering how to make axis configurable for various combinations of rotaries.
[13:55:23] <jepler> the most limited approach is what I've already done: hard-code a particular configuration in the source code
[13:55:29] <jepler> (in this case, XYZBCUVW to match max5)
[13:55:41] <SWPadnos> including configuring whether the tool or the work rotates, or not?
[13:55:51] <SWPadnos> I suppose it doesn't matter, if the code can do either
[13:57:03] <jepler> slightly more flexible is allowing the user to specify a string similar to that one, which specifies the order in which the various translations or rotations are applied, including a minus sign to invert the sense of the next letter
[13:57:15] <jepler> so stuart's machine would become XYZ-ABUVW in that representation
[13:57:20] <cradek> can you put all the configuration-specific stuff in one place, so someone like stuart can see how to add a new configuration, and then eventually we'll have all the important ones?
[13:57:32] <cradek> then all we need is a way to pick between them, which is easy
[13:57:58] <cradek> oh I see - you want to write them all, all at once
[14:00:45] <SWPadnos> in theory, if you have separate functions to translate and rotate each axis, all you need is a loop to iterate over the letters, and optionally invert the sign of the parameter sent to the "movement" function
[14:00:54] <jepler> yes, I already wrote the code
[14:01:01] <jepler> I guess the question in my mind is whether it's flexible enough
[14:01:13] <SWPadnos> ok, whatever you did is probably the right way to do it :)
[14:01:17] <SWPadnos> what does it not do?
[14:01:32] <jepler> it doesn't let you displace the center of rotation
[14:01:43] <SWPadnos> hmm. ok
[14:02:29] <cradek> isn't that just a matter of setting the linear axes' origins correctly?
[14:02:38] <jepler> cradek: yes, I think so
[14:03:03] <SWPadnos> err - are you guys talking programmatically or mechanically?
[14:03:12] <jepler> SWPadnos: cradek is talking about emc configuration
[14:03:25] <SWPadnos> ok
[14:03:37] <jepler> defining XYZ 0,0,0 to be in the right spot with respect to the rotating axes
[14:03:56] <SWPadnos> but the axes don't have to have intersecting axes of rotation
[14:04:13] <cradek> no, but where they don't have that, you have a pivot length (in your kinematics)
[14:04:39] <SWPadnos> yes - that's the part that isn't in the AXIS code at the moment, right?
[14:04:49] <cradek> I think AXIS doesn't care about that
[14:05:01] <jepler> when you have the proper kinematics, then the gcode doesn't have to account for the pivot length (which is what you want)
[14:05:03] <SWPadnos> hmm - I'd have to drink more to know :)
[14:05:09] <SWPadnos> coffee that is
[14:05:13] <jepler> bring us some of your coffee. the stuff here is terrible.
[14:05:14] <cradek> it only shows the tooltip path and the tool vector
[14:05:17] <SWPadnos> that's true
[14:05:29] <jepler> cradek: so you think this representation is probably OK?
[14:05:32] <SWPadnos> heh - OK, when those tickets get below $1800 again
[14:06:44] <cradek> jepler: I don't feel like I know the answer to that
[14:07:12] <SWPadnos> I'd say that it's an improvement, and if anyone needs the translation thing, they can add it
[14:07:26] <SWPadnos> (or you will first if you find it an interesting problem)
[14:08:43] <jepler> I think the syntax to add a translation is pretty obvious: -1.0X -- but if I can skip writing it I'm happier
[14:09:01] <jepler> you'd end up with something like XYZ-1.0XB1.0X
[14:09:17] <jepler> to translate X before rotating B, then translate it back after
[14:09:20] <jepler> or whatever it ends up being..
[14:10:14] <SWPadnos> would that also take care of the rotating work case? (like you were working on for gears cut on an A axis)
[14:10:37] <SWPadnos> by rotating A before moving XYZ or something
[14:15:02] <alex_joni> hmm.. anyone knows where I could find a lathe chuck 3D model?
[14:15:26] <SWPadnos> http://sketchup.google.com/3dwarehouse/
[14:15:46] <SWPadnos> nope, they don't have one ;)
[14:15:59] <alex_joni> yeah, I already searched the warehouse
[14:23:48] <jepler> this is with GEOMETRY=BX -- the cone is pointing an unfortunate direction, though
http://emergent.unpy.net/files/sandbox/gear.ngc
[14:24:51] <SWPadnos> all I see is text! :)
[14:24:58] <jepler> oops, meant to link to the image:
http://emergent.unpy.net/files/sandbox/gear.png
[14:25:32] <SWPadnos> cool
[14:26:12] <cradek> wow
[14:29:24] <alex_joni> nice
[14:29:34] <alex_joni> SWPadnos: you should be able to parse that ngc
[14:29:56] <SWPadnos> I did - the image wassimilar to the one jepler posted, only the cone was pointing a different direction :)
[14:31:26] <jepler> bah!
[14:34:16] <jepler> OK, I think I'll check it in
[14:34:45] <SWPadnos> GEOMETRY is an ini setting?
[14:35:06] <jepler> yes -- [TRAJ]GEOMETRY seemed like the least inappropriate place
[14:35:31] <SWPadnos> maybe DISPLAY or AXIS section - it's display only, not the trajectory planner that deals with it
[14:36:15] <jepler> mmmaybe you're right
[14:38:23] <jepler> ah -- using BZ makes the cone point the right way
[14:40:44] <jepler> hmmmm negating doesn't seem to work
[14:42:33] <SWPadnos> unknown axis "-" :)
[14:46:33] <jepler> oh -- it was a "duh"
[14:47:00] <jepler> I reverse the string because the order that the transformations are applied is the reverse of the order I write them in the string
[14:47:11] <jepler> but then in the specification -BZ there is no axis that the - is applied to
[14:54:06] <SWPadnos> are those arcs or lines on the gear perimeter?
[14:54:26] <jepler> it's all "straight lines"
[14:54:29] <SWPadnos> ok
[14:54:36] <jepler> G1 moves
[14:54:51] <SWPadnos> a rotation gives you an arc even when it's a "G1"
[14:55:19] <SWPadnos> that should be simple I think - the center of rotation is always 0,0 in the plane of rotation
[14:55:39] <jepler> wait -- what are you asking?
[14:56:08] <jepler> are you asking if the preview is made up of one straight line for each G1 move on the perimeter?
[14:56:11] <SWPadnos> if it's possible/easy enough for the preview to show an arc when cutting is done by moving a rotary axis
[14:56:37] <SWPadnos> yes, sort of
[14:56:58] <SWPadnos> I'm wondering if the preview has straight lines for the peaks and valleys ofthe gear teeth
[14:57:02] <jepler> maybe this zoomed image will help to answer the question:
http://emergent.unpy.net/files/sandbox/gear-zoomed.png
[14:57:26] <jepler> (slightly different gcode, using G0 and G1 moves)
[14:57:35] <SWPadnos> err - it may - they seem more arc-ish there :)
[14:57:44] <jepler> the preview shows a curve even though the motion is written as G1
[14:57:55] <jepler> like axis' preview of arcs, it does an arbitrary subdivision of the move
[14:58:00] <SWPadnos> ok, cool! - that's what I wanted/was asking about
[14:58:32] <SWPadnos> I din't understand that, but it's OK
[15:00:30] <jepler> does this make any sense for documentation? I'm having trouble putting into words what GEOMETRY= does
[15:00:33] <jepler> http://pastebin.ca/1184301
[15:02:05] <SWPadnos> let me digest that a bit. I think it's pretty reasonable, but I don't know if a "normal person" would need more
[15:03:49] <BigJohnT> what does the BC do in the geometry string?
[15:04:38] <jepler> BigJohnT: that says when to apply the effect of the B and C rotary axes: UVW will be affected by the rotations created by B and C (because they're later in the string), but XYZ won't (because they're before)
[15:05:12] <jepler> take the simpler example: BZ
[15:05:30] <jepler> that makes the Z axis be rotated by B
[15:05:56] <BigJohnT> ok
[15:06:07] <jepler> so if you move out to Z1 and then move B, the entire cone moves around in a circle
[15:06:25] <jepler> if you wrote ZB, then doing the same thing would rotate the cone but the tip of the cone would stay fixed at the same spot
[15:06:48] <BigJohnT> as it would in a machine?
[15:07:53] <jepler> it depends on the machine and on the kinematics.
[15:09:00] <BigJohnT> so this is a way to display the backplot that more resembles the actual machine... Cool
[15:09:11] <jepler> yeah
[15:09:13] <cradek> yes, very cool
[15:09:33] <BigJohnT> I think that a "normal person" might need a few examples :)
[15:09:34] <CIA-36> EMC: 03jepler 07TRUNK * 10emc2/src/emc/usr_intf/axis/scripts/axis.py: user-configurable preview of rotational axes
[15:09:34] <CIA-36> EMC: 03jepler 07TRUNK * 10emc2/src/emc/usr_intf/axis/extensions/emcmodule.cc: user-configurable preview of rotational axes
[15:09:51] <alex_joni> jepler: I think it's ok (the pastebin text), but another example can't hurt..
[15:09:54] <jepler> back at workshop I did something specific to chris's 5-axis machine .. hopefully this new code will cover other machines like archivist's (?) gear cutting machine and stuart's cinci
[15:10:29] <alex_joni> BigJohnT: one day we'll have vismach integrated in the AXIS preview with an exact model of the machine & tool :)
[15:10:40] <BigJohnT> SWEET!
[15:10:41] <CIA-36> EMC: 03jepler 07TRUNK * 10emc2/docs/src/config/ini_config.lyx:
[15:10:41] <CIA-36> EMC: document [DISPLAY]GEOMETRY
[15:10:41] <CIA-36> EMC: fix some markup
[15:10:53] <alex_joni> BigJohnT: kidding.. jepler is probably preparing to take my head off
[15:11:38] <BigJohnT> can I watch
[15:11:57] <BigJohnT> * BigJohnT gets back to making chips
[15:13:26] <skunkworks> again - you guys are great.
[15:14:57] <alex_joni> SWPadnos: would this pass as a chuck?
http://imagebin.org/24953
[15:15:22] <SWPadnos> works for me, but I'm not the guy to ask ;)
[15:15:45] <alex_joni> it's not for turning .. so it should only resemble something :)
[15:16:00] <SWPadnos> can't you make the base plate round (like the chuck itself)?
[15:16:43] <alex_joni> heh... that's because of the snapshot
[15:16:49] <alex_joni> it should be "fairly" round
[15:17:04] <SWPadnos> oh ;)
[15:25:54] <alex_joni> this is a simulation tool, not the CAD to draw in.. so the exact shape is not that important
[15:36:39] <jepler> let the record show that alex_joni has offered to integrate vismach and axis
[15:38:17] <CIA-36> EMC: 03jepler 07TRUNK * 10emc2/src/emc/usr_intf/axis/scripts/axis.py: get rid of debugging messages
[15:39:22] <CIA-36> EMC: 03jepler 07TRUNK * 10emc2/configs/sim/axis_9axis.ini: specify geometry for this machine
[15:39:34] <BigJohnT> ok I have that recorded on the records :)
[15:41:38] <CIA-36> EMC: 03jepler 07TRUNK * 10emc2/configs/stepper-xyza/inch.ini: specify the geometry for this machine
[16:32:12] <alex_joni> logger_dev: you didn't see anything
[16:32:12] <alex_joni> I'm logging. I don't understand 'you didn't see anything', alex_joni. Try /msg logger_dev help
[16:32:40] <alex_joni> bbl
[17:02:05] <fenn> couldn't GEOMETRY be the same as COORDINATES?
[17:11:29] <SWPadnos> it could be, but you wouldn't put minus signs in COORDINATES
[17:11:51] <SWPadnos> also, there's no dependency on the order of COORDINATES (AFAIK)
[17:19:34] <Lerman> SWPadnos: I'm having some problems with Halscope ... and a question: How are "bit" type signals displayed? and can you sync on them?
[17:19:51] <Lerman> The problem is false triggering.
[18:05:02] <SWPadnos> BITs are displayed as either 0 or 1, and yes, you can trigger on them. I don't know if the level is automatic, the edge sensitivity is set from the rising/falling button
[18:07:15] <SWPadnos> Lerman, also make sure the scope is in "normal" mode rather than auto
[18:07:23] <Lerman> I get frequent false triggering on float values. The scope triggers and I can't find a value greater than the trigger value.
[18:07:38] <Lerman> Yes. Running "normal" "single".
[18:07:52] <SWPadnos> ok - just checking the basics first :)
[18:08:36] <SWPadnos> when that happens, you should zoom out so you can see every sample displayed. I'm not sure how it decides which value to use when a single pixel represents multiple samples
[18:08:45] <Lerman> Can't hurt. I'm having trouble getting homing to work. One problem is that my min and max Y limit switches were interchanged.
[18:09:05] <SWPadnos> using one of them as the home switch as well, I presume??
[18:09:20] <Lerman> The "f" value displayed on the bottom shows the distance to the trigger point as well as the value at the point.
[18:09:53] <Lerman> Yes minlimit is the home switch. It would be nice if axis displayed different symbols when you hit the min and max limits.
[18:10:06] <SWPadnos> yep, so you can find the trigger point easily, but since the pointer can only point at one pixel, I can't tell you which sample value is displayed if the pixel represents more than 1 sample
[18:10:10] <Lerman> (But I guess you usually know which one you hit).
[18:10:12] <SWPadnos> that would be nice
[18:10:15] <SWPadnos> yep
[18:10:28] <Lerman> Then zoom in so that each pixel is only one sample.
[18:10:33] <SWPadnos> exactly
[18:10:59] <Lerman> Also, you shouldn't have to check override limits if you try to jog in the direction away from the limit switch.
[18:11:22] <Lerman> But you need to check it even to enable the servos (on axis).
[18:11:39] <SWPadnos> I think that's in the bowels of task actually
[18:11:52] <Lerman> I can believe that.
[18:11:57] <SWPadnos> you can't start up when on a limit, unless "ignore limits" is on
[18:12:08] <Lerman> Bowels might be the right word.
[18:12:13] <SWPadnos> start up meaning switching from machine off to machine on
[18:12:15] <SWPadnos> heh
[18:12:21] <SWPadnos> lower intestine at least
[18:13:25] <Lerman> Well, I have X and Y homing. Z is refusing -- I'm getting following errors. I think I need some more tuning.
[18:14:54] <SWPadnos> cool (mostly)
[18:15:47] <Lerman> Well. Cool except for this is "just" a conversion from emc to emc2. It shouldn't require this much effort.
[18:20:08] <SWPadnos> if you have the old tuning values and the new values from some axis, then you may be able to use the same factors to calculate the new values for the other axes
[18:20:34] <SWPadnos> or at least check to see whether they're in the same ballpark
[18:21:53] <alex_joni> well.. depends if the factor between the values is the same
[18:22:01] <alex_joni> if it's not, it gets tricky :)
[18:22:23] <SWPadnos> indeed :)
[18:28:20] <alex_joni> you can still solve it with some newton ...
[18:28:27] <alex_joni> forgot the translation of that
[18:29:34] <SWPadnos> newton-rhapson?
[18:29:43] <SWPadnos> iteration
[18:30:03] <alex_joni> series
[18:30:09] <SWPadnos> ah
[18:30:32] <alex_joni> http://en.wikipedia.org/wiki/Difference_operator
[18:31:43] <alex_joni> I remember some program I wrote in pascal a really long time ago that used newton series to mimic a certain function
[18:32:18] <alex_joni> you gavfe it pairs of values (input/output) to train it, and then (after constructing some polynome coefficients) it would calculate the output for other input values
[18:34:04] <cradek> [143471.401175] Default Trap Handler: vector 14: Suspend RT task df877000
[18:34:16] <cradek> does anyone have any hints for tracking this down?
[18:35:39] <alex_joni> cradek: do you only get it with the m5i20 driver loaded?
[18:36:10] <cradek> yes, I don't seem to get it in sim/axis or sim_step_cl
[18:36:53] <SWPadnos> those don't load any RT drivers though, do they?
[18:37:25] <cradek> motion and all hal components are still in realtime
[18:37:30] <SWPadnos> sure
[18:37:51] <alex_joni> cradek: does halcmd show still work?
[18:37:55] <alex_joni> after the trap?
[18:38:00] <alex_joni> is this on hardy?
[18:38:09] <SWPadnos> have you tried both m5i20 and hostmot2?
[18:38:47] <cradek> yes hardy, no hostmot2
[18:38:55] <cradek> I will try to trigger it again and then try halcmd
[18:39:17] <cradek> an interesting data point is that the 2.2 branch of m5i20 runs great
[18:39:31] <jepler> cradek: but we never set the watchdog-control to 3 in 2.2. ..
[18:39:40] <jepler> I think, anyway
[18:39:51] <cradek> I am using the same config, and it has that setp in it
[18:40:17] <alex_joni> does the same config run on 2.2 and trunk?
[18:40:22] <alex_joni> * alex_joni would have not expected that
[18:40:25] <cradek> yes
[18:40:26] <jepler> cradek: ok, hmm
[18:40:41] <cradek> jepler: the bitfile in my 2.2 is one step older (with index mask, without watchdog fix)
[18:40:42] <alex_joni> sounds like this:
http://osdir.com/ml/linux.distributions.emc.devel/2007-11/msg00001.html
[18:43:41] <cradek> yes halcmd show does still work
[18:44:39] <alex_joni> so do you see which thread is stopped?
[18:46:18] <jepler> the quoted text in this message suggests how to at least get an instruction pointer:
http://osdir.com/ml/comedi/2003-01/msg00002.html
[18:50:16] <cradek> bonk
[18:50:20] <cradek> http://cvs.linuxcnc.org/cvs/emc2/src/hal/components/pid.c.diff?r1=1.33;r2=1.34
[18:52:32] <cradek> anyone spot it yet?
[18:54:28] <alex_joni> hmm.. not yet
[18:54:53] <SWPadnos> more parens needed on the *(pid->satureated_count) ++; line?
[18:54:53] <alex_joni> pid->limit_state ?
[18:55:23] <CIA-36> EMC: 03cradek 07TRUNK * 10emc2/src/hal/components/pid.c: fix memory corruption crash
[18:55:28] <alex_joni> although (without looking) I assume that's a parameter and doesn't need dereferencing
[18:55:33] <SWPadnos> I guess we'll see in a sec :)
[18:56:19] <alex_joni> heh
[18:56:51] <alex_joni> cradek: see.. if you tune your servos properly it won't die :D
[18:57:15] <cradek> haha
[18:57:25] <SWPadnos> woohoo! at least I had the correct line :)
[18:59:43] <alex_joni> SWPadnos: with a typo
[19:02:42] <SWPadnos> I'm a good typoist
[19:07:42] <alex_joni> we know
[19:10:59] <SWPadnos> tahnk oyu
[19:36:36] <jepler> cradek: argh, it was me?
[19:37:18] <cradek> IT WAS YOU!
[19:37:23] <alex_joni> lol
[19:37:52] <jepler> * jepler hides and feels ashamed
[19:38:00] <cradek> haha
[19:38:26] <jepler> I try to do something nice for you but you just complain that it's buggy and crashes your system
[19:38:39] <cradek> yeah I'm pretty ungrateful sometimes
[19:38:59] <cradek> back to trunk for me! yay!
[19:39:15] <cradek> I like the new AXIS message thingy, and the halscope save/load
[19:47:36] <jepler> yeah -- the message thing is a big "why didn't I listen sooner" kind of thing
[19:48:13] <alex_joni> * alex_joni still thinks emc2 should have a log with these..
[20:01:35] <LawrenceG> cradek, BigJohnT
http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Simple_EMC_G-Code_Generators gui for engraving "yay" uses qcad fonts
[20:05:17] <LawrenceG> fenn, you helped too! thanks
[20:07:34] <BigJohnT> LawrenceG: you da man!
[20:07:44] <LawrenceG> open source software is inspiring
[20:08:15] <SWPadnos> LawrenceG, one suggestion on the bezel maker: the number of divisions might be easier if it's "Major Divisions" and "Minor Divisions", instead of total ticks and "major every N"
[20:08:39] <SWPadnos> so the one you made would be 11 major and 3 (or 4, depending) minor
[20:09:00] <LawrenceG> yea... it takes a little playing, but the visual feedback is immediate
[20:09:54] <SWPadnos> yep - not a big deal, but it occurred to me that I'd be more likely to know that I want a 0-10 knob with quarter subdivisions than one with 37 total ticks :)
[20:10:28] <LawrenceG> right on
[20:10:29] <SWPadnos> (actually, I'd probably want 41 total ticks - that one only goes from 0-9 ;) )
[20:12:04] <LawrenceG> you can have anyway you want it! fenns code for parsing qcad fonts is a gold mine.... they are very nice stroked fonts rather than ttf fonts that are meant to be filled
[20:12:17] <SWPadnos> UTSL! :)
[20:12:46] <SWPadnos> I guess I should get back to building up this computer - bbl
[20:12:58] <LawrenceG> lunch time here... cu
[20:13:52] <fenn> i think the fonts are originally from the 'hershey' collection
[20:20:11] <fenn> cxf_fonts.tgz is 488kB which is over the wiki limit of 215kB; how do i put something in the dropbox?
[20:21:33] <jepler> fenn: tell me the URL and I'll see that it gets there
[20:21:45] <jepler> there's not an automated way for someone to do it, but I think I have the necessary shell access
[20:22:11] <fenn> its at
http://fennetic.net/pub/irc/cxf_fonts.tgz
[20:22:59] <jepler> semi-long-lived copy at
http://linuxcnc.org/dropbox/cxf_fonts.tgz
[20:23:30] <fenn> thanks
[20:39:02] <BigJohnT> LawrenceG: you still around?
[20:54:40] <BigJohnT> off to my fab shop...
[21:00:12] <jepler> cradek: hm, tell me if this is not a terrible idea: from the "A" channel of your spindle, use a simple circuit to produce an "A Delayed" signal, and use that as inputs to a quadrature counter.
[21:00:44] <cradek> sounds pretty terrible to me
[21:00:47] <jepler> OK
[21:00:54] <cradek> for a fixed speed, it might be ok
[21:01:10] <cradek> I want it to work reliably from about 100-3000 rpm
[21:02:07] <jepler> BIT10 CounterMode 0 = quadrature 1 = up/down
[21:02:17] <jepler> looks like the old hostmot also has up/down mode
[21:02:24] <cradek> yay!
[21:03:07] <jepler> hm -- did the hal_m5i20.c modifications not get checked in yet?
[21:05:11] <cradek> doesn't look like
[21:05:21] <cradek> cd
[21:05:22] <cradek> oops
[21:05:27] <jepler> cradek: here's what I think you do in the wiring to use up/down mode (which I'd actually call step+direction mode): wire "B" to VCC if you want to count up, and wire "A" to the one output of the spindle counter.
[21:05:33] <jepler> it will count up on each rising edge of "A"
[21:05:38] <cradek> neat.
[21:05:48] <cradek> I will try it.
[21:06:20] <cradek> hm, I won't be able to tap. I will want a new encoder eventually.
