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

Why is a M-BUS slave board needed? (and not a master board) #35

Closed
B48D81EFCC opened this issue Nov 9, 2023 · 4 comments
Closed

Why is a M-BUS slave board needed? (and not a master board) #35

B48D81EFCC opened this issue Nov 9, 2023 · 4 comments

Comments

@B48D81EFCC
Copy link

Hello,

I am wondering, why we need a slave board in this case?
I would assume that the ESP32 is the master and the meter (e.g. Kaifa) is the slave.

I hope you can wipe out my lack of knowledge.

@DaPeace
Copy link

DaPeace commented Nov 29, 2023

The Kaifa is the master and is just pushing the data to the slave one-way. Thats why you need a slave-board.

@B48D81EFCC
Copy link
Author

Hi,

okay thanks! I am wondering why Kaifa is the master. Is it configurable? Can the Kaifa device be the slave?

If Kaifa is always the master, this would prevent to add other slaves to the M-Bus, isn't it?

@Soundrico
Copy link

you can add other slaves to the mbus eg water or gas meters, etc

@B48D81EFCC
Copy link
Author

Ah sorry. Yes, other slaves can be added to the bus of course.
Hopefully the other devices like gas or water meters are not a master as well.

I was just surprised that the Kaifa device is a master, since M-Bus is a single master bus.
I think (for max. flexibility) the bus master should be a separate device.

Thanks for the clarification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants