least I could do
cradek: any thoughts about 2.1.7?
I just realized that I should fix the m5i20 demo
I think it's a good idea
there are index lines in the hal file that are commented out
speaking of index pulse, is there a use to exposing the latched encoder "index" signal on a HAL pin? I notice several drivers do it. should I add it to pluto?
jepler has changed the topic to: EMC2 development -- http://linuxcnc.org/
jepler: good question
I really can't think of a reason for it - people use hardware counting because signals are too fast to sample in software, so you can't reliably sense the index pulse that way anyhow
the driver writers exposed the index pin, so I did the same when fixing the drivers
the "instantaneous" value on the index pin is already exposed, so that the pin can be used as general purpose input or for encoder index
I'm talking about adding a HAL pin that reads TRUE if an index was seen since the last read
don't to that
maybe I used the wrong terminology
the canonical access to "index seen since last read" is index-enable going false (the tri-state handshake thing)
I was unaware that some drivers exported something else
the 5i20 certainly doesn't (at least not since I fixed it)
maybe I misinterpreted what I saw back when I was reading the motenc driver
well, the motenc and the original 5i20 driver both did strange stuff with index, and maybe that was one of the strange things
I fixed the motenc driver at the workshop, and the 5i20 last week, I'm about 95% sure the motenc doesn't do that now, and I KNOW the 5i20 doesn't
iirc, ppmc does that
it was handy for debugging but probably not for much else
cradek: have you had the guts to update yet? I made a lot of changes to pluto, as I think you saw...
since workshop I haven't quite wired the lathe fully yet
it just needs to be plugged in
I have some parts to make soon though, so I'll try it
some punches that close/rivet eyelets of some kind - I don't quite have a spec yet
for a friend of bill's who makes some kind of clothing
she needs a different pair of punches for each size, and they cost > $60/pair, I'm hoping to make gcode that scales so it's simple to make a new size
have you ever seen elgoog?
[03:10:25] <jmkasunich> http://elgoog.rb-hosting.de/index.cgi
yes, but I don't get it
its just supposed to be amusing
I suppose it would be usefull to people who worked on their montors and connected the horizontal sweep coil backwards
heh - it was used by lots of people in china, because the chinese block of google didn't affect it
maybe 9 axes, so you know which are linear, is the best answer - even though we have to extensively screw with all the layers
I'll help, fwiw
we could do it on a branch.
(as long as we didn't let it rot for too long)
* alex_joni can help too
* skunkworks can cheer
maybe we can fix the joints/axes issue at the same time..
I'm still tempted to do 'COORDINATES = X - Z' and issue errors for axes that don't exist for 2.2
'-' meaning Y is missing?
jepler: if it's straightforward, sure why not
jepler: it's a can of worms.. I tried it twice for 1-2 hours
guess I stumbled on strange/wrong stuff, and drifted from the goal
two simple approaches: (A) change the table of function pointers so that the entry at 'a' is not read_a, if there's no 'a' axis
(B) change read_a to check a flag for "A axis is present"
(and so on for the other 5 supported axis letters)
ok, so a handfull of canon stuff to pass this back and forth
yeah, could be as simple as int GET_EXTERNAL_AXES(void), with one bit of the return value representing one axis
lowermost bit should be X
you may also want to put the same information in the stat buffer, so that axis can get it from there instead of parsing it from the inifile
exactly how you represent it in the inifile is an open question, but 'COORDINATES=X-Z' or 'COORDINATES=XZ' seem like two good ways to do it.
right now it's COORDINATES = X Y Z
changing to = X Z seems like it would be most natural to the user
* alex_joni was thinking the same thing
you probably don't want to make the user figure out what "slots" the letters go in
or what to put between them
the user has to know to write '[AXIS_2]' for Z and '[AXIS_0]' for X ...
so on the other hand, the "-" might be documentation
he should write joint_0 and joint_1
* cradek kicks alex_joni under the table
then use the kins to map j0 to X and j1 to Z
* alex_joni is immune
I am talking about something that can be done for 2.2 now
oh, forget it then
bbl.. gotta run for a while