D-Star Connection Issue with multiple hotspots - RESOLVED

[k0eg]

Thank you all for your continued suggestions and assistance!!!

id also suggest you change DMR IDs by adding an ssid to each eg. 315070801 1315070802 (01) (02) this way the DMR server will see each installation as a seperate connection.

Thank you for this - I've had this configuration on DMR in place since last fall - so all is good here. DMR works exactly as I desire - being able to leave the mobile in my truck and able to operate on both without having to move the hotspots around.

Connect your mobile installation to the home network to check if your getting blocked by your mobile broadband service provider.

Connect your mobile installation to the home network to check if your getting blocked by your mobile broadband service provider.

At this point I'd have to concur... Cable both up to your home router (just to avoid WiFi interference at first). Then try using each system from the radio (recommend not linking both to the same reflector). If you can link through both modules/frequencies when cabled to the home router, THEN

I like you suggest, I'm not sure why I would not have tried that before. Given my time to perform that configuration, I thought I would do one additional check to try to rule out any network issues with linking.

Linking / unlinking network test results:
With this test, I believe, we can rule out any network issues with linking and unlinking being network related.

Verification of config: Radio is able to link/unlink REF004C on home Pi-Star, only changing R1 / R2 settings.

Test: Attempt link from radio to REF004C from radio on mobile Pi-Star
Transmit: REF004CL to mobile Pi-Star
Result: Unsuccessful / no change
Observation: Log shows receipt of REF004CL, dashboard also shows receipt of transmission in RF section, but no link takes place

Test: Attempt manual link on Pi-Star using dashboard D-Star Link Mananger to REF004C on mobile Pi-Star
Result: SUCCESSFUL
Observation:

• Log show successful link/unlink, dashboard shows successful link/unlink
  Radio receives Pi-Star "Linked to REF004C" and "Unlinked" when manual unlink is performed.

Dashboard after manual link

1 - Manual Link.jpg (69.98 KiB) Viewed 1920 times

Dashboard after attempt at radio unlink - unsuccessful

2 - Radio Unlink.png (86.16 KiB) Viewed 1920 times

Dashboard after manual unlink

3 - Manual Unlink.png (84.75 KiB) Viewed 1920 times

Log of above on mobile Pi-Star

Code: Select all

M: 2020-09-01 16:00:39.891 D-Star, received RF header from K0EG /KARL to I
M: 2020-09-01 16:00:40.203 D-Star, received RF end of transmission from K0EG /KARL to I, 0.5 seconds, BER: 0.0%, RSSI: -47/-47/-47 dBm
M: 2020-09-01 16:01:05.656 D-Star, received RF end of transmission from K0EG /KARL to REF004CL, 0.5 seconds, BER: 0.0%, RSSI: -47/-47/-47 dBm
M: 2020-09-01 16:01:41.282 D-Star, received network end of transmission from K0EG /INFO to CQCQCQ , 7.0 seconds, 0% packet loss, BER: 0.0%
M: 2020-09-01 16:02:53.029 D-Star, received RF header from K0EG /KARL to U
M: 2020-09-01 16:02:53.149 D-Star, received RF end of transmission from K0EG /KARL to U, 0.3 seconds, BER: 0.0%, RSSI: -47/-47/-47 dBm
M: 2020-09-01 16:04:11.867 D-Star, received network header from K0EG /INFO to CQCQCQ

Log of D-Star conversation on mobile Pi-Star

Code: Select all

