From 7028ea51271a19a6fdcd8e67a7a9a9bda88c971f Mon Sep 17 00:00:00 2001 From: Steve Zingman Date: Tue, 14 Feb 2017 11:13:13 -0500 Subject: [PATCH] Created Burst timing being outside the acceptance window of the repeater (markdown) --- ...tside-the-acceptance-window-of-the-repeater.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 Burst-timing-being-outside-the-acceptance-window-of-the-repeater.md diff --git a/Burst-timing-being-outside-the-acceptance-window-of-the-repeater.md b/Burst-timing-being-outside-the-acceptance-window-of-the-repeater.md new file mode 100644 index 0000000..c2d8fae --- /dev/null +++ b/Burst-timing-being-outside-the-acceptance-window-of-the-repeater.md @@ -0,0 +1,15 @@ +Some handhelds appeared to work but the repeater didn't see the voice packets. It was due to the burst timing of the handheld being outside the acceptance window of the repeater. There was quite a variation between radios. + +If that is your problem you could try the following... + +in the MMDVM firmware DMRSlotRX.cpp module you will find the following lines:- + +const uint16_t SCAN_START = 400U; const uint16_t SCAN_END = 490U; + +These define the acceptance window. You could try decreasing SCAN_START to 390 and increasing SCAN_END to 500. + +Having a wider window puts more load on the DUE so don't make it too large. + +Of course this may not be your problem but its worth a try. + +Colin G4EML