›

FLSun SR has extreme Connection Problems

RockymbRockymb
in Repetier-Server
Ive plugged in my FLsun via a Windows Machine, the print starts completely normal, but after a few layers it starts pausing the print , because the firmware doesnt give the response repetier awaits. The Software said it should be fine after the reset but its not, a quick replig also doesnt help.
Any Ideas how I can fix this?
Thanks in advance

Comments

  • RockymbRockymb
    Update: My other Printer (Anycubic Kobra) is expieriencing the same Issue, also the Kobra and my Magician Pro seem to have heavy Problems when it comes to Printing, Repetier seems to ignore the home before Printing often times and also doesnt set the right height for the printer head, when im printing frim sd card all those problems dissappear.
    Please Help me
  • RepetierRepetier
    First always try the regular ping-pong mode which allows also serial reading of log as ok from firmware belongs always to previous command. Check the log and if it is not clear post the excert of the log (without any filter). Also after next update I plan a big faq entry on communication issues.

    What does ignore home before printing mean. Normally the gcode has the home command in it's gcode and we send it 1:1. See log where it gets send if there are issues but by default we do not remove / replace commands also you can confiure server to do so in printer config. So maybe also check for active replacements if they might catch that command.
  • RockymbRockymb
    Repetier said:
    First always try the regular ping-pong mode which allows also serial reading of log as ok from firmware belongs always to previous command. Check the log and if it is not clear post the excert of the log (without any filter). Also after next update I plan a big faq entry on communication issues.

    What does ignore home before printing mean. Normally the gcode has the home command in it's gcode and we send it 1:1. See log where it gets send if there are issues but by default we do not remove / replace commands also you can confiure server to do so in printer config. So maybe also check for active replacements if they might catch that command.
    After changing the 3 Printers to Ping Pong Mode the Anycubic and Magician work fine(no no home problems), but the FLSUN is expieriencing the same Issues as before. This is the Console without any Filters:
    Recv:18:24:44.705: Not SD printing (24)
    Mesg:18:24:51.757: Warning: Communication timeout - resetting communication buffer.
    Mesg:18:24:51.757: This means that a expected firmware response was not seen within the expected time.
    Mesg:18:24:51.757: The typical reason is a communication error and print should continue after the communication reset.
    Mesg:18:24:51.757: Connection status: Buffered:44, Manual Commands: 1, Job Commands: 5000
    Mesg:18:24:51.757: Buffer used:44 Enforced free byte:0 lines stored:1
    Mesg:18:24:58.759: Warning: Communication timeout - resetting communication buffer.
    Mesg:18:24:58.759: This means that a expected firmware response was not seen within the expected time.
    Mesg:18:24:58.759: The typical reason is a communication error and print should continue after the communication reset.
    Mesg:18:24:58.759: Connection status: Buffered:17, Manual Commands: 0, Job Commands: 5000
    Mesg:18:24:58.759: Buffer used:17 Enforced free byte:0 lines stored:1
    Mesg:18:25:05.772: Warning: Communication timeout - resetting communication buffer.
    Mesg:18:25:05.772: This means that a expected firmware response was not seen within the expected time.
    Mesg:18:25:05.772: The typical reason is a communication error and print should continue after the communication reset.
    Mesg:18:25:05.772: Connection status: Buffered:33, Manual Commands: 1, Job Commands: 5000
    Mesg:18:25:05.772: Buffer used:33 Enforced free byte:0 lines stored:1
    Mesg:18:25:05.772: Warning: Too many timeouts without response - disabling timeout message!
    Mesg:18:50:12.802: Connection closed by os.
    Mesg:18:50:16.522: Connection started
    Mesg:18:50:16.522: Printer reset requested - emergency:false
    Mesg:18:50:16.600: Dtr: false Rts: false
    Mesg:18:50:16.631: Dtr: true Rts: true
    Recv:18:50:16.647: Connection verified by:ok
    Recv:18:50:16.647: FIRMWARE_NAME:Marlin bugfix-2.0.x (Apr 2 2022 10:32:24) SOURCE_CODE_URL:github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:FLSUN SuperRacer EXTRUDER_COUNT:1 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff
    Recv:18:50:16.647: Cap:SERIAL_XON_XOFF:0
    Recv:18:50:16.647: Cap:BINARY_FILE_TRANSFER:0
    Recv:18:50:16.647: Cap:EEPROM:1
    Recv:18:50:16.647: Cap:VOLUMETRIC:1
    Recv:18:50:16.647: Cap:AUTOREPORT_TEMP:1
    Recv:18:50:16.647: Cap:PROGRESS:0
    Recv:18:50:16.647: Cap:PRINT_JOB:1
    Recv:18:50:16.647: Cap:AUTOLEVEL:1
    Recv:18:50:16.647: Cap:RUNOUT:1
    Recv:18:50:16.647: Cap:Z_PROBE:1
    Recv:18:50:16.647: Cap:LEVELING_DATA:1
    Recv:18:50:16.647: Cap:BUILD_PERCENT:0
    Recv:18:50:16.647: Cap:SOFTWARE_POWER:0
    Recv:18:50:16.647: Cap:TOGGLE_LIGHTS:0
    Recv:18:50:16.647: Cap:CASE_LIGHT_BRIGHTNESS:0
    Recv:18:50:16.647: Cap:EMERGENCY_PARSER:1
    Recv:18:50:16.647: Cap:PROMPT_SUPPORT:0
    Recv:18:50:16.647: Cap:SDCARD:1
    Recv:18:50:16.647: Cap:REPEAT:0
    Recv:18:50:16.647: Cap:AUTOREPORT_SD_STATUS:1
    Recv:18:50:16.647: Cap:LONG_FILENAME:1
    Recv:18:50:16.647: Cap:THERMAL_PROTECTION:1
    Recv:18:50:16.647: Cap:MOTION_MODES:0
    Recv:18:50:16.647: Cap:ARCS:1
    Recv:18:50:16.647: Cap:BABYSTEPPING:1
    Recv:18:50:16.647: Cap:CHAMBER_TEMPERATURE:0
    Recv:18:50:16.647: Cap:MEATPACK:0
    Recv:18:50:16.662: X:9.52 Y:51.38 Z:0.20 E:0.00X:9.52 Y:51.38 Z:0.20 E:0.00 Count A:20144 B:20924 C:23652
    Recv:18:50:16.662: Not SD printing
    Recv:18:50:16.662: X:9.52 Y:51.38 Z:0.20 E:0.00X:9.52 Y:51.38 Z:0.20 E:0.00 Count A:20144 B:20924 C:23652
    Recv:18:50:16.662: X:9.52 Y:51.38 Z:0.20 E:0.00 Count A:20144 B:20924 C:23652
    Mesg:18:50:16.662: Some printers don't implement timing, but can cause unexpected execution based on file name.
    Mesg:18:50:16.662: By triggering unknown command here we block it for real usage.
    Mesg:18:50:16.662: So please ignore unknown command if it appears now.
    Recv:18:50:16.724: X:9.52 Y:51.38 Z:0.20 E:0.00X:9.52 Y:51.38 Z:0.20 E:0.00 Count A:20144 B:20924 C:23652
    Recv:18:50:16.724: X:9.52 Y:51.38 Z:0.20 E:0.00 Count A:20144 B:20924 C:23652
    Recv:18:50:54.657: Not SD printing (19)

    Any Thoughts?
  • RockymbRockymb
    edited February 2023
    Another Update:
    Anycubic Kobra is running into the same problems again,Home Problems are away, Log for the Kobra:
    Mesg:20:41:38.457: Warning: Communication timeout - resetting communication buffer.
    Mesg:20:41:38.457: This means that a expected firmware response was not seen within the expected time.
    Mesg:20:41:38.457: The typical reason is a communication error and print should continue after the communication reset.
    Mesg:20:41:38.457: Connection status: Buffered:31, Manual Commands: 1, Job Commands: 5000
    Mesg:20:41:38.457: Buffer used:31 Enforced free byte:0 lines stored:1
    Mesg:20:41:42.458: Warning: Communication timeout - resetting communication buffer.
    Mesg:20:41:42.458: This means that a expected firmware response was not seen within the expected time.
    Mesg:20:41:42.458: The typical reason is a communication error and print should continue after the communication reset.
    Mesg:20:41:42.458: Connection status: Buffered:18, Manual Commands: 0, Job Commands: 5000
    Mesg:20:41:42.458: Buffer used:18 Enforced free byte:0 lines stored:1
    Mesg:20:41:46.459: Warning: Communication timeout - resetting communication buffer.
    Mesg:20:41:46.459: This means that a expected firmware response was not seen within the expected time.
    Mesg:20:41:46.459: The typical reason is a communication error and print should continue after the communication reset.
    Mesg:20:41:46.459: Connection status: Buffered:45, Manual Commands: 1, Job Commands: 5000
    Mesg:20:41:46.459: Buffer used:45 Enforced free byte:0 lines stored:1
    Mesg:20:41:46.459: Warning: Too many timeouts without response - disabling timeout message!
  • RepetierRepetier
    Logs sare incomplete - no commands being send or ack messages. What I see is
    Recv:18:50:54.657: Not SD printing (19)
    Wonder why your printer tells this constantly. What command triggers this and since we do no sd printing that is clear but it sounds like it expects sd printing here. Might be a hint when we know which commands trigger this. At startup we send no commands saying we do sd printing.
  • RockymbRockymb
    I checked every Port of the Printer if there was any other storage device plugged in, there was not. I set the timeout to 20s wait, it didnt help, the Printers are expieriencing the same Issues
  • RockymbRockymb
    Repetier said:
    Logs sare incomplete - no commands being send or ack messages. What I see is
    Recv:18:50:54.657: Not SD printing (19)
    Wonder why your printer tells this constantly. What command triggers this and since we do no sd printing that is clear but it sounds like it expects sd printing here. Might be a hint when we know which commands trigger this. At startup we send no commands saying we do sd printing.
    The FLSUN automatically occurs as a Harddrive in Windows if its connected and has something lika a micro sd plugged in, maybe it has something to do with that
  • RepetierRepetier
    Some 32 bit boards promote sd card as disk in addition to serial connection. Should not be a promblem from this. But as said full communication might show better whats going on then the reduced version.
  • RockymbRockymb
    Right now 2 new Prints are running on the FLSun and the Anycubic, till now everything is running fine. 
    I have maid no changes att all to the FLsun, I changed the buffer in the Anycubic to 0, the Flsun even has a SDcard insertet.
    I keep providing Updates in this discussion if further problems occour.
  • RepetierRepetier
    Buffer 0 is not good, except if ping-pong is active then it is ignored anyway. Low values degrade to ping-pong mode.
  • RockymbRockymb
    Repetier said:
    Buffer 0 is not good, except if ping-pong is active then it is ignored anyway. Low values degrade to ping-pong mode.
    Yes its Ping Pong mode on the Kobra

  • RockymbRockymb
    The FLSun has now Problems with Printing again, it just randomly stops because it becomes none or the wrong Firmware response. The Kobra has a simillar problem but the Kobra resumes after a few seconds
  • RepetierRepetier
    So it is even after timeout not responding? There is an option to try to reconnect usb on linux systems on timeout. This helps if it is the driver hanging and not sending any further data also it shows the connection is alive.
  • RockymbRockymb
    I am using a Windows Machine, even a manual replug works only like half of the time
  • RepetierRepetier
    If unplug does not work and you need to disable printer plus unplug to get it working it is the printer side communication that crashed I'd say. As long as it has power ist does not start again and disabling printer might also not work if it gets power from usb. This is mostly from electric noise cauing signals that crash the driver. Check if cables come close to usb parts, shorter usb cable or different usb port are things that might help. Especially if you have other usb devices on same usb bus it might also be cross polution.
Sign In or Register to comment.