Hi, I have a couple of questions, if you can help. Q1 - Is it possible with the controller to pause a job and issue a M9 gcode. I see there is a tool off option but this doesn't work whilst the job is paused ? I am operating a solenoid and would like the air feed turned off when pausing a job, is this possible ? Q2 - With the Acro 1515 should I see any belt sagging? The X gantry belt although tight, does show some sagging, but doesn't seem to affect the operation many thanks.
Negative: 4th bullet point of Grbl v1.1 Commands (That Grbl wiki sure is a must read) The Safety Door feature does stop tool and coolant though Picture of how much sag might be good, but normally belts should be tight, question is is it just a little sag as in its tight but gravity is still a thing, or its hanging like its not tight?
Thank you. Here's a picture of the sag. Yes the wiki is a good read, and its helping on most queries, just the odd one.... Re the Safety Door feature, is this something that can be hard wired into the Blackbox and effectively pause the machine as well as the coolant then ?
See docs:blackbox-x32:connect-door-sensor [OpenBuilds Documentation] - BlackBox X32 Docs are a good read too Belt might be able to go a little tighter. But on the larger ACROS with the belt underneath it will always have a little visible sag. If its not skipping pulley teeth under acceleration loads, or causing inaccuracies its good
Reading some forum posts around the door safety switch I may look at other options. Any issue you can see with simply connecting a 24V DC switch to the live feeding the 24V solenoid so I can manually turn off the solenoid. Plan is to pause the machine and flick the switch to turn off solenoid ?
From what I read, its changing firmware, moving jumpers and installing switch, but they could have been old posts also. Wasn't quite sure then if I could just pause the Acro and cooland/solenoid would stop, and on resume the coolant/solenoid would start again.... Got the machine running well now and hesitant to break it with too many further changes, if you see what I mean, thanks.
I do! Sleep easier: Backup now! CONTROL > Grbl Settings tab > Backup Settings > and store that backup where you will be able to find it when you most need it! Label it clearly, add yourself some notes on what state the machine is in at this time. No jumpers even But for reference: 1) CONTROL > Wizards and Tools > Firmware Flashing Tool 2) BlackBox X32 tab > Machine Style > 2/3Axes with Door Switch > Flash 3) Wire switch as shown in docs:blackbox-x32:connect-door-sensor [OpenBuilds Documentation] That's about it Door switch does - its made for use with OpenBuilds Modular Enclosure System - open the door, tool stops, coolant stops. Close door, click Resume in CONTROL (safety reasons it doesn't resume on door close, you do need to click Resume) and it turns on coolant and tool as per your configured delays, then resumes movement
Oh not as tricky as I thought, but some of the threads were from 2017 ! Is there a recommended switch ?
Our usual Xtension Limit Switch Kit as shown in docs:blackbox-x32:connect-door-sensor [OpenBuilds Documentation] BlackBox X32 was released in Dec 2022 But mind you, also didn't have a Door jumper or anything much more difficult than now
Works a treat now ! Only other issue is that the stop job button doesn't turn off coolant, is this a firmware setting ? thanks
Will see if I can replicate, should work. Just double checking you are CONTROL V.1.0.375 or newer and flashed with that version? (so we use Same for test)
Yes on 1.0.376. I also notice sometimes the grbl tab dissappears, seems to come back, but cant work out why its not there....even though connected to Blackbox.
If you connect with the "door open", it might not pull the settings (controller locked because door is open) It can't really disappear when its been created (On connection, we send $$, when the settings comes back from the controller, we create the tab with it. It only gets recreated when you save Grbl settings or do a refresh. So if its not showing, it means we werent able to pull the settings dump with $$ at connection time, with a door switch installed, most likely controller was not in Idle state at time of connection) Will test. Thanks
OK so running V1.0.376 Flashed the DOOR firmware Reconnected to BlackBox X32 (Running [14:07:32] [ $I ] [VER:1.1f.20240402:acro1515] ) Started a job with M8 in the header Code: G17 G20 G90 G0Z0.8000 G0X0.0000Y0.0000 M8 M3S18000 G4 P1.8 G0X2.2851Y2.3598Z0.2000 G1Z-0.1875F30.0 G1X2.2758Y2.3612F60.0 G1X2.2664Y2.3598 G1X2.2583Y2.3559 G1X2.2517Y2.3498 G1X2.2470Y2.3422 G1X2.2448Y2.3335 G1X2.2453Y2.3239 G1X2.2483Y2.3156 G1X2.2537Y2.3084 G1X2.2609Y2.3030 G1X2.2693Y2.3000 G1X2.2791Y2.2995 G1X2.2879Y2.3017 G1X2.2956Y2.3064 ................... and more Coolant came on and move started Waited a couple seconds Hit Stop Coolant turns off just fine
No, still does it for me. Went back to no door switch firmware, disconnected switch and does it on that also. Pressing home, does however turn off coolant.
Not really, I cut it down to code just containing M8, then G1 Coordinates. The coolant is controlling a solenoid valve, 24V which has led on it so I can see when power on/off ..... Still getting grbl tab going missing...
ok, still working on grbl tab one, will update when replicable. On coolant issue. Have done further testing.... Code very basic G0 X.... Y.... M8 G1 X..... and so on Stop button, coolant stays on. Whilst in stopped position, Tool Off Button does nothing, M9 on console does nothing. However Tool On, then Tool Off stops coolant as does M8 first then M9. Home All and Abort, both stop coolant.
Any more thoughts on this Coolant off issue, could I have a faulty Blackbox and how do I report it ? thanks
Mainly waiting on some replication information, so we can replicate it. If the mosfet had burned out - it have been stuck in always on or always off - its still switching off for you on some other actions, so its more procedural, software, firmware at this time. Burned out mosfet would also have been excludedeven if it was Do post the full file so we can test with the same Also grab the bootup log from your firmware, and Grbl Settings backup
