G999.9 random arc centers
jmkasunich_ is now known as jmkasunich
G999.8 "always give invalid radius error"
G999.7 "ignore arcs"
is G999.9 the same as 'undesired circular motion'? All real controllers use G999.6 for that...
maybe there should also be something like G999.17 "non-euclidian geometry"
SWPadnos: how goes the board?
it's OK. I'm having the FPGA mental block problem though :(
wecome to the club
the analog section seems to work fine, and I can light the LEDs under PC control
what kind of block are you having?
though the AD8250 doesn't seem to be as accurate as the spec sheet would have you believe
premature optimization, I think
you have a million gates to work with
you don't need to optimize
I have the SPI block from Peter, but I want to have a single unit that has one clock and 3 SPI in (or 4 out for the DACs)
I know :)
I do need to minimize address space usage though - this needs to run at 10KHz minimum, and there is a lot of data, so I think it's a good idea to make the read data addresses contiguous
similar for write addresses
I had to find some of the syntax for arrays of vectors and all that stuff - not being very comffortable with the language seems like an overwhelming impldiment sometimes
I've found that too
on the bright side, I did manage to get libmodbus working, so I have a short program that can read/write modbus endpoints
I tend to think in schematics and then try to figure out the VHDL that will give me the desired result
that can be turned into a userspace HAL modbus module easily, if some reasonable method of specifying the information you want can be found
I tend to think in microcontroller code, which doesn't always translate as well to VHDL
I did find out the array syntax though
all the eamples seem to define a new type, like so:
type somestuff is array(x downto 0) of std_logic_array(y downto 0)
then signal something : somestuff
std_logic_array is a predefined type?
the only weird thing (that I've read about anyway) is that you need separate parentheses for subscripting: something(3)(5) is a std_logic element
err - vector?
and then you can do stuff like obus <= something(0)(buswidth-1 downto 0)
std_logic_vector is just an array of std_logic, predefined for you in the IEEE1164 library
interesting - jon elson just described the "touches the disk every couple seconds" thing that I've been seeing on this box
could be like the kjournald thing I saw every 5 seconds
strace is good for that kind of stuff
er, i mean lm-profiler
I used top ;)
the only process I didn't know I had started which had nonzero total CPU was kjournald
there are about a bazillion processes running on this bo
mine too. I did that test after setting up a real runlevel 2 - multiuser but no X
without all the crap that normally gets started
I suspect that my blinkin-light is one of the craps
"the crap that normally gets started"
blinkin-light is the disk access LED
I thought you had done some modding with daemons to drive the uber-cool case LEDs or soemthing :)
something touches the disk every couple seconds, 24/7
is this the vmware box?
echo 1 > /proc/sys/vm/block_dump (as root), and dmesg will tell you who is accessing the disk
in my case, vmware, and kjournald
you might want to do /etc/init.d/sysklogd stop first
so the kernel log isn't being written to disk, which would make more transactions to log, which would be written to disk, which would....
that was like telling someone how to defuse a bomb. "cut the black wire .... but first, cut the blue wire" :)
I didn't do it, just thought it was funny
you're up late :P
and I'm up early
heh - that was fast :)
cradek: have you ever had time to look at the A-axis problem?
the stepconf A-axis problem
oh stepconf? no sorry
I couldn't find a pin-9-specific bug looking at the driver or the outb()'d values in a running emc...
yeah - I checked that a little too, and didn't see anything
I probably wasn't as thorough as you though
I wonder if there's a maximum reasonable distance homing should search for index
yes, there probably is
I read that if the BP doesn't see an index within 0.2 inches after the switch, it stops with an error
index is mostly useful with rotary encoders, so one revolution is a reasonable amount
right, but who knows what a revolution is
(in the general case I mean)
che might know
(in the general case :P)
jepler, have you tried using a single outw for the two parport outs? (I think they're at adjacent addresses - ignore if not)
rtapi_outb(outdata, port->base_addr + 2);
but thanks for making me look it up; I would have missed this
SWPadnos: hey, got my jog wheel working shortly after your last help the other day. now gotta work on the proper switches for changing axes and increments. thanks again.
Guest576 is now known as skunkworks_
speaking of inifiles do we want to make "convert existing sample configs to use 'net'" a goal before 2.2 releases?
I could sure do it for the sims and stepper, configurations I can at test
I think I changed all linkpp with net a while ago
I think that's a good idea
there are certainly others that aren't "fixed"
and anything else that leads to deprecation warnings, such as use of blocks (I think those were already fixed)
jepler: blocks have been fixed iirc
what about it?
isn't it deprecated, moved into encoder?
not that any configs use it
nist-lathe, max, sim/lathe, sim/servo_sim
err - nevermind me. I can't read
I think nist-lathe is the only one
yep, looks that way
looking for loadrt.*counter is much more effective than just counter