Welcome to Our Community

Some features disabled for guests. Register Today.

Ramming into the stops

Discussion in 'Controller Boards' started by Lee Dorman, Mar 3, 2024.

  1. Lee Dorman

    Builder

    Joined:
    Feb 9, 2024
    Messages:
    6
    Likes Received:
    0
    A little background: I am very new to the cnc world. I bought an open builds cnc that a guy had built custom but never finished it. I purchased the blackbox x32 and the openbuilds interface as well as the power supply bundle from open builds to get everything up and running and up to date. Everything is wired per open build's specs for the limit switches as well as the stepper motors. I did reverse the y2 motor at the black box input. Everything works perfect. It jogs beautifully, homes perfect with no issues. The table size is 37 9/16" wide (x axis) by 59" wide (Y axis). I manually cut a very shallow box with a 90 degree V bit to get the size of the actual usable cutting area so I knew what size to make the fly cut. I made a simple rectangle cutting path in Vcarve pro for the fly cut and not matter what size I make it or where I put the reference datum point (center of table or one of the corners) when I start the program, everything begins like it should exactly as it showed on Vcarve. It goes to the reference datum point then it just slams into the mechanical stops at the Y- and X+ corner of my table. I pretty positive the post processer is correct as I selected the open builds post from the drop down menu on Vcarve. There are no errors coming up other that the you hit a limit fault when it slams into the corner of the table. Any thoughts on what the issue could be and or how to go about fixing it? Thanks for any input y'all have. One thing I did notice when I used the post processor inch version everything at least went in the correct direction. When I tried the mm version the gantry tried to go in the opposite direction when I started the program.
     
  2. Peter Van Der Walt

    Peter Van Der Walt OpenBuilds Team
    Staff Member Moderator Builder Resident Builder

    Joined:
    Mar 1, 2017
    Messages:
    14,051
    Likes Received:
    4,123
    1) use Troubleshooting tab to test switches (all working, and plugged into correct axis?)
    2) did you remember to enable Hard Limits in Grbl Settings

    As for the gcode, make sure you have the correct Post, docs:software:vectric [OpenBuilds Documentation]

    And make sure machine is calibrated and reliable (no slipping, binding, stalling etc)
     
  3. Lee Dorman

    Builder

    Joined:
    Feb 9, 2024
    Messages:
    6
    Likes Received:
    0
    I looked at everything per your suggestions and the post is correct and up to date in vectric. I'm using the openbuilds interface to do everything at the CNC. How can I calibrate the machine or set where the hard limits are? I can only turn them on and off in the interface.
     
  4. Peter Van Der Walt

    Peter Van Der Walt OpenBuilds Team
    Staff Member Moderator Builder Resident Builder

    Joined:
    Mar 1, 2017
    Messages:
    14,051
    Likes Received:
    4,123
    Use a computer > CONTROL > Wizards and Tools > Calibration menu

    You can set where to Home to, but limits are all checked without discrimination once enabled. Thus on/off only. No need to tell it where a limit is. If any limit is hit its stopping.

    Do read the Grbl Wiki to understand all this stuff: Home

    Read all the pages, all have golden info
     
  5. Lee Dorman

    Builder

    Joined:
    Feb 9, 2024
    Messages:
    6
    Likes Received:
    0
    So here's where things are at currently. I have downloaded the openbuilds control software to my desktop as well as downloaded and installed the required drivers. I connect my desktop to the black box x32 and got it to connect on the control software and did the calibration on all three axis. The original issue is still happening no matter what I do with the gcode from Vcarve. I've change the reference datum point from the center of the cnc table to the center of the cutting area to the corners and every time when the program is ran the cnc moves to the starting point exactly the starts towards the actual cutting start point and just rams in to the mechanical stops on the cnc. I've tried changing the size of the rectangle cutting path that I created on Vcarve and the same results. I have to be missing something but I have no idea what it would be. Any advice at this point?
     
  6. Peter Van Der Walt

    Peter Van Der Walt OpenBuilds Team
    Staff Member Moderator Builder Resident Builder

    Joined:
    Mar 1, 2017
    Messages:
    14,051
    Likes Received:
    4,123
    Are you using the correct Post Processor yet?

    Please post a Grbl Settings backup for review too? (CONTROL > Grbl Settings tab > Backup Settings button)

    Please post an example gcode file that does the bad moves too for review
     
  7. David the swarfer

    David the swarfer OpenBuilds Team
    Staff Member Moderator Builder Resident Builder

    Joined:
    Aug 6, 2013
    Messages:
    3,288
    Likes Received:
    1,837
    you don't mention it so lets check, you are jogging to the point on the material that you indicate din the CAM is the 0,0,0 point and clicking the 'setZero' buttons to tell the controller where to start, right?
     
  8. Lee Dorman

    Builder

    Joined:
    Feb 9, 2024
    Messages:
    6
    Likes Received:
    0
    Yes. I have set zero at the center of the CNC table itself as well as the center of the actual cut area and the top corners of the cut area and same result.
     
  9. Peter Van Der Walt

    Peter Van Der Walt OpenBuilds Team
    Staff Member Moderator Builder Resident Builder

    Joined:
    Mar 1, 2017
    Messages:
    14,051
    Likes Received:
    4,123
    Don't forget to add details as requested
     
  10. Lee Dorman

    Builder

    Joined:
    Feb 9, 2024
    Messages:
    6
    Likes Received:
    0
    The post processor I'm using is the openbuilds blackbox 32 inches from the drop down menu on vcarve. I've tried the mm version as well with same results. One thing to note from this morning when I plugged in the blackbox and tried to connect to the openbuilds control I got the error that there was no supported firmware detected, port closed. This past Thursday I flashed the blackbox with the flashing tool on the open builds control so it lost the firmware after I turned everything off after caliberating it that evening. I flashed it again today and after it connected to the control software so the grbl settings may not be the same that I'm sending you today. I'm not smart enough on this to know if it is or not. I have attached a screen shot of the error that I was getting before I had to flash the box again today as well as the grbl back up and the gcode that I used on the last attempt. Thanks for the help.
     

    Attached Files:

  11. Peter Van Der Walt

    Peter Van Der Walt OpenBuilds Team
    Staff Member Moderator Builder Resident Builder

    Joined:
    Mar 1, 2017
    Messages:
    14,051
    Likes Received:
    4,123
    Stop reflashing, and read the onscreen error. It directed you to docs:blackbox-x32:faq-usb-connection-failed [OpenBuilds Documentation]

    Fix whatever is causing the shorts / brownout while there is still a Blackbox to save. If it dies it won't be covered under warranty. Note FAQ says nothing about reflashing. Firmware cannot magically disappear
     
  12. Lee Dorman

    Builder

    Joined:
    Feb 9, 2024
    Messages:
    6
    Likes Received:
    0
    I did go to the link and followed everything on it. I flashed it on Thursday evening because it was the only thing I could think of let to do because every time I tried to connect the open builds control to the black box that error came up. I tried it on two different computers with multiple different usb cords and still got the error. I know it doesn't say anywhere in the trouble shooting or FAQ's to flash it but that was the only thing left I could do to try to see if it would work and it did. I get it that software and firmware doesn't just disappear unless it is manually deleted but for some reason the firmware is not staying in place or is corrupted from Open builds because that's where it's coming from. I don't know how to fix whatever is causing the shorts / brownout that you are saying it apparently has. It never crossed my mind that there was a short some where because there wasn't a power issue. I don't even know what brownout is. Steps I can take to start trying to do that without voiding the warranty would be greatly appreciated. Can we get on a phone call and share my computer screen with you so you can go through things to see what is going on and try to get this figured out or is the forum the only way to do this?
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice