Posts made by wieman01

@dc42

I just noticed that the issues has returned. I was a little premature in hoping the issue had gone... I renamed "Pause.g" to "pause.g" but to no avail it appears.

Any other clue that would come to your mind?

@dc42 said in Question: Cannot connect via DWC while print is paused (Duet 2):

@wieman01 I'm guessing that you are running a Duet with attached SBC ?

I am running 7 Duet 2's in combination with Duex 5's on 24V. No SBC attached. May I ask why you would ask?

The setup is perfect for us, however, next year we'll get a few Duet 3's to see how we can further scale our printers.

@dc42 said in Question: Cannot connect via DWC while print is paused (Duet 2):

@wieman01 please share the contents of your pause.g file.

Thank you. These are the contents:

G91            			; relative positioning
G1 Z20 F360     		; lift Z by 10mm

When I checked the file I noticed I had filed the contents under "Pause.g" with a capital letter. I changed it to "pause.g" and ta-da... I can connect with no problems.

So sorry for having bothered you, but apparently this discussion was necessary.

Thank you both!

@Phaedrux

Yes, I can ping the Duet's ip address, I get a response. DWC also tries to connect, but the connection drops constantly.

Hello,

We face a strange issue whenever we pause one of the prints or when the printer pauses having run out of filament. As soon as we reset the machine or press "Continue" the wifi connection works fine.

We run the firmware version 3.4.5 on a Duet 2 with an external antenna.

Is that by design or am I missing something?

Hello, @ctilley79,

I generally have these issues when there is a problem with the wiring or the connectors. Manual extruding via DWC works fine, but then the motor needs higher currents, it move backwards because the wires only let through so much current.

I would check every wiring the in particular the soldering joints and connectors. This solves this particular problem for me every time.

wieman01

@JoergS5 said in Robotic kinematics:

@wieman01 hello,

this is a big robot you're planning to buy (or maybe build?). I have no experience with big robots, so I can only give you some thoughts without guarantee, but maybe on the forum are users with experience.

My thoughts are, if it shall be Duet based:

• it will use probably servos with high current, so a 6XD board is probably the right choice, with a 3HC extension card for optional more axes for endpoint functionality if necessary
• those robots use a lot of energy to operate. It depends on your requirements, but I would personally try to buy a low enery one which is slower or smaller or has less payload capability, but this depends on what you're planning to do with it. For palletizing e.g. the 5 axis robots have counterweights, they should need less energy compared to the 6 axis ones. The palletizing robots use a parallelogram structure for one axis less.

Hello, @JoergS5,

Thank you, that is a starting point.

We will be using that robot for 3D-printing. The overall payload it will have to carry won't exceed a few kilograms. So there is no heavy lifting involved.

Buying vs. building one myself... that is the question. I will need to see what is available first and then decide. It's tempting through to start designing one from scratch now that you are asking...

wieman01

Hello Joerg,

First of all, thank you for your continuing support & effort, this is really impressive work you have accomplished so far. Looking forward to the first final release (although it will probably never be final I reckon)!

I was wondering if you had any recommendations as to what robot you would take into consideration that works best with the Duet boards. I am new to this, and I don't really know where to start and particularly what I need to pay attention to.

What I am looking for is a robot arm that would allow for a "build volume" (if you can even use that terms in this regard) of approximately 1500x1000x1000mm (1500mm being the maximum height) for 3D-printing. I know there are lots of commercial options out there, but I was wondering what criteria a second-hand robot would have to meet in order work with your code and the Duet 2 (or 3). I don't want to spend 10K plus EUR before I know what I am doing.

Would be great if you could share a few ideas, but I totally understand you're a busy man.

Looking forward to hearing from you.

wieman01

@oliof

Thank you, you're amazing! I will indeed check it out, you got me curious. I will let you how it goes when I am ready.

@dc42 said in Question: G29 S4 for Duet 2 (firmware v3.5):

