Hayley Tague
11-16-2020, 10:29 AM
So I've run into an issue while using the fiber - I've successfully been able to use the rotary quite a few times now on some tumblers and different things, but last week I started getting an error saying "Computer low on memory!" that would pop up when lighting or trying to mark in Split2 rotary mode. The program would either stop responding or close itself out after this message came up.
For reference, I'm using the provided computer that came with the fiber.
I tried to troubleshoot the issue myself with some of the threads I've seen on here. I ran a memory diagnostic on the computer two or three times and no alarm bells went off there. I changed my PCI Express and USB settings to off with no luck.
The issue seems to lie in my hatch settings - I can run a part with .01mm hatch no problem (usually) but anything smaller than that causes a shutdown. I get the error more consistently with each progressively smaller hatch I try to run until it completely gives out at about .005 mm.
Could this be something with my driver or where should I look next? Thanks.
Edited to add: this has happened to me originally after a day full of work so I chalked it up to overuse. Same thing has happened to me on start-up multiple times now so I'm assuming that isn't the issue.
For reference, I'm using the provided computer that came with the fiber.
I tried to troubleshoot the issue myself with some of the threads I've seen on here. I ran a memory diagnostic on the computer two or three times and no alarm bells went off there. I changed my PCI Express and USB settings to off with no luck.
The issue seems to lie in my hatch settings - I can run a part with .01mm hatch no problem (usually) but anything smaller than that causes a shutdown. I get the error more consistently with each progressively smaller hatch I try to run until it completely gives out at about .005 mm.
Could this be something with my driver or where should I look next? Thanks.
Edited to add: this has happened to me originally after a day full of work so I chalked it up to overuse. Same thing has happened to me on start-up multiple times now so I'm assuming that isn't the issue.