Keeper's Ledger

This is not just a project. This is my call to the future to be free. Make yourself, make things, be yourself. This protocol spans multiple levels, take what you want. It is all documented. Designed to be easy to get in, and get out. You do not need to be an engineer to understand what is happening here, nor do you need to implement all the levels

Send the message, receive the message, do what you want with it. It carries on. Low down to the mosfet, high to the automation and trains. It's all there. Connect what you want. Just build. Don't care about the network, it can handle it. Maybe don't stream audio over it?

enjoy.

Guidelines

To those building or inheriting:

This is to be easy, an eight and and eighty year old should be able to program Beeton decoders with little help outside of this wiki. Document it well, but make it so easy documentation is minimal.

RailCall (Beeton Bridge) is thin, expose the functions needed to communicate. Do not just dump all functions in here. Think of it as 'super public' borrowing words from Java. Public, anyone has access. Super, at a higher level. You get that message, you do not care who sent it, act.

Beeton HA. Also thin, uses RailCall extensively to get the things into HA. Expose, let HA do rules.

Beeton Hive. A basic automation maker. Not as extensively made as HA, make it so it works, but does not replace HA.

Beeton Hive Rail. Replace TrainController. Keep it simple, clean, yet powerful. Blocks, track schematic (not full layout format with curve types), signals, routing, etc. But easy, and allow user to take over. Manual Drive with and without safeties.

Any others. Keep in mind, someone will have to work with this, and they won't know as much as you. Keep it simple, get an eight or eighty year old to test it, and change it until it works. Nothing here is fixed in stone, save for the guidelines here. Breaking these guidelines change the project and disowns the concept of Beeton.