No output from G32 on DSF 1.2.4 / DWC 2.07

dc42

Have you tried RRF 3.01RC1 ?

kraegar

Just tried it, no change.

Danal

Duet Web Control 2.0.7
Board: Duet 3 MB6HC (MB6HC)
DSF Version: 1.2.4.0
Firmware: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 3.0 (2020-01-03b3)

Console in DWC:

2/15/2020, 9:43:31 AM	G32
Leadscrew adjustments made: 0.143 0.051 0.107, points used 3, deviation before 0.105 after 0.000

kraegar

@Danal Man, I'm stumped.

I had this reported by a user. I was running DWC 2.0.5 and DSF 1.2.3, and was getting output just fine. So we started troubleshooting. When I updated DSF to 1.2.4 (which upgraded DWC to 2.0.7) I "lost" the output on the console. Doesn't matter how I run it - I can hit the button in DWC, run G32 manually, or even run M98 P"bed.g" - I get no output for the adjustments made.

Duet Web Control 2.0.7
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)

Danal

Yeah, that is kind of odd. I am on 3.0 at the moment due to doing some apt-get stuff; I have been on various releases past that, including a couple of Dave's dropbox links, and I don't recall losing this.

I take it the machine is physically doing what you expect?

mvieleers

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

mvieleers

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_3

Version 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.7

Restored my own config files.

POSITIVE RESULT: G32 produces output in the console.

Next steps:
sudo apt-get update
sudo apt-get upgrade

Version 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.7

NEGATIVE 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.

Danal

I'll do an upgrade and report back.

Luke'sLaboratory

Actually, I'll pile in here -

I went and checked mine and yep, I'm not getting console readouts for G32 NOR something like a G30 S-1. Anything that's supposed to use the built-in echo just doesn't work. I didn't notice because it physically works, which is all I noticed.

RC1 with DSF1.2.4 and DWC2.0.7, Duet 3 with PI.

blt3dp

I wanna say that I first installed my Duet 3, upgraded to RRF 3 stable and all the packages that go with it that I didn’t see the G32 response. There was an update somewhere in between there and now that I was getting it but when DWC 2.0.7 came out and I upgraded all packages, the G32 responses stopped.

Danal

After an apt-get sequence, I still get it just fine.

Duet Web Control 2.0.7
Board: Duet 3 MB6HC (MB6HC)
DSF Version: 1.2.4.0
Firmware: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 3.0 (2020-01-03b3)

Chrome browser, if that makes any difference.

2/15/2020, 7:14:53 PM G32
Leadscrew adjustments made: 0.118 0.120 0.109, points used 3, deviation before 0.115 after 0.000

kraegar

Tried in chrome just to verify (I usually use Firefox)

Danal

What is in your bed.g?

mvieleers

@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)

Danal

Hmmm... I'm really stumped. I don't see any differences that would make a difference, and I'm getting it consistently.

Danal

SSH into your Pi, and try the following (while you run a G32):

sudo journalctl -fu duetcontrolserver

If that doesn't show anything relevant, then:

sudo journalctl -fu duetwebserver

There will (should) be a lot more output on the webserver, and again, it is up to our eyeballs to see if anything is relevant.

chas2706

Hi, I mentioned in another post that since upgrading to RRF3.01_RC1 I too do not get any output from G32. I have Duet3 with raspberry pi.

chas2706

@Danal said in No output from G32 on DSF 1.2.4 / DWC 2.07:

sudo journalctl -fu duetcontrolserver

This is my output from the above command:

Feb 17 10:50:26 Duet3 DuetControlServer[345]: [info] Executing nested macro file Leadscrew_Levelling.g on channel HTTP
Feb 17 10:50:26 Duet3 DuetControlServer[345]: [info] Executing nested macro file bed.g on channel HTTP
Feb 17 10:50:26 Duet3 DuetControlServer[345]: [info] Executing nested macro file homeall.g on channel HTTP
Feb 17 10:50:35 Duet3 DuetControlServer[345]: [info] HTTP: Optional macro file deployprobe.g not found
Feb 17 10:50:52 Duet3 DuetControlServer[345]: [info] HTTP: Optional macro file retractprobe.g not found
Feb 17 10:50:52 Duet3 DuetControlServer[345]: [info] HTTP: Optional macro file deployprobe.g not found
Feb 17 10:51:02 Duet3 DuetControlServer[345]: [info] HTTP: Optional macro file retractprobe.g not found
Feb 17 10:51:02 Duet3 DuetControlServer[345]: [info] HTTP: Finished macro file homeall.g
Feb 17 10:51:02 Duet3 DuetControlServer[345]: [info] HTTP: Optional macro file deployprobe.g not found
Feb 17 10:51:13 Duet3 DuetControlServer[345]: [info] HTTP: Optional macro file retractprobe.g not found
Feb 17 10:51:13 Duet3 DuetControlServer[345]: [info] HTTP: Optional macro file deployprobe.g not found
Feb 17 10:51:26 Duet3 DuetControlServer[345]: [info] HTTP: Optional macro file retractprobe.g not found
Feb 17 10:51:30 Duet3 DuetControlServer[345]: [info] HTTP: Optional macro file deployprobe.g not found
Feb 17 10:51:38 Duet3 DuetControlServer[345]: [info] HTTP: Optional macro file retractprobe.g not found
Feb 17 10:51:38 Duet3 DuetControlServer[345]: [info] HTTP: Finished macro file bed.g
Feb 17 10:51:39 Duet3 DuetControlServer[345]: [info] HTTP: Finished macro file Leadscrew_Levelling.g

and with sudo lournalctl -fu duetwebserver I get:

Feb 17 10:54:24 Duet3 DuetWebServer[463]: [DoCode] Executing code 'M98 P"0:/macros/Bed Levelling/Leadscrew_Levelling.g"'
Feb 17 10:55:33 Duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Mvc.Infrastructure.ContentResultExecutor[1]
Feb 17 10:55:33 Duet3 DuetWebServer[463]: Executing ContentResult with HTTP Response ContentType of text/plain; charset=utf-8
Feb 17 10:55:33 Duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[2]
Feb 17 10:55:33 Duet3 DuetWebServer[463]: Executed action DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer) in 69796.3473ms
Feb 17 10:55:33 Duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
Feb 17 10:55:33 Duet3 DuetWebServer[463]: Executed endpoint 'DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer)'
Feb 17 10:55:33 Duet3 DuetWebServer[463]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Feb 17 10:55:33 Duet3 DuetWebServer[463]: Request finished in 69805.2756ms 200 text/plain; charset=utf-8

With both examples I notice the Pi does not return to "pi@Duet3:~ $ " is this something to do with the problem?

oliof

@chas2706 said in No output from G32 on DSF 1.2.4 / DWC 2.07:

With both examples I notice the Pi does not return to "pi@Duet3:~ $ " is this something to do with the problem?

That is due to the -f switch which means follow and waits for new stuff to be written to the journal. Not returning to the command prompt without hitting Ctrl-C is normal in this case.

chas2706

@oliof said in No output from G32 on DSF 1.2.4 / DWC 2.07:

With both examples I notice the Pi does not return to "pi@Duet3:~ $ " is this something to do with the problem?

That is due to the -f switch which means follow and waits for new stuff to be written to the journal. Not returning to the command prompt without hitting Ctrl-C is normal in this case.

Ok thanks I see.
I don't know what the problem is then. I just get no output from the console at all.