Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PWM Control Channel (BLTouch only) #38

Closed
hinotori74 opened this issue Jun 21, 2020 · 8 comments
Closed

PWM Control Channel (BLTouch only) #38

hinotori74 opened this issue Jun 21, 2020 · 8 comments

Comments

@hinotori74
Copy link

Hi all,

With Probe BLTouch is not posible select "exp.heaterX" (X=3,4,5,6 or 7) on "PWM Control Channel (BLTouch only)", only permit select duetx.pwmX (X=1,2,3,4 or 5).

Thanks

@chrishamm
Copy link
Collaborator

It is possible but the pin names are different:

	{ PortCPin(3),	PinCapability::wpwm,	"exp.heater3,exp.8,!duex.e2heat,!duex.pwm1" },
	{ PortCPin(5),	PinCapability::wpwm,	"exp.heater4,exp.13,!duex.e3heat,!duex.pwm2" },
	{ PortCPin(8),	PinCapability::wpwm,	"exp.heater5,exp.18,!duex.e4heat,!duex.pwm3" },
	{ PortCPin(11),	PinCapability::wpwm,	"exp.heater6,exp.23,!duex.e5heat,!duex.pwm4" },
	{ PortAPin(15),	PinCapability::wpwm,	"exp.heater7,exp.31,!duex.e6heat,!duex.pwm5" },

So exp.heater3 corresponds to duex.pwm1 etc.

@hinotori74
Copy link
Author

hinotori74 commented Jun 24, 2020

I had tried putting "duex.pwm1" but it didn't work. According to the above it should be "duex.pwm1" or "! duex.pwm1". The website (https://configtool.reprapfirmware.org) leaves it as "duex.pwm1".

@hinotori74
Copy link
Author

With "duex.pwm1" the bltouch pin was never activated. With "exp.heater3" it works perfectly.

@hinotori74
Copy link
Author

I confirm that "!duex.pwm1" works correctly. The website (https://configtool.reprapfirmware.org) leaves it as "duex.pwm1", the "!" sign is missing

@jhbruhn
Copy link

jhbruhn commented Jul 4, 2020

Using duex.pwm1 in the ConfigTool for what was previously exp.heater3 does not work for me, the BL Touch Probe is never deployed. When changing the channel to "!duex.pwm1" manually, it works, but this conflicts the ConfigTool...

@natthapolvanasrivilai
Copy link

natthapolvanasrivilai commented Jul 5, 2020

Using duex.pwm1 in the ConfigTool for what was previously exp.heater3 does not work for me, the BL Touch Probe is never deployed. When changing the channel to "!duex.pwm1" manually, it works, but this conflicts the ConfigTool...

Because of this issue, i've crashed nozzle hard to the bed once, . Definitely needed it fix, before more people crashing their nozzles to the bed.

@hinotori74
Copy link
Author

@chrishamm please, reopen the issue.

@chrishamm
Copy link
Collaborator

I'll invert the duex.pwm# channels in the next version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants