Thank you. I've updated the documents "Configuring RepRapFirmware for a Linear Delta printer" and "GCode" from https://duet3d.dozuki.com/c/RepRapFirmware. The document "Calibrating a delta printer" already included the information.

@fma As far as function, they seem the same. The 7i is a thinner overall package. On the other hand, the non-'i' version is better supported in regards to finding printable cases for it.

@t3p3tony I had merged your changes manually into the original SCAD file by David. It did not improve the results in my tests. They were actually a little bit worse. But currently my printing is completely on hold and will be for another couple of weeks. After that I will compare your updated version with the one I had created.

@giostark you should run G32 a few times, until it gets as close as possible to converged. Leave the mesh bed levelling out for now. Once you have it converged as close as possible then you can do mesh bed levelling if you need to. They are not the same thing. As you are using a BL touch off to one side it is worth manually checking the probe trigger height at each point you are using for G32 in bed.g. Start by confirming that probe correctly sets Z0 in the bed center. Then move to each of the other point and check the Z trigger height. If you see any difference (cause by effector tilt) the capture that in the H offset in the G30 commands in bed.g Cheers Tony

Is this a new problem? Have you recently upgraded to 2.02RC3? Idris

@maukvdlaan I have used my WorkBee for some serious work, including milling 40mm thick POM (but just 0.5-0.7mm on each pass!). Although I have it for about 8 months, it starts showing problems with the wheels on X and Z axis. In my setup, I have started with a Kress FME-P 1050 (left over from an eShapeOko) and GRBL. When Duet firmware had minimal "must have" support for CNC I moved away from GRBL and then I also changed to an 800W air cooled Chinese spindle with VFD. You mention "10 stepper motors". Considering the default 4 used in WorkBee, I guess you intend to have up to 7 spindles. My spindle with its mounting adapter weighs about 2.5kg. Your solution will be way over 5kg because for each spindle you will actually need a fully blown Z axis in order to be able to move it up and down, my bet being over 10kg. The C-Beam X axis will not be able to cope with such weight, showing significant deflection and allowing the Z axis to incline from vertical! A much better solution to your problem is to simply bite the bullet and go for a spindle with ATC. There is a 800W one made in France, if I properly recall, water cooled, weighing about 2.5-3kg, for about 2000EUR, or as a complete kit (including VFD, water pump, tool holders etc.) for about 3000EUR. Considering all steppers needed for your setup, V-Wheels, V-Slot profiles, nuts&bots, mounting plates and whatever, your final bill will be significantly higher! That being said, with Duet you can accomplish your current target rather easily because of the tool changing macros. Just make a general macro that homes all Z axis one after the other by simply homing the first Z axis, replacing the driver for the Z axis and repeat for all. Then make tool specific macros that call the general macro and then force the Z axis driver again and apply the tool offsets. When you change the Z axis you must also remember to change the spindle control pin(s). For homing all those Z axis, just connect all home switches in series (NC switches!). It is easier than having 7 separate wires to the Duet.

For your information: In monitor mode of the da Vinci 1.0 Pro I got: 330k-->29°C 99.8k-->62°C 46.9k-->96°C With these data the RRF configuration tool calculated: R25: 388403 Ω β: 3670 K Best regards Uli

@dc42 even when I commented the P0 out with ; , it stills runs when I tested M584 X0 . But still no motion from external drive 5 6 7 8.

If you can, print your duct in ASA or polycarbonate. Quite a bit more heat resistant.

I thought I replied to this a long time ago. I guess I didn't hit submit... Thanks for the information! I will look into M915. Thanks again!

@phaedrux said in Surface Finish : Duet path planner?: Something like the RailCoreII which has shown incredibly detailed prints at very low layer heights. It's a lot more sturdy and solid than a Dbot. Mine is a custom build and a tank, but I wonder if I should remove the sprint bed like I did with my delta. I'm somewhat encouraged by the results Thanks for your suggestions

