@deirdrebeth - It’s not a WiFi issue…respectfully we are a software company ourself and use both internal servers (our own data center) and cloud based systems for various portions of our app…We would have clients around the globe chomping at us if our internet was an issue because our own app would be down. I wish it was that simple. Our entire office is running fine off the “router” you are referring too and we have our network segmented to computers dedicated to just running our printers/lasers. Yes - the large printers are running and other lasers are running fine but just this one Glowforge unit seems to be locking up and it only occurs in the cloudbased application. So that makes me fairly confident it’s a cloud issue on their end. It appears to be an issue with loading the SVG (either too much detail) file which is causing the app and laser to freeze up. That would make the most sense but it’s not a very complex design - see attached.
@vee - Thank you for checking in…The incident occurred shortly before I made the post (EST) and I struggled with the system for about 30min or so before posting. I have a .025 piece of aluminum in the system at 12"x6" in size. The artwork was created in illustrator and exported to an SVG file. When I attempt to load the artwork it only loads about 1/3 of the file. Additionally the bed scan will not refresh and I am unable to then remove the file from the job. Everything then freezes up and won’t function at all.
I attempted to remove the elements but the screen freezes and shows nothing of a bed scan. (See attached for various screen shots)…the bed scan should be showing a 6"x12" piece of aluminum but it’s just all white. The second time it was just all black with no images at all.
I do have a question for you…Are there “detail” limitations with what you can put in this laser? This is not a very detailed file but appears to cause your system issues with loading it. I’ve tested the graphic and if I reverse (invert) the target design then it goes through the process of loading but the bed image issue still occurs.!