Posts made by Royce

@dc42
I tried with 3 different cables with no luck.
In the meantime, Idris sent me a replacement Orion, I'm going to check this soon and report back

Any ideas on this issue?

Thanks for the answer!
Yes, the Orion is indeed produing a active-low trigger, as clarified with Idris.
I'm getting a value of 1000 whenever the probe / nozzle is tapped on. The connection between the Orion and the board is fine, i double checked that with 3 other spare cables.
Here's the output of M558, looks good to me:

and of G31 T8:

Best,
Paul

Hi folks,
I'm experiencing an intermittent issue with my Duet equipped Hypercube Evo.
After the last print worked fine, the Duet doesnt seem to recognize the Orion trigger signal and moved the bed into the nozzle. The LED turns blue and the Z-Probe value in DWC turns to 1000 but the bed doesnt stop.
It can be seen here:
https://www.youtube.com/watch?v=QPJLcA02j2s

Here's a pastebin of my config (which worked fine before):
https://pastebin.com/SvTHw5F2

I already talked to Idris and measured the signal voltage of the Orion which was fine.
I also went through the usual procedure with loosening the orion mount screws etc.
What also makes me wonder is that the Z value is the following after the bed is stopping (when it pressed the entire assembly up for about 5-10mm):

Any help is appreciated!

Best,
Paul

@dc42
Do I need to set M572 in the config or in the slicer's start code?

I noticed that the jumpyness started at around 55-60C and stopped when it reached the set temperature (85C)

Thank you, I'll read it up
Very much appreciated!

"Funny" thing is that is stabilizes as soon as it finished heating:

That's good to know.
So I need to dig into the PA feature a little more, I didnt use it so far.
Any point to start?

Hi there,

since yesterday, I experience a jumpy bed temp reading.
Looking at the numbers, it's jumpiung around 2-3 degrees within seconds.
The graphs looks like this when heating up (and stabilzes when finished heating):

Is my thermistor about to die?

Best,
Paul

Well, when changing perimeter lanes (from inner to mid to outer), there is no retraction. It just changes the lanes.
So I dont think the stop has something to so with the retraction.

@dc42
Good idea.
Gcode file added to the Google Drive link from above

@phaedrux
No wipe or coast is used (wipe + coast gave me worse results).
PA is disabled, Firmware version 1.21

I'm retracting 6 or 6.5mm at 60mm/s.
Dont know where these numbers come from

Update:
The short stop is also present on an object sliced with Slic3r.

Hi folks,
As I'm currently analyzing my blobbing problem, I noticed the following:
When retracting at layer change, the nozzle pushed quite a big blob at the start or the first (inner) perimeter.
Additionally, the nozzle stops for a split second when it changes to the next perimeter(s) which also results in additional blobbing.
Does anyone have a clue why this stopping occurs?
Link to S3D profile and Duet config:
https://drive.google.com/drive/folders/1Km_6ZQwyBDyLP2Ud__PldtW7bxEX-NcE?fbclid=IwAR3nCLb5PsGNBp8A_SwU41jG-jFciY0TJX-w4Bt0CYU6mMRsYJOXp-UB6xk

Thanks in advance,
Paul

@dc42
The bed doesnt get probed after the G28 in bed.g, that's the issue. After the homing, the x/y axis goes total nuts. I'll make a video when I get home

I found the culprit.
Y Endstop was set to the low end instead of high end.
Thank you all

Good evening,

I set up my config.g and bed.g according to this manual:
https://duet3d.dozuki.com/Wiki/Using_the_manual_bed_levelling_assistant

part in config.g:

; Manual Bed leveling assistant prerequisite
M671 X-4:302:302:-4 Y-4:-4:300:300 P0.5

bed.g:

M561                ; clear any bed transform
G28                 ; home all axes
; Probe the bed at 4 points
G30 P0 X15 Y15 H0 Z-99999
G30 P1 X285 Y15 H0 Z-99999
G30 P2 X285 Y285 H0 Z-99999
G30 P3 X15 Y285 H0 Z-99999 S4

It should probe front left, front right, rear right, rear left.
My origin is set to the front left.

After the homing with G28 (in the bed.g), the head doesnt probe the first point at 15/15 (that's also the z homing position) but it tries to drive the printhead against the limits (like it wants to probe outside the bed).
Therefore, the G32 command fails in the end.
Are my config set up correctly? Am I missing anything?

Additionally, this is my homeall.g, if it helps:

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool on Sun Jul 15 2018 21:09:13 GMT+0200 (Mitteleuropäische Sommerzeit)
; home X
G91                     ; relative positioning
G1 Z5 F6000 S2          ; lift Z relative to current position
G1 S1 X-305 F1800	; move quickly to X endstop and stop there (first pass)
G1 X5 F6000       	; go back a few mm
G1 S1 X-305 F360        ; move slowly to X axis endstop once more (second pass)
G1 X5 F6000       	; go back a few mm to prevent running the motor into the Y endstop mount

; home Y
G1 S1 Y305 F1800 	; move quickly to Y endstop and stop there (first pass)
G1 Y-5 F6000       	; go back a few mm
G1 S1 Y305 F360        ; move slowly to Y axis endstop once more (second pass)
G1 Y-5 F6000       	; go back a few mm

; home Z
G90                     ; absolute positioning
G1 X15 Y15 F6000        ; go to first bed probe point and home Z
G30                     ; home Z by probing the bed
G1 Z5 F100 S2          ; uncomment this line to lift the nozzle after homing

@dc42
Thanks for the reply.
I have set them as follows:

M569 P0 S0                            ; Drive 0 goes forwards
M569 P1 S0                            ; Drive 1 goes forwards
M569 P2 S1                            ; Drive 2 goes forwards
M569 P3 S0                            ; Drive 3 goes backwards

What would I have to do to achieve my goal to have 0/0 in the front left corner?

@dc42
Perfect, that answers my question.
Thank you!