Posts made by iZippy82

@deckingman

Yeah, I sure will.

thank you again, the "noise" was driving me mad.

@deckingman

I've just tested with Q10.

The noise is almost gone and the LED is now "flashing" now.

Thanks

@Veti

Which is why it's running on the mks mosfet, that can handle 30 amps

@Veti

the reason is in the first post. (I agree it's not the best writing, I'm blaming that on lack of coffee.)
"it makes noise. electrical noise that I can see matches the leds intensity from the duet 2 wifi board."
"Is there a reason why the board would make this noise?"

There is short video linked as well.

@deckingman

My m950
M950 H0 C"bedheat" T0
it's set to PID and I've run auto m303 h0 s60 and saved it with m500.

The config.overide has values stored in it.

I've not set the frequency. I'm guessing that's running at default value, i'll try to see if I can find the recommended freq for the mks mosfet is.

Thanks I'll try it.

Hi,

It's just a regular mk2a 300x300 with a pei sheet.

Hi,

I'm mainly asking for two reasons.
Current setup I'm running a 480 watt heatbed, 24volt. Using a mks 30a mosfet.

Everything "works", heats up, keeps temps within a 1-2 c during prints. But the reason I'm considering using e1 to control the mosfet is.

First question. Whenever the board is running (motors, hotend and heatbed) and pwm is controlling the mosfet. it makes noise. electrical noise that I can see matches the leds intensity from the duet 2 wifi board. and it's not coming from the mosfet. Can't really explain. I could try to record it. As the mosfet is handling the roughly 20 amps, I figure I could try to use the e1 instead of the heatbed and shouldn't really be that much power needed from the e1 connection.

Is there any reason I couldn't/shouldn't do this, or even use a heater connector from the expansion.

Second question. which should properly have been the first one. Is there a reason why the board would make this noise?

Note: I'm running a 24v 33amp psu.
Board: Duet 2 WiFi (2WiFi) V.1.03
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.1.1 (2020-05-19b2)
Duet WiFi Server Version: 1.23

Edit: Link to video Can be hard to hear, not easy to record it.

Br
Alan

Thanks for the reply dc42, it is a Corexy.

Seems power off and back on again did it, for some reason it was only moving to Y30 before, not Y15
But it's doing it correct now for some reason.

Thanks

Hi,

So happy that i bought my duet wifi, thanks dc42 for the introduction at 3dmeetup.

My questions is that i'm using a induction sensor which is working great. just changed the design of my hotend and the sensor is now moved about 68 mm on the Y axis.

My idea is that i want the sensor to probe the entire 300x300 heatbed. which was working fine when the sensor was closer to the hotend. What i've done to make sure it probes the first 68 mm on the Y axis is that I've change the print area

To this
M208 X0 Y-68 Z0 S1 ; Set axis minima
M208 X332 Y313 Z300 S0 ; Set axis maxima

Z probe
G31 P500 X0 Y68 Z0.5

Mesh
M557 X15:300 Y15:298 S40

This seems to work, but it doesn't probe all the way at the Y15 when running a G29

Any tips? or is there a smarter way of doing this?

Best regards
Alan