@Marco-Bona said in Strange behavior with Bl touch:

@Phaedrux, I have understand where the problem lies, I have a small motor very close to the probe, if I enable the motor before touching the bed it creates some disturbance at bltouch.

From what I read before I went with BLTouch sensors on all my machines, they're very sensitive to noise. To combat this, on all my machines I've threaded the wires through a braided shield I bought from McMasterCarr. It's paid of as I don't have any repeatability issues with any of them, and two of them run next to motors and heater wires. I do heat shrink both ends to prevent the braided shield from fraying.

Interference-Shielding Expandable Sleeving
1/4" ID

I had a similar issue on a machine that showed vertical walls like in your picture. In my case, my extruder current was my issue. I increased my current from 600mA to 800mA in config.g and that took care of the weird striping issues. I'm assuming the backpressure inside the nozzle caused it to over/under extrude on a regular basis creating the bulging.

It's an easy test to increase your extruder motor current and then print again. Just something I've experienced with similar results as in your picture.

@ÖrjanE said in Files in /sys on RRF3:

Ok. I guess the relevant bin-files to keep are DuetMaestroFirmware.bin, DuetMaestroIAP.bin and DuetWiFiServer.bin. The others coming from the .zip seem to be for Duet3 or the other Duet2-cards.

DuetWifiServer.bin isn't something for a Duet 2 Maestro, its for the Duet 2 Wifi board so that one could be deleted also.

It might be nice if the M308 page actually told you that you can only have Sensors 0-31 defined. I converted my Duet Maestro config which used Virtual Heaters 100,101,102 to the RRF3 and took a little while to notice I couldn't setup sensor 100. Trial an error messages only let me go up to 31. It would be helpful if there was a note on the M308 GCode command.

I'm including this here for the next guy who ends up with the same issue I had trying to create the Virtual Heater 100, 101, 102.

@fcwilt

A laser engraver would be one example where you might use G29 to measure your bed surface, and then perform a G30 to re-zero your Z axis against an object your going to engrave to set the proper z height for the correct focus length. You want the laser to move in a consistent plane, but will want a different Z position for laser focus against an object.

The same can be said for a 3D engraver or a small milling machines.

Only thing I had to do with my Ender-5 when I installed a Micro-Swiss All Metal Hotend was rerun the PID tuning. It used the same thermistor and same heater cartridge, but had a different nozzle/heater block/throat/cold zone so I figured it'd be a good idea to re-tune the PID with the new hotend.

Beyond that, I didn't have to change anything else. Even my retraction stayed the same until I fitted the E3D titan as a direct drive.

I know this sounds a bit silly, but have you tried turning the second board off and back on a few times and try to connect between each power on?

I have (4) Duet 0.8.5 boards each with unique MAC addresses and IP Addresses, and every so often when I turn them on they don't respond on the network properly. In my case, I shutoff the machine, give it a second, and then turn it on again and try to connect. Sometimes it takes 2-4 attempts before the boards respond on the network. No idea why it works, no idea why it doesn't sometimes. I have found its more frequently an issue when a machine goes un-powered for a longer period of time which means it could be some capacitor issue in the 0.8.5 design is discharging over time causing the issue and the repetitive turning it on and off recharges it enough to behave.

I also found it happens less frequently when I changed my config lines for M552 to include the S1 parameter, but I still see this happen every so often.

I just noticed something while working with a few of my printers.

When you start a print, the PanelDue changes to the Status screen as expected. However, the title bar at the top doesn't reflect the currently printing file.

If I change screens to anything else, and then come back to the "Status" screen the title bar now reflects the current file that is printing.

Since the PanelDue changes to the "Status" screen automatically when it starts printing, I would have thought it would have updated the title bar.

I also went and checked, this behavior isn't new. My PanelDue v1.1 with Firmware 1.21.3 has the same behavior as the PanelDue 7i with 3.4.1-pre2.

Figured I'd bring this to someone's attention. I remember this being a new feature at some point early on displaying the current file being printed, but couldn't find that post.

@gasstaldy I believe you need to define Tool 0 and not Tool 1. You probably need to change your config similar to the one listed below.

; Tools
M563 P0 S"MK8" D0 H0 F0:1                          ; define tool 0
G10 P0 X0 Y0 Z0                                    ; set tool 0 axis offsets
G10 P0 R0 S0                                       ; set initial tool 0 active and standby temperatures to 0C

T0                                                 ; select first tool

When I did a similar setup on my Duet 2 Maestro, when I upgraded to Version 3.1.1 I had to change my deployprobe.g and retractprobe.g files to P0 instead of the P3 that I used with V2 firmware.

