High BER and invalid fich error

User avatar
AI7HL
Posts: 30
Joined: Tue May 18, 2021 6:16 pm

High BER and invalid fich error

Post by AI7HL »

What gives? 11.4% loss?

20:58:20 c4fmcalltracker: got header
20:58:20 c4fmpacket: header
20:58:20 dst: *****EAMas src: AI7HL
20:58:20 dl: ul:
20:58:20 c4fmcalltracker: voice call started, dst: *****EAMas dgid: 0 src: AI7HL id: 2cbe92a2aea80642
20:58:20 nvmm-csd: ignoring special callsign *****EAMas
20:58:20 c4fm4dmrcon: new call, cid 2cbe92a2aea80642
20:58:21 c4fmcalltracker: invalid fich
20:58:21 c4fm4dmrcon: call start, using ids dst 98 src 3138590 for this grp call
20:58:21 c4fmcalltracker: invalid fich
20:58:22 c4fmcalltracker: invalid fich
20:58:22 homebrew: ping sent
20:58:22 homebrew: pong received
20:58:22 c4fmcalltracker: invalid fich
20:58:22 c4fmcalltracker: invalid fich
20:58:22 c4fmcalltracker: invalid fich
20:58:22 c4fmcalltracker: invalid fich
20:58:24 c4fmcalltracker: invalid fich
20:58:24 c4fmcalltracker: invalid fich
20:58:25 c4fmcalltracker: invalid fich
20:58:25 c4fmcalltracker: invalid fich
20:58:26 c4fmcalltracker: invalid fich
20:58:27 c4fmcalltracker: invalid fich
20:58:27 c4fmcalltracker: invalid fich
20:58:27 c4fmcalltracker: invalid fich
20:58:28 c4fmcalltracker: invalid fich
20:58:28 homebrew: ping sent
20:58:28 homebrew: pong received
20:58:28 c4fmcalltracker: invalid fich
20:58:28 c4fmcalltracker: invalid fich
20:58:29 c4fmcalltracker: got terminator
20:58:29 c4fmpacket: header
20:58:29 dst: *****EAMas src: AI7HL
20:58:29 dl: ul:
20:58:29 c4fmcalltracker: call ended, dur 8.1s ber 11.4% loss 0.0% rssi -61
20:58:29 c4fmcall: tx confirm
20:58:29 c4fm4dmrcon: call end, timeout: 0
20:58:29 batt: stat: charge/100mA, 100% (4084mV 35C est. 0h0m)
20:58:30 modem-djq: emptied, closing
User avatar
HA2NON
SharkRF team
SharkRF team
Posts: 6270
Joined: Fri Mar 25, 2016 3:33 pm
Contact:

Re: High BER and invalid fich error

Post by HA2NON »

Make sure the Half Deviation setting is turned off in your transceiver, and use plain C4FM modem mode on the openSPOT. If there's no such setting in your transceiver's menu, then you have to use C4FM Half Deviation modem mode, and run C4FM Half Deviation AutoCal on the openSPOT (or manually change the RX offset on the Modem page for the lowest BER). Test the connection between your transceiver and the openSPOT using the built-in local echo service. http://manuals.sharkrf.com/openspot3/en ... ho-service
Norbert Varga, HA2NON
SharkRF Team
User avatar
AI7HL
Posts: 30
Joined: Tue May 18, 2021 6:16 pm

Re: High BER and invalid fich error

Post by AI7HL »

HA2NON wrote: Fri Nov 26, 2021 7:43 am Make sure the Half Deviation setting is turned off in your transceiver, and use plain C4FM modem mode on the openSPOT. If there's no such setting in your transceiver's menu, then you have to use C4FM Half Deviation modem mode, and run C4FM Half Deviation AutoCal on the openSPOT (or manually change the RX offset on the Modem page for the lowest BER). Test the connection between your transceiver and the openSPOT using the built-in local echo service. http://manuals.sharkrf.com/openspot3/en ... ho-service
I'm having the same trouble with all my C4FM radios. So I was suspecting a problem with the openSPOT.
Last edited by AI7HL on Sat Nov 27, 2021 8:08 am, edited 1 time in total.
User avatar
AI7HL
Posts: 30
Joined: Tue May 18, 2021 6:16 pm

Re: High BER and invalid fich error

Post by AI7HL »

