Is your feature request related to a problem? Please describe.
For our printers we do need multiple background tasks to be performed and some should be scheduled every x ms (currently ranging between 100ms and 10s).
Additionally for the (internal) scheduling, logging and synchronization with external systems we want to have at least ms resolution on a timestamp and it should be usable with simple g-code meta commands.
Describe the solution you propose.
In order to not implement this as new modules for the firmware and because it seems to be working fine we are using the deamon to schedule the calls to macros that execute the required tasks.
Currently there are state.time and state.msUpTime which are derived from a single source.
For now I recombine them in daemon.g as a global variable and have a custom rollover implemented.
It would be much appreciated to have access to the base time source with ms resolution and graceful rollover behavior via the object model.
Describe alternatives you've considered
Currently using a self made solution in daemon.g based on state.time and state.msUpTime and a global variable.
Provide any additional context or information.
No response
Is your feature request related to a problem? Please describe.
For our printers we do need multiple background tasks to be performed and some should be scheduled every x ms (currently ranging between 100ms and 10s).
Additionally for the (internal) scheduling, logging and synchronization with external systems we want to have at least ms resolution on a timestamp and it should be usable with simple g-code meta commands.
Describe the solution you propose.
In order to not implement this as new modules for the firmware and because it seems to be working fine we are using the deamon to schedule the calls to macros that execute the required tasks.
Currently there are
state.timeandstate.msUpTimewhich are derived from a single source.For now I recombine them in daemon.g as a global variable and have a custom rollover implemented.
It would be much appreciated to have access to the base time source with ms resolution and graceful rollover behavior via the object model.
Describe alternatives you've considered
Currently using a self made solution in daemon.g based on
state.timeandstate.msUpTimeand a global variable.Provide any additional context or information.
No response