Lightobject.com Support Forum

Our new DSP AWC 608 looks like it *might* have some sort of an internal memory issue going on, and I was wondering if anyone else had seen anything like this. The attached image shows the results of a cut file that I loaded (along with several other files) into the controller this morning. You can see the leaf shape that has an obvious cut error, and if we repeat running the same file from the controller, the error happens every time at the exact same spot in the exact same way. This isn't a file issue- this sort of thing has actually happened with several different files since the controller was installed, and if I reload the exact same file into a different position in memory in the controller, it'll cut fine. It seems to be a function of where in memory the file is loaded rather than the file itself, and the other files that I loaded up this morning haven't had this problem.

We've seen this happen with several files over the past few weeks since installing the new controller. Has anyone else observed this with their own cutters? It looks to me (software programmer by day, laser junkie by night) like it's either a bad location in the physical memory, or a pointer issue in the controller software. We've tried All Delete to completely clear the memory, and the problem just pops right back up.

It could be a 'bug' on the OS. What version of the OS installed on your DSP card?
Check it with the LCD control panel and scroll it down to the last roll, hit enter to read the version
Let me know and see if I have update patch for you


Marco

Thanks for getting back to me so quickly!

Is "Main Board" the number you need? 7.14.05.28

OS update sent. Give it a try see if it fix the problem or not

Marco

hi there
you should not load many files in the machine ( DSP) memory because the memory is only 64mb. after a big file you should format the memory with the display format memory function.
sometimes because the memory will write over the old file something is left what comes then in the play with the new file.
I have seen and experienced this many times.
greetings
walt

scrappyjedi wrote:Our new DSP AWC 608 looks like it *might* have some sort of an internal memory issue going on, and I was wondering if anyone else had seen anything like this. The attached image shows the results of a cut file that I loaded (along with several other files) into the controller this morning. You can see the leaf shape that has an obvious cut error, and if we repeat running the same file from the controller, the error happens every time at the exact same spot in the exact same way. This isn't a file issue- this sort of thing has actually happened with several different files since the controller was installed, and if I reload the exact same file into a different position in memory in the controller, it'll cut fine. It seems to be a function of where in memory the file is loaded rather than the file itself, and the other files that I loaded up this morning haven't had this problem.

We've seen this happen with several files over the past few weeks since installing the new controller. Has anyone else observed this with their own cutters? It looks to me (software programmer by day, laser junkie by night) like it's either a bad location in the physical memory, or a pointer issue in the controller software. We've tried All Delete to completely clear the memory, and the problem just pops right back up.

Thank you for the OS update, Marco! We will give that a try and see how it works.

For myself, I have the same problems with mine. What I do is I break up a file into several color combo's depending on cutting, engraving, and order of both. This has cleared up all 'vector spacing' errors I've had over the past while with working on it.

Just don't have too many objects with one particular color and it seems to fix it (unless the new OS fixes this?)

hi marco
what is the newest OS update???
greetings
waltfl

I've been running for several days on the OS upgrade and haven't seen the issue again. I also formatted the controller memory after upgrading, so I can't really say which procedure fixed it. If anyone else is having this issue, I suggest trying both.

Thanks again, Marco!

Good to hear that it worked but Ouh~~~ you did two things at the same time so I can't tell whether was the new patch helped or it was a memory issue.


Marco

I know! And as an engineer I should know better!

Well, you can downgrade OS to the previous and check it. Since you have new OS, so you can upgrade to the new one as soon as you want. That way, you can learn and so do I. I learned CO2 by doing "test & try", nothing new. Well, if you don't want to mess it around and need it for production, then it is understandable.


Marco

I've been having the same issues as Scrappy there, and I'm still on the old OS. So I don't think it's a memory issue.

If the newer OS is available, I'd love to fix mine as well

Axeman wrote:I've been having the same issues as Scrappy there, and I'm still on the old OS. So I don't think it's a memory issue.

If the newer OS is available, I'd love to fix mine as well

Links sent per your request. Let me know if it solved the problem

Marco