k7rex
New Member
Posts: 10
|
Post by k7rex on Jun 27, 2016 12:21:25 GMT -7
I am using DSTAR Commander (latest version) with a Star*Board GMSK modem; works GREAT !!!! That said I do have one issue --- for whatever the reason the senders Call Sign ID does not display on the radio (??)... The senders Message displays just fine, just the call sign ID is missing... If I go through a D-STAR D-PLUS repeater the Call Sign IDs displays normally (as do the messages) and I have DSTAR Commander (latest version) on my DVAP Access Point and everything is normal there so I am sure it is not the radio... It is only when I am using my GMSK Hotspot with DSTAR Commander that the call sign does not come through - everything else works perfectly.... Note: I don't recall this being an issue until I did last upgrade (DStarCommander_V2.01)... Any ideas ? Dan/K7REX
|
|
|
Post by W6KD on Jun 28, 2016 11:47:10 GMT -7
Usually that's caused when the data stream starts before the radio has stabilized in transmit...with the dvMega, for example, dstarrepeater has a user-configurable transmit delay.
I don't see any such option in the dstarrepeater modem tab for the GMSK boards...not sure if there's somewhere else you can adjust that.
Regards
|
|
k6jm
New Member
Posts: 3
|
Post by k6jm on Jun 28, 2016 14:52:48 GMT -7
GMSK Modems running DUTCH*Star firmware do have a firmware setting for TX delay. Just run NAWinCFG and adjust the Delay Time setting. I usually start out with 250 ms, but you can play with that (probably adjust higher) to see if you can get the callsign and 4-character user text to display at the beginning of the received transmission. Radios spin up faster than others....
Jim
|
|
k7rex
New Member
Posts: 10
|
Post by k7rex on Jun 28, 2016 16:22:13 GMT -7
Thanks to both Bob and Jim for the reply... I am running DUTCH*Star firmware on my GMSK modem so Jim's solution makes sense. I'll give that a try, I'll reply back if it doesn't... Again - Thanks...
~Dan
|
|
k7rex
New Member
Posts: 10
|
Post by k7rex on Jun 29, 2016 15:53:49 GMT -7
Bob -- So far, Jim's (K6JM) suggestion of making TX delay changes using NAWinCFG has not worked (User RX ID still not displaying)... One thing that comes to mind; I have been using the DSTAR Commander for DVMEGA on my GMSK Modem hotspot and choosing DVMEGA dual-band so that I can set it up on VHF, should I be using the VHF DVAP image?... I don't see a connection between that and the problem of the radio not displaying the RX users ID's, but I don't want to leave any rock upturned....
Added notes: For a sanity check I had a friend of mine do some testing on my hotspot.... He experienced the same problems with the RX callsign ID not being displayed as I am on my end. We then went over to one of the local D-STAR repeaters and there everything displayed as it should on both or our radios.... I think we can illuminate the radio settings as a possibility and stay focus on the GMSK Modem using DSTAR Commander.... Also: Thinking this problem may of came with the newest commander (2.01) update I tried using the 2.00 version with the same results...
One other thing I tried was to have the GMSK Hotspot unlinked and then transmitting to it with my IC-80AD watching my ID-51A which was able to display my RX Callsign ID and message as it should using that method. Then linking both my UHF DVAP and the VHF GMSK modem to REF001C I would transmit on one to see myself on the other... As with other stations coming through the GMSK modem, the RX callsign ID was not being displayed... It is only when the gmsk hotspot is linked is there a problem.
~Dan
|
|
|
Post by W6KD on Jun 29, 2016 18:04:15 GMT -7
The only significant difference between the DVAP and dvMega versions is how the USB I/O is configured in Linux.
Try ~300ms tx delay...that seems to work at least with dvMega. That said, the fact that DStar Commander works at all with the DVRPTR and GMSK boards is a happy accident...it was designed solely with the DVAPs and dvMegas in mind, and those are the only RF hardware I have to test with here.
Good luck
|
|
k7rex
New Member
Posts: 10
|
Post by k7rex on Jun 29, 2016 18:20:14 GMT -7
300ms is where I left it set on my last change... I'll try some other images to see what works and doesn't work and get back with you with the results.... Note: I REALLY like DSTAR Commander and had hoped to use it, maybe before all is said and done I still can...
Thanks ----
Dan/K7REX
|
|
k7rex
New Member
Posts: 10
|
Post by k7rex on Jun 30, 2016 17:18:15 GMT -7
Added note: Sorry for any inconvenience that may of come from my repeated linking and re-linking into REF001C while making adjustments on my GMSK Modem. The problem being that I need to be on a busy reflector to see if changes made, made an effect to the RX user ID display; the GMSK Modem disconnects each time I run NAWinCFG... I believe I have a solution now so that I won't need to use a reflector...
|
|
k7rex
New Member
Posts: 10
|
Post by k7rex on Jul 24, 2016 8:10:13 GMT -7
This problem was a hardware issue that has been resolved... Using a GMSK Modem with DSTAR COMMANDER works great with no issues...
Dan/K7REX
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jul 27, 2016 8:59:51 GMT -7
Hi Dan,
I'm just curious, what did the hardware issue turn out to be?
73, Dan - AI2M
|
|
|
Post by kc9sio on Aug 2, 2016 15:20:49 GMT -7
Here's my issue. I am using a Raspberry P2, with D-Star Commander 2.0, a Moen Star Board GMSK node adapter modem, plugged into the data jack in the back of my Yaesu FT 897D. When it beacons every 10 minutes, just like I programmed it to, the TX LED lights up on the GMSK board, and it keys up the FT 897D. The transmit LED lights up there as well, and the signal bar on the radio comes up. However, I can not get my ID-51A Plus to communicate with the hotspot. What am I doing wrong?
|
|
k7rex
New Member
Posts: 10
|
Post by k7rex on Oct 27, 2016 9:53:47 GMT -7
For KC9SIO: Sounds like your problem can be fixed by re-running NAWinCFG and NAWinTEST board adjustments. See Step 4 on Building a D-Star Compatible Hotspot on www.k6jm.com/hs-setup.htm... For AI2M: After trying everything suggested by both this forum and from the dealer the dealer offered a warranty swap and the replacement board worked. No clue why the first board stopped working correctly...
|
|