From 9265ebaa9b79fe1563ee500d3869eba57b584a45 Mon Sep 17 00:00:00 2001 From: Cort Buffington Date: Wed, 3 Jun 2015 14:38:58 -0500 Subject: [PATCH] Update --- FAQ.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/FAQ.md b/FAQ.md index 44dd045..f0051c8 100644 --- a/FAQ.md +++ b/FAQ.md @@ -1,7 +1,7 @@ ##DMRlink FAQ **PURPOSE:** Since DMRlink was published, a number of similar questions have come in regarding it's use. This FAQ will attempt to address common questions or concerns. -**Can DMRlink bridge networks like a c-Bridge?** Yes, it can bridge IPSC networks, but no, not not quite like a c-Bridge. DMRlink is able to bridge IPSC networks, it is able to selectively "choose" which TGIDs to bridge and which not to bridge, and it can re-write the TGID, but it cannot change the timeslot of a transmission. If it comes in on TS1, it will have to go back out on TS1. It also does not have automatic scheduling or "trigggering" of bridge events. +**Can DMRlink bridge networks like a c-Bridge?** Yes, bridge.py can bridge IPSC networks, but no, not not quite like a c-Bridge. It does not have automatic scheduling or "trigggering" of bridge events. Currently bridge rules must all be static. **Someone said DMRlink "bricked" their repeater, is it safe to use?** DMRlink has no abilty to speak the XNL/XCMP protocol (which involves encrypted keys) that Motorla uses to control radios and repeaters. DMRlink simply cannot even remotely speak the language necessary to do this.