Topics created by Nxt-1

@chrishamm I can't really provide any more info I am afaid. Even before I posted the original thread, I already fixed the issue with a mixture of --reconfigures and reinstalls. I mainly posted to raise awareness in case more people encountered the issue.

@nxt-1 Right, that's a dependency of DWC and it's used by the temp+layer charts and the IS+CL plugins. I'll check if I can upgrade that one as part of DWC 3.5.

Hi @phaedrux , I missed your reply. No not mechanical as I did several prints before and many more since, without as much as a hint of a layershift. At the same time I was not able to reproduce the underrun values while printing that file. The layershift did occur again with that file but I have a part now that is 'good enough' so haven't bothered with it to be completely honest.

@chrishamm Again, my appologies. I need my printer at the moment and am not using beta firmware. I will consider a release candidate once a find the time to read up on all the changes.

@nxt-1 said in Large input cap for Duet 3 6HC:

I still am kind of concerned about the inrush current so I figured a NTC in series should be effective as a current limiter.

It could just possibly limit charge current, if that lasted long enough to heat it up - but once the voltage stabilises, the current to / from that cap will be minimal and it will revert to high resistance.

You could just use a low value resistor to limit the current to under the PSU maximum; it should be reasonably effecting overall.

Or run a 24V relay via a series resistor from the big cap, and get it set up so it only pulls in at near 30V, then connects a far lower value resistor across a mid value soft start resistor.

And don't forget that if the PSU is permanently connected to the Duet, its output smoothing caps are added to the Duet onboard caps, so need allowing for in any motor current dumping calculations.

An old Meanwell 10A 24V I have kicking about has 4000uF on its output.

Also, the PSU is only 4A, the motor current must be lower still, so the energy returned on shutdown should only be a fraction of that in DC42's calculations, as those were for 24A motor load; 6 x 4A motors.

