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

Warn about controlling mutliple engines with same address #260

Open
nic547 opened this issue Jul 25, 2022 · 0 comments
Open

Warn about controlling mutliple engines with same address #260

nic547 opened this issue Jul 25, 2022 · 0 comments
Labels
type:enhancement New feature or request
Milestone
0.1.0

Comments

@nic547
Copy link
Owner

nic547 commented Jul 25, 2022

For engines with a non-zero address, acquiring a second engine with the same address should be impossible and warn the user about the fact that another engine with the same address is already active.

For engines with dcc address zero it is assumed that those addresses are controlled by the CommandStation.
@nic547 nic547 added the type:enhancement New feature or request label Jul 25, 2022
@nic547 nic547 added this to the 0.1.0 milestone Jul 25, 2022
@nic547 nic547 moved this to Backlog in TauStellwerk Jul 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type:enhancement New feature or request
Projects
TauStellwerk
Status: Backlog
Milestone
0.1.0
Development

No branches or pull requests
1 participant
@nic547