From: Bernd W. <f.j...@t-...> - 2021-04-14 12:37:32
|
Dear Harald, Thank you for the warning about decoders and also for the analysis made at https://www.stacken.kth.se/~haba/slamra/dcc/ackpulse/. The TAMS decoders which I use provide ACK only for reading some CVs ond not for others. Verifying works better. (For fairness it should be mentioned that they don't offer ACK as a feedback method in their document, only RailCom.) The wiring which I use is based on your https://www.stacken.kth.se/~haba/slamra/dcc/ackdetect/ - Thank you for having shared that. Bernd Am 22.03.21 um 13:02 schrieb Harald Barth: >> - ACK-detection for NMRA programming. Theoretically, supporting the RI line by Patch 13 should already provide >> the functionality, but practically, the self-made low cost wiring used by me needs more programming for timing >> and signal detection. > > As I have had part of the code that does the ack detect in DCC++EX > https://dcc-ex.com/ I can tell you that ack detection is a major PITA > because many decoders do _not_ do what they should according to NMRA > spec. Especially considering the so called 6ms pulse timing. We now > allow ack pulses from 2ms to 12ms and have runtime tunable ack pulse > level and duration. Some decoders need more startup time (reset > packets) as well. > > Harald. > |