Posts made by taconite

@fcwilt are you sure you habe filament diameter 1,75 Set in the settings? Default for cura is 2.85

@paulhew As I said it was already working. I guess the update try did something to the image. I don't have the in-depth knowledge to know how and which files to delete to free up space

@paulhew
I changed the default password and can login with the new password via SSH. The past weeks I was able to login with the new password aswell. I tried rapsberry but I get an error promt

Hey guys,

I have a Raspberry Pi for an 7" touchscreen. It runs the duet image and I tried upgrading it but if failed because of to less storage (the image is running on an 8 GB card).

But everything was working fine.

As of today I can't login to the pi (the desktop is not running) and I can connect via VNC but can't login

I can connect via SSH and the df command showed:

why is the root folder 100% full? what can I do to fix that?

@bberger
@dc42
is there an explanation why Klipper is performing better than RRF? Has it something to do with the processing power? or is the algorithm implemented differently

I see something similar as RRF is not able to get completely rid of ringing

I have the same problem - from 3.4 I have the behaviour that even during filament loading I get an filament error so the loading is canceled

I talked to Tony on Formnext and he told me that support for Duet2 will be ongoing for years. Now you are thinking about a feature freeze. To be honest I don't think it's a good idea because then I guess more and more people are not going to use Duet2 anymore but prefer to run Klipper when the firmware for Duet2 gets more and more outdated. I can't say if the Duet3 boards are a viable replacement (e.g. I am running Duet2 and Duex5).

I prefer the option to remove the support for exotic kinematics from 3.4 onwards (so they could still run 3.4).

To make a real decision I guess it would be important to know what you would like to do the RRF in the future. Which features do you want to implement which are a USP for RRF

Hey guys,

Is there a way to assign an filament run-out sensor to a specific tool. Reason is that I get filament run-out error even if the tool is not used in the current print.

Thanks guys

But then I guess the documentation is wrong

@alankilian
You are totally right - there are no such things as obvious - I am sorry that I did not provide all the information you need.

@dc42
So In my head the Duet GPIO Inputs looks something like this

I don't mind if its inverted, the problem is that I already have a PCB with the functionality. Problem is that I am not that deep into circuit design. I don't get why it was working before ( did I plan the TCMT4100 wrong)?

EDIT:
Oh no I see my error ...

Thank you all for your replies @TomW @alankilian @zapta

I have been using the GPIOs already several times like this (not on this Duex 5 but on others and on Duet2s aswell)

the only difference is that I am not using a 4N35 anymore but TCMT4100

@dc42 So that means that I can't trigger them with 5V even if the pull up resistor is not enabled with ^

EDIT: Which would make no sense because I've done this before.

Hey guys,

I declared the pin GPIO2 on GPIO Header of the duet as Input but it is all the time at +5V. Same goes for GPIO1

M950 J1 C"duex.gp1"
M950 J3 C"duex.gp2"
M950 P4 C"duex.gp3"

In the rest of the config.g there is no other J* that could conflict with the definition.

no it gets really strange. I decreased the size of the probing radius (calibration and mesh compensation) and with the "original" values I get this L414 R236

Calibrated 6 factors using 7 points, (mean, deviation) before (-0.000, 0.006) after (0.000, 0.005)

M665 L414.000:414.000:414.000 R238.041 H465.172 B150.0 X0.146 Y0.015 Z0.000
M666 X-0.003 Y-0.210 Z0.214 A0.00 B0.00

@dc42 thank you for your reply

Z-Probe: inductive sensor, M18, similar to what I was using on other printers
Joints: They are Ball-joints, Igus, KCRM-05 they have a little play which I compensated with springs

EDIT: the nozzle is replaced by the sensor so it sits at X0 Y0

@t3p3tony
Isn't that super tedious? In which intervals should I change the rod length? It should not be off by mm

I use this page to view the mesh because I am getting the maximum deviation
http://lokspace.eu/3d-printer-auto-bed-leveling-mesh-visualizer/

But 7 Factor was not working as well and I tried to manipulate it manually and it did not improve.

@t3p3tony
Tried 7 iterations with just 7 points

M665 L414.000:414.000:414.000 R235.772 H464.295 B150.0 X0.033 Y-0.455 Z0.000
M666 X0.028 Y-0.064 Z0.037 A0.00 B0.00

deviation is a lot higher than with more points
Calibrated 6 factors using 7 points, (mean, deviation) before (-0.006, 0.235) after (-0.000, 0.235)

before that it was more in this direction
Calibrated 6 factors using 17 points, (mean, deviation) before (0.000, 0.088) after (0.000, 0.088)

@t3p3tony

yeah but what if the measured trigger height result in bad parameters from the beginning?

@t3p3tony

so yeah nothing helped

1. deleted the trigger heights from bed
2. ran 13 cycles with 6-factor on 17 points
3. ran 7 cycles with 7-factor on 17 points

Still the same result as the delta radius is adjusted

Any other ideas?