It would be great to have a single button to zip all the files in the SD Card and download it. I know you can currently download all the system files, but it would be nice to include the other directories to simplify backup process.

1. Option to include specific directories (ie: gcodes, macros, sys, www, etc.)
2. Option to automatically append the current date and time to the filename to make the names unique

If this is not possible, at least having the option to "Download as ZIP" the files in the "macros" folder similar to the system files would be good. When I select all the macro files and folders and right click, there are no options to zip the files to back them up. The only option is to "delete" the files.

@Pao de Forma,

Stop being an idiot and you won't have to replace it with an inferior driver chip. If you have enough skills to solder and replace the TMC2660 chip with a A4988 driver and update the firmware yourself, you won't even have to ask the question in this forum. Stop wasting DC42's time and let him work.

If you really want a challenge, replace the core i9 extreme CPU on an Intel board with an 8088 CPU. It will keep you busy.

Any chance of adding function to download all the macros as a zip file instead of just having a "delete" option only?

@dc42 said in Firmware 2.0RC1 and 1.21.1RC1 released:

@shadowx said in Firmware 2.0RC1 and 1.21.1RC1 released:

@dc42 said in Firmware 2.0RC1 and 1.21.1RC1 released:

iap4e.bin

I still had the original iap4e.bin file from 6/11/2016. I didn't realize I had to update that until I looked at the bottom of the 1.21 which mentions the iap4e.bin should be revised also. Thanks.

Thanks for confirming. The original iap4e.bin file had the firmware filename hard coded as "DuetWiFiFirmware.bin". Later versions use the filename passed to them by the firmware that is being replaced.

I just did a quick test with the old iap4e.bin and it won't take the 2.0RC1 update. As soon as I updated the file to the latest one from 1.21, the update worked perfectly. Thanks for all your help. Hopefully, this will help someone else if they have not updated that file.

The diff lube stays on gears during rotation so it helps cushion the gaps. Its the preferred lube in this application. I had the same issues and the 10K diff lube completely eliminated any ripples on the surface. Now its all smooth.

David,

I think its better if you put a picture on the wiki for the 2 wire and the 4 wire config to make things clearer. Hopefully this image will help users out. This is for the production board, the jumpers are reversed for the pre-production boards.

@dc42 said in Bad PT100 board?:

@shadowx said in Bad PT100 board?:

On the 100 ohm resistor test, I attached a short jumper cable between 1&2 and 3&4 and still had the same results. The jumper wires measured around 0.7 or 0.8 ohms. Note, these measurements are on the top screws of the terminals on the PWB boards. I wasn't able to probe the bottom solder pads unless I remove the boards.

Those measurements sound good. Does the second channel on the PT100 board behave in the same way when you test using the 100 ohm resistor?

Yes. I was only able to test the second channel since the terminals on the RTD1 broke off. I can solder the wires or a connector to the RTD1 solder pads to test.

I have a Kingst LA1010 logic analyzer. Is there certain pins I can connect to on the board to check if I get the proper signals from the RTD board? I recall there was a schematic available somewhere but don't have the links to them anymore. I guess the basic checks is for power first to the board and then any output signals from the SPI interface.

Thanks for you help.

@dc42 said in Bad PT100 board?:

@shadowx with that board revision, when using a 2-wire connection or testing with the resistor, you need to add a link wire between terminals 1 and 2 and another between 3 and 4 (with the resistor fitted between terminals 2 and 3 as you have indicated), or alternatively put solder bridges across the pads provided.

I use a 4 wire system on my printer. My measurement between the two middle terminal (2 &3) is around 120 ohms. Between connection 1&2, I get around 1.1 ohms and 3&4, I get 1.2 ohms.

On the 100 ohm resistor test, I attached a short jumper cable between 1&2 and 3&4 and still had the same results. The jumper wires measured around 0.7 or 0.8 ohms. Note, these measurements are on the top screws of the terminals on the PWB boards. I wasn't able to probe the bottom solder pads unless I remove the boards.

I just hope it wasn't something stupid I did on the configuration file like left out a semi colon somewhere or added an extra space. I don't believe I changed anything, but its been a least a week since my last print.

I compared it to my last backup in June and I don't see any differences in the extruder heater or tool settings.

@phaedrux said in Bad PT100 board?:

@shadowx said in Bad PT100 board?:

M350 X16 X16 X16 X16 I1

I don't know if this is intentional, but you're setting the microstepping for the X axis 4 times in a row here but not the other axis.
That is an error on my part. The error has been there since 2018 and earlier that I overlooked. I have fixed the setting as shown in the results on the bottom of this reply.

As for your PT100 problems, have you tried reseating the board in it's connector yet?
I reseated the board multiple times. I took the board in and out at least 5 times.

Can you measure the resistance of R1 and R2 resistors? They should read ~400 ohms.
They are both about 400.1-400.5 ohms

@shadowx said in Bad PT100 board?:

Just as a sanity check, I unplugged the wires and put in a 100 ohm resistor in the terminals shown with red arrows. I can't read 0 degrees on my PanelDue or web interface. There is no temperature display for the extruder.

