steve_stallings is now known as steves_logging
what is the good reason to make the "predefined parameters" required in the var file?
it seems like making them all optional, and having the one which must be nonzero default to 1.0 would be just dandy
there's some strange behavior - I think variables are only saved if they were previously in the file when read
(I'm not saying any of that is good)
but, you can (currently) make #1 or any other number nonvolatile by adding it to the file
I wonder why the "active" coordinate system is even saved, given that M2 resets it to G54
you don't need to use M2
oh -- if you use %%?
that's how people can/should avoid resetting their various coordinates
maybe we should add M2.1 -- stop program but don't fuck with my offsets
M2 does a lot of things - not sure how you'd choose which ones M2.1 would do
ouch -- I edited drivers.lyx with lyx, but now (on another machine, maybe a different lyx version) building the documentation blows chunks because lyx can't parse the file
while I feel I should like a gui program that makes LaTeX more accessible, I sure hate lyx
There were errors during the LaTeX run.
32 errors detected.
You should try to fix them.
^^^ fuck you
LyX: Paragraph ended before \@item was complete.:
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
(too bad it won't even tell me what line...)
"\@item" doesn't even seem to appear in the source file
they should spend more time making the error messages informative instead of cutesy
by removing different parts of the text and running 'make docs', I've narrowed it down to the two figures I added
Say jepler What is the NML command for home all?
rayh: home axis number -1
aha -- if you have a Figure inside a Description layout, you get this weird cascade of errors
hmm - does 2 nominations equal a second? ;)
very good question
figured out the SAT business/problems ;)
yeah, it was a buggy importer
there's a field in the SAT that says what the scaling is (units / mm), and the importer always assumed 1
at least you know that now
yup, the problem is the app I used to export it has an urge to scale everything by 10, and put 10 there..
like that ever mattered :)
so.. how's things in your corner of the globe
I actually have paying work!
and I get to make things that will be useful for EMC (or at least HAL) while getting paid
yeah? what's that?
analog I/O card for the Mesa
sorry - phone
yeah, A/D and D/A converters on a 50-pin ribbon connector
err - on a board connected via 50-pin ribbon connector :)
16-bit resolution, probably 4 in and 4 out per baord
I can probably release it that way, yes
and the driver can be added to HAL
I'm not sure yet
this is for some relatively high speed signals (10 KHz per channel), and I'm not sure exactly how I'll do it yet
high speed relative to EMC PID loops, that is
I may also put a slew rate limiter in the FPGA, so it can do multiple updates inside a single "servo period"
I'll probably need to put some work into A64 and SMP as well, though I'll likely be asking questions on those subjects :)
oh, and I'll probably be able to contribute some knowledge, if not some packages, for an embedded EMC install (meant for headless or text-only operation)
* alex_joni is looking at another bug reported by petev
if one is in MDI and ESTOP RESET (so no machine on)..
(this only works on tkemc, AXIS doesn't let you MDI when not switched on..)
commands like M3 M8 etc work
wonder if that's a feature..
what are M3 and M8? (spindle forward and ???)
doesn't spindle on seem strange when machine is switched off?
you can do it even when ESTOP
spindle off and flood/mist off I can imagine, I wonder if it's some symmetry thing
change to MDI, hit ESTOP .. spindle goes off
type M3, spindle works again
that would make sense, if you could also command motion in that state
but since you can't ...
command motion while estopped???
I'm not sure of the advantages of MDI while not in MACHINE_ON
right - it would make sense to be able to turn on the spindle if you could also command motion, but since you can't command motion in estop, the spindle makes no sense
so.. anyone else thinks MDI while not switched on makes not a lot of sense
I don't think MDI as a whole should be disabled
for example, turning coolant off or doing other M codes may be valid
(especially custom M codes)
for me anything but machine on is an error state
err - I'm not sure exactly why :)
that should be left to the integrator I think
(AXIS does this right btw.. won't allow you to MDI while not switched on)
well, here's the logic:
* alex_joni is all eyes
I have a weird machine, and the predefined machine on->stopped transition does some stuff I've set up in ladder
but there are things I don't want to explicitly start/stop at that transition, depending on what's being done at the time
so I leave some things alone, and the operator can MDI those as needed
(that's all the logic)
why would he switch to stopped ?
I have no specific example of such a situation though
the counterargument: if MDI only allows you to command things that can't be done in estop reset, then there's no point in allowing MDI in estop reset :)
like I said.. switching to anything except machine on is an error state
SWPadnos: right.. no point in having MDI for anything else but MACHINE_ON
err - I may not have understood the situation we're discussing
right now you can only use MDI in machine on (with AXIS)
if you're running tkemc, you can send MDI commands in all states
even ESTOP and ESTOP RESET
but motion is not accepted
what commands are accepted when the machine is in the ESTOP RESET state?
I have no idea..
if there are actions that are acceptable in ESTOP RESET state, then MDI should be allowed in that state
basicly it accepts a TASK_PLAN_EXECUTE command
if there are none, then disabling MDI in non "machine on" state is fine
there are a few
S and F work too
but I can't find a reason for any of these to work in non "machine on"
M codes, tool prep, etc.
you may not need machine on to e.g. load a tool carousel
but you may need to issue tool prep commands to do that
imo it would be a misconfigured machine if things start moving while not switched on
the carousel moving isn't the same as the "machine" moving
doesn't matter.. I have my hands in there
also, you still want to be able to turn things off - I'm not sure that everything is turned off at machine off (like coolant)
it is.. I just checked ;)
same for spindle
ok. if it's defined that everything is turned off at machine off->estop reset transition, then MDI may be unnecessary