Best posts made by kuhnikuehnast

Hi there,
just wanted to show you what all is possible using a Duet Wifi

https://www.youtube.com/watch?v=TvXCyZwuqzM

1. G28 home all axis
2. G32 - auto bed compensation. There are 2 servos "popping" up to define a fixed point for the BLTouch to level the Z-Axis
3. Clean the nozzle
4. Mesh bed compensation (this is no longer shown on the video)

Everything solved using macros

(here you can see the servos popping up more detailed: https://www.youtube.com/watch?v=e0h5YHoAH68 )

I really like the Duet!

greetings kuhni

But why? The PanelDue is mounted next to the printer? So just look above and you'll see what is going on?

omg- @dc42 you've been right! After now searching for the error over and over, it was really a bad connection... So for now- everything works fine

Hi there,
As I am at odds with changing nozzles due to the process of "re-adjustment" of the tool offset I got an idea:
What about using a piezo disc that is laying on the bed to adjust the nozzle offset? The Idea would be:

1. Probe the height with the typical sensor above the piezo disc (piezo disc not in use)
2. move the nozzle over the pizeo disc and "probe"
3. the difference between 1 and 2 is the tool offset.

This could be implemented as an G-Code like "probe 5 times, take the median" and you could always adjust the offset before every print. (maybe the piezo disc could be mounted on the side or so)

I think this would be a cool idea especially if you use a tool changer with a fixed probe on the x-carriage like e3d does...?

What are your thoughts about?

greetings kuhni

Hi there,
found a funny bug:
If the name of a macro is to long, it gets cropped on the PanelDue screen. But if you click on the cropped name on the PanelDue, you get the answer that the Macro isn't found. (It tries to execute a Macro with exactly the same cropped name as on the PanelDue and not the original one).
Would be great to fix this!

greetings kuhni

Hi!
This weekend, an unfortunate mistake happend to me:
For any reason the BL-Touch clamp broke while homeing... Unfortunately this happend exact at the moment I had no eye on the printer... As I came back, the nozzle had scratched over the whole printbed and was stuck at a bed clamp.

So my question:
Is there a chance to use stall detection as emergency shutdown? So if the board detects stall detection (e.g. after a print didn't stick at the printbed and the nozzle crashed into it etc.) the stepper motors should be turned off as well as the heatbed and nozzle?

Greetings kuhni

The Piezo Disc itself is easy to get! But it is always used with a special "converter board". This is hard to get- and I don't know exactly what this baord is doing?

Hi there,
as I am planning to convert my Prusa Clone to DuetWifi I consider to buy a PanelDue. For my Hypercube Evolution I own a 7'' integrated, but this Panel would be almost the size of the whole heatbed So is there a page with all the dimensions so I could have a look and pick the size I need. (Or is there maybe a 5'' Paneldue integrated that will be released soon?)

greetings kuhni

Did some further tests now:
I flipped the belts, so all Idlers are run on the smooth side of the belt (and are changed to smooth Idlers with no teeth) except the Pulleys of the Stepper motor. Therefore I had to flip the belt. This reduced the ringing a lot. It is still there but almost gone. Here a photo of the new belt-lineup (only for one motor otherwise my painting skills would be to confusing )

I also had to loose the belt tension a lot to reduce the ringing even more. So it is still visible but you can't feel it any more...

Also performed a second test:

changed to 0.9° stepper motors to increase the steps/mm. (and also tested 16 teeth Pulleys instead of 20. So I could compare the print quality from 200 steps/mm with 80 steps/mm… But there was no difference.

Next, I will try to replace the belt by a fishing line. So there won't be any toothed pulleys in the hole system any more. (the line just wrapped around the motor shaft 5 times to ensure enough friction). I know, that this isn't a solution, but it may help to find out whether the ringing is really caused by the belts...?

It is really strange!I think I just masked the problem with this conversion, but I did not fix the cause…
Almost everybody else uses the Hypercube evolution with a regular belt line-up...?

Here a picture of the setup

So, next test finished:
The problem seems really to be due to the toothed belt... Using fishing line (the line wrapped around the motor shaft 5 times) the ringing was completely gone! (Despite by a damn poor accuracy )

Now that the culprit has been located, the question remains: Why do I have a ringing problem while others don't? And what else can I try to solve the problem?

I think I solved the problem:

• it wasn't the SD-card- but as I changed the cable and re-crimped an USB-3-cable everything now seems to work!

yihaaa