Topics created by Mentaluproar

@Falcounet yep I got /dev/spidev0.0 /dev/spidev0.1 to show up an got them merged into the current kernel passed in the bufsiz on the grub line options to the kernel cuz the modprobe.d method doesn't work. Just would not talk. Error 19. Maybe I'll get curious in few days and go for another round with it.

@mentaluproar If I read correctly, lockdown is a form of a firewall and privacy tool.
So one could compare it against eset - which is what I have and I have exactly the same issues as you do. I have to disable web protection in my eset to be able to use the DWC. This came on with a DWC change a while back.

You can add command to start FAN in files homeall.g, homex.g, homey.g and homez.g
Printer will be silent before running G28 command.

@mentaluproar the input and output are separate MCU pins. You can use a single port as described at https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Duet_Num_3.

@jens55 I rolled back to the stock board and will just be using Klipper for it instead while I take a closer look at this board. I cant turn the parts fan on and off so I think there's a dead mosfet on here too. I measured with the stock board and it was 0.2 volts higher than the duet. I tuned the voltage up just a touch to hit 24 even even with the bed head on. shouldn't matter but meh.

My soldering skills are potato-class so I might not be able to repair this board.

@phaedrux It's at 12v....because the LEDs are 12v, but the rest of the system is 24v! Of course!

I'll try fixing this tomorrow but I seem to remember there was some reason I had it wired up this way.

EDIT: I remember, I blew some of the mosfets on the duet over the years so the duet fan headers don't work right, hence I used the deus. I really should fix this things properly someday

Well that solves it. When and where did you purchase the smart effector?

@Mentaluproar said in Turn light on or off via URL:

Is there a page that explains this somewhere?

i just had a look in the web browser console which command is send from the web ui

@Veti said in Piezo probe not seen SKR 1.4 RRF3:

this thread should be moved to the lpc category

Moved.

On the 3Dprinters Discord, someone has tuned stacked Y splitters well enough that he can do 6 colors (white, 5 colors) in XY and 11 colors in Z(white, 5 colors, and 5 pastel colors by printing a white layer under a thin layer of the five colors).

As much as I like tool changers, you can get a lot of mileage out of the Y splitter approach if you build it well enough.

sample print

The inversion didn’t work but simply switching S0 to S1 did. Thanks. Now for the bltouch....

https://youtu.be/kmfgr1k050U

I think the prusa MMU was having similar issues with tip diameter, maybe look into how they were dealing with it.

Well, it's still messed up. Heater fault on an overnight print. It seems to only happen during long prints.

The thermistor is integrated into the plate and is covered in a sticky foam. I might be able to pry and shove a regular thermistor on a wire under all that. It shouldn't be hot enough to damage the wire, right?

Which guide? It's already part of the M106 fan wiki entry.

The best way to maximize the mesh grid is to take your M208 as the bed surface, then add/subtract your probe offsets. That will give you the area for M577 that the probe can reach. Adjust it slightly so that you can get a whole number of points within it. Tip, if you send an M577 with a unreasonably high number of probing points it will suggest the actual maximum to you.

Now if your print head can move the nozzle outside of the printable area so that you can reach the probe further you could temporarily increase your axis limits with a larger M208 command, probe the bed with G29, and then return the limits back to only the printable area with M208 again.

Also under the heading of 'interesting' is that I have the same issue. The only thing different for me is that when I tried to measure the header voltage I managed to short the lines out with the probes and the magic smoke left the driver 😞
For obvious reason I have abandoned (until the FET is replaced) to measure fan voltage.

FOUND THE PROBLEM!

Either my zprobe connector is shot on the duet, or it was pissed I was probing on the duet when the PWM signal was on the duex2. Moving it over to duex.gp1 fixed it. I did have to enter this manually though, as reprapconfigurator does not currently let you assign a gpio pin as zprobe in.

@Phaedrux okay, thanks.

@Mentaluproar said in gap fill causes stepper to spasm:

M566 X1000 Y1000 Z1000 E500

Likely due to the low E jerk.