HA2NON wrote: Fri Nov 26, 2021 7:43 am Make sure the Half Deviation setting is turned off in your transceiver, and use plain C4FM modem mode on the openSPOT. If there's no such setting in your transceiver's menu, then you have to use C4FM Half Deviation modem mode, and run C4FM Half Deviation AutoCal on the openSPOT (or manually change the RX offset on the Modem page for the lowest BER). Test the connection between your transceiver and the openSPOT using the built-in local echo service. http://manuals.sharkrf.com/openspot3/en ... ho-service
I've never seen a Yaesu C4FM radio that had anything resembling a setting for "half deviation". Could you be more specific as to where to find this setting?

Yaesu radios have a DN (digital narrow) mode and a VW (voice wide) mode. Is this what you are referring to? Trying to run autocal in digital narrow mode does not work.
Last edited by AI7HL on Sat Nov 27, 2021 8:14 am, edited 1 time in total.
User avatar
HA2NON
SharkRF team
SharkRF team
Posts: 6270
Joined: Fri Mar 25, 2016 3:33 pm
Contact:

Re: High BER and invalid fich error

Post by HA2NON »

For an example, you can find this setting on the FT2D by pressing the DISP button, and select TX/RX, and then MODE. Some transceivers don't have this setting and they only operate in half deviation mode. In this case proceed with AutoCal and/or RX offset adjust, as I wrote before.
Norbert Varga, HA2NON
SharkRF Team
User avatar
AI7HL
Posts: 30
Joined: Tue May 18, 2021 6:16 pm

Re: High BER and invalid fich error

Post by AI7HL »

HA2NON wrote: Sat Nov 27, 2021 7:27 am For an example, you can find this setting on the FT2D by pressing the DISP button, and select TX/RX, and then MODE. Some transceivers don't have this setting and they only operate in half deviation mode. In this case proceed with AutoCal and/or RX offset adjust, as I wrote before.
Thank you for pointing me to the right spot. That was extremely helpful. The setting is labeled "FM Bandwidth" on the FT-3DR. Once I switched to narrow mode, autocal worked great. I was off by 200.

I switched to narrow mode... ran autocal... then switched back to wide.

After doing a couple of tests... it looks like that has likely fixed the problem.

I think your help was exactly what I needed.
User avatar
AI7HL
Posts: 30
Joined: Tue May 18, 2021 6:16 pm

Re: High BER and invalid fich error

Post by AI7HL »

AI7HL wrote: Sat Nov 27, 2021 8:00 am
HA2NON wrote: Sat Nov 27, 2021 7:27 am For an example, you can find this setting on the FT2D by pressing the DISP button, and select TX/RX, and then MODE. Some transceivers don't have this setting and they only operate in half deviation mode. In this case proceed with AutoCal and/or RX offset adjust, as I wrote before.
Thank you for pointing me to the right spot. That was extremely helpful. The setting is labeled "FM Bandwidth" on the FT-3DR. Once I switched to narrow mode, autocal worked great. I was off by 200.

I switched to narrow mode... ran autocal... then switched back to wide.

After doing a couple of tests... it looks like that has likely fixed the problem.

I think your help was exactly what I needed.
Turns out this did not fix my problem. So for all practical purposes, the cross mode feature of all three of my openSPOT3 hotspots from C4FM to DMR seems to be broken. Any other ideas?

I've tried this with multiple C4FM radios, and multiple openSPOT3 hotspots. The problem is consistent.

If I use my D-Star radio in place of my C4FM radio... cross mode works just fine. Cross mode from C4FM does not.

I should also point out... the problem is somewhat intermittent. Some transmissions are perfect with no errors. Others are a complete disaster and there are many errors in the log.
Last edited by AI7HL on Sun Nov 28, 2021 6:32 am, edited 1 time in total.
User avatar
HA5OGR
Posts: 638
Joined: Sat Mar 26, 2016 7:32 pm
Location: Dunavarsány
Contact:

Re: High BER and invalid fich error

Post by HA5OGR »

I connected to talkgroup 98 (radio test) like you. I'm using an FT-2DE radio and Openspot 3 but I haven't activated the half deviation feature in radio menu. I attach my log extract.

