Dialog 11, Radius Deviation Too Large gcode made by Featurecam. How can I solve this?
Close
Login to Your Account
Results 1 to 10 of 10
  1. #1
    Join Date
    Mar 2016
    Country
    CANADA
    State/Province
    Ontario
    Posts
    102
    Post Thanks / Like
    Likes (Given)
    21
    Likes (Received)
    12

    Default Dialog 11, Radius Deviation Too Large gcode made by Featurecam. How can I solve this?

    Dialog 11 on a Deckel FP50CC/T

    I am breaking free of manually writing CAM and am having trouble. I have done a few CAM programs and wrote a few post processors, but am now branching into using an old version of Featurecam. I have been spending some time converting a Dialog 4 post processor to Dialog 11. It currently runs cycles, arrays of holes, and standard moving operations.

    I am consistently having "Radius Deviation Too Large" when I test it on the Deckel. On other machines which had this error I forced the CAM to not do curves and do straight lines, but those cases I was using a modern computer to drip info and a different CAM program. I don't know how to force Featurecam to make straight lines.

    Below is the g-code start. It is hung up on N120.

    Code:
    % 111*%
    [ MADE IN FEATURECAM ]
    N20 G17
    N25 M6 T001
    
    [ ROUGH1 POCKET POCKET1 ] 
    N35 G0 Z10 
    N40 G0 X0.2835 Y-1.0 F25 S+2482
    N45 G0 Z1.0
    N50 G0 Z-0.15
    N55 G1 Z-0.24 
    N60 Y0. Z-0.3129 
    N65 Y-1.0 Z-0.3857 
    N70 Y0. Z-0.4586 
    N75 Y-1.0 Z-0.5314 
    N80 Y0. Z-0.6043 
    N85 Y-1.0 Z-0.6771 
    N90 Y0. Z-0.75 
    N95 G3 X0.2835 Y0. I-0.2835 J0. F50
    N100 G2 X0.3325 Y0.308 I0.9931 J0.
    N105 G3 X0.1912 Y0.5861 I-0.2097 J0.0684
    N110 X0.4864 Y0.3788 I-0.1912 J-0.5861
    N115 X0.0495 Y0.7843 I-1.4665 J-1.1421
    N120 X-0.5465 Y0.7764 I-0.2923 J-0.4393
    N125 X0.0708 Y0.9469 I0.5465 J-0.7764
    N130 G2 X-0.3734 Y1.0522 I0.108 J1.4452
    N135 G3 X-0.8246 Y0.9823 I-0.1679 J-0.4073
    .....
    I am currently unsure of how to fix this. Most post relating to Featurecam link to HSM, which has a different post processor format (.cps vs .cnc). What do other people do to make CAM for their Dialog 11s?

  2. #2
    Join Date
    Feb 2001
    Location
    Redwood City, CA USA
    Posts
    4,990
    Post Thanks / Like
    Likes (Given)
    184
    Likes (Received)
    917

    Default

    Autodesk has a post for Fusion 360. Maybe take a look at that. I have no idea whether it is any good. Their Fusion post for Dialog 4 needed a lot of work to make it work. I guess nobody QCs this stuff.


    Sent from my iPhone using Tapatalk

  3. Likes Vitran liked this post
  4. #3
    Join Date
    May 2002
    Location
    South Central PA
    Posts
    13,617
    Post Thanks / Like
    Likes (Given)
    2280
    Likes (Received)
    3535

    Default

    A shot in the dark here because I don't know Featurecam or D11 - I had obscure errors on circle quadrants long ago on an Acramatic control with smartcam and edgecam, It turned out to be the endpoint of one arc was not close enough to the beginning point of the next arc or line, The arc centers and angles and radii varied just enough that the endpoints were far enough apart that the control couldn't make the leap to join them - something on the order of .001". This sort of sounds similar. I found it by reverse engineering the G code line by line. I resolved it by forcing the code accuracy to a closer tolerance.

  5. Likes Vitran liked this post
  6. #4
    Join Date
    Dec 2002
    Location
    Benicia California USA
    Posts
    8,141
    Post Thanks / Like
    Likes (Given)
    1844
    Likes (Received)
    2472

    Default

    Think Rich is correct.
    Supplied posts are usually pretty poor ...Program makers are depending on the user being current and they will "tune" the post to your needs. Program out of maintenance and you are on your own.

    Don't know about your CAM or specifics to Dialog 11, but would try and insert a G64 at the program beginning. In D4 this is a modal command...which will cause the control to "blend" the contours so that exact start and end points are averaged...might help here.
    Have no idea if the D11 uses this , works to eliminate herkey,jerkey moves on the D4....

    Cheers Ross

  7. Likes Vitran liked this post
  8. #5
    Join Date
    Mar 2016
    Country
    CANADA
    State/Province
    Ontario
    Posts
    102
    Post Thanks / Like
    Likes (Given)
    21
    Likes (Received)
    12

    Default

    I tried a G64 but no luck so far. I have used it before when I was doing a large contour map.

    I'll do some searching to see if there is a way to increase the tolerance in Featurecam. See if I can get six decimal place accuracy so the Deckel can round it the way it wants.

  9. #6
    Join Date
    Oct 2012
    Location
    Austria
    Posts
    169
    Post Thanks / Like
    Likes (Given)
    14
    Likes (Received)
    42

    Default

    I faced this problem with an old version of HSM on a dialog 4 control.It was occuring only in "adaptive clearing" method of cutting where optimal movements are selected by the CAM.On a chat I had with a programmer he suggested tunning the program tolerances and accuracy on the settings.This is not so bad, because its a roughing method.

  10. #7
    Join Date
    Feb 2001
    Location
    Redwood City, CA USA
    Posts
    4,990
    Post Thanks / Like
    Likes (Given)
    184
    Likes (Received)
    917

    Default

    Quote Originally Posted by Vitran View Post
    I tried a G64 but no luck so far. I have used it before when I was doing a large contour map.

    I'll do some searching to see if there is a way to increase the tolerance in Featurecam. See if I can get six decimal place accuracy so the Deckel can round it the way it wants.
    In Dialog 4, G64 only works within G41/G42 cutter radius compensation in the control. In Fusion or HSM, if you choose compensation in the computer, rather than the control, G64 won't apply. In HSM, compensation in the control (G41/G42) is only applied during finish passes, not during clearing. That's why I can write much nicer-acting D4 code by hand than what comes out of Fusion, but that is time-consuming to say the least.

  11. Likes AlfaGTA liked this post
  12. #8
    Join Date
    Mar 2016
    Country
    CANADA
    State/Province
    Ontario
    Posts
    102
    Post Thanks / Like
    Likes (Given)
    21
    Likes (Received)
    12

    Default

    Thanks for the help, but still no luck yet.

    I laid out the rotation and it is wrong. It does an arc from X3.38785 Y3.25 to G3 X3.37286 Y3.46373 I-1.53030 J0. By doing the equation by hand and on the computer, it should be I-1.531195, a difference of almost a thou.

    Seems an issue in the calculator or the precision of the arc fitting. Not sure what I can do to make it up. May mean I can't use Featurecam if I can't do an arc.

    I did make it partly work, but I think I broke it too. I changed the G values from XYIJ to XYR and that works. Issues come that it has the same spot twice with a radius at the start and end of every block of code. Wait, now that I think about it, it must be making a circle to come back to itself. Crud.

  13. #9
    Join Date
    Mar 2016
    Country
    CANADA
    State/Province
    Ontario
    Posts
    102
    Post Thanks / Like
    Likes (Given)
    21
    Likes (Received)
    12

    Default

    I was dreaming last night and I found the cause of the issue, however unsure why it showed up. I tested it this morning and it worked like a charm.

    The Dialog 11 controller, for arcs, is G2/G3 X# Y# II/A# JI/A# where A is for absolute and I is for incremental. The post processor for the Dialog 4, which I based my code off of, did not have this A or I. Without the I or A, the processor will assume absolute, resulting in the error in the code.

  14. #10
    Join Date
    Dec 2002
    Location
    Benicia California USA
    Posts
    8,141
    Post Thanks / Like
    Likes (Given)
    1844
    Likes (Received)
    2472

    Default

    Good catch...
    If you are programming off a CAM system don't think that having the option to use the "switch" to define the circle center is of any value..just go with running everything absolute....

    Now i can see times where having the choice on the center definitions would be nice for some hand coding...
    Cheers Ross


Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •