k3ldar / gsendpro Goto Github PK

Not when simulating
What to do on error

Need a better way of selecting between servers when connecting from a client

To be determined

Test license so user can test without purchase

For scenario where a user has a pallet changer etc

This would allow the override to be precisely used if GCode contains z up with G0 (rapid)

Validate GCode commands against firmware to ensure they are all supported

M commands for
Post/put/get/delete (only one can be selected for each call)

G Commands for parameters including:

Accept header
UserAgent
Timeout
Basic Auth (personal access token)

Optionally validate response to ensure it is what is expected.

This would allow a user to have a single server installation and client installs on remote computers

Process to issue a new license after purchase and verify it is valid

As a user I would like a tray icon that can be used to:

• Control service (stop/start)
• Manage Plugins

As a developer I would like an easy to use plugin interface so as I can easily extend GSendPro, via service, sender and editor

Build in for updated version and automatic download (ready to install)

As a user it would be handy to have a wizard which can help tune a Grbl machine

Same as title, more required for the installer to automatically register plugins etc

Could be on a layer by layer basis or a slider which increments/decrements the code up to that position

also determine if z top/bottom

Create reports on crash management for easy oversight

As a user I would like the ability to select file associations when installing the product

Page about service scheduling

Allow sub programs to be viewed as part of the editor (collapsible code)

After initial release of v1.0

Predefined and allow custom items which form part of the servicing schedule. Allow to be defined whether it's interim or full service.

Also allow dynamic items to appear as defined from www.gsend.pro

FluidNC support as firmware type: http://wiki.fluidnc.com/en/support/gcode_senders

Currently uses generic settings, would be nice to use actual settings when used through GSender

Allow machine selection in gcode viewer for more accurate time settings

Might not be wise as could be dangerous, but food for thought at the moment

Within 2d view, highlight the safe moves so they are easily visible

Allow version history for sub programs so a user can easily see when / what changed

Description on how they are used etc

Where it makes sense

Allow the active XY coordinates to be automatically magnified

After loading a machine in desktop, jog speed is not remembered

Allow command to verify the height and position of the current tool.

This might require hardware to be installed that can be used as a "touch point"

Allow a view which show the visual representation of G55 through G59 so they can be viewed by a user

Extend to have tool length which is then used when probing a static Z position to help speed things up so time is not wasted when probing

It would be nice to have a key logger facility to indicate what the user has pressed when running a machine

To install plugins from online

Allow the maximum line length to be adjusted via settings