codebuster

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • September 15, 2016 at 4:00 pm in reply to: Any examples of two or more TinyG with SPI or RS485? #9912
    codebuster
    Member

    Can I bump this topic? Let us test – Can someone please document this or provide some guidance on how to get TinyG talking in RS485? What header does it even transmit over on the TinyG v8h, J14, J15?

    July 10, 2016 at 12:47 pm in reply to: Why is G38.2 done in machine coordinates? #9835
    codebuster
    Member

    Yes, it’s a file built from the edge branch, where the header file that determines the $fb is on 449.01.
    I can do that. Hopefully it will bring to their attention the need of work coordinate systems by machinists talking about this on both this forum, their github, and the chilipeppr community.

    July 9, 2016 at 9:13 pm in reply to: Why is G38.2 done in machine coordinates? #9833
    codebuster
    Member

    Has the code for G38.2 been adapted to use G10 L2 coordinate systems in the v .98 branch? I sent an email regarding build 449.01 of v.97 edge and haven’t received a reply yet.

    I figured it would be some kind of problem with this. Are there any ideas on how to use the new homing limit switch type from build 449.01 ($zsn=4 probe) with a manual cycle? This might be made a lot easier with canned cycles and a description of the functionality of this switch type than trying to bottle it up into a single G code command.

    Also, the SpDir won’t flash when the machine goes into Alarm mode from a limit switch hit, dunno if that’s related.

  • Author
    Posts
Viewing 3 posts - 1 through 3 (of 3 total)