Some of you may remember I reserved a kinematics type number back in August 2019.

And some of you remember I wanted to take a break from 3d printers.

Well, I failed either so far. But as of today, I have a prototype machine built that I can implement for. Luckily, someone did it for Smoothieware (the same person whose prototype build I copied, with his blessing and help).

Here is a first photo:

And here is a short video of me abusing delta mode and absolute tower moves to show that it's only mostly dead:

https://photos.app.goo.gl/c4ptuJajXeWNc8di9

Still missing are endstops, belt tension, anything on the effector to do useful stuff, a surface to do stuff on ... but for implementing the kinematics this should be sufficient. Let's see if I can get to there in less than nine months (-:

Hi,
I would like to document what I needed to do to compile RepRapFirmware and DuetWiFiSocketServer on a Debian Buster system (similar to a previous report on doing the same on Linux Arch).

First off, do not waste time trying to install the build chain from debian packages. They are sorely outdated and will not work.

The Build Instructions are a decent baseline, but to get everything going, I had to close some gaps.

Build Tools

1. Eclipse IDE for C++ downloaded from upstream. This requires a JRE to run, but openjdk is sufficient.
2. arm GNU toolchain downloaded from upstream. The Debian packages are massively outdated and builds will fail.
3. xtensa architecture toolchain from upstream is needed for DuetWifiSocketServer. As with the arm-gcc cross compiler, the Buster packages are outdated and won't build the project.
4. ESPtool because the esptool.py included in the xtensa architecture toolchain has different command line switches and the build will fail without the binary
5. eboot.elf from the Arduino ESP libraries

Additional Dependencies

In addition to the repositories listed in the build instructions, you need LwipESP8266 and CoreESP8266 as prerequisites to build DuetWiFiSocketServer.

More Project Variables and Paths

1. For LwipESP8266, set GccPath to the bin dir of the xtensa-lx106-elf compiler suite
2. For CoreESP8266, set GccPath to the bin dir of the xtensa-lx106-elf compiler suite
3. For DuetWifiSocketServer, set

• EspBootFile to the path to a valid eboot.bin
• EspToolPath to the esptool binary (NB esptool.py does not work because it has another call signature)
• GCCPath to the bin dir of the xtensa-lx106-compiler suite

From the default settings on the checked out projects it looks like you can find those when you added ESP8266 support to a local arduino installation, but when I set this up I was tired and couldn't remember how to set up board support on Arduino so it was more straightforward for me to download and build everything from source. It also made it possible for me to ensure that I really got the latest versions of everything.

With all this in place, I was able to build CoreNG, FreeRTOS, RRFLibraries, LwipEsp8266, CoreEsp8266, DuetWifiSocketServer and finally RepRapFirmware without a hitch.

