e-jones is now known as e-jones|away
e-jones|away is now known as e-jones
what do you guys think about removing all the stepper sample configs?
good idea. I've seen one person trying to run it in simulation...
as far as stepper/ goes there's some documentation-ish stuff in standard_pinout.hal, but I think that kind of thing is better covered elsewhere (and it may be all stuff stepconf does anyway)
ditto for stepper-xyza
not so sure about stepper-gantry
Sherline* should probably remain since as far as we know they are applicable to specific machines that are on the market
nist-lathe? not sure.
demo_step_cl? not sure.
this may not be the time to clean up stuff anyway.
forget I said anything.
when would be the time? I assume you're talking about master anyway..
I meant 2.4.
what's the real benefit?
people go directly to stepconf
oh -- no, I'm not going to do something like that in 2.4!
maybe the thing to do is make a single stepper-based sample config, with very very well documented ini and hal files
including ini options that aren't used, and explanations of exactly why each thing is being done
I don't think those really help anyone
the documentation is the documentation.
most people will use stepconf, so anything else is useless to them
others will want to learn what's going on, and documentation is a great way to do that, but isn't "real world" enough to follow easily
I think yet another kind of documentation isn't going to help that
Jymmm mentioned this idea, it's like the very well commented ini files for apache or similar - you can learn what you need to change by reading the config file
I'm not sure
like the recent "but I want howtos, not documentation" on the list
heh, well that's just different :)
the documentation has all the information (presumably), which has a different use than an example
so I'd say sure, let's remove all but one well-documented stepper config, but I'd prefer to not lose all the case-study based documentation
too many people don't give it a good try... They want to be spoon fed.
btw - I was hooking up pins to the mesa gpio to show dad the buttons that appear in axis... He thought that was cool.. Getting more excited.
yay! my old laptop is actually 8.04, and even has the RTAI kernel on it
so, I get this interesting error when upgrading from emc2.2 to emc2.4 (both emc2 and emc2-dev):
E: /var/cache/apt/archives/emc2-dev_1%3a2.4.0_amd64.deb: trying to overwrite `/usr/share/man/man1/comp.1.gz', which is also in package emc2
ah, there's no 2.4 version of emc2-dev
err, nevermind that last
huh. and on the second try it worked
that's something to do with how the comp manpage got (correctly) moved from the main package to the deb package
so I assume the comp manual was moved from emc2 to emc2-dev, and apt just didn't do it right
did it actually make the install fail?
emc2-dev didn't install the first time, but did the second time
I hate the sf website
jepler: That's pretty broad, can you be more specific?
to name a few things: it's slow, the organization puts what I want always at least 2 clicks from the project page, and the issue tracker lacks the very obvious "go to report by number, no matter the project or artifact type"
jepler: Can you give me an example link?
Jymmm: OK, your task is to find whether tracker item 2917663 is closed; if it is, give me a link to the change that closed it.
ok, link to project?
Jymmm: on sf no two projects have the same tracker item number, so you *should* be able to go to the report without knowing the project
but anyway the project is tktoolkit
[18:38:54] <Jymmm> http://sourceforge.net/tracker/index.php?func=detail&aid=2917663&group_id=12997&atid=312997
jepler: Is that what you were looking for?
Jymmm: what sequence did you use to get there? I had to use 'support', then in each tracker try entering the number to see if there was a search result.
I went to http://tktoolkit.sf.net/
which redirected me to http://tcl.sourceforge.net/
then where it says "Directly jump to a project's bug or patch by number: " (half way down the page) I entered in 2917663 and pressed ENTER.
Jymmm: ah, so you solved the problem by not using the sf site itself, but something the tcl people kindly built to make up for a defiency in it
that's lateral thinking at its best
jepler: Well, no not really. You could have easily just done: http://sourceforge.net/support/tracker.php?aid=2917663
Jymmm: yes, that's another thing you can do to go around the sf website
jepler: Or just ask in #sourceforge http://sourceforge.net/apps/trac/sourceforge/wiki/Support%20by%20IRC
jepler: I'm not necessarily defending them, just saying there are alternatives available
I think it underscores what I was saying, that their website is no good
or at least has some specific rough corners that I always hit
(that link into trac points out that sf doesn't even use its own bug tracker anymore, they love it so much)
[18:53:27] <jepler> http://sourceforge.net/apps/trac/sourceforge/report/1
jepler: Well, I know the developers and the infrastructure, it's somewhat narrow minded. They haven't used their tracker in years. It's mostly Trac now.
is this cool or stupid or somewhere in between? http://timeguy.com/cradek-files/emc/newsplash.png
cradek: does it retain the easy scaling of the current version?
if we like it, I'll make sure it does
Is it Axis v2.4 or EMC v2.4?
the version number applies to the combination
I'd drop the ^2 and leave everything else then.
OR... EMC [v2.4 diagonally] AXIS
replacing the fowardslash with the diagonal v2.4
eh, just a thought =)
Jymmm: hm, I thought we had an existing logo with ^2, but I'm not finding it on anything
cradek: Might be a copyright infringement too
cradek: the emc 2.2 splash did
I was tempted to say EMC/AXIS [rotated]v2.4[/rotated]
I'm never sure how the 2 works
What about two lines, with the 2nd being "Enhanced Machine Controller v 2.4"
Jymmm: it turns out a lot of people cut this in stuff, so it has to be reasonably small
well the features should be big so you don't need special tooling, but the overall thing should not be too huge: this means you don't get many letters to work with
2nd line: Version 2.4
or 2nd line: http://LinuxCNC.org/
self promotion is always a good thing =)
Re: removing stepper example configs .. Please don't remove any of them! I have looked at many of them and extracted various bits of info out of them. I even looked at the NIST lathe example recently and found something, but I don't remember what it was. The combination of
the sample configs and the stepconf program is a good mix. :-)
Re: Modbus... I sent Chris Morley some revised Classic Ladder Modbus RTU/TCP related source files via the forum for him to test. I tested all of the baud rates and all of the functions and I can't get it to error any longer. I also tested the TCP version with all of the functions and that still works fine. I believe the comm issues are fixed. Modbus RTU Serial is now very quick.
it's better to send as patches prepared with 'git format-patch' and to the mailing list instead of in private
I put it in the public forum.. anyone can download them.. I was concerned about the format thing when making a patch file... do you use git to create the patch? I can read up on that and send them to this email list .. do you mean the emc-dev email list or the emc email list?
the forum exists solely for end-user support. I don't know that any developer reads it with any regularity
gotcha ... I was going back and forth with Chris about it and he wants to test the routines .. I'll see about making a git patch file and send it to the list.
use 'git commit' (or git gui) to create a commit with accurate authorship information and a description of your change, then 'git format-patch -1' to turn that newest commit into a text patch, then attach the message to an e-mail to the emc-developers list. (if you really trust your mailer you can inline it, but most folks use mailers that will mangle a patch when sent inline)
yeah, that kind of discussion is 100 times better on the mailing list
[19:31:43] <cradek> http://timeguy.com/cradek-files/emc/splash2.png
[19:32:11] <jepler> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Git#Share_your_changes_with_others
OK... that sounds easy .. thanks .. I'll do that..
with block delete you can toggle the second line on and off
(wonder if that's a good thing?)
I like the splash :-)
re: blovk delete, I'd say it's not a good thing - it's one more variable
cradek: Maybe drop the http://
and jsut have "LinuxCNC.org" (case preserved)
14:07 < Jymmm> or 2nd line: http://LinuxCNC.org/
when you and you decide what you want, let me know :-)
cradek: Yeah I know. But seeing it, the http://
looks cluttered imo
it might be a bad font - it all looks cluttered
Can the axis preview have clickable url's? ;)
much cleaner looking: http://timeguy.com/cradek-files/emc/splash3.png
hm, the gcode is 10x as big as before...
I like lowercase "emc2.4"
cradek: maybe "www.linuxcnc.org" instead of the http://..
hm, that's probably a good idea
[20:05:50] <cradek> http://timeguy.com/cradek-files/emc/splash4.png
EMC: 03cradek 07v2.4_branch * re66c1f9661d2 10/configs/sim/ (axis_9axis.ini lathe.ini): These need separate var files.
EMC: 03cradek 07v2.4_branch * r0d01a2294fea 10/share/axis/images/axis.ngc: new splash screen for 2.4
ries_ is now known as ries
cradek: if somebody would try to make this file, would it turn the spindle on? the current version of 2.3 doesn't do that I believe...