Posts made by imonsei

Anyone care to look this over for glaring errors?
It does spit out a valid grid for me, and expands toward start of x and/or y if you go beyond bed edge max

;--- Start adaptive mesh probing
; this defines a minimum size of 60x60 mm grid for probing if your print is too small, with 20 mm between probes. if you have placed your print items too near the print bed end, we move probe area, so we don't probe outside the print bed.
{if first_layer_print_size[0] > 60 and first_layer_print_size[1] > 60
}M557 X{first_layer_print_min[0]}:{first_layer_print_max[0]} Y{first_layer_print_min[1]}:{first_layer_print_max[1]} S20 
{else
}M557 X{
  if first_layer_print_min[0]+60 < print_bed_max[0]}{
    first_layer_print_min[0]}:{first_layer_print_min[0]+60}{
  else}{
    first_layer_print_max[0]-60}:{first_layer_print_max[0]}{
  endif} Y{
  if first_layer_print_min[1]+60 < print_bed_max[1]}{
    first_layer_print_min[1]}:{first_layer_print_min[1]+60}{
  else}{
    first_layer_print_max[1]-60}:{first_layer_print_max[1]}{
  endif}{
endif} 
G29 S0
;--- Stop adaptive mesh probing

@imonsei I just thougt of a potential error: if you don't define a probe grid big enough, the printer will be unhappy about this.
I modified my script, so it always takes at least a 60x60 millimeter grid, for a 3x3 probe grid.
I have made checks, if you place your items too far to the end of the build plate, and the probe would go outside the end.
This is posted as a reply because the code here is kind of unreadable unless you take time to break it down.
When my brain is cooperating with me again, I would like to expand the probe area toward Xmin and Ymin if we are close to the max edge of the buildplate. That will have to be another day.

;--- Start adaptive mesh probing
; this defines a minimum zise of 60x60 mm grid for probing if your print is too small. if you have placed your print items too near the print bed end, we restrict probe area, so we don't probe outside the print bed.
;TODO: check if we go outside of print bed and expand toward xmin and ymin in stead
M557 X{first_layer_print_min[0]}:{min(max(first_layer_print_max[0], first_layer_print_min[0]+60),print_bed_max[0])} Y{first_layer_print_min[1]}:{min(max(first_layer_print_max[1],first_layer_print_min[1]+60),print_bed_max[1])};define probe area with 20mm between each probe spot
G29 S0 ;start probe, save and activate height map
;--- Stop adaptive mesh probing

@imonsei I forgot to say that when i delay heating the nozzle, it is not suitable for printers that use the nozzle for probing the bed. In this case definitely heat the nozzle before doing probing, so the heat expansion of the metal in the nozzle has had time to happen, and the little plastic at the end of the nozzle doesn't give false Z readings.

EDIT: Silly me forgot that arrays are zero indexed, so before we probed a square that was turned 90 degrees to what it should have been.

Hihi.
I made this little snippet to have your printer only probe the bed in the areas where you have your prints.
I have only tested it on SuperSlicer, but the command fully complies with PrusaSlicer documentation.
You insert this script in your "printer settings" section, in the "start g-code" box.
It should go after you have heated the bed, and after G28, and G32.
This replaces your normal G29 command.

;--- Start adaptive mesh probing
M557 X{first_layer_print_min[0]}:{first_layer_print_max[0]} Y{first_layer_print_min[1]}:{first_layer_print_max[1]} S20  ;define probe area with 20mm between each probe spot
G29 S0 ;start probe, save and activate height map
;--- Stop adaptive mesh probing

I made this for my V-core3.1.
Here is my full start g-code, in case you need it, or have suggestions for improvements.

M115 U3.1.0 ;tell printer latest fw version
M83  ; extruder relative mode

; Heat bed before probing so heat expansion of bed is mostly accounted for
M140 S[first_layer_bed_temperature] ; set bed temp
M190 S[first_layer_bed_temperature] ; wait for bed temp

