@alankilian G32 runs bed.g and then makes corrections to the axis programed in bed.g
It is not the same as mesh comp as far as I understand it.
@alankilian G32 runs bed.g and then makes corrections to the axis programed in bed.g
It is not the same as mesh comp as far as I understand it.
I have 8 machines all running on Duet2Wifi's with Panel Dues and identical settings. Two of them were plagued by this issues for the past year.
I was rebuilding one of them last week and decided to dig in an figure out what the issue was. I didnt think it was my router because all of them have reserved ip address. After hours of screwing with YAT and confirming that all the connections on the board were good, I cleared all the IP reservations and did a software update on my router. (EERO Mesh)
I was shocked to find that after the router firmware update, the issue was totally resolved on both the machines that had the issue. Not sure if it was the actual router firmware update, or the fact that I cleared the ip reservations and did new ones for each machine. Eitherway....the problem is gone.
When using G32, Does G32 need to be added to the staring scripts on the slicer or does the Duet2Wifi save the compensation until its manually run again?
@shanian79 I figured it out. The M7/M9 commands are not supported. However when Duet gets these commands, it looks for a .sys macro of that name and executes it if there is one.
For example, I added and M7 and M9 macro to my sys folder.
When Duet gets an M7 command, it executes the M7 macro with M42 that turns on the solenoid wired to out1. M9 turns it off.
M7 file in .sys folder
M42 P0 S0 ; turn the valve off
@fcwilt Its a CNC command that turns Cooling on and off. It's not listed in the REPRAP Dictionary, however from what I have found, it is a valid command. Its just specific to CNC and doesn't have a purpose with FFF, so its not listed.
@dc42 How do I setup my config.g to allow the F360 M7 commands to control the solenoid I have on out1? I can't find any documentation for how to allocate M7 to a specific i/o pin.
I have a 24v solenoid wired to out1 on a Duet3 6HC. I currently have it set to turn on/off in the start.g and stop.g.
I would like to get rid of this and have it controlled by the Fusion360 post processor nc file with the M7 command.
How do I set this up in my config.g file. I can't find any information on how to allocate that I/O pin to the M7 command. I assume its a M950 line, but I don't know what the correct labels/names are for M7 allocations.
Thanks!
@dc42 disregard....I figured it out
@dc42 Thanks! How exactly would I do that? Is there a link to a thread that explains how to do this?
@dc42 Thanks! My main question is how to set the solenoid outputs in the config to turn on when a job starts and shut off when its complete. I don't think I can modify the G-code created by Fusion360 to have starting and ending scripts like with FDM slicer software. I'm using the F360 Workbee post processor.
I ordered some 12v solenoids to control on/off for my air and cooling fluid sprayers on my CNC. What is the best way to set them up to open when a job starts and close when the job is finished?
I'm running the latest CNC version of 3.3 on a Duet 3 Board. Using Fusion 360 Cam with Workbee post processor .nc
DuetWifi with latest stable release.
Has been working fine, then between jobs the Z-probe is showing as triggered (1000), regardless of probe position. Using a BL Touch V3.
Replaced the BL Touch unit with a new one-did not solve.
I tried using other heater pins for servo wire, with updated config - did not solve
Re-installed firmware and DWC - did not solve
DWC shows probe triggered after reboot even when probe is unplugged.
Any suggestions appreciated. Config settings are below.
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Fri Feb 21 2020 09:47:23 GMT-0600 (Central Standard Time)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Ender A" ; set printer name
M575 P1 S1 B57600
; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet
; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S0 ; physical drive 1 goes backwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E415.00 ; set steps per mm
M566 X1200.00 Y1200.00 Z24.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z180.00 E6000.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z100.00 E5000.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I50 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X235 Y235 Z260 S0 ; set axis maxima
; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z
; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"zprobe.in+zprobe.mod" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-30 Y0 Z1.65 ; set Z probe trigger value, offset and trigger height
M557 X40:215 Y40:195 S20 ; define mesh grid
; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M308 S1 P"e0temp" Y"thermistor" T500000 B4723 C1.19622e-7 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M143 H1 S350 ; set temperature limit for heater 1 to 300C
M307 H1 R2.583 C137.6 D4.53 S1.00 V24.1 ; disable bang-bang mode for heater and set PWM limit
; Fans
M950 F0 C"fan0" Q10 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q10 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H-1 ; set fan 1 value. Thermostatic control is turned off
M950 F2 C"fan2" Q10 ; create fan 2 on pin fan2 and set its frequency
M106 P2 S1 H-1 ; set fan 2 value. Thermostatic control is turned off
; Tools
M563 P0 D0 H1 F-1 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
; Custom settings are not defined
; Miscellaneous
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
M501
M591 D0 P5 C"e0_stop" R5:300 E3.0 S1 ; Duet3D laser sensor for extruder drive 0, connected to endstop input 3 (E0), tolerance 40 to 140%, 3mm comparison length, disabled
Just following up on this. I've been running my CNC on a Duet3 board for a couple months now and loving it! Thanks to all who put the time and effort into this project!
https://drive.google.com/file/d/1IoRxP0r1AkXaKeTeyZBixeCDPX-JHSoq/view?usp=sharing
Looking for some insight and help with this. It's driving me mad! Photos, config and M122 listed below.
I have 6 identical machines all running the exact same hardware, config and Duet2Wifi boards on 3.2.2. RR3 and DWC
One of them keeps jumping on the Y axis at the same height for any model/print file. I have gone through and eliminated all physical possibilities, replaced the belt and stepper just incase there was something that was not visible, wiped the Duet and re-loaded all firmware.
I don't believe its a slicer (Simplify3D) issue as the same model file prints normally on the other machines.
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N85S4-7J1FG-3SJ6P-KB9ZR
Used output buffers: 3 of 24 (24 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73944 of which 132 recycled
Never used RAM 14544, free system stack 99 words
Tasks: NETWORK(ready,182) HEAT(blocked,150) MAIN(running,418) IDLE(ready,20)
Owned mutexes:
=== Platform ===
Last reset 26:55:40 ago, cause: software
Last software reset at 2021-03-08 09:18, reason: User, GCodes spinning, available RAM 14544, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
MCU temperature: min 15.3, current 23.5, max 25.4
Supply voltage: min 21.9, current 22.4, max 22.8, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 0, standstill, SG min/max 0/280
Driver 1: position 800, standstill, SG min/max 0/296
Driver 2: position 5498, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max 0/1023
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-03-09 12:14:29
Cache data hit count 4294967295
Slowest loop: 251.86ms; fastest: 0.09ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 4.7ms, write time 144.4ms, max retries 0
=== Move ===
DMs created 83, maxWait 10720108ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 82007, completed moves 82007, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.2
Heater 1 is on, I-accum = 0.6
=== 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 253.46ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
CONFIG
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Fri Feb 21 2020 09:47:23 GMT-0600 (Central Standard Time)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Ender C2" ; set printer name
M575 P1 S1 B57600
; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet
; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S0 ; physical drive 1 goes backwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E415.00 ; set steps per mm
M566 X1200.00 Y1200.00 Z24.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z180.00 E6000.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z100.00 E5000.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E1000 I50 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
; Set idle timeout
; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X235 Y235 Z260 S0 ; set axis maxima
; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z
; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"zprobe.in+zprobe.mod" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X10 Y5 Z1.1
; set Z probe trigger value, offset and trigger height
M557 X20:210 Y20:210 S20 ; define mesh grid
; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M308 S1 P"e0temp" Y"thermistor" T500000 B4723 C1.19622e-7 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M143 H1 S300 ; set temperature limit for heater 1 to 300C
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
; Fans
M950 F0 C"fan0" Q10 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q10 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H-1 ; set fan 1 value. Thermostatic control is turned off
M950 F2 C"fan2" Q10 ; create fan 2 on pin fan2 and set its frequency
M106 P2 S1 H-1 ; set fan 2 value. Thermostatic control is turned off
; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y-10 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
; Custom settings are not defined
; Miscellaneous
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
M591 P1 C"xstop" S1
M501
M591 D0 P5 C"e0_stop" R1:300 E3.0 S1 ; Duet3D laser sensor for extruder drive 0, connected to endstop input 3 (E0), tolerance 40 to 140%, 3mm comparison length, disabled
This is great! Thank you! Will this CNC screen format work on a 7i Panel Due?
Disregard. I figured it out. I was testing the Workbee CNC DWC on this machine yesterday before I installed it on the actual CNC machine. It installed RepRap2 on the board. When I put RR3 back on it the issue went away.