Machine stuck on homing and centering

Welcome to the forum.

Try using your phone as a hotspot to connect to the internet. Sometimes this is an issue with an unstable wifi connection even though all other wifi devices are working normally.

3 Likes

Did you clear the cache on your browser? Are you 100% sure the machine is stuck, rather than the app?

When you first turn the machine on, do you hear clicking?

2 Likes

Yes, I hear clicking and once in a while the head moves. I’m reconnecting the chords now incase I didn’t put them in right or tight enough. I’ve also connected to my phones wi-fi. I go to the dashboard and the last picture I used still shows on the screen as well.

Ok. I cleared cache, checked the wires to make sure everything was secure. Put lens in the middle and also tried it on the left. It now says head not found or i get the error it didn’t take a picture.

I have also purchased black and white chords, I have replaced them and tried the old ones again with some sticky tape to secure them. I get the same messages. However, the head does move. But not like it does on a regular start up.

The clicking means you’re successfully connected to the internet, so at least that’s not your issue.

I’d check the head cable again. Make sure none of the tiny metal fingers have bent the wrong way.

2 Likes

I even tried installing the old one in again but will double check it. Maybe I need to buy another knew one incase I messed the new one up but it don’t appear broke or bent

Might be time to contact actual support - they can read the logs and might be able to see something we can’t. You can read your logs too, but they’re not written clearly so I’ve never found it worth it!

1 Like

Greetings - Is anything on the bed? Mine did the exact same thing when I left a funky shaped cutout on the honeycomb after cutting.

Yes, I think so too. I will have to find out what is wrong for sure. Thank you for the help though. And how do I read the logs?

No nothing on the bed. I even took out the crumb tray and tried it at one point.

1 Like

Ok thank you

I got the logs. Will turn everything in the house off today and try restarting everything. I even thought maybe it was my laptop so maybe I will head to my tablet instead and try it. I did get the logs though

1 Like

Here is a few of the lines from one folder. They are a bit hard to read though,. So, Idk.

lol.Aug 10 20:40:29 kernel: imx-sdma 20ec000.sdma: Direct firmware load for imx/sdma/sdma-imx6q.bin failed with error -2
Aug 10 20:40:29 kernel: i2c-dummy-sensor: probe of 0-0036 failed with error -22
Aug 10 20:40:29 kernel: i2c-dummy-sensor: probe of 2-0036 failed with error -22
Aug 10 20:40:29 kernel: sdhci-esdhc-imx 2190000.usdhc: card claims to support voltages below defined range
Aug 10 20:40:29 kernel: galcore: clk_get vg clock failed, disable vg!
Aug 10 20:40:29 kernel: glowforge: loading out-of-tree module taints kernel.
Aug 10 20:40:29 kernel: ov5648 0-0036: sensor id high value mismatch: 0x0 instead of 0x56
Aug 10 20:40:29 kernel: ov5648: probe of 0-0036 failed with error -22
Aug 10 20:40:29 kernel: ov8856 0-0036: 0-0036 supply dovdd not found, using dummy regulator
Aug 10 20:40:29 kernel: ov8856 0-0036: 0-0036 supply avdd not found, using dummy regulator
Aug 10 20:40:29 kernel: ov8856 0-0036: 0-0036 supply dvdd not found, using dummy regulator
Aug 10 20:40:29 kernel: wl18xx_driver wl18xx.0.auto: Direct firmware load for ti-connectivity/wl1271-nvs.bin failed with error -2
Aug 10 20:40:29 kernel: urandom_read: 1 callbacks suppressed
Aug 10 20:40:35 ntpd[540]: bind(24) AF_INET6 fe80::4ff:fed4:c67%6#123 flags 0x11 failed: Cannot assign requested address
Aug 10 20:40:35 ntpd[540]: unable to create socket on wlan0_ap (5) for fe80::4ff:fed4:c67%6#123
Sep 8 02:12:57 kernel: wlcore: WARNING no fw rx ba on tid 3
Sep 8 02:12:57 kernel: wlcore: WARNING no fw rx ba on tid 4
Sep 8 02:12:57 kernel: wlcore: WARNING no fw rx ba on tid 5
Sep 8 02:12:57 kernel: wlcore: WARNING no fw rx ba on tid 6
Sep 8 02:12:57 kernel: wlcore: WARNING no fw rx ba on tid 7
Sep 8 02:12:57 kernel: wlcore: WARNING no fw rx ba on tid 7
Sep 8 02:12:57 kernel: wlcore: WARNING no fw rx ba on tid 6

