Topics created by Reine

@Reine The reprapfirmware package only holds firmware binaries for Duet boards. If you are using a third-party board, the upgrade prompt (where you see All boards are up-to-date!) does not show up. That means you will have to install firmware updates manually in SBC mode (also the reason why the Install Updates button is visible in Settings -> General then).

@Reine Oops, you're quite right. M106 S255 (which is probably what the slicer is producing in the Gcode) doesn't work, but M106 P0 S255 does. I thought M106 without a P parameter defaults P to zero. But I think it must default to the tool fan, which makes sense in a multi-tool setup, because then you're changing the fan speed of the current tool. But if no fan is associated with the tool, it doesn't fall back to F0. I've always just had no fan specified in M563, so it DOES default that to F0. I put F-1 in yesterday, but didn't run a print to realise it wouldn't be controlled by slicer Gcode.

I think you may just have to live with the slight annoyance of seeing 'Tool fan'. Sorry!

Ian

@Arminas theres no limitation regarding duex as its basically part of the mainboard

I suggest you retune your heater as a tool so that it can take the cooling fan into account.

M303 T0 S220 for example

https://docs.duet3d.com/User_manual/Reference/Gcodes#m303-run-heater-tuning

@Reine the frequencies of Z vibrations are quite high, so they may well be caused by something other than ringing e.g. a fan.

@droftarts I noticed this issue after upgrading to a CPAP remote fan setup, which when installing I rerouted some wires and like you mentioned the cable to the display ran close to the can wire and also two steppers, but just for a few cm.

As the issue was only happening when printing I took your advice and re-routed the display wire away from both can and stepper wires and guess what, no more connection issues 🙂

0DF90DB8-F0E7-4696-933C-4EC3AD1C2429_1_105_c.jpeg

Sorry for the delayed replay guys, as previously mentioned this was also discussed and mostly resolved in the RRF channel on the unofficial RatRig Discord.

@Herve_Smith I'm using this flex plate, and as mentioned it's fastened with adhesive. https://ratrig.com/3d-printers/accessories/heaters-surfaces/flexplate-set-pei-410-x-410-mm.html

@deckingman I could very well have meant MBC, tbh that's a term I haven't heard before you mentioned it. I referred to ABL as I thought that was the entire system that scanned, mapped and compensated for the bed topography.

My setup is as follows:
RatRig VCore 3.1 400

Duet 6HC / 1LC VzBot CNC Toolhead VzBot Hextrudort VzBot Goliath My own adaptor to make it work https://www.printables.com/model/507786-duet-1lc-mount-for-vzbots-ratrig-printhead 0.5mm nozzle RatRig "SuperPinda" sensor CPAP fan

I was running v3.4.5 when this was reported and are now running v3.4.6.

Here are my main config files:
config.g
bed.g
config-override.g

@chrishamm nice, yes I am running 3.4.5. Any ETA on those releases?

Alright @jay_s_uk, gonna try a quick fix with M581 and segmentation. Hit me up if you need a hand testing stuff later, happy to help! Cheers!

@Reine said in Identify thermistor?:

So if these sensors read 10K ohms at 25c, it would seam like my sensor is functional then?

If it's a 10K thermistor (which would not be unusual for a bed or chamber thermistor) then it is probably functional.

Perhaps there was a problem with the wiring between the thermistor and the controller?

@Reine you can query individual keys see:

https://github.com/Duet3D/RepRapFirmware/wiki/HTTP-requests#get-rr_model

@Reine you could try state.job.filePosition/state.job.file.size.

You can always use the "Seconds since time started" as your timestamp in your filename. Putting a "+" in front of state.time gives you this number.

G29 S3 P{"heightmap-"^+state.time^".csv"}

This will keep your files in order.
Then you can append the human readable timestring into the heightmap file so you'll have it.

@Reine SET_GCODE_OFFSET is no legit G-code so I suggest you remove that in any case. I am not aware of any G-code that could output "PA 0" so I guess it is something in your slicer or config settings.

@Reine Just found them on fermio.de, but IMHO they are quite expensive.
IIRC I got 5 meters of NeoPixel RGB LEds for roughly the same price.
Not 24V, but 5V supply, so what?

@engikeneer ahh that makes perfect sense, it's 0 now and at layer 25 so the superpinda isn't sensing the bed any more. Thanks

@Reine this video is about the klipper input shaper graphs, but ignoring the different scales I think it explains it relatively well... https://youtu.be/M-yc_XM8sP4

@Reine see here https://github.com/Duet3D/DuetSoftwareFramework/blob/master/src/DuetPiManagementPlugin/README.md

@Reine said in Hooked up a 4028 fan but can't control it?:

@droftarts I have gotten it to work, turned out the initial wiring I had was correct, but I had to lower the Q value for it to work. I'm now at Q10600 which gives me around 2500 rpm minimum.

I suggest trying an external pullup on the PWM line. It won't resolve the running at minimum PWM issue (as noted by others - that might be how it is designed), it might improve the response when it is running.

I've seen a couple of fans recently that don't seem to have adequate pullup on their own. See https://forum.duet3d.com/post/306593 for my posting about one example. That was a reasonably reputable fan bought from digikey. (Full disclosure: I've also got some questionable fans from aliexpress that an external pullup didn't help.)

Note that I found that both too weak a pullup and too strong a pullup worked less well than the value I eventually settled on (4k).

@Reine the result is the outcome of the last command.