gSender 1.5.0-Edge-7 looks good at first glance, various UI improvements. Running on my house Mac (no CNC connection) so canât do much beyond browse the UI and menus for now.
Opened a gcode file that has rotary (A-axis) and the visualiser has not populated - might be because I have no machine connected. However, a warning popped up saying âfile contains Rotary, you must enable Rotary modeâ - I cannot do this, nor do I want to. My machine is permanent 4-axis, so there is no valid swapping of Y axis to perform A function - that would in fact be harmful to my machine.
[Edit: hadnât noticed âfeather modeâ in visualiser was on. Turned this off (greyed out) and the 3D file opened without giving the above mentioned error]
I will install this -7 Edge on my workshop Mac tomorrow and see if the same behaviour is there with the CNC connected (grblHAL, USB connect, Franken-OKO, permanent 4-axis XYYZA with proximity sensors on XYYZ and A, self-aligning YY during homing, spindle, coolant/mister)
@AndyCXL FWIW, I have the Vortex closed loop version on a Mk1 with the SLB. In gSender, I do not use rotary mode. I use 4 axis mode. Like yours, my machine has all 4 axes live all the time.
If it hasnât been requested yet, could we PLEASE have a setup option to allow screen blanking?
I am currently fighting with Windows to let me edit the file that controls this functionality. Every time a new version lands, I have to re-learn (yeah I am old and forget things) how to get gSender to blank the screen..
Just to be clear, I am talking about screen blanking and not suspension or anything else.
Does Edge have the ability to turn the spindle off when you pause a job? will the spindle startup again when the job is resumed
You can do this in Pause/Resume automations (in both Edge and main) with the caveat that pause events change pause behaviour (we canât simply immediately feed hold because we need to be able to send the event code so it stops sending but completes the planning buffer vs holding immediately if thereâs no event)
Would very much like to test it, but [gSender-1.5.0-Edge-7-arm64.AppImage does not run on may Raspberry Pi 5. It just does nothing. What am i doing wrong?
Maybe I am missing something. What is the reason that there is not a toggle switch to change between inches and mm on the main page where the visuzalizer and jog dials are? It seems that you still have to go to the settings page to do that.
I have encountered that gSender Edge 7 keeps asking me to unlock the job at the top of the screen while the job is running. Iâve had this happen numerous times in a job.
What are the minimum requirements to run gSender Edge 7 on a Mac computer?
Itâs not something weâll plan to get in now, but Iâve recorded the thread where you discuss what youâre looking for and the current workaround and Iâm sure we can make an optional setting for that in the future 
@keverin16 Iâm not sure, these mightâve been done in Error or just something the team was trying since we havenât taken the time to fully flesh out pi builds till we get closer to release. If itâs meant to work, then just double check how your downloading and check our recommendations for troubleshooting Pi installs Installation - gSender Docs
Yes switching mm to inches is in the settings this is how weâve always had it for gSender, is there a reason youâre thinking it makes more sense on the main page?
Whatâs the specific unlock message youâre getting while running a job?
Minimum computer requirements are on main page: Introducing gSender | Sienci Labs
Hey folks, another Edge release with a number of tweaks, fixes, and look and feel adjustments
Portrait mode and touch support
Weâve added portrait mode for gControl and other users who want a different perspective on things. Either swap your display orientation in your operating system or turn the device if itâs has a gyroscope to update the layout automatically.
- Pinch gestures should now zoom the visualizer rather than changing FoV
- FoV alterations so grid doesnât get cut off when zooming/dollying too far
- Still working on sliders being more responsive on touch screen, should be in next release.
Config refinements
- Modified (non-default) gSender settings now also highlight if changed from their default setting and have a one-click button to restore them to default.
- gSender settings are also now filtered by the âShow modifiedâ toggle
- Quick actions no longer appear when not connected to a machine
- Various look/feel and labelling changes
AutoSpin setup support
- We now support setup for the AutoSpin inside the Spindle section of Config
- One click and the correct EEPROM changes are made for you based on your connected controller type (vanilla grbl/grblHAL)
Harmonized design
- Look and feel of dialogs and modals standardized and branded across the app
- Look and feel of button standardized in a number of places and active (pressed) state added for touch feedback.
- Numerous buttons that cause motion correctly coloured to the primary blue.
- Numerous other tweaks to standardize look of inputs
- Buttons that control accessory state (spindle/coolant as example) now have active indicator states
Tool Change fixes and alterations
- Passthrough option works again
- Skip Dialog option added to config and now skips pause modals on top of combining code blocks without a modal
- Re-ordered strategies
- Added Tool Change state to UI to match SLB LED
Jogging
- Fixes for selected speed not being used
- Fixes for correct unit being passed to continuous jogging
- Jog commands now emitted to UI console on grblHAL controller again
Probing
- Bit sizes now ordered
- Can now delete any bit, not just custom ones
- Bits now persist
- Adding a new bit should be a bit less troublesome
Miscellaneous
- Dark mode tweaks to some tools that were still unfinished/unclear
- Workflow state controls now allow stopping a file during dwells.
- Surfacing Tool reorganized to look more similar to Rotary Surfacing tool and should be clearer to use
- Coolant tab can now be hidden in config by disabling âCoolant Tabâ in the Accessory Outputs section.
- Close file no longer notifies twice
- Start from line correctly shows max file length
- A axis jogging image corrected to the proper rotation
- Secondary functionality tabs tied to config options (coolant, rotary, spindle). This means you need to enable rotary functionality in config if you want A axis controls to appear.
- Stop sign button now stops most motions instead of just Jog movements again
- Added disabled state to numerous buttons that should have had them before
- Resize listener added to carve page so visualizer doesnât disappear when swapping pages
- Stats Diagnostic now exports EEPROM settings similar to main gSender
- Reconnect Automatically now works
- Stat page look and feel and functionality updates
- Pop out console works again
- Opening a recent file that has been deleted/moved now informs the user and removes it from the list
- PI build available thanks to @Siganberg
Download
As always, Edge is early-access software and things can and will go wrong - please do not use Edge for time-sensitive or expensive projects and be aware of the risk.
Artifacts can be found on Github:
Jog buttons only work when actually clicking with mouse. Cannot hold down mouse button for continuous movement.
Huh, I have the opposite problem here: the jog input is so laggy it often thinks it should do a rapid when I only want a single click (e.g., manual probing). After crashing the tool into the workpiece on probe too many times I finally gave up and got the sensor probe working today. Hopefully the sensor logic is less non-deterministicâŠ
Anyway, at least on precise jog it would be great if (a) gSender only ever emit single steps rather than continuous jog, and (b) if the output was formatted the same-ish in the console, and I guess included the continuous jog stop?
And while debugging all of this, the pop-out console in gSender 1.5.0 Edge-8 doesnât seem to work here:
Not sure why the console window has the same menu bar as the whole appâŠ
Iâve seen the same failing pop-out behavior with Edge-8 on Debian Linux.
Can someone explain how the Go To function works in edge 8? In the old gsender, when you click Go To the values would be filled in with the current X Y Z locations. all you had to do was enter the new values in the fields you wanted to change and press go.
In Edge, there is ABS and INC - neither prefills in the current values. If you toggle between ABS and INC then back to ABS it will fill in the values (the Z is ALWAYS wrong BTW) and when you enter a value to move to and press go, the system moves close to the home location. For the life of me, I canât get Edge to move to a location.
Also, when I press XY that should move the spindle to the XY zero AND LEAVE THE Z at the current height. Several times I have pressed XY and the bit will dive down PAST the z0 and ruin a piece. Other times it will work exactly as expected, and I canât seem to find any rhyme or reason why it works sometimes and not other.
This thread closed since now the official 1.5.0 version is released and Edge is finished itâs cycle!
@DocRM just to finish off your question, the behaviour you saw for the Go To function in Edge 8 was broken and has since been fixed in 1.5.0/1.5.1 where the values now populate correctly and the Z value is fixed. Regarding pressing XY, if you have a machine with homing then make sure you home the machine when you start it up, since otherwise the Z-axis will try to move to the safe height of the homes axis and might move in an unexpected direction instead