05:53:46 nvmm: net check
05:53:46 nvmm: net check
05:53:47 nvmm: net check ok (1017 ms)
05:53:48 homebrew: ping sent
05:53:48 homebrew: pong received
05:53:49 c4fmcalltracker: got header
05:53:49 c4fmpacket: header
05:53:49 dst: *****E5m3M src: HA5OGR
05:53:49 dl: ul:
05:53:49 c4fmcalltracker: voice call started, dst: *****E5m3M dgid: 0 src: HA5OGR id: 942c52eec44ab626
05:53:49 nvmm-csd: ignoring special callsign *****E5m3M
05:53:49 c4fm4dmrcon: new call, cid 942c52eec44ab626
05:53:50 aprs-queue: added delayed msg type 2 to slot #3 HA5OGR-7
05:53:50 aprs-queue: processing delayed slot #3 HA5OGR-7 type 2
05:53:50 c4fm4dmrcon: call start, using ids dst 98 src 2167002 for this grp call
05:53:51 aprs-queue: added delayed msg type 2 to slot #4 HA5OGR-7
05:53:51 aprs-queue: processing delayed slot #4 HA5OGR-7 type 2
05:53:51 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:53:51 aprs-queue: processing delayed slot #0 HA5OGR-7 type 2
05:53:52 aprs-queue: added delayed msg type 2 to slot #1 HA5OGR-7
05:53:52 aprs-queue: processing delayed slot #1 HA5OGR-7 type 2
05:53:53 aprs-queue: added delayed msg type 2 to slot #2 HA5OGR-7
05:53:53 aprs-queue: processing delayed slot #2 HA5OGR-7 type 2
05:53:54 aprs-queue: added delayed msg type 2 to slot #3 HA5OGR-7
05:53:54 homebrew: ping sent
05:53:54 homebrew: pong received
05:53:55 aprs-queue: added delayed msg type 2 to slot #3 HA5OGR-7
05:53:55 batt: stat: done/500mA, 100% (new) (4080mV 35C)
05:53:55 aprs-queue: added delayed msg type 2 to slot #3 HA5OGR-7
05:53:56 aprs-queue: added delayed msg type 2 to slot #3 HA5OGR-7
05:53:57 aprs-queue: added delayed msg type 2 to slot #3 HA5OGR-7
05:53:58 c4fmcalltracker: got terminator
05:53:58 c4fmpacket: header
05:53:58 dst: *****E5m3M src: HA5OGR
05:53:58 dl: ul:
05:53:58 c4fmcalltracker: call ended, dur 8.7s ber 0.1% loss 0.0% rssi -90
05:53:58 c4fmcall: tx confirm
05:53:58 c4fm4dmrcon: call end, timeout: 0
05:53:59 modem-djq: emptied, closing
05:54:01 homebrew: ping sent
05:54:01 homebrew: pong received

During my QSO on talkgroup 216 I didn't notice also any error that you're talking about.

