#linuxcnc Logs

Nov 19 2024

#linuxcnc Calendar

01:15 AM Deejay: moin
04:10 AM Tom_L: morning
04:11 AM JT-Cave: morning
04:27 AM Tom_L: 48F hi 56F
04:59 AM JT-Cave: looks like a couple of frosty nights coming up in a couple of days
05:34 AM lcnc-relay: <travis_farmer@discord> Morning
06:37 AM lcnc-relay: <onceloved.cn@discord> A 184 MB g-code file takes up 11 GB of memory and is slow to load. Is there any solution?
06:37 AM lcnc-relay: <onceloved.cn@discord> https://jauriarts.org/_matrix/media/v3/download/jauriarts.org/PEpupVyIOHioiylmwVpFikQn/SI9P6BBQB1YF_1SRHV_tmb.jpg
06:37 AM jpa-: which GUI?
06:38 AM jpa-: you could try to disable preview if you don't need it
06:38 AM lcnc-relay: <onceloved.cn@discord> Preview has been disabled
06:39 AM lcnc-relay: <onceloved.cn@discord> dragon
06:39 AM jpa-: what process is using the memory?
06:40 AM lcnc-relay: <onceloved.cn@discord> It should be linuxcnc
06:41 AM jpa-: does it start using the memory immediately when you load the file, or only when you start running it?
06:42 AM lcnc-relay: <onceloved.cn@discord> while loading
06:42 AM jpa-: that seems weird, i think loading should be gui-only action and not affect the linuxcnc process
06:43 AM lcnc-relay: <onceloved.cn@discord> Don't know why it takes up so much memory
06:43 AM jpa-: are you sure it is the linuxcnc process?
06:44 AM jpa-: and not the gui process?
06:45 AM lcnc-relay: <onceloved.cn@discord> Wait a minute. I'll upload the file to Google Drive. You can try it.
06:50 AM lcnc-relay: <onceloved.cn@discord> https://drive.google.com/file/d/1CrPPNpNI4-4yZ1y0EMBj6hNHNafwFrZf/view?usp=sharing
06:51 AM lcnc-relay: <onceloved.cn@discord> https://drive.google.com/file/d/1CrPPNpNI4-4yZ1y0EMBj6hNHNafwFrZf/view?usp=sharing
06:51 AM rdtsc-wk: might be able to install 'btop' (perhaps even 'top') and see a tree of the processes and which one is using all the RAM
06:51 AM lcnc-relay: <onceloved.cn@discord> This is the g code file
06:54 AM jpa-: at least with axis it is taking time & memory in the gui process
06:55 AM jpa-: probably because axis has that text box it loads the code to
07:04 AM jpa-: i guess if it didn't run out of memory on gui side for me, it would start using more in the linuxcnc process
07:15 AM jpa-: onceloved: i think a workaround could be this: https://linuxcnc.org/docs/html/gcode/o-code.html#ocode:calling-files add a prefix and suffix to bigfile.ngc and put it in macros folder, and then have a tiny file that only calls that macro
07:15 AM jpa-: this way gui does not have to worry about the big file at all
07:17 AM jpa-: at least loading is fast for me and the file starts to run in simulator
07:19 AM jpa-: https://jpa.kapsi.fi/stuff/pix/linuxcnc_bigfile.png
07:25 AM Tom_L: increase line tolerance
07:25 AM Tom_L: if the file is full of short linear moves
07:26 AM Tom_L: ie circles interpreted as line segments etc
07:26 AM Tom_L: especially on surfaces
07:27 AM Tom_L: it kinda sounds like a surface file due to the size
07:31 AM jpa-: it's a surface file, but to me it looks like the move lengths are quite reasonably
07:31 AM jpa-: it seems to be a 16+ hour job
07:32 AM Tom_L: i didn't have time to look at it... i'm out the door
07:32 AM jpa-: move lengths appear to be about 0.4 mm in X and 0.08mm stepover in Y
08:15 AM lcnc-relay: <onceloved.cn@discord> jpa-: I've tried your method but it doesn't work
08:39 AM jpa-: in what way does it fail?
08:39 AM lcnc-relay: <onceloved.cn@discord> It’s the same as loading the g code directly
08:44 AM lcnc-relay: <onceloved.cn@discord> https://jauriarts.org/_matrix/media/v3/download/jauriarts.org/xmbcXUmeZPsiwlKRlRfyEbWQ/TO0C2R7M8GIZ3S6SF.png
08:44 AM lcnc-relay: <onceloved.cn@discord> My computer only has 4g of memory
08:45 AM lcnc-relay: <onceloved.cn@discord> https://jauriarts.org/_matrix/media/v3/download/jauriarts.org/nFZLuSyWEpABbYhhctGhFLpP/OVNGFKV1UE70625OD.png
08:48 AM jpa-: if using axis, set the display preview timeout
08:49 AM jpa-: the virtual machine i tested on also has just 4GB and loaded the macro thing in a few seconds
08:51 AM lcnc-relay: <onceloved.cn@discord> The preview timeout is now 5 seconds. Is it better to set it longer?
08:56 AM jpa-: should be ok
08:57 AM jpa-: i have it 5 sec also
09:00 AM lcnc-relay: <onceloved.cn@discord> It seems it can be loaded
09:01 AM lcnc-relay: <onceloved.cn@discord> https://jauriarts.org/_matrix/media/v3/download/jauriarts.org/YOTRKETBIjLzstVgemMuHqCB/WATMPVWO34608XU.png
09:12 AM lcnc-relay: <onceloved.cn@discord> PREVIEW_TIMEOUT = 5 - Timeout (in seconds) for loading graphical preview of G-code. Currently AXIS only.
09:12 AM lcnc-relay: <onceloved.cn@discord> Can’t this parameter be used in other interfaces?
09:29 AM Centurion_Dan1 is now known as Centurion_Dan
09:33 AM jpa-: onceloved: it should be possible to add it to other interfaces, but i think no-one has done so
09:41 AM lcnc-relay: <onceloved.cn@discord> It seems that only axis can be used
09:46 AM rdtsc-wk: curious, wonder if the gcode file would be smaller if arcs (G2, G3) were used?
09:47 AM rdtsc-wk: or G5 qubic spline
09:53 AM rdtsc-wk: https://linuxcnc.org/docs/html/gcode/g-code.html#gcode:g5
09:53 AM rdtsc-wk: of course your CAM software must be able to output G5
09:58 AM lcnc-relay: <onceloved.cn@discord> It shouldn't be too small, right?
11:28 AM cyborg_ar: So im trying to understand how jogging works with an encoder. looks like axis.c calculates a delta from the last count it saw. but there is no explicit handling of encoder roll-over
11:29 AM cyborg_ar: looks like if it gets compiled in 32 bits delta is a signed int so roll over gets handled transparently, but in 64 bits it would not, it would produce a ridiculous motion
11:32 AM cyborg_ar: (reading axis.c, function axis_hadle_jogwheels)
11:35 AM cyborg_ar: granted, with 100ppr it would take cranking the thing for like 6 months straight to roll over, but it could happen...
11:41 AM cyborg_ar: oh wait int is 32 bits in 64, so it does get handled there ok
11:41 AM cyborg_ar: i hate non explicit types for calculations like that :P
11:44 AM cyborg_ar: in theory it is still UB tho since overflow of signeds is not defined (though everyone relies on it haha)
11:54 AM lcnc-relay: <zmrdko@discord> Hello! Q: is that really true, that mesa is not supported on raspberry pi 5?
12:10 PM lcnc-relay: <skunkworks8841@discord> no
12:10 PM lcnc-relay: <skunkworks8841@discord> and it depends..
12:10 PM lcnc-relay: <skunkworks8841@discord> 🙂
12:11 PM lcnc-relay: <skunkworks8841@discord> you can use ethernet mesa hardware
12:11 PM lcnc-relay: <skunkworks8841@discord> I don't know if the spi part is working
12:27 PM jpa-: cyborg_ar: there are also physical limits on how far you can jog in a single direction
12:27 PM cyborg_ar: yeah im more thinking how a count can accumulate even when the jogging is off or in between restarts
12:29 PM cyborg_ar: I'm trying to make my own mpg pendant and wanted to see if i could get away with 16 bit counters, but looks like i gotta use 32
12:29 PM lcnc-relay: <zmrdko@discord> skunkworks8841@discord: Yes, i meant ethernet like 7i96s
12:32 PM jpa-: cyborg_ar: you could make a hal component that does the unwrapping of delta for 16-bit counts
12:32 PM cyborg_ar: true
01:03 PM rdtsc-wk: linuxcnc can store user-variables in a .var file; might be able to copy/retrieve the count to/from that (but of course it won't record anything while off.)
01:20 PM -!- #linuxcnc mode set to +v by ChanServ
03:47 PM roycroft: well that was a productive lunch hour
03:47 PM roycroft: i powered up my dust collector for the first time since moving into the new shop
03:47 PM roycroft: i still have a couple minor things to do before i can use it, but i can do those right after work
03:48 PM * roycroft officially has a functional woodshop, finally
03:48 PM xxcoder: yay!
03:48 PM xxcoder: just read that freecad 1.0 is finally out. https://wiki.freecad.org/Release_notes_1.0
03:49 PM xxcoder: also yay!
03:49 PM roycroft: wow
03:49 PM roycroft: after 20-ish years, freecad is officially in release mode
03:49 PM xxcoder: yeah. hard program to dev lol
03:49 PM roycroft: makes my shop progress seem pretty fast in comparison :)
03:49 PM xxcoder: yup lol
03:50 PM roycroft: it only took me 8 months to get it working
03:50 PM xxcoder: tetris done?
03:51 PM roycroft: no, not at all
03:51 PM roycroft: i have a lot of work to do on the interior of the shop -it's going to be at least a couple more months on that
03:52 PM xxcoder: lol ok yeah lot of work to do
03:52 PM roycroft: but i can use my machines as of today
03:52 PM roycroft: which will make many of the projects inside the house that have been on hold possible
03:56 PM roycroft: in the shop, i have a section of wall to paint, then i need to move my fastener cabinets to put up insulaion and sheathing behind them
03:56 PM roycroft: that's going to be the hardest part of the entire project
03:57 PM roycroft: it's probably going to take me the better part of a day just to move them, and just as long to move them back
04:15 PM rdtsc-wk: Been 'working' on my mill for 2+ years, lol
04:16 PM Tom_L: i worked pretty steady on mine and iirc took 6 weeks
04:18 PM rdtsc-wk: just the choices in chainflex cabling is astounding
04:18 PM Tom_L: jt made a help file system for flex now
04:18 PM xxcoder: lol years and never finished for my cnc router. hopefully roy will finish it someday lol
04:18 PM Tom_L: yeah i know
04:19 PM Tom_L: http://tom-itx.no-ip.biz:443/~webpage/cnc/Mill_Steel/
04:19 PM Tom_L: it's all there if anybody cares
04:19 PM xxcoder: honestly dont matter if roy never does
04:20 PM xxcoder: wow nearly 10 years for tom machine now
04:20 PM xxcoder: 8 years now I think well 7-8 anyway
04:22 PM rdtsc-wk: dang Tom, nice job. machine building is not easy
04:22 PM xxcoder: yeah tom did awesome. I remember looking forward to new pictures batch
04:22 PM Tom_L: doesn't seem that long ago
04:25 PM lcnc-relay: <JT> Time flies
04:25 PM Tom_L: jt i left a note in -dev
04:26 PM lcnc-relay: <JT> Ok
04:26 PM Tom_L: i think the help files are great
04:27 PM lcnc-relay: <JT> Did you see the estop and power button changes
04:27 PM lcnc-relay: <JT> Cool
04:27 PM rdtsc-wk: haven't had a chance to check out help yet, but am sure to be impressed :)
04:27 PM Tom_L: now if i can get the wordage right
04:27 PM Tom_L: http://tom-itx.no-ip.biz:443/~webpage/cnc/JT-SHOP/flexgui/help_window.png
04:28 PM lcnc-relay: <JT> I like that they are not modal
04:28 PM Tom_L: can the font size be changed easily?
04:29 PM Tom_L: probably not
04:29 PM lcnc-relay: <JT> JT sits and waits at pt
04:29 PM lcnc-relay: <JT> I've not tried to change the font
04:31 PM lcnc-relay: <JT> Size
04:35 PM Tom_L: is there a way to have the help text start at the top if it's more than the window?
04:35 PM Tom_L: from -dev...
04:35 PM lcnc-relay: <JT> Probably
04:36 PM Tom_L: that would be a plus
04:38 PM lcnc-relay: <JT> I think I just have to set the cursor at the top after adding the text
04:38 PM Tom_L: mine scroll and end up starting from the bottom
04:39 PM Tom_L: they must be fixing amber alert... my phone has gone off with a test 5-6 times in the last 2 days
04:40 PM xxcoder: or they thought they was pinging test server and not live server
04:40 PM Tom_L: if i knew who it was, i might ping them..
04:40 PM xxcoder: lol
04:41 PM lcnc-relay: <JT> LOL
04:43 PM lcnc-relay: <JT> Back to the barn
05:16 PM * JT-Shop takes 5 before going out to work on the 82
05:31 PM * roycroft heads out to do the last couple things necessary before using the dust collector
06:10 PM roycroft: all done - it sucks now
06:11 PM xxcoder: good, if it blew, it would suck
06:36 PM roycroft: shims and screws arrived a few minutes ago
06:36 PM roycroft: now i can mount the cabinets in my studio
06:36 PM roycroft: and start unboxing stuff and putting it away in the cabinets
06:36 PM roycroft: and now that i have dust collection i can finish up the laser enclosure, which needs some slight remodeling
06:47 PM xxcoder: nice
06:50 PM rdtsc_away is now known as rdtsc
07:16 PM lcnc-relay: <big_kevin420@discord> @rdtsc do you know of any cam that can output splines?
07:17 PM lcnc-relay: <big_kevin420@discord> ive only found 1 really old one, and i think it was more of a filter/post processing tool rather than a cam
07:17 PM lcnc-relay: <big_kevin420@discord> i think maybe HSM something cam can also
07:18 PM Tom_L: at the cam point i think most output line segments
07:18 PM lcnc-relay: <big_kevin420@discord> but what i found was, everyone stopped caring about splines in cam
07:18 PM lcnc-relay: <big_kevin420@discord> yeah exactly, even if your controller supports splines, finding a cam to output splines is a dif story
07:19 PM Tom_L: my newer iges import converts everything to polylines
07:19 PM Tom_L: my old one which i prefer imports lines & arcs
07:20 PM lcnc-relay: <big_kevin420@discord> which is nice, because even trying to use spline geo in cam is hard, i usually have to convert splines into lines before i can even use that geo in cam
07:20 PM Tom_L: i don't think i've ever come across one
07:20 PM Tom_L: polyline circles are a pita
07:20 PM lcnc-relay: <big_kevin420@discord> sometimes i make them by accident, but sometimes solidworks makes them because its cleaner
07:21 PM lcnc-relay: <big_kevin420@discord> arcia is doing some stuff with splines with a guy on the forum right now
07:21 PM lcnc-relay: <big_kevin420@discord> but when ever i look at it, i just thing....the cam
07:22 PM Tom_L: https://apps.autodesk.com/ACD/en/Detail/Index?id=2862038210154022300&appLang=en&os=Win32_64
07:22 PM Tom_L: i think opposite of what you're looking for
07:22 PM lcnc-relay: <big_kevin420@discord> well, not always, but yeah
07:22 PM lcnc-relay: <big_kevin420@discord> uhh does that cost monety?
07:23 PM lcnc-relay: <big_kevin420@discord> ok its 3rd party
07:23 PM lcnc-relay: <big_kevin420@discord> but yeah mastercam has one included
07:24 PM Tom_L: i think it would be fairly specialized if it output splines
07:25 PM lcnc-relay: <big_kevin420@discord> i mean, it doesnt really have to be, all the spline info is there, and most bigboy cnc controllers support splines
07:25 PM lcnc-relay: <big_kevin420@discord> but then the cam never caught up
07:25 PM lcnc-relay: <big_kevin420@discord> so controllers stareted doing othershit to compoensate
07:26 PM lcnc-relay: <big_kevin420@discord> and now, the bigboys use DNC and stuff, and controllers started not having a size limit
07:27 PM Tom_L: we did DNC on an old machine years ago
07:27 PM Tom_L: didn't have alot of memory
07:28 PM Tom_L: and we cut alot of surfaces back then
07:28 PM Tom_L: dnc isn't something new
07:29 PM Tom_L: i set it up for my bud
07:29 PM lcnc-relay: <big_kevin420@discord> exactly
07:30 PM lcnc-relay: <big_kevin420@discord> the push for spline support in cam was negated
07:30 PM Tom_L: i don't think linuxcnc would / should ever need dnc
07:30 PM lcnc-relay: <big_kevin420@discord> by using dnc
07:30 PM lcnc-relay: <big_kevin420@discord> it doesnt, idk how that would even work, thats basically like grbl or something
07:31 PM Tom_L: grbl just about has to
07:31 PM lcnc-relay: <big_kevin420@discord> but if you dont need to have smaller programs because of DNC
07:31 PM lcnc-relay: <big_kevin420@discord> no one is pushing industry cam industry to support splines
07:32 PM Tom_L: it's going to have to translate into either a G1 or G2-3 in any case
07:32 PM lcnc-relay: <big_kevin420@discord> so instead of using better spline output from the cam, controllers now have special functions to process surface type profiles and smooth out the motion
07:32 PM Tom_L: unless they are specialized proprietary commands
07:33 PM lcnc-relay: <big_kevin420@discord> well, yeah most controllers* have a special spline command
07:33 PM lcnc-relay: <big_kevin420@discord> then they also have commands to make the surface profiles machine better because of lack of spline data
07:33 PM Tom_L: and it's likely different for every control that supports it
07:33 PM lcnc-relay: <big_kevin420@discord> more or less, but thats besides the point
07:34 PM Tom_L: G61 like?
07:34 PM lcnc-relay: <big_kevin420@discord> instead of using splines in cam, its now using special smoothings modal commands before a surface profile
07:34 PM lcnc-relay: <big_kevin420@discord> uhh
07:34 PM lcnc-relay: <big_kevin420@discord> kinda but not qwuite
07:34 PM Tom_L: G64
07:34 PM lcnc-relay: <big_kevin420@discord> i think controllers still use g61
07:34 PM lcnc-relay: <big_kevin420@discord> its closer to to g64 kinda of
07:35 PM lcnc-relay: <big_kevin420@discord> but they are closer to how the cam line filter works i think
07:35 PM lcnc-relay: <big_kevin420@discord> and has to do with cordial devations and points
07:39 PM lcnc-relay: <big_kevin420@discord> fanic uses aicc, and nanoAI i think]
07:39 PM lcnc-relay: <big_kevin420@discord> the one is the same command as linuxcnc spline, g5
07:40 PM Tom_L: i've never used it
07:42 PM lcnc-relay: <big_kevin420@discord> ok, yeah aicc i think is closer to g64, but nanoAI is closer to spline stuff, for smoothing out surface progfiles
07:44 PM lcnc-relay: <big_kevin420@discord> so, the point is, cam software compines fucked us, and mastercam rarely has new features that matter, and spends more time year to year fixing basic ui bugs that they shouldnt have even released
07:45 PM lcnc-relay: <big_kevin420@discord> so, not stepnc, no splies, work with the same old shit, it was fine 20 years ago its fine now
07:46 PM lcnc-relay: <big_kevin420@discord> and then controller compinies nickle and dime you for every feature, 512kb of memory? in 2024?
08:21 PM rdtsc: saw a forum thread about this earlier; linuxcnc G5 is cubic - not a B-spline - so the math is waaaay different. doesn't seem to be much interest in it, even though it would make sense for surfacing
09:31 PM rdtsc is now known as rdtsc_away
10:43 PM Unterhaus_ is now known as Unterhausen