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

[Feature] multiple motors/hubs per train #159

Open
Novakasa opened this issue Sep 1, 2023 · 3 comments
Open

[Feature] multiple motors/hubs per train #159

Novakasa opened this issue Sep 1, 2023 · 3 comments
Assignees
@Novakasa
Labels
enhancement New feature or request

Comments

@Novakasa
Copy link
Owner

Novakasa commented Sep 1, 2023 •
edited
Loading

requested on youtube: https://www.youtube.com/watch?v=cBF-G4d4vw8&lc=Ugyaq-p0Sv_qh-kbco94AaABAg

lots of thinking needed for this one though
@Novakasa Novakasa added the enhancement New feature or request label Sep 1, 2023
@Novakasa Novakasa self-assigned this Sep 1, 2023
@Novakasa
Copy link
Owner Author

Novakasa commented Sep 1, 2023

maybe just have a second ble_train assigned to the layout train? Needs to be in a "puppet" mode, and the other hub will be "master" and have the sensor. Maybe allow for two sensors?

@Novakasa
Copy link
Owner Author

Novakasa commented Sep 1, 2023

The issue will be the communication between the two hubs. If it has to go through the PC, this might take too long. Maybe the pybricks advertising communication might work?

@Novakasa
Copy link
Owner Author

Right not it should probably be the same program running on "puppet" and "master", where master has the sensor. The hubs will detect automatically whether they have a sensor or not and maybe send that to PC, which can sanity check.
Since sensor advance will be sent from master to PC anyway the PC can forward the sensor advance command to the puppet hub. This will have some delay but hopefully not too much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Novakasa Novakasa

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Novakasa