Can no longer transmit from C4FM radio to D-Star

VK3FD
Posts: 7
Joined: Mon Mar 11, 2019 5:04 am

Re: Can no longer transmit from C4FM radio to D-Star

Post by VK3FD »

Seems to be working ok DMR to DStar, otherwise non-operational for C4FM to DStar and for locating REF/XRF reflectors using DStar radio Icom 51A. Previously (pre-update) to V17, all worked without problems. Ian VK3FD

User avatar
HA2NON
SharkRF team
SharkRF team
Posts: 5023
Joined: Fri Mar 25, 2016 3:33 pm
Contact:

Re: Can no longer transmit from C4FM radio to D-Star

Post by HA2NON »

VK3FD where do you see this "server not found" message? Which server do you want to connect to?

robertr6 the OS3's call log shows the destination callsign as it is received from your transceiver. Please send us a screenshot which explains what you mean.
Norbert "Nonoo" Varga, HA2NON
SharkRF Team

robertr64
Posts: 15
Joined: Tue Mar 31, 2020 2:03 pm

Re: Can no longer transmit from C4FM radio to D-Star

Post by robertr64 »

There should already be a screen shot above next to the settings

User avatar
HA2NON
SharkRF team
SharkRF team
Posts: 5023
Joined: Fri Mar 25, 2016 3:33 pm
Contact:

Re: Can no longer transmit from C4FM radio to D-Star

Post by HA2NON »

Your screenshot does not show any issues except that you are using an incompatible browser. Please use Chrome or Firefox and save your REF/XRF connector settings again. Maybe your browser is not sending the settings correctly to the OS3, as it is unsupported.

If the REF/XRF connector is set to list Reflectors (and not Gateways), and the "Auto set URCALL to network" checkbox is checked, then your C4FM call is sent with destination callsign CQCQCQ, and source callsign KC3LYZ. The latter is also mentioned in the call log ("Sent as D-STAR group call src KC3LYZ"). The ALL you see in the call log entry is the destination callsign from your C4FM call. This does not affect the D-STAR call to the network.
Norbert "Nonoo" Varga, HA2NON
SharkRF Team

robertr64
Posts: 15
Joined: Tue Mar 31, 2020 2:03 pm

Re: Can no longer transmit from C4FM radio to D-Star

Post by robertr64 »

I tried on the IOS Safari browser and got the same issue. Chrome is very slow on my Windows 10 machine, any plans to support Edge? On a working transmission I see CQCQCQ (from DMR or D-Star, which are ok), but on C4FM it only sporadically sets that.

The first screen is from REF020A via Chrome where nothing is heard aside from the local hotspot frequency.

Now if I switch to REF020E, it comes over on the network ok, and I can hear myself (see 2nd screen)
Attachments
status2.png
openspot3.jpg

User avatar
HA2NON
SharkRF team
SharkRF team
Posts: 5023
Joined: Fri Mar 25, 2016 3:33 pm
Contact:

Re: Can no longer transmit from C4FM radio to D-Star

Post by HA2NON »

With a DMR transmission from your DMR transceiver you'll see the DMR ID your transceiver is transmitting to at the "To:" field. This is the same methodology as for C4FM calls, where you see the destination callsign your C4FM transceiver is transmitting the call.

In cross mode you'll only see CQCQCQ fields in the log entries of calls coming from the network, not from your transceiver (OS3 modem).

Please also post a device log section which shows a call coming from your transceiver to the network. You'll find the device log on the Status page.
Norbert "Nonoo" Varga, HA2NON
SharkRF Team

robertr64
Posts: 15
Joined: Tue Mar 31, 2020 2:03 pm

Re: Can no longer transmit from C4FM radio to D-Star

Post by robertr64 »

