Home › Forums › TinyG › TinyG Support › FW 440.18 CW/CCW bug?
- This topic has 15 replies, 3 voices, and was last updated 9 years, 1 month ago by cmcgrath5035.
-
AuthorPosts
-
September 14, 2015 at 11:01 am #8743cmcgrath5035Moderator
I just created a relatively simple milling job, tried to run it and believe I may have found the issue Kurt S is having here:
My CAD system created the following, with two CCW circles
When I ran it, the 8 holes cut OK, both circles got skipped.
I hand edited the Gcode to change from G03 circles to G02 circles.
CW cutting ran fine
September 14, 2015 at 4:40 pm #8744cmcgrath5035ModeratorOOps
I just installed FW 440.20, now neither CW or CCW run cut………….
September 15, 2015 at 8:32 am #8745rtgallusMemberPlease clarify, do you mean that FW 440.20 works OK? If it does, I will install it.
RTG
September 15, 2015 at 11:08 am #8746cmcgrath5035ModeratorNot for me, but that could be the SPJS 1.83 issue.
Check back in an hour (!2:00 EDT)September 15, 2015 at 12:07 pm #8747cmcgrath5035ModeratorOK, reran a series of tests.
I have two Gcode files availableThis is a new job, simple one at that. Eight (8) holes and two circles.
The CAD generated Gcode used a single G03 (ccw) arc command for each circle.
When I originally found it didn’t run, I manually changed the two commands from G03 to G02 (cw) arcs and created a second file.Results:
FW Ver SPJS CW CCW
—— —- — —
440.18 1.83 OK Bad
440.18 1.80 OK Bad
440.20 1.83 Bad Bad
440.20 1.80 Bad BadBad == Bit descends to proper cut depth then immediately returns to safe level and moves to next line of Gcode without any arc movement.
This is a new job, I never tried it on 440.14 and no longer have the 440.14.hex around.
If of use, the tinyGV7 parameters are here (same used 440.18 and 440.20)——-
For rtgallus – 440.20 has been tested by Alden with a MUCH tougher Gcode file and worked well, so whatever is going on here may not affect others.
The fact that these are full circle cuts may be the issue.(?)
If 440.18 is failing you for some reason, I would say give 440.20 a try and post your results.September 15, 2015 at 3:29 pm #8748rtgallusMemberThank you. I’m actually using 440.19 and SPJS 1.80 and also 1.83 and have had no problems. My problem in the past has been overloading of the buffer with other version of SPJS that have resulted with the machine pausing.
I have not had a problem with CW or CCW circles run in gcode generated by CamBam, either in inches or mm. Here is a dropbox link to a file that I ran in air just a little while ago. Most circles are G2 but some G3 also.
Thanks again.
Rick
September 15, 2015 at 4:25 pm #8749cmcgrath5035ModeratorLink?
I’d like to give a trySeptember 16, 2015 at 7:42 am #8750rtgallusMemberSeptember 16, 2015 at 7:47 am #8751rtgallusMemberSeptember 16, 2015 at 9:38 am #8752cmcgrath5035ModeratorGot it, thanks. I am off to try it on my machine.
FYI, I found that My issue was resolved by invoking a Gcode generator option to cut circles as two half arcs.
But I see that you have some full circles, so yours will be a good test.September 16, 2015 at 10:55 am #8753cmcgrath5035ModeratorYour job seems to run fine, but it is so large it is difficult to tell if there are issues.
In fact, looking at it it is not obvious that there are any single command circles – 360 degree arcs from a point back to that point.
Can you with “designer knowledge” identify any (by Gcode line number)?September 16, 2015 at 1:31 pm #8754rtgallusMemberCan’t find any in the file that I sent you but I did create a cw and ccw circle in cambam and they plotted in air just fine.
https://www.dropbox.com/s/x7zbwmehx60rpke/CW.txt?dl=0
https://www.dropbox.com/s/dz8mpsv3tz9w0je/CCW.txt?dl=0
Not sure if this will be of any help.
September 16, 2015 at 5:34 pm #8755cmcgrath5035ModeratorThanks.
Apparently, the implementation of full circle (360 degree ) arcs is highly non-standardized in the Gcode world.
If you look closely, you will see that in fact your files send two arc commands that comprise 360 deg.
That may explain why my gcode tool has an output option to break circles into two arcs, which does work for me.
So problem understood, if not completely solved.BTW: I found it amusing that my Gcode simulator imports your files with error – 3/4 of a circle and 1/4 of the circle arc incorrectly rotated! No wonder Alden is pulling his hair out with Arcs.
October 12, 2015 at 6:21 pm #8842cbeauvoisMemberHi,
Hardware: TinyG v.8.0, platform v.1.0
Firmware: Build 440.19, 440.20After upgrading from build 438.02 to 440.20 (and note, this also applies to 440.19), G2/G3 lines are no longer interpreted, i.e. these lines seem to just get skipped over, and no response is sent back from TinyG – Everything else seems to work fine, but no more arcs/circles 🙁
Example of simple file w/G2/G3 that seems to skip those commands:
https://www.dropbox.com/s/iulodjnlgf4i6kg/DoorButton.nc?dl=0Settings that worked for above file using build 438.02:
https://www.dropbox.com/s/ah6al649xlx6elf/10.9.2015.rtf?dl=0My two questions are:
1) How can roll back to build 438.02? Is the hex file available? Couldn’t find the branch on GitHub, or a hex file repo. If it’s available somewhere or someone still has it, would really help so I can get some jobs done until I figure out what’s going on.
2) What else can I provide to help debug this further?
Thanks *alot*.
October 12, 2015 at 6:50 pm #8843cbeauvoisMemberP.S. Just in case it’s useful, here’s a second file that also used to work; It cuts complete circles (using G3) while simultaneously lowering the Z axis to create a spiral:
-
AuthorPosts
- You must be logged in to reply to this topic.