steves_logging is now known as steve_stallings
Single beds, extra for linen, bath down the hall probably, but still a bargain. Wifi and common area available in dorm!!
yeah I sure plan on doing that. if we have common area in the evening/whatever, all the better
steve_stallings is now known as steves_logging
when you run the hole circle program G91 does not come on, it stays in G90 mode... fresh pull and build this morning
jthornton: need more info
seems OK at commit f28d2ebf (Jan 21)
start sim/axis; home all; load and run hole-circle.ngc; go to mdi tab and see G90 in modes; command G0X1 and get a motion consistent with G90
seems ok for me too (fresh pull)
guys, what do you think about my patch to move program text to the left panel?
[15:10:32] <micges> http://imagebin.ca/view/1B9GME.html
aystarik: you must ask jepler, Axis is his part
I think the net effect is rather unbeautiful but if there's a usability improvement it might balance this. Can you say why this configuration is better?
in particular I think the following make the appearance worse: it causes unwanted blank space in the button panel, and it causes the speed controls to be separated from their labels by unwanted space.
the left side now combines things of very different widths and that makes for a rough appearance
also I know people on 800x600 screens already have problems fitting AXIS on the screen with some configurations; your change probably makes this much worse because the window is more sparsely packed.
I've retrofitted 3 mills, and on first two, I have this patch applied. On third, I decided to go as is, but operators requested it...
program view should be taller to be useful, it is so on any CNC screenshot you could find... EMC is the only one with the wide program view...
I agree with cradek. the left part is about 580 pixels in the screenshot. That leaves only around 240 pixels of preview on an 800x600 display, or 460 on a 1024-wide screen. it might make sense for a wide-screen system, but I simply don't want to get into making ONE thing in the GUI movable from place to place
because you can never do it with just ONE thing
I'm glad you can provide this change to your users who want it, though.
one could set t.text width to 60, it will provide more room for preview...
jepler: so, the patch is rejected, there is no way to make acceptable, right?
I didn't look carefully at the patch, but if it's possible to have this as a "widescreen" option (ini or axis.rc selected), that would be a good thing IMO
SWPadnos: I disagree. I mean, an option is technically possible but I don't want to go down that path
I don't necessarily want to see 100 different options all sitting in the AXIS python script, but having options for various screen aspect ratios or resolutions sounds like a good goal
SWPadnos: because after I say "yes" to the first one how will I say "no" to the second one?
as long as it's done right (which I don't know about this patch)
ok, I can see that
jepler: forget being fair! :)
so we should try to come up with some way of making this kind of change easy to maintain, outside the program logic
if by that you mean "write a new GUI with that as a guiding concern", knock yourself out.
whether it's an external "function" that sets up the screen (and you can choose which one to use in the config), or a table of locations/sizes of screen elements, or whatever
(not the grinding kind)
could be the grinding kind
* jepler is *so* sick of watching paint dry^W^Wfpga firmwares build
you need a 12-core PC
it would help
sadly, the only one I've had contact with is sitting unused in Dallas
to go beyond 4 cores you still need a multi-socket board and server class CPUs right?
yep, dual CPUs for 12 cores, single for 6
until the AMD Magny-Cours chips come out (end of March?), which will have 8 and 12 core chips
ulp, newegg says there's one 6-core CPU and it's $2400
I think I'll try to exercise patience instead
yeah, the Intel XEON something
the AMD chips were much less expensive, as little as $400 or so each, but they're not available much any more
[16:54:59] <SWPadnos> http://www.pricewatch.com/gallery/cpu/opteron_2427
I wonder why seb didn't split firmwares by fpga size (so that there are separate packages for 7i43-200 and -400, for instance)
the images are in the 1MB range, aren't they?
depends on the FPGA
it seems like there's a point where the additional package names are more confusing than choosing between the few possible images for your card
they range from 131022 (7i43-200) to 651919 (3x20-1M) uncompressed
ok, so it seems reasonable that there might be 8 or so of them in a single package - it's still only a few meg
-rw-rw-r-- 1 www-data jepler 196275 2010-01-16 17:24 hostmot2-firmware-bin-i43_200-v0.2.tar.gz
-rw-rw-r-- 1 www-data jepler 314201 2010-01-16 17:24 hostmot2-firmware-bin-i43_400-v0.2.tar.gz
so the guy with the -200 card is forced to download 300kB more every time there's an update
for anyone not on dialup that's nothing
2 seconds on my slow-ish DSL line
SWPadnos: AMD is cheaper because it's slower... look at spec.org SPECint results (these are applicable to compiling).
micges: watching the active g codes they do not change from g90 to g91 but will change when you run each line in the mdi
I was running the hole-circle.ngc from dev and noticed that the active g code for g90 did not change when a g91 was in effect
* jthornton goes back to stacking firewood
in auto mode, the active gcodes represent the codes after any "readahead" the interpreter has done -- including all the way to m2
jepler: thanks, that makes sense now :)
where is the source for tkemc? I don't see it under src/emc/usr_intf
EMC: 03jthornton 07master * ra81c1ded8317 10/docs/src/ladder/ (images/wrapping-counter.png ladder_examples.lyx): add wrapping counter example
EMC: 03jthornton 07master * r4a9da83ee4f3 10/docs/src/ladder/classic_ladder.lyx: add note on compare about no spaces
EMC: 03jthornton 07master * rfc2378f7717f 10/docs/src/gui/axis.lyx: add note about active g codes
EMC: 03jthornton 07master * r9e83220b8bf6 10/src/hal/components/thc.comp: update to the THC comp
EMC: 03jthornton 07master * r6bf21183c075 10/docs/src/gcode/ (images/polar01.png images/polar02.png main.lyx): add info on polar
jthornton: thanks for doing polar docs!
cradek: do they look ok?
I only looked at the patch - not sure I have what it takes to build them
but yeah, looks good to me
You have: 44 oz in gravity
You want: newton meter
great little program