Jun 09 2017

Android DMR M1DU – First 24 Hours

So after a lot of consideration and some collaboration with Bob (W2CYK) regarding c-Bridge integration into the RFinder application, I decided to pull the trigger and get one of the android/radio devices.  The M1DU is a ruggedized Android 6 Phone plus a 77UHF FM/DMR Transceiver.

After playing around with it for a few hours and figuring out how it worked, I decided to take the plunge and pull the SIM from my Samsung Galaxy S7 and put it in the M1DU and begin the process of converting it to my daily carry device.

As with any Android device, while the base OS is the same, the interfaces, etc., are a bit different and it’s taken some getting used to moving from my trusty S7.

I have to admit, being able to pull up and application that knows where you are, choose a repeater and hit a button and you’re ready to TX, it very nice.  However, along with that model comes a paradigm shift.  Gone are the ideas of zones, channels, scan lists, etc.  Basically you have a single channel that can be programmed with a couple of touches.  It’s taken me a bit to get used to, but once I’ve adjusted the way i think, the idea has merit.  I do think there is room there for “presets” which would be tied to the 16-position channel selector on top.  Additionally, I’d like to see some sort of scan, although Bob said currently, it’s just too slow, which while disappointing, I’ve seen similar in other radios.

I also think there needs to be a one button talk around option.  The good thing is that in my discussions with Bob, he’s open to development ideas and acknowledges that he’s new to DMR.  However, for being new to DMR, he has a good handle on the basics.  I will be working with him to automatically pull talkgroup info from c-Bridges and import into the RFinder DB.  Right now, Brandmeister enjoys that ability.

At any rate, during my first 24 hours, I made a list of observations that I felt worth noting.  Some of these I’ve talked to Bob about and will add those comments as well.  So here we go:


1). No PTT tones?  Impossible to tell if you’ve successfully hit the repeater.
  • So this one is a biggie.  There is no tone at all when you key up the radio.  On analog or digital.  While a mere convenience on analog, on DMR those tones confirm you’re into the repeater and have a time slot.  The good news here is that he’s working with the developers to implement the PTT tones.  I’m not sure how much influence that I’ll have here, but I intend to make the suggestion that it’s optional and selectable for both modes.  Also, a bonk or DMR failure tone will also need to be implemented.
2). No scan?  Nuisance delete?
  • As mentioned above, there currently is no scan.  Bob was talking about the scanning of frequencies, etc., whereas I was thinking more of a TG scan on a given repeater.  I’m not sure what can be worked out here, but we’ll see.
3). Any concept of zones?  Or are you just expected to re-program when you move between machines?  I realize you can have multiple machines in the one zone you get, but we typically organize the TG’s with one machine per zone.
  • This is where the paradigm shift takes place.  There is no need for zones, channels or code plugs.  You select a repeater, analog or DMR, then select the TG you want to be on and hit “Send to Radio” and you’re done.  It’s very easy and very intuitive, although it flies in the face of conventional practices.  Again, I still see the need for presets, etc.  Once we get the c-Bridge integration working, we’ll re-examine this and perhaps re-evaluate.
4). I’ve had the PTT app crash a few times.  Is there any debug or data I can gather/report to fix that?
  • So I was not aware, but the RFinder App integrates directly to the internal radio.  There is also an app called PTT, that someone just opening the box would gravitate toward.  I did.  It’s also the only app covered in the documentation which is very basic.
5). I’ve had the radio stick on PTT 2-3 times, which is a bit scary, but the red light wasn’t on, yet I was stuck in transmit.  The only way to clear it was to switch channels.
  •   So far, while using only RFinder, I have not had a situation where PTT locked open, however, I have had at least one occurrence of the radio shutting down, even though the LED indicated that it was active.
6). Can the channels be named or the voice files changed?
  • Again, this refers to the PTT app.  no need for this in the RFinder app.  Also contact info is automatically populated in RFinder vs. PTT.
7). What is the POC button?  It is indicated in the manual, but no explanation given.
  • PoC = PTT over Cellular and it intended for use in applications like Zello.  Although Bob tells me there is currently a bug in it’s implementation.  I don’t recall the specifics of the bug, perhaps we didn’t really go into it.  I might install Zello just to check it out.
8). Same goes with the button between the power connector and the power button.  Can either of those be programmed or used?
  • This button is currently not programmed for use, but that options exists based upon my take-away from my call with Bob.
9). I saw in the setup the unit seems to support two SIMs.  Is this true?  I have a vacation phone that I could consolidate, if that’s the case.
10). In the receive groups what does Ref_Times mean?  I typically do not use receive groups, but found yesterday that the radio would not unmute unless I had a receive group with the TG in it.
11). When switching between high/low power the verification prompt always appears, even though you check the no longer prompt box.
We ran out of time for the last three questions.  When I get those answers, I will update this post.
Since this list, I’ve made a few additional observations:
12). Bluetooth seems to be a bit flaky.  I pair my phone with Ford’s Sync in my 2011 F150.  All of my other phones work flawlessly, but the M1DU seems to disconnect randomly.  This is still under investigation.
13). In speaking with Bob, the manufacturer assures him Android 7 is an option for this platform.  I’m eagerly awaiting that.  Perhaps that would have eased my transition from my S7.
One cool thing is the charging jack.  It’s very similar to the Mac Lock on the Apple MacBooks.  I’m a Mac Guy for the most part and I just upgraded to a new MacBook without the Mag Lock charger.  I think that is one of the dumbest moves Apple has made.  USB-C is nice, but it’s not nearly as rugged.
Battery life has been great.  It has a 6200mAh battery.  I’ve run it all day with both the radio and phone and bluetooth on and when I get home I’m usually ~60% of the battery left.
That’s all I have for now.  I have the device paired with one of my Android Wear Smart Watches and used it daily.  So far so good.  Installing other android apps is just like one would expect and thus far, I’ve run into no real nuances beyond the differences in Android 6 and 7 and the button differences.
I’m sure I’ll have more as I continue to work with the unit, but at this point, I like it.  There are some things to get used to, but it’s a different piece of gear.  The ability to consolidate two device into one, even with the slight increase in size appeals greatly to me.

Mar 06 2017

NF9K Technical Specialist Report – February 2017

Provided some assistance to an Indiana HAM regarding the Raspberry Pi. He’s building an AllStar node and also looking into the RTCM units to build out a simulcast system. This will be an interesting project to follow. Last I heard from him, he’s purchased GPS references for each RTCM. Simulcast is nothing without perfect timing.

