- Allstar-Digital - lists.keekles.org

Dmrlink.log
by Robert Newberry 20 Dec '15

20 Dec '15

Should I be doing anything with my dmrlink.log? I have a 16gb card installed, I just didn't know if I should change settings once things are connected and working. N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658

2 2

Success!
by Robert Newberry 19 Dec '15

19 Dec '15

Steve, I got my node 42657 peered to you. I don't have my repeater connected because I left my programming cables at work. Looking at my log it should be OK. N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658

1 0

PiDV / DV3000
by Michael Hebert 19 Dec '15

19 Dec '15

Steve, I received my PiDV this afternoon. I was going thru and making sure I had all the dependencies taken care. I notice there was a problem with update-rc.d AMBEserverGPIO start 50 2 3 4 5 root@repeater:/srv/DV3000# cd /etc/init.d root@repeater:/etc/init.d# update-rc.d AMBEserverGPIO start 50 2 3 4 5 update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults I hope to have everything up and running tonight. I will have node 28304 link to my dmr repeater. Michael KD5DFB

2 4

Fwd: [MTUSA] Fwd: [pnw-dmr] Re: Tytera MD-380 Digital Timing Issue
by Robert Newberry 18 Dec '15

18 Dec '15

Has anyone else seen this? I am forwarding it from another list. I'm not doing this to trash the md-380, it's technical and I thought the list might want to see it. N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658 ---------- Forwarded message ---------- From: "Mike N07RF no7rf(a)trbo.org [mototrbousa]" <mototrbousa(a)yahoogroups.com > Date: Dec 17, 2015 8:29 PM Subject: [MTUSA] Fwd: [pnw-dmr] Re: Tytera MD-380 Digital Timing Issue To: "mototrbousa" <mototrbousa(a)yahoogroups.com> Cc: I am forwarding this information as it is near first person and involves Aeroflex actually taking a look at the problems that we have been hearing with hams using the MD-380. While the 380 users may not appreciate the issues, those who do hear them, should. I've neutered the attribution only as I don't have permission to forward the post. At this point, I'd caution folks to consider looking at other DMR radios, if not for their first DMR radio, then for their move up with subsequent purchases. If a MotoTRBO radio is not on your RADAR, then the CS-750 has a great value to cost ratio and is DCI's recommended alternative if cost thrumps compatibility. -- Mike, NO7RF, Mazama Washington, no7rf(a)trbo.org <no7rf(a)trbo.org?subject=Reply+to+my+.sig>, www.trbo.org == == == == == == Forwarded message == == == == == == >From : <pnw-dmr(a)yahoogroups.com> Date : Thu, 17 Dec 2015 17:14:59 -0800 Subject : [pnw-dmr] Re: Tytera MD-380 Digital Timing Issue == == == == == == Forwarded message == == == == == == Here is another Tytera MD-380 observation. (In) December, I attended a digital radio service presentation by the well-known service monitor company Cobham/Aeroflex. I brought my 450 MHz MD-380 along. After the presentation, I asked Mike Fortna of Aeroflex to take a look at the infamous MD-380. He said Tytera had contacted them about developing an Autotest routine for Tytera products, so Mike was interested in seeing the Tytera MD-380's alignment. Testing was done on 441 MHz Simplex and again on TS1 on the Gunnysack pair with the Cobham/Aeroflex 8800S Digital Radio Test Set. The 4FSK modulation was perfect. Mike had just been explaining that most problems with alignment are revealed on the 4FSK display, but the Tytera was perfect. I asked him to look at the energy in each timeslot. I think this display is called the power profile. The graphic showed timeslot 1 and 2 simultaneously. What was observed was a non-standard rise time when keying the transmitter. The power in timeslot 1 came up about half of maximum, hung there for a few uS, then went to full power. It was not a nice rounded envelope. It was a stair step. No overshoot was observed. Other than the "stutter" in reaching full output, the waveform was mostly normal. The abnormal condition was likely caused by the "stutter" in rise time. This abnormal condition is RF energy "spilling over" into timeslot 2 in this case. It seemed to appear in timeslot 2 for the same duration as the stutter in the timeslot 1 rise time. Mike Fortna of Aeroflex found it interesting enough to take a screen shot. He stated it was a better example of a DMR power profile alignment problem than what he was currently using. The same waveform anomaly occurred on Simplex and Duplex. Rapid keying, de-keying and keying again made no difference in the waveform. I have read that transmitting on both timeslots simultaneously was a "feature." This doesn't seem to be true. I didn't have time to test on timeslot 2. Testing was rushed because everyone knew that Seattle traffic was building! Further, more comprehensive testing is required with a greater pool of radios. It would be interesting to test some high-band models as well. Does anyone have an IFR3920 or 8800S with the DMR option? This only meant to be a verbal description of the graphical representation of an anomaly in my particular MD-380's timeslot power profi le. Your mileage may vary, as they say. -- Mike, NO7RF, Mazama Washington, no7rf(a)trbo.org <no7rf(a)trbo.org?subject=Reply%20to%20my%20.sig>, www.trbo.org __._,_.___ ------------------------------ Posted by: Mike N07RF <no7rf(a)trbo.org> ------------------------------ Reply via web post <https://groups.yahoo.com/neo/groups/mototrbousa/conversations/messages/2982…> • Reply to sender <no7rf@trbo.org?subject=Re%3A%20Fwd%3A%20%5Bpnw-dmr%5D%20Re%3A%20Tytera%20MD-380%20Digital%20Timing%20Issue> • Reply to group <mototrbousa@yahoogroups.com?subject=Re%3A%20Fwd%3A%20%5Bpnw-dmr%5D%20Re%3A%20Tytera%20MD-380%20Digital%20Timing%20Issue> • Start a New Topic <https://groups.yahoo.com/neo/groups/mototrbousa/conversations/newtopic;_ylc…> • Messages in this topic <https://groups.yahoo.com/neo/groups/mototrbousa/conversations/topics/2982;_…> (1) MTUSA website: http://groups.yahoo.com/group/mototrbousa/ Visit Your Group <https://groups.yahoo.com/neo/groups/mototrbousa/info;_ylc=X3oDMTJmZTNpdHA5B…> - New Members <https://groups.yahoo.com/neo/groups/mototrbousa/members/all;_ylc=X3oDMTJnNG…> 4 [image: Yahoo! Groups] <https://groups.yahoo.com/neo;_ylc=X3oDMTJlNGthOTRxBF9TAzk3NDc2NTkwBGdycElkA…> • Privacy <https://info.yahoo.com/privacy/us/yahoo/groups/details.html> • Unsubscribe <mototrbousa-unsubscribe(a)yahoogroups.com?subject=Unsubscribe> • Terms of Use <https://info.yahoo.com/legal/us/yahoo/utos/terms/> . __,_._,___