ok here is the log file:
11:39:36 httpsrv[0]: websocket opened with token beb2b8a4
11:39:36 httpsrv[0]: websocket opened with token beb2b8a4
11:39:37 batt: stat: done/500mAref: got ping, replying
11:39:37 , 98% (4080mV (new) 35C)
11:39:38 ref: got ping, replying
11:39:39 ref: got ping, replying
11:39:40 ref: got ping, replying
11:39:41 ref: got ping, replying
11:39:42 ref: got ping, replying
11:39:43 ref: got ping, replying
11:39:43 ref: got ccs ping
11:39:43 ccs: sending pong
11:39:44 ref: got ping, replying
11:39:45 ref: got ping, replying
11:39:46 ref: got ping, replying
11:39:47 ref: got ping, replying
11:39:47 batt: stat: done/500mA, 98% (4080mV (new) 35C)
11:39:48 ref: got ping, replying
11:39:49 ref: got ping, replying
11:39:50 ref: got ping, replying
11:39:51 ref: got ping, replying
11:39:52 ref: got ping, replying
11:39:53 ref: got ping, replying
11:39:54 ref: got ping, replying
11:39:54 ref: got ccs ping
11:39:54 ccs: sending pong
11:39:55 ref: got ping, replying
11:39:56 ref: got ping, replying
11:39:57 ref: got ping, replying
11:39:57 batt: stat: done/500mA, 98% (4086mV (new) 35C)
11:39:58 ref: got ping, replying
11:39:59 ref: got ping, replying
11:40:00 ref: got ping, replying
11:40:01 ref: got ping, replying
11:40:02 ref: got ping, replying
11:40:03 ref: got ping, replying
11:40:04 ref: got ping, replying
11:40:05 ref: got ping, replying
11:40:05 ref: got ccs ping
11:40:05 ccs: sending pong
11:40:06 ref: got ping, replying
11:40:07 ref: got ping, replying
11:40:07 batt: stat: done/500mA, 98% (4086mV (new) 35C)
11:40:08 ref: got ping, replying
11:40:09 ref: got ping, replying
11:40:10 ref: got ping, replying
11:40:11 ref: got ping, replying
11:40:12 ref: got ping, replying
11:40:13 ref: got ping, replying
11:40:14 ref: got ping, replying
11:40:15 ref: got ping, replying
11:40:16 ref: got ping, replying
11:40:16 ref: got ccs ping
11:40:16 ccs: sending pong
11:40:17 batt: stat: done/500mA, 98% (4080mV (new) 35C)
11:40:17 ref: got ping, replying
11:40:18 ref: got ping, replying
11:40:18 nvmm: net check
11:40:18 nvmm: net check ok (10 ms)
11:40:19 ref: got ping, replying
11:40:19 c4fmcalltracker: got header
11:40:19 c4fmpacket: header
11:40:19 dst: *****E5Keb src: KC3LYZ
11:40:19 dl: ul:
11:40:19 c4fmcalltracker: voice call started, dst: *****E5Keb dgid: 0 src: KC3LYZ id: 981062fee816ea06
11:40:19 nvmm-csd: ignoring special callsign *****E5Keb
11:40:19 c4fm4dstarcon: new call, cid 981062fee816ea06
11:40:20 ref: got ping, replying
11:40:20 c4fm4dstarcon: call start, using src callsign KC3LYZ for this call
11:40:20 ref: call started
11:40:20 c4fm4dstarcon: dstar msg to net change to 1
11:40:21 ref: got ping, replying
11:40:22 ref: got ping, replying
11:40:22 c4fmcalltracker: got terminator
11:40:22 c4fmpacket: header
11:40:22 dst: *****E5Keb src: KC3LYZ
11:40:22 dl: ul:
11:40:22 c4fmcalltracker: call ended, dur 2.1s ber 0.3% loss 0.0% rssi -46
11:40:22 c4fmcall: tx confirm
11:40:23 c4fm4dstarcon: call end, timeout: 0
11:40:23 ref: call stopped
11:40:23 ref: got ping, replying
11:40:23 modem-djq: emptied, closing
11:40:24 ref: got ping, replying
11:40:25 ref: got ping, replying
11:40:26 ref: got ping, replying
11:40:27 batt: stat: done/500mAref: got ping, replying
11:40:27 , 99% (4088mV (new) 35C)
11:40:27 ref: got ccs ping
11:40:27 ccs: sending pong



Bob Rodriguez - KC3LYZ

VK3FD
Posts: 7
Joined: Mon Mar 11, 2019 5:04 am

Re: Can no longer transmit from C4FM radio to D-Star

Post by VK3FD »

VK3FD here. The C4FM to DSTAR seems to be working this morning, however the OS3 is still not finding DStar from the icom id51 - the message is audio rather than appearing as text and simply says the server is not found - on any reflector I try (the local reflector here in Australia is REF023C). This only on TX as I can hear on Rx. BTW, I am using latest IOS on iPad and IPhone. Ian

VK3FD
Posts: 7
Joined: Mon Mar 11, 2019 5:04 am

Re: Can no longer transmit from C4FM radio to D-Star

Post by VK3FD »

The weird ways of this one continue, but seem right now to be SOLVED. I checked whether the same issues would occur using my OS2, and they did. Having gone back through the Forum’s past posts, there was a suggestion to check whether you were properly registered on DStar: I confirmed on the US trust server that I was, but also found on another search that I apparently was not. I then used my local trust server to confirm that I was. However, the trick that has worked so far is to ensure YOUR RADIO CALLSIGN transmitted is as simple as possible and corresponds exactly with the callsign used when registering your OpenSpot. In my case, my radios were transmitting VK3FD B/ whereas the OS3 registration was my simple straightforward callsign. Overtime, it seems that the OS3 system may have remembered the other radio variations of the callsign , somehow confusing the system. Having my DStar, C4FM and DMR radios now operating cross-mode as needed, all seems to be good (for the present time).
Regards
Ian
VK3FD

robertr64
Posts: 15
Joined: Tue Mar 31, 2020 2:03 pm

Re: Can no longer transmit from C4FM radio to D-Star

Post by robertr64 »

Any more ideas on how to get C4FM radios to transmit on D-Star? When I key up on REF020A, it always says "Openspot3" on the radio so only getting out locally. Luckily, I think this particular reflector has a Fusion bridge, but a lot of others don't yet.

Post Reply