I don't know if that's relevant to your Duet 2 Ethernet, but something to try since you said your deploy macros don't work.

@gasstaldy I believe you need to define Tool 0 and not Tool 1. You probably need to change your config similar to the one listed below.

; Tools
M563 P0 S"MK8" D0 H0 F0:1                          ; define tool 0
G10 P0 X0 Y0 Z0                                    ; set tool 0 axis offsets
G10 P0 R0 S0                                       ; set initial tool 0 active and standby temperatures to 0C

T0                                                 ; select first tool

@mfs12 @Phaedrux One thing to note, this Out of Filament message appears to have no way to acknowledge it, either from the DWC or from the PanelDue. So from that perspective, something around this message should probably be addressed, It doesn't re-occur on the PanelDue unless I pull out the filament again, but it always displays when connecting to the DWC.

One side note which probably isn't important, but the Duet 0.8.5 with Firmware 1.26.1 and PanelDue with firmware 1.25; this pop-up does not exist or is not triggered. In all honesty, its almost better that this message isn't presented as it's not a constant nag as it is with the newer firmware. The out of filament still works as expected and pauses properly, but without the contact nagging pop-up or DWC message.

I fixed it by ordering a Micro USB to DIP Adapter 5pin Female Connector B Type PCB Converter pinboard from Amazon and then soldering jumper wires to the associated components based on the v1.1 schematic. Got it working and updated to 1.25.0 firmware now.

For anyone that finds this post in the future looking for that USB part number, your schematic calls out Micro-USB-Receptacle - TJC-0069-B47589-0001

@dc42 It may be pertinent to update the docs.duet3d.com site then reflecting the correct information.

@mfs12 What do you mean log?

When I connect to the printer via HTML, the console is empty apart from the Connected message. The Diagnostics has some information, but since the printer is sitting idle when the screensaver is active and still idle when I pull the filament would it even have any useful information? And I don't see any other "log" file being written anywhere.

By the way, I may not have mentioned it until now, but the printer can be sitting idle with screensaver for several hours after the print is finished before I manually pull out the filament which triggers this message. I don't like to leave filament sitting on the machine overnight if its not printing.

@mfs12 the same issue still exists. Attached is a screenshot of the issue. It may make more sense if you can see what happens.

You can see the screensave is still working in the background, but the popup for out of filament shows up on top and doesn’t stop the screensaver. If I click the red X in the corner, it stops the screensaver. I would have expected this particular popup to either popup behind the screensaver or cause the screensaver to be interrupted so the 120 timer starts again which would then cover this pop up if it wasn’t closed.

This happens every time I take the filament out after a print is done. Since my end code extracts the filament beyond the Revo nozzle, I don’t have to heat anything to pull filament.

@mfs12 That's fixed it now. The title bar changes to reflect the currently printing file. Any hope for an update for the v1.1 boards for this particular fix also?

There is a discrepancy in the instructions for flashing the PanelDue via the Duet controller.

https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_PanelDue

This page says you have to rename the .bin file to PanelDueFirmware.bin, which is fine. However, later on the M997 command example has the full original filename in the command. Obviously these file names are meant to match, but it has me wondering if it's still required to rename the .bin file or not. It works with the rename, but does it work without the rename like the example?

@mfs12 I'm not using any M291 for the pop-up. In my case its the Out of Filament pop-up when I pull the remaining filament out of the extruder motor. Since I use the Revo, I extract 18mm while hot. At that point I can pull the remaining out at any time with the manual lever.

This is on my machine with the 3.4.1-pre2 firmware currently. I'll try the pre3 and see if its any different.

@tratoon One thing that may help, your build surface looks rather thick in the pictures. I assume it is either a piece of glass or something similar. I'm also assuming it is sitting on the stock heatbed. If your parts are beginning to peel up at the corners, I would highly suggest increasing your bed temperature. I know you said you were printing at 60C heatbed, but if my assumptions are correct that temperature is underneath your build surface at the heated bed itself. Your build plate surface is probably not at 60C due to heat loss. Generally speaking, your heatbed should be at or near the glass transition temperature of the material you are printing. Depending on the brand of PLA, sometimes this is 60C others are higher. I have found 70C works very well when I use eSun PLA+. So I would recommend you increase your heatbed to 70C or even 75C to compensate for the thick build plate and see if you see any improvements.

Personally, I detest using any sort of glue or hairspray or brim when most times a clean build plate and a hot build plate will make for great bed adhesion assuming you don't have external factors cooling stuff off before the print is finished.