@wieman01 we're not planning to add this feature to Duet 2 because it's applications are fairly niche and both flash memory and RAM on Duet 2 are running out. However, if you set up to build RepRapFirmware yourself then it should be straightforward to enable the feature in the Duet 2 build. You might have to remove another feature (e.g. a kinematics that you don't need) to make space in flash memory.

That is too bad, but I understand, it is rather niche. I may in fact take a look at the RepRap source code later in the year should the need arise again to have this feature. Would you mind pointing me to the relevant section where this feature is enabled for the Duet 3?

Thank you for your response.

Hello,

I saw in the latest changelog that the G29 S4 feature was added for Duet 3. That is indeed great news, and I am excited to see this feature also for the Duet 2.

Any chance this will ever be implemented for the Duet 2? It would certainly make my life a lot easier.

wieman01

@joergs5 said in Robotic kinematics:

@wieman01 tested will be:

6 axis industrial robot
CNC 5 axis including CoreXY 5 axis
4 axis palletized robot

Documentation starting point is https://docs.duet3d.com/User_manual/Machine_configuration/Configuring_RepRapFirmware_for_a_Robot_printer and by the robot tag there are specialized documents for the specific types.

Other serial chain types are possible by configuring Denavit-Hartenberg parameters. With this concept, prismatic/linear and rotary axes can be combined in any combination, as long as they are in series. The current limit is 7 axes, but this is just a fixed variable.

Thank you, @JoergS5. So the supported hardware isn't restricted to certain manufacturers, but to the design of the robot. That makes sense. I'll look into it. And really big thanks for your contribution here!

Hello,

Is there a list of compatible robots somewhere on docs.duet.com? I searched but could not find anything...

Just curious what Duet will be capable of with the upcoming release (3.5).

wieman01

@jay_s_uk

Oh, gosh, can it be that simple?! Thank you, my friend, that worked like a charm. All good now, the G31 parameter is safely stored in "config-override.g".

wieman01

Hello,

After completing the z-calibration procedure I typically open "config.g" and manually adjust the z-offset by using G31.

config.g:

; BL Touch
M950 S0 C"duex.pwm5"												
M558 P9 C"^zprobe.in" H5 F150 T6000									
G31 P25 X0 Y-36 Z1.95									

z-calibration (part 1):

G28
M561
G1 F3000 X240 Y160 Z20	
M564 S0

z-calibration (part 2):

G92 Z0
G1 Z5
G30 S-3
M500 

I was hoping M500 would save the setting in "config-override.g", but it does not.

Is there any way I can make this a permanent setting (i.e. even after restarting the machine) once I have run the script?

Thank you.

wieman01

@boa said in Question: BL Touch Probe Offset & Mesh Bed Leveling:

@wieman01 Y range is limited only from one side. Y=0 coordinates can be reached by bltouch - it just moves nozzle to position Y=36, and then proble is at Y=0.

But.. if nozzle can go only to Y=350, then probe can reach only points with Y <= 350-36.

So M557 would have Y range Y0:314, as any higher Y is out of reach of probe tip.

Thank you, that makes sense. I'll change the settings accordingly. This could be reason why bed leveling appears to be slightly off.

Hello,

I hope this is an easy one... I am using a BL-Touch as proximity sensor and have configured a XY-Offset as it sits in front of the nozzle:

G31 P25 X0 Y-36 Z1.100

These are the axis limits:

M208 X0:480 Y0:350 Z0:260 S1

Z probe has been calibrated using the center point of my print bed (X240, Y175).

This is how I invoke mesh bed leveling:

G32
M557 X0:480 Y0:350 P5:4 		; probing points for mesh bed compensation
G29 S2					; clear height map
G29 S0 					; run mesh bed compensation procedure & save map

Now my question is how I should account for the Y-Offset (G31) of the BL-Touch (36mm). Should I increase the first Y-value by 36mm (Y36:350) or should I reduce the second value (i.e. Y0:314)?

Thank you for your help!

wieman01

@jay_s_uk

Thank you, that is good news. I'll keep an eye out and see what I can find when the first beta comes out.

Hello,

Right now I am using M557 to define the mesh size and spacing before I run a G29. It all works well so far.

In previous versions you used to be able to define specific probing points for mesh bed compensation using x- and y-coordinates. I understand that is now deprecated.

Is there any way I can still do that using a workaround of some kind?

wieman01

Also let us know what BL version you have got. Depending upon the version you may need different cabling (including a resistor, etc.). You find the version number on the back of the device.