|
|
Post by mundo161 on Mar 25, 2023 0:46:40 GMT
I am doing the initial set up on my machine. When I jog the X,Y and Z axis the alarms trigger and stop the movement of the machine as they are meant to do. When I do "home machine" trial it runs through the alarm switches like they aren't even there. The Z switch works as it should during the homing process. Any thoughts?
|
|
|
|
Post by bLouChip on Mar 25, 2023 4:04:54 GMT
what model machine are you using ?
how much experience do you have with CNCs, grbl, and gcode ?
what alarm codes are you getting ?
Please post the console results of $i, $$, $# and $g commands, the results will help us diagnose the problem.
|
|
|
|
Post by mundo161 on Mar 25, 2023 11:49:32 GMT
I have a mega v standard. I am brand new to all of this. I am not getting any alarms when doing machine home. It literally doesn't stop when it hits the switches, I have to turn the machine off/unplug it to get it to stop running. I get the alarms in jog mode but home mode doesn't alarm
|
|
|
|
Post by mundo161 on Mar 25, 2023 15:40:20 GMT
I just got home and redid the run. It did the same thing so I had to turn the machine off and back on. This is the alarm that came up on the screen:
[ERROR]An error was detected while sending '$H': (ALARM:6) HOMING FAIL. The active homing cycle was aborted. Streaming has been paused.
[ERROR] Error while processing <ok>: An unexpected command was completed by the controller.
GRBL1.1i Mega V 4 Axis Router ['$' for help]
>>> $$
[MSG:Check limits]
[MSG:'$H'|'$X' to unlock]
$0 = 10 (step pulse time, microseconds)
$1 = 255 (Step idle delay, milliseconds)
$2 = 0 (step pulse invert, mask)
$3 = 2 (step direction invert, mask)
$4 = 0 (invert step enable pin, boolean)
$5 = 0 (invert limit pins, boolean)
$6 = 0 (invert probe pin, boolean)
$10 = 1 (status report options, mask)
$11 = 0.020 (junction deviation, millimeters)
$12 = 0.002 (Arc tolerance, millimeters)
$13 = 0 (report in inches, boolean)
$20 = 0 (soft limits enable, boolean)
$21 = 1 (Hard limits enable, boolean)
$22 = 1 (homing cycle enable, boolean)
$23 = 1 (homing direction invert, mask)
$24 = 50,000 (Homing locate feed rate, mm/min)
$25 = 800.000 (Homing search seek rate, mm/min)
$26 = 200 (homing switch debounce delay, milliseconds)
$27 = 5.000 (homing switch pull-off distance, millimeters)
$30 = 100 (maximum spindle speed, RPM)
$31 = 0 (minimum spindle speed, RPM)
$32 = 1 (laser-mode enable, boolean)
$100 = 57.288 (x-axis travel resolution, step/mm)
$101 = 57.288 (y-axis travel resolution, step/mm)
$102 = 200.000 (z-axis travel resolution, step/mm)
$103 = 13.333 (A-axis travel resolution, deg/mm)
$110 = 16510.000 (x-axis maximum rate, mm/min)
$111 = 16510.000 (y-axis maximum rate, mm/min)
$112 = 4570.000 (z-axis maximum rate, mm/min)
$113 = 15000.000 (A-axis maximum rate, deg/min)
$120 = 1470.000 (X-axis acceleration, mm/sec^2)
$121 = 1470.000 (Y-axis acceleration, mm/sec^2)
$122 = 700.000 (Z-axis acceleration, mm/sec^2)
$123 = 4000.000 (A-axis acceleration, mm/sec^2)
$130 = 900.000 (X-axis maximum travel, millimeters)
$131 = 900.000 (Y-axis maximum travel, millimeters)
$132 = 100.000 (Z-axis maximum travel, millimeters)
$133 = 360.000 (A-axis maximum travel, deg)
ok
>>> $G
[GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]
PK
|
|
|
|
Post by bLouChip on Mar 25, 2023 18:53:17 GMT
Ok, so a couple observations on the data... 0.1) save your factory grbl config settings using UGS Machine->Firmware Settings->Export command. 1) unrelated to this issue but can cause other issues during normal ops later, I recommend you configure Hard Limits off, so $21=0, Soft Limits on $20=1. Hard Limits can cause false trips due to EMI/RFI on the signal wires in Mega V config with limit switches wired Normally Open, and in case of just using homing switches, its only 1/2 the protection anyway, the other end of the axis is not limit switched. Basically, if Hard Limits are on, then grbl is always watching in alarm mode for the switch to make (including noise), but it HL is off, then grbl just looks for the switches when Homing. Soft Limits prevent you from moving past the limits at both ends, grbl does the math limit test for each motion command, it knows the axis length and current position (sort of) after homing. 2) slow down the rapid speed and acceleration/deceleration, its easier on the machine wear and tear, easier for you to catch a possible errant move. In the case of slower accel/decel rate, the machine will have much less mechanical resonance shaking it with each start and stop motion. I recommend $110, 111 = 8000, $120, 121 = 800, issue the 4 commands separately to grbl on the console command line. When you get to the point of doing a long running job (> 60 mins or so) then put the max factory values back if you like, at least the max speeds if not accel/decel.
3) To allow for a little more room at end of axis travel before crashing, I adjust my max axis dimensions down a bit, I run $130=890, 131=785 (I have a fixture at front of work area bed), and 132=88. If you are using rotary, consider $133=2160 (6 revolutions or some other multiple of 360).
Now to your homing issue... 1) please verify: Your config values look std for MegaV, thus XY switches should be back left corner, Z should be top. 2) please verify: after you connect your MegaV control box USB to computer, your computer is powering up the Arduino board inside. You don't need to power on the control box yet via the EPO switch, leave it off for now. Now "make" each homing switch one at a time with your hand and while watching the UGS DRO (Digital ReadOut) window, normally bottom left of UGS screen where XYZ coords are given. When each switch is "made", then you should see the corresponding "Alarm [XYZ]" indicator light up in red text. If you see these indicators before "making" a switch, then it means you have that switch wired Normally Closed instead of Normally Open. To orient the switch, the post opposite side of the actuator is Common (black wire), the next post is Normally Open (red wire). Look closely on the switch body, it gives the contact diagram.
If you haven't been able to correct the issue with switch wiring or having a swapped connection to the control box, then you'll need to unplug the aircraft connectors for each switch at the control box and check each wire continuity with an ohm meter or test light. Assume the control box is wired and labled correctly by MillRight.
If the wiring checks out, post your verification and other results, but you'll likely need to contact support@millrightcnc.com for additional diag and instruction.
The MillRight version on the Resource page is very stale, it was built by them for 4 Axes support before github version had such.
Here are some good links to have handy for grbl and gcode...
|
|
|
|
Post by mundo161 on Mar 25, 2023 23:22:53 GMT
So I down loaded the link to github. That version is not giving me the ability to refresh the portal to find my machine.
|
|
|
|
Post by bLouChip on Mar 25, 2023 23:26:02 GMT
right-click on the toolbar and select "Connection"
|
|
|
|
Post by mundo161 on Mar 25, 2023 23:39:26 GMT
Nothing happening its already checked. Trying to send a pic but this thing keeps telling me that everything is too big to attach GRRRRR I appreciate your patience and help
|
|
|
|
Post by bLouChip on Mar 25, 2023 23:45:57 GMT
re. UGS V2.0.12, best not to worry about that right now, I was just advising of the version I use in case the DRO in your version did not display the Alarm status of switches. It appears your Z limit switch is operating correctly, so try it first. You should be able to revert to using the MillRight version of UGS and we can resume diag of the homing switches.
|
|
|
|
Post by mundo161 on Mar 25, 2023 23:54:18 GMT
So I switched back. I don't know where to rewrite the code suggestions that you made.
|
|
|
|
Post by bLouChip on Mar 25, 2023 23:56:33 GMT
best if we chat on the phone, check your DMs.
|
|
|
|
Post by bLouChip on Mar 26, 2023 2:32:11 GMT
mundo161 and I got on the phone to discuss his homing Alarm6 problem. I'm not able to help him definitively because the grbl configuration settings are locked on his MegaV and the message indicates MR Support needs to unlock it.
He's writing MR Support to request assistance.
Here's what we could do though... 1) Z is homing correctly, however XY crash into the homing switches causing the eventual Alarm6, which is: [“ALARM:6” : _(“Homing fail. Reset during active homing cycle.”)], according to: domoticx.com/cnc-machine-grbl-error-list/
2) the X and Y homing switches seem to be adjusted correctly so the actuator "makes" the switch well before the switch body is in peril of collision. And the homing switches are wired correctly and do indicate the correct axis in UGS when manually activated. In fact, when the MV attempts to home, after Z homes correctly, a manual activation of X and Y cause the normal 800mm/min grbl switch search to cease and respond with motion of backing out 5mm to initiate the slow 50mm/min home seek; this does not occur in normal operation of homing on this machine, rather its the crash into the switches during 800mm/m search and Alarm6 is thrown. I seem to recall this condition once or twice on my machine long ago, and I fixed it with increasing the $26 value to 250ms, the debounce delay value. This errant case is 200ms factory setting. So because the grbl config settings are "locked", they can't be changed without a magic unlock code other than $X, according to the message thrown when we attempt to $26=400 or anything else or any other $nn setting.
3) the factory config for X and Y axis maximum travel does not match the model, he has a 19"x19" MV yet the $130, 131 values are 900mm (35" MV XL model), so MR Support needs to unlock for this setting too.
Other than that, it works great 
|
|
|
|
Post by bLouChip on Mar 26, 2023 3:04:08 GMT
I found this post in the forum that perhaps explains how to "unlock grbl configuration settings" when using the MillRight UGS version... i figured it out. I had to unlock the settings (Tools, options, UGS, Sender Options, and then uncheck the "Settings Locked" button), then i changed my $27 to 10mm to start. that fixed my offset issue. I have since started backing it down just to see how close I can get and am able to get it to work at 6mm without an issue. For reference, it was set at 5mm from Millright. thanks for helping me find some stuff to look at! Andy So after unlocking the "Settings Locked" button in UGS, you should be able to issue $26=400 to bump up the homing debounce delay and see if that fixes the Alarm6 homing problem. I use a 400ms debounce delay on my probe switch so these switches can need that much time. I use 250ms for homing debouce delay, the setting I'm suggesting you change from 200 to 400, let's just give it plenty of time.
I suspect the "Settings Locked" "feature" is only in the MillRight version of UGS, its not been in any of the github versions that I've been using since day 2 of my MegaV period  |
|
|
|
Post by mundo161 on Mar 27, 2023 20:11:37 GMT
Thank you to Millright tech support for helping me get this fixed. I apparently had the switches backwards on the frame x-switch where the y-switch should have been and vice versa. Swapping out the 2 switches fixed it instantly!! Thanks again Millright and Lou for the effort you put in trying to help me with this as well, all of it is greatly appreciated!!
|
|