G28                         ; home all
G32                         ; make sure build plate is level. 3 point probe.

;G29 S1                      ;load mesh (disabled because of adaptive mesh probing)
;--- Start adaptive mesh probing
M557 X{first_layer_print_min[0]}:{first_layer_print_max[0]} Y{first_layer_print_min[1]}:{first_layer_print_max[1]} S20  ;define probe area with 20mm between each probe spot
G29 S0 ;start probe, save and activate height map
;--- Stop adaptive mesh probing

; Heating nozzle after probe so we avoid oozing
M104 S[first_layer_temperature] ; set extruder temp
M109 S[first_layer_temperature] ; wait for extruder temp

;---start adaptive purge line
G92 E0.0 ; reset extruder
G1 X{first_layer_print_min[0]-10} Y{first_layer_print_min[1]} Z0.8 F6000.0 ; position 10mm left from the lower left of the first layer
G1 X{first_layer_print_min[0]-10} Y{first_layer_print_min[1]+30} E6 F360.0 ; extrude some filament in the y direction
G92 E0.0 ; reset extruder
G1 X{first_layer_print_min[0]-30} Y{first_layer_print_min[1]+15} E6 F360.0 ; extrude some filament in both the x and y direction
G92 E0.0 ; reset extruder
G1 X{first_layer_print_min[0]-10} Y{first_layer_print_min[1]} E6 F360.0 ; extrude some filament returning back to the start
G92 E0.0 ; reset extruder
;---end adaptive purge line

@deckingman thank you for your explanation much appreciated.

@deckingman That's a bit odd, because in the web interface it shows controls for both, and if i change the one fan slider, it changes the other slider a second later.
Same thing when the gcode changes the fan speed, the web interface's 2 sliders both change.
It also "sounds like" it's changing both, but I could be mishearing it, and I cannot verify visually.
On the web interface on PC is two buttons that switches between the fan you want to change speeds for. Clicking back and forth shows no difference in value. On mobile web interface you can see two sliders, and they both change. Just to make sure I'm describing it properly.
You are correct that it says "tool fan" and "Layer fan".

(I have the newest stable firmware and web control)

I have a duet3 6hc on a v-core printer.

My fans are configured like this:

M950 F0 C"out7" Q500                   ; create fan 0 on pin out3 and set its frequency
M106 P0 C"Hotend Fan" S0 H1 T45 L255   ; set fan 0 name and value. Thermostatic control turned on for Hotend
M950 F1 C"out4" Q500                   ; create fan 1 on pin out4 and set its frequency
M106 P1 C"Layer Fan" S0 H-1		       ; set fan 1 name and value. Thermostatic control is turned off

I have noticed that my slicer's gcode doesn't specify which fan to change speeds on, so both the fans are changing speeds. Is this working as intended?
I would have thought that when you ask the slicer to do more or less cooling on bridges, for instance, it is the layer fan you would like to have fan speed change on?
Is there a way to achieve this?
Also I thought the L255 parameter made the fan for the hotend run at max speed when turned on, so I'm clearly misunderstanding something.

Thanks for your time.

@droftarts
You were correct. I took the motor out of the orbiter and tested. It turned happily when no extruder was attached.
Opened up the planetary gears and did an inspection. Everything looked well lubed and turned easily.
Put it together again, and now it spun as it is supposed to.
Thank you

About the 1.2A - no, it doesn't get hot. It's in the documentation for the unit, so I hope they know what they are doing.

Hi guys.
I got myself a headscratcher I can't really figure out.

My problem is that when I try to extrude, I can extrude about 4mm, and then the motor starts buzzing, and stops extruding/turning. If I then try and retract, I can retract about 4mm and then then the buzzing starts again.

I have this setup
Board: Duet 3 MB6HC (MB6HC)
Firmware: RepRapFirmware for Duet 3 MB6HC 3.4.4 (2022-10-20)