M: 2020-09-01 16:37:49.973 D-Star, received network end of transmission from K0EG /INFO to CQCQCQ , 7.0 seconds, 0% packet loss, BER: 0.0%
M: 2020-09-01 16:43:55.644 D-Star, received network header from NA3P /DICK to CQCQCQ via REF004 C
M: 2020-09-01 16:43:58.189 D-Star, received network end of transmission from NA3P /DICK to CQCQCQ , 2.7 seconds, 0% packet loss, BER: 0.0%
M: 2020-09-01 16:44:14.678 D-Star, received network header from W3YD /AMBE to CQCQCQ via REF004 C
M: 2020-09-01 16:44:31.577 D-Star, received network header from N2JBJ / to CQCQCQ via REF004 C
M: 2020-09-01 16:44:34.098 D-Star, received network end of transmission from N2JBJ / to CQCQCQ , 2.7 seconds, 0% packet loss, BER: 0.0%
M: 2020-09-01 16:44:37.403 D-Star, received network header from W3YD /AMBE to CQCQCQ via REF004 C
M: 2020-09-01 16:44:46.679 D-Star, received network end of transmission from W3YD /AMBE to CQCQCQ , 9.6 seconds, 8% packet loss, BER: 0.0%
M: 2020-09-01 16:44:50.955 D-Star, received network header from N2JBJ / to CQCQCQ via REF004 C
M: 2020-09-01 16:44:59.205 D-Star, received network header from W3YD /AMBE to CQCQCQ via REF004 C
M: 2020-09-01 16:45:00.579 D-Star, network watchdog has expired, 1.1 seconds, 98% packet loss, BER: 0.0%
M: 2020-09-01 16:46:09.017 D-Star, received network end of transmission from N2JBJ / to CQCQCQ , 42.2 seconds, 0% packet loss, BER: 0.0%
M: 2020-09-01 16:46:47.396 D-Star, received network end of transmission from W3YD /AMBE to CQCQCQ , 34.8 seconds, 0% packet loss, BER: 0.0%
M: 2020-09-01 16:46:51.183 D-Star, received network header from N2JBJ / to CQCQCQ via REF004 C
M: 2020-09-01 16:49:11.447 D-Star, received network end of transmission from W3YD /AMBE to CQCQCQ , 73.6 seconds, 0% packet loss, BER: 0.0%
M: 2020-09-01 16:49:24.235 D-Star, received network end of transmission from N2JBJ / to CQCQCQ , 8.4 seconds, 0% packet loss, BER: 0.0%
M: 2020-09-01 16:49:27.933 D-Star, received network header from W3YD /AMBE to CQCQCQ via REF004 C
M: 2020-09-01 16:49:30.417 D-Star, received network end of transmission from W3YD /AMBE to CQCQCQ , 2.4 seconds, 0% packet loss, BER: 0.0%
M: 2020-09-01 16:52:34.564 D-Star, received network header from K4QBS /AMBE to CQCQCQ via REF004 C
M: 2020-09-01 16:52:38.636 D-Star, received network end of transmission from K4QBS /AMBE to CQCQCQ , 4.0 seconds, 0% packet loss, BER: 0.0%
Download the log: here

Test radios - I tested but Mobile Pi-Star configuration with both my ID-51a+2 and IC-7100
- both are able to link/unlink with the home Pi-Star, but not with the mobile Pi-Star
- both have two repeater memories defined in the D-Star repeater list
- Both radios are able to hear from and transmit voice on both Pi-Stars
- Both radios are able to receive digital data (show callsigns, etc) in the Msg: area
- Both Pi-Stars log the network header from both radios


Findings:
1. Mobile Pi-Star manual linking works
1.1 (I suggest) Rules out (network/firewall/layer 2) issue with Pi-Star connection to D-Star network
2. Issue remains with linking/unlinking from radio

Next steps??? Suggestions???
1. Is there more detailed logging for Pi-Star / D-Star that can be enabled?
2. Is there any logging that can be acquired from the backend / D-Star network to see what's being received from the Pi-Star?
If you know how I can accomplish the above, please comment.

Does this isolate the issue to being on the Pi-Star? Or, is this still a network traffic (hand-shaking/D-Star protocol)issue?


Thank you and 73s

Karl

[M1DNS]

If the attempts of linking with dstar manager actually result in both linking then theoretically that can only leave the radio setups between memories. Check and double check that each is exactly the same between the memory settings that link Vs the settings of the radios memory channel that doesnt link.

Sent from my SM-G935F using Tapatalk

[AF6VN]

The only thing I notice is that your log does NOT show a "received RF header" for the link command. It shows that it received an INFO command header and end Tx, and THEN reports an end Tx for the link command, which has me perplexed.

