An example

Home › Forums › TinyG › TinyG Support › An example

Viewing 5 posts - 16 through 20 (of 20 total)
1 2
  • Author
    Posts
  • January 28, 2014 at 6:15 am #5298
    tomking505
    Member

    I’d like to have the offending gcode myself. But when it happened, I was more worried about solving the problem, and continued playing with settings in CamBam until I got it to work sufficiently. That over wrote my gcode with something that worked. Sorry.

    In CamBam, I slightly adjust depth increment and stepover, which don’t change the finished product, just the way it routes.

    I know that is no help. Sorry about that. When it happens, I just see red and work the problem.

    • This reply was modified 10 years, 9 months ago by tomking505.
    January 28, 2014 at 7:25 am #5300
    psyko
    Member

    @alden I’m running 380.05.

    I’ll try to find GCode that causes the issue. Infortunately, I’m not close to my workshop now…

    January 28, 2014 at 7:35 am #5301
    alden
    Member

    It will be good to check this out. Thanks for the help.

    January 30, 2014 at 6:42 pm #5319
    tomking505
    Member

    I may have a clue to why my machine moves strangely after a Coolterm cancel.

    I just got the same behavior, except I got a curve error. Backtracking it makes me think Coolterm is halting exactly when you hit the cancel button. It doesn’t halt after it sends a return, as I assumed. If true, Tinyg only receives part of a command. When I manually enter a command and hit enter, Tinyg sees the partial command plus my command, and tries to do something with it.

    I would prefer to use TGfx. The hold button works much better for halting a job. But I still cannot update the firmware on either of my TinyGs.

    Tom

    • This reply was modified 10 years, 9 months ago by tomking505.
    February 2, 2014 at 8:09 pm #5326
    tomking505
    Member

    Confirmed.

    I just cancelled a job to TinyG sent through CoolTerm. Half-way through the job, I could see my speed was too high, so I pressed ‘cancel’ on the CoolTerm dialog.

    Just to test the thing, I pressed return only. Tinyg said:

    tinyg [mm] err: Arc specification error: G2 X83.852 Y66.

    You see the decimal part of the Y was cut off. CoolTerm apparently stops dead in it’s tracks, midway through a send. So only part of the command is sent.

    If, for example, CoolTerm sent two fewer characters, when I hit return, it would have sent a Y6, which would have smashed through what I was working on.

    By the way, the “flush serial port” command in CoolTerm didn’t help. I did that before hitting a return. 🙂

    I will update the Wiki to note this behavior.

    Tom

  • Author
    Posts
Viewing 5 posts - 16 through 20 (of 20 total)
1 2
  • You must be logged in to reply to this topic.