I purchased a glowforge basic at the very beginning. I loved the machine for years.
It worked perfectly everytime I tried to use it. Then - November-December last year, my machine stopped cutting fully though material. I could tweak settings or do multiple passes, but it was not cutting at previous power levels.
I contacted support. They offered to replace/upgrade my machine to the plus machine because the basic was no longer available. I want to say i was asked to pay $1400.00 for a refurbished replacement machine.
A new machine was shipped. Worse problem, will not cut or even mark material. Dead on arrival. RMA for a new machine.
Second replacement came, same problem, will not cut or even mark material. Dean on arrival - this one appeared to not be filled all the way with coolant. RMA for a new machine.
I was understandably very upset and frustrated. I received my replacement machine in February 2024 timeframe. This is the third replacement, and my fourth machine.
I left for vacation the day after it arrived, so i did not get it setup. Life happened, and the machine set unopened indoors in a clean dry location until today. I thought for sure - when i eventually get this thing out and get it runinng it should be fine. I thought there could be no chance that they could send me three DOA machines back to back to back.
Today - i setup the machine. Will not cut or mark any material on any setting. I see the laser firing in the tube. The machine acts like it is cuttting. It will just not cut.
I tried numerous designs, with different proofgrade material. Tried proofgrade settings, tried manual settings. Tried an outline cut full power, not a single mark even on the masking.
Has anyone else had a similar issue? I can’t believe that QAQC is this bad. I now have 4 seemingly faulty machines in my house. I have moved three machines in/out of my basement.
I have unpacked and repacked machines 3 times now.
Since i never used my machine in the 6 month warranty, I am assuming that glowforge is going to tell me to pound sand.
This has to be a backend software bug right? Has anyone else been through this level of nonsense?
Jason