Hey, guys. I've attached some images of an issue I'm currently experiencing in addition to my GRBL settings. What is happening is that the mill is just stopping, sometimes with error, sometimes without. I thought maybe a limit switch was being triggered, but there is no alarm. Any advice would be greatly appreciated. Here is a link to the images. Here is the "more details" tab on the error: "See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary. at System.ThrowHelper.ThrowKeyNotFoundException() at System.Collections.Generic.Dictionary`2.get_Item(TKey key) at GrblPanel.GrblGui.showGrblStatus(String data) at GrblPanel.GrblIF.raiseAppSerialDataEvent(String data) at GrblPanel.GrblIF.VB$StateMachine_40__client_ComReadData.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.8.4470.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll ---------------------------------------- GrblPanel Assembly Version: 1.0.9.18 Win32 Version: 1.0.9.18 CodeBase: file:///C:/Users/millright/Downloads/GrblPanel-Release-1.0.9.18A/GrblPanel.exe ---------------------------------------- Microsoft.VisualBasic Assembly Version: 10.0.0.0 Win32 Version: 14.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.8.4360.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.8.4470.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.8.4400.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.8.4390.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Runtime.Remoting Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll ---------------------------------------- RepeatButton Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Users/millright/Downloads/GrblPanel-Release-1.0.9.18A/RepeatButton.DLL ---------------------------------------- Accessibility Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll ---------------------------------------- System.Data Assembly Version: 4.0.0.0 Win32 Version: 4.8.4455.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- System.Numerics Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box." Thanks, Zach
Grbl Panel is not a maintained application anymore - last worked on in 2018. See Releases · gerritv/Grbl-Panel Consider something more up to date like CONTROL OpenBuilds Software - FREE Software for CNC Control: OpenBuilds CONTROL and OpenBuilds CAM
Alright, I started the job on the latest OpenBuilds version of GRBL and the same thing happened. All the values are the same as above (it imported them successfully). The job started fine, was moving fine, etc, and then the machine stopped moving but the job kept going (GRBL displayed the axes values as changing, but the graphic did not show it moving). Here is the last bit of the log (the alarm 3 was me pressing "STOP" as nothing was moving): " [14:02:53] [ X138.403 Y216.202 Z-27.433 ] ok [14:02:53] [ X137.924 Y215.371 Z-27.276 ] ok [14:02:53] [ X137.442 Y214.537 Z-27.152 ] ok [14:02:53] [ X136.931 Y213.651 Z-27.053 ] ok [14:02:53] [ X135.854 Y211.787 Z-26.842 ] ok [14:04:08] [ ALARM ] ALARM: 3 - Reset while in motion. Grbl cannot guarantee position. Lost steps are likely. Re-homing is highly recommended. [ undefined ] [14:04:08] [ ] ALARM: 3 - Reset while in motion. Grbl cannot guarantee position. Lost steps are likely. Re-homing is highly recommended. [ undefined ] [14:04:08] [ ] ALARM:3 [14:04:08] [ JOB COMPLETE ] Job completed in 00h13m" What could be causing this? Is it electrical? Connection based (I've tried three different USB cables and two different laptops)? Thanks, Zach
Not that I'm aware of. All of the lights are green and I'm able to move each axis and send it home immediately after it stops. Thanks, Zach
@protozach, are you able to identify the part of the log immediately before it stopped moving? (assuming that happened a bit before the lines you posted) Alex.
I'm going to try and rule out EMI (making sure everything is neat in the surrounding area, etc.) and then I will watch the log on my next run. Thanks, Zach
Here is the log when it stopped moving (the log actually stopped this time instead of continuing). "[09:21:21] [ X48.214 Y128.774 Z-19.888 ] ok [09:21:21] [ X48.72 Y129.651 Z-20.536 ] ok [09:21:21] [ X49.047 Y130.217 Z-20.941 ] ok [09:21:21] [ X49.445 Y130.907 Z-21.389 ] ok [09:21:21] [ X49.778 Y131.484 Z-21.743 ] ok [09:21:21] [ X49.959 Y131.797 Z-21.923 ] ok [09:21:21] [ X50.375 Y132.517 Z-22.307 ] ok [09:21:21] [ X50.733 Y133.138 Z-22.619 ] ok [09:21:21] [ X51.223 Y133.987 Z-23.001 ] ok [09:21:21] [ X51.718 Y134.843 Z-23.354 ] ok [09:21:21] [ X52.348 Y135.935 Z-23.753 ] ok" I'm going to try spraying some anti-static spray in the air later today, hopefully this helps but I'm starting to get to my wit's end. The mill itself is a Millright PowerRoute XL which is only 25 months old so I can't imagine it would need to be completely rewired at this point, but who knows. The Y-Limit switch did go faulty and we replaced it already, so maybe it is wiring? I feel like there'd be more information in the log if it was wiring, maybe? EDIT: I've also increased the humidity levels to be much higher than they normally would be. I'm thinking with the change of seasons (drastic here in ND), the mill is reacting poorly. So far so good. Thanks, Zach
Valid possibility: @protozach see docs:blackbox:install-windows-selective-suspend [OpenBuilds Documentation]
I saw you guys talking about the selective USB thing earlier in this thread (or another, I've done a lot of Googling and you guys have helped so much without even knowing) and that has been off. I have the place feeling like Florida in August and, somehow, the mill is running at full capacity. Normally I would never go above 50-55% humidity, but environments change, I suppose. Thanks and I'm sure I'll be back, Zach
This is a question not really related to GRBL, but maybe you guys would have some input or be able to point me in the right direction. I've had my second limit switch in less than two months fail. If they were new with the machine, they should only be about two-years-old. Both times, the NO (normally open) to COM had zero continuity when checked on the multimeter (I made sure to have the switch pressed when checking). The NC (normally closed) has continuity just fine (this one never has anything hooked up to it, though). I was under the assumption that these simple mechanisms lasted quite some time. Luckily, they are cheap and I can pick replacements up locally, but could this have anything to do with my machine itself? The wires all have continuity so I can't think of anything other than very poor luck.
Only thing that comes to mind is your homing search and seek rates - if you are hitting the switch hard? Alex.
Hi, I have been using my OX Cnc machine for a year or two.. but never used the HOME function. I decided to finally set it up and connect the switches.. I decided to run home position top right at the back of the machine. (mine is 1500x1500 mm). and I want the zero point 000 to be front left.. (I assumed this was ok) when I send the machine HOME it moves to the back corner and stops at the right time, all works well.. although the address that comes up on the screen is wrong.. when I request for it to return to 000 it overshoots and starts skipping steps. ( I have a physical stop) If I set the 000 to be further in, it is out by almost 200mm in the X axis and around 6-80mm in the Y axis. I don't understand why the Home switch doesn't show the right address. Any advise would be appreciated. Peter
The normal set up with grbl is that the back, right, up corner is the maximum for each axis (that has to be so) and is also X0, Y0 and Z0 (in the MACHINE co-ordinate system) - that means that, as you move away from that corner the co-ordinates become negative. Your jobs, of course, are run in a separate WORKPLACE co-ordinates system where you set the workplace zero in the same place on your workpiece as you set the origin in your cam software - that co-ordinate system can have both positive and negative co-ordinates. Alex.
Homing sets Machine Coordinates You, the operator, sets Work Coordinates (SetZero Buttons or G10 commands) - jog to where the Stock Origin is, then Set Zero there. Stock origin moves around all the time, you always have to Set Zero. See docs:blackbox:hello-world [OpenBuilds Documentation] Homing allows you to pick up the last Zero'd origin by rehoming, but more importantly, Homing sets Machine coordinates for Advanced CAMs that move in more than one Coordinate system (eg Fusion360 etc)
Thanks, for the replies! I dont think I explained it very well. If I set a 0 point somewhere on the table.. and the send the machine home, it goes home. If I then ask it to go to 0, it misses by a about 30mm on x axis and about 10mm on y axis.. it overshoots the mark! I expected it to return to 0..?
You need to calibrate to make sure that it is still moving accurately after a year or two of belt stretch. Then you need to fine tune your max rates and acceleration, and may also the current settings on the drivers. and do all that AFTER cleaning all the V slots and wheels to make sure it is not getting stuck on dirt. Particularly during rapid moves, the tiniest bit of extra resistance can cause missed steps. But also. If you use home switches you can never send to to machine 0,0,0 without GRBL throwing a limit error, after a limit error position in not known, you have to home again. all about home and the machines sense of self : Home, Fusion360 and G53 Z moves
I'm hoping this is the right place to ask some questions about Grbl? So i'm building a fully automated 3dscanning system for multiple objects. The system includes wireless turntables (exept for power input) with a rasperry pi, arduino uno, stepper and A4988 stepperdriver inside. Unfortunately marlin does not fit on the arduino, so I'm currently trying to get Grbl going on it instead, but I'm having a hard time =( Main problem is that I can only execute 1 command and after that Grbl does not respond and i have to reset with power button for Grbl to respond to command again. There are no limit switches, only x-axis and yes I know about G91. Does not seem to be the problem.. I'm using node red+pronterface on the raspberry pi to send the commands via usb to Arduino/Grbl.. What could be the problem? an easily corrected noob mistake maybe? =) Hoping for some good help from you Grblexperts! =)
What command do you send? Grbl sends an OK when it accepts a command - are you monitoring the return serial responses? Grbl v1.1 Interface · gnea/grbl Wiki is a must read
I have tried a few. For example: "connect" followed by "$J=G91 X10.0" "connect" followed by "$J=X10.0" "connect" followed by "G91" followed by "G0-F200-X10" Nevermind I give up now after about 30 hours of Grbling and teacuping. I'll just pick a marlin compatible board and bing bang works from the start no problem whatsoever. Thanks for helping though =)
why are you sending 'connect' ? that does not exist anywhere in the GRBL wiki, and is not part of the Gcode standard either. Code: "G0-F200-X10" will fail too, remove the - characters, and G0 never obeys F words, so leave that out (if you need to specify the feedrate, use G1) Code: "G91 G0 X10" will rapid to 10mm from the current position.
Ok, thank for the help. I am pretty sure I have already tried that and it works only once though sorry nevermind the connect command. Those commands i send from the pronsole terminal i should not have included connect command in my question..
Im starting to think that pronterface/pronsole is not working good with Grbl. Maybe there is a better way to send gcode commands to Grbl/arduino from Raspian terminal though usb?