@dc42 I can run the command from console without issue wheter the extra 0 is there or not (I'd expect it to not be an issue as I understand it just refers to the mainboard explicitly instead of the default asume). Loading config.g from console also gives no issue.

Should it be helpful, I get a correct tacho signal reported by DWC.

@nxt-1 Thanks, I can reproduce that. I'll fix it in the software version.

@dc42 Damn, that was not the "the boards are ready to ship tomorrow" answer I hoped for 🙂 For real though thanks for the insights, I appreciate Duet3D being open about this.

G29 with no S parameter now runs file sys/mesh.g if it exists; otherwise it behaves like G29 S0 as before

At its most basic mesh.g would need to contain G29 S0 to initiate a mesh compensation probing routine. As long as the probe and mesh grid configuration are already in config.g. Beyond that you can get as fancy as you want. Preheat, homing, special probe configuration, speed settings, etc.

; Macro to run a mesh bed compensation routine (G29) ; M291 P"Grid bed compensation map will be cleared and re-calculated. Ok or Cancel?" R"WARNING. This will take about 30 minutes." S3 ; User must click OK or cancel. ; Preheat to probing temps M291 P"Preheating to bed to 60 and nozzle to 210 for accurate probing" R"Proceed?" S3 T0 ; Activate first tool M190 S65 ; Set bed to 65 and wait ;M109 S210 ; Set nozzle to 210 and wait. Used only for stall detection probing. ; Clear current mesh compensation map and disable compensation. G28 ; Home all M561 ; Disable any current bed compensation ; Set lower speeds for Z homing and lower Z motor current M98 P"ZSpeedsSlow.g" M98 P"CurrentsHoming.g" ; Drop motor current to prevent damage in case of head crash M98 P"0:/macros/musical tunes/GetAttention.g" ; Tone to get user attention M291 P"Running mesh grid compensation probing cycle. Do not disturb the printer." M558 H1.5 ; lower dive height G29 S0 ; Run mesh compensation M98 P"0:/macros/musical tunes/GetAttention.g" ; Tone to get user attention M558 H3 ; return dive height ; Turn off heaters M140 S0 ; Set bed to 0 and release M104 S0 ; turn off hot end heater M98 P"ZSpeedsNormal.g" M98 P"CurrentsNormal.g" M291 P"Homing" G28 ; Home all M84 ; turn off the motors M291 P"Check heightmap for results." R"Probing complete!" S3

@nxt-1 thats for confirming that. I will look ot see if the incorrect error message is reported in the latest version of the forum software when we upgrade to that.

@nxt-1 My question is this, is the blue LED off, solid on, or blinking during the times your Duet board is not pingable? That would at least tell if the board is connected to the access point or wifi router or hub.

@nxt-1 said in Upgrading Duet 3 6HC - voltages:

I am thinking about going from a WiFi to a Mainboard 6HC in the near future and I am looking to understand how I can/need to pass different voltages around.

Here a my voltage/power requirements as they stand now:

32V - 50W:
As I understand I can use a 32V psu on the POWER IN terminals. I only need this voltage to drive the steppers, yet I am not sure for what all the power in voltage is used around the board.

Use 32V VIN. This will be supplied to the stepper drivers, the OUT0..OUT3 ports, and any of the OUT4..OUT9 ports whose jumpers are set to VIN.

24V - 150W:
I need 24V to drive some contactors, my existing ssr, a berd-air and a high power extruder heater. Not clue how to get this connected the Duet.

Your SSR control terminals are probably OK with anything from 3 to 32V. Check the details for your particular model.

For the extruder heater, you may be able to get a custom 32V one, or use a 36V higher powered one on 32V. See e.g. http://leader-heater.com/42-.html. Otherwise, connect the heater between your +24V supply and the OUTn_NEG pin on the OUT connector. Same for the Berd Air and the contactors.

12V - 270W:
Mainly for fans and a water pump, maybe some led lighting. The other 200W is for peltier elements and does not need to be controlled by the Duet. Not clue how to get this connected the Duet.

Duet 3 provides a 12V output, but the current is limited to 0.8A. So OK for most types of fan used in 3D printers, but not for LED lighting or water pump. You can feed 12V from a higher current supply to the centre pin of one of the OUT voltage selection jumper blocks, with the jumper removed.

5V - 30W:
Used for the Duet itself and Jetson Nano I will be using as sbc.

The Duet generates its own 5V supply, alternatively you can provide external 5V power through the 3-pin connector provided.

When you create a new post there should be a bar chart icon in the post creation window between the full screen button and the emoji button. See if you can edit your first post and add it.

@engikeneer You are right that could be a good opportunity. I'd have to check clearance really well but if people are interested it can be done 🙂

In that case, I suspect an interference suppression capacitor is causing the slow rise times, or possibly just the capacitance of the motor windings. When the mosfet turns off, the motor inductance, resistance and capacitance from a LCR resonant circuit that start to ring; but the diode clamps the oscillation it when it reaches 24V.

The basic issue you are having is that lightly-loaded DC motors respond more to the peak voltage they are supplied with than to the average voltage.

If you never want to drive the pump as maximum RPM then the simplest fix may be a power resistor in series with the pump; or you could power the pump positive terminal from 12V from a buck regulator instead of 24V. If you do need the full range then I suggest an LC filter between the Duet and the pump, with the flyback diode connected to the input (Duet end) of the filter. However, you will need to use quite a large inductor. Even at 65kHz PWM frequency you will need at least 1mH with a suitably-high rated current.

@dc42 That would make sense.

@dc42 I didn't know this feature was considered for debugging only. I guess the drivers are using some indirect type of measurement and not some plain resistance measurement.

I guess making it configurable and documenting it well to informing that it might trigger false positives, especially at low currents.

@Nxt-1 said in Battling sources of vibration and noise:

And if you have time to spare you could try out all things possible with the trinamic chips in software?

I havent really tried anything here, AFAIK you can only tune some parameters aiding in standstill noise with the drivers on a Duet 2. (which isn't an issue here) Correct me if I am wrong

The Duet 2 uses TMC2660 drivers, that don't have stealthChop, which would be the big thing to try.
Unless you set something different they should have defaulted to spreadCycle, which makes them much quieter than something like an Allegro or TI driver...
Although you might get different results changing that parameter, fixed off-time tends to be nasty (it can give some really unpleasant resonant noise), but its worth testing the 0-2 values for D.

M569 :
https://duet3d.dozuki.com/Wiki/Gcode#Section_M569_Set_motor_driver_direction_enable_polarity_and_step_pulse_timing

I once got someone to try replacing resistors on an Allegro step-stick... you don't want to hear a printer with drivers that run at 16kHz.
People were upset from about 50 feet away.

I've got a nice (and relatively cheap) BLDC servo, I still need to test it and see what sort of noise it makes...

@Phaedrux Is that the Duet4?