Continued work on building out the infrastructure for the Indiana Quantar Network (IQN). We opted to go with VPN connections between the core and each site. Doing so eliminated holes in the firewall and static IP requirements. It also makes the entire infrastructure available from a single point. I wrote documentation for configuring the VPN, so that we can keep everything standardized, I still need to write the documentation for the Cisco routers. Our efforts have literally been brick by brick…. As an example, you obtain the proper Cisco router, then you have to buy the right cards for digital and analog audio, the right cables and adapters to connect to your Quantar. You also require DSP resources in your router to run mixed mode, and then there is all the planning for each repeaters ports, subnets, IP addresses, VPN tunnel config, etc. But it’s coming together. As I write this, three tunnels are up and two repeaters on online with a couple more to come very shortly. While the following techinically happened in March, The first official P25 QSO on the IQN too place on 3/4/2017 @ 02:41UTC between K3HTK and NF9K. This was a huge milestone given all the work we’ve put in thus far and really paves the road to shift into overdrive now! We’ve established an FB Group for the IQN (https://www.facebook.com/groups/1742372622743134/) Come join us!

I received a comment via my website from an 8-Call asking about the Henry Amplifiers that I currently use. He was interested in using one for DMR, which I am doing and was curious since the website mentions analog only. Since the DMR repeater brings up both time slots at one time, they will work with most amplifiers, however DMR portables and mobiles will not. Before I purchased the one I have in service, I consulted with the folks at Henry and the confirmed that they work fine with DMR. I shared what I’d learned and my experiences.

Participated as a VE for the WD9BSA VE Team on 2/11/17. We had five come in to test and we gave exams on 10 elements. All in all, we added four new hams to our ranks. (2 General from zero, 1 General Upgrade and one Tech).

As mentioned in last months report, I’ve been working with the developers of the c-Bridge on their implementation of the SIP protocol. In addition to discovering a bug right out of the gate, I found some major issues with release 9032. It would only run for 2-3 days before becoming completely unresponsive. The issue did not manifest itself on a local-traffic c-Bridge as IN-2 had no issues. But IN-1 has the right combination to trigger whatever it is. After multiple attempts and captures of various system stats during the periods working up to a crash, I ended up sending all the data I had to the devs and downgrading to restore system functionality.

On the topic of SIP and the c-Bridge, I’ve successfully been able to initiate a phone call by keying up a talkgroup and conduct two-way communications. Very similar to the functionality of the Echolink client for smart phones. I was able to get the c-Bridge to register as a client to my FreePBX installtion allowing me to pick up a phone and “dial” a talkgroup again establishing two-way communications. I also configured an open conference and had the c-Bridge call and join the conference whenever a talkgroup was keyed up. I then used a SIP phone to also call the conference. The only catch was the conference is designed not to pass DTMF becasue it’s used for conference control, so I could not toggle TX/RX via the phone in this configuration. My next step will be to test with a SIP client on my smart phone. But if all works like I expect, I could offer DMR/talkgroup connectivity to users in a similar fashion to what Echolink does. We’ll see how things go. The IQN is taking a lot of my cycles, but the c-Bridge SIP setup is definitely high on my list of things to work on. I will say that I’m learning a lot on how the c-Bridge works under the hood…. And how to manipulate the system from the linux shell.

Received an email from a 7-Call asking about assistence configuring a Cisco router for P25 Quantar Linking. We exchanged a few emails and I was able to get him on the right path.

Programmed up some Motorola 33cm HT’s (MTX) for a local ham. Which meant I had to dig out the DOS laptop! But it worked fine and after programming one, I was able to do partial clones to the other two. In return, he presented me with a nice Moscato, which promptly went to the XYL. If she’s going to benefit from my work in Ham Radio, shouldn’t she at least get her ticket?!?!?!?!

I was ask once again to present at the Indianapolis Hamfest. They seem interested in another Raspberry Pi presentation. I’d be interested in hearing from folks on what they’d like to see. So if you have any ideas, please shoot me an email (bill@nf9k.net).

I’ve started thinking about building an ADS-B setup similar to what K3HTK has done, but likely without the solar aspect. There is just a cool factor about snagging that info out of the air and displaying it on a map.

When I first started with the IN-1 c-Bridge, Mike Shirley (N07RF) was a huge help. He was a fantastic mentor and teacher and we spend many hours in email, on the radio, even on the phone as he helped me through the learning process. He just recently inquired about SIP capability to the c-Bridge Devs and they referred him to me. The student becoming the teacher is definitely a great feeling and it was awesome to give back to someone who’s given me and the rest of the DMR community so much.

On the same note, I was also hit up my W2AXB, who like Mike, was interested in SIP on the c-Bridge. I was amazed at how quick news traveled that I was working on that stuff. Both guys were looking for the ability to have the c-Bridge function as an autopatch similar to analog repeaters used to do. While the c-Bridge implementation of SIP isn’t far developed, I still have an idea involving an FXO gateway that I’m hoping to try when I can find some time.

Received a website comment from an HK2-Call regarding the DR1X Fusion repeater. He was looking for help regarding the TOT settings and APRS integration. I’m still working with him on these issues.

Helped K3HTK through the process of requesting AMPRNet IP space. We’ll start building routers in a couple of weeks to deliver the IP space to his house…..

Received an email from the Purdue University Amateur Radio Club. They are interested in joining the IQN and after a few emails, we believe the have all of the necessary gear at this point. Once finals are finished for them, we’ll be bringing them online. They will be doing P25 only.

Boy, I think that’s it. It’s been a busy time, but I’m loving every minute of it. Nothing like going downstairs to the Laboratory and walking around looking at things, thinking, I could work on that, or that or this, or…. What a hobby!!!

Jan 26 2017

AMPRNet Public IP Space

For those who are unaware, public IP space ( is available to licensed amateur radio operators.  This space is available in standard CIDR blocks (/29, /28, /27, etc).  It can be utilized in one of four ways:

  1. Radio
  2. Tunnel
  3. Direct
  4. Children

For a detailed description of each of these types, please visit the AMPRNet website: www.ampr.org

In my case, I applied for an received a /22 block of IP’s, which amounts to 1022 usable addresses.  This space can be subnetted down to smaller blocked and distributed throughout your Amateur Radio IP Network as needed.

I chose to go the Direct route (pun intended) which utilizes BGP (Border Gateway Protocol) to host the IP space.  This process involved requesting an LOA from AMPR, locating an on-line cloud provider who will support BGP peering (I used www.vultr.com at the recommendation of a fellow ham), configuring a router (I used vyos, https://vyos.io/, on a virtual machine), and then configuring BGP for my space.

Once this was complete, I built a VPN tunnel to another router in my home network.  In this case, it was another vyos instance and established an OpenVPN tunnel between the two.  Once the VPN tunnel was up and running, I built out an OSPF (Open Shortest Path First) router instance to bring the IP block in via the tunnel.  Most ISP’s that service the home will not let you peer BGP directly, hence all of the above.

As the project stands right now, I have a dummy interface configured on my home router and I’m able to ping it via the internet.  The plan is to replace all of my public-facing internet resources that are dedicated to Amateur Radio with one of these AMPRNet IP’s.

It’s been a lot of fun and a lot of frustration getting all this up and running.  Special thanks goes out to Stephen Brown (K1LNX) and Brian Walls (KD9GFX) for their assistance in figuring out exactly how to do this.  Until today, this was merely an idea we’d all shared and now it’s a reality!

More to come…….


Jan 06 2017

NF9K ARRL Technical Specialist Report – December 2016

Received an email comment via my website looking for assistance in programming a 33cm Motorola MTX9250.  After a primer on topics such as personalities, CPS modifications for ham band use, he was off to the races with his shiny new HT!
Finished building and testing a Raspberry Pi based EchoIRLP node for Steve Jones (W9SMJ).  I’m still waiting to meet up with him to deliver the final product, but he will be pleased.  I know he’s looking to get his node connected up to Randy Fisher’s node that I built a couple of months ago.
Worked with Randy (K9MMQ) up in Ft. Wayne on a port-forwarding sitiuation through his Ubiquiti Edge Router.  I will say, having been a firewall guy for 20+ years, they way the lay out their ACLs is very misleading.  But we were able to get things figured out and connect him up to various nodes and reflectors as a test.  As Hanibal Smith would say, “I love it when a plan comes together!”
Traded out internet devices at my primary DMR site in Indianapolis.  The Verizon box that was over there keep loosing connetivity.  I’ve back on a USB device and a CradlePoint router, which proved to be rock solid.  I’d taken the Verizon box over because it had the ability for two analog lines to be added and I was considering dorking around with a digital auto patch.  Also replaced the cooked Astron PS on the amplified.  I found a contiuous duty switcher on Amazon rated at 50A, so we’ll see how it works out.  So far, so good.
Worked with an IL ham an his openSPOT.  He was very interested in connecting in with our network and joining our weekly nets.  In order to facilitate his request, I needed to follow up on some open connectivity items between Crossroads and BrandMeister.  Luckily those guys remembered our discussions from ~6 months ago and we discovered most of it was partially build.  So a little tweaking and we were able to provide the connectivity requested.
Another website comment from a mother of a new ham with a brand new TYT MD380.  They were having issues getting it programmed.  I guided her through the process and also suggested she join our FB group where she was able to get multiple people on board to help her.
Attended the Grant County ARC Christmas Party where I was presented with a lifetime membership for my technical contributions to their organization.  Very unexpected, but very honored to have been given something like that.
Bought a Tera 7400 DMR HT.  This is the unit that you see Powerworx advertising.  So far, I’m pretty impressed.  It’s a Chinese radio, of course, however, it’s quite solid.  I like the black screen with the white letters and much like the hacked MD-380 firmware, you’re able to download the global DMR contact database and store it on the radio instead of having to enter it into CPS or mess around with kludgy import processes.  Of the cheaper DMR radios I own (Connect Systems, TYT, Zastone, etc.) the Tera 7400 is my favorite.  I believe it retails new with programming cable for around $275, so closer to the CS750 in cost, but in all things, you get what you pay for.
Helped the guys up in Homer, AK with some codeplug changes on their MD-380’s.  Things are progressing well up there.  Excitement is growing and they are learning!  I sort of wish I was a little closer to the action, but I am considering a trip up there at some point.

Received a website comment from a ham asking for assistance in upgrading the firmware on his DV Mega.  He was unclear about the modification required on the board and where to apply it.  I was able to provide him a link with the information he required and he was good to go.

Received an email from a Bulgaria Ham asking to collaborate with the XLX DSTAR Reflector I have up and running.  He’s wanting to experiment with the inter-connectivity.  Sometimes it amazes me at the request I get for help and more so where they come from….  But they find me somehow and I think that is pretty cool!
Repaired a small issue with the IRC website wherein the logo disappeared.  Very odd, the only thing I can think is that a URL got munged during one of the automatic updates.  Luckily the fix wasn’t too involved and it was back pretty quickly.  The rest of the site was fully functional, just no logo.
Helped one of the Homer, AK guys with his openSPOT and an understanding of what was connected and what was not.  He quickly picked up on things and was up and running in no time.
Began tinkering with the Arcom RC-210 web interface software.  I built a Pi based upon Rasbian/Jessie and have it connected up to my controller and ready for the software installation.  Unfortunately there are no docs available currently, so you pretty much have to pull it down from GitHub and wing it.  I’d hoped to get to this while I was on vacation, but I didn’t get any further than setting the node up.  Perhaps I’ll have more to share next month.
With the only networked DMR repeater in AK connected to our c-Bridge we are currently the hub for the Alaska Statewide (#3102) talkgroup.  The AK guys are open to sharing it with whomever and have requested to get it linked up to Brandmeister so that they can get on with their hotspots.  I’ve completed the work on our side and am waiting for the BM guys to do their thing.  We’re close, but at last test, it’s not working.  Hopefully that will be resolved soon.
Started talking to some other hams about a P25 network throughout IN.  I already own two Quantars (one on 33cm the other one 70cm) and just purchased an AstroTac 3000 Comparator to function as the central hub.  As you will recall from previous reports, I had successfully linked my 70cm Quantar to a similar setup down in KY.  It sounds as if we might be looking to duplicate what they are doing down there for IN.  This could get real fun, real fast.  I’m looking forward to the collaboration and the learning as we bring the various pieces into play.
That’s it for December!  Whew!  See you next month!


Dec 05 2016

NF9K ARRL Technical Specialist Report – November 2016

November was not as radio active due to vacation, the Thanksgiving Holiday and an impromptu business trip to South Carolina for work.  However, I did manage to generate some activity, so here goes:
 Obtained four TYT MD-380 DMR radios, flashed them with the MD380Tools firmware, using a Raspberry Pi, and got them shipped up to four very excited amateurs in Homer, Alaska.
 Performed some administration work on the IRC website, updating some out of date information, publishing minutes, etc.  Also re-worked some forms in order to support different email addresses for the IRC staff.
 Donated an unused 30′ tower to another local ham.  The tower was originally donated to me, and I was able to replace it with a 55′ one, so I paid it forward.
 Setup my openSPOT to connect to a home-brew SharkRF server and utilized the openSPOT all the way down to Gatlinburg, TN, connected to a USB cellular modem via a CradlePoint router.  This made for a very portable and dedicated means of communication.  I plan to do some additional work with the SharkRF server software, but was impressed with what I’ve seen thus far.
 At the request of our repeater trustees, the Crossroads Talkgroup (#8710) was extended to the K4USD DMR Network.  I worked with W2XAB to setup the necessary c-Bridge CC links to make this initiative a success.
 That’s pretty much it for November.  Looking forward to the latter part of December and taking some much needed time off.  I hope to kick start some stalled projects during that time.
 I wish everyone a very safe and very Merry Christmas and a Happy New Year!


Nov 01 2016

NF9K ARRL Technical Specialist Report – October 2016

I received a new firmware to test for the the scan bug that I reported in BridgeCom’s 220Mhz Mobile.  Sadly, I haven’t had a chance to apply the new firmware, but hope to shortly.  From reading the info provided, they’ve fixed part of the issue I reported, which was while in memory scan, power cycling the radio lands you in VFO mode upon power up.  I’d also ask about having scan start back up, specifically for memory scan, but that might take them some more work.
I got bit by the Astron loose screw bug.  For those of you who are familiar with the larger Astron power supplies that have the screws in the top of the capacitor, you’re familiar with this issue.  This particular amplifier powered the amp on my DMR repeater.  The loose screw cause things to get a little warm, but I believe it can be repaired and put back in service.  It’s on the bench now with hopes of returning to service soon.
Received a website comment regarding my BlueDV project.  I was able to answer the questions posed as well as provide some insight regarding firmware upgrades to the DVMega boards.  For those interested in reading more: http://www.nf9k.net/?p=698
Upgraded a fellow ham’s Pi-based IRLP node to include functionality for Echolink.  Also order pieces to build another pi-based EchoIRLP node for another ham.  Those pieces should start to arrive shortly and I’ll start working on building that up.
I received my SharkRF openSPOT box.  For those not familiar with it is yet another hot spot solution, but what makes it different from the others (DV4Mini, DVMega) is that is can transcode one digital format to another.  So it’s possible to carry on a DMR QSO using your Fusion radio, for example.  You can also do DMR <-> CF4M, etc.  Very cool little package.  I haven’t had much of an opportunity to dig in yet, but do have it up and running.  You can read more here: https://www.sharkrf.com/products/openspot/learn-more/
Fixed a small cosmetic display issue with the IRC website.  Still not sure why it occurs, but thankfully it’s not service impacting.  I suspect something to do with the way the template is coded and the various browers that visit the site.
Fielded an initial website question regarding the new Alaska DMR repeater (more on that in a minute) which lead to an email exchange and a primer on DMR and other technologies, including DV4mini and reflector linking, etc.  There are a lot of folks out there working on many of the same projects and it’s great to collaborate and share knowledge/experience.  This particular ham is working on an MMDVM project, which I have partially built myself….  If only there were more time in a day.
The crowing achievement of the month was the installation of a DMR repeater in Homer, Alaska.  This project has been going on for several weeks.  I was initially contacted by a Indiana Ham who had sold one of his DMR repeaters to a ham in AK.  He wanted to know if I’d be interested in helping them get started and if they could join our network.  The answer of course was a resounding yes.  After many emails and a few phones calls, the c-Bridge programmed, the repeater configured and tested and shipped to AK.  An XPR7550 was shipped from AK to IN for initial programming, so they could have an example to work from and to provide a nice tool for learning.  All in all, many hours were logged by myself and one other ham here in IN and the local Hams in AK.  It all came together on Saturday, October 29th at 16:30EST when we held our first DMR QSO to the state of Alaska.  Since then, every time the guys key up on any of the wide-area talkgroups, they are getting mobbed by people from all of the country and in some cases the world.  DMR contacts with AK are quite the rage.  I continue to receive emails from the locals on how much they are enjoying this new mode of communication and how interest in continuing to flourish.  They’re already talking about bringing another machine online!  The next step for me will be to prepare four TYT MD-380 with the MD380Tools firmware as well as a Raspberry Pi with the scripts necessary to install the upgraded firmware so that they can do it on their own.  This has been so much fun and just goes to show what can be accomplished when you have the right folks involved.  Truly a team effort and my thanks to those involved that helped make this happen.
Well, that’s it for this month.  I wonder if it’ll be snowing by the time we’re all doing this again?


Oct 07 2016

NF9K Technical Specialist Report – September 2016

Received a website comment from a local amateur looking to use DMR to communication back to Franklin, IN, once he moves to Texas. I was able to help him by by explaining how the various DMR Network inter-connect and what TG’s he’d likely be able to find in common.

Responded to another website comment and helped a local amateur with programming his subscriber ID into his radio. He was using a template provided by someone else, but couldn’t find the ID setting.

Another website comment regarding the downloading of available code plugs. Help out by providing some instructions on how to accomplish the task.

Successfully linked my recently acquired UHF Quantar to a P25 Network in KY/TN. The connectivity is accomplished by using a wireline card with the v.24 daughter board in the repeater or a third party adapter if you do not have the v.24 card. You then interface that with a WIC-1T serial interface card on a Cisco router. The Cisco router is then configured for serial tunneling which connects in my case to an AstroTac 300 Comparator. Very cool setup, and the Cisco stuff is right up my alley. I loved it when I my work and hobby’s cross over. The repeater is still on the bench, but will begin finalizing antenna/tower this month and get it up in the air and in service.

I took the time to support the Amateur Radio Parity Act. While it no longer affects me, I did live for a number of years under a CC&R and would love for those hams still burdened by such a situation to get some relief.

Purchased and assembled a BlueDV unit. A very cool/small DMR/DSTAR interface that uses Bluetooth to an Android device or USB connectivity to its control application. More info can be found here: http://www.nf9k.net/?p=698

Received an email from a California Ham looking for assistance in interfacing an XPR8300 to an RC210 controller. We discussed the limitations of such a configuration, many of which he wasn’t aware of, but the design is what they’re going to use for now. I help him map out the various lines he’d need to get everything going.

Ordered an SharkRF OpenSpot device. Hopefully that’ll be in before next months report and I can provide some first-hand info. In the mean time, the device supports DMR (Brandmeister, DMRplus), D-Star (DCS, REF/DPlus, XRF/DExtra, XLX), System Fusion (FCS, YSFReflector) networks. And the biggest thing is it supports cross modem modes, allowing you to talk with your C4FM radio on DMR, and with your DMR radio on System Fusion networks. I’ve seen this in action and think it could really open some doors for cross-networks or allow people who have invested in one particular mode to access others without buying additional radios.

Updated the IRC website with new meeting minutes as well as new repeater directories and the various associated download files.

Began working on a NOAA weather alert interface that can be used on the Crossroads DMR network. I have the solution running on the bench, but still have some logistics to work through.

Had some connectivity issues at two of my DMR sites. Cellular internet is convenient but not nearly as reliable as wired. And the more rural you get, the less reliable things are. But I’m happy to report that impact was minimal and everything came back online after being rebooted.

Began working on an out-of-state DMR collaboration that has some promising opportunities. Hopefully things continue to develop and I’ll have more to share in the upcoming months.

I believe that’s it for September… Oh yeah, besides the fact I’m now a year older…. 73 until next month!

Sep 26 2016

BlueDV – DMR/DSTAR Interface

The BlueDV is a very small and portable DMR/DSTAR interface.  The whole piece is actually a combination of two parts, the BlueDV adapter and the DVMega board.  More details on the individual pieces later.  What appeals to me most about this solution is the size, and the interface, which runs on an Android phone or tablet and connects via Bluetooth or you can connect it via USB to a Windows machine running the software.  Since the interface is actually on a separate device, there is no need to worry about finding your IP or remoting into the device to make changes.  All configuration is done via the application interface.

There are three pieces to the BlueSpotDV (DVMega, BlueSpot Board and Case):

1). The DVMega Board – This comes in two flavors, a single band (70cm) and a dual band (2m/70cm). While dual band, it’s only one band at a time, because it’s a single serial interface. I initially chose the dual band because I travel for work and I figured it might be nice should I end up somewhere that 70cm wasn’t allowed. However, in hindsight, the dual band has been more heartache than I expected. I had to solder a wire on, to upgrade firmware, very few images readily support the dual band capability. The Maryland DSTAR was the only one I found at the time. You can get the DVMega board many places, but I bought mine from GigaParts:http://www.gigaparts.com/SearchResults.html?search=dvmega

2). The BlueSpot Board – Now called BlueDV due to a lega issue. This board attaches to the DVMega and provides the capability of running it in dongle (USB) mode, directly connected to a PC. Or you can put it in bluetooth mode and connect it to a phone/table and run it that way. With the v3.04 firmware that was recently released you’re able to do DMR, DSTAR and C4FM (Fusion). You can get the board here: http://www.combitronics.nl/index.php…

3). Case – There are so many great projects out there for Raspberry Pi and other platforms, but rarely does one of the component manufacturers offer a case. In this case (pun intended) you can order a case along with your BlueDV. Since I was ordering from the Netherlands, I figured I’d just get a case as well.

Assembly pretty much went just like the pictures I posted. The DVMega snaps into the case, the light pipe attachment sits onto of the BlueDV and provides a nice resting spot for the DVMega. Then you snap the top on.

Hope that helps. If you have further questions, please don’t hesitate to ask!

14485140_10210209672135995_7689924258845855956_n 14485072_10210209672496004_4398418318330629957_n 14470601_10210209672736010_2562600108521058780_n 14517430_10210209673096019_2486126996568796498_n 14495470_10210209673256023_5908282437305609085_n 14516489_10210209673536030_1783330017930105151_n 14484852_10210209673936040_4626434111818310743_n 14440671_10210209674256048_8007827363174966406_n 14494751_10210209674496054_8850651507700836112_n 14502767_10210209674816062_8366717893991450822_n 14517374_10210209675096069_1254782142991808725_n 14470598_10210209675536080_2245091914001064291_n


Sep 08 2016

Tytera MD-380 Hack (MD380Tools) – Updated (Project moved to GitHub)

By now, everyone has heard of the hacked Tytera firmware, but application of it was tricky at best.  Recently I discovered a script that when run from a Raspberry Pi, makes the process painless.

The script was written by WH6AV.  I ran mine on an original Pi 2, because that’s what I had handy.  The compile process would likely have been faster on a newer model, but was still not too bad.

I actually ran it on a Pi that previously ran Asterisk using the RasPBX image, so no special requirements.  I also ran it as root, since it runs through apt-get update/upgrade and running as root just made it easier.

Login via SSH and run following command:

sudo apt-get install git -y

Wait for installation of GIT to complete. You will be back at CLI, command line interface prompt. Type the following:

sudo git clone http://github.com/wh6av/md380-radio

Wait for cloning to complete. You will be back at CLI. Type the following to change into md380-radio directory:

cd md380-radio

To execute program, type the following at CLI:

sudo ./md380-update

Just walk through the options.  You may skip those that reference the MMDVM.  To do the initial flash, you need to put the MD-380 in DFU mode, which is done by pressing the PTT and Top Side Button together and then turning on the radio.  The LED will flash red/green if you are successful.

One interesting feature of the new firmware is that contacts are stored in a users.csv file on the radio’s file system.  So I plan to keep the Pi around to update the radio from time to time.

Inside the MD380Tools menu option, you’ll find options for changing your Subscriber ID (think DMR-MARC ID), which could be handy if you need to let someone else use your radio and do not have the CPS/cable handy.

Please let me know if you discover any cool features as I’ve just begun to play myself.

Sep 07 2016

NF9K ARRL Technical Specialist Report – August 2016

Built a couple of different Raspberry Pi setup’s for use with a DV4Mini.  I utilized the official 7″ Pi touchscreen and two different stands.  One of the stands required modification of the config.txt file in the /boot partition to flip the screen 180 degrees.  The second stand did not require any modification.  Next was the task of getting the dv4mini control panel to run on the Pi.  There are binaries compiled for the Pi’s ARM architecture, but finding the most recent versions can be tricky.  I discovered some bugs in the ARM/64-bit version of dv_serial.  It appears that binary was compiled against the wrong platform.  The good news is that dropping back to the 32-bit version appears to work.  The last part was figuring out how to run the package from linux.  This was accomplished by installing the mono package, which is a cross-platform .NET framework.  I will be documenting the process as well as posting some pictures to my website soon.
I attended another VE Session with the WD9BSA Group on August 18th.  We tested six people, with a total of 8 exams administered resulting in three new Technicians and 1 General Upgrade.  This particular session held some new experiences for me as it was my first one in the role of Team Leader.  It was great to learn a little more about the process and how the back-end things work.
Received an email from an Illinois Ham seeking assistance on programming his EFJ 5100 for 33cm.  We exchanged several emails and I believe that I have him headed down the right path.  I’m certainly he’ll let me know if he requires additional help.  The next step may be to arrange a team viewer session to help him out.
Performed a lot of c-Bridge programming activities related to the roll-out of the Indiana Statewide Talkgroup #3118 to the Crossroads DMR Network.  We still have a bit of work to do, but it was rolled out to several repeaters without issue.  Many thanks to Steve Jones, W9SMJ for making this available!
Received a website comment from a ham looking for help/understanding on how he could make a cross-country trip and utilize DMR.  I gave him a primer of the technology as well as the various networks that might be in play across his decided path.  However, I believe it highly likely that he’ll find enough TG’s in common during his trip to make it successful as far as DMR goes.
Worked with the Laurel VEC to establish the N9AG VE Team with them.  Being affiliated with both the ARRL and Laurel helps us make the most out of our testing sessions as well as reach out to different audiences that otherwise might not attend a testing session.
Resources from the N9AG, IEN and WD9BSA VE Teams are looking for a central spot to potentially host a monthly evening VE session.  More on this as our plans develop.
Crossroads DMR finally reached the point where it was necessary to upgrade our c-Bridge from the 15 peer license to the 30 peer license.  The folks at BridgeComm were great to work with, as always, and facilitated a straight forward upgrade.
Minor work still continues on the IRC Email server, investigating email bounces, etc., but I’m happy to report that these efforts have dropped down to basic administration!
I think that’s it.  I’m already working on some hopefully cool P25 stuff to report next month.  Until then….

Older posts «