Sorry I made an edit which obviously didn’t take… 1.9.16, win64
Can you try 1.9.15?
1.9.16 isn’t an official release yet
Just tried both .15 and .14 with the same result
Everything else working ok? Can you jog the machine without issue?
Can you get a screenshot of CNCjs right before you try the probe?
Just dug into the grbl source. There’s only one way that error could happen on a probe, and it shouldn’t be happening with your probe commands.
It shouldn’t matter, but can you try a different sender? Just a sanity check.
Maybe a communication issue? Try restarting everything.
@neilferreri sorry no progress, my girlfriend borrowed my truck today and the oil filter popped off on the highway - Engine is written off… At about $10,000 to replace I’m less than pleased, or $2000 for a rebuild kit which I Can probably do it in a week or two…
I’ll try and get in the shed tomorrow and check out bcnc or ugs and see if I get the same result.
Another question - is there a continuous jog option at a fixed feed on cncjs? Or is it only incremental?
@neilferreri. The touch probe macro you did up for CNCJS using the Carbide 3D Touch probe has worked great for me! Thanks. Sorry for the delay in getting back here to let you know. Using this macro, and the built in Z probe macro has been a great help for me. Thanks again.
I have not technically seen this issue but possibly have seen something similar…I have never run the CNCjs server from Windows or Mac. I have tried several different setups using various Raspberry Pi (Not sure of the plural for “Pi”). What works for me is running the CNCjs server on a Pi ZeroW connected via usb to the SO3 control board and then accessing the server with my laptop via wifi. I have NEVER had an issue with this setup. I use a shuttlexpress connected to the laptop for jogging. The shuttlexpress is a tiny bit glitchy-like you have to wake it up or something- but this setup works great.
Now here is where I have run into hangs…I tried to run CNCjs using a keyboard, mouse and monitor plugged directly into the Pi. The server running in the background and accessing it using Chromium (localhost) on the same Pi. The PiZero could not do it at all. It worked on a Pi3B+ but the console would become unresponsive with longer runs. However, the machine was still running the gcode. Sound familiar? The Pi3B+ simply couldn’t drip the gcode, run the CNCjs server, and run the console via Chromium all at the same time. Rather than failing though, the computer seemed to shut down non-essential processes, like the console. This is mostly speculation, but it is what I observed. So maybe, possibly, you are running into the same thing on Windows or Mac machines with the same setup??? I honestly don’t know for sure, just putting this out there for smarter folks to ponder.
There is a desktop CNCjs app for Mac and PC you can download, if I understand correctly, there is no need for the controller between the laptop and the CNC
You are correct. You can run CNCjs using the Windows/Mac app and control the Oko, but you must have that computer plugged into the Oko via usb. The Pi route adds wireless access to the Oko. I like having the wireless access to the machine so I can use either my laptop or my desktop as the interface. I also like to move my laptop away from the machine when running a cycle.
Well I guess it is a choice with some advantages and some disadvantages. I have an old laptop as my Shapeoko controller. I can take my work laptop wherever I want and I should be able to access my Shapeoko controller using remote access but I prefer not going away when the Shapeoko is working. Again, this has advantages and disadvantages, you need an old computer to act as a controller.
Yes, but the issue hasn’t seemed to be addressed yet. I have a cheap Win 10 tablet running my SO3, and I’ve seen the issue with that. I have another CNC connected to a much more capable PC, and I don’t recall ever having the hang up issue. That said, I do more with the SO3, so I haven’t tried a comparable job.