What country are you in? Maybe I can point you to someone who can give you better service. Or maybe after I see your error log I can convince your reseller that you need a new controller board.
This is the log file:
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.14.32-ultimaker (root@runner-ptzpiGvW-project-11447330-concurrent-0) (gcc version 6.3.0 20170516 (Debian 6.3.0-18)) #3 SMP Tue Jan 21 13:06:10 UTC 2020
[ 0.000000] CPU: ARMv7 Processor [410fc074] revision 4 (ARMv7), cr=10c5387d
[ 0.000000] CPU: div instructions available: patching division code
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt: Machine model: Ultimaker UM3-XL (2621)
[ 0.000000] bootconsole [earlycon0] enabled
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] cma: Reserved 64 MiB at 0x7bc00000
[ 0.000000] On node 0 totalpages: 261894
[ 0.000000] free_area_init_node: node 0, pgdat b0a64800, node_mem_map eb300000
[ 0.000000] Normal zone: 2302 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 261894 pages, LIFO batch:31
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: Using PSCI v0.1 Function IDs from DT
[ 0.000000] random: fast init done
[ 0.000000] percpu: Embedded 16 pages/cpu @efea2000 s34956 r8192 d22388 u65536
[ 0.000000] pcpu-alloc: s34956 r8192 d22388 u65536 alloc=16*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 259592
[ 0.000000] Kernel command line: um_an=235b console=tty0 fbcon=map:63 root=/dev/mmcblk1p2 ro rootwait rootdelay=2 rootfstype=f2fs console=ttyS0,115200 earlyprintk
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 961612K/1047576K available (5120K kernel code, 473K rwdata, 1604K rodata, 2048K init, 259K bss, 20428K reserved, 65536K cma-reserved, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xf0000000 - 0xff800000 ( 248 MB)
lowmem : 0xb0000000 - 0xeff06000 (1023 MB)
pkmap : 0xafe00000 - 0xb0000000 ( 2 MB)
modules : 0xaf000000 - 0xafe00000 ( 14 MB)
.text : 0xb0008000 - 0xb0600000 (6112 kB)
.init : 0xb0800000 - 0xb0a00000 (2048 kB)
.data : 0xb0a00000 - 0xb0a76720 ( 474 kB)
.bss : 0xb0a7d34c - 0xb0abe1d4 ( 260 kB)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] GIC: Using split EOI/Deactivate mode
[ 0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[ 0.000008] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[ 0.008089] Switching to timer-based delay loop, resolution 41ns
[ 0.014623] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[ 0.024129] clocksource: hstimer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370868154 ns
[ 0.033807] Console: colour dummy device 80x30
[ 0.038744] console [tty0] enabled
[ 0.042263] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=240000)
[ 0.052723] pid_max: default: 32768 minimum: 301
[ 0.057596] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.064329] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.072282] CPU: Testing write buffer coherency: ok
[ 0.077751] /cpus/cpu@0 missing clock-frequency property
[ 0.083171] /cpus/cpu@1 missing clock-frequency property
[ 0.088619] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.094827] Setting up static identity map for 0x40100000 - 0x40100060
[ 0.101641] Hierarchical SRCU implementation.
[ 0.108766] smp: Bringing up secondary CPUs ...
[ 0.114271] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.114422] smp: Brought up 1 node, 2 CPUs
[ 0.124408] SMP: Total of 2 processors activated (96.00 BogoMIPS).
[ 0.130674] CPU: All CPU(s) started in HYP mode.
[ 0.135390] CPU: Virtualization extensions available.
[ 0.141621] devtmpfs: initialized
[ 0.152856] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 4
[ 0.161008] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.170963] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.179732] pinctrl core: initialized pinctrl subsystem
[ 0.186368] NET: Registered protocol family 16
[ 0.192313] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.200366] cpuidle: using governor ladder
[ 0.204594] cpuidle: using governor menu
[ 0.208864] No ATAGs?
[ 0.208958] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[ 0.219454] hw-breakpoint: maximum watchpoint size is 8 bytes.
[ 0.241561] reg-fixed-voltage ahci-5v: could not find pctldev for node /soc@1c00000/pinctrl@1c20800/ahci_pwr_pin@1, deferring probe
[ 0.253622] reg-fixed-voltage usb0-vbus: could not find pctldev for node /soc@1c00000/pinctrl@1c20800/usb0_vbus_pin@0, deferring probe
[ 0.267705] SCSI subsystem initialized
[ 0.271765] usbcore: registered new interface driver usbfs
[ 0.277422] usbcore: registered new interface driver hub
[ 0.282955] usbcore: registered new device driver usb
[ 0.288410] pps_core: LinuxPPS API ver. 1 registered
[ 0.293468] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.302755] PTP clock support registered
[ 0.307872] clocksource: Switched to clocksource arch_sys_counter
[ 0.322629] NET: Registered protocol family 2
[ 0.327826] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.335161] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.341831] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.348437] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.354508] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.361236] NET: Registered protocol family 1
[ 0.869859] hw perfevents: no interrupt-affinity property for /pmu, guessing.
[ 0.877410] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 5 counters available
[ 0.887436] Initialise system trusted keyrings
[ 0.892108] Key type blacklist registered
[ 0.896516] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[ 0.909212] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.919135] Key type asymmetric registered
[ 0.923467] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[ 0.930986] io scheduler noop registered
[ 0.935271] io scheduler cfq registered (default)
[ 0.940729] sun4i-usb-phy 1c13400.phy: could not find pctldev for node /soc@1c00000/pinctrl@1c20800/usb0_id_detect_pin@0, deferring probe
[ 0.956742] sun4i-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver
[ 1.022248] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
[ 1.031593] console [ttyS0] disabled
[ 1.055478] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 48, base_baud = 1500000) is a U6_16550A
[ 1.064603] console [ttyS0] enabled
[ 1.071677] bootconsole [earlycon0] disabled
[ 1.101645] 1c28c00.serial: ttyS1 at MMIO 0x1c28c00 (irq = 49, base_baud = 1500000) is a U6_16550A
[ 1.131929] 1c29000.serial: ttyS2 at MMIO 0x1c29000 (irq = 50, base_baud = 1500000) is a U6_16550A
[ 1.164098] 1c29400.serial: ttyS3 at MMIO 0x1c29400 (irq = 51, base_baud = 1500000) is a U6_16550A
[ 1.181152] loop: module loaded
[ 1.185434] libphy: Fixed MDIO Bus: probed
[ 1.190360] sun7i-dwmac 1c50000.ethernet: PTP uses main clock
[ 1.196135] sun7i-dwmac 1c50000.ethernet: no reset control found
[ 1.202220] sun7i-dwmac 1c50000.ethernet: no regulator found
[ 1.207964] sun7i-dwmac 1c50000.ethernet: Ring mode enabled
[ 1.213547] sun7i-dwmac 1c50000.ethernet: DMA HW capability register supported
[ 1.220791] sun7i-dwmac 1c50000.ethernet: Normal descriptors
[ 1.234789] libphy: stmmac: probed
[ 1.238252] mdio_bus stmmac-0:00: attached PHY driver [unbound] (mii_bus:phy_addr=stmmac-0:00, irq=POLL)
[ 1.247735] mdio_bus stmmac-0:01: attached PHY driver [unbound] (mii_bus:phy_addr=stmmac-0:01, irq=POLL)
[ 1.258321] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.264902] ehci-platform: EHCI generic platform driver
[ 1.270640] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 1.276856] ohci-platform: OHCI generic platform driver
[ 1.282559] usbcore: registered new interface driver usb-storage
[ 1.289715] sunxi-rtc 1c20d00.rtc: rtc core: registered rtc-sunxi as rtc0
[ 1.296522] sunxi-rtc 1c20d00.rtc: RTC enabled
[ 1.301168] i2c /dev entries driver
[ 1.305740] axp20x-i2c 0-0034: AXP20x variant AXP209 found
[ 1.319034] ldo1: supplied by regulator-dummy
[ 1.323747] ldo2: supplied by regulator-dummy
[ 1.329268] ldo3: supplied by regulator-dummy
[ 1.335026] ldo4: supplied by regulator-dummy
[ 1.339486] vdd-io-pg: Bringing 3000000uV into 3300000-3300000uV
[ 1.346019] ldo5: supplied by regulator-dummy
[ 1.351500] dcdc2: supplied by regulator-dummy
[ 1.356592] dcdc3: supplied by regulator-dummy
[ 1.362555] axp20x-i2c 0-0034: AXP20X driver loaded
[ 1.370751] sdhci: Secure Digital Host Controller Interface driver
[ 1.376955] sdhci: Copyright(c) Pierre Ossman
[ 1.382716] sunxi-mmc 1c0f000.mmc: Got CD GPIO
[ 1.439216] sunxi-mmc 1c0f000.mmc: base:0xf0149000 irq:30
[ 1.445676] sunxi-mmc 1c11000.mmc: allocated mmc-pwrseq
[ 1.508147] sunxi-mmc 1c11000.mmc: base:0xf014b000 irq:31
[ 1.513987] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.524097] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.531235] Registering SWP/SWPB emulation handler
[ 1.536857] registered taskstats version 1
[ 1.541044] Loading compiled-in X.509 certificates
[ 1.546997] Key type encrypted registered
[ 1.561079] ehci-platform 1c14000.usb: EHCI Host Controller
[ 1.566733] ehci-platform 1c14000.usb: new USB bus registered, assigned bus number 1
[ 1.575243] ehci-platform 1c14000.usb: irq 33, io mem 0x01c14000
[ 1.607907] ehci-platform 1c14000.usb: USB 2.0 started, EHCI 1.00
[ 1.614325] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.621164] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.628406] usb usb1: Product: EHCI Host Controller
[ 1.633288] usb usb1: Manufacturer: Linux 4.14.32-ultimaker ehci_hcd
[ 1.639658] usb usb1: SerialNumber: 1c14000.usb
[ 1.644958] hub 1-0:1.0: USB hub found
[ 1.648852] hub 1-0:1.0: 1 port detected
[ 1.653721] ehci-platform 1c1c000.usb: EHCI Host Controller
[ 1.659411] ehci-platform 1c1c000.usb: new USB bus registered, assigned bus number 2
[ 1.668299] ehci-platform 1c1c000.usb: irq 38, io mem 0x01c1c000
[ 1.678244] mmc1: new DDR MMC card at address 0001
[ 1.683710] mmcblk1: mmc1:0001 P1XXXX 3.60 GiB
[ 1.688592] mmcblk1boot0: mmc1:0001 P1XXXX partition 1 16.0 MiB
[ 1.694767] mmcblk1boot1: mmc1:0001 P1XXXX partition 2 16.0 MiB
[ 1.700778] ehci-platform 1c1c000.usb: USB 2.0 started, EHCI 1.00
[ 1.707959] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.714777] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.722035] usb usb2: Product: EHCI Host Controller
[ 1.726918] usb usb2: Manufacturer: Linux 4.14.32-ultimaker ehci_hcd
[ 1.733289] usb usb2: SerialNumber: 1c1c000.usb
[ 1.737908] mmcblk1: p1 p2 p3
[ 1.743202] hub 2-0:1.0: USB hub found
[ 1.747032] hub 2-0:1.0: 1 port detected
[ 1.751951] ohci-platform 1c14400.usb: Generic Platform OHCI controller
[ 1.758703] ohci-platform 1c14400.usb: new USB bus registered, assigned bus number 3
[ 1.766878] ohci-platform 1c14400.usb: irq 34, io mem 0x01c14400
[ 1.842078] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.848911] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.856136] usb usb3: Product: Generic Platform OHCI controller
[ 1.862077] usb usb3: Manufacturer: Linux 4.14.32-ultimaker ohci_hcd
[ 1.868445] usb usb3: SerialNumber: 1c14400.usb
[ 1.874657] hub 3-0:1.0: USB hub found
[ 1.878503] hub 3-0:1.0: 1 port detected
[ 1.883329] ohci-platform 1c1c400.usb: Generic Platform OHCI controller
[ 1.890065] ohci-platform 1c1c400.usb: new USB bus registered, assigned bus number 4
[ 1.898132] ohci-platform 1c1c400.usb: irq 39, io mem 0x01c1c400
[ 1.972102] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.978929] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.986155] usb usb4: Product: Generic Platform OHCI controller
[ 1.992096] usb usb4: Manufacturer: Linux 4.14.32-ultimaker ohci_hcd
[ 1.998464] usb usb4: SerialNumber: 1c1c400.usb
[ 2.003696] hub 4-0:1.0: USB hub found
[ 2.007511] hub 4-0:1.0: 1 port detected
[ 2.012396] usb_phy_generic usb_phy_generic.0.auto: usb_phy_generic.0.auto supply vcc not found, using dummy regulator
[ 2.023760] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[ 2.029579] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 5
[ 2.037659] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
[ 2.044490] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.051741] usb usb5: Product: MUSB HDRC host driver
[ 2.056710] usb usb5: Manufacturer: Linux 4.14.32-ultimaker musb-hcd
[ 2.063078] usb usb5: SerialNumber: musb-hdrc.1.auto
[ 2.068702] hub 5-0:1.0: USB hub found
[ 2.072518] hub 5-0:1.0: 1 port detected
[ 2.077108] sunxi-rtc 1c20d00.rtc: setting system clock to 1970-01-01 00:00:08 UTC (8)
[ 2.085558] vcc3v0: disabling
[ 2.088596] vcc5v0: disabling
[ 2.091587] ahci-5v: disabling
[ 2.097489] Freeing unused kernel memory: 2048K
[ 4.300181] sun4i-drm display-engine: bound 1e60000.display-backend (ops sun4i_backend_ops [sun4i_backend])
[ 4.310611] sun4i-drm display-engine: bound 1e40000.display-backend (ops sun4i_backend_ops [sun4i_backend])
[ 4.320996] sun4i-drm display-engine: No panel or bridge found... RGB output disabled
[ 4.328914] sun4i-drm display-engine: bound 1c0c000.lcd-controller (ops sun4i_tcon_ops [sun4i_tcon])
[ 4.338585] sun4i-drm display-engine: No panel or bridge found... RGB output disabled
[ 4.346453] sun4i-drm display-engine: bound 1c0d000.lcd-controller (ops sun4i_tcon_ops [sun4i_tcon])
[ 4.467888] rc_core: IR keymap rc-cec not found
[ 4.472450] Registered IR keymap rc-empty
[ 4.476612] rc rc0: RC for sun4i as /devices/platform/soc@1c00000/1c16000.hdmi/rc/rc0
[ 4.484672] input: RC for sun4i as /devices/platform/soc@1c00000/1c16000.hdmi/rc/rc0/input0
[ 4.493384] sun4i-drm display-engine: bound 1c16000.hdmi (ops sun4i_hdmi_ops [sun4i_drm_hdmi])
[ 4.502062] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 4.508703] [drm] No driver support for vblank timestamp query.
[ 4.565267] sun4i-drm display-engine: fb0: frame buffer device
[ 4.608326] [drm] Initialized sun4i-drm 1.0.0 20150629 for display-engine on minor 0
[ 4.687747] F2FS-fs (mmcblk1p1): Magic Mismatch, valid(0xf2f52010) - read(0x2000)
[ 4.696325] F2FS-fs (mmcblk1p1): Can't find valid F2FS filesystem in 1th superblock
[ 4.704460] F2FS-fs (mmcblk1p1): Magic Mismatch, valid(0xf2f52010) - read(0x2005)
[ 4.711982] F2FS-fs (mmcblk1p1): Can't find valid F2FS filesystem in 2th superblock
[ 4.719729] F2FS-fs (mmcblk1p1): Magic Mismatch, valid(0xf2f52010) - read(0x2000)
[ 4.727218] F2FS-fs (mmcblk1p1): Can't find valid F2FS filesystem in 1th superblock
[ 4.734892] F2FS-fs (mmcblk1p1): Magic Mismatch, valid(0xf2f52010) - read(0x2005)
[ 4.742393] F2FS-fs (mmcblk1p1): Can't find valid F2FS filesystem in 2th superblock
[ 4.824518] EXT4-fs (mmcblk1p1): mounted filesystem with ordered data mode. Opts: (null)
[ 5.049272] F2FS-fs (mmcblk1p2): Mounted with checkpoint version = 14de4
[ 5.304918] F2FS-fs (mmcblk1p3): Mounted with checkpoint version = 485d5e38
[ 5.871957] systemd[1]: System time before build time, advancing clock.
[ 5.902046] systemd[1]: Failed to find module 'autofs4'
[ 5.931162] NET: Registered protocol family 10
[ 6.200195] Segment Routing with IPv6
[ 6.213142] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 6.236189] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[ 6.258684] systemd[1]: Detected architecture arm.
[ 6.309195] systemd[1]: Set hostname to <ultimakersystem-ccbdd300b763>.
[ 6.668632] systemd-fstab-generator[129]: Checking was requested for "rootfs", but it is not a device.
[ 6.754666] systemd[1]: File /lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
[ 6.771815] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
[ 7.108716] systemd[1]: griffin.system.service: Service has a D-Bus service name specified, but is not of type dbus. Ignoring.
[ 7.141705] systemd[1]: griffin.printer.service: Service has a D-Bus service name specified, but is not of type dbus. Ignoring.
[ 7.215331] systemd[1]: charon.service: Service has a D-Bus service name specified, but is not of type dbus. Ignoring.
[ 7.275022] systemd[1]: Condition check resulted in Journal Audit Socket being skipped.
[ 7.284934] systemd[1]: Listening on udev Control Socket.
[ 7.896042] rfkill_gpio usb0-kill: usb0-kill device registered.
[ 7.920005] rfkill_gpio usb1-kill: usb1-kill device registered.
[ 7.930699] rfkill_gpio usb2-kill: usb2-kill device registered.
[ 8.408081] usb 1-1: new high-speed USB device number 2 using ehci-platform
[ 8.558069] usb 2-1: new high-speed USB device number 2 using ehci-platform
[ 8.639124] systemd-journald[147]: Received request to flush runtime journal from PID 1
[ 8.661864] systemd-journald[147]: File /var/log/journal/afdbb9483672e59ab7707abe600ea16d/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 8.698254] usb 1-1: New USB device found, idVendor=28c7, idProduct=3841
[ 8.705047] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 8.712439] usb 1-1: Product: USB 2.0 Camera
[ 8.716755] usb 1-1: Manufacturer: Ultimaker B.V.
[ 8.779005] usb 2-1: New USB device found, idVendor=0cf3, idProduct=9271
[ 8.785780] usb 2-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
[ 8.793302] usb 2-1: Product: WLAN
[ 8.796859] usb 2-1: Manufacturer: MVQ1812
[ 8.801048] usb 2-1: SerialNumber: 12345
[ 10.050156] media: Linux media interface: v0.10
[ 10.091272] Linux video capture interface: v2.00
[ 10.125117] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (28c7:3841)
[ 10.136016] uvcvideo 1-1:1.0: Entity type for entity Processing 2 was not initialized!
[ 10.146919] uvcvideo 1-1:1.0: Entity type for entity Extension 6 was not initialized!
[ 10.159239] uvcvideo 1-1:1.0: Entity type for entity Camera 1 was not initialized!
[ 10.170326] input: USB 2.0 Camera: USB 2.0 Camera as /devices/platform/soc@1c00000/1c14000.usb/usb1/1-1/1-1:1.0/input/input1
[ 10.182941] usbcore: registered new interface driver uvcvideo
[ 10.188837] USB Video Class driver (1.1.1)
[ 11.138263] usb 5-1: new high-speed USB device number 2 using musb-hdrc
[ 11.641835] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[ 11.929159] sun4i-ss 1c15000.crypto-engine: Die ID 0
[ 12.019455] usb 5-1: New USB device found, idVendor=18a5, idProduct=0251
[ 12.026200] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 12.033569] usb 5-1: Product: STORE N GO
[ 12.037525] usb 5-1: Manufacturer: Verbatim
[ 12.041915] usb 5-1: SerialNumber: 07019A1D1824C314
[ 12.098838] usb-storage 5-1:1.0: USB Mass Storage device detected
[ 12.144144] scsi host0: usb-storage 5-1:1.0
[ 12.183651] libata version 3.00 loaded.
[ 12.448676] ahci-sunxi 1c18000.sata: controller can't do PMP, turning off CAP_PMP
[ 12.456214] ahci-sunxi 1c18000.sata: forcing PORTS_IMPL to 0x1
[ 12.468239] Generic PHY stmmac-0:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=stmmac-0:00, irq=POLL)
[ 12.518073] sun7i-dwmac 1c50000.ethernet eth0: RX IPC Checksum Offload disabled
[ 12.525436] sun7i-dwmac 1c50000.ethernet eth0: No MAC Management Counters available
[ 12.533273] sun7i-dwmac 1c50000.ethernet eth0: PTP not supported by HW
[ 12.588026] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 12.590799] pca953x 3-0024: 3-0024 supply vcc not found, using dummy regulator
[ 12.614546] usb 2-1: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested
[ 12.699992] ahci-sunxi 1c18000.sata: AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl platform mode
[ 12.709761] ahci-sunxi 1c18000.sata: flags: ncq sntf pm led clo only pio slum part ccc
[ 12.921091] usb 2-1: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.4.0.fw, size: 51008
[ 13.013733] usbcore: registered new interface driver ath9k_htc
[ 13.174887] ath9k_htc 2-1:1.0: ath9k_htc: HTC initialized with 33 credits
[ 13.418192] scsi host1: ahci-sunxi
[ 13.495069] ath9k_htc 2-1:1.0: ath9k_htc: FW Version: 1.4
[ 13.500809] ath9k_htc 2-1:1.0: FW RMW support: On
[ 13.504622] edt_ft5x06 3-0038: no IRQ setup, using polled input
[ 13.505198] input: generic ft5x06 (79) as /devices/platform/soc@1c00000/1c16500.i2c/i2c-3/3-0038/input/input2
[ 13.521629] ath: EEPROM regdomain: 0x60
[ 13.521635] ath: EEPROM indicates we should expect a direct regpair map
[ 13.521645] ath: Country alpha2 being used: 00
[ 13.521649] ath: Regpair used: 0x60
[ 13.600619] ata1: SATA max UDMA/133 mmio [mem 0x01c18000-0x01c18fff] port 0x100 irq 37
[ 13.888859] ieee80211 phy0: Atheros AR9271 Rev:1
[ 13.952745] ata1: SATA link down (SStatus 0 SControl 300)
[ 13.975448] sunxi-wdt 1c20c90.watchdog: Watchdog enabled (timeout=16 sec, nowayout=1)
[ 14.281140] f2fs_msg: 2 callbacks suppressed
[ 14.281155] F2FS-fs (mmcblk1p3): Mounted with checkpoint version = 485d5e3a
[ 14.757488] sun4i-codec 1c22c00.codec: Codec <-> 1c22c00.codec mapping ok
[ 14.778269] input: axp20x-pek as /devices/platform/soc@1c00000/1c2ac00.i2c/i2c-0/0-0034/axp20x-pek/input/input3
[ 14.870473] axp20x-gpio axp20x-gpio: AXP209 GPIO driver loaded
[ 14.978366] at24 1-0050: 2048 byte 24c16 EEPROM, writable, 16 bytes/write
[ 15.053949] scsi 0:0:0:0: Direct-Access Verbatim STORE N GO PMAP PQ: 0 ANSI: 6
[ 15.073061] sd 0:0:0:0: [sda] 31318016 512-byte logical blocks: (16.0 GB/14.9 GiB)
[ 15.093777] sd 0:0:0:0: [sda] Write Protect is off
[ 15.098683] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[ 15.114737] sd 0:0:0:0: [sda] No Caching mode page found
[ 15.120200] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 15.149078] sda: sda1
[ 15.162393] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 15.175706] systemd-journald[147]: File /var/log/journal/afdbb9483672e59ab7707abe600ea16d/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[ 19.522726] usbcore: registered new interface driver uas
[ 19.779452] ath9k_htc 2-1:1.0 wlx000e8e8f2428: renamed from wlan0
[ 33.645097] i2c i2c-3: new_device: Instantiated device lm75b at 0x4f
[ 33.793775] lm75: probe of 3-004f failed with error -5
[ 34.597135] Netfilter messages via NETLINK v0.30.
[ 34.677053] nf_tables: (c) 2007-2009 Patrick McHardy <kaber@trash.net>
[ 44.059978] random: crng init done
I did not try to print directly from Cura over wifi. Never done this before. I will try it.
GregValiant 1,250
I have a nice system for these situations. It is powered by two of the printer stepper motors so they must function. It requires a table the same height as the window sill, and two pulleys (one to open the window and the other to drag the printer over the sill). The system was designed with PencilCAD so no translation software is necessary (though you will appreciate that Email won't work).
There is one constraint regarding printer defenestration: A first floor window above a flower garden doesn't work well. A 10th floor window above a concrete parking lot is very satisfying (unless your supervisors Ferrari is parked below).
-
3
If you unplug the flow sensor from the feeder, and disable the flow sensor under the Gear Icon-->Settings menu, does it allow you to start the print?
https://ultimakernasupport.zendesk.com/hc/article_attachments/360049153871/Feeder3.JPG
I have flow sensor disabled but never tried to unplug it and print it. I will try. Thanks.
The log files should be huge - tens of thousands of lines long. That's just 44 seconds of the boot process when you first power on the printer. There should be many log files covering several days. Ideally you want the error to occur and then right afterwards you copy the log files to the USB flash.
So there is a communication between the linux computer (the boot process is shown in the logs above) and the servo controller computer (an arduino based computer). The linux computer is on an Olimex lime2 red circuit board. It has a powerful dual core cell-phone-like processor. The arduino based computer is on the white circuit board under your printer.
The arduino (white PCB) controls your servos directly. The linux computer (red PCB) has to tell the arduino what it wants - typically by sending gcodes to it. For example "G28" is sent to the arduino and the arduino runs a script to home 3 of the servos.
The communication between these 2 computers occurs over USB possibly? Or maybe a direct serial connection? What I suspect is that as part of this communication, the gcodes and responses from arduino back to the linux computer, contain some message that indicates an error. The linux computer doesn't know what to do with certain unexpected results and so spews out this generic message. This is my theory as to what is going on.
Regardless - both computers are mounted on the same single component (Ultimaker won't ship just one of the PCBs).
I'm hoping that the log file will show some of this communication error which will prove beyond any doubt that the problem is with one of these 2 computers.
4 hours ago, gr5 said:The log files should be huge - tens of thousands of lines long. That's just 44 seconds of the boot process when you first power on the printer. There should be many log files covering several days. Ideally you want the error to occur and then right afterwards you copy the log files to the USB flash.
Do you mean this?
This was done directly after it crashed and only way was to restart it then capture the log files then.
cap_Ultimaker-00b763_2019-02-14_10.20.13_N0_X186.5Y213.5.zip
Yes! Perfect. Below is the portion with the problem. In the "boot-2" file which is the most recent log file:
It's having a problem with one of the flow sensors. I think it's just not even connected? Or defective? I guess it could be:
The sensor
The cable
The circuit board.
I'd check out the cabling. I don't know if it's the left one or the right one. The sensors are inside the feeders. Notice how it gets the error "timeout on reading flow sensor". I don't know if sensor=147 implies left or right sensor.
It could be simply the cable came off during shipping - under the printer? If you can't find any loose cables then I think you need to contact the reseller again and ship it back again. Sorry. Send them the text below.
The feeder comes apart very easy if you just remove the two obvious screws. Taking it apart farther than that is tricky. I don't remember if you have easy access to the sensor or not. I wouldn't remove the bottom cover without permission from your reseller.
Feb 14 10:21:18 ultimakersystem-ccbdd300b763 python3[1001]: 2019-02-14 10:21:18,925 INFO printerService Procedure next step: PRINT: PRINTING
Feb 14 10:21:18 ultimakersystem-ccbdd300b763 python3[1001]: 2019-02-14 10:21:18,967 INFO switchActiveHotendProcedure Target hotend = 0
Feb 14 10:21:18 ultimakersystem-ccbdd300b763 python3[1001]: 2019-02-14 10:21:18,994 INFO printerService Procedure finished: SWITCH_ACTIVE_HOTEND
Feb 14 10:21:19 ultimakersystem-ccbdd300b763 python3[1001]: 2019-02-14 10:21:19,007 INFO printerService Procedure finished: PRE_PRINT_SETUP
Feb 14 10:21:19 ultimakersystem-ccbdd300b763 python3[1001]: 2019-02-14 10:21:19,056 INFO printerService Procedure start: SWITCH_ACTIVE_HOTEND: WAIT
Feb 14 10:21:19 ultimakersystem-ccbdd300b763 python3[1001]: 2019-02-14 10:21:19,060 INFO printerService Procedure next step: SWITCH_ACTIVE_HOTEND: WAIT
Feb 14 10:21:19 ultimakersystem-ccbdd300b763 python3[1001]: 2019-02-14 10:21:19,142 WARNING transportLayer Got error line 1 from printer: Error:A1335_FLOW_SENSOR_ERROR: timeout on reading flow angle, sensor=147
Feb 14 10:21:19 ultimakersystem-ccbdd300b763 python3[1001]: 2019-02-14 10:21:19,144 ERROR controller Halting ALL procedures
Feb 14 10:21:19 ultimakersystem-ccbdd300b763 python3[1001]: 2019-02-14 10:21:19,148 ERROR applicationLayer Marlin error: SYSTEM HALT!
Feb 14 10:21:19 ultimakersystem-ccbdd300b763 python3[947]: 2019-02-14 10:21:19,165 ERROR marvinService Added Fault: <Fault: level=3 code=13 message='Error:A1335_FLOW_SENSOR_ERROR: timeout on reading flow angle, sensor=147' data='dbus.Dictionary({}, signature=dbus.Signature('sv'))'>
Feb 14 10:21:19 ultimakersystem-ccbdd300b763 python3[1866]: INFO Okuda.DBus.PrinterServiceProxy Processing PrinterError(level: 3, code: 13, msg: 'Error:A1335_FLOW_SENSOR_ERROR: timeout on reading flow angle, sensor=147')
Feb 14 10:21:19 ultimakersystem-ccbdd300b763 python3[1866]: INFO Okuda.Components.screen_saver modeChanged: Mode.Printing --> Mode.AttentionRequired
Feb 14 10:21:19 ultimakersystem-ccbdd300b763 python3[1001]: 2019-02-14 10:21:19,232 INFO printFileStep Print procedure aborted
4 hours ago, gr5 said:Yes! Perfect. Below is the portion with the problem. In the "boot-2" file which is the most recent log file:
It's having a problem with one of the flow sensors. I think it's just not even connected? Or defective? I guess it could be:
The sensor
The cable
The circuit board.
The flow sensor has not been working for the life of the printer. I never worried about it as I cam from the UM 2 and it doesnt have one. I have disabled them both after following:
On 2/11/2021 at 5:59 PM, Priddy said:If you unplug the flow sensor from the feeder, and disable the flow sensor under the Gear Icon-->Settings menu, does it allow you to start the print?
Thanks also for the recommendation Priddy,
You're welcome! I hope that helps better narrow it down.
-
1
- 2 weeks later...
SOLVED:
There is a bug.... In my first post I wrote a list of what I did to try and solves this. It seems they have fixed something in an update half way through my solving because the end result the bug is:
With my Gcode, plus Flow Sensor unplugged and Flow Sensor disabled this errors shows.
Also, with this exact Gcode on a different S5 with Flow Sensor disabled and unplugged it shows the same error.
We have yet to identify what is wrong with my Gcode. With the Distributor's Gcode everything works fine and they were only able to get my Gcodes working if Flow sensor was plugged in and not disabled. So now I can use it with this in this state. I did try this anyway at the start, but they think when I updated it, it changed something. We dont know if its when I updated Cura or the S5. But I have it working 😄
-
1
Yikes. But you make it sound like you have to have the distributor slice the files for you?
- 7 months later...
Hello! I have the same problem with my printer. It started after i disassembled and reassembled the flow sensor 1. How do i fix this?
Edited by ProfessorKompressorThe flow sensors are complicated. There are I think 4 different flow sensors for the S5 and none of them are compatible with each other. And you have to tell the firmware which sensor it is. So if you changed out hardware then that could be part of the issue.
For now you can of course just turn off the flow sensor so you can at least still print.
Can you explain more about what you did? Did you buy your printer from 3dverkstan.se? They are very knowledgable - good people there.
- 1 month later...
kmanstudios 1,120
So, I cannot print now. My S5 printer got jammed during a print when filament shattered in the tube. It was old and I thought it would work after heating up. When I tried to get the feeder (#1) off the back to open it up, it popped one of the filament sensor wire connectors rendering the sensor useless.
But now, it just runs through the leveling process, runs the printhead to the front and then moves the printhead to the switch and it just dies with this message:
When it gives that message, the printhead stays at the switching position where it froze up and the buildplate drops without any resistance or guidance from the z screw.
This is when I try to print from USB or even the x,y calibration.
I have restored to default printer settings, but it wants to load black Tough PLA which I do not have, so I have to stop at that point. The feeders do work though when I load materials normally.
I just finished updating the firmware to the latest and it went smoothly. But it just will not print.
And, as luck would have it, I am on my last piece for Christmas gifts. GRRRrrrrrrrr....
I formatted a USB and copied the logs to it. This is all that is on the USB zipped up.
DataLogs_Kman.zipDataLogs_Kman.zip
I can perform all other functions as far as I can tell...just not printing.
Edited by kmanstudios
Hi there @kmanstudios,
Sorry to hear about your mishaps.
Let's see a picture(s) where the broken wire is located on this sensor and maybe someone can shear some more info about it. -Even if the wire is broken, -there might be a fix for it.. 🙂
Regards
Torgeir.
kmanstudios 1,120
Here is the pic you requested.
What I am confused about is that the connector is left off and I turned off the sensor.
Also, it goes through all motions until it is ready to actually print. If it can control the motion for that, what is missing at print time?
Thanks for your quick response. 🙂
In the meanwhile, I spent this morning cutting up the final piece (cut into three) to fit on my UM3E. Just spoiled by the S5 print area.
GregValiant 1,250
There are tools called Pin Sets (because there is more than one size in the set) that are sized to stick into the plastic multi-plug and allow the brass contacts to be pulled out. Then it's just strip and solder. You may be able to remove them with a paper clip or a dental tool. Each brass contact has a tang on the back that seats in a depression inside the plug and needs to be released to allow the contact to be pushed or pulled out. To re-assemble just push them back in in the correct orientation so the tang gets seated again. Needless to say - get the correct colors into the correct holes.
Those other wires don't look so good either.
kmanstudios 1,120
1 hour ago, GregValiant said:Those other wires don't look so good either.
Yeah, my fine motor skills are not what they used to be. I am in contact with fbr8 (serial numbers to identify correct S5) to get a replacement. I am thinking of just cutting the rest of the wires off that connector and do a wire colour to wire colour soldering and heat shrink wrap.
I always thought that the connector wires were too short. This way, splicing them will make them a tad longer so it is not so easy to slip.
Edited by kmanstudios-
Our picks
-
UltiMaker Cura 5.7 stable released
ArunC posted a topic in UltiMaker Cura,
Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more.
-
-
- 18 replies
.thumb.jpeg.0b7a05eafc09add17b8338efde5852e9.jpeg)
Picked By
MariMakes, -
-
Release Notes: S-Line Firmware 8.3.0 (Latest)
Dustin posted a topic in Firmware,
S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
(Sorry, was out of office when this released)
This update is for...
All UltiMaker S series
New features
Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.-
-
- 0 replies
Picked By
MariMakes, -
-
.thumb.jpeg.0b7a05eafc09add17b8338efde5852e9.jpeg)
Recommended Posts
gr5 2,172
Is there an error number? Like "ultimaker.com/ER25"? Can you show a photo on of the display on the S5?
My guess is you need a new white PCB controller board. They don't sell it separately - you have to get the Olimex board with it. Normally around 650 euros/dollars but you are still under warranty.
So after you get the error, put a USB flash stick into the printer and go to maintenance and get the log files. Then post the newest 2 log files here. The data in the log files last several days so you probably don't even have to duplicate the error but it is helpful to have the error near the newest portion of the log files. Knowing the time within a minute of when the error occurred because the log files have the time in them as well and they tend to be full of lots and lots of non-errors so it's sometimes hard to find an error in there but usually I can just search for "error".
Link to post
Share on other sites