Extra Steps?

Home › Forums › TinyG › TinyG Support › Extra Steps?

Viewing 6 posts - 16 through 21 (of 21 total)
1 2
  • Author
    Posts
  • November 10, 2011 at 10:02 pm #1475
    rainbow_lazer
    Member

    ah, so close and yet so far! Here’s what’s up:

    -Figured out that the current pot was actually labeled, just very tiny-ly. I’ve got the current set just below the point where the motors will pulse from thermal shutoff.

    -I changed the JM for each axis to 3000 [inches]. I’ve left it there, as I’m not entirely clear on what this setting does.

    -I dropped the SR/FR for X and Y to a pretty conservative 61ipm/60ipm, respectively. All three axes run really nicely with individual, manual G-code commands (G0 and G1).

    -The bad news: When I go to run a whole G-Code file, I’m missing steps in X and Y. The strange thing is, it’s in a very consistent pattern; ie the same file will run incorrectly the same way multiple times. Here’s a sample that I tried (should be a 1″x1″ square pocket), and the result after running it twice.

    I’ve tried dropping the SR/FR settings, but no change in misstepping. I’m wondering if this could be a problem with the way CoolTerm is feeding in the file? Otherwise I’m stumped for troubleshooting.

    November 11, 2011 at 7:56 am #1476
    alden
    Member

    Are you running coolterm Mac or Coolterm windows? We very recently found something that might be a bug on the windows version. The Mac version (1.4x+) works fine. NB: Xon must be enabled in both Coolterm and in TinyG. It’s the default for TinyG. It’s not for Coolterm. There are also some Pythons scripts we should post that can spool the file if this is a problem. So there are alternatives if you are on Windows Coolterm.

    Can you tell me where in the file if has a problem? TinyG will handle line numbers, so if PartKam can generate them it’s easier to diagnose things if they are present.

    I’ll try the file over the weekend. Are you planning to be around over the weekend? I’d like to short-cycle this with you if we can.

    November 11, 2011 at 3:49 pm #1477
    rainbow_lazer
    Member

    Alden, I’m using Mac Coolterm. I’m not sure about line numbering in Partkam, although it’s a short enough file where I could hand-code them.

    I agree on short-cycling… Let’s try to tele-meet over the weekend. I’ll be working the rest of today, tomorrow and Sunday from 11am Pacific til late-at-night Pacific. Maybe we can do a g+ hangout?

    November 11, 2011 at 4:10 pm #1478
    alden
    Member

    I’m going home soon and am going to try running your pocket code before I have go go out tonight.

    I’ll be around most of the day Saturday. We can do a hangout, or we could set up to connect on gchat and use a video call. I’ll send you my gmail addr off list.

    November 11, 2011 at 5:57 pm #1479
    alden
    Member

    Chris, I ran the pocket cutter file on the Lumenlabs and the Zen and they both worked w/o incident. Let’s pick it up on Sat and find out what’s going on. Ping me when you are ready to start and we can get online. I’ll be in in the AM and can get started as early as you can stand. Don’t worry about waking me up.

    November 13, 2011 at 9:45 am #1480
    alden
    Member

    Chris – I found and fixed the issue we encountered yesterday. The drift in non-power mode axes has been eliminated. I will post on github as 0.911. I’m around today to try it out. Ping me if you want to test. – Alden

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