@dc42 That sounds great. Glad this will be implemented in the next firmware update.

Thank you for your fast response! I checked the wiring here: https://d17kynu4zpq5hy.cloudfront.net/igi/duet3d/c4tc5QKFkWux5iWq.full There it says the order for X and Y is: 2B-2A-1A-1B. One pair is A one pair is B so I connect one pair in the middle of the pin and the other pair on the two outer pins - or am I'm doing something totally wrong here? EDIT: one pair is BLUE/RED one pair is BLACK/GREEN previously the colour scheme was GREEN/BLUE/RED/BLACK now I changed it to BLUE/RED/GREEN/BLACK and tested it again.. ... same problem no Error but nothing moves

@phaedrux can you swap to the other pr100 port to confirm before rewiring?

Helped me a lot in replacing controlboard. Thanks a lot for all your effort

Here is the updated version, with some guides for the small tubing added. The copper heatblocks are from Alphacool and I have no clue how well they work . For now they are just attached with a ziptie. I do have some thermally conductive glue I want to use in the final version.

yes that is a bug

This one just popped up on twitter https://mobile.twitter.com/Machine_Elite/status/1164988969911799808

@dc42 My Apologies, my dyslexia is getting confused between the bootup logo Duet3D and my board(see below) RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03RC4 running on Duet WiFi 1.02 or later Board ID: 08DGM-917NK-F23T0-6J1DA-3S86T-KZBWD Used output buffers: 3 of 24 (17 max) Does this work with power resume, and if so then what am i doing wrong?

@duncan-rtfm Sorry to hear you're having such bad luck with wifi. I think you'll like the Ender 3 and Maestro combo. They are very well matched. https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+1:+Wiring/37

@sethipus The DBot isn't a very good candidate for enclosure. It's way more work than it's worth IMO. I've made do with a plastic shroud that can hang around the entire printer on it's stand. It's like a loose curtain. At the top is an exhaust duct. It works fairly well with ASA, etc, both with chamber temp and fume exhaust, but it's not perfect. 40c at best. A design like the Voron2 or RailCore II that are designed from the ground up for enclosure would be perfect... if you want another new printer.

Too bad the duet forum can't be merged with like a Discord server, that would be pretty cool and pretty convenient with how you can like tag or pin people or everyone in that particular thread, I'd be way more active on a Discord server, just saying, phone mobile notifications for the discord app are kinda nice, I have it notify my only when someone specifically tags me. @dc42 Not sure if you're interested in this at all, but I have have access to a few industrial machines, I found a way to get the list of the supported G-Codes and M-Codes in Fanuc's controllers. I have access to a 2014 Doosan Puma GT2100 CNC lathe and idk what year Doosan DNM 5700 mill and a very large and rather new Haas GR712 and two ProtoTrak controllers. Perhaps I'm unfamiliar with the specific intent of the Duet 3.0, but I vaguely remember a conversation with you about standardizing the G-Codes at least, as M-Codes tend to be manufacturer and/or machine application specific. I'll get lists/pictures of all the G-Codes and M-Codes if you want and if there's any other information you want/need from the Fanuc controllers (kinda wanna reverse engineer their controller myself cuz they are the standard for industrial CNC controllers). It's for several networking and interface ports, can't imagine it would be that hard to get code from the controllers:) Anything you wanna know about some of the industrial controllers we have in our shop?? Oh, and this is something cool I discovered is Macro B Programming on Fanuc controllers. Click here for a PDF on my Google drive about Macro B Programming inside Fanuc controllers It allows parametric hand programming for canned cycles like G71 on a CNC lathe which is a roughing operation. link to pictures of my program I created in a couple minutes

@skhotso said in z babystepping not working: doesn't look like this is getting many hits. I'm going to try formatting and reinstalling the dwc image. Did you check to see if the babystepping amount wasn't somehow set to zero or other very small amount? Frederick

