If you use the remote browser, load a file and send it, it sends bad gcode for starting the spindle and jogging and who knows what else. Below are screenshots of exactly what Im talking about.
First I will give you the header of the gcode file.
This screenshot shows the console output of running the file with that header. I canceled the job after the spindle and dust collection turned on.
Next, I will connect to the computer remotely, then connect to the machine and do the same thing.
As you can see, it adds some information when remotely connecting where it is not if you're just using it on the machine that's connected directly to the CNC
S18000M3 G4 Ptrue
The only way to resolve this issue is to completely shut down the program, launch it, and NEVER connect to the remote interface at all for any reason.
This issue is related to the custom delay that was introduced in the latest version, or versions. Needless to say, it didn't start the spindle and then proceeded to snap a 45-dollar 1/8-inch Amana Spectra endmill. My post-processor already adds the delay and had no issues in previous versions either locally or remotely.
I'm using remotely rather liberally, as the remote device is in the same room, just has a much better monitor on it.
This was a concern of mine when this feature was first announced, as crating and or modifying gcode should not be done by the sender at all, only the post processor.sigh
Also, if you try and jog under the same circumstance from the remote end, you get this in the console.
here I was just trying to raise the Z after the malfunction. This behavior only happens if you try and jog from the remote side, but device side it will jog, in this case, the Z.
J-eremy
commented
2 weeks ago
If you use the remote browser, load a file and send it, it sends bad gcode for starting the spindle and jogging and who knows what else. Below are screenshots of exactly what Im talking about.
First I will give you the header of the gcode file.
This screenshot shows the console output of running the file with that header. I canceled the job after the spindle and dust collection turned on.
Next, I will connect to the computer remotely, then connect to the machine and do the same thing.
As you can see, it adds some information when remotely connecting where it is not if you're just using it on the machine that's connected directly to the CNC
S18000M3 G4 PtrueThe only way to resolve this issue is to completely shut down the program, launch it, and NEVER connect to the remote interface at all for any reason.
This issue is related to the custom delay that was introduced in the latest version, or versions. Needless to say, it didn't start the spindle and then proceeded to snap a 45-dollar 1/8-inch Amana Spectra endmill. My post-processor already adds the delay and had no issues in previous versions either locally or remotely. I'm using remotely rather liberally, as the remote device is in the same room, just has a much better monitor on it.
This was a concern of mine when this feature was first announced, as crating and or modifying gcode should not be done by the sender at all, only the post processor. sigh
Also, if you try and jog under the same circumstance from the remote end, you get this in the console.
here I was just trying to raise the Z after the malfunction. This behavior only happens if you try and jog from the remote side, but device side it will jog, in this case, the Z.
TLDR: DON'T USE REMOTE MODE AT ALL.