Hi All Just finished putting the cnc lead 1010 together. yea when I select the x axis - on control software the motor goes in the wrong direction. all the axis do this. I have the blackbox to. wire wrong? mb
Wire wrong (swop first two wires), or simply click Grbl Settings in Control, and scroll down to the Axis Inversion: Use the switches to invert (or uninvert) till it works the right way
Trying to figure out what’s up with the control portion of the software on my pc. It works flawlessly as far as controlling the machine goes, but I find myself needing to close it manually via task manager, then reopen, in order for it to work after sitting idle for a bit. I also have to unplug the usb, then plug it back in for the software to recognize the controller upon startup. If I open the program with the usb plugged in, it won’t pick it up. I’m sure I have a setting or something wrong on my pc, what can I try? Also on a separate note, is there a way to add a command for tool on and off if I have an iot relay? Or do I still have to control the spindle manually by clicking “tool on” or “tool off”? If like to have it shut off automatically at the completion of a job.
Aww man, what OS are you running? Any other PCs around to check with to eliminate the PC. Havent seen other reports of similar yet. Tool On / ToolOff. Yes in your CAM you should be able to add start and end gcodes. What CAM are you using? Have it add M3 S1000 to the start, and M5 to the end
Hey Peter. Getting app-update.yml not found error when trying to auto update from 1.0.144 to 1.0.147. I'm going to uninstall and install 147 manually. Just wanted to let you know.
A note to all, note that the 'S1000' is important. The default is S0 and M3 S0 will NOT turn the spindle on. ergo M3 by itself will not turn on (until after an S1000 has been issued). Further, if you are using an IOT relay (or other relay) for spindle on/off then the only valid value is S1000 (with default GRBL settings). Any lesser number will cause the spindle enable to do PWM pulses instead, and the relay will not like that at all.
It’s a cheesy budget minded HP, lol. It’s new, but it’s pretty basic. I don’t have another one to try unfortunately, I might be able to borrow one though. I’m using aspire to design/create the g code, then control as the sender. For the pc I’ve turned off all of the power saving settings, it doesn’t sleep or go on standby. I’ve fiddled around with different ports too but it’s the same story with the usb not being recognized until it’s unplugged and plugged back in. It’s not a big deal or anything, just trying to find out what I might be doing wrong.
not a problem, thats how we find bugs, i love that you report issues. Its just to find those bugs it helps a little to play the elimination game too. Or at the very least we might think of a PC side setting or two. I'll think about this some more too. I assume Windows 10?
Nope most software vendors have the correct M3/5 etcs in their Post Processors already, pretty standard stuff. Grbl specific post processors especially already cater for these
Well there is your problem.. You are using Windows Jokes aside.... Since there is a Osx verison.. should not be too hard to port the code to FreeBSD... hint hint devs... don't make me do it (besides.. you don't want me going through your code.. I do IT security vulnerability/code assessments for a living....)
Unlikely (; too small a userbase. Also Add FreeBSD support to electron · Issue #3797 · electron/electron (no support in Electron)
I see the same problem reported too, although my new HP Laptop Windows 10 is set for Sleep. After waking, the Control screen is unresponsive and I must kill using Task Control in order start it over.
I'd like to suggest an improvement, maybe? In the image below, my CNC went out of control/bounds. My board was tight, not slipping around. It would be nice if the Controller Console Messages were logged someplace for recall. After hitting Emergency stop, I lost exactly where in gcode I was at to further investigate... I understannd too, once these are written, it becomes a maintenance issue of when they should get deleted. Thx Dennis
I believe I have captured the problem... after a Websocket error, the interface is all locked up and needs to be restarted.
WS Disconnected, means the NodeJS backend died, which would be related possibly to USB port errors (EMI) (When a serious USB error occurs we can sometimes get a crash from node-serialport that also kills the whole backend process - not something we can fix, the root cause is the USB port disappearing, windows being slow to release it, node-serialport thinks there is still a port and try writing to it (fails of course). Fix the disconnects and the software will behave Refer to instructions here to run the backend with logging: Post #272 OpenBuilds CONTROL Software -> Second section about how to start backend in command prompt (we can also debug the backend) Try catch a screenshot
Sidenote, with your two somewhat seperate reports, forms a bigger picture... that runaway gcode, is also a sign of USB issues (mangled command, or missing command) This can happen if we expect to send as an example: G1 Z10 G1 X200 And the USB drops a couple characters due to EMI noise: G1 Z1. .......00 Which looks like G1 Z100 becuase the 0G1Z2 got mangled or not send. Typical EMI man (or just a very bad USB port, i've had a little 10" walmart windows tablet/laptop (nexbook or something like that) that i thought would make a great machine for near the CNC - did that kinds of stuff all the time. Replaced it with a Pipo X10, no issues ever again.
Your correct, the abnormal ending problem is due to the COM port, although your closing the port... you trap and never return to the GUI screen, perhaps showing the communications port is closed... enabling an opportunity to reopen the port? There are other popular programs out there used to communicate with 3D Printers and CNC, that offer a communications option to disable Hardware flow control? Those programs often recommend not using Hardware controls for reliability? How are you handling this?
It can be improved. Your behavior differs from the lab though, here i get a sigterm and the process dies. Pull requests welcome though (; OpenBuilds/SW-Machine-Drivers
We don't offer it as an option, because Grbl doesnt support hardware flow control.: gnea/grbl We use the Character counting interface described here: gnea/grbl In our implementation, we still use node-serialport v4.0.7, and as per the v4.0.7 docs: node-serialport/node-serialport Flow Control is disabled by default.
hello, I am in the process of getting my lead machine 1010 up and running, the hardware is about done and I can make it move about using the control software so still grinning my head off about that When I bought the kit I went for the high torgue motors because why wouldn't you (urgh urgh urgh) and I then read that they really need the external drivers which I got, then I thought I need a box to put them in so I bought a little metal box with a door, the kind you see in the sides of machines, then I thought I have some space in that box so I could mount the board and some other bits and maybe some buttons (I am running the xpro v3 which allows for physical buttons) and make a control box annnnd then my head kind of ran away skipping through the fields of ebay and bangood and I now have a bunch of hardware in boxes sat on my CNC ready to build a standalone control box, bear with me I am getting closer to my point. I saw your post about using a raspberry Pi as a controller (connected to the xpro) was not very good, but I figured I would give it a go as I will do all my modelling on my PC in my nice cosy office than then transport it to the machine,via memory key (I have toyed with the idea of wifi or ethernet but lets not get ahead of ourselves), to my cold garage where I can make noise and dust without the wife shouting at me. If it turns out that the pi really isn't up to it then you can buy teeny tiny pcs that would also fit inside my control box but they cost a wee bit more. So with the combination of the control box and a raspberry pi needing a screen I of course went with the logical and simple option, touchscreen!!!! I have a door panel on my control box that's just the right size for a 7" touchscreen (it will take a 10" on its side but those extra 3" cost a lot more money) and some buttons so then I got all excited and dug out my raspberry pi that was gathering dust in a drawer because I finally have a project to use it for (at this point I discovered that I know naff all abut setting one up but I can google like a champion). and that's where I am at, I have a raspberry pi running openbuilds control (I built it using this tutorial: OpenBuilds/SW-Machine-Drivers) which autostarts in fullscreen (that took some working out) sending commands to my xpro by poking at the screen which makes the gantry move back and forth. So next job is mounting all of the bits and buttons in the space with sufficient cooling to stop it melting and hopefully cut out the hello world example. And finally we get to the point, the 7" screen, its kinda not very big and I have sausage fingers, I can use it but it requires the kind of finesse that I generally lack (I am aware that CNC is all about the finesse and to be honest it has already crossed my mind that when the mechanics are done (fairly competent) and the wiring is done (less competent but no smoke as yet) then I really must learn how to use a CNC (I blame youtube, everyone makes it look so easy )) I have digressed again, back to the point, I noticed that there is a fair amount of white-space on the controller screen and in my situation that is at a premium so I wonder if I might be so cheeky as to offer/ask for a proposal for a tighter layout (either as main or as an alternative) which will be bigger on the screen. I appreciate that I am in a unique position with my setup but I figured some people might be running touchscreen laptops so it might work there as well. I have attached a poorly put together example using ms paint, alternatively is there/could there be a way of tweeking the GUI ourselves? sorry for rambling on, its late here in the UK so really should go to bed... Mat
@matcoller a few suggestions for you. Use a stylus. Give the phone pendant a try. Maybe rotating the screen 90 degrees might help?? While I dont have sausage fingers, I couldnt imaging trying to run any of the grbl controlers on a 7" screen. I have a 10" screen on mine and its okay.... for me anyways. I believe Peter posted a link earlier in this thread to an affordable 10" windows 10 tablet/box thingy that he uses. If I remember correctly, it was less than $200. Again, if I remember correctly, they had larger screen ones for not much more. One last suggestion, if you know anything about css, there's nothing stopping you from moving and resizing things in the UI yourself. The downside to this is updates. I have no control over what changes get incorporated into Control. This is just some user to user advice and I hope you find some of it useful.
How about a writeup of that (; I also use a 10" 1280x768 Pipo X10 and I can touch things fine. The LCD you got: Genuine Pi LCD? (decent resolution, IPS) or cheap 800x600 chinesium? (;
@sharmstr thank you for the suggestions, they are all good ones and you got me thinking about using a 10 inch tablet, it has the screen and the 'board' all in one, I didn't consider it before as I forgot that you can get them windows flavored but it would make more sense. I did think about modifying the CSS but I am a data warehouse coder and all that fancy web stuff is a bit too new fangled for me (I opened the source, had a panic attack and closed it again) I did try to rotate the screen but Raspbian is having none of it, I am not using the Pi LCD so I am wondering if that might be an issue, I will keep plugging away. I have used the phone pendant, its a really nice approach, just a bit too small for regular use @Peter Van Der Wal yep, its a chinesium but it is a fancy chinesium able to handle high resolutions (I am running at 1240 by 720, I think they were the numbers) and is IPS, its quite a nice neat little screen, thin yet all built in, no dangling ribbons. Had I been a bit less impulsive I might have spotted that there is an official PI 7" touch (which has rotation built into it) but you live and learn, I could get one but i'm thinking if my current setup is indeed too small I would jump to a 10 inch tablets based upon yours and sharmstr suggestions as they are a nice 'all in one' approach. With regards to the write-up for the auto start, I have a pi 3B+ on its way with a bigger card which will need to be set up so I will use the notes I scribbled down to do that, if my incoherent late night chicken scratch (distilled down from MANY MANY different approaches) works then I will post it here.
Yeah please do I dont get time to play with the Pi much and since a lot of folks like it, I dont object to adding instructions for those who want to to our official docs. Just because we dont 'officially' support it doesnt mean we dont love helping those who can help themselves
