Home › Forums › TinyG › TinyG Support › 440.16 Firmware still having arc issues
- This topic has 37 replies, 3 voices, and was last updated 9 years, 4 months ago by wephotography.
-
AuthorPosts
-
July 30, 2015 at 2:35 pm #8140wephotographyMember
See 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, 5 months ago by wephotography.
July 30, 2015 at 4:58 pm #8142aldenMemberOK. I need to dig in here to see what’s going on. I’ll report back. Sorry for the issues and thanks for your patience.
July 31, 2015 at 10:18 am #8143aldenMemberMaking progress here. Is it possible you could generate a complete Avery file that is only 10 inches in diameter? I am testing on a machine that cannot accommodate the 24″ extent of the entire file. If this is not practical I can make do with the existing files. Thanks.
July 31, 2015 at 12:37 pm #8144wephotographyMemberHave 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, 5 months ago by wephotography.
July 31, 2015 at 12:43 pm #8146aldenMemberThanks. I have sullycut working well. Still going through the entire file just to be sure. Takes a while, as I’m sure you are aware.
July 31, 2015 at 1:33 pm #8147wephotographyMemberYeah it sure does. Thanks for getting after it so quickly though.
July 31, 2015 at 2:10 pm #8148aldenMemberI’ve been after this bug for a while, so your misfortune is my opportunity. Thanks for the excellent files. I got about 75% of the way through sullycut before we had a power glitch (house power, not my machining setup). But it ran well up to then and the errors in that one were way back at the beginning. I ran the iolated Avery V withou error, and am running the full Avery10x10 now but the error there is much later in the file. I’m using OpenSCAM as a previewer. Great program. I’ll report back as I get more information.
- This reply was modified 9 years, 5 months ago by alden.
July 31, 2015 at 3:35 pm #8150wephotographyMemberMay try the isolate E file as well. It was a very consistent error so may be a good test run.
July 31, 2015 at 4:48 pm #8151aldenMemberI did run the E file. Ran fine to the end. Is it possible to get these files with a single pass – no depth-of-cut (i.e. multiple passes)? That way I can use them for regression testing with a pen plotter. I will get the revised code pushed to edge over the weekend so you can test using the updater.
July 31, 2015 at 9:42 pm #8153wephotographyMemberI can do that. What depth would work best for you?
August 1, 2015 at 1:27 am #8155wephotographyMemberNevermind I read that wrong. Ill generate new ones in the morning set to 0 depth.
August 1, 2015 at 4:31 pm #8158wephotographyMemberSorry 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.
August 1, 2015 at 11:23 pm #8161aldenMemberNo problem. Any time is fine. I can definitely use them.
You should be able to get the new file from the updater. I’d recommend using Master-440.18. Edge is (as always) a work in process.
Thanks for the help.
August 10, 2015 at 1:45 am #8194wephotographyMemberRan 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.
August 10, 2015 at 2:00 am #8195wephotographyMemberThe problem is present in 440.18 as well as the current Edge.
-
AuthorPosts
- You must be logged in to reply to this topic.