2 2

Re: [Allstar Digital] DV4MINI working
by Robert Newberry 17 Dec '15

17 Dec '15

Well my laptop running ubuntu is a 32 bit machine. I noticed that dv4m.ham.dmr.ch only offers a 64 bit download for 15th December 2015. I reinstalled the 25th September 2015 and everything works again. So for the lack of information, I figured it was "encouraged" to read the documentation and work thru the problem myself. Rather than asking someone to solve it for me. N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658

6 21

DV4MINI working
by Robert Newberry 16 Dec '15

16 Dec '15

Ok got my dv4mini working on ubuntu. Who's on the air for a quick hello? N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658

5 19

P25
by Michael Hebert 16 Dec '15

16 Dec '15

All, Not that I need another iron in the fire but, Has anyone experimented with P25 yet? My guys here in Houston are chomping at the bit especially since seeing what we are doing with DMR. Michael KD5DFB

2 1

DV4M and DMRlink
by Robert Newberry 15 Dec '15

15 Dec '15

I came home and my DV4M showed up in the mail today and I brought home my 8300 to start testing with dmrlink. Now I don't know which project to start tonight! N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658

2 1

Masters, Peers and bridges, oh my
by Steve Zingman 15 Dec '15

15 Dec '15

I'm going to try to flesh this out. Consider the following IDs 21000 C-Bridge Master With talk groups, 1,2,3 12345 DMRlink Peer 54321 DMRlink Master 56789 Mototrbo repeater peer 98765 Mototrbo repeater peer 12345 is pointed at 21000 12345 bridges with 54321 Talk Groups 1 and 2 are bridged. 56789 is pointed at 54321 98765 is pointed at 54321 See the rules below: RULES = { '12345': { 'TRUNK': False, 'GROUP_HANGTIME': 5, 'GROUP_VOICE': [ {'SRC_GROUP': 1, 'SRC_TS': 1, 'DST_NET': '54321', 'DST_GROUP': 1, 'DST_TS': 1}, {'SRC_GROUP': 2, 'SRC_TS': 1, 'DST_NET': '54321', 'DST_GROUP': 2, 'DST_TS': 1}, ], 'PRIVATE_VOICE': [ ] }, '54321': { 'TRUNK': False, 'GROUP_HANGTIME': 5, 'GROUP_VOICE': [ {'SRC_GROUP': 1, 'SRC_TS': 1, 'DST_NET': '12345', 'DST_GROUP': 1, 'DST_TS': 1}, {'SRC_GROUP': 2, 'SRC_TS': 1, 'DST_NET': '12345', 'DST_GROUP': 2, 'DST_TS': 1}, ], 'PRIVATE_VOICE': [ ] } } Example 1: Traffic is "transmitted" by 21000 on TG1 That traffic is "received" on 12345 That traffic is bridged to 54321 because a bridge is defined for TG1 56789 "receives" the traffic on TG1 98765 "receives" the traffic on TG1 Subscriber radios on 56789 receive the traffic on TG1 Subscriber radios on 98765 receive the traffic on TG1 Everybody is happy Example 2: Traffic is "transmitted" by 21000 on TG3 That traffic is "received" on 12345 That traffic is NOT bridged to 54321 because there is no bridge defined for TG3 56789 does NOT "receive" the traffic 98765 does NOT "receive" the traffic Subscriber radios on 56789 do NOT receive the traffic Subscriber radios on 98765 do NOT receive the traffic Everybody is clueless, they hear nothing. Example 3: Subscriber radio transmits to repeater 56789 on TG4 That traffic is "received" on 54321 That traffic is NOT bridged to 54321 because there is no bridge is defined for TG4 98765 "receives" the traffic because 98765 and 56789 are peers on the same network Subscriber radios on 98765 receive the traffic Everybody is happy, The QSO is local and does not leave the local area. -- "Anything is possible if you don't know what you are talking about." 1st Law of Logic

1 0

DMRlink test master and...
by Steve Zingman 15 Dec '15

15 Dec '15

If you point a peer at the test master, please us a repeater id that matches one of your AllStar nodes. That way I can see where the traffic is coming from. On another note, there is a bug in the mk_dmrlink script. It does not copy the sample playback configuration file into the playback directory. from the root prompt: cd /opt/dmrlink/playback cp ../samples/playback_config_SAMPLE.py playback_config.py -- "Anything is possible if you don't know what you are talking about." 1st Law of Logic

2 4