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

Very noticeable display lag on 3.5.2 on DWC when using Duet + SBC + PanelDue. Watching the temperatures rise/fall appears to be frozen, then quickly counts, then holds, then quickly counts again. Even watching the X, Y, Z, U positions also has this delayed display.

Functionally, it works, but it was not like this prior to 3.5.2.

I decided to test a little further back to see if it was firmware issues or hardware. I'm definitely leaning towards hardware issue.

I went and flashed the PanelDue V3.0a board with firmware 1.17 which was the oldest firmware I could find for V3 and connected it to the SSD1963QL9AU608F LCD screen. No good. The backlight comes on, but it just flashes a white line across the edge of the LCD screen. This PanelDue V3.0a refuses to drive this specific 7" LCD. It works with the PanelDue V1.1 and PanelDue V2.0 boards but does not work with the PanelDue V3.0a board. Go figure, but there must be something different on this specific LCD panel that's not compatible with this newer board.

Either way, I have a fix and will just swap the LCD panels on the machines until I get combinations that work.

@droftarts Yea, I'll check again, but that may just be a typo. Searching for SSD1936QL9 results in only entries for SSD1963QL9

Edit: So yea, I checked again. All the chips say SSD1963QL9 on one line, and the AUxxxxx on a second line underneath. Typo when I listed 1936QL9.

Only case where I'd buy another one would be if I upgraded my final Duet 0.8.5 Flexion machine to something newer. With the new Jubilee printer I've finished building and it having multiple tool heads, I may just dismantle the Duet 0.8.5 Flexion machine anyway. Will have to see how the Jubilee runs my Ninjaflex prints.

And the infrequent updates for PanelDue firmware, I'll never buy another integrated PanelDue LCD.

After Tim from Filastruder proved the PanelDue V3 board worked, I did some more testing with the one I still had and some older ones. It appears I came into an incompatible LCD screen that does not work with the PanelDue V3.

SSD1963QL9AU608F LCD screen works with PanelDue V2.0, and PanelDue V1.1 board, but does NOT work with the PanelDue V3.0a board
SSD1963QL9AU542AF LCD screen works with PanelDue V3.0a and a PanelDue V1.1
SSD1963QL9AU622F LCD screen works with PanelDue V2.0 board and a PanelDue V3.0a.

All of the combinations tried did not involve flashing any firmware. Only plugging in the already functional PanelDue boards to the various 7" LCD panels.

One additional thing to note, my PanelDue V2.0 board is pre-August 2016 and does not accept any firmware files above 1.25.

I'll just have to shuffle some LCD screens between printers for combinations that work, but I'll definitely think twice before order a new PanelDue interface board due to some of these unpublished incompatibilities.

Edit: corrected typo on SSD1963 part numbers.

Noticed I keep getting an error message showing up on the PanelDue. It states "Error: Pop(): stack underflow on Aux" This also shows up on the console if I have DWC already open.

This usually happens when I do some command on a PanelDue like Extrusion or home, or some other movement command. Then when I start a Macro, I get this error message pop-up. The Macro appears to run though, its just an annoyance message. I usually see this after I'm manually priming the extruder, and then run my macro to set the filament position prior to starting a print job.

Duet 3 Mini 5+ Mini5plus 3.5.1
Duet Software Framework DSF 3.5.1
Duet Web Control DWC 3.5.1
PanelDue 3.5.0 (4-wire connection only)

And yes, I am running a Duet 3 Mini 5+ in SBC mode with a PanelDue. I like the responsiveness of DWC from a Raspberry Pi 4, and the flexibility of going wired or wireless without any config change. It's also very interesting that the PanelDue can see and control the Duet 3 Mini 5+ even after I command the SBC to shutdown, but all the config is on the Raspberry Pi 4 with no MicroSD card in the Duet 3.

I've also seen the occasional message about slowing polling down, but that's only on the console of the PanelDue and not a pop-up message.

@Phaedrux Email sent and Filastruder copied. Thanks!

@droftarts

Tried the following firmware files:
https://github.com/Duet3D/PanelDueFirmware/releases/download/3.5.0/PanelDueFirmware-3.5.0-v3-7.0.bin
https://github.com/Duet3D/PanelDueFirmware/releases/download/3.4.1/PanelDueFirmware-3.4.1-v3-7.0.bin
https://github.com/Duet3D/PanelDueFirmware/releases/download/3.4.0/PanelDueFirmware-3.4.0-v3-7.0.bin
https://github.com/Duet3D/PanelDueFirmware/releases/download/1.25.0/PanelDueFirmware-v3-7.0-nologo.bin

I even tried a V2 firmware just to see if it acted any differently.
https://github.com/Duet3D/PanelDueFirmware/releases/download/3.5.0/PanelDueFirmware-3.5.0-v2-7.0.bin

I also tried a 7.0c version. This one didn't blink anything on my LCD which I wouldn't expect it to, but figured it was worth a try.
https://github.com/Duet3D/PanelDueFirmware/releases/download/3.4.0/PanelDueFirmware-3.4.0-v3-7.0c.bin

I also tried the other resolution ones to see if there was a difference.
https://github.com/Duet3D/PanelDueFirmware/releases/download/3.5.0/PanelDueFirmware-3.5.0-v3-5.0.bin
https://github.com/Duet3D/PanelDueFirmware/releases/download/3.5.0/PanelDueFirmware-3.5.0-v3-4.3.bin

BOSSAC flashes them all without issue, but nothing ever shows up on the LCD screen. Even just plugging in the USB cable to power the screen, the V3 PanelDue does not work.

I even tried flashing with BOSSAC on my Macbook Air and my Windows 11 PC, both using V1.9.1.

The LCD and the 4-pin cable work with the old V1.1 board, but not with this new V3 board. I'm wondering if this is a D.O.A. V3 PanelDue. It was still sealed in a pink bag prior to me connecting my LCD and flashing the firmware over USB the first time.

@droftarts
I can try put my Flea-Scope on it and see if it can see any differences.

Although, with all of these boards being brand new and only in operation a week or so, I wouldn't expect it to have a failed part already unless defective from the start.

@droftarts The cabling works if I replace the V3 board with the older V1.1 board.