Ok so this is annoying the heck out of me, especially since after the 2.03 update i had / have to redo my toolchange tpre/tpost/tfree gcodes for dual extrusion. (yes i read the release notes) I have a new problem that it is now doing an additional Y offset each time it is doing the coordinate offsets, as well as a Z offset where it moves the bed up when changing from t1 to t0, but then does not move it back down when switching from t0 to t1. This moves the bed up by the specified offset each time it is doing two toolchanges, until it crashes into the nozzle. But i should put that into a different thread. The point is i can not change the config files when troubleshooting. i have also done another firmware (re) update. I can connect over YAT, but when i want to M997 S1 it gets me this: M122<CR> Trying to connect at 230400 baud: failed Trying to connect at 115200 baud: failed Trying to connect at 74880 baud: failed Trying to connect at 9600 baud: failed Error: Installation failed due to comm write error ok WiFi module is disabled ok WiFi module is disabled ok WiFi module is disabled ok === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later Board ID: 08DGM-917NK-F23T0-6J9DJ-3S86S-TWBWD Used output buffers: 1 of 24 (6 max) === RTOS === Static ram: 25680 Dynamic ram: 93952 of which 0 recycled Exception stack ram used: 320 Never used ram: 11120 Tasks: NETWORK(ready,1360) HEAT(blocked,1172) MAIN(running,3756) IDLE(ready,160) Owned mutexes: === Platform === Last reset 00:06:57 ago, cause: software Last software reset at 2019-07-31 01:38, reason: User, spinning module GCodes, available RAM 11084 bytes (slot 2) Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d Error status: 0 Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest block write time: 0.0ms, max retries 0 MCU temperature: min 36.9, current 37.3, max 37.7 Supply voltage: min 24.5, current 24.5, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: standstill, SG min/max not available Driver 1: standstill, SG min/max not available Driver 2: standstill, SG min/max not available Driver 3: standstill, SG min/max not available Driver 4: standstill, SG min/max not available Date/time: 1970-01-01 00:00:00 Cache data hit count 1069836646 Slowest loop: 3.08ms; fastest: 0.07ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Move === Hiccups: 0, FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === DDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 0 Stack records: 1 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 idle in state(s) 0 serial is ready with "M997 S1M552 M552 M552 M552 M122M122M122M122M122M122" 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: 1001.22ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 0 of 8 WiFi - Network state is disabled WiFi module is disabled Failed messages: pending 0, notready 0, noresp 0 Socket states: 0 0 0 0 0 0 0 0 ok I have done some research and usually this problem resolves when updating the DuetWifiServer.bin file to the matching one with the firmware. I have also paid attention to install the firmwares while VIN is applied. @dc42 recommended to replace the board in this thread. https://forum.duet3d.com/topic/8541/duet-wifi-always-starting-and-will-not-connect-to-wifi/19 It is weird because it worked in the beginning, also after the 2.03 update it worked for some time flawlessly. If i replace the board, can i only do it with the resellers that i bought it from? I bought it from e3d, but i live in germany so it is sort of stupid. I also dont know if the sporadic inability to connect to DWC has anything to do with this, or not. But still. Is there anything else i can try? The firmware is 100% updated, all the files are, the second to last update before my attempt now was even through DWC. It´s really frustrating but i don´t want to chuck that board because i spent already 350€ between the board, 7i panel, breakout and pt100 board. Any help greatly appreciated. Thanks Max

One of the biggest issues with controlling 3D printers from PCs or single-board computers is that the operating systems that run on PCs and on most SBCs such as the Raspberry Pi are not real-time operating systems. That makes them fundamentally unsuitable for controlling 3D printers by themselves. There are variants of Linux/Unix that claim to be real-time (e.g. QNX), but none in widespread use in the open source community. IMO an obvious way forward would be to develop a variant of Linux that allocates only 3 cores of a 4-core RPi to Linux and runs a proper real-time OS such as FreeRTOS on the 4th. Together with a prioritised interrupt handling system, this could in theory allow an RPi alone to control a 3D printer properly. However, the RPi probably doesn't have enough I/O capability - although I haven't checked the Pi 4. Forget I/O expanders, they are too slow to drive stepper motors. FPGAs are a good solution where a limited and predefined set of tasks needs to be done very quickly; but in other cases, a 32-bit microcontroller is more flexible, easier to program, and probably costs less. We don't think it's worth using FPGAs in motion control applications unless there is a compelling need for extremely high step rates. Our strategy with Duet 3 is to support and encourage running the user interface and initial GCode processing on a RPi or other SBC, but to keep the motion planning and step generation on a dedicated processor running under a real time operating system. The ARM Cortex M7 MCU on the Duet 3 is possibly overkill in this application, but it gives us the CPU power and extra RAM to provide additional functionality in the future.

@minim said in Question about DWC v2xx: You can also use the old interface when you run dwc2.0RC7. Just add "/reprap" behind the link. I do that since I find the old easier to use. Thanks for that info. So far I'm liking the new layout. Frederick

@psychotik2k3 said in Questions about the "Save" Parameter R: @dc42 what about workspaces ??? i mean what is saved with G60 ? machine coordinates or workspace (ie g55) coordinates ?? also what is the lifetime of these saves ??? is it erased when rebooting the card, emergency shutdown ? power shutdown ? thanks In firmware 2.03 and later the machine coordinates are saved. So if you save the coordinates using G60, change workspace offsets, and then restore coordinates using G1 R, the tool head will move to the same physical position as when you saved it. Save points are forgotten when you reboot for any reason.

Mines 225- but when I look around the bed(which is set to build volume 450x450y and 225 origin offset I can move the piece around to like x300? I would think I would want to max out at 225? Guess that's a S3d bug I've never noticed. Would this be valid? G02 X220Y0 I0J-220.0

@phaedrux said in Another question about setting "Z=0 Datum": Logically you'd think it should be the probe that's at the center of the bed. That's how I do it anyway. I believe @dc42 Added that section with the 2.03 update. Perhaps he can clarify. It seems to be that the probe should be centered also. Perhaps we will hear from dc42. Frederick

I have tried all you have suggested and nothing has changed. Nothing is getting hot and I cannot find any shorts. Thanks.