These are from the dmesg log
Booting Linux on physical CPU 0x0
Linux version 5.4.3 (oe-user@oe-host) (gcc version 9.3.0 (GCC)) #1 SMP PREEMPT Tue Apr 28 20:15:56 UTC 2020
CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
OF: fdt: Machine model: Glowforge Control Board
Memory policy: Data cache writeback
Reserved memory: created CMA memory pool at 0x1a000000, size 320 MiB
OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
On node 0 totalpages: 130816
Normal zone: 1150 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 130816 pages, LIFO batch:31
CPU: All CPU(s) started in SVC mode.
percpu: Embedded 15 pages/cpu s31436 r8192 d21812 u61440
pcpu-alloc: s31436 r8192 d21812 u61440 alloc=15*4096
pcpu-alloc: [0] 0
Built 1 zonelists, mobility grouping on. Total pages: 129666
Kernel command line: console=ttymxc0,115200 consoleblank=0 root=/dev/mmcblk2p1 rw quiet ramoops.mem_address=0x2ff00000 ramoops.mem_size=0x100000 ramoops.record_size=0x2000 ramoops.console_size=0x2000 ramoops.ecc=1 ramoops.dump_oops=1

This is the boot log. .

Wed Aug 10 20:40:15 2022: hwclock: can’t open ‘/dev/misc/rtc’: No such file or directory
Wed Aug 10 20:40:15 2022: Wed Aug 10 20:40:15 UTC 2022
Wed Aug 10 20:40:15 2022: hwclock: can’t open ‘/dev/misc/rtc’: No such file or directory
Wed Aug 10 20:40:15 2022: INIT: Entering runlevel: 5
Wed Aug 10 20:40:16 2022: grep: /var/pstore/console-ramoops*: No such file or directory
Wed Aug 10 20:40:16 2022: Creating network interfaces… done.
Wed Aug 10 20:40:16 2022: Configuring network interfaces… Successfully initialized wpa_supplicant
Wed Aug 10 20:40:20 2022: udhcpc: started, v1.31.1
Wed Aug 10 20:40:20 2022: udhcpc: sending discover
Wed Aug 10 20:40:23 2022: udhcpc: sending discover
Wed Aug 10 20:40:24 2022: udhcpc: sending select for 192.168.42.2
Wed Aug 10 20:40:24 2022: udhcpc: lease of 192.168.42.2 obtained, lease time 86400
Wed Aug 10 20:40:24 2022: /etc/udhcpc.d/50default: Adding DNS 192.168.0.1
Wed Aug 10 20:40:24 2022: /etc/udhcpc.d/50default: Adding DNS 192.168.0.1
Wed Aug 10 20:40:24 2022: done.
Wed Aug 10 20:40:24 2022: Starting system message bus: dbus.
Wed Aug 10 20:40:24 2022: hwclock: can’t open ‘/dev/misc/rtc’: No such file or directory
Wed Aug 10 20:40:24 2022: Starting ntpd: done
Wed Aug 10 20:40:24 2022: Starting syslogd/klogd: done
Wed Aug 10 20:40:24 2022: Starting services: done

You should send the logs to support. I think I’m safe in saying that ‘most’ of us in here don’t know how to read them. The folks that do know how to read them might be able to translate into more helpful info.

3 Likes

I did send them they offered a new refurbished machine. I’m gonna try to keep playing with it cause after $6995 I’m not about to spend another $2000 for one. I would go away from glowforge. But would like to keep trying different things and if anyone has any other suggestions I’m willing. I thought maybe the new chords I bought were faulty or something. Replaced both the white one and black, just ordered a new pulley wheel cause I broke it taking off belt to clean machine.

Have you installed any new electronics in your home… cordless phone, AppleTV, microwave, etc

2 Likes

Not anything new, no. I do have electronics though. I also tried creating a hot spot, resetting all networks, tried to connect from laptop, phone and a tablet. I just get stuck on homing and gives me the error it can’t read the head. So, I replaced the black and white chord but that didn’t help. This weekend I thought k would take the machine to my other house across town and hook to the internet there as it is better but it was working here. It is just stuck I think or something needs replaced. But I truly have no idea what is wrong just stuck with can’t read head error with last photo I engraved stuck on screen for about 3 weeks now

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.