Message-ID: <67949493@news.ausics.net>
From: Computer Nerd Kev <not@telling.you.invalid>
Subject: Re: News : ARM Trying to Buy AmperComputing
Newsgroups: comp.os.linux.misc
References: <_hycnQxlN5kAphr6nZ2dnZfqn_SdnZ2d@earthlink.com>   <6d5c7f67-7c7b-66aa-d9d3-54f71f77ae43@example.net> <luvpr9Fc5laU3@mid.individual.net> <198f4f8c-a0d0-7caf-b67e-1f61fee9de41@example.net> <UcicndjNUaEg0hH6nZ2dnZfqnPSdnZ2d@earthlink.com> <35e42921-5781-8728-236f-afad1d3b56b1@example.net> <vSydnd3xKfdNFhD6nZ2dnZfqn_udnZ2d@earthlink.com> <7258fd01-44f7-850d-3f69-54b93489f64d@example.net> <vml7e7$31s95$1@dont-email.me> <_ASdnRmnz7GABhP6nZ2dnZfqn_qdnZ2d@earthlink.com> <39751a64-73b7-7c03-b140-8dd7d4b4355c@example.net> <8x2cne8LCIYpbxP6nZ2dnZfqn_GdnZ2d@earthlink.com> <5caa2a20-e6c6-720a-5e6c-54e41729d0a4@example.net> <leKdnWYal46GqQ36nZ2dnZfqnPWdnZ2d@earthlink.com> <2cf850b4-7fd8-4839-8b34-1d947c81e709@example.net> <lvcsvdFfp0mU3@mid.individual.net> <b7e6faa1-6fb9-169a-c183-5f058be07538@example.net> <lvdh9gFiunpU1@mid.individual.net> <58556bf4-fe5c-047c-d60e-1e4aba9f71f1@example.net> <vmtqvk$1ll9u$21@dont-email.me> <6792a4f9@news.ausics.net> <vmvner$25d2c$2@dont-email.me>
User-Agent: tin/2.0.1-20111224 ("Achenvoir") (UNIX) (Linux/2.4.31 (i686))
NNTP-Posting-Host: news.ausics.net
Date: 25 Jan 2025 17:36:51 +1000
Organization: Ausics - https://newsgroups.ausics.net
Lines: 48
X-Complaints: abuse@ausics.net
Path: ...!eternal-september.org!feeder3.eternal-september.org!news.bbs.nz!news.ausics.net!not-for-mail
Bytes: 3613

The Natural Philosopher <tnp@invalid.invalid> wrote:
> On 23/01/2025 20:22, Computer Nerd Kev wrote:
>> Mine does need print software to interpret the Gcode and generate
>> build files that the printer itself can understand. But it's pretty
>> ancient as home 3D printers go (an original Makerbot Cupcake).
>> 
> Well mine (creality K1) seems to understand the GCODE directly, but the 
> slicer 'knows' about the machine, its commands and the plastic 
> materials, so it pretty much does all of that.

Maybe. You could check the output and see - Gcode is text based,
eg. this tiny snippet from a print I didn't get around to doing today:

G1 X-26.981 Y-1.748 Z3.36 F6240.0
M101
G1 X-20.752 Y-1.748 Z3.36 F3970.1225
G1 X-20.752 Y1.748 Z3.36 F3978.0
G1 X-27.748 Y1.748 Z3.36 F3844.7845
G1 X-27.748 Y-1.748 Z3.36 F3978.0
G1 X-27.286 Y-1.748 Z3.36 F3978.0
G1 X-26.981 Y-1.748 Z3.36 F3978.0
M103

G codes are posisitioning, M codes turn things on/off (the
extruder in this case). You can write it yourself like to use the
build platform as an agitater for etching PCBs in a tub on top,
which I tried but it turns out I enjoy doing the agitation manaully
more anyway (and less risk of splashing etchant on my 3D printer,
though it's mostly wood).

Slicers do need some machine-specific info even just to make the
Gcode. Hence I can't use the new ones with mine. I did look into
adding/hacking a driver (or whatever they call it) in Slic3r for
the Cupcake, but it's fixing something that ain't broke and I don't
like to touch C++ code if I can avoid it.

> I think modern printers are very much better than they used to be.Its 
> now out of 'unstable' and more into 'testing' with their onboard code

Well I've learnt the bugs pretty well by now and they're just like
old friends. Plus it's nice with the Cupcake that everything's open
source so it's been easy for me to modify the electronics a bit
(and someone so inclined could even fiddle at those bugs in the
firmware).

-- 
__          __
#_ < |\| |< _#