Downloaded and installed. Since I have a keypad, I looked at the shortcuts closely. Here are a few observations:
- The four homing to corner locations are missing
- ctrl+alt+a cannot be used. Thereās no error saying itās used elsewhere.
1 Like
Some first quick feedback on Edge 1.5.0 E6, running on Mac with Franken-OKO-3XL, Teensy 4.1 on Phil Barret BOB, GrblHAL, XYYZ, self-made permanent Rotary A with limit switches on all 5 (2 on Y) axes, VFD, USB connect.
- Very much like the fixed/improved continuous jog behaviour, it no longer ābit at a timeā moves and is now continuous if multiple clicks (or keyboard shortcuts) are made
- Very much like the Park button and concept
- Scaling of the UI no longer fits my 13" Retina laptop screen, all of these 1.5.0 Edge versions have been the same. The lower ~20% of the screen is only accessible by vertical scrolling, which āworksā but is not ideal. Not sure what expectations are in general for resolution on a shop machineās screenā¦
- Rotary axis keyboard shortcuts do not seem to be working, either KB ctrl-alt-. or with my self-made rotary pendant (that sends the same KB command via its own USB KB persona)
- Scrolling the Console window seems rather slow, not smooth as in āliveā gSender
Iāve not run any JOBs as yet, wanting to be sure the various comments over Z uncertainty during zero setting are resolved before spoiling anything
2 Likes
hey i just checked at my workspace and home, if the machine is preset and home those shortcuts will appear, theyāre not showing at home with no machine connected
kinda strange but are deffinetly there
Thanks. Good to know.
Spent an hour on the machine today using Edge 1.5.0 E6 and all good so far.
- Honing a āhole centre zeroā probe macro, all worked as expected and all previous macros also worked without issues too
- Surfaced my segmental spoil board by 0.25mm, all good except one minor observation - the spindle started but hadnāt reached full speed by the time the first engagement of the cutter happened - I changed the order of the first positioning commands in the gcode and it spun up the spindle in good time
- Not sure why, but the smooth jogging I noted in an earlier post seems to have reverted to ābit at a timeā today. Didnāt spend any time investigating what or why
- [Edit - it seems I clicked the āaeroplaneā icon and hadnāt noticed - this icon/button doesnāt indicate which mode of jogging is selectedā¦]
- Noticed that when closing the current gcode file, the alert/notification appears twice
1 Like
A post was split to a new topic: Issue with Continuous jogging starting in 1.5.0
What is the last version of edge you have been able to run successfully? Im stuck on 1.3.10
It would also be nice to have all job history and stats and maintenance transfer whenever updating to a newer version
@Cmcustom For āliveā jobs, I am using 1.4.12 latest release and for me it works well. Playing with Edge 1.5.0 E6 to help give it the best launch to live and with it the improved UI
1 Like
@KGN
The good: It was good to see that this version brought in all my keyboard shortcuts, including those for macros, from gSender.
With the exception of those that I will list below, all the keyboard shortcuts work.
The not good
- I have set shift-A and alt-A to jog the A axis. Neither of these work. I canāt see anything else in the shortcut list that these combinations have been set to.
- Setting jogging from precise to normal to rapid does change the jog increment. However, holding down my shortcut keys or holding down the GUI buttons moves the axes at the same speed regardless of the speed selected. (At least this time, I tested with no bit in the router and Z as high as it would go before jogging down.)
- This one seems to be inconsistent. File is running. I hit the pause shortcut=!. The job pauses and a orange/brown āclick to unlock machineā icon appears in the upper right of the visualizer window. Now, sometimes clicking that unlocks the machine and it continues for a few lines,the stops. At that point, I am able to resume using the start shortcut = %. Other times, clicking that does nothing. In fact all is locked up. The only solution is to disconnect and re-connect. Even then sometimes re-connect does not work. The controller needs to be power cycled to get things back to normal.
- I canāt figure out what is triggering this one. When Edge opens, the title bar shows gSender Edge 6. However, after some combination of actions, the title bar changes to just gSender. Not a big deal, but it would be good to know if I am running Edge or gSender since I have a very short memory.
1 Like
I assume the Park function is based on Machine coordinates and not Work coordinates? I actually added Home, Park, and Bit Change macros to the three programmable buttons on the SLB EStop.
Also it would really nice top be able to either change the order of the control panes (i.e., Probe, Macros, Coolant, etc.) on the main window or, better yet, select which ones are even visible (like the Rotary pane). I donāt use the probe or coolant panes and it would be nice to have them not cluttering the interface.
Park uses G53, so entirely machine coordinates.
Thanks and figured. Will have to play around and see if this works better than the programmable buttons solution
This will be the case, but Edge has its own separate settings file (where stats are saved) since itās beta software and we donāt want to risk settings changes in Edge causing problems in main gSender.
@KGN I ran a couple of toolpaths today. I noticed that once a job has started, the disconnect button disappears on the main page. I found it in the tools menu, but I would prefer that it stays on the main page as it does in gSender. Attached is a screencap.
im saying from edge to edge it doesnt transfer
@KGN I reported previously that it was good to see that Edge had brought in all my keyboard shortcuts from my gSender installation - including those assigned to my macros.
Well, it seems that I spoke too soon. Not only are those shortcuts gone in Edge, they are also gone in gSender 1.4.11. The jogging and other shortcuts that apply to basic gSender functions are still there. However, all those assigned to macros are gone.
Yet another release with a number of fixes, look and feel tweaks, and changes.
Config
- Config menu now only shows sections that currently have inputs available in them
- Config hides sections that are filtered or EEPROM only when not connected
- Added a āNon-Defaultā toggle next to the search filter that filters all EEPROM values to those not default to your selected machine profile
- Added some AltMill specific settings to the appropriate sections
- Added warning when not connected that some settings that are EEPROM only may not appear.
- Look and feel changes
Tools
- Surfacing tool had units added, labels corrected, should convert properly based on preferred units, and some responsiveness changes
- Squaring and Calibration tools look and feel and behaviour changes
Shortcuts
- Jog behaviour changes again - should be better now
- Added missing Rapid Position shortcuts
- Rotary shortcut fixes
Dark Mode
- Numerous tweaks to look and feel for legibility
- Gamepad shorcut area again usable in dark mode
Connection
- Work on robustness of auto detect firmware
- Fix for situations where connecting to alarmed machine would result in disconnect state and inability to reconnect
Look and Feel
- Side bar sizing scales appropriately based on monitor size
- Various new icons
- Numerous sizing tweaks to text and interactable elements such as tabs
- A jog icons should now be the correct directions.
- Fixed stats menu to bottom of screen
- Many, many other things
General
- Go To flyout again usable. Labelling improved for incremental and absolute.
- Various remote mode config tweaks
- Updating jog defaults in config should be reflected on main UI
- A number of other changes honestly itās exhausting.
Download
gSender Edge can be found on Github. As always, Edge is BETA SOFTWARE, so if youāre not comfortable with the very real possibility something might go wrong you shouldnāt be using it.
1 Like
@KGN hi both, I noticed this behaviour too (where the spindle is not even close to full speed before the bit is plunged into the workpiece), BUT this also happens in 1.4.12ā¦ so not sure when the bug was introduced.
I see that edge 7 has just been released so will take a look at that, but as I use 1.4.12 as my daily driver, then it would be good if this were fixed across both the beta and public release versions.
One issue I have running Edge is that I run a larger monitor for my screen and I use Windows 10 as my OS. In my display settings I have the Scale and Layout set to 150%.
With non Edge Gsender this scale setting has no impact on the UI in GSender but with new Edge Gsender it does and cause parts of the UI to need to scroll.
