Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE]-System Monitor - Expose program reset, processor reboot, and appliance/server feedback (SIMPL Bridging) #1053

Open
jkdevito opened this issue Jan 24, 2023 · 5 comments
Assignees
Labels
enhancement New feature or request planning

Comments

@jkdevito
Copy link
Contributor

Describe the solution you'd like
Add support to the System Monitor class and bridge for the following

  1. Program reset
  • Ideally implemented with a press&hold
  1. Processor reboot
  2. Feedback on whether the code is running on a server vs. an appliance

Additional context
We must consider how these updates may also affect a server and whether they would add benefit or need protection when Essentials runs on a server.

@jkdevito jkdevito added the enhancement New feature or request label Jan 24, 2023
@jkdevito jkdevito self-assigned this Jan 24, 2023
@ndorin ndorin changed the title [FEATURE]-System Monitor - Expose program reset, processor reboot, and appliance/server feedback [FEATURE]-System Monitor - Expose program reset, processor reboot, and appliance/server feedback (SIMPL Bridging) Jan 26, 2023
@ndorin
Copy link
Contributor

ndorin commented Jan 26, 2023

@jkdevito Can you confirm our assumption that this feature would enhance SIMPL bridging only, as the rest of this is accessible natively in S# Pro?

@jkdevito
Copy link
Contributor Author

jkdevito commented Jan 26, 2023

Correct, this would be a feature to expose the program reset, processor reboot, and appliance vs. server FB on the system monitor EISC in SIMPL, allowing developers to maintain a consistent implementation regardless of the processor type defined in SIMPL.

@jtalborough
Copy link
Contributor

@jkdevito. just checking. Any movement on this by chance?

@jkdevito
Copy link
Contributor Author

jkdevito commented Sep 7, 2023

It appears to have been merged in on PR #1070 . If that is correct we can close this feature request.

@jkdevito
Copy link
Contributor Author

jkdevito commented Sep 7, 2023

Looking closer at the PR, it appears to only have been merged into development.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request planning
Projects
None yet
Development

No branches or pull requests

3 participants