Member decup::Service::socket (http::Message &msg, State decup_state): should this broadcast Z21 programming mode?
Member decup::Service::zppSocket (http::Message &msg): should this broadcast Z21 programming mode?
Member decup::Service::zsuSocket (http::Message &msg): should this broadcast Z21 programming mode?
Member mdu::Service::socket (http::Message &msg, State mdu_state): should this broadcast Z21 programming mode?
Member mdu::Service::zppSocket (http::Message &msg): should this broadcast Z21 programming mode?
Member mdu::Service::zsuSocket (http::Message &msg): should this broadcast Z21 programming mode?
Member ota::Service::Service (BaseType_t xCoreID): should this broadcast Z21 programming mode?
{task_function.cpp} Member out::track::dcc::anonymous_namespace{task_function.cpp}::make_offsets (): DCC/RailCom timings seem to get worse when the DCC tasks runs the second time?
Member out::track::get_current_limit (): currently ignored... should be 500mA for DCC serv, MDU and DECUP, user setting for DCC op
Member z21::Service::socket (http::Message &msg): if the socket cloases for any reason we're fucked, there must be some way to detect such cases and restart the socket in the Frontend?
Member zusi::Service::socket (http::Message &msg): should this broadcast Z21 programming mode?