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.
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.AF6VN wrote: ↑Mon Aug 31, 2020 9:31 pmAt 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
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.
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
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