Posts made by natewalck

Hey all!

I am working on a PrintNC build and happen to have a spare Duet3 that I intend to use for the PrintNC.

It uses a VFD Spindle, which I intend to use a PWM to 0-10V board to adapt for Duet3 use (Something like this: https://www.amazon.com/DAOKI-Voltage-Converter-Interface-Switching/dp/B081W4NTML .Thanks to folks in PrintNC discord for this tip).

As for powering the steppers, I assume the thing to do is 32V input for the 5160s, correct?

Does anyone have suggestions on a solid 32V PSU that would be able to power some beefy Nema23s?

So to summarize, the list of needed hardware as I understand it:

• Duet 3
• PWM to 0-10V Board for VFD control
• Nema 23s for each axis
• Spindle (In my case, a 2.2Kw VFD spindle)
• 32V Power Supply
• Endstops

Is there anything else that would be useful on the hardware end in relation to running a CNC using a Duet 3?

I think having a known good hardware setup for each CNC size/class may be nice, then people can jump right in and riff on it as desired.

Here is the correct data:

config.g: https://github.com/natewalck/railcoreiiduet/blob/master/300ZL/sys/config.g
homeall.g: https://github.com/natewalck/railcoreiiduet/blob/master/300ZL/sys/homeall.g
homex.g: https://github.com/natewalck/railcoreiiduet/blob/master/300ZL/sys/homex.g
homey.g: https://github.com/natewalck/railcoreiiduet/blob/master/300ZL/sys/homey.g
homez.g: https://github.com/natewalck/railcoreiiduet/blob/master/300ZL/sys/homez.g

Doing the same exact process as in post # 18 (with the bed showing 0.1 too low):

And here is the M122 output after each command:

After G28:

0_1561083216074_M122_after_G28.txt

After G32 run 1:

0_1561083226991_M122_after_G32x1.txt

After G32 run 2:

0_1561083235889_M122_after_G32x2.txt

After G28 Z:

0_1561083244610_M122_after_G28_Z.txt

After G29 command (As shown above):

0_1561083256472_M122_after_G29.txt

As you can see, the bed still appears ~ 0.1mm too low using the above sequence.

Also, I don't see "comp offset" anywhere in the M122 outputs. It shows no bed compensation being used at all.

Thanks!

Nate

Note: This does test did NOT use a G28 Z after the second G32 but before the G29, so it is not exactly the same as the post just before this one.

Doing the same thing, but with a M122 after EACH command yielded this:

Also here is the M122 output after each command.

M122 After G28
0_1561079030629_M122_after_G28.txt

M122 After G32 First run
0_1561079035542_M122_after_G32x1.txt

M122 After G32 Second Run
0_1561079039717_M122_after_G32x2.txt

M122 After G29 (same commands as previous post)
0_1561079095120_M122_after_G29.txt

G28
G32
G32
G28 Z

Then for mesh:

G91
G1 Z5
M557 X40:290 Y42:332 S250
G29

Yielded this:

Yep! In the post above I included all relevant files including homez.g.

After doing the G32s I did do another home Z before the bed mesh, which is why this is extra confusing for me.

Also worth nothing, upon starting up the machine from powered off, I do the following sequence:

• Home All (X/Y/Z as above)
• G32

The first G32 always adjusts the bed ~ 0.1mm as found here: https://www.dropbox.com/s/sxivxywouhscamj/Screenshot 2019-06-15 13.45.33.png?dl=0

Hey All, I was curious if anyone else has seen this before. I am running a RailCore 300ZL and discovered some odd behavior when using Mesh after having used ZL. The entire bed looks around 0.1mm low on the bed mesh, but if I G30 near the first probe point for the ZL, it fixes it.

My bed.g for ZL:

M561 ; clear any existing bed transform
G30 P0 X40 Y42 Z-99999 ; define 4 points in a clockwise direction around the bed, starting near (0,0)
G30 P1 X290 Y42 Z-99999
G30 P2 X290 Y292 Z-99999
G30 P3 X40 Y292 Z-99999 S3
G1 X0 Y0 F5000

And now here is the procedure where I see this occur:

• Home All
  HomeX.g:
  ; home X - Sensorless

M400 ; make sure everything has stopped before we make changes
M913 X30 Y30 ; reduce motor current to 30% to prevent belts slipping
M201 X900 Y900 ; reduce acceleration on X/Y to stop false triggers
M915 P0:1 S3 R0 F0 ; both motors because corexy; Sensitivity 4, don’t take action, don’t filter

G91 ; use relative positioning
G1 S1 X-270 F4000 ; move to home position
G1 X25 F2000 ; back off to edge of bed

G90 ; back to absolute positioning
M400
M913 X100 Y100 ; motor currents back to normal
M201 X3000 Y3000 ; accel back to original

HomeY.g:

; home Y - Sensorless

M400 ; make sure everything has stopped before we make changes
M913 X30 Y30 ; reduce motor current to 50% to prevent belts slipping
M201 X900 Y900 ; reduce acceleration on X/Y to stop false triggers
M915 P0:1 S3 R0 F0 ; both motors because corexy; Sensitivity 4, don’t take action, don’t filter

G91 ; use relative positioning
G1 S1 Y-270 F4000 ; move to home position
G1 Y25 F2000 ; back off to edge of bed

G90 ; back to absolute positioning
M400
M913 X100 Y100 ; motor currents back to normal
M201 X3000 Y3000 ; accel back to original

HomeZ.g:

;File : homez.g
;Effect : does a 2-stage Z-homing. Once quickly to bring the bed up from a long distance quickly, then again slower for better accuracy.
;Use-case : the machine may be Z-homed from any position at a reasonable pace, without resorting to dangerous options such as M564 H0 - while still retaining accuracy of the final probe.

G91 G1 Z5 F800 S2 ; lift z so we don't crash
G90 G1 X150 Y150 F6000 ; Move to the center of the bed

; M558 Fxxx sets the probing speed.
; Probe rapidly to get us in the right ballpark.
; This brings the bed up quickly but may be less accurate.
M558 F500
G30

; Probe again slowly for precision
M558 F50
G30

• G32

• G32

• G32

• Home Z (See above)

• Probe 4 points - Mesh:
  G91
  G1 Z5
  M557 X40:290 Y42:332 S250
  G29

This gives me the following mesh: https://www.dropbox.com/s/2mvz5nutzgz3knd/Screenshot 2019-06-15 14.22.59.png?dl=0

Then, if I do the following:

• Move to first ZL point and Home Z
  G0 X40 Y42
  G30

• Probe 4 again (Same as above)

I get this mesh: https://www.dropbox.com/s/4cmuv0og34z365e/Screenshot 2019-06-15 14.25.42.png?dl=0

I'm not sure why the first mesh shows ~ 0.1mm low on all corners.

Thanks,

Nate

@chrishamm Thank you so much for getting the source code up on Github! I believe @cheeseandham has started a config for RailCore (Found here: https://railcore.org/doku.php?id=en:300zlconfigcreator).

We've been talking about how we could handle the various different configurations on the RailCore IRC channel. We would love to have config "blocks" so to speak, so it is easier to specify all the options in one JSON blob for the RailCore.

For instance, you'd have one config block(dictionary, hash, whatever) for Titan and one for Bondtech BMG. You'd also have a block of config for each Z probe type (Piezo, IR, BLTouch, etc). Then people could select their probe in q drop down and get all relevant config options for that item/part.

Hey all!

I was curious if the source code for the RRF Configurator Tool was on github.

Also, how does one contribute a preset for the tool? We'd love to add a preset for RailCore II.

Thanks,

Nate

Cool, makes sense. So even though the sensor itself is only 2 wires, running 4 back to the daughterboard makes it more accurate than using 2 wires and the jumper.

I have the newest revision daughterboard.

Hey all!

On the E3D PT100 sensor it has 2 wires. Is it best to run those 2 wires into the daughterboard on 2 and 3, then bridge 1/2 and 2/3 as per documentation?

I’ve also heard of using 4 wite extensions from the sensor back to the daughterboard. In this case, you can plug the 2 wires from one lead into blocks 1/2 and 2 wires from the other lead into blocks 3/4.

Which setup is most preferable?

Thanks!

Nate

I talked to Mosaic support and they confirmed it works with a Duet:

“Yes, it will work with a Duet, and you have the option of connecting Palette 2 to the printer via USB using the CANVAS Hub, or you can simplify load the files to your printer's SD card, similar to how it's done with a Palette+.”

Hey all!

I'm seeing a very interesting behavior with my mini IR probe on Duet 1.21.

If I run Home X, Home Y and then Home Z, the Z home stops ~ 5-6mm too tall (above trigger height) and the red light flashes 4 times.

If however, I call home Z again, it will home properly. If I call home Z again, it homes properly again.

If I then home X and Y, then call Home Z, it once more will home 5-6mm too high (4 red light blinks). Again, if I do a home Z, it works as expected (1 red light blink).

Here is a video of this behavior: https://www.dropbox.com/s/81h5kmzat10xeul/2018-04-14 15.00.05.mov?dl=0

config.g: https://github.com/natewalck/railcoreiiduet/blob/master/sys/config.g
homex.g: https://github.com/natewalck/railcoreiiduet/blob/master/sys/homex.g
homey.g: https://github.com/natewalck/railcoreiiduet/blob/master/sys/homey.g
homez.g: https://github.com/natewalck/railcoreiiduet/blob/master/sys/homez.g
homeall.g: https://github.com/natewalck/railcoreiiduet/blob/master/sys/homeall.g

I am pretty baffled and have no idea why this is occuring. I was using a 1.3 Mini IR probe and saw this behavior, so I swapped it out for a 1.1 Mini IR Probe and it behaved in exactly the same fashion. Also of note, the 1.3 probe was working fine on 1.21 for a few days. I had finished a print on Thursday night (I shut it off post-print) and when I went to home on Friday morning, it had the above behavior. I did not change anything between stopping after the Thursday night print and homing on Friday morning. Also, it does flash 4 times upon started (as expected).

Thanks in advance.

Nate

When using Z motor bed leveling with 3 lead screws (as described https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors: ), is there any advantage to probing more points than in front of the lead screws?

For instance, would there be a benefit to probing the 4 corners rather than in front of the 3 lead screws or would this reduce accuracy? Since the leadscrew location is recorded in M671 command, I was curious if that meant we could probe the 4 corners for front/back leveling.

Thanks!

@dc42:

The directions don't say you need to measure the trigger height at all the points you want to probe, they suggest you measure it at various places to check that it is consistent. Mesh bed compensation assumes the same trigger height at all probe points, so it won't give accurate results if the trigger height varies a !ot.

Ok, I'm still confused then. If I have G31 set and the Z probe height homed as per the directions, why is the G29 not responding to the probe firing off? Am I missing some other setting/config?

Thanks!

@dc42:

The difference is that a plain G30 starts probing from wherever it already is; whereas G29 moves the head to one dive height above the bed and starts probing from there. So before you can run G29, you need to home the printer, and homing must establish the Z=0 position to within an accuracy of one dive height.

I assume using G31 to set Z offset is not the same as homing the printer?

In the directions here: https://duet3d.com/wiki/Using_mesh_bed_compensation

It shows to do steps 4-10 at all the places you want to probe. I don't see that measured Z height being specified anywhere prior to running the M557/G29. Does the machine remember all the Z heights for the points you probe in that process?

If that is the case, I should make a macro that handles this for me to make the process more hands off.

I'll try this manually and report back, but I want to make sure I fully understand what is going on during that homing process (and how that information is used by G29).

Alright, I confirmed that bed.g is working as expected with 4 point leveling. For some reason, the probe doesn't activate using G29, not entirely sure why. Let me know if there is anything else I should try out.

[[gcode]]
; bed.g
; called to perform automatic bed compensation via G32
;

;T99    ;Non-existant tool, no offset.
; Clear any bed transform
M561

; Home all axes
G28

;Goto Center. Unlike other points, this should include compensation for probe X/Y coordinates.
G0 Z35
G0 X143 Y63.5
G30

G0 Z35
M98 P/macros/cd_topRight
G30 P0 Z-10000

G0 Z35
M98 P/macros/ce_bottomRight
G30 P1 Z-10000

G0 Z35
M98 P/macros/cf_bottomLeft
G30 P2 Z-10000

G0 Z35
M98 P/macros/cc_topLeft
;G30 P3 S0 Z-10000  ;Calibrate with same number of factors as points probed.
;G30 P3 S4 Z-10000  ;Four factor calibration.
G30 P3 S4 Z-10000  ;Three factor calibration.
;G30 P3 S-1 Z-10000 ;Simply report coordinates.

;Pause for UI.
G4 P1500

;Return to safe position.
G0 Z35
M98 P/macros/cb_center

@dc42:

@natewalck:

The only issue now is the probe activating isn't stopping the head from dropping.

Under what conditions? You've told us that when you send G30, the probe does stop the head dropping when it triggers.

Gotcha. When running the G29 command, the probe does not stop the head movement. When running a G30, it does.

To summarize:

• Boot Duet

• Home all axes

• Run G30

Probe stops head. Doing the same thing, but with the M557 + G29, it does not stop.