oops - bbiab
where was I
oh, thats right... enable seems inverted
and the mode bits are borked too
I get quadrature when I ask for step type 0
sorry about the pause there - I heard something like "My whole family is stupid - how can anybody talk to these people" after a phone call between my wife and her sister ..
sounds like a bad omen
yet strangely familiar
cradek, u there?
a few days ago I disabled 4 services (hplip, bluez-utils, laptop-mode, and nvidia-kernel)
since then, I have not had any strange behavior with emc apps
not sure if this was the cause, or just coincidence, but the system seems much more stable now
I'm running a 5 KHz servo rate with 1 KHz TP as well with no RT issues on the slow VIA board
wow, 5kHz servo is really fast
is that motenc?
maybe services that arent't absolutely required should be disabled by default in the live install?
yes, motenc 100
my drives are pretty fast, and the built in filter doesn't have a high enough corner freq
with 1KHz servo, the drives were too quick to get good response for both large and small error
with the 5 KHz servo rate, all problems went away
you have no base (faster) thread right?
base is at servo rate
how's your machine coming?
excellent, it moved and homed last night, and everything seems to work right
more testing tonight
did u try the auto tune yet?
not yet, and after reading the manpage, I'm not very clear on how to use it
what part wasn't clear? I'll try and explain it better
it doesn't really answer the question `what procedure do I use to autotune'
the at_pid functions as a normal pid and auto-tune
when the tune-mode pin is false, it's in normal pid mode
I did figure that out (since it has all the pid pins)
when tune-mode is true, it's in tune mode
the run a tune cycle, you set the start-tune pin
there are only 2 params
the number of cycles, which you can probably leave at the default of 50
and the tune-effort
do I know how far it will move? I wonder how to know if it's safe, how to abort etc
tune-effort is how much output is will use to create the limit cycle
that is determined by the machine and tune-effort
that's why you want to start with a small effor
to see what the reaction is
then build up until a good portion of the motor current is used
on my machine it only moves about 50 mil on Z
but my drives are pretty quick, and Z is light
I pretty much just replaced pid with at_pid in my test hal and bypassed motion pos fb
then all the other checks are still in place for limits, e-stop, etc.
it would be nice to have soft limits in effect too, but that would require more work
the state machine for the auto-tune does obey the enable pin and will abort mid cycle
so command stays constant, and it moves around that value to tune?
so you want to be in the middle of your travel when you first run it
are the params all ignored during this, or do you need an initial setup of those terms?
no, all PID params are not used
when the cycle completes, they will be filled in
ok great, I'll try it
ok, let me know how it works
That actally sounds pretty easy ;)
did my questions help for improving the docs?
I added a refresh button to the tcl script to see the values after a tune cycle
yeah, I'll add some more to the man page
thanks, I'll read that too before I start
anybody have ideas about what should go on the back side of a 1-page quick reference? (the first side is assumed to be the gcode quick reference)
maybe some diagrams like the image skunkworks posted
[23:32:54] <SWPadnos> http://www.electronicsam.com/images/KandT/conversion/cheatsheet.JPG
yeah in fact that's why I asked about it earlier -- but most of it did not seem directly applicable to emc
for instance, you don't have to specify arc feed rate in that nutty way...
just the M02 / M03 directions, G17/18/19 plane orientation, G2/G3 directions ...
yeah -- arc directions and maybe some images related to cutter comp were suggested by cradek
hmmm. is it supposed to be a G-code quick ref or an EMC2 quick ref?
I was wondering why you wanted that - was wondering if you where doing something with punchtapes ;)