Forum Replies Created
-
AuthorPosts
-
wephotographyMember
Heres what works for me when i get the verified failed error on my mac laptop. I restart my computer with the usb plugged in, with no other servers running like JSON. Unplug my machine and power back on. Typically this works first try but if not i either unplug and plug in the usb or power cycle my machine until i dont receive any errors. May take a few tries but always ends up working.
wephotographyMemberAll files running perfectly with 440.19. G2 & G3 arcs. Even ran a file that was 99 percent arc commands and all good. Thanks again for the help.
wephotographyMemberI use makercam for everything as theres not many options for mac users in the cam world. Im not sure ive had to force stop the machine as it runs until it hits the machines Y rails. All the runaway cuts ive had just keep going until it runs out of machine room so im assuming none of them return like the circles do.
- This reply was modified 9 years, 3 months ago by wephotography.
wephotographyMemberLooks like right around 6200 in chillipeppr numbering
wephotographyMemberI just added a screenshot of the failure area of the code. I ran the file four times, twice in 440.18 and twice in 442.04 with the exact result. I have noticed in the past that if i change the dimensions of the file or change bit size it can alter or remove the outcome of errors. Ive cut full run test pieces with no issues, changed my settings to a smaller bit for accuracy and resulted in a runaway or a circle cut. Ive also added the full original code file as i was running on my machine. That one is WWlogogcode. Would I be any more stable with an arduino/grbl set up?
wephotographyMemberThe problem is present in 440.18 as well as the current Edge.
wephotographyMemberRan into another runaway cut issue today. About ready to lose it on this thing. Most of my files cut fine but when i made a new one it took off on me again mid job. Please see the WW jpeg file along with the WWerrorgcode file with the depth set to .001 already.
wephotographyMemberSorry I never had time to get to the files this morning. Ended up having a lot more work to do today than expected. Ill try to get after them this evening if you still need them.
wephotographyMemberNevermind I read that wrong. Ill generate new ones in the morning set to 0 depth.
wephotographyMemberI can do that. What depth would work best for you?
wephotographyMemberMay try the isolate E file as well. It was a very consistent error so may be a good test run.
wephotographyMemberYeah it sure does. Thanks for getting after it so quickly though.
wephotographyMemberHave two new files on dropbox. See avery10x10 and sully10x10. The other files should already be small enough such as the 5error or E error.nc files. Both of those files triggered circles. The sully file was the worst on runaway cuts. I did cut the sully file successfully on the 380 firmware i was previously using.
- This reply was modified 9 years, 3 months ago by wephotography.
wephotographyMemberSee links for my test videos. Note that the bit being used is larger than the bit in the file. Didint want to risk snapping such a fine bit if it went wrong so it may have cut that section correctly if it had the right size bit in there. Looking at the video of the real time cut it looks to have not handled the curve correctly. The file from the video is in dropbox titled averyV
- This reply was modified 9 years, 3 months ago by wephotography.
wephotographyMemberGot the new firmware loaded. It actually seems to be worse than before. I ran the code that was just the inner cut of the V in averygcode and it didnt even cut the whole V, just ran the top left corner. Seems to have inaccurately cut that part as well. Uploading two videos now of what it did.
-
AuthorPosts