Posts made by Johncoffee

I think I got my answer from the SeeMeCNC forum:

http://forum.seemecnc.com/viewtopic.php?f=77&t=12819&p=110440#p110440

Thanks a lot David.

With best regards
Stephan

Dear David,
Thanks a lot for your suggestions. I will investigate as you have suggested.

I just realise that my ink to 713.maker didn't work in my former post.
Here it is again:

https://713maker.com/rostock/duet-smart-effector-adaptor

I'll post my findings later here again.

Best regards
Stephan

I plan to install a Duet smart effector to my Rostock Max V2 that was previously upgraded from the Rambo 1.3 to a Duet wifi board.

http://forum.seemecnc.com/viewtopic.php?f=77&t=12819&p=110437#p110437

Now a user suggested me to use the Duet smart effector plate instead of the BL touch.

In order to do so, I need

• a Aluminum adapter for the Duet smart effector from https://713maker.com/rostock/duet-smart-effector-adaptor

• The Duet smart effector itself from Duet3D

Do I need more? I'm not sure about the ball cups / arms. I'd like to use the original ones as shown at 713maker.com's adapter plate webpage.

Or is there more I need to install this?

Thanks for a short advice - hope there is some here

@dc42
This answers my question. Thanks a lot for your detailed explanations!

I'm wondering why my trigger height reading from the web UI console window is sometimes different from the Z height at the web UI head position reading (top left in DW screen)

Any explanation?
What reading is now correct?
I've repeated the shown example twice - both time the same readings.
See below:

0_1563050411703_rmv2 2019-07-13 22-35-11.png

Thanks a lot - will check this.

Quick question:
When I set baby stepping e.g. -0.06mm, this isn't indicating in the Z position at the head position Why not?
I would expect that my current position : 0.8mm as layer no.4 of my print would change to 0.74mm?

I have updated by Delta Rostock Max V2 with a Duet Wifi 1.04 and the 7inch screen.
Additionally I printed a new effector plate which is equipped with a BL touch sensor.
I follow all instruction from the Duet Wifi pages how to calibrate the sensor, the bed, the rod length and all other parameters.

So far so good - all works fine and my prints are good.

Still I get the feeling that I'm really not sure when to do what regarding bed level measurements.

G29 is bed mesh leveling - this is understood.

What I don't get is: whats the difference between the G30 commands in my bed.g file and the G32 commands? I've read https://duet3d.dozuki.com/Wiki/Gcode#Section_G30_Single_Z_Probe and so forth
several time, but somehow still it doesn't click with me.
For example :

• Why do I need still need auto calibration when I have the bed mesh level measurement?
• When do I run G32 ? What is different to all the G32 commands in bed.g ?
• When looking at this video: https://www.youtube.com/watch?v=BgkJVgFnPaE&t=1542s the author 'Design Prototyp Test' explains thoroughly the Duet and probing the bed. But still I'm not sure when to change between these commands.
• During calibration I had to enter the 6 parameters like rod length etc. into the config.g file. Are these values now being temporary overwritten with a G32 or G30 command

Can someone describe this in simple words?

Thanks - Every answer is highly appreciated

1_1563006967656_IMG_6328.jpg
0_1563006967655_IMG_6329.jpg

@ozzzzzzy Got it. Thanks for your explanation

@Ozzzzzzy
Can you explain again the purpose of your task? I don't really understand what you are trying to achieve.

Thanks a lot.

Interestingly - as of today, all of a sudden, deleting of Gcode files also works with Safari. I don't know why, but the confirmation window pop-up like alright. Like it does on Firefox. I haven't even closed and reopen Safari - it just works.

For me the issue is closed herewith.

@dc42

I've upgraded to FW2.03 and Duet Web Control to 1.22.6.
Result: same problem.

But then I decided to try to use Firefox 67.04 instead Safari 11.1.2 on Mac Os High Sierra. And tadaaaaa - This seems to solve the problem.

With Safari I don't get the dialog window to reconfirm the delete action. With Firefox this pops up for confirmation.

Thanks for your help.

Thank you both for your reply.
I'm currently not in front of the printer

Believe that it is v1.20.
The problem exists for any file.
I will later try to upload a short screen recording clip.

I can't delete the code files in the "G-Code Files" directory via the web interface. Uploading / Overwriting / Printing works wonderful, but selecting delete doesn't seem to work. I also don't get any error message.

Any guess what I'm doing wrong?

Thanks @veti & @dc42 for your reply. Highly appreciated to get such a quick answer.

• Individual tower moves G1 S2 moves --> OK
• Endstop status M119 --> OK.
• Increased homing distance from 405mm to 500mm. --> that was it !!!

(I initially thought 405mm would be more than enough, since my homed height is ~360mm. That was my fault)

Thank you both for helping me.

Best
Stephan

Hi,
I'm all new to the Duet Wifi and in the process to get everything working with my Rostock Max V2.

What puzzles me is the error "G0/G1 insufficient axis homed" when issuing a G28 command. It happens usually only, then the 3 delta arms are in a different height (e.g. when the print head is on some outer area the bed).

When sending G28, the first tower (e.g. Z) gets homed, then the second (e.g. Y) and finally the third (X) moves towards the upper endstop. But before third tower reaches the endstop, the "G0/G1 insufficient axis homed" is issued and the X tower motor stops.
A second G28 command homes without issues.

What can be done to overcome this?

Thanks !