Build Environment
-
In the process of creating a build environment for the Duet and I've encountered a 'Deprecated' package - is there an alternate - I'm not a fan of building new code on deprecated libraries.
DEPRECATED > GNU ARM Eclipse
Has anyone built an environment for the 6HC that can highlight any gotcha's and other hassles - I may as well learn from others experiences as I'm totally unfamiliar with the Eclipse IDE.
Has anyone built the firmware as a project in MSoft Dev Studio ?
-
I have no experience setting it up in a Windows environment but if you have access to a Linux virtual or physical machine, I'd suggest using that. You don't need any deprecated stuff and there'll be less fiddling around.
-
AFAIR I only installed Gnu Arm Eclipse to get a version of Make that can handle the long command lines generated by Eclipse. There may be other suitable versions of Make.
-
Might build this up in a linux virtual. Haven't managed a single viable compilation yet ....
To be fair I may just be suffering from a familiarity with Marlin. What I need may well already be present and I just need to figure out how to configure / use.
I'd like a 'configuration' assistant that I can use whilst building - the ability to drive steppers in order to set levels and such - in particular I plan to explore 3 axis Z levelling and initialisation. I plan to use a Prusa Inductive Z probe also - may work - may not.
Given the additional power now available via the duet boards compared to what I'm used to a more thorough 'debug' log would be nice - i.e. record missed steps, CPU load and stepper currents etc but align it to the gcode being executed etc - I'm not overly interested in speed but it would be nice to see where the limits are for the code / firmware.
Marlin was much more straightforward to build - again that could be a lack of familiarity with RepRap.
-
Just to be clear...you don't need to build RRF to use it. All configuration is done in the config.g text file and read by the firmware at startup. You only need to build it to modify/add functionality, fix bugs, etc. and very few people do that.
-
your starting point is here
https://configtool.reprapfirmware.org/
and here is a guide that you can follow
https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+1:+Wiring/37?lang=en -
Appreciate all that, and appreciate the pointers, alas I am at heart a tinkerer and hopelessly curious - I like to understand how stuff works, partly to help me figure things out when they don't.
I am also not about to let automation loose until I have confidence that it will do nothing stupid (me doing something stupid is something no software can fix).
CoreXY and RepRap is new territory - I'm just working out how it all goes together .... to do that I take things apart and have a look. That said the only code available for the 6HC at the moment seems to be Beta so I don't think it hurts to try and understand it some.
On the other hand it isn't always clear what the appropriate answer is - consider the Pinda used on the Prusa Mk3 (that I intend to use). There is temperature compensation for the trigger point
2.0mm @10c
1.9mm @70c
1.8mm @100cit is also a 4 pin device since it contains a thermistor - now in RRF which one would you select .... the answer is currently none of them.
-
Understanding the code is a great goal. I read sections of it all the time.
I've never been motivated to setup to build it, there is really no need unless you are going to modify the source and build. Seriously... ALL configuration is G- and M- code based. Never a need to build, unless you have a burning desire to support your own fork.
-
Nope - no desire to maintain any 'fork' - just for understanding - my print habit is a means to an end (scale modelling) but it has grown arms and legs since I started, pretty much always have something on the printer either for myself or others. Building a CoreXy with a 6HC as a heart because I need larger X and Y volumes.
Started exploring 3D CAD / CAM, Electronics and have gone down all kinds of interesting rabbit holes (well I think they're interesting) - including trying to make sense of cartesian geometry given a pathological dislike of algebra.
-
@Garfield said in Build Environment:
Nope - no desire to maintain any 'fork' - just for understanding -
Then setting up a build is many hours that don't really gain anything. Just browse Github, and/or download a zip and unzip and use your favorite text/search thingie.
