Duet 2 Wifi LaErrors?



  • So I've had this board for a little while on my FT-5 R2, it's working well I'm still fine tuning it.

    I notice that I get LaErrors when running M122
    It seems to operate fine, but I do seem to get random ribbing at times.
    any ideas?
    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS) running on Duet WiFi 1.02 or later
    Board ID: 08DGM-9T6BU-FG3SN-6JKD4-3SD6S-TUZHD
    Used output buffers: 1 of 20 (20 max)
    === RTOS ===
    Static ram: 28380
    Dynamic ram: 95820 of which 0 recycled
    Exception stack ram used: 468
    Never used ram: 6404
    Task NETWORK ready, free stack 324
    Task HEAT blocked, free stack 1256
    Task MAIN running, free stack 3624
    === Platform ===
    Last reset 04:43:30 ago, cause: power up
    Last software reset at 2018-12-29 20:06, reason: User, spinning module GCodes, available RAM 6404 bytes (slot 3)
    Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff
    Error status: 20
    Free file entries: 9
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms
    MCU temperature: min 38.2, current 39.6, max 39.7
    Supply voltage: min 24.1, current 24.3, max 24.7, under voltage events: 0, over voltage events: 0
    Driver 0: ok, SG min/max 0/373
    Driver 1: ok, SG min/max 0/283
    Driver 2: standstill, SG min/max not available
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Date/time: 2018-12-30 16:30:35
    Slowest loop: 9.68ms; fastest: 0.08ms
    === Move ===
    Hiccups: 0, StepErrors: 0, LaErrors: 22, FreeDm: 178, MinFreeDm 150, MaxWait: 0ms, Underruns: 229, 0
    Scheduled moves: 885813, completed moves: 885784
    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.0
    Heater 1 is on, I-accum = 0.5
    === 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: 4.30ms; fastest: 0.01ms
    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 1333, notready 0, noresp 0
      WiFi firmware version 1.21
      WiFi MAC address 84:f3:eb:83:4d:60
      WiFi Vcc 3.35, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 16768
      WiFi IP address 192.168.0.21
      WiFi signal strength -72dBm, reconnections 0, sleep mode modem
      Socket states: 0 0 0 0 0 0 0 0
      === Expansion ===


  • Forgot to mention, I only print VIA SD card either the internal or Due 5i


  • administrators

    Another user reported getting LA errors running RRF 2.01. The error reports turned out to be caused by rounding errors in the calculations, and release 2.02 includes a fix for this. So if you upgrade to firmware 2.02 then the LA errors may go away.



  • Interesting, what could be another cause?
    I will upload the new firmware soon.

    It seems to trigger when printing spheres and get ribbing not shown on other geometries.



  • Thanks!
    So far so good, I had to flash the firmware differently than described, I uploaded both the web and Duet firmware at the same time, then uploaded just the duet firmware again and then hit "yes, update firmware" and boom, off it went.

    I'm liking the absence of a reconnect button and request vs. actual speed.

    Now I'm working on pressure advance on it's MK10 nozzle setup.

    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
    Board ID: 08DGM-9T6BU-FG3SN-6JKD4-3SD6S-TUZHD
    Used output buffers: 3 of 20 (17 max)
    === RTOS ===
    Static ram: 25524
    Dynamic ram: 98560 of which 0 recycled
    Exception stack ram used: 416
    Never used ram: 6572
    Tasks: NETWORK(ready,648) HEAT(blocked,1232) MAIN(running,3844) IDLE(ready,200)
    Owned mutexes:
    === Platform ===
    Last reset 00:23:28 ago, cause: power up
    Last software reset at 2018-12-31 16:16, reason: User, spinning module GCodes, available RAM 6660 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: 9
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 38.7, current 38.9, max 38.9
    Supply voltage: min 24.3, current 24.5, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: ok, SG min/max not available
    Driver 1: ok, SG min/max not available
    Driver 2: standstill, SG min/max not available
    Driver 3: ok, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Date/time: 2018-12-31 16:59:14
    Cache data hit count 4294967295
    Slowest loop: 1.44ms; fastest: 0.08ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
    === Move ===
    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 150, MinFreeDm: 150, MaxWait: 0ms, Underruns: 0, 1
    Scheduled moves: 27092, completed moves: 27062
    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.0
    Heater 1 is on, I-accum = 0.5
    === GCodes ===
    Segments left: 1
    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 doing "G1 X148.108 Y167.986 E0.02387" 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: 170.19ms; fastest: 0.08ms
    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.21
      WiFi MAC address 84:f3:eb:83:4d:60
      WiFi Vcc 3.35, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 17040
      WiFi IP address 192.168.0.21
      WiFi signal strength -69dBm, reconnections 0, sleep mode modem
      Socket states: 0 0 0 0 0 0 0 0


  • @wyvern Starting with the 2.02 release you only have to upload the main firmware zip file. It contains everything needed and should update everything as needed.



  • Oh I see, much easier to do.
    New to duet (and 3D printing in general, come from PC building/ Hydraulic/mechanical/drone background) but compared to a ramps 1.4 board it's like comparing a candle stick to a COB projector light, it's taking some time getting familiar with the ins and outs as well as G-Code language.

    Print just finished MUCH better, still not perfect, but better than before, I printed the same exact file (just a sphere) with the same filament. Curious as to see how other prints turn out, going to swap out the 20T pulleys for 16t ones and finally install the anti-backlash nuts.



  • @wyvern said in Duet 2 Wifi LaErrors?:

    going to swap out the 20T pulleys for 16t ones

    Don't forget to change your steps per mm as needed.

    RepRapfirmware and the duet can take some getting used to, but it's hard to go back once you realize how flexible it is.



  • Thanks, yes, I'm aware of the steps adjustment, I installed larger Z lead pulleys and now have 800 s/mm vs 400.

    I'm at 79.5 on X and Y, I think 16t will put me at around 100 if they are quality pulleys and not wonky sizes. I don't print much above 60mm/s and 100-120mm/s travel.

    And yes, I do like how everything is easily found and configured, Marlin was a cluster truck trying to find what you were looking for and would often give me issues compiling.
    My favorite thing is not having to lug my 60lbs printer in and out of my room to plug in the USB is a life saver since the printer lives in the garage.

    Currently working on dynamic acc. and so far I'ts improved the print along with pressure advance.



  • Appears it has fixed it, done a few prints, currently have a deceivingly long print wrapping up- only 144gr but takes up the entire bed, 23hrs in 1.5 to go and no LaErrors.

    Thanks @dc42 .

    looking waaaaaay better than my 1.4 MKS, it had issues with this print as it is a retraction and geometry nightmare- steppers and drivers are barely warm, however I did install heat sinks just because I had them.

    Now to build in a web-cam and filiment runout switch, possibly a optical bed level sensor, but I'm new to configuring such a setup, I have a Anycubic delta with a microswitch probe, it works, but that stupid machine will have a stroke and either slam into the bed or print into the air randomly after reboots and require the whole process again.


Log in to reply