Topics created by Sphyloid

@sphyloid I think you can already do what you want in a macro, like this:

Home the axis. Using one tool, use M675 to probe the centre of the cavity. Extract the position of that axis from the object model. Subtract the extracted position from where the cavity centre ought to be, and add that to the offset of that tool. Repeat steps 2 to 4 for the other axis, and again using the other tool.

@droftarts Actually, that does exactly what I am looking for. A while ago I read the entire gcode dictionary for the duet, and since I did not see any similar posts on the forums I assumed it was not added yet. This makes things easier for me!

@dc42 Thanks for the help, I just created a guide incase anyone else tries to do this: https://duet3d.dozuki.com/Guide/Panucatt+Viki+2+-+VIKI2+setup/111

@rjenkinsgb Thanks, when I read the write up on editing G30 from dc42 I thought that editing G30 would set the expected Z value at that location, but I did not realize he was talking from the perspective that XY values would change where it probed.

Thanks!

Peltier modules are bidirectional.

Can you switch the water flow between heated and cold via valves, and reverse the peltier supply polarity for heating / cooling?

It would save the mass of the second set of peltier modules and allow the one set to be distributed more evenly under the bed.

If you used a second heating channel with an appropriate PTC (rather than the normal NTC) thermistor for the cooling control, the board would read the temperature in reverse and should allow it to drive the cooling control?

The displayed temperature would be wrong, but it should allow regulation?

The purpose of that was to allow us to change the address of the DueX for trying out variants of the board.

@sphyloid Look in the duet 2 wifi schematic, it has the info in the properties. http://uk.farnell.com/taiwan-semiconductor/es1cl/diode-ultra-fast-s1a-150v/dp/1559125

@sphyloid, 0u1 typically means 0.1uf = 100nf.

@sphyloid google docs imports those CSVs ok if you want a "free" alternative that's more than a text editor.

@t3p3tony
I think you owe David a beer 😉

@zipzap Thank you!

@sphyloid
TWIDEXCBV3.PNG

The DueX uses a I2C expander chip + mosfets to drive the additional fans, and a 74HCT02 chip + mosfets to drive the additional heater heater outputs.

Well that's great news!

You could add a G4 delay after the back off move.

What Duet?
What firmware?
Post your config.g and homeall
Post the results of M122 and M98 P"config.g"

I also put the G10 offsets in another file called Toffsets so I can edit it and rerun it without having to edit config.g
I call it from within config.g as well

@Sphyloid said in IDEX H-Bot:

................. I regard my design as functional given that myself and two senior level engineers, one with a doctorates in mechanical engineering, have reviewed the design. Furthermore I have done extensive FEA on the assembly with a safety factor of 5 for a total deflection of 0.2mm on the Z, and 0.02mm on the X/Y axis.

Given that layer heights tend to be in the order of 0.2 or 0.3mm, then designing a printer which has a predicted deflection equal to that layer height is not a good thing (in my humble opinion). I'm surprised any senior engineers (with or without doctorates) would say that is acceptable.

As for speed, H-bot wins again. When you have enough stiffness, you can use huge motors. To re-iterate, H-bot is easier to engineer when you have enough stiffness. You need to take advantage of that stiffness if you do not want to lose speed.

For FDM printing, the speed is largely governed by how fast you can melt and extrude filament. So while huge motors might allow one to use high accelerations in order to attain high speed, there is little point in doing so if the hot end is incapable of supplying molten filament at the required rate. The best I've been able to do is about 300mm/sec using multiple extruders feeding into a mixing hot end.

Honestly it is quite alarming how little I know about getting this to work at a firmware level. Any tips on where I could get better guidance?

@dc42 has written the firmware so there is little to know. All you have to do is configure it. For info, I'm a 67 year old (retired) mechanical engineer with not much in the way of paper qualifications and I have been able to configure and run a CoreXYUVAB with 6 extruders. So I'm sure that someone who is a clever as you will be just fine. The Duet Wiki contains all the information you need and if you get stuck, this forum is a good resource to use.

@Phaedrux The Duet still turns on and runs fine until it skips X around. I found where the short was and all it had access to short was the X endstop and X stepper.

Ended up ordering a replacement, had to go with a cloned version since I could not find a real duet anywhere. The printer works fine now. Though I found there was no cooling for the duet, the rear of the board had little to no clearance and the board cooling fan was choked with the air flowing away from the board instead of under.

I added hotglue to the main ribbon solder joints and the rear of the connectors and removed the grounding wire that may have shorted them. Also I wired the X stepper directly to the board so that the breakout only has the 5V endstop.

Thank you for the help guys, looking forward to having my duet running on another of my machines.

X_Board_A_1024x1024.jpg