GSender, any special steps to use?

gsrunion · January 12, 2024, 6:29pm

I guess all those are single line comments and not inline.

Gibs · January 12, 2024, 7:37pm

That will only stop the tool from locking up when getting a M6 command. You will need to remove any inline comments from the gcode file as well. Essentially you want to make sure the SO5 at no point receives a parentheses.

Removing all of the yellow from the picture below and using the suggested javascript changes is what is needed. I modified my post processor to use semicolons instead of parentheses.

LordofCandy · January 12, 2024, 9:02pm

I’ve been smashing my face on just getting the bit setter to work, did you do anything special for yours? New to Tool Change, What's Missing? - ❓ Question - Sienci Community Forum

Gibs · January 12, 2024, 10:05pm

I use macros for bit setter. From my understanding, the macros I use are a modified version of @neilferreri’s macros which I then further modified to use PRB values for probing and also removed any use of inline comments. You would need to modify the “init” macro to have the correct x and y location of your bit setter if you choose to use the same macros.

My work flow is as follows:

Set zero by either 3d touch probe or using Vbit and eyes depending on precision needed.
Run “init” macro to initialize variables.
Run “probe tool” macro to set initial bit height.
Run gcode file
Change tool manually then run “probe tool” macro to offset zero with new bit height.
Repeat steps 4-5 until done.

bitsetter-macros.zip (1.3 KB)

gsrunion · January 12, 2024, 10:08pm

I was under the impression that, with the right configuration, GSender could do the needful for a BitSetter…

Is that the path you have been down? I had not gotten that far yet.

gsrunion · January 12, 2024, 10:13pm

Ok. I opened an issue/feature request on their github. Feature Request: Suppress gcode comments in gcode sent to machines. · Issue #444 · Sienci-Labs/gsender · GitHub
I can navigate javascript well enough that I can go ahead a create a pull request with the changes you have listed, However a more wholistic solution, as described in the ticket, would be a bit more challenging to implement.

LordofCandy · January 12, 2024, 11:55pm

Yes. I tried this route first since it was mentioned by a developer as being the integrated way forward for folks like us. But it just hangs. Maybe there’s a comment in there somewhere as it exhibits a similar behavior to using Neil’s default code. I’d love to get it solved in their native newness but I’m not sure that’s possible until someone peeks in and asks for some data for those of us having issues.

Give it a try though and report back. While I don’t want to be the only one having a problem of it works for you maybe I missed something. If it doesn’t at least we are not alone. Heheh.

gsrunion · January 13, 2024, 12:04am

I’ll try shortly. If it is a gcode problem, that should be viewable in the console. Will see shortly.

Gibs · January 13, 2024, 12:58am

That is because they utilize inline comments to send info to the console during the tool change.

Example console output when running on a machine that does not lock up when sent inline comments:

T6(M6)
ok
feeder G4 P0.5
ok
feeder M5
ok
feeder ({"PROBE_THICKNESS_MM":30,"PROBE_DISTANCE":73,"PROBE_FEEDRATE":150,"PROBE_SLOW_FEEDRATE":75,"RETRACT":4,"XPOS":"0.000","YPOS":"0.000","ZPOS":"0.000","PROBE_POS_X":5,"PROBE_POS_Y":20,"PROBE_POS_Z":30,"Z_SAFE_HEIGHT":-10,"UNITS":"G21","SPINDLE":"M5","DISTANCE":"G90","FEEDRATE":"F0"})
ok
feeder G4 P0.5
ok
feeder G91 G21
ok
feeder G53 G0 Z-10
ok
feeder G53 G0 X5 Y20
ok
feeder (Toolchange initiated)
ok

You can find the portion of code that does this in gSender here:

github.com

Sienci-Labs/gsender/blob/d3c86520890b9580517c792977988382b91dffdf/src/app/wizards/automaticToolchange.js

