Prevent fan burst during startup on RRF 3.2.2

ShadowX

@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?

dc42

@shadowx Fan 1 is intended to be on by default, because we intend you to use it as the hot end heatsink cooling fan. The idea is that if the hot end is hot and you reset without the SD card present, or you upload new firmware, the fan will be on by default.

Fan 2 should not blip at startup. Resistor R91 should hold the gate low (resisting the pullup resistor in the MCU, which has a resistance between 50K and 150K) until the firmware sets it low.

If this still happens with firmware 3.3 then I will test whether it happens on my bench system.

If you have any spare heater ports on your Duet, you can use those to drive fans.

ShadowX

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

dc42

@shadowx have you tried firmware 3.3 yet?

ShadowX

@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!

jay_s_uk

@shadowx that's been fixed in 3.3.0 I believe

ShadowX

@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.

ShadowX

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

@shadowx I suggest upgrading the paneldue to 3.2.11 to see if it can be replicated

ShadowX

@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.

jay_s_uk

@shadowx sorry. Didn't realise you had an older one