Great news! The Icom NXCore server is now updated to support Short Digital Messaging (SDM). This works over all repeaters connected to the Florida NXCore server, AND it works over the hotspot reflectors, too!
At the present time, there’s a slight incompatibility between radio manufacturers. For now, most Icom radios will receive messages sent by other Icom radios, and Kenwood radios will receive messages sent by Kenwood radios, as well as the Icom 4300/6300 series, which was built as part of a partnership with Kenwood. As this technology is new to NXCore, there may be some future enhancements to allow for greater compatibility between the brands.
Messages are sent to talkgroups, rather than to individuals, when sending between repeaters on the NXCore network. In order to send only to a single individual, the recipient and sender must be on the same repeater, where linking is not needed.
In order to receive SDM, your radio’s configuration may need to be updated. If you need help, leave a comment below, including your radio’s model number, and we’ll provide the steps for your particular radio.
With the arrival of this technology, users of Talkgroup 1200 will soon receive severe weather alerts throughout the NWS Tampa Bay region.
We hope you enjoy this new enhancement to NXCore, thanks to the hard work of Bob Thoelen, N1XDN, the author of the NXCore software.
An updated version of NXCore has been installed on the Kenwood server, which should enable Short Digital Messaging (text messages) from your radio, to other radios on a talkgroup (not individual) basis.
All repeaters connected to the Florida Kenwood NXCore server, have had this feature enabled, but we need your help to test it. Please attempt to send text messages across a talkgroup, with the recipient on another connected repeater. Let us know your results.
Some limitations: Initially, we are testing repeater-to-repeater on the same server only. We have not yet enabled the passing of messages between other Core servers in the network. If it works locally, we’ll try to broaden the scope. Also, as with voice mode, the messages will not go between Kenwood and Icom/hotspots at this time (rest assured, we’re still working on that part).
For users on the Icom network, we have a little more debugging left to do, but we plan to roll out a similar test on the Icom side very soon.
Many thanks to Robert Thoelen for his continued work on NXCore, without whom none of this would be possible.
The popularity of reflectors has grown by leaps an bounds in the past year. These reflectors give hotspot users a way to access NXDN talkgroups, and speak to other hotspot users. However, there are some important steps you must take, to ensure your reflector/talkgroup can also be heard on NXDN repeaters throughout the country.
STEP ONE: Configure your reflector’s NXDNreflector.ini file Locate the Icom Network section of your .ini file, and configure it as follows:
TGEnable= <your talkgroup ID here>
Any lines that start with a “#” can be left as-is. That symbol signifies a line that is commented-out, and will be ignored. Restart your reflector when done.
If you have any other lines that begin with “Address,” you must put a pound sign at the beginning of those lines. Failure to do so may cause conflicts in the network. Unused address lines can simply be deleted, if desired.
STEP TWO: Notify the Core admins NXCore must recognize your IP address, to be accepted on the network. Send an E-Mail to Jason, KD4ACG, at email@example.com. Provide your talkgroup number, name, and IP address. It will be added in 24-48 hours.
Effective today, All repeaters connected to the Florida NXCore server, have access to the Alabama Link Talkgroup, TG 31010. This is a multi-mode talkgroup, so you’ll hear users from D-Star, DMR, and Fusion, in addition to NXDN.
On all repeaters, it’s a dynamic talkgroup. Key your radio on Talkgroup 31010 to activate. It will remain active on your repeater for up to 15 minutes since your last transmission. However, when finished, please key Talkgroup 1200 to reconnect it to the local repeater, without waiting for the 15-minute period to lapse.
Just letting everyone know, development of a SOFT-bridge between the cores is in the works at this time, not ETA due to current events, but the R&D on it is on the books and
being worked out.
The SOFT-Bridge will allow us to join the Kenwood and Icom cores with a data pipe that
allows us to have a seamless network between both Icom and Kenwood repeater owners. Basically a transparent bridge. Hope to have more information on this when it becomes available.
nxcore.org website to a nasty hacker hit, I am in the process of rebuilding it and giving it a facelift and more up to date look. nxcoreorg is the server farm hosting the world wide nxdn network connections for the Icom and Kenwood networks. The last heard lists and other information along with the code will get a fresh look and once over by the nxcore developers and admins after the new year. More on this when it comes. Stay tuned here for more information.
Here is a valid suggestion submitted to the community;
One thing I would like to see addressed is the ability to send and receive messages through connected repeaters. NXDN Messaging is a very powerful tool! I have a Windows messaging app I will be bringing to the Hamfest this weekend that could reduce reliance on the Internet for Hams with NXDN radios. The ability to implement it here in West Central Florida is limited to the reach of the single repeater your station can hit. We need to be able to overcome that limitation to make NXDN messaging more universally accepted. Think about the potential impact for SKYWARN.
here is the reply and my comments
(I would like to hear from others too!)
You bring up a good point Paul, but I have been battling this for a while now.
While I can send data like the D-RATS terminal program on NXDN via the voice stream,
The SMS data is a bit more complex. The ETSI standards for it only talk about the SU through the rptr to SU, but very little of it is in the conventional code for multi-site transport. I will see if I can reach out to the Japan and get some more input put into this, while I do know that Type C Trunking will carry it out, I also know that an IP NXDN CONSOLE can So the same thing. Though the flow chart is IP to SU by way or the repeater, I think with a work on the IP side and some data runs and captures via ICOM NXDNIP protocol, this can be achieved for 2020. We have a diverse group of people who are good with code and can come up with something to make it work.
Keep in mind, standard sms is 1024 character, while EXTENDED sms is 4096.
Truncated CONSOLE NWS messages can be entered into the network if done correctly. I will have to test that with my Kenwood Console on our UHF statewide system to my radios, but the Icom Ver 2 and nx5000 and 3000 platforms will do upto 4096 sms.
I will put that on the board for sure, because, if we can have a restricted web input to generate Certain “canned” messages to listening radios, that would be a leap ahead of all things NXDN!
IF the MMDVM and hotspot communities put their thinking caps on, I am sure this can be a very powerful, and use tool to the SAR and Skywarn communities.
Please send any comments you may have to firstname.lastname@example.org, I will try my best to get them answered and posted here.
If you’re accessing the network through one of the repeaters in this list, you only need to make sure you have a memory channel programmed for each talkgroup you want to use. Optionally, some radios allow you to select a talkgroup from a list, without needing a separate channel.
Consult the user’s manual for your radio for specific instructions.
All dynamic groups are on a five-minute timer. Every time you key the radio on your desired talkgroup, the timer automatically resets.
This document may be freely shared wherever its information may be useful.