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.
Evans KD4EFM
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.
Evans KD4EFM
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.
Paul-NB9X
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.
DULY NOTED!
Evans KD4EFM
Please send any comments you may have to info@nxcore.org, I will try my best to get them answered and posted here.
Here is the current list of repeaters and talkgroups, served by the Florida NXCore server.
nxdnrepeaters <– PDF file for downloading.
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.
73 de Jason, KD4ACG
Here is a list of viewable dashboards for the NXDN WW Network.
Thanks to Adrian, VK4TUX for putting this together.
| Service | TalkGroup | Dashboard |
| Canada | TG 302 | p25canada.hopto.org/nxdn/ |
| VK 505 | TG 505 | 112.213.33.44/db/ |
| 1200 | TG 1200 | 1200.mmdvmvk.org |
| 9000 | TG 9000 | nxdn.duckdns.org/9b/ |
| Pacific | TG 10400 | nxdn.mmdvmvk.org |
| Deutsch | TG 20000 | srv08.oevsv.at/nxdn/ |
| 25000 | TG 25000 | 45.62.211.216 |
| 50525 | TG 50525 | 50525.nxref.org |
| 65000 | TG 65000 | 45.62.251.179 |
Many have been pointed to a Google Spreadsheet style location, a new site has already, taking over the role of assigning ID’s.
The site is http://radioid.net
Radio ID is the master site for obtaining DMR, NXDN ID’s for amatuer use.
P25 ID’s can also use the DMR ID format, which some people follow that ID use also.
SO, please, kindly keep it within the parameters of 1 to 65519, and even though you CAN enter your full DMR ID, please register with radioid.net and follow all instructions withing the site.
Some additional information I wanted to put out:
For MMDVM email List go to: https://groups.yahoo.com/neo/groups/mmdvm/info
For the FaceBook PiStar group: https://www.facebook.com/groups/pistar/
I will add this to the Side Links area also.
Thanks and Welcome newcomers!
Evans
KD4EFM
What is all this buzz about MMDVM and NXDN and ???????? other homebrew kits that are joining the Digital Ham Radio Era?
Well, like most forms of digital technology comes advancement of it. In this case it came from Jonathan Naylor G4KLX and his project for D-Star, Fusion and P25 (aka P25NX).
*I only know of those modes from Jonathan
But for some of you, you already know what it is and does. For others, it’s where you can take micro-computing to the next communications level, and have a “repeater controller” doing all the hard work with simple radio gear, and OR a hotspot 2-way now.
Here is where things stand at the moment, from the MMDVM Yahoo group, by way of Jonathan:
“I have merged he NXDN branch for both the modem firmware and the host into master. This means that the default version of the code is now NXDN enabled.
It has basic networking built-in, talking to the single MMDVM NXDN reflector. I posted details of how to use it a couple of weeks ago. I am working on making the software compatible with the official NXDN amateur network, and in due course, that, along with some form of gateway will be released. At that time the MMDVM NXDN reflector will be retired.
Please note that the extra processing load of the NXDN code means that it isn’t possible to run five modes on an Arduino Due. Aside from NXDN, D-Star and DMR are the next heaviest protocols for processing, so it may be possible to run (say) NXDN and P25 on a Due, and maybe more. The more powerful STM32 and Teensy based systems can easily run all five modes. I believe firmware for the ZUMSpot and MMDVM_HS boards will also be available soon.
In unrelated news. I’ve been adding FCS support into the YSF Gateway and taking the opportunity to clean the code up also. I did a first test this evening trying to log into FCS001-20 but with no success 🙁 It’s early days though.
Jonathan G4KLX ”
So with that being said, the next level of NXDN and the Homebrew world is network linking, which is still being tested at this time, though the MMDVM network has a function for linking, it is not currently connected to the NXCore 65000 relm at this time.
I will let you know when that chapter comes into play, but do expect to see a SURGE of new users to say hello to!
Thanks
Evans Mitchell
KD4EFM