What exactly does it display for a temperature? The PanelDue screen does not show temperature for the extrude and the web interface shows the bottom image.

Finally, can you send M98 P"config.g" just to check for any syntax errors in your config?

Here are the error messages that came back. This is after fixing the M350 command to:
M350 X16 Y16 Z16 E16 I1

M98 P"config.g"
Error: in file macro line 31 column 19: M350: array too long, max length = 0
Error: in file macro line 32 column 25: M906: array too long, max length = 0
Error: in file macro line 36 column 24: M566: array too long, max length = 0
Error: in file macro line 37 column 25: M201: array too long, max length = 0
Error: in file macro line 38 column 28: M203: array too long, max length = 0
Error: in file macro line 41 column 18: M92: array too long, max length = 0
Error: Invalid extruder number '0'
Error: bad drive number
Error: Tool 0 not found
Error: Tool 0 not found

At first, after fixing the M350 command, the whining noise was gone and the PanelDue shows "Tool 0 not found". The macro turns on the bed heater bed, but I get the "tool 0 not found" error message. I thought fixing the M350 solved the noise issue at the time.

However, if I shut off the printer and restart it, the noise is back if I run the heater macro right away. After I home the printer, the noise is gone when I start my heater. I guess that noise is related to the motors and homing the printer first before I turn on the heater stopped that noise from happening. Note, when the motors where whining, I did not get a tool error on the panelDue, however, I had to use the stop button or that noise would not stop. After the printer homed, I had no more noise and that tool error message popped right up.

G10 P0 R0 S190  ; Set standby and extruder temp to 200C
M140 S65 H0 	; Set heated bed initial value to 65C
T0 				;  Select Tool 0 to turn on the extruder to active

Thanks for all your help.

I have a DuetWifi V1.0 board. Everything was running fine last week. When I turn it on today, it does not sense my extruder temperature. If I try to turn on my heaters, it generates a very loud pitched noise.

The first thing I suspect was a bad connection. I measured the resistance at the RTD1 terminals with the machine off and it was around 120 ohms. I checked all the connections and it seems fine.

Unfortunately, while working, the terminal on the board broke off. Since RTD2 was not used, I moved the wires to those terminals and changed my M308 to use "spi.cs2". I was not able to read any temperature on the RTD2 port either.

Just as a sanity check, I unplugged the wires and put in a 100 ohm resistor in the terminals shown with red arrows. I can't read 0 degrees on my PanelDue or web interface. There is no temperature display for the extruder.

I'm just wondering if the board went bad or if its a bad setting. Its hard to say its a bad setting when everything was working fine last week.

Does anyone have suggestions? I haven't probed the PT100 board yet or hooked it up to a logic analyzer. It just seems like its an upward battle since I migrated to RRF3.

; Configuration file for Duet WiFi
; executed by the firmware on start-up

; ---------------------------- General Settings ------------------------------------
M111 S0 		; Debugging off
G21 			; Work in millimeters
G90 			; Send absolute coordinates...
M83 			; ...but relative extruder moves
M555 P1 		; Set firmware compatibility to look like RepRapFirmare

; ---------------------------- Printer Bed Settings ------------------------------------
; Rod length settings for reference:
; L = Ideal Length / Measured_length * Original Delta Rod Length
; Larger Number = Smaller part size
; Smaller Number = Larger part size

; Delta Radius setting for reference:
; Lower number  - Middle get looser
; Higher number - Middle get tighter

; MANUAL CALIBRATION DATA
M665 L438.000 R264 H424.75 B150 				; M665 - Set delta radius, diagonal rod length, printable radius and homed height, B = safe printing radius
M666 X0 Y0 Z0									; M666 - Put your endstop adjustments here, or let auto calibration find them

; ---------------------------- Motor and Extruder Settings ------------------------------------
; Motor Settings
M569 P0 S1 										; Drive 0 (S0 = Backwards; S1 = Forwards)  X-Axis
M569 P1 S1 										; Drive 1 (S0 = Backwards; S1 = Forwards)  Y-Axis
M569 P2 S1 										; Drive 2 (S0 = Backwards; S1 = Forwards)  Z-Axis
M569 P3 S0 										; Drive 3 (S0 = Backwards; S1 = Forwards)  Extruder
M350 X16 X16 X16 X16 I1 						; Configure microstepping without interpolation
M906 X1000 Y1000 Z1000 E600 I30 				; Set motor currents (mA) and motor idle factor in per cent
M84 S30 										; Set motor idle timeout

; Acceleration, Jerk and speed
M566 X1000 Y1000 Z900 E170 						; Jerk - Set maximum instantaneous speed changes (mm/min)
M201 X2000 Y2000 Z2000 E200 					; Set accelerations (mm/s^2)
M203 X20000 Y20000 Z20000 E5000 				; Set maximum speeds (mm/min)

; Extruder
M92 X80 Y80 Z80 E2680 							; Set steps per mm; E value is in mm/minute    E2715
M572 D0 S0.18  									; Extruder pressure advance

