Well, going to break the interwebs again!
From KC1LSN, he has managed to take a NX-411 and work it with a MMDVM hotspot for NXDN!
Congrats Rob!
cut and paste with hopefully more to come!
It is working! Very excited to have my NX-411 able to do NXDN through a duplex hotspot. Using WSPD if it matters but not because that's required, Pi-Star would do it just fine. I got tired of staring at Pi-Star so I changed it up.
I just wanted to create a post to document the result in case others are curious, and to say thank you to everyone who proposed ideas. I didn't reply to every post to keep the s/n ratio down, but I did look at every post and used each one to evaluate my programming and settings.
A special thank you to Alex who went above and beyond to actually look ay my DAT and confirm that everything was programmed properly on the radio itself. I was surprised, to say the least, when he came back saying that I'd done that job correctly. As I posted in here I was certain it was my lack of knowledge about the nx-411 and NXDN that was causing the issue.
So what was it? Very early on, and I mean pretty much as soon as I made my original post, Lloyd suggested to me that I need to run the offset calibration tool. I did that test as per his advice. Well, "an attempt was made" but I didn't really run the test properly the first time. I sat down again today, pulled up all the responses here, and started fresh... this time running the offset calibration properly in the process. Lloyd was entirely correct about that process being the answer. The MMDVM board needed an absolutely *massive* offset. So there's a great lesson in not skimming the instructions and sticking with the test longer to really explore the outcome.
I can confirm a couple of things now:
From KC1LSN, he has managed to take a NX-411 and work it with a MMDVM hotspot for NXDN!
Congrats Rob!
cut and paste with hopefully more to come!
It is working! Very excited to have my NX-411 able to do NXDN through a duplex hotspot. Using WSPD if it matters but not because that's required, Pi-Star would do it just fine. I got tired of staring at Pi-Star so I changed it up.
I just wanted to create a post to document the result in case others are curious, and to say thank you to everyone who proposed ideas. I didn't reply to every post to keep the s/n ratio down, but I did look at every post and used each one to evaluate my programming and settings.
A special thank you to Alex who went above and beyond to actually look ay my DAT and confirm that everything was programmed properly on the radio itself. I was surprised, to say the least, when he came back saying that I'd done that job correctly. As I posted in here I was certain it was my lack of knowledge about the nx-411 and NXDN that was causing the issue.
So what was it? Very early on, and I mean pretty much as soon as I made my original post, Lloyd suggested to me that I need to run the offset calibration tool. I did that test as per his advice. Well, "an attempt was made" but I didn't really run the test properly the first time. I sat down again today, pulled up all the responses here, and started fresh... this time running the offset calibration properly in the process. Lloyd was entirely correct about that process being the answer. The MMDVM board needed an absolutely *massive* offset. So there's a great lesson in not skimming the instructions and sticking with the test longer to really explore the outcome.
I can confirm a couple of things now:
- The MMDVM duplex boards that claim they can operate in the 900mhz world can, provided they're not defective or the person who manufactured it didn't cut any corners
- The NX-411 is capable of being programmed to do NXDN via hotspots, both simplex and duplex, I have successfully used both, both have no issues changing talk groups or with RX/TX via RF.