Re: [Video] Adding a USB Webcam to DWC with a Raspberry Pi

Hello, so i really like the idea of monitoring prints. Im following your advice and using MotionOS setup on an Orange Pi One. I have a Duet2 WiFi board and would really like to utilize the WiFi capabilities of the Duet to carry over the video image to DWC. Any suggestions as to this being possible? Thank you all!

@Phaedrux
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.3.13 on Sat Sep 24 2022 19:41:27 GMT-0600 (Mountain Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-242 Y-242 F6000 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F6000 ; go back a few mm
G1 H1 X-242 Y-242 F240 ; move slowly to X and Y axis endstops once more (second pass)
G1 H1 Z-266.5 F240 ; move Z down stopping at the endstop
G90 ; absolute positioning
G92 Z0 ; set Z position to axis minimum (you may want to adjust this)

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.3.13 on Sat Sep 24 2022 19:41:27 GMT-0600 (Mountain Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 Z-266.5 F6000 ; move Z down until the endstop is triggered
G92 Z-2.5 ; set Z position to axis minimum (you may want to adjust this)

  ; Configuration file for Duet WiFi (firmware version 3.3)

; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.13 on Sat Sep 24 2022 19:41:26 GMT-0600 (Mountain Daylight Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Ender3" ; set printer name
M918 P1 E4 F2000000 ; configure direct-connect display

; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S0 ; physical drive 3 goes backwards
M569 P4 S1 ; physical drive 4 matches drive2
M584 X0 Y1 Z2:4 E3 ; set drive mapping
M671 X-27:263 Y115:115 S10 P2 ; leadscrews at left (connected to Z) and right (connected to E1) of X axis
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E130.00 ; set steps per mm
M566 X1200.00 Y1200.00 Z24.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z720.00 E6000.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z100.00 E5000.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E1000 I50 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X-5 Y-15 Z-3.5 S1 ; set axis minima
M208 X235 Y235 Z250 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop
M574 Z1 S1 P"zstop" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin zstop

; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F200 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-56.6 Y-3.5 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X20:180 Y20:220 S40 ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S150 ; set temperature limit for heater 0 to 150C
M308 S1 P"spi.cs1" Y"rtd-max31865" ; create sensor number 1 as a PT100 sensor in the first position on the Duet 2 daughterboard connector
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 R2.383 K0.432:0.000 D17.52 E1.35 S1.00 B0 V23.8
M143 H1 S375 ; set temperature limit for heater 1 to 275C

; 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
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P2 S1 H1:0 T45 ; set fan 2 value. Thermostatic control is turned on

; Tools
M563 P0 D0 H1 F0 ; 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

; Custom settings

; Miscellaneous
M501 ; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
T0 ; select first tool

What if we could see the mathematics behind the representation of Z in the firmware files in a simple, field variable controller in the DWC. Where using text fields to supply user inputs of the real world numbers that controll the position and show corrections of all things related to Z positioning.

I would like to see this user adjusted model directly change the firmware variables for Z related data. Firmware files such as 'config.g's Z-probe sections Z-probe offset, 'homeall's Z-home position, absolute Z, etc.

Visual representation of the point of extrusion relative to the point at which printing begins on the bed. Everything else that surrounds and determines this in a scalable vector model controlled by the user.!

All-in-all be able to effectively synthasize a visual representation of the machines homing of the z. Maybe in real time have the numbers(variables) change according to the machine movements reguarding homing, probing in real time and as a simulated model using user inputs. Reminds me of the old Adobe flash projects in freshmen year.

@phaedrux
In DWC; Dashboard; Status box; under Sensors; Z-Probe. The output of the probe does not change, ever. I can invert the signal by adding an "!" in front of the "^zprobe.in" and the signal will appear to have been inverted in the Z-Probe Status field. But really thats a superficial readout change. So, having run the static test and hoping that the Duet 2 WiFi board picked up the tip touching the bed is to no avail. This is the second BLTouch I've used/tested with. Swaped the Z-Probe and the GND signals too... nada.

Hello! some issues withthe bltouch not showing any detection. Correct setup in config.g:

M558 P9 C"^zprobe.in" H5 F200 T6000

propper deployment and retraction of the probes solonoid through:

M950 S0 C"exp.heater3"

The wiring is correct and has continuity. Just isnt showing once the tip is drawn back after touching the bed. Anything helps!!!

Im trying to get a bltouch clone to pull from the duet2's expansion header's 5v and grnound pins #1 & #2. The multimeter is reading only +4.75v from the 5v and GND pins. I am using some Crealty 24v fans for the hotend so have pulled a 24v line to the fan power select center pin and have selected the EXTERNAL jumper and a 5v psu as the EXT 5V power source. Blade fuses check out. I'd like to think that locating the 5v regulator will be the imediate solution however I have noticed that at one point all 5, if not 4, board LED indicators were illuminated. Any suggestions or secret documents that would power up the expansion header?

@arhi Finding this Thermistor pin to be the one. As listed in the Hardware and Connections of the https://docs.duet3d.com/Duet3D_hardware/Duet_2_family/Duet_2_WiFi_Ethernet_Hardware_Overview#physical-connections: EXPANSION HEADER THERM7 (pin 39) e6temp, exp.thermistor7, exp.39 duex.e6temp. Wish I knew basic HTML and make this look like I have a clue.

@arhi Hello! Im looking for something along the similar to your query-- an analog pin for an input signal. Spicificly, I have a PT100 Amp board, temp. sensor that doesnt seem to use a MAX31865 chip. Triangle labs tl pt100 amplifier board. Deduced from their "official" AliExpress website, they state that only a single signal pin is required to recieve the one beseigheded 'signal' of analog discourse. Aside, a mere 5v and a 0v, or grounding pin secures the trios. Simple, right? Well, provided that this windy briefment is sufficient to satisfy any required knowlageable instruction and not interfere with the foreseeable future of the Duet 2 board I hope this might be the first, only informal documentation on attatching one of these things to a Duet 2. Please, anything further is always appreciaed and thank you for you time and responses.

@fickert so where are the follow ups to this general topic? I mean even a GENERAL response ANYWHERE in the forum would suggest some hope for the desk jockeys and neck crackers out there. Honestly, I thought there would be an easily found list, pdf even, at the top of any search engines response to search: DWC keyboard shortcuts. Nothing! Good luck, Im not a programmer by any means what so ever. Thanks.

@phaedrux
I see. I really feel like keeping the warranty active based on the various issues that have arisen in the past. However the time it has taken to resolve those issues has been a bit of another issue. Is there any middle ground we could take that solves the driver without voiding the warranty? I'm a big fan of resolution the 'smart' way, seems to serve better than any dumb way I've ever conceived. I appreciate having people smarter than mine in my corner. Thanks and I appreciate you.