(had to restart system as too much DMR traffic, and my default is for REF030C)

Code: Select all

M: 2020-09-02 21:35:07.414 MMDVMHost-20200615_Pi-Star_v4 is running
M: 2020-09-02 21:35:10.507 D-Star link status set to "Linking to REF030 C "
M: 2020-09-02 21:35:10.866 D-Star link status set to "Linked to REF030 C  "
M: 2020-09-02 21:35:12.880 D-Star, received network header from AF6VN   /INFO to CQCQCQ   via REF030 C
M: 2020-09-02 21:35:19.846 D-Star, received network end of transmission from AF6VN   /INFO to CQCQCQ  , 7.0 seconds, 0% packet loss, BER: 0.0%
M: 2020-09-02 21:35:32.834 D-Star, received RF header from AF6VN   /D74A to REF001CL
M: 2020-09-02 21:35:32.840 D-Star link status set to "Linking to REF001 C "
M: 2020-09-02 21:35:32.997 D-Star link status set to "Linked to REF001 C  "
M: 2020-09-02 21:35:34.160 D-Star, received RF end of transmission from AF6VN   /D74A to REF001CL, 1.5 seconds, BER: 0.0%
M: 2020-09-02 21:35:36.231 D-Star, received network header from AF6VN   /INFO to CQCQCQ   via REF001 C
M: 2020-09-02 21:35:43.247 D-Star, received network end of transmission from AF6VN   /INFO to CQCQCQ  , 7.0 seconds, 0% packet loss, BER: 0.0%
M: 2020-09-02 21:35:52.707 D-Star, received RF header from AF6VN   /D74A to CQCQCQ
M: 2020-09-02 21:35:53.592 D-Star, received RF end of transmission from AF6VN   /D74A to CQCQCQ  , 1.0 seconds, BER: 0.0%

M: 2020-09-02 21:36:10.171 D-Star, received RF header from AF6VN   /D74A to        I
M: 2020-09-02 21:36:11.513 D-Star, received RF end of transmission from AF6VN   /D74A to        I, 1.5 seconds, BER: 0.0%
M: 2020-09-02 21:36:13.577 D-Star, received network header from AF6VN   /INFO to CQCQCQ   via REF001 C
M: 2020-09-02 21:36:20.598 D-Star, received network end of transmission from AF6VN   /INFO to CQCQCQ  , 7.0 seconds, 0% packet loss, BER: 0.0%
M: 2020-09-02 21:36:30.399 D-Star, received RF header from AF6VN   /D74A to REF030CL
M: 2020-09-02 21:36:30.404 D-Star link status set to "Linking to REF030 C "
M: 2020-09-02 21:36:30.518 D-Star link status set to "Linked to REF030 C  "
M: 2020-09-02 21:36:31.715 D-Star, received RF end of transmission from AF6VN   /D74A to REF030CL, 1.5 seconds, BER: 0.0%
M: 2020-09-02 21:36:33.775 D-Star, received network header from AF6VN   /INFO to CQCQCQ   via REF030 C
M: 2020-09-02 21:36:40.736 D-Star, received network end of transmission from AF6VN   /INFO to CQCQCQ  , 7.0 seconds, 0% packet loss, BER: 0.0%
pi-star@pi-star-3b(ro):pi-star$

[k0eg]

I want to thank the Elmers who submitted thoughts and ideas, and most of all patience with pouring over the information I posted.

Those that pointed to the programming on the radio were correct.

I version control my code plugs and as was suggested, started from scratch only to find the following issue, once I compared a new working config with the old configuration.

Screen Shot 2020-09-15 at 2.45.00 PM.png (20.7 KiB) Viewed 1868 times

The gateway need to be the correct callsign - K0EG::G {minus ":"s} and what I had accidently entered was the letter "O" instead of the number zero "0".

I don't know how many times I had looked at the entry, but it certainly didn't stand out. As a result I'm going to see if I can change the font in the system to address any future issues.

Thank you all for your help!

73s de Karl, K0EG