Filename too long error



  • This is a recent development with one of our boards and we can not figure out why this is occurring.

    A print starts but after about 2-5 min this error appears and the printer starts to behave radically, like low extrusion or it slows down. "on this occasion when the printing was around 60% done, and although the printer did not stop, the quality of the printing after that was very poor. "

    Short print files go through, only extended print files that are 5min long fail.

    This we have tried:
    Format SD card and put on fresh files. (including the www folder)
    Different SD card
    Re-flashing the firmware
    Having no G-code files on the card other than a 100% confirmed working good ones. (Prints that we have done over 1000 times)

    alt text

    Here is a failing gcode file: SV.gcode

    config.g


  • Moderator

    Were you able to capture a M122 after the poor print behaviour?

    Firmware and DWC version? Which Duet board?

    M92 X71 Y71 Z946                      ; Steps/mm for X Y Z
    M92 E70                 		  	; Steps/mm for E 
    M350 X1 Y1 Z1 E1 I1			; Set 1x microstepping with interpolation
    M906 X0 Y0 Z0 E0 I30 			; Set motor currents (mA) and increase idle current to 30%
    

    Seems odd. External drivers?



  • Duet 2 Wifi Board
    Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
    Firmware Electronics: Duet WiFi 1.02 or later
    Firmware Version: 2.04RC1 (2019-07-14b1)
    WiFi Server Version: 1.21
    Web Interface Version: 1.21-RC4

    Steps and external drives are correct. We power the motors directly so we set board power to 0.


  • administrators

    We had a report of something very similar a few weeks ago. It turned out that Kapersky AV had started sending OCP requests via HTTP that contained very long strings. RRF treats them like any other HTTP request, so it looks for a file of that name - but the length of the request gives rise to the "Filename too long" message.

    There is a workaround for this issue in RepRapFirmware 3.1.1. Alternatively, there may be an option in Kapersky to avoid making these requests.


Log in to reply