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.

Sign up for GitHub

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

Jump to bottom

Duplicate Actuator values in DB when upscaling project #45

Open
4 tasks
Willmish opened this issue Mar 12, 2022 · 0 comments
Open
4 tasks

Duplicate Actuator values in DB when upscaling project #45

Willmish opened this issue Mar 12, 2022 · 0 comments
Assignees
@Willmish
Labels
bug Something isn't working enhancement New feature or request future extension outside of client requirements
Milestone
Final submission

Comments

@Willmish
Copy link
Owner

  • If the project is to ever be upscaled (more sensors in each subsystem), each sensor will still be sending data with its current value, and the current actuator value, so we will have duplicate acutator values for those readings.

Another issue:

  • If more actuators are in the system, storing the actuator ID and type will also be necessary

To consider:

  • Separate Table just for the actuator values or Sensor types and actuator values
  • Store all IDs and actuator values
@Willmish Willmish added bug Something isn't working enhancement New feature or request labels Mar 12, 2022
@Willmish Willmish added this to the Final submission milestone Mar 12, 2022
@Willmish Willmish self-assigned this Mar 12, 2022
@Willmish Willmish added the future extension outside of client requirements label Apr 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Willmish Willmish

Labels
bug Something isn't working enhancement New feature or request future extension outside of client requirements
Projects
None yet
Milestone
Final submission
Development

No branches or pull requests
1 participant
@Willmish