; Configuration file for Duet WiFi (firmware version 1.20 or newer) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool on Mon Jun 18 2018 23:27:29 GMT-0300 (Hora oficial do Brasil) ; General preferences G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves M667 S1 ; Select CoreXY mode ; Network M550 PJose Arthur Printer ; Set machine name M552 S1 ; Enable network M587 S"ASSJA1" P"291005gus" ; Configure access point. You can delete this line once connected M586 P0 S1 ; Enable HTTP M586 P1 S0 ; Disable FTP M586 P2 S0 ; Disable Telnet ; Drives M569 P0 S1 ; Drive 0 goes forwards M569 P1 S1 ; Drive 1 goes forwards M569 P2 S1 ; Drive 2 goes backwards M569 P3 S1 ; Drive 3 goes forwards M350 X16 Y16 Z16 E16 I0 ; Configure microstepping without interpolation M92 X80 Y80 Z400 E100 ; Set steps per mm M566 X900 Y900 Z10 E120 ; Set maximum instantaneous speed changes (mm/min) M203 X12000 Y12000 Z300 E3000 ; Set maximum speeds (mm/min) M201 X1000 Y1000 Z100 E5000 ; Set accelerations (mm/s^2) M906 X800 Y800 Z800 E820 I30 ; Set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y-50 Z0 S1 ; Set axis minima M208 X200 Y200 Z200 S0 ; Set axis maxima ; Endstops M574 X1 Y1 S0 ; Set active low endstops M574 Z1 S2 ; Z-Probe M558 P7 H6 F120 T6000 ; Set Z probe type to switch and the dive height + speeds G31 P20 X0 Y50 Z0 ; Set Z probe trigger value, offset and trigger height M557 X25:175 Y25:175 S20 ; Define mesh grid ; Heaters M305 P0 T100000 B3988 C0 R4700 ; Set thermistor + ADC parameters for heater 0 M143 H0 S120 ; Set temperature limit for heater 0 to 120C M305 P1 T100000 B4725 C0 R4700 ; Set thermistor + ADC parameters for heater 1 M143 H1 S280 ; Set temperature limit for heater 1 to 280C ; Fans M106 P0 S1 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off M106 P1 S1 I0 F500 H-1 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off M106 P2 S1 I0 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off ; Tools M563 P0 D0 H1 ; Define tool 0 G10 P0 X0 Y0 Z0.5 ; Set tool 0 axis offsets G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C ; Automatic power saving M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss ; Custom settings are not configured ; Miscellaneous M501 ; Load saved parameters from non-volatile memory T0 ; Select first tool

Same issue here. Reverted to DWC1.21 as a test. When 1.21.1 stopped responding, I captured this from ctrl+shift+j XML Parsing Error: no root element found Location: http://10.10.30.86/rr_download?name=0:/sys/oem.json Line Number 7, Column 1: rr_download:7:1 Use of nsIFile in content process is deprecated. NetUtil.jsm:302:12 Removed unsafe attribute. Element: svg. Attribute: xlink. react-dom.js:11623:4 Removed unsafe attribute. Element: svg. Attribute: xmlns. react-dom.js:11623:4 Removed unsafe attribute. Element: svg. Attribute: xlink. react-dom.js:11623:4 Removed unsafe attribute. Element: svg. Attribute: xmlns. react-dom.js:11623:4 Removed unsafe attribute. Element: svg. Attribute: xlink. react-dom.js:11623:4 Removed unsafe attribute. Element: svg. Attribute: xmlns. react-dom.js:11623:4 Removed unsafe attribute. Element: svg. Attribute: xlink. react-dom.js:11623:4 Removed unsafe attribute. Element: svg. Attribute: xmlns. react-dom.js:11623:4 Removed unsafe attribute. Element: svg. Attribute: xlink. react-dom.js:11623:4 Removed unsafe attribute. Element: svg. Attribute: xmlns. react-dom.js:11623:4 Use of nsIFile in content process is deprecated. NetUtil.jsm:302:12 Removed unsafe attribute. Element: svg. Attribute: xlink. react-dom.js:11623:4 Removed unsafe attribute. Element: svg. Attribute: xmlns. react-dom.js:11623:4 Removed unsafe attribute. Element: svg. Attribute: version. react-dom.js:11623:4 Error: WebExtension context not found! ExtensionParent.jsm:861:13 On average, I would have 10-15 seconds to perform an action before everything stopped responding. I even got to the point of using an Asus RT-N16 as a wireless AP on my second VLAN (10.10.30.0/24 for wireless clients) wired to my trunked switch. I placed the AP in the same room about 6-7ft away. No dice on that front. While typing this, I popped back into the machine and was able to update a macro about 3 minutes after connecting. This is a massive improvement compared to reloading DWC between each button click and pre-typing commands/macros for a copy/paste in 1.,21.1. RTOS full release on DuetWifi. My second machine has the same issue, just not to such a great extent. Both have the "disappearing.config.g" experience.

@dc42 M122 reports; WifFi/Ethernet version 2.0(RTOS) running on Duet WiFi 1.02 or later Board ID: ....a very long sequence of letters. Nothing else.

@rcarlyle I've been wanting to try playing around with Klipper using the duet as the MCU. Best of both worlds if you will. Best in class electronics and very high steps rates. If klipper succeeds in implementing s curve motion planning before the duet I will probably give it a shot.

Come faccio a capire a quale motore (P) corrisponde il segnale E2 della breakout?

@zerspaner_gerd your sensors look nice, but I would check that someone has already written a blog about how to connect it to arduino at least. Some vendors sell sensors where you have to pay much for the data cable or software to access the data. You could check how the filament sensor is implemented to see which ports are possible, also. This sensor is implemented as M591, maybe a watercooling sensor can be implemented in firmware also.

Ah yes. Reading comprehension impaired due to fatigue and reading on a phone while eating in hospital cafeteria. I should probably not bother but the distraction is nice.

Great info @dc42 . With this stuff, finding out what to do is half the fun!

I have added this to my list to investigate when I start working on the next PanelDue firmware release.

Try adding I1 to your m558 command for the 3d touch. It may behave differently than the BLTouch. How is it wired? Is the pin clean and straight? Does it move freely by hand?

@phaedrux what is the extruder? It totally goes away if you revert to a previous firmware version?

Can you post your homing files?

Thanks.. !! I'll look into that. I'm still in the design phase of everything so i'll look and see if there may be a another way of doing multi-material instead of directly form the duet. I know in interviews Prusa mentioned that they are using a arduino for the material handler so maybe I can do the same and use one of the data parts. I wanted to map each material in the changer as a tool and use the Tx command to switch between materials. this may still be possible as i haven't gotten all the way through the documentation.