Just need to vent a little. But as someone who paid a little bit extra for the recommended Archim board on promises of “the improved design and robust safety features.” I have to say that from this very early stand point, I am left a little bit disappointed. I understand that much of my frustrations are around the firmware, but since firmware and boards are so closely linked in this case, I’ll just treat them as interchangable.
Now let me be clear. Using Ryan’s Archim Dual firmware seems to get the very basics done. That is, that the machine moves according to GCODE, and the endstops work. And functionally, it is a capable CNC machine.
As my use and experience progresses, I do, however want to explore areas that might improve or enhance my hobby experience. Half the fun is tinkering and just getting it to work (at least for me). Yet, I find myself getting to areas over my head when it comes to firmware and compiling. I’m finding more and more that perhaps getting the RAMPS board should have been the way to go since it is likely a much more mature branch of Marlin.
Just some of my current frustrations with the Archim Firmware
- I can't implement this marlin bugfix to enable G54 for the Archim board
- #define HOST_ACTION_COMMANDS is not available in current working firmware. (This one is specific to the desire to integrate CNCjs to my workflow, currently, it does not appear that the two are in full communication with each other. It isn't working for me in a headless configuration.)
- There's much more goodies on thingiverse for a Ramps/Rambo board.
- Hmm, seems like I can't use ESTL cam controller with this board