I was able to get the Wyzecam V2 with the Dafang firmware working to provide a video feed in DWC using the Safari browser. The video is choppy, but sufficient to monitor the progress of a print. In the Dafang firmware, I changed the Codec for RTSP Server to "MPJEG" (MPJEG is probably a typo in the Dafang firmware) and the video size to 1280x720 (larger and smaller sizes also worked). I then assigned a fixed IP address to the Wyzecam on my router. In DWC, under Setting, General, Webcam, I inserted the Webcam URL as "http://xxx.xxx.x.xx/cgi-bin/currentpic.cgi" (where xxx.xxx.x.xx is the fixed IP address I assigned), set the Webcam update interval to 500ms, repeated the above URL exactly under URL to open when Webcam image is clicked, and turned off both "Do not append extra HTTP qualifier when reloading images" and "Embed webcam image in iframe." Hope this helps.

You are correct, the height would not matter at that point.

@brewchester Just checking to best sure. BLTouch version 3.1, at least for me, worked out of the box (after adjusting the mounting height). Earlier versions required cutting a trace on the PCB to operate on 3.3V logic; this was not required for the v3.1.

Here are my BLTouch settings (I am on firmware version 3.1.1), if it helps:

; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F90 T10800 A10 S0.005 ; set Z probe type to bltouch and the dive height + speeds probe up to 5 times until 2 consecutive readings are within 0.005, if none average of 5
G31 P500 X67.5 Y-11.5 Z2.946 ; set Z probe trigger value, offset and trigger height
M557 X70:280 Y15:255 S30 ; define mesh grid

The mounting specs (for the pin height relative to the tip of the nozzle) for the BLTouch, if I recall correctly, changed with the v3.1, compared to earlier 2.X versions. You might want to double check the antclabs manuals (available at www.antclabs.com) to verify your retracted pin height is within that specified for the v3.1 ). I have mine at 3.3mm above the nozzle tip - in the middle of the acceptable range.

What version BLTouch do you have? It is typically printed on the PCB visible from the outside of the BLTouch.

If you search the forum for "Cura Script to Automatically Probe Only Printed Area" that thread contains Python scripts (and detailed instructions) you can add to your slicer (Cura, S3D and Prusa Slicer) to automatically probe the bed for the area occupied by your model. This has been working very well for me using both Prusa Slicer and Cura.

I was able to get the Wyzecam V2 with the Dafang firmware working to provide a video feed in DWC using the Safari browser. The video is choppy, but sufficient to monitor the progress of a print. In the Dafang firmware, I changed the Codec for RTSP Server to "MPJEG" (MPJEG is probably a typo in the Dafang firmware) and the video size to 1280x720 (larger and smaller sizes also worked). I then assigned a fixed IP address to the Wyzecam on my router. In DWC, under Setting, General, Webcam, I inserted the Webcam URL as "http://xxx.xxx.x.xx/cgi-bin/currentpic.cgi" (where xxx.xxx.x.xx is the fixed IP address I assigned), set the Webcam update interval to 500ms, repeated the above URL exactly under URL to open when Webcam image is clicked, and turned off both "Do not append extra HTTP qualifier when reloading images" and "Embed webcam image in iframe." Hope this helps.

@dc42 @Phaedrux Thank you both for your help. I contacted Printed Solid and they are processing a warranty exchange.

@dc42 Yes, I was reading the soldered pins of the 4-pin connector from the front side of the PanelDue.

@dc42 Thank you for the reply. I monitored voltage from the 5V and ground connections on 10-pin CONN_SD connection on the Duet 2 WiFi and saw a consistent 4.90 to 4.91 volts. I also monitored 5V and ground from the soldered ends of the 4-wire connector on the PanelDue and saw voltage between 4.85 volts and 4.89 volts. Interestingly, when the screen appeared normal, the voltage on the PanelDue was typically 4.88 volts. If I pressed the screen (which caused the screen to turn white), this caused the voltage to drop to 4.85 volts. After about 30 seconds the screen would return to normal and the voltage would climb back to 4.88 volts.

Again, the PanelDue worked perfectly with none of these issues for the first four weeks after I installed it. I have not made any changes to the mechanics or electronics of the 3D printer since installing the PanelDue, only minor tuning since upgrading the Duet Firmware to 3.1.1, which I did in conjunction with the installation of the PanelDue.

If you think it might remedy this issue, I can make third connection cable for the PanelDue (I am thinking of using 8-conductor ethernet cable, crimping two conductors from the ethernet cable for each of the four connections on the PanelDue).

Thank you for the reply. The 1 m four-wire cable supplied with the PanelDue has 26 AWG plastic-coated wire. The 65 cm four-wire cable I assembled is 24 AWG silicone-coated wire. I do not believe that my multimeter was designed for precise measurements of fractions of an Ohm. Each conductor from the supplied cable and my assembled cable measure 0.5 Ohms (tested at the pins, which suggests the crimps on both cables are fine), which is the same reading I get by touching the leads for my multimeter to each other.

I am reading a steady 4.91 volts on the 5 volt connection for the PanelDue on the Duet 2 WiFi, even when the BLTouch is going through the deploy and retract testing on startup. What voltage should I be seeing on the 5 volt rail?

The PanelDue was working fine for about 4 weeks.

I purchased the PanelDue 7i approximately six weeks ago from Printed Solid, and installed it on my Core XY printer (based on the Hypercube Evolution) with an existing Duet 2 WiFi control board. The PanelDue is connected with a four-wire cable, with the wires twisted to help prevent interference. Following installation, the Panel Due worked flawlessly for about 4 weeks under relatively light use (a few prints per week). About two weeks ago, my PanelDue began to have thick, white horizontal lines on the screen. These lines would, on some occasions disappear, but as soon as I touched the touch screen, the entire display would turn white for about 30 seconds, after which the screen would typically return to normal, until touched again. In this state, I am not able to use the PanelDue and have had to resort to DWC.

To attempt to rectify this issue, I have:

• Reset the PanelDue;
• Re-routed the four-wire cable so that it is not near any other wiring;
• Replaced the four-wire cable (65cm in length) with one made with silicon wires and new connectors and pins that were supplied with my Duet 2 WiFi;
• Removed the PanelDue from its enclosure;

None of these efforts have solved the screen issue. When I power the PanelDue from USB (disconnected from the Duet 2 WiFi) the screen does not exhibit these issues. The PanelDue is running firmware version 1.24, and the Duet 2 WiFi is running firmware version 3.1.1. The Duet 2 WiFi is powered by a genuine Meanwell 24 volt power supply.

If the forum permits, I am posting two images showing the horizontal lines (with and without the enclosure). The lighting causes the horizontal lines to appear blue, but they are white. These were taken while the printer was idle.

Any thoughts or suggestions? Could my PanelDue have a defect?