Hi.
I’m using xpro cnc - grbl. Serial console keeps logging and I can’t find a way to disable it. I tried filter button. I had that problem earlier, but it just disappeared. Also, I can run only a sample of simulation of a pcb. How to simulate the whole process?
Thank you.
what workspace are you in?
/jpadie is there any other workspace working with grbl 1.1?
Hover over the funnel icon to see the regular expression for filtering. jpadie is only filtering out /^ok|^\n/ so he could add filtering out lines starting with < and [ to help clean up your serial port console. The /grbl workspace has a bigger filter on it. Hover the funnel icon to see it.
What do you mean by running part of the simulation? Is the whole pcb showing in the 3D viewer? If so, you’re probably fine to run an airjob to test it.
Yeah I can see it. How can I change it?
You can fork the workspace and modify the init method of the serial port console to pass in a larger regular expression. Or, you can figure out a macro that wipes out the serial port console and then reinstantiates it with your new regular expression.
It would be nice, if you fork the workspace, to send jpadie a pull request via Github.
I can see a whole pcb, but when I try to run a simulation it stops after maybe 2 sec. I can do the milling or an airjob.
@Daniel_Wiejak You can try my workspace, I added a filter for that: http://chilipeppr.com/chpech
@jlauer The reason the simulation is not working is because the grbl is constantly reporting it’s current position, the 3D-viewer widget subscrubes to that, this causes a call to gotoXyz() which interrupts the simulation.
My proposal for a solution would be that gotoXyz() only interrupts the simulation if the position differs from the last position.
If you prefer I can implement it (tomorrow) and do a pull request.
It’s the grbl widget that gets the proprietary position data and converts it to the standard chilipeppr format and republishes to the workspace. Only then does the 3d viewer get it. So I would suggest you modify the grbl widget to not republish, rather than modify the 3d viewer.
Ok, I will look into it.
Also, one option, that I try to discourage, but is there, is the pubsub system is all amplify.js and it’s synchronous. So, you can subscribe to a pubsub signal at a higher priority than all other widgets and return false to cancel them, so they don’t propagate. Or you can return true to let it continue to propagate to other listeners. It’s a really cool system that is at the heart of ChiliPeppr. So you could subscribe to position updates and cancel them if duplicated, but I discourage using this nuclear option because you have to pick a priority number and there’s no central record of what widget may have picked a priority number and thus you get some spaghetti flow that confuses people in the future.
BTW, you could also override that serial port filter from a macro by doing something like this:
cprequire(
[“inline:com-chilipeppr-widget-spconsole”],
function(myObjWidgetSpconsole) {
// u now have a reference to the serial port console
myObjWidgetSpconsole.filterRegExp = “/^ok|^\n|^<Idle|^[GC:/”;
}
);
What’s not clean about this is that it doesn’t update the GUI with what the new filter is, so a setFilter method should get created rather than the half-ass code i put in the init method. My bad.
Although, it sure would be nicer if a pubsub signal was exposed from the serial port console to let you do something like:
chilipeppr.publish("/com-chilipeppr-widget-spconsole/changeFilter", “/^ok|^\n|^<Idle|^[GC:/”);
So that it’s clean, structured, and documented in the pubsub popup modal window.
The grbl widget will now only publish axes if the coordinates have changed. You might try it here @Daniel_Wiejak http://chilipeppr.com/chpech
For a customizable filter an edit option in the spconsole would probably be the cleanest. A pubsub would introduce unnecessary complexity since the filter is to no interest to any other widget. But it’s probably not necessary at all.
Thanks guys. I’ve forked/changed the filter. I tried your workspace @ChPech and it solved all my problems! Thank you. What controller do you use?
One more thing, I’m getting crazy estimated times like 8h?