; ---------------------------- End Stops ------------------------------------
; Endstops
M574 X2 S1 P"xstop" 							; Configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop" 							; Configure active-high endstop for high end on Y via pin ystop
M574 Z2 S1 P"zstop" 							; Configure active-high endstop for high end on Z via pin zstop


; ---------------------------- Bed Level and Probe Settings ------------------------------------
; Grid Mesh
M557 X5:205 Y5:165 S20 								; Define mesh grid

;Precision Piezo Settings
M558 P1 C"zprobe.in" H1 F400 T10000 R0.5 S0.1 A6  	; R- Recoverty Time before probing start; A - max times to probe each point; S - tolerance with each probe
G31 P500 X0 Y0 Z0.08 								; Set Z probe trigger value, offset and trigger height  (increasing z makes nozzle go lower)


; ---------------------------- Motor and Extruder Settings ------------------------------------
;Bed Heater
M308 S0 P"bed_temp" Y"thermistor" T100000 B3950 R4700 L0 H9		; Define bed temperature sensor
M950 H0 C"bed_heat" T0 											; Heater 0 uses the bed_heat pin, sensor 0
M307 H0 A366.5 C667.4 D11.7 S1.00 V0.0 B1 						; Bed heater setting
M140 H0															; Map heated bed to heater 0
M143 S100 														; Set maximum heater temperature to 100C
M570 S200 														; Set maximum heating time to 200s

;Extruder Heater
;M308 S1 P"spi.cs1" Y"rtd-max31865" F60	A"RTD1"					; Define E0 temperature sensor, RTD1
M308 S1 P"spi.cs2" Y"rtd-max31865" F60 A"RTD2"	    			; Define E0 temperature sensor, RTD2
M950 H1 C"e0heat" T1 											; Heater 1 uses the e0heat pin and sensor 1
M307 H1 A347.2 C180.2 D4.8 S1.00 V12.0 B0 						; Hot End heater setting

; ---------------------------- Fan Settings ------------------------------------
; Fan mapping
M950 F0 C"fan0" Q500		; Map Fan 0 to P0
M950 F1 C"fan1" Q500		; Map Fan 1 to P1
M950 F2 C"fan2" Q500		; Map Fan 2 to P2

; Fan Settings
M106 P0 B0 S0 H-1 			; Set fan 0 value, Thermostatic control is turned off
M106 P1 B0 S0 H-1 			; Set fan 1 value, Thermostatic control is turned off
M106 P2 B0 S0 H-1 			; Set fan 2 value, Thermostatic control is turned off

; ---------------------------- Tool Settings ------------------------------------
M563 P0 D0 H1 				; Define tool 0
G10 P0 X0 Y0 Z0 			; Set tool 0 axis offsets
G10 P0 R175 S190			; Set initial tool 0 active and standby temperatures.  R= standby S= active

; ---------------------------- Network Settings ------------------------------------
M552 S1 					; Enable network and acquire dynamic address via DHCP
M575 S1 P1 B57600			; Set the Serial Communication parameters

Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.3 (2021-06-15)
Duet WiFi Server Version: 1.26

@jay_s_uk I can't update to 3.2.11. Anything greater than 1.24 requires more memory and the v1.1 of the panel due has limited memory space.

Due to the lack of RAM this build will not run on version 1 or early version 2 PanelDue boards that use the ATSAM3S2B chip.

Version 1.0, 1.1 and earlier v2 PanelDue: ATSAM3S2B processor (64MHz, 32kb RAM, 128kB flash) - these are the ones that the new firmware probably won't run on.

I wonder if the PanelDue's firmware for the DoEmergencyStop() delay code: "Delay(1000)" after the M999 command needs to be increased to prevent the signal overlap that caused the command errors.

Probably not the most elegant solution, but if it works, it works.

	static void DoEmergencyStop()
	{
		// We send M112 for the benefit of old firmware, and F0 0F (an invalid UTF8 sequence) for new firmware
		SerialIo::Sendf("M112 ;" "\xF0" "\x0F" "\n");
		TouchBeep();											// needed when we are called from ProcessTouchOutsidePopup
		Delay(1000);
		SerialIo::Sendf("M999\n");
		Delay(1000);
		Reconnect();
	}

@jay_s_uk I am running 3.3 right now and the error is still there. My PanelDue firmware is 1.24 and its the latest for version 1.1 of the PanelDue hardware.

@dc42 I just installed RRF 3.3 and it seems to fix the problem. The Fan1 turns on for a brief second as designed. The Fan0 and Fan2 does not come on for a brief second when I reset the board. It looks good!

I still get the random command error messages as described by the link below. This only happens when I press the "STOP" button on the PanelDue. When I click on the "Emergency Stop" button on the web interface, the error message does not pop up.

I rechecked my wires to the PanelDue. It is only less than a foot long and is fully shielded the whole length other than the connector locations.

https://forum.duet3d.com/topic/17990/rrf3-paneldue-stop-function-results-in-a-false-error-message

Thanks for your help!

@dc42 Thanks for letting me know. My Fan0 is fine, but the Fan1 and Fan2 blips. For now, I will use Fan0 port.

@dc42 Is there a way to fix this problem in the config.g file or do I have to just remove the resistor on the other fan ports?