Big Red loosing her mind

[ice_man]

Interesting experience.... Turned on machine, started OS, files downloaded to Red, design came up that I had running when I quit last nite. Now it is supposedly ready to sew after locating and tracing the design. Now is where it gets crazy.... Hit the GO button and the pantagraph jumps back close to center of the hoop then moves God Knows Where and (if she were to start there the needle would most assuredly crash into the hoop) I am grateful I always start the machine with my finger on the RED button in case of emergencies.
I went throough the whole thing 3 times (start to finish, power up and so on)and it happened 3 times, then it quit and worked OK.
Any ideas????

[Juli in Kona]

I think you have to get rid of all the files in the Amaya jobs/current. Just delete them and then start OS again and then bring up your design fresh. That should fix the problem.

Juli in Kona

[sschroed2]

Had this same thing happen last week. Machine raced all the way to one side and stopped. Broke needle, horrifying sound, was sure Something major broke, did this in the middle of sewing a design. I shutdown everything, then restarted computer, etc. Sewed about 80,000 stitches everything went well. Then all of a sudden it did it again. So I called Melco Tech Supt. They emailed me info for my ehternet settings and told me to delete the folders for Jobs and Machines. I changed some of my ethernet settings per the instructions and deleted the jobs & machine folders, and successfully sewed out 150,000 stitches with no problem. It seems to have fixed the issue. However, I live on pins & needles wondering if it will do it again. When it's software the blame allways goes to Windows, but I can't help but wonder if there isn't something that could be done to improve AMAYA OS software. I get tired of having garments ruined because you never know when this will happen. For me it's been about 8 months to a year since it last happened, only then it didn't move as far, only about 1 to 2 inches. This time moved all the way to the stops about 10 inches and drug the needle thru the material as it went. My theory now is that I will delete my jobs and machines folders every couple of months.

[Anita]

I guess this should be under a different heading, hardware or software...but I want to stick with the thread. I could be way off base on this...but it's worth asking.

Anyone know the scoop on those 2 files, jobs/current? By name, they sound like the files that keep track of jobs in the queue and/or the last job stitched (to be restored when the system is restarted after a shutdown). Sounds like removing those files is a solution to more than 1 problem. Next time my Amaya seems confused, I'll give this same solution a try. I won't assume that it's me that's confused LOLOLOL.

I may be accomplishing the same thing as deleting those 2 files in a roundabout way by saving the design to a new filename. Or by bringing up a new design, loading it to the Amaya, then reopening the original file and loading it to the Amaya.

Now that I think about it, this may have inadvertently solved a problem I recently had. This weekend, when trying to deal with trims, I noticed that I could make changes to a design, save it and load to the Amaya, but the file wouldn't update and it didn't appear to reload to the Amaya. I used Expolorer to watch the timestamp on the file and it wouldn't change even if there were changes made to the design. I then saved the file to a new filename, loaded it to the machine and everything magically worked fine.

I hope this had the same affect as removing those files...and that it is a solution to some of the anamolies I've experienced. I hate things to just "magically" work. That's against my sys admin nature.

Anita

[sschroed2]

Saving as a new name does not have the same effect. When I'm digitizing everytime I make a change I save to a new name and I still had the problems. It seems that for some reason the files in those two directories get corrupt. Melco claims it's a Windows problem. Could be, I don't know.

[Anita]

Thanks. Just what I needed to know. Whether it's Windows or Melco...it's a simple enough fix if you know it exists.

Anita