Raspberry PI4 and alfawise U30 PRO

dinodn

Hi i have this problem...printer work and stop continually any Idea?

21:23:36.330: start

21:23:36.330: echo:Marlin 1.1.9

21:23:36.335: echo: Last Updated: 2018-08-01 | Author: (none, default config)

21:23:36.337: echo:Compiled: Jun 11 2019

21:23:36.343: echo: Free Memory: 1686 PlannerBufferBytes: 1232

21:23:36.346: echo:EEPROM version mismatch (EEPROM=? Marlin=V55)

21:23:36.349: echo:Hardcoded Default Settings Loaded

21:23:37.215: echo:SD card ok

21:23:56.252: FIRMWARE_NAME:Marlin 1.1.9 (Github) SOURCE_CODE_URL:https://github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:3D Printer EXTRUDER_COUNT:1 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff

21:23:56.252: Cap:SERIAL_XON_XOFF:0

21:23:56.252: Cap:EEPROM:1

21:23:56.252: Cap:VOLUMETRIC:1

21:23:56.252: Cap:AUTOREPORT_TEMP:1

21:23:56.252: Cap:PROGRESS:0

21:23:56.252: Cap:PRINT_JOB:1

21:23:56.252: Cap:AUTOLEVEL:0

21:23:56.252: Cap:Z_PROBE:0

21:23:56.252: Cap:LEVELING_DATA:0

21:23:56.252: Cap:BUILD_PERCENT:0

21:23:56.252: Cap:SOFTWARE_POWER:0

21:23:56.252: Cap:TOGGLE_LIGHTS:0

21:23:56.252: Cap:CASE_LIGHT_BRIGHTNESS:0

21:23:56.252: Cap:EMERGENCY_PARSER:1

21:23:56.252: Cap:AUTOREPORT_SD_STATUS:0

21:23:56.252: Cap:THERMAL_PROTECTION:1

21:23:56.252: X:0.00 Y:0.00 Z:0.00 E:0.00 Count X:0 Y:0 Z:0

21:23:56.253: Warning: Communication timeout - resetting communication buffer.

21:23:56.253: Connection status: Buffered:10, Manual Commands: 4, Job Commands: 0

21:23:56.253: Buffer used:10 Enforced free byte:0 lines stored:1

21:43:03.294: Warning: Communication timeout - resetting communication buffer.

21:43:03.295: Connection status: Buffered:0, Manual Commands: 0, Job Commands: 0

21:43:03.295: Buffer used:0 Enforced free byte:0 lines stored:0

dinodn

22:14:02.143: N3363 G1 F4020 X109.813 Y100.759 E429.94812

22:14:02.204: ok

22:14:02.204: N3364 G1 X109.883 Y100.689

22:14:02.431: ok

22:14:02.431: N3365 G0 F7200 X109.883 Y100.7

22:14:02.432: N3366 G0 X111.698 Y100.759

22:14:09.835: ok (3)

22:14:09.839: Warning: Communication timeout - resetting communication buffer.

22:14:09.839: Connection status: Buffered:0, Manual Commands: 0, Job Commands: 5000

22:14:09.839: Buffer used:0 Enforced free byte:47 lines stored:0

22:14:09.839: M117 ETA 22:38:37 day 31

22:14:09.839: @excludeTimeOn

22:14:09.839: @snapshot 0

22:14:09.839: N3367 G1 F7200

22:14:09.839: @excludeTimeOff

22:14:09.840: N3368 G1 F4020 X100.759 Y111.698 E430.33402

22:14:09.844: ok

Repetier

How frequent are these problems? And are they at regular intervals?

What normally is the problem is that communication errors happen and not all returned "ok" messages are received like that, so server does not know that the command is finished.

Unfortunately the firmware seems to have all features disabled that would help fixing such errors or are not visible in log due to hiding some communication. When firmware has ok with line numbers, wait and busy protocol enabled server can quite quickly detect a missed ok.

dinodn

>>>How frequent are these problems? And are they at regular intervals?

Hi, thank you for your reply...

When i print many times the nozzle are stopped few seconds and restart (this create fusion on the object printed) not a regular interval.

I have a little usb cable (30 cm) and my power supply for raspberry is 3 ah. When i print from my pc have not problem....

i think the problem are on raspberry or in repetier software...

Repetier

It is not the software. If you use repetier-server on pc it would most likely also get better. Different serial drivers or usb ports behave a bit different, especially on the pi which is very power sensitive. 3a does not say anything. If it is a usb charger with 3a you might still get problems with voltage. If you login with ssh and send
dmesg

you will see if you have undervoltage from time to time. Also it not always causes a disconnect it seems still to cause problems from time to time. And without firmware side ways to detect this the last resort is timeout. What you need is a power supply best with 5.1 or 5.2v. But the fact that linux does not disconnect usb is already good. With bigger problems linux will disable usb for a short time causing a full abort.