You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using Direwolf 1.5 on Raspberry PI 3 with Ubuntu 18.04
All seems to be working fine, except that I can't insert any delay between receiving and digipeating packets. Basically digipeating start immediately after packet is recieved.
Currently I have this in my configuration:
This should give very little chance to transmit at earliest, 1 second after the packet is received. But in reality PTT/digipeating is triggered immediately after packet enters.
Am I missing something or what could be wrong?! Any ideas?
The text was updated successfully, but these errors were encountered:
kandev
changed the title
Ignoric SLOTTIME and PERSIST setting
Ignoring SLOTTIME and PERSIST setting
Apr 5, 2020
None of those values are intended to delay the digipeating function. They are for just interfacing with your specific radio's key up characteristics. The digipeater section has the "DEDUP" feature which can minimize duplication and there is also the "satgate" feature offers a delay as well but I don't think that's appropriate here. Please read the UserGuide for more details on these items as well as the "“viscous” discussion which is supported by APRX but not Direwolf.
As David stated, APRS digipeaters are supposed to retransmit immediately, after the channel is clear, rather than waiting the usual random time. This is intentional.
Uh oh!
There was an error while loading. Please reload this page.
I'm using Direwolf 1.5 on Raspberry PI 3 with Ubuntu 18.04
All seems to be working fine, except that I can't insert any delay between receiving and digipeating packets. Basically digipeating start immediately after packet is recieved.
Currently I have this in my configuration:
This should give very little chance to transmit at earliest, 1 second after the packet is received. But in reality PTT/digipeating is triggered immediately after packet enters.
Am I missing something or what could be wrong?! Any ideas?
The text was updated successfully, but these errors were encountered: