M999 - sometimes gives 'Operation Cancelled' message

[jens55]

This is happening intermittently.
SOnetimes it works, sometimes it doesn't.
Sometimes when I have changed config.g and select 'yes' to reset the duet it will do the operation, sometimes it comes back with m999 operation canceled.

[jens55]

[SIam]

can you please provide more information? which board? which firmware? config.g ?

[jens55]

It's a duet2 wifi board and I am in the process of upgrading from RRF2 to RRF3. The issue has never occurred in RRF2. I mostly noticed it when editing the config.g file, saving it and answering 'yes' to the question of restarting the Duet. The issue also happens when manually issuing a 'M999' command.
config(1).g

It seems unrelated to config.g, sometimes it flakes out and other times a reset works fine. Anyway, I have attached the latest config.g file.

[SIam]

why you do

M350 X16 Y16 Z16:16 E256:256 I1 ; Configure microstepping with interpolation for x,y,z,E0 and E1

Interpolation only works with 16 Steps not with 256

in your config:

M106 P0 S0                     ************************            ; set fan 0 value .

**************************************************************************************************************************************
 
; old code from RRF 2
; set up for piezo z probe
 
;M558 P8 I1 R0.3 F600 H10 T3000     	   	  ; Digital mode (P5), active high (I1), delay (R0.3), speed (F600), dive height (H5), probe up to 4 times (A4) for at least two consecutive consistent ;readings,travel speed (T8000)
;M558 P1 I1 R0.3 F300 H5 A4 T8000
 
;M558 P1 I1 R0.3 F300 H5 T8000  
 
;;G31 P500 X11.0 Y0.5 Z1.65 ; set threshold and offsets
;The XYZ parameters in the M558 command define which axes the Z probe is used to home (0 = Z probe not used to home this ;axis, 1 = Z probe used). By default, RepRapFirmware for the Duet 0.8/0.8.5 (but not ;the Duet 2) uses the Z probe to home ;the X and Z axes.
 
;The H parameter defines the Z probe dive height, which is the height above the trigger height from which probing starts. ;The default is 3mm or 5mm depending on firmware version. You may wish to increase it ;during initial calibration.
 
 
;G31 X0 Y0 Z-0.18 P474                              ;probe X, Y, Z offsets (all zero = first nozzle), might use x+10 for the spot between the nozzles, Trigger point of probe
						   ; G31 must come after M558
						   ; Z should normally be slightly negative as the probe triggers just below zero
; correct for proper MMU temperature
 
***************************************************************************************************************************************
 

bevore the stars missing a ; semicolon

after the error operation canceled type in the g-code console M122 and post the result

[jens55]

@SIam said in M999 - sometimes gives 'Operation Cancelled' message:

why you do

M350 X16 Y16 Z16:16 E256:256 I1 ; Configure microstepping with interpolation for x,y,z,E0 and E1

Interpolation only works with 16 Steps not with 256

Yes, I am aware of that. This is what I had in RRF2 and I assume the interpolation gets ignored for the extruders.

in your config:

M106 P0 S0                     ************************            ; set fan 0 value .

bevore the stars missing a ; semicolon

Awesome catch - thanks !

after the error operation canceled type in the g-code console M122 and post the result

The damn thing is working at the moment. I will keep trying to catch it when it faults out.

[jens55]

There we go:

m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-917DA-G4MS8-6JKD0-3SD6M-KTSRA
Used output buffers: 3 of 24 (7 max)
=== RTOS ===
Static ram: 30516
Dynamic ram: 93004 of which 0 recycled
Exception stack ram used: 216
Never used ram: 7336
Tasks: NETWORK(ready,1048) HEAT(blocked,1184) DUEX(suspended,160) MAIN(running,3676) IDLE(ready,156)
Owned mutexes:
=== Platform ===
Last reset 00:00:14 ago, cause: software
Last software reset at 2020-01-14 14:06, reason: User, spinning module GCodes, available RAM 7252 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 29.8, current 30.2, max 30.6
Supply voltage: min 24.3, current 24.4, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 28385061
Slowest loop: 1.51ms; fastest: 0.10ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.44ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 of 8

• WiFi -
  Network state is running
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.23
  WiFi MAC address b4:e6:2d:52:ef:1f
  WiFi Vcc 3.43, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 26096
  WiFi IP address 192.168.1.114
  WiFi signal strength -46dBm, reconnections 0, sleep mode modem
  Socket states: 0 0 0 0 0 0 0 0
  === Filament sensors ===
  Extruder 0 sensor: no filament
  Extruder 1 sensor: ok

[jens55]

I also noted the last two lines re filament sensors - the web panel shows neither one of the sensors as active which I posted about on another thread.

[jens55]

Just a closing remark to this thread ..... apparently the M999 error message was a known bug in the web interface and has been fixed in version 2.06