/*
 * Copyright (C) 2022 Sienci Labs Inc.
 *
 * This file is part of gSender.
 *
 * gSender is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, under version 3 of the License.
 *
 * gSender is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 * GNU General Public License for more details.
 *
 * You should have received a copy of the GNU General Public License
 * along with gSender.  If not, see <https://www.gnu.org/licenses/>.
 *
 * Contact for information regarding this program and its license
 * can be sent through gSender@sienci.com or mailed to the main office
 * of Sienci Labs Inc. in Waterloo, Ontario, Canada.

This file has been truncated. show original

LordofCandy · January 13, 2024, 1:42am

ahh its all making sense and all tied to the same issue. Neil had me remove a comment in his bit setter init and viola that works. So now just need to dodge commentary files or run them through some additio

Always glad when you can understand a problem better!

gsrunion · January 13, 2024, 2:15am

Confirmed just tried to run the BitSetter…choke. Guess I need to check out that macro. Also, I have a BitZeroV2, that is now working since I was sent a new front panel board. Has anyone successfully gotten probing to work with it? I would be good with treating it like a standard probe without a hole, but the routine has to move far enough to avoid the loop.

gsrunion · January 13, 2024, 2:54am

gsrunion · January 13, 2024, 2:55am

Well this isn’t good. Some garbage showing up in the traffic logs now. And the machine doesn’t want to jog. It does however initialize, and probe the bit…with CM that is. It will home and jog with GSender…it seems to have hosed CM somehow. Tried CM on another computer, ran through the setup wizard, and resent configuration to the machine. Jogging, homing, all that seem to work. However, the machine is cutting like garbage. I have some round countersink holes I am cutting and it seems to be stuttering on each of the small line segments that make up the circles. It’s as if banter to and from the machine, like baud rate has dropped to next to nothing or response latency has went way up.

I’m thinking the firmware on that esp chip got corrupted somehow and that I need to reflash firmware. I capture video, but it seems I can’t upload here.

Edit: the stuttering might be from having the log open as per Weird stuttering in corners S5 Pro - #3 by CthulhuLabs

neilferreri · January 13, 2024, 4:35am

@gsrunion Can’t assume. Have you powered down the machine completely? I cant think of a way you could’ve corrupted any firmware simply by connecting to another sender.

gsrunion · January 13, 2024, 4:44am

Yeah…probably not corrupted firmware, but perhaps some on chip configuration. Who knows what kind of state the machine gets in when it receives those inline comments and goes tango uniform.

I have done a couple of reboots of the machine and waiting 30s or so while also closing CM. I’m inside from the shed for the evening but I’ll go out in the morning and see if things run better with the log closed. The log thing is pretty plausible as painting some text on the screen adds extra latencies.

As far as the borked CM on my tablet. That is a weird one. It acted up even after uninstalling and doing a clean install. I guess maybe a reboot was in order as well. Something else to try in the morning.

Gibs · January 13, 2024, 3:48pm

Carbide motion leaves some config files on your computer after uninstall. You can try deleting the files found in your C:\Users\<username>\AppData\Local\Carbide 3D\ and C:\Users\<username>\AppData\Roaming\Carbide 3D\ after uninstalling, then try a clean install. Might not do anything but it is worth a try as you already verified it works fine on a different computer.

gsrunion · January 13, 2024, 6:06pm

Yeah I was going to go do a more thorough deletion. For now I am good using the laptop.

gsrunion · January 13, 2024, 6:06pm

The stuttering does appear to have been from having the console open.

Gibs · January 14, 2024, 4:53pm

So I did some further review of the gSenders code. By modifying line 8892 of the index.js file found in your C:\Program Files\gSender\resources\app\server folder(if that is where you installed it), you can strip out all comments from being sent to the SO5 from macros, gcode files and the tool change wizard. I have already tested this and it works fine.

Changing
var commentMatcher = /\s*;.*/g
to
var commentMatcher = /\s*;.*|\(.*\)/g;

will allow you to use the built in fixed position tool change wizard. This will also strip all comments from macros and gcode files.

This can be found in the original code of gSender GrblController.js line 268. After the electron build it becomes line 8892 in index.js

github.com

Sienci-Labs/gsender/blob/d3c86520890b9580517c792977988382b91dffdf/src/server/controllers/Grbl/GrblController.js#L268


      
              if (trigger === 'system') {
                  taskRunner.run(commands);
              } else {
                  this.command('gcode', commands);
              }
          });
          
          // Feeder
          this.feeder = new Feeder({
              dataFilter: (line, context) => {
                  let commentMatcher = /\s*;.*/g;
                  let comment = line.match(commentMatcher);
                  const commentString = (comment && comment[0].length > 0) ? comment[0].trim()
                      .replace(';', '') : '';
                  line = line.replace(commentMatcher, '')
                      .replace('/uFEFF', '')
                      .trim();
                  context = this.populateContext(context);
          
                  if (line[0] === '%') {
                      // %wait

All code changes needed in index.js:

Line#8983 from line = line.replace('M6', '(M6)');
to line = line.replace('M6', ';M6');
Line#9118 from line = line.replace('M6', '(M6)');
to line = line.replace('M6', ';M6');
Line#8892 from var commentMatcher = /\s*;.*/g
to var commentMatcher = /\s*;.*|\(.*\)/g;

Note: line numbers are based off of the v1.2.2 build

neilferreri · January 14, 2024, 5:56pm

Anytime you have the C3D console open, you’re having these issues?