Posts made by Phaedrux

The main thing was removing the probe mod pin and adding the pullup resistor enable, but recovery/settle time is a good idea for the bltouch anyway.

Do you have a cancel.g in /sys?

Are the motors being disabled or going idle?

Can you post a photo of your heightmap being displayed so we can see what you mean?

What firmware and DWC version are you using? Be sure you're using at least 2.05.1 and 2.0.7.

The heightmap is only active right after G29 has been run, or if the saved heightmap has been loaded with G29 S1. So you need to either run G29 before the print, or you need to load the saved map with G29 S1 in your slicer start gcode.

You can check to see if the correction is active by sending M122 and looking for the line :Bed compensation in use: mesh, comp offset 0.000

M913 is a percentage of M906. Does that help?

@icecube45 said in 3.1.1 - BLtouch doesn't function after cancelling a job.:

M558 P9 C"zprobe.in+zprobe.mod" H5 F120 T12000 A10 S0.018

Not sure if this will help, but modify this command to be:

M558 P9 C"^zprobe.in" H5 F120 T12000 A10 S0.018 R0.5

Do you have a cancel.g file in /sys?

Please post your config.g, your homing files, and your slicer start and end gcode. Also send a M122 and post the result.

Does the Bltouch work normally otherwise? You're able to home multiple times in a row?

Thanks for the video.

Your post script was edited out because it has absolutely nothing to do with 3d printing.

I've flagged this for @dc42 and @chrishamm to take a look at.

Can you also ensure that your pi/DSF is fully updated? And also please provide the results of an M122.

Tool fan is the fan of the selected tool. It makes more sense if you have more than 1 tool.

Where are your M950 commands to create the fan pins? They must come before the M106 commands.

; Fans
M950 F0 C"fan0" Q500                           ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1                                 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500                           ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45                              ; set fan 1 value. Thermostatic control is turned on

@omni A new post will get more visibility for your issue, especially with a descriptive title.

How do you have things currently connected to the board?

Your config.g looks ok provided you're actually using RRF3. Can you send M115 in the console to see the currently installed firmware version?

Can you try deleting your current heightmap.csv and running a new G29 to create a fresh one?

How are you trying to add them and what is happening when you do?

In DWC you should be able to go to the macros section and there are buttons to create folder or file. You can also upload a file from your computer.

2.0.4 is a bit old at this point, perhaps best to update to 2.05.1 and DWC 2.0.7 that comes with that release.

@omni Sorry. I'm not really failiar with that sensor. Perhaps best to start a new thread with your issue rather than tack on to this older thread.

The firmware update shouldn't make a difference to it, but updating the DWC would replace your modded version. You might be able to continue using your modded version as long as the DWC version is compatible with the new firmware version.

Most probes are like switches, either on or off, so a value of 1000 or 0. But analogue probes are different and you can get a range of values between 1000 and 0 and that can be used to detect when the probe is getting close to the bed and start to slow down.

@omni said in Help with pulse-generating Filament Sensor:

S0

S0 is disabled, is it not? Try S1 maybe?

Were you perhaps using RRF3 config on a RRF2 board?

@Bmilam said in USB Drivers:

here is the broken link:
https://github.com/Duet3D/RepRapFirmware/blob/dev/Driver/DuetDriverFiles.zip

Where was that link from? We should get it corrected.

What does your temp graph look like?

What is your bed heater?

What is your PSU?

How is it wired?

What is the thermistor?