LaErrors, should I care about them? S3D



  • I noticed I am getting some LaErrors on 2.02 firmware. Is this due I am using Simplify3D? I know it doesn't produce good quality g-code (as I remember the segment length isn't even).

      M122
      === Diagnostics ===
      RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
      Board ID: 08DGM-9568A-F23SD-6JTDG-3SD6P-1UN7D
      Used output buffers: 3 of 20 (16 max)
      === RTOS ===
      Static ram: 25524
      Dynamic ram: 98624 of which 0 recycled
      Exception stack ram used: 512
      Never used ram: 6412
      Tasks: NETWORK(ready,544) HEAT(blocked,1176) MAIN(running,3868) IDLE(ready,200)
      Owned mutexes:
      === Platform ===
      Last reset 11:55:08 ago, cause: software
      Last software reset at 2019-02-08 22:23, reason: User, spinning module GCodes, available RAM 6324 bytes (slot 2)
      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: 134.4ms, max retries 0
      MCU temperature: min 28.4, current 32.2, max 34.6
      Supply voltage: min 0.3, current 0.6, max 27.7, under voltage events: 1, over voltage events: 0, power good: no
      Driver 0: standstill, SG min/max 0/1023
      Driver 1: standstill, SG min/max 0/1023
      Driver 2: standstill, SG min/max 0/1023
      Driver 3: standstill, SG min/max 0/1023
      Driver 4: standstill, SG min/max not available
      Date/time: 2019-02-09 10:18:35
      Cache data hit count 4294967295
      Slowest loop: 102.71ms; fastest: 0.06ms
      I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
      === Move ===
      Hiccups: 0, StepErrors: 0, LaErrors: 118, FreeDm: 240, MinFreeDm: 148, MaxWait: 166516ms, Underruns: 0, 0
      Scheduled moves: 0, completed moves: 0
      Bed compensation in use: none
      Bed probe heights: 0.000 0.000 0.000 0.000 0.000
      === Heat ===
      Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
      Heater 0 is on, I-accum = 0.1
      Heater 1 is on, I-accum = 0.6
      === GCodes ===
      Segments left: 0
      Stack records: 3 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: 135.87ms; fastest: 0.00ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
      HTTP sessions: 1 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.22
      WiFi MAC address 60:01:94:34:3e:4b
      WiFi Vcc 3.38, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 29520
      WiFi IP address 192.168.88.12
      WiFi signal strength -55dBm, reconnections 0, sleep mode modem
      Socket states: 0 0 0 0 0 0 0 0

  • administrators

    @dragonn, please make the GCode file available to me and I will look into it.



  • Sure, no problem
    https://www.dropbox.com/s/1rei041f33wfwkb/Tolerance_tester (1).gcode?dl=0
    I also attached my config.g if it will be needed
    0_1549704851966_config (1).g


  • administrators

    Thanks, please leave them there because it will be several days before I can retrieve them.

    Last time LA errors were reported it turned out to be a rounding issue and print quality was not affected.


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.