The last ten days I kept myself busy with a V-Core Pro Corexy kit. It sports a 750W AC heater, three independent z steppers, MGN15 linear rails, 9mm Gates belts, a Duet3 with a Raspberry Pi4, hall effect endstops, a polypropylene print plate, paracord-sleeved cabling, a 450W Meanwell PSU (overpowered without running a heater, but that hopefully means it will rarely switch on it's fans). Print volume is 300x300x300 -- but since I use integrated leadscrew steppers, Z is likely close to 330.

The kit is super chonky for lack of a better word. The belt runs are super clean and parallel to everything, and the belt tensioner is integrated in the X carriage requiring a single screw per belt to tension.

I am almost ready to do a first print, but am missing mounts for the endstops and Z calibration. After that, everything will be cleanup and incremental improvements.

Because someone on the 3d Printers discord asked for help with his V-Core Pro, I finally got my act together and got mine up and running again (with the notable exception of part cooling).

Beauty shot:

Hemera and the toolboard are a real good combination, but it gets in the way of my preferred hemera part cooler. The mini IR probe works well on the mamorubot PP plate, and the Duet3 board was good with the Zesty Nimble, but I decided to use the Hemera here now, which means the tool board got some more work to do.

Next steps are

• fixing up the CAN cable (and power cable)
• possibly adding a drag chain to avoid dangling cables
• fixing the heater block rotation (it's "wrong")
• replacing the cheap noname SSR that came with the bed heater with a zero crossing one to avoid flicker when it keeps set temperatures.
• possibly adding the magnetic filament sensor
• part cooling. Because the front of the head is already pretty crowded, I am thinking of borrowing the cooling setup from the Medusa switching hotend: 5015 in the back and a flexible cooling hose to the front
• adding some panels for passively heated chamber for more fun with ASA and ABS

This machine is a Duet Baby: Duet3 board, tool distribution board, tool board, mini IR probe, PanelDue .... (hence it would be a nice touch to finally add the filament sensor somewhere).

For people looking for a nice, configurable 12864 display, I cannot recommend the BTT TFT2.4 (or other sizes) well enough. While it's nominally an MKS-like touch screen, it also has an 12864 emulation mode that works perfectly fine with the Duet Maestro (including external SD card support), except for annoyingly not drawing the initial screen nicely.

So far I had to fiddle around with the screen (go to a sub menu, back out) to fix this display corruption, but today dealing with other things on my DICE I figured that the display comes up nicely after a reset initiated when the config file is updated. So there must be a better way than physically twiddling buttons I thought.

The solution is fairly simple: Patience. And this is how you introduce patience (at the end of your config.g):

M918 P1 E4 ;-- initialize screen 
G4 P500    ;-- wait half a second
M918 P1 E4 ;-- initialize again

People smarter than me may figure out how to teach the touch screen to talk PanelDue, other than the MKS one the BTT one is fully open source with all files available.

And here is a beauty shot:

Looks nice! What led you to choose repetier server over DWC?

I like weird machines, so I am biased (some may remember that I built a SCARA once just so).

I like that due to the limited overhead in Z it fits under my desk with room to spare at 80% the same attainable z height as my long-retired delta which needed almost a meter high uprights (I.e., triple the height).

I don't think it's super efficient in terms of space and recent CoreXY designs (like Voron0) beat it in that regard. The design is patent encumbered until 2022 I believe so you won't see it much outside non-commercial / research projects like mine.

That said, if we all would just build practical / sensible machines we would never enjoy things like deckingman's CoreXYUVAB -- not that I claim the same ingenuity or mechanical engineering skill. But that machine spurred the development of the mixing hotend; who knows what this or any other "objectively less practical than existing designs" will give rise to?

That's markforged kinematics and should be possible to define with M669 K11

@fxstein somewhat offtopic nit-pick, but "direct drive" and "direct" are two different things. "Direct drive" usually means an ungeared extruder (while I am nit-picking, I'll nitpick on myself and mention that this should be "filament feeder", with the opposite being geared extruder (like Bondtech or Hemera). The "direct" versus "Bowden" (no drive) are really "short distance" vs "long distance" (between filament feeder and hotend).

Here is the same printer 3 months later. I had to replace the heater due to broken cables, updated to the DICE specific hotend in the process, switched the belt carriage to one that clamps the belts with screws instead of gluing them in, fixed some screws, did remove all the various voltage fans with 5V ones, and added a small 12864 controller to the Maestro.

It's still due a few upgrades (I will need to find someone milling me the front plate with the air intake hole and an integrated holder for the 12864 rather than having one put on a 3d printed front plate with double sided tape, and I recently learned the hotend fan is not the right version (too little airflow, which explains my heat creep issues).

As for sample printed parts, the following picture has the motor bracket and flexshaft coupler for a remote direct extruder, as well as the under-effector fan assembly printed on the DICE with reasonable success. Maximum print speed was a conservative 100mm/sec

Here's config.g and config-override.g
vcp-config.g
vcp-config-override.g

This shorter gcode file did trigger the issue as well.

olm-x_end_stop.gcode

I was able to pare this down to two of the four objects on the plater, fixing them with netfabb made it possible to print them ...

So while the STLs had some errors, KISS did generate gcode, and I wouldn't expect RRF to memory fault on trying to parse gcode.

I am going to print the plater object by object now to see if a particular object triggers the Memory Fault Protection.

Forgot to add that running a simulation of the file works fine.

Hi,
I have a gcode file generated with the latest KISS Slicer v2 alpha which consistently soft resets the printer when I try to print it via DWC or serial console.

Here is M122 after trying to trigger a print with pronterface using M32:

Connecting...
Printer is now online.
>>>M36 "ormerod-leadscrew-mount.gcode"
SENDING:M36 "ormerod-leadscrew-mount.gcode"
{"err":0,"filament":[],"fileName":"0:/gcodes/ormerod-leadscrew-mount.gcode","firstLayerHeight":0.4,"generatedBy":"KISSlicer - PREMIUM","height":29,"lastModified":"2020-07-04T11:35:46.3573294+02:00","layerHeight":0.2,"numLayers":144,"printTime":null,"simulatedTime":null,"size":16576478}
>>>M32 "ormerod-leadscrew-mount.gcode"
SENDING:M32 "ormerod-leadscrew-mount.gcode"
File opened
File selected
[... serial connection resets ...]
>>>M27
SENDING:M27
[ERROR] Can't read from printer (disconnected?) (SerialException): call to ClearCommError failed
Disconnected.
Connecting...
ok T0:38.4 /0.0 B:79.6 /0.0
Printer is now online.
>>>M27
SENDING:M27
Not SD printing.
>>>M122
SENDING:M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
Board ID: 08DGM-9T66A-G63SJ-6J1D6-3SD6R-9U0BA
Used output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 154604
Dynamic ram: 162432 of which 20 recycled
Exception stack ram used: 292
Never used ram: 75868
Tasks: NETWORK(ready,1968) HEAT(blocked,1124) CanReceiv(suspended,3536) CanSender(suspended,1488) CanClock(blocked,1436) TMC(blocked,204) MAIN(running,4952) IDLE(ready,76)
Owned mutexes:
=== Platform ===
Last reset 00:00:20 ago, cause: software
Last software reset at 2020-07-04 12:54, reason: Memory protection fault, spinning module GCodes, available RAM 74976 bytes (slot 0)
Software reset code 0x0163 HFSR 0x00000000 CFSR 0x00000082 ICSR 0x04432804 BFAR 0x00000032 SP 0x2041787c Task MAIN
Stack: 00441df3 0040305a 610f0000 2044d648 00405159 0047280c 20417b10 20417a58 00000000 00000002 00000002
Error status: 0
[ERROR] Error status: 0

MCU temperature: min 39.3, current 39.7, max 39.9
Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0
Driver 0: standstill, reads 33324, writes 14 timeouts 0, SG min/max 0/0
Driver 1: standstill, reads 33324, writes 14 timeouts 0, SG min/max 0/0
Driver 2: standstill, reads 33328, writes 11 timeouts 0, SG min/max 0/0
Driver 3: standstill, reads 33325, writes 14 timeouts 0, SG min/max 0/0
Driver 4: standstill, reads 33326, writes 14 timeouts 0, SG min/max 0/0
Driver 5: standstill, reads 33326, writes 14 timeouts 0, SG min/max 0/0
Date/time: 2020-07-04 12:54:38
Slowest loop: 3.81ms; fastest: 0.14ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is ready with "M122" in state(s) 0
Aux is idle in state(s) 0
Trigger* is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon* is idle in state(s) 0 0, running macro
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 1.43ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 0 of 8
- Ethernet -
State: disabled
Error counts: 0 0 0 0 0
[ERROR] Error counts: 0 0 0 0 0

Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages sent 88, longest wait 2ms for type 6036
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 27ms ago
RX/TX seq numbers: 2333/640
SPI underruns 0, overruns 0
Number of disconnects: 0
Buffer RX/TX: 0/0-0

This is on an MB6HC 0.6 with a tool distribution board and a tool board, running RepRapFirmware 3.1.1

FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_DATE: 2020-05-19b2

The Gcode file is available at https://drive.google.com/file/d/1ZeHqJQDHAMaIg1NdQABQmRF3ZLk1Sa5F/view?usp=sharing

@FelixH you can power the Raspberry Pi from the Duet3, no extra PSU needed.

But you could also run the Duet3 in standalone mode and add an ethernet-wifi bridge like I do on the Duet 0.6 (GL.inet AR150M in my case because I had one lying around, but similar solutions can be had for about 20 bucks).

@Steve-Lynch in RRF 3 if you dont define a thermistor or bed heater, it won't look for one. In RRF2 you need to disable them explicitly (M140 H-1 IIRC).

Progress with some "original" upgrades: tensioning extruder and herringbone gears are a go, at least in this dry run:

https://photos.app.goo.gl/MfdNzu5QyG21fXnm6

Nice! I am still waiting for mine to be shipped ... can you also do some basic actions (homing, pause print)

@Phaedrux Bondtech offers 18Ncm pancake steppers and I had trouble driving a genuine BMG reliably with a 13Ncm pancake stepper, so I would recommend staying at or above those torque levels.