Formbot 400
-
Seems weird to use a fan with M42 instead of M106. I'm not sure what the reason to do that would be.
At any rate, you'd still need an M950 command that creates the pin for M42 to use.
What port is the fan actually connected to on the board?
-
@phaedrux well I don't know but I have the settings that worked with reprap 2.0 below it shows what pin it is connected to but how can I configure this in my macro settings just copy and past from 2.0 to 3.0
;; Convenience macro to make this script be a button on the UI,
;; for cases when the built-in filament load/unload UI won't work.
;; NOTE you still need to have the tool selected before running this macro
;; or you'll get errors.M42 P5 S1.0
-
@unknowx said in Formbot 400:
well I don't know
You don't know where it's physically plugged into the board?
-
@phaedrux well no because I didn't open to see the board but the old macro config that worked fine states p5 so it must be port 5
-
Is it this one?
; --- Case Fan ---
M950 P5 C"duex.fan7"
M42 P5 S0.0 ;If that's where it's physically connected then your air filter macro needs to change to 5.
Either way, we need a pin name, like this C"duex.fan7"
-
@phaedrux well below is the config for reprap 2.0 which was working fine and the fan name and pin is the same but for reprap 3.0 it's not working see below
-
@unknowx said in Formbot 400:
the fan name and pin is the same
And if you were using a normal Duet board I might be able to guess what it is.
-
@unknowx I think I know what the issue is if you agree with me I think I have to remove the semi colon to activate it right?
-
which semi colon?
-
@phaedrux this one I'll market it before the command if you see the first config attached for reprap 2.0 the semicolons are removed to activate the command but the second config for reprap 3.0 the semicolons are there not removed.
-
@unknowx actually I am wrong g sorry the case fan is different t from controller fan my bad anyways still don't know why
-
Well we just need to know where the cable is physically connected. Perhaps it's labeled or next to a port that's already in use and configured and we can suss out the pin name that way.
The semi colon blocks out everything after it only.
