Posts made by zendesigner

mmm, now it stays -1% to max 1% ??

Duet3D laser filament monitor v1 on pin xstop, disabled, allow 10% to 120%, check printing moves every 3.0mm, calibration factor 1.000, version 1, measured min -1% avg 0% max 1% over 14966.6mm

@dc42

hi thanks for the help. they flash quick blue when filament goes through, but one didn't do it consistently.
I removed it and there was some scraping dust blocking inside the sensor. so that was the culprit.

it's starting to measure now

Duet3D laser filament monitor v1 on pin xstop, disabled, allow 10% to 120%, check printing moves every 3.0mm, calibration factor 1.000, version 1, measured min -1% avg 0% max 0% over 92.9mm

cheers
Zen

do i have the same issue as this topic ? i'm on 3.4.5

https://forum.duet3d.com/topic/31001/magnet-filament-monitor-v4-calibration-issue/35?_=1698699481372

Hi,
As i'm going over all my printers to get them perfect, i noticed now in my Tronxy5 3 extruders that my filament monitors have not been tested yet.

When i do a M591 D0 i get this:

Duet3D laser filament monitor v1 on pin xstop, disabled, allow 10% to 120%, check printing moves every 3.0mm, calibration factor 1.000, version 1, measured min 0% avg 0% max 0% over 911.0mm

It seems not to measure anything. they have their ligths on and flashing so might be something else.
this is my config

;filament monitors
M591 D0 P5 C"xstop" R10:120 E3.0 S0 ; Duet3D laser sensor for extruder drive 0, connected to endstop input 0 (E0), tolerance 10 to 120%, 3mm comparison length, disabled
M591 D1 P5 C"ystop" R10:120 E3.0 S0 ; Duet3D laser sensor for extruder drive 1, connected to endstop input 1 (E1), tolerance 10 to 120%, 3mm comparison length, disabled
M591 D2 P5 C"zstop" R10:120 E3.0 S0

thanks zen

@droftarts

Forever in your debt . that indeed did the trick.

My config g must have lost the configuration for the DUEX2 (not5 by the way)

I uploaded my config with the repraptool and came to the conclusion it didn't have the duex2 in the file.
then saw your post

IT's back to all working now with this fan config

cheers mate

Ok, so i opened up the electronics case.

so i'm basically running a DUET 2 wifi with an duex5 expansion board.

The Led strip are attached to FAN 3,4 and 5 on the expansion board.

What has gone wrong in my config.g somewhere in the past , or did something on the board fail ?

@droftarts

hi Ian, it's 1 strip in a kossel metal side tower with RGB leds. so 3 strips in paralell with maybe 30 leds in each, they always worked at full brightness so it's probably not a power issue. they also flicker briefly when i reset or start the board so they are getting power still. The hardware connections box has not been opened for years.

So i assume it's firmware change related. i'll play around with the frequency a bit.

thanks

@Phaedrux
thanks, they are not Neopixels though. just simple strip with 4 wires ground, red, blue, green.

think i probably have to open it up to see how it is connected to the board. I did it in a time where leds where just able to be controlled by the board, so i think they were just coupled to the fan's pins.

it always worked through the m106 command. i never used the m150 command so they are probably not on that header connected

HI on ly Kossel metal with Duet wifi i installed long time ago 3 rgb led strips where each color was controlled by m106 commands to light up during different stages of the print.

This is how the slicer 'simplify3d' sets the commands:
start
G28 ; home all axes
G21 ;set millimeters
G1 F200 E-3 ;retract filament for probing
M106 P4 s0 ;turn blue leds off
M106 P3 s255 ;turn leds red
G32 ;probe bed
G1 x0 y0 Z75.0 F2000 ;move the platform down 75mm
G92 E0 ;zero the extruded length
G1 F200 E13 ;extrude 10mm of feed stock
G92 E0 ;zero the extruded length again
G29 S1 ;load height map
G4 s5 ;pause 5 secs
G1 F500 ;start print

this was on firmware 1.2

now with recent firmware updates i've lost the functionality of these leds. the flicker whne the board restarts so they are still getting power. Just the board or gcode file seems to have forgotten on how to invoke them.
current gcode

; 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 S0 H-1 ; set fan 1 value. Thermostatic control is turned off
M950 F2 C"led1" ; create led 1 on pin fan3 and set its frequency
M106 P2 S0 H-1
M950 F3 C"!led2"
M106 P3 S0 H-1
M950 F4 C"led3"
M106 P4 S0 H-1

