You may know it as CNJHAM, because that is how it all started. CNJHAM was first implemented as a lone StarNet smart group. CNJHAM then begat XLX020. Hardware transcoding was soon implemented and followed by links to Brandmeister DMR and YSF Fusion. In this new year, we’ve added Wires-X (for connection from Fusion repeaters) as well as P25 connections.
CNJHAM/XLX020A can be reached via the following methods:
I’ve been a Sirius subscriber since before it was Sirius XM and before Howard Stern first fled from teresstrial radio to the birds. I stopped being a regular commuter in 2013 and so my listening time shifted from the car to home.
At one point I mounted a small antenna to the side of the house and listened directly to the satellites. This was soon replaced by my Logitech Squeezebox internet “radio”. At some point, Sirius made some protocol change for the internet streaming that broke the Squeezebox app and there was to be no fix. So I switched to a Grace internet “radio”. Then came another change and the Grace could no longer be used.
I’ve been a Google Home smart speaker user for a couple of years and it always seemed odd that Google and Sirius had not partnered on a solution. Well, Happy Radiomas to me! In November, Sirius XM rolled out Google Home device integration. After setting up the credentials in the Google Home app, Sirius radio fun is now as close as saying “Hey Google, Play Spectrum on Siriux XM”.
Thanks Sirius and Google for making it easy to listen to Sirius in the same way that I listen to many other audio sources. If you are not using your smart speaker to listen to the radio, you’re missing out.
Former shortwave listeners, especially, can find a wealth of programming from around the world. For example, you can get the lastest news from the BBC or updates on the fire situation in Australia from Radio Australia. Make a resolution to explore this capability in the new year and you won’t be disappointed. You can even request, “Hey Google, play the latest Glenn Hauser’s World of Radio podcast.”
XLX020 has upgraded to Luc (LX1IQ)’s latest xlxd (2.3.1) software. We now support direct connections via the Yaesu YSF protocol.
Luc is in contact with the distributors of Pi-Star and the OpenSpot to have this capability added to the dashboards. In the meantime, there is a simple change that you can make to your Pi-Star configuration to connection to XLX020.
You’ll have to be willing to edit your Pi-Star /etc/mmdvmhost file. Look for the [System Fusion Network] stanza. You’ll need to change the GatewayAddress to xlx020.k2ie.net and the GatewayPort to 42000.
A fellow New Jersey ham was having the hardest time using my XLX reflector. He could connect to a reflector module. He could hear conversations, but none of his transmissions were making it out over the reflector. Strangely, he had no such problems when using a DPlus reflector. His radio is a Kenwood D74A.
He uses a SharkRF openSpot2 as his hotspot. While helping to search for a solution, I remembered a thread I saw on the Pi-Star Forums. The author complained of not being heard on an XLX reflector via a D74A. The cause and the solution had nothing to do with Pi-Star, but rather it proved to be a quirk with the D74A and the XLX software.
Apparently the D74A allows any character to be entered into the Callsign Extension field. These are the 4 bytes following the “/”. While these characters were orignally made available to support reciprocal operations and portable suffixes, they are now commonly used to identify the type of radio being used. So my D74A callsign is setup as K2IE____/D74A (the underscores represent spaces). My friend’s radio had “@?” in the Callsign Extension field. These unexpcted characters seemed to cause the XLX reflector to ignore the attempted transmission.
The Icom radios support only A-Z and 0-9 in the callsign extension field. The D74A allows lowercase and special symbols too. Don’t use anything other than A-Z and 0-9 in the Callsign and the Callsign Extension fields and you won’t have this problem.
To make things more interesting, the ham who reported this issue is visually impaired. He relies upon the radio’s voice prompts. However, the Kenwood D74A voice prompting system ignored the @? characters completely, so he never had any idea that they were present. Another local ham who was alerted to the special character problem on the D74A spotted the issue and fixed things.
If you’re a fan of either D-Star or DMR, you have probably noticed the proliferation of multi-protocol gateways. These gateways, such as the XLX020 system, permit users of radios of one type to communication with users of radios of another type. Multiprotocol gateways help to defragement the amateur digital landscape.
However, there can be issues if the transmitting operator is not registered on both systems. Have you been on a DMR radio and seen the transmitting party display as radio id 0? They are a D-Star (or Fusion or P25 or NXDN) operator who has not registered a DMR radio number.
For DMR operators who have not registered with their nearest D-Star gateway, transmissions could even fail to pass through the D-Star gateway to connected D-Star repeaters.
Therefore, k2ie.net highly recommends that all amateurs using any digtial voice mode register for BOTH a DMR radio id and with a local D-Star gateway, whether or not you have a corresponding digital radio.
My callsign has changed and we are migrating the blog over to http://k2ie.net. Please update all bookmarks that formerly pointed to k2dls.net.
I’ve been asked, “Why did you change your callsign?”
1×2 callsigns are hard to come by, especially one from your own call area. K2IE is an especially easy call for CW use. And, I was a friend and co-worker of the former holder of this callsign, Robert Norton. Unfortunately, Bob became a silent key well before his time.
Bob and I used to talk about radio and he encouraged me to get my amateur radio license. He also provided some insight into the hobby that I draw upon to this day. It is an honor to hold his callsign.
I’ve spent a couple of months chasing down this issue, reading post after article on this subject. The consensus so far has been:
1) Update to the latest firmware. 2) Run the MMDVMcal procedure to minimize the BER. 3) Set the DMR preamble time on your radio to 960 ms.
After weeks of poor results, I came upon the solution that has worked for me (and for others) in a manual for the Anytone 878 produced by Bridgecom. Bridgecom recommends a DMR preamble duration of 100 ms.
1) Update to the latest firmware. 2) Run the MMDVMcal procedure (or enter the sticker offset values for RXOffset and TXOffset). 3) Set the DMR preamble to 100 ms.
Well, I was testing on an Alinco MD-DJ5, a radio very similar to the Anytone 878. So I tried the preamble setting (called Wake Head Period in my software).
I have now achieved the mystical “five 9s” of reliability. I press PTT, I talk, my transmission gets received.
Ah, the sweet smell of success… And kudos to Bridgecom for the level of support that provide for Anytone 878 users.
This solution has worked so far with an Alinco DJ-MD5, a Motorola XPR, and a CS-700 (where I had to use 120 ms because the dropdown increments in steps of 60.). Oddly, my Hytera PD-365 does not support values lower than 360.
When I travel to other countries, I try to take out a few minutes to scan the AM broadcast band. I have observed that over the past few years I am hearing less and less. Sometimes there is nothing to hear but static and local noise. Many counties are completely abandoning AM broadcasting in favor of FM and digital (DAB). The urban environmental interferance levels don’t help things either.
A recent bandscan in Athens provided a nice surprise. The standard AM broadcast band was full of strong signals, most playing music. I settled on a strong station on 828 kHz playing a program of American standards and light fare. There were a few short announcements in Greek but I was listening as I fell asleep, so didn’t catch anything I could remember.
A bit of research the next morning showed that 828 kHz, and most other stations heard on the AM band in Athens, are unlicensed hobby stations. The Greek government does not seem to care much and these stations are providing a service.
If your travels include Athens, don’t forget to bring along an AM radio. You won’t be disappointed.
There are a couple of warring camps in the Allstar (app_rpt) development world. One group, AllStarLink, Inc., has claimed to represent the vision and interests of Jim Dixon <WB6NIL>, the original developer of app_rpt. Another group, HamVoip, has made some significant changes in that code in an effort to improve it.
So why can’t we all get along?
Jim Dixon released his code under the terms of the Gnu Public License. The short explanation of GPL is that anyone is free to use the code but any enhancements must be shared back with the community. AllStarLink, Inc. has insisted that HamVoip share the source code to its enhancements. HamVoip has declined.
The acrimony in some online forums has been thick enough to cut with a knife. Some have branded HamVoip as pirates and some have said that AllStarLink ought to get over itself and has no authority to enforce anything.
The scale has shifted in favor of the AllStarLink, Inc. defense of “open source”. In a recent announcement, the Board of Directors reports that:
AllStarLink, Inc., the extension of Jim Dixon’s vision for AllStar, has obtained all rights including Copyright to app_rpt and associated material. In the spirit of Open Source, we encourage code contributions to the project. Thank you for your continued support in keeping the AllStar vision alive.
Hopefully this settles matters once and for all. May Jim Dixon’s vision of an open, community based solution for analog repeater linking live long and prosper.