Firmware
0.4.1
Loading...
Searching...
No Matches
Bug List
{task_function.cpp} Member
drv::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?
{task_function.cpp} Member
drv::out::track::dcc::anonymous_namespace{task_function.cpp}::operations_loop
(dcc_encoder_config_t const &encoder_config)
Can't error check here? For some reason transmit_bidi immediately fails in ULF_DCC_EIN mode.
Member
mw::ota::Service::Service
()
should this broadcast Z21 programming mode?
Member
mw::roco::z21::Service::socket
(
intf::http::Message
&msg)
if the socket closes for any reason we're fucked, there must be some way to detect such cases and restart the socket in the Frontend?
Member
mw::zimo::decup::Service::socket
(
intf::http::Message
&msg,
State
decup_state)
should this broadcast Z21 programming mode?
Member
mw::zimo::decup::Service::zppSocket
(
intf::http::Message
&msg)
should this broadcast Z21 programming mode?
Member
mw::zimo::decup::Service::zsuSocket
(
intf::http::Message
&msg)
should this broadcast Z21 programming mode?
Member
mw::zimo::mdu::Service::socket
(
intf::http::Message
&msg,
State
mdu_state)
should this broadcast Z21 programming mode?
Member
mw::zimo::mdu::Service::zppSocket
(
intf::http::Message
&msg)
should this broadcast Z21 programming mode?
Member
mw::zimo::mdu::Service::zsuSocket
(
intf::http::Message
&msg)
should this broadcast Z21 programming mode?
Member
mw::zimo::zusi::Service::socket
(
intf::http::Message
&msg)
should this broadcast Z21 programming mode?
Firmware 0.4.1