The documentation for the Orbiter 2.0 states the following Gcodes needs to be set for Reprap firmware.
I put them last in the config.g file so I'm sure they will be set, in case I accidentally set something above that could overwrite.
The config.g file is also attached in case there is something relevant.config.g
M350 E16 I1
M92 E690
M203 E7200
M566 E300
M201 E10000
M906 E1200 I10
M572 D0 S0.02
M207 S1.5 F7200 Z0.2

I have heated the nozzle to 200 and have pla on the spool. I can push some through by hand, when pushing in the lever.

The Orbiter 2.0 didn't come with a connector that was correct for the board, so I had to crimp one myself. I'm fairly certain the order of the wires is correct, because it does move the filament forward when i tell it to extrude, and backwards when I retract (until buzz-stop)

Anybody have an idea, or know what I should read up on?

@stephen6309 That worked a treat. Thank you both for your help you are real human beans.

@stephen6309 oh. I was nervous about the partition I couldn't read containing important files. Performing the reformat as we are speaking.

@gloomyandy I am using the duet 3 board with a sd card plugged directly into the board. there is no raspberry pi machine connected to it.
Sorry if I haven't been clear on that.

@stephen6309 Dang it. I hoped it wouldn't be a big overhaul. Thanks for taking time out of your day to help me.

@stephen6309 Uh. I'm getting a "connection refused" error. when i SSH to the IP of the duet board.
is that a setting i have to enable in a file on the SD-card?

@stephen6309 I shall give it a try. thanks in advance.

Hi
I purchased a ratrig vcore3 with the duet 3 board a while ago.
It came with a nice 16gb SDcard, but it's only formattted to use little of that space, which leaves under 200MB for gcodes.
Now I have received a job requiring a gcode file over 300MB
Is there a way for me to make a new partition of the unused space, and have the Duet mount it to use as the gcodes folder?
It corrently has the "boot" partition, and then an unreadable partition (from the viewpoint of reading the SDcard on windows10), and about .. 15 gigs of unused space.
Or is there a smarter way about doing this?

My firmware is - Firmware: RepRapFirmware for Duet 3 MB6HC 3.3 (2021-06-15)
I have only been using the web interface to access the printer so far.

@droftarts they have a section in their assembly instructions specifically for the 6HC that said to use io2.
I figure they just copied over the mini instructions without actually testing it beforehand.

@phaedrux IT'S ALIIIIIIIIIIIIVE!!!!! Thank you so much.
I'll write a note to the ratrig people.
Their documentation and config files specify that we should use the io2 port.

I am so excited now. Weeeeeeee ^____^

I'm noticing that it doesn't say anything about a z-probe or an endstop in any of the info commands.
Should I be worrying about this, or is that normal?

@pcr said in BLtouch probe pin does not deploy:

M122

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TJ-6J9DJ-3SD6R-1996T
Used output buffers: 1 of 40 (11 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 91940 of which 112 recycled
Never used RAM 111236, free system stack 208 words
Tasks: NETWORK(ready,30.1%,212) ETHERNET(notifyWait,0.1%,117) HEAT(notifyWait,0.0%,331) Move(notifyWait,0.0%,302) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,343) TMC(notifyWait,7.4%,93) MAIN(running,61.6%,924) IDLE(ready,0.8%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:13 ago, cause: power up
Last software reset at 2021-11-19 12:36, reason: User, GCodes spinning, available RAM 111236, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 126
MCU temperature: min 17.1, current 24.8, max 24.8
Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, reads 6291, writes 15 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 6291, writes 15 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 6291, writes 15 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 6292, writes 15 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 6292, writes 15 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 6292, writes 15 timeouts 0, SG min/max 0/0
Date/time: 2021-11-19 13:44:44
Slowest loop: 9.18ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 3.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 117, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 49), ts 66/0/0
Tx timeouts 0,0,65,0,0,50 last cancelled message type 30 dest 127

=== Network ===
Slowest loop: 16.31ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0