I’ve just got a bitsetter and manually Z0. Using Fixed Tool Sensor with correct coordinates.
It gets to a tool change, opens up the wizard:
and hangs here… “Run Gcode” is greyed out, and the following items beneath it aren’t accessible either so… I’m not quite sure how to test/troubleshoot this.
What piece am I missing?
edit: Machine Shapeoko Pro 5, VFD, running gSender 1.2.2
What is this from? I’m not familiar with it.
@LordofCandy Welcome to the group, Andy.
I don’t have your machine, nor a tool sensor. Have you followed all the instructions set out here
If so, the Sienci gSender team monitors this category and I’m sure that someone will be able to help you when they re-open later this week.
@gwilki Yessir, I was under the impression from trying to read from the earlier posts (BitSetter and other tool length sensors supported in gSender - #5 by NeilFerreri) when a bit setter was being set by Macros that this newer build of gSender could obviate that need by using the fixed tool, but the page Additional Features - gSender Docs doesn’t go deep with it, nor say if anything else needs to be setup, or how to validate it. So when I set it up per the basic instructions and get a tool change popup (tool paths generated from Vectric & @NeilFerreri 's post processing multi-tool script I get a hung tool change.
Other odd info is if you cancel it (the wizard), and then stop your job (because you can’t do anything), you are truly hung in gSender as the screen shows that it still thinks its running (“Running”) but nothing else can be done. So you have to quit and restart, reconnect, and reinit everything.
Hopefully I’m just missing a key piece of information and a dev or someone who has this working can chime in on for I know not how to proceed.
sidenote: I did get Edge setup as well and it still has the same behavior.
Yessir. It is the 4x4 machine.
Are you getting a soft limits error in the console like I am?
See my post here: gSender 1.2.2 Triggers Soft Limits During Fixed Tool Sensor Change
No, I read your issue and we’re a bit divergent and I’m not sure why. It intercepts the tool change code the wizard pops and I’m stuck right at the gate. I also don’t have soft limits on by default. I thought if I get comfortable with gender I’ll institute some changes but I’m just trying to find parity at the moment.
Did you have anything else setup to have the dialog progress?
Been holding out to go back to what Neil setup hoping to see a dev poke their head in and tell me what i did wrong or what to test for validation. Guess I’ll start working toward Neil’s macros and a pause for instruction at tool change for now. New wizard looks cool.
Well can’t fault me for trying… but I can’t get this to work properly no matter what I do. I went back to @NeilFerreri 's macro’s and got the positional data and loaded that in.
ok
G4 P0.5
ok
G21
ok
M5
ok
G90
ok
G53 G0 Z-20
ok
G53 X-1.5 Y-1217.34
ok
G4 P0.5
ok
G53 Z-75
ok
G91
ok
G38.2 Z-100 F200
[PRB:-1.500,-1217.338,-90.725:1]
ok
G0 z2
ok
G38.2 z-5 F40
[PRB:-1.500,-1217.338,-90.719:1]
ok
G4 P.25
ok
G38.4 z10 F20
[PRB:-1.500,-1217.338,-90.688:1]
ok
G4 P.25
ok
G38.2 z-2 F10
[PRB:-1.500,-1217.338,-90.719:1]
ok
G4 P.25
ok
G38.4 z10 F5
[PRB:-1.500,-1217.338,-90.688:1]
ok
G4 P.25
ok
G90
ok
G4 P0.5
ok
(TOOL_REFERENCE = -90.65)
gSender client thinks its still responsive but it isn’t. Feeder won’t take input, won’t give back ok’s, it’s just taking everything and punting into null for all I know. Only way to get back is a full disconnect/reconnect/home. Also checked Edge just to verify and same behavior.
So I’m hamstrung on tool changes of any sort at the moment. If I’m missing something it’s gonna be dumb and obvious, or I’m an edge case and I hate being the edge case.
gSender looks lovely and I’d love to use it as a driver, but I need the bitsetter to be operable in one fashion or another.
Thoughts and consolations welcome. hehe!
@LordofCandy Sorry for missing all this. I think I saw a discord message from you right before I fell asleep one day and then forgot about it all.
First question… Do you have a SO5?
Edit: I now see that you do.
Try removing the comments that display in parentheses.
(TOOL_REFERENCE = [global.state.TOOL_REFERENCE])
I have no idea why they did it, but C3D uses an ESP-32-S2 for USB communication. As far as we can tell, there’s some bug in their firmware that can’t handle those comments going through.
This was it! Comments. Wow, such an innocuous idea but it causes the SOP5’s a great deal of issue.
There are comments in the tool change code :
Thanks to gibs for pointing it out : GSender, any special steps to use? - #29 by Gibs - Unsupported - Carbide 3D Community Site
and maybe we can get comments stripped out of machine sent info : Feature Request: Suppress gcode comments in gcode sent to machines. · Issue #444 · Sienci-Labs/gsender · GitHub
Did my first toolchange test and Neil’s code (sans comment) worked great. Now I can really get into gsender.
We’ll take a look at stripping them out. Unfortunate bug for sure.