@chrishamm Just to make sure I'm not doing anything wrong...conditional gcode is not yet in dsf 1.3.1, correct?
Posts made by mvieleers
-
RE: No output from G32 on DSF 1.2.4 / DWC 2.07
-
RE: No output from G32 on DSF 1.2.4 / DWC 2.07
@chrishamm This is indeed correctly working now in DSF 1.3.1. Great job! Thanks! As this was the original issue, I guess this topic can be closed now.
-
RE: No output from G32 on DSF 1.2.4 / DWC 2.07
@PaulHew I have the same issue. After I ran a G29, it displays correctly.
-
RE: No output from G32 on DSF 1.2.4 / DWC 2.07
@chrishamm said in No output from G32 on DSF 1.2.4 / DWC 2.07:
I hope I can get conditional G-code working in DSF next week.
Cool!
-
RE: No output from G32 on DSF 1.2.4 / DWC 2.07
@chrishamm Brilliant. Quick question, sorry to polute this topic, but were you able to implement conditional gcode in this version of dsf?
-
RE: No output from G32 on DSF 1.2.4 / DWC 2.07
@chrishamm Thanks a lot for the hard work. Installed DSF 1.3.0 and DWC 2.1.0 and RRF3.01-RC6. This issue with no output on the G32 command still persists, unfortunately.
-
RE: No output from G32 on DSF 1.2.4 / DWC 2.07
@chrishamm said in No output from G32 on DSF 1.2.4 / DWC 2.07:
Again, sorry for the inconvenience!
No worries! I (and probably most others) understand that this is not your day job. Appreciate everything you're doing.
Looking forward to try the new release, when it's available.
-
RE: No output from G32 on DSF 1.2.4 / DWC 2.07
@Danal Well that's strange behaviour. I'm losing the console output immediately, as soon as DSF 1.2.4.0 is installed.
I really am confident it is the DSF, as I am now running on standalone mode with same firmware and same DWC version without issues.Hopefully @chrishamm will get around to looking into this.
-
RE: Connection Lost Duet3/SD/RRF3.01-RC2/DWC2.0.7
@droftarts
M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_VERSION: 3.01-RC2 ELECTRONICS: Duet 3 MB6HC FIRMWARE_DATE: 2020-02-18b1
Duet Web Control 2.0.7Config.g
; Configuration file for RailcoreII 300ZL with Duet 3 (firmware version 3); *********************
; ETHERNET CONNECTION
; *********************
M552 S1 P0.0.0.0 ; Assign IP-address with DHCP; ***********
; DEBUGGING
; ***********
M111 S0 ; Debug off
M929 P"eventlog.txt" S1 ; Start logging to file eventlog.txt; *********************
; GENERAL PREFERENCES
; *********************
M550 P"Duet3" ; Machine name and Netbios name (should be the same)
;M555 P2 ; Set output to look like Marlin (in standard config)
M575 P1 B57600 S0 ; Comms parameters for PanelDue
G21 ; Work in millimeters
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves; ***********************
; STEPPER CONFIGURATION
; ***********************M569 P0 S1 D3 ; Drive 0 goes backwards| X stepper / Rear
M569 P1 S0 D3 ; Drive 1 goes forward | Y Stepper / Front
M569 P2 S1 D3 ; Drive 2 goes backwards| Extruder S1 for Bondtech
M569 P3 S1 D3 ; Drive 3 goes backwards| Front Left Z
M569 P4 S1 D3 ; Drive 4 goes backwards| Rear Left Z
M569 P5 S1 D3 ; Drive 5 goes backwards| Right ZM669 K1 ; select CoreXY mode
M584 X0 Y1 Z3:4:5 E2 ; set drive mapping; *********************
; LEADSCREW LOCATIONS
; *********************
M671 X-7:-7:345 Y21:273:150 S25 ;Front left (-7,35), Rear Left (-7,289), Right (347,164); ******************************
; AXIS AND MOTOR CONFIGURATION
; ******************************
M350 X16 Y16 Z16 E16 I1 ; Set 16x microstepping for axes & extruder, with interpolation.
;M906 X500 Y500 Z400 E700 I60 ; Motor currents (mA) - Conservative
M906 X1400 Y1400 Z1200 E800 I60 ; Set OWN motor current (mA)
;M201 X500 Y500 Z02 E500 ; Accelerations (mm/s^2) - Conservative
M201 X2500 Y2500 Z100 E1500 ; set OWN accelerations (mm/s^2)
;M203 X3000 Y3000 Z50 E1800 ; Maximum speeds (mm/min) - Conservative
M203 X24000 Y24000 Z900 E3600 ; set OWN maximum speeds (mm/min)
;M566 X200 Y200 Z5 E10 ; Maximum jerk speeds mm/minute - Conservative
;M566 X800 Y800 Z100 E1500 ; Set OWN maximum jerk speeds mm/minute
M566 X1000 Y1000 Z100 E1500
M92 X200 Y200 ; Steps/mm for X.Y
M92 Z1600 ; Steps/mm for Z - TR8*4 / 0.9 deg stepper
M92 E816.78 ; Steps/mm for Extruder | Bondtech BMG; *************************
; AXIS LIMITS AND ENDSTOP
; *************************
M208 X-9:300 Y0:306 Z-3:325 ; 300ZL settings
M574 X1 S1 P"io1.in" ; X endstop
M574 Y1 S1 P"io2.in" ; Y endstop
M950 J0 C"io3.in" ; Z (crash prevention) endstop Left Front
M950 J1 C"io4.in" ; Z (crash prevention) endstop Left Back
M950 J2 C"io5.in" ; Z (crash prevention) endstop Right
M581 P0:1:2 T0 S1 C0 ; emergency stop (T0) when any of Z endstops is triggered in all cases (C0); *********************
; BLTOUCH AND PROBING
; *********************
M558 P9 C"io7.in" H5 R1 F120 T6000 A5 S0.02 B0 ; Define BLTouch (F120, A5)
M950 S0 C"io7.out" ; create servo pin 0 for BLTouch
G31 X-1 Y38 Z5.251 P25 ; Offsets (Note: Positive number is closer to the bed)
;E.G. If probe offset is 42 on Y, then Y50:290 will take the hotend to Y08 to Y248)
M557 X45:254 Y45:261 P10:10 ; define mesh grid; *************
; THERMISTORS
; *************
M308 S0 P"temp0" Y"thermistor" A"Bed Top" T100000 B3950 ; BOM thermistor for top of the bed
M308 S1 P"temp1" Y"thermistor" A"Bed Bottom" T100000 B3950 ; BOM thermistor for bottom of the bed
M308 S2 P"temp2" Y"thermistor" A"Tool" T500000 B4723 C1.196220e-7 ; Slice engineering thermistor for tool; *********
; HEATERS
; *********
;M570 P5 T25 S360 ; Print will be terminated if a heater fault is not reset within 360 minutes
; BED HEATER
M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
M143 H0 S100 ; set temperature limit for heater 0 to 100C
M140 H0 ; Map the heater to the bed
M140 P0 S-273 R-273 ; Standby and initial Temp for bed as "off" (-273 = "off")
M307 H0 A206.9 C476.6 D14.6 S1.00 B0 ; Keenovo
; TOOL HEATER
M950 H1 C"out1" T2 ; create tool heater output on out1 and map it to sensor 2
M143 H1 S270 ; set temperature limit for heater 1 to 250C
M307 H1 A275.2 C80.8 D1.9 S1.00 V23.9 B0 ; Slice engineering Mosquito; ******
; FANS
; ******
; PART COOLING
M950 F0 C"out 8" Q500 ; Part cooling Fan
M106 P0 S0.0 H-1 C"Part Fan" ; Turn off fan
; TOOL
M950 F1 C"out 7" ; Hotend Fan
M106 P1 S1.0 H2 T40 C"Tool Fan" ; Turn on fan at 50 degrees hotend
; ELECTRONICS
M950 F2 C"!out4" Q25000 ; Electronics in/out Fans
M106 P2 S1.0 H-1 C"Electronics Fan" ; Turn on fans; ************************
; FILAMENT RUNOUT SENSOR
; ************************
M591 D0 P1 C"io6.in" S1 ; Set filament runout sensor to io6.in; ******************
; TOOL DEFINITIONS
; ******************
M563 P0 S"Mosquito" D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 S-273 R-273 ; Set tool 0 operating and standby temperatures(-273 = "off")
M572 D0 S0.1 ; Set Pressure Advance; ***************
; MISCELLANEOUS
; ***************
M501 ; load saved parameters from non-volatile memory (config-override.g)
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
T0 ; select first tool -
RE: Connection Lost Duet3/SD/RRF3.01-RC2/DWC2.0.7
@bearer MAC OS Catalina is what I'm running
-
Connection Lost Duet3/SD/RRF3.01-RC2/DWC2.0.7
Hi,
After several minutes being connect to my Duet3 via ethernet cable in DWC through http://duet3.local, the connection is lost. DWC is unable to reconnect to the Duet3. From then on I cannot connect to it anymore on http://duet3.local, untill I manually reset the Duet3The strange thing is that the ip-address is still assigned to the duet. I get a response when I ping it, I can also go to http://<ip-address> and DWC comes up.
When I am connect through the ip-address, the connection error does not occur.So the issue is only related to the url http://duet3.local
Any thoughts? -
RE: Overview of implemented Gcode RRF3 for Duet3+Pi
@Phaedrux thx! Read a lot, but never stumbled upon that page strangely enough.
-
Overview of implemented Gcode RRF3 for Duet3+Pi
Is there an overview available of all Gcodes that have been implemented in DWC for a RRF 3(.01-RC2) Duet3+Pi combination?
I've ran into a situation that M500 has not been implemented, but I also noticed that M291 is not working.
It would be helpful to understand what can and cannot be used.Thank you!
-
RE: No output from G32 on DSF 1.2.4 / DWC 2.07
@chas2706 Please note, to make this work, you cannot be on a release of Reprapfirmware that requires DSF 1.2.4.
-
RE: No output from G32 on DSF 1.2.4 / DWC 2.07
@Danal Just to be sure: this is my bed.g logs for completeness. Don't believe there's much to go on in there. (by the way, I had upgraded to 3.01-RC2 before.)
duetcontrolserver:
Feb 18 20:30:45 duet3 DuetControlServer[352]: [info] Executing nested macro file bed.g on channel HTTP
Feb 18 20:30:46 duet3 DuetControlServer[352]: [info] Executing nested macro file deployprobe.g on channel HTTP
Feb 18 20:30:53 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file deployprobe.g
Feb 18 20:30:53 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
Feb 18 20:30:54 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file retractprobe.g
Feb 18 20:30:54 duet3 DuetControlServer[352]: [info] Executing nested macro file deployprobe.g on channel HTTP
Feb 18 20:31:01 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file deployprobe.g
Feb 18 20:31:01 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
Feb 18 20:31:02 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file retractprobe.g
Feb 18 20:31:02 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
Feb 18 20:31:02 duet3 DuetControlServer[352]: [info] HTTP: Finished macro file retractprobe.g
Feb 18 20:31:04 duet3 DuetControlServer[352]: [info] Executing nested macro file deployprobe.g on channel HTTP
Feb 18 20:31:11 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file deployprobe.g
Feb 18 20:31:11 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
Feb 18 20:31:12 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file retractprobe.g
Feb 18 20:31:12 duet3 DuetControlServer[352]: [info] Executing nested macro file deployprobe.g on channel HTTP
Feb 18 20:31:19 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file deployprobe.g
Feb 18 20:31:19 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
Feb 18 20:31:20 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file retractprobe.g
Feb 18 20:31:20 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
Feb 18 20:31:20 duet3 DuetControlServer[352]: [info] HTTP: Finished macro file retractprobe.g
Feb 18 20:31:23 duet3 DuetControlServer[352]: [info] Executing nested macro file deployprobe.g on channel HTTP
Feb 18 20:31:30 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file deployprobe.g
Feb 18 20:31:30 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
Feb 18 20:31:31 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file retractprobe.g
Feb 18 20:31:31 duet3 DuetControlServer[352]: [info] Executing nested macro file deployprobe.g on channel HTTP
Feb 18 20:31:38 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file deployprobe.g
Feb 18 20:31:38 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
Feb 18 20:31:39 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file retractprobe.g
Feb 18 20:31:39 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
Feb 18 20:31:39 duet3 DuetControlServer[352]: [info] HTTP: Finished macro file retractprobe.g
Feb 18 20:31:42 duet3 DuetControlServer[352]: [info] Executing nested macro file deployprobe.g on channel HTTP
Feb 18 20:31:49 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file deployprobe.g
Feb 18 20:31:49 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
Feb 18 20:31:50 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file retractprobe.g
Feb 18 20:31:50 duet3 DuetControlServer[352]: [info] Executing nested macro file deployprobe.g on channel HTTP
Feb 18 20:31:57 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file deployprobe.g
Feb 18 20:31:57 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
Feb 18 20:31:58 duet3 DuetControlServer[352]: [info] HTTP: Finished intermediate macro file retractprobe.g
Feb 18 20:31:58 duet3 DuetControlServer[352]: [info] Executing nested macro file retractprobe.g on channel HTTP
Feb 18 20:31:58 duet3 DuetControlServer[352]: [info] HTTP: Finished macro file retractprobe.g
Feb 18 20:31:58 duet3 DuetControlServer[352]: [info] HTTP: Finished macro file bed.gduetwebserver:
Feb 18 20:30:44 duet3 DuetWebServer[463]: info: DuetWebServer.Controllers.MachineController[0]
Feb 18 20:30:44 duet3 DuetWebServer[463]: [DoCode] Executing code 'G32'
Feb 18 20:31:58 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Mvc.Infrastructure.ContentResultExecutor[1]
Feb 18 20:31:58 duet3 DuetWebServer[463]: Executing ContentResult with HTTP Response ContentType of text/plain; charset=utf-8
Feb 18 20:31:58 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[2]
Feb 18 20:31:58 duet3 DuetWebServer[463]: Executed action DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer) in 73655.5472ms
Feb 18 20:31:58 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
Feb 18 20:31:58 duet3 DuetWebServer[463]: Executed endpoint 'DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer)'
Feb 18 20:31:58 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Feb 18 20:31:58 duet3 DuetWebServer[463]: Request finished in 73656.4125ms 200 text/plain; charset=utf-8
Feb 18 20:33:05 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Feb 18 20:33:05 duet3 DuetWebServer[463]: Request starting HTTP/1.1 POST http://duet3.local/machine/code text/plain;charset=UTF-8 3
Feb 18 20:33:05 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Cors.Infrastructure.CorsService[4]
Feb 18 20:33:05 duet3 DuetWebServer[463]: CORS policy execution successful.
Feb 18 20:33:05 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
Feb 18 20:33:05 duet3 DuetWebServer[463]: Executing endpoint 'DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer)'
Feb 18 20:33:05 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[3]
Feb 18 20:33:05 duet3 DuetWebServer[463]: Route matched with {action = "DoCode", controller = "Machine"}. Executing controller action with signature System.Threading.Tasks.Task`1[Microsoft.AspNetCore.Mvc.IActionResult] DoCode() on controller DuetWebServer.Controllers.MachineController (DuetWebServer).
Feb 18 20:33:05 duet3 DuetWebServer[463]: info: DuetWebServer.Controllers.MachineController[0]
Feb 18 20:33:05 duet3 DuetWebServer[463]: [DoCode] Executing code 'G32'
Feb 18 20:34:19 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Mvc.Infrastructure.ContentResultExecutor[1]
Feb 18 20:34:19 duet3 DuetWebServer[463]: Executing ContentResult with HTTP Response ContentType of text/plain; charset=utf-8
Feb 18 20:34:19 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[2]
Feb 18 20:34:19 duet3 DuetWebServer[463]: Executed action DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer) in 73870.6134ms
Feb 18 20:34:19 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
Feb 18 20:34:19 duet3 DuetWebServer[463]: Executed endpoint 'DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer)'
Feb 18 20:34:19 duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Feb 18 20:34:19 duet3 DuetWebServer[463]: Request finished in 73872.5775ms 200 text/plain; charset=utf-8 -
RE: No output from G32 on DSF 1.2.4 / DWC 2.07
@Danal
; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Thu Jan 23 2020 14:06:49 GMT+0100 (Midden-Europese standaardtijd)M561 ; clear any existing bed transform
G1 Z5 H2 ; move nozzle up
;4-point bed levelling
G30 P0 X15 Y45 Z-99999
G30 P1 X15 Y275 Z-99999
G30 P2 X275 Y275 Z-99999
G30 P3 X275 Y45 Z-99999 S3
G1 X0 Y0 F5000 ; move the head to the corner (optional) -
RE: No output from G32 on DSF 1.2.4 / DWC 2.07
Tried to find out where it goes wrong...
Started with a fresh install of Duetpi (with GUI) from here: https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3Version info:
Board: Duet 3 MB6HC (MB6HC)
DSF Version: 1.1.0.5
Firmware: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 3.01-RC1 (2020-02-08b3)
Duet Web Control 2.0.7Restored my own config files.
POSITIVE RESULT: G32 produces output in the console.
Next steps:
sudo apt-get update
sudo apt-get upgradeVersion info:
Board: Duet 3 MB6HC (MB6HC)
DSF Version: 1.2.4.0
Firmware: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 3.01-RC1 (2020-02-08b3)
Duet Web Control 2.0.7NEGATIVE RESULT: G32 does not produce output anymore.
This confirms that the root cause lies within the DSF version (As kraeger also produced output with DSF 1.2.3.0, we can narrow it down to changes made between 1.2.3.0 and 1.2.4.0.) or with a conflicting update in any of the other 146 updates available since this version of Duetpi.
-
RE: No output from G32 on DSF 1.2.4 / DWC 2.07
I am the aforementioned user. Physically it is working, just the output to the console is missing. It is not only the G32. I also noticed a G30 S-1 does not report to console