i don't want to open up the hardware underneath if possible to see the pins as it's all tightly packed.

SO did anything change in the Gcode or m106 command settings the board pins going from 1.2 to this version?

Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.5 (2022-11-30)
Duet WiFi Server Version: 1.27

cheers
Zen

seems i have a wiring issue. compared it with my other printers

Hi,

I got the boards working now and switched around the X,Y,Z1,Z0 to the duex5 and the E0, E1, E2 on the Duet wifi 2 i'm running RRF3.2 now.

Now i'm getting cofused with choosing the right drives and endstops in the RRF tool. And that compared to the wiring diagrams of both the duet2 and the duex5.
The tool shows different endstop names as the wiring diagram , and has 2 X,Y,Z driver letter assignments. When you add the duex5 as a board it adds choice boxes same as the original ones.

Is there a pinout list of names anywhere, so i can clearly change it in the config.g later?


hi ,

Thanks for the help. I'm using an RRF2 board still from an older printer.

Will let you know how it went

zen

HI I'm having following issue/question.

I'm working on a large 3 color corexy printer. It has 4 steppers for movement (x,y,z1, z2) and corresponding microswitches endstops (x, y, Z, E0 for Z2) . Now i have 3 steppers for extruders with 3 laser filament sensors.

I have a duet 2 wifi + duex 5 were i'm using the duet5x for the extruder steppers (e2,e3,e4) and wanted to use the corresponding endstops on the duex 5.

Now i read in this forum that laser filament sensors can't be used on the duex 5 due to a limitation in the board.

So my question is now how do i fix this ?

Can i place the movement steppers and endstops on the DUEX 5, and the extruders and filament sensors on the duet 2 ? so complete reversed from my original approach.
And if so how you configure this then in the software ?

Or are there better ways to get the 3 filament sensors working on duex 5 ?

Cheers
Bart

wow Great,

I just bought a WMD30LV mill and planning on converting it to CNC. i have some duet wifi boards lying around and would like to use them as i have them in all of my 3d printers.

This certainly would make the special zero requirements and the jogwheel possible in a really nice way.

Cool dude, really thanks.
Zen

ok thanks will do

cheers
bart

Hi Simon,

I'm afraid it still doesn't work. the indication in duet wifi is ok now but, the piezo still reacts only when you let go, not when you put pressure on it. So the nozzle keeps pushing into the bed. and doesn't trigger the duet.

The piezo is mounted with the connector towards the nozzle tip. just like your video. Do i need to turn it around ?
Or could it be that the piezo's are not soldered correctly as you say that in one of your video for the old model also ?

Let me know what to do.

Bart

HI sImon,

Thanks for your excellent help. I tried the low setting before but it hought it was L1 instead of I1. So kinda misread the font

Now the value is 0 and goes to 1000 is being tapped.

Cheers

Bart

HI Simon or maybe DC42

I'm currently testing the orion module you send me on my Duet wifi. Duet is configured with wifi and i'm testing the zprobe and end stops to see if it works.

So now i have this upside down behaviour.

• The orion reacts to taps and switches from a red led to the blue one. I calibrated the sensitivity and thats ok. Now when i just push on my hotend it only triggers when i release it. I looked at your tuning video and you mention if this happens that you have soldered the piezo wrong. so don't think this is the case here as i installed exactly the same as your latest video.

• Now in the webinterface of duet the Z probe is seen + the voltage is ok. But it stands constanly at a value 667 and when i tap the orion it returns quickly to zero.

*reversing the connector on orion makes the red led on all the time and creates the correct behaviour that it triggers on push down. But that then put's the value on 880+ in the duet and it almost doesn't change when tapped.

So what am i doing wrong and what needs to be reversed somewhere to get the correct 0 - 600+ value when triggered in dueton push down of the nozzle, not on release?

these are my Zprobe settings in config.g

; Z-Probe
M558 P1 H5 F120 T12000 ; Set Z probe type to unmodulated and the dive height + speeds
G31 P500 X0 Y0 Z0 ; Set Z probe trigger value, offset and trigger height
M557 R125 S20 ; Define mesh grid

Thanks for your help.

Bart

HI Simon,

I just ordered your Orion module yesterday , with the intention to use it with a duet Wifi on a Kossel Metal delta printer.

Nice to find your thread here. looking forward to reading it and combining it with the DUet.

Bart