05:32:29 homebrew: ping sent
05:32:29 homebrew: ping sent
05:32:29 homebrew: pong received
05:32:32 c4fmcalltracker: got header
05:32:32 c4fmpacket: header
05:32:32 dst: *****E5m3M src: HA5OGR
05:32:32 dl: ul:
05:32:32 c4fmcalltracker: voice call started, dst: *****E5m3M dgid: 0 src: HA5OGR id: 7260e652c2ec8cea
05:32:32 nvmm-csd: ignoring special callsign *****E5m3M
05:32:32 c4fm4dmrcon: new call, cid 7260e652c2ec8cea
05:32:33 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:32:33 aprs-queue: processing delayed slot #0 HA5OGR-7 type 2
05:32:33 batt: stat: charge/500mAc4fm4dmrcon: call start, using ids dst 216 src 2167002 for this grp call
05:32:33 , 100% (4190mV 33C est. 0h2m)
05:32:33 aprs-queue: added delayed msg type 2 to slot #1 HA5OGR-7
05:32:33 aprs-queue: processing delayed slot #1 HA5OGR-7 type 2
05:32:34 aprs-queue: added delayed msg type 2 to slot #2 HA5OGR-7
05:32:34 aprs-queue: processing delayed slot #2 HA5OGR-7 type 2
05:32:35 homebrew: ping sent
05:32:35 homebrew: pong received
05:32:35 aprs-queue: added delayed msg type 2 to slot #3 HA5OGR-7
05:32:35 aprs-queue: processing delayed slot #3 HA5OGR-7 type 2
05:32:36 aprs-queue: added delayed msg type 2 to slot #4 HA5OGR-7
05:32:36 aprs-queue: processing delayed slot #4 HA5OGR-7 type 2
05:32:37 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:32:37 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:32:38 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:32:39 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:32:40 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:32:41 homebrew: ping sent
05:32:41 homebrew: pong received
05:32:41 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:32:41 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:32:42 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:32:43 batt: stat: charge/500mA, 100% (4190mV 33C est. 0h2m)
05:32:43 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:32:43 nvmm: net check
05:32:43 nvmm: net check ok (12 ms)
05:32:43 c4fmcalltracker: got terminator
05:32:43 c4fmpacket: header
05:32:43 dl: ul:
05:32:43 c4fmcalltracker: call ended, dur 11.6s ber 0.1% loss 0.0% rssi -56
05:32:44 c4fmcall: tx confirm
05:32:44 c4fm4dmrcon: call end, timeout: 0
05:32:45 modem-djq: emptied, closing
05:32:47 homebrew: ping sent
05:32:47 homebrew: pong received
05:32:53 batt: stat: charge/500mA, 100% (4190mV 33C est. 0h2m)
05:32:54 homebrew: ping sent
05:32:54 homebrew: pong received
05:33:00 homebrew: ping sent
05:33:00 homebrew: pong received
05:33:02 dmrcalltracker[0]: group call from net to 216, rerouting to 9
05:33:02 dmrcalltracker[0]: grp voice call started, dst: 9 src: 2163007 id: 54b6ce842c7cc816
05:33:02 dmrcalltracker[0]: group call from net to 216, rerouting to 9
05:33:02 dmrcalltracker[0]: group call from net to 216, rerouting to 9
05:33:02 c4fm4dmrcon: new call, cid 54b6ce842c7cc816
05:33:02 dmrcalltracker[0]: group call from net to 216, rerouting to 9
05:33:03 batt: stat: charge/500mA, 100% (4190mV 33C est. 0h2m)
05:33:03 dmrcalltracker[0]: group call from net to 216, rerouting to 9
05:33:03 c4fm4dmrcon: call start, using src callsign HA3TBL for this call
05:33:04 dmrcalltracker[0]: group call from net to 216, rerouting to 9
05:33:04 aprs-queue: processing delayed slot #0 HA5OGR-7 type 2
05:33:04 dmrcalltracker[0]: group call from net to 216, rerouting to 9
05:33:05 dmrcalltracker[0]: group call from net to 216, rerouting to 9
05:33:06 homebrew: ping sent
05:33:06 homebrew: pong received
05:33:06 dmrcalltracker[0]: group call from net to 216, rerouting to 9
05:33:06 dmrcalltracker[0]: call ended, dur 4.1s ber 0.0% loss 0.0% rssi 0
05:33:06 c4fm4dmrcon: call end, timeout: 0
05:33:08 modem-djq: emptied, closing
05:33:12 c4fmcalltracker: got header
05:33:12 c4fmpacket: header
05:33:12 dst: *****E5m3M src: HA5OGR
05:33:12 dl: ul:
05:33:12 c4fmcalltracker: voice call started, dst: *****E5m3M dgid: 0 src: HA5OGR id: 2cd0603c067a2c10
05:33:12 nvmm-csd: ignoring special callsign *****E5m3M
05:33:12 homebrew: ping sent
05:33:12 c4fm4dmrcon: new call, cid 2cd0603c067a2c10
05:33:12 homebrew: pong received
05:33:12 aprs-queue: added delayed msg type 2 to slot #1 HA5OGR-7
05:33:12 aprs-queue: processing delayed slot #1 HA5OGR-7 type 2
05:33:13 c4fm4dmrcon: call start, using ids dst 216 src 2167002 for this grp call
05:33:13 batt: stat: charge/500mA, 100% (4190mV 33C est. 0h2m)
05:33:13 aprs-queue: added delayed msg type 2 to slot #2 HA5OGR-7
05:33:13 aprs-queue: processing delayed slot #2 HA5OGR-7 type 2
05:33:14 aprs-queue: added delayed msg type 2 to slot #3 HA5OGR-7
05:33:14 aprs-queue: processing delayed slot #3 HA5OGR-7 type 2
05:33:15 aprs-queue: added delayed msg type 2 to slot #4 HA5OGR-7
05:33:15 aprs-queue: processing delayed slot #4 HA5OGR-7 type 2
05:33:16 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:16 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:17 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:18 homebrew: ping sent
05:33:18 homebrew: pong received
05:33:18 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:19 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:20 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:20 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:21 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:22 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:23 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:23 batt: stat: charge/500mA, 100% (4190mV 33C est. 0h2m)
05:33:24 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:24 homebrew: ping sent
05:33:24 homebrew: pong received
05:33:24 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:25 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:26 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:27 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:28 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:28 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:29 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:30 homebrew: ping sent
05:33:30 homebrew: pong received
05:33:31 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:32 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:32 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:33 batt: stat: charge/500mA, 100% (4190mV 33C est. 0h2m)
05:33:33 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:34 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:35 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:35 aprs-queue: processing delayed slot #0 HA5OGR-7 type 2
05:33:36 aprs-queue: added delayed msg type 2 to slot #1 HA5OGR-7
05:33:36 homebrew: ping sent
05:33:36 homebrew: pong received
05:33:36 aprs-queue: added delayed msg type 2 to slot #1 HA5OGR-7
05:33:37 aprs-queue: added delayed msg type 2 to slot #1 HA5OGR-7
05:33:38 aprs-queue: added delayed msg type 2 to slot #1 HA5OGR-7
05:33:39 aprs-queue: added delayed msg type 2 to slot #1 HA5OGR-7
05:33:40 aprs-queue: added delayed msg type 2 to slot #1 HA5OGR-7
05:33:40 aprs-queue: added delayed msg type 2 to slot #1 HA5OGR-7
05:33:41 aprs-queue: added delayed msg type 2 to slot #1 HA5OGR-7
05:33:42 homebrew: ping sent
05:33:42 homebrew: pong received
05:33:42 aprs-queue: added delayed msg type 2 to slot #1 HA5OGR-7
05:33:43 aprs-queue: added delayed msg type 2 to slot #1 HA5OGR-7
05:33:43 batt: stat: charge/500mAnvmm: net check
05:33:43 , 100% (4190mV 33C est. 0h2m)
05:33:43 nvmm: net check ok (16 ms)
05:33:44 aprs-queue: added delayed msg type 2 to slot #1 HA5OGR-7
05:33:44 aprs-queue: processing delayed slot #1 HA5OGR-7 type 2
05:33:44 aprs-queue: added delayed msg type 2 to slot #2 HA5OGR-7
05:33:44 aprs-queue: processing delayed slot #2 HA5OGR-7 type 2
05:33:45 aprs-queue: added delayed msg type 2 to slot #3 HA5OGR-7
05:33:45 aprs-queue: processing delayed slot #3 HA5OGR-7 type 2
05:33:46 aprs-queue: added delayed msg type 2 to slot #4 HA5OGR-7
05:33:46 aprs-queue: processing delayed slot #4 HA5OGR-7 type 2
05:33:47 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:48 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:48 homebrew: ping sent
05:33:48 homebrew: pong received
05:33:48 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:49 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:51 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:52 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:52 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:53 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:53 batt: stat: charge/500mA, 100% (4190mV 33C est. 0h2m)
05:33:54 homebrew: ping sent
05:33:54 homebrew: pong received
05:33:54 aprs-queue: added delayed msg type 2 to slot #0 HA5OGR-7
05:33:55 c4fmcalltracker: got terminator
05:33:55 c4fmpacket: header
05:33:55 dst: *****E5m3M src: HA5OGR
05:33:55 dl: ul:
05:33:55 c4fmcalltracker: call ended, dur 42.1s ber 0.1% loss 0.0% rssi -57
05:33:55 c4fmcall: tx confirm
05:33:55 c4fm4dmrcon: call end, timeout: 0
05:33:56 modem-djq: emptied, closing
05:33:59 dmrcalltracker[0]: group call from net to 216, rerouting to 9
05:33:59 dmrcalltracker[0]: grp voice call started, dst: 9 src: 2163007 id: 58b40242cc1c1476
05:33:59 dmrcalltracker[0]: group call from net to 216, rerouting to 9
05:33:59 dmrcalltracker[0]: group call from net to 216, rerouting to 9
05:33:59 c4fm4dmrcon: new call, cid 58b40242cc1c1476
05:33:59 dmrcalltracker[0]: group call from net to 216, rerouting to 9
05:34:00 homebrew: ping sent
05:34:00 homebrew: pong received
05:34:00 dmrcalltracker[0]: group call from net to 216, rerouting to 9
05:34:00 c4fm4dmrcon: call start, using src callsign HA3TBL for this call
05:34:01 dmrcalltracker[0]: group call from net to 216, rerouting to 9
05:34:02 dmrcalltracker[0]: group call from net to 216, rerouting to 9
73 de Lajos
Openspot alpha tester
User avatar
AI7HL
Posts: 30
Joined: Tue May 18, 2021 6:16 pm

Re: High BER and invalid fich error

Post by AI7HL »

HA5OGR wrote: Sun Nov 28, 2021 5:14 am I connected to talkgroup 98 (radio test) like you. I'm using an FT-2DE radio and Openspot 3 but I haven't activated the half deviation feature in radio menu. I attach my log extract.
I only set it to narrow mode to run the autocal. Then I set it back to wide. Also... I did a complete reset on my openSPOT... twice.

I will do more testing and get back to you with the results.
User avatar
HA5OGR
Posts: 638
Joined: Sat Mar 26, 2016 7:32 pm
Location: Dunavarsány
Contact:

Re: High BER and invalid fich error

Post by HA5OGR »

Try moving your radio closer to your Openspot.
73 de Lajos
Openspot alpha tester
Post Reply