The dozuki.com server is down. A message on that site says they are working on it.

@nhof said in Noise from motors:

When you say 'recalibrated aluminum frame' what do you mean?

If you changed the way parts are connected or tightened them, the frame could be resonating differently than before which could cause more audible noise.

You're fully right ! It was a resonating issue. I disassembled and assembled again all parts of the 3D printer, and the silence is back 🙂

Thank you.

M280 P3 S160 I1 should clear the alarm and raise the pin. (substitute P3 for whatever servo channel you're using, an remove the I1 if you're using a Duex)

Raising the BLTouch above the bed enough after homing should be enough to keep it out of the way at the next power up, no?

If the bed heater turns on as soon as you power it up, that could indicate that there is a short between the bed heater element and ground.

If you give us some more information maybe we can work out what's going wrong and solve the root of the issue?

Ya, definitely better tablets out there now. But the only thing I do on it is manually control the printer if I'm sitting in front of it.. 🙂
Never will buy another RCA again though because they have taken efforts to prevent root.

........ and with no power to hold the motors, it's all too easy to accidentally move a gantry out of position. In fact, simply walking past a cheap kit printer stood on wonky desk can be enough☺

@core3d-tech said in Moving the gantry damage the stepper drivers when powered off?:

what about when the power is on and you move the gantry too fast. Can this still cause issues? Does it matter whether power is on or off?

It's possible in theory to damage the drivers by moving the gantry too fast, although you would normally have to move it very fast to cause damage. The Motor EMF calculator at reprapfirmware.org will tell you just how fast - look for the speed at which the EMF due to rotation exceeds 27V. Damage is probably more likely with power on, especially if it's 24V power.

@vlad, yes it's essentially an architecture limitation i.e. lack of a large RAM buffer, and to a lesser extent the use of SPI to transfer the data from the WiFi module. I have just tested the SD card write speed on the Duet WiFi on my bench using M122 P104, and I get speeds of about 1.6Mbytes/sec all the way up to 200Mbyte files. This is with a Kingston Memory 8Gb Class 4 card. I don't think we will do much better that that using the current 8kb write buffer. The problem is, once the card sees the end of the 8kb block write, it may start to do internal wear levelling operations, and those take time.

I am also minded to add another M105 subfunction that tests the speed of uploading a file but discards the data instead of writing it to file. This would help users who are getting slower than expected uploads to determine whether the SD card or the WiFi network is the bottleneck.

We recognise that users want faster upload speeds, and we have addressed that in Duet 3. However, by better overlapping transfers from the WiFi or Ethernet module with transfers to the SD card, I am hopeful that in as future Duet 2 firmware release we can achieve more than 1Mbyte/sec consistently, assuming a good WiFi connection.

https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation

Thanks for confirming this. I'm sorry that you received a faulty Duet.

it sounds to me that you are trying to use the auto leadscrew adjustment, but you haven't connected the two Z motors to different drivers. So it is giving you instructions for manual bed levelling instead. When it says "0.38 turn up", "up" refers to the bed. So it means you need to turn the screw to raise the bed or lower the gantry on that side. The figure "0.38" will only be accurate if in your M671 command you told it the lead of the leadscrew in the P parameter.

The limits are applied after tool offsets have been applied. In most situations, I think this makes sense. For example, on a print head with 2 nozzles, it it the head that is limited in the possible X and Y movement, not the individual nozzles. But I can see that for an IDEX machine there is a case to be made for applying the Z limit before applying the tool offset.

One workaround would be to choose your Z origin such that all tool Z offsets are zero or negative. But this wouldn't prevent you from crashing a tool with a negative Z offset into the bed.

My guess is that your slicer start GCode doesn't select a tool. As this is a common problem (because many slicers assume that a tool is already selected), RRF selects a tool automatically if you issue a M109 command with no tool selected. But perhaps that doesn't happen when you use simulation mode. I will check. Meanwhile you could put a T0 command in your start.g file.

@phaedrux That got it. it was such a small bend that to the naked eye it was unnoticeable. I had to get the magnifying lamp out and clamp it to the table to really look at it and it had a small bend. I appreciate it and thank you for your help. I was getting ready to just turn off the z stop and print like that tonight.

In theory yes, but you would need to connect the TMC2130 drivers to the SPI bus so that you can program the stall threshold, add support for the TMC2130 in the firmware, and add support for mixing different smart driver types in firmware. So not easy.

@sputnikoc3d said in Tutorial - running Duet Wifi 2 in Access Point Mode ?:

Pronterface ok here for this YAT is just not my cup of tea - at all.

Bear in mind that Pronterface forces all the characters you send to upper case, which is awkward for entering passwords in particular. That's why we suggest YAT for this purpose.

Hi Andre
Thanks for your help, makes sense.
Jeremy