I've seen an error message on the PanelDue console that hasn't shown up in the Gcode console. Wifi reported error: incomplete write wifi reported error: incomplete write It shows up twice like that. It happened once while trying to download a gcode file from the DWC. The download failed in the browser as well. Then it happened again uploading a Gcode file. But the gcode file seems to have uploaded correctly. When I saw the error message I checked the DWC console which was up and running but nothing was there. I then ran a M122 to see the diagnostics and the DWC reloaded and the printer paused for a second mid print and then carried on. When the DWC reloaded I ran M122 again. This time it worked. But doesn't seem to show anything amiss. Nothing was logged to the PanelDue console. === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02RC3(RTOS) running on Duet WiFi 1.02 or later Board ID: 08DDM-9FAM2-LW4SD-6JKF0-3SN6N-T2ZBY Used output buffers: 1 of 20 (20 max) === RTOS === Static ram: 28532 Dynamic ram: 98720 of which 12 recycled Exception stack ram used: 512 Never used ram: 3296 Tasks: NETWORK(ready,328) HEAT(blocked,1184) MAIN(running,3484) Owned mutexes: === Platform === Last reset 02:13:18 ago, cause: power up Last software reset at 2018-10-15 13:21, reason: User, spinning module GCodes, available RAM 3480 bytes (slot 0) Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d Error status: 4 Free file entries: 9 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest block write time: 0.0ms, max retries 0 MCU temperature: min 44.5, current 44.9, max 45.3 Supply voltage: min 23.8, current 23.9, max 24.1, under voltage events: 0, over voltage events: 0 Driver 0: ok, SG min/max 0/1007 Driver 1: ok, SG min/max 0/254 Driver 2: standstill, SG min/max 0/222 Driver 3: ok, SG min/max 0/240 Driver 4: standstill, SG min/max not available Date/time: 2018-10-21 16:43:25 Cache data hit count 4294967295 Slowest loop: 4.63ms; fastest: 0.07ms === Move === Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 150, MinFreeDm: 150, MaxWait: 0ms, Underruns: 0, 0 Scheduled moves: 191830, completed moves: 191800 Bed compensation in use: mesh Bed probe heights: 0.000 0.000 0.000 0.000 0.000 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 Heater 0 is on, I-accum = 0.2 Heater 1 is on, I-accum = 0.4 === GCodes === Segments left: 1 Stack records: 3 allocated, 0 in use Movement lock held by null http is idle in state(s) 0 telnet is idle in state(s) 0 file is doing "G1 X186.602 Y122.915 E0.08193" in state(s) 0 serial is idle in state(s) 0 aux is idle in state(s) 0 daemon is idle in state(s) 0 queue is idle in state(s) 0 autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 182.79ms; fastest: 0.08ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 1 of 8 - WiFi - Network state is running WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.21 WiFi MAC address 5c:cf:7f:ef:4a:74 WiFi Vcc 3.31, reset reason Turned on by main processor WiFi flash size 4194304, free heap 13216 WiFi IP address 10.10.0.63 WiFi signal strength -40dBm, reconnections 0, sleep mode modem Socket states: 0 2 0 0 0 0 0 0 === Expansion ===

Okay i solved my problem now. Forgot to flash the Firmware on the Wifi Module with M997 S1. Only flashed the main Firmware!

I have a bltouch also, but I don't use it in the resurrection macro. I home to z max endstop then continue if that makes sense. Hopefully that's what your after. I also had to use a UPS as I didn't have enough juice left to move up out of the way. I just used the battery on light through an optocoupler to an end stop and pause the print

@dc42 said in Short circuit of fan P0 and P2: Was your fan voltage selector jumper set to the VIN position or the 5V position? No, the jumper is on V_in. If I think about it, I probably short-circuited the 5 V pin with a fan pin. That would also explain why the diodes didn't burn out and the sparks on the measurement tip. Can you still communicate with the Duet through the USB port? No unfortunately not, the board is not recognized. U2 is the 3.3V regulator. If U2 and U11 fail, this usually means that there has been excessive voltage on the 5V rail. This may in turn lead to excessive voltage on the 3.3v rail. However, if the green 3.3V LED is lit, that is a good sign. After looking again, all LEDs except the 3.3 V are lit. This also explains why the board is not recognized by the USB. I already ordered replacements for U2 and U11, they should come the next days. If I have short-circuited the 5 V line with the 24 Volt, my odds probably are bad

@claustro it will be! We are working on a housing, hob, etc design that is more reliable.