High BER and invalid fich error

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 6:22 am Try moving your radio closer to your Openspot.
I have been using a mobile radio at my QTH with a 10ft antenna in the attic. Set to 5 watts.

What I have done is switched my setup back around to where I will resume using the C4FM radio for DMR. Today I reset all three of my openSPOT3s back to factory settings. We'll see if the problem still occurs. If it does, I will try to do a better job of collecting information.

I have made a handful of transmissions tonight with no errors.
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 »

Your 5 W power may not be enough! Increase your output power!
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 »

Ok. I was incorrect in my previous statement. Out of my three openSPOT3 devices... only one is exhibiting this problem. I just tested all three with C4FM to DMR. Keying up a number of times on #1 produced no errors. Had a 20 minute QSO on #2. No errors. Keyed up #3 a few times and major errors each time. It was also #3 where I first noticed the errors. And it may have been the only one with the errors I am thinking now.

So, what to do? All three were reset. Same radio. One openSPOT3 with consistent errors. Warranty issue?

Here is a piece of my log...

08:59:40 c4fmcalltracker: invalid fich
08:59:40 c4fmcalltracker: invalid fich
08:59:40 c4fmcalltracker: invalid fich
08:59:40 c4fmcalltracker: missing callsigns for late entry
08:59:40 c4fmcalltracker: invalid fich
08:59:40 c4fmcalltracker: invalid fich
08:59:41 c4fmcalltracker: invalid fich
08:59:41 homebrew: ping sent
08:59:41 c4fmcalltracker: missing callsigns for late entry
08:59:41 homebrew: pong received
08:59:41 c4fmcalltracker: invalid fich
08:59:41 c4fmcalltracker: invalid fich
08:59:41 c4fmcalltracker: late entry
08:59:41 c4fmcalltracker: voice call started, dst: *****F0UHX dgid: 0 src: AI7HL id: 1e48b0ee40bcd410
08:59:41 nvmm-csd: ignoring special callsign *****F0UHX
08:59:41 c4fm4dmrcon: new call, cid 1e48b0ee40bcd410
08:59:41 batt: stat: charge/100mAc4fmcalltracker: invalid fich
08:59:41 , 100% (4106mV 33C)
08:59:42 c4fmcalltracker: invalid fich
08:59:42 c4fmcalltracker: invalid fich
08:59:42 c4fmcalltracker: invalid fich
08:59:42 c4fm4dmrcon: call start, using ids dst 9990 src 3138590 for this prv call
08:59:42 c4fmcalltracker: invalid fich
08:59:42 c4fmcalltracker: invalid fich
08:59:43 c4fmcalltracker: invalid fich
08:59:43 c4fmcalltracker: invalid fich
08:59:43 c4fmcalltracker: invalid fich
08:59:43 c4fmcalltracker: invalid fich
08:59:43 c4fmcalltracker: invalid fich
08:59:43 c4fmcalltracker: invalid fich
08:59:44 c4fmcalltracker: invalid fich
08:59:44 c4fmcalltracker: invalid fich
08:59:44 c4fmcalltracker: invalid fich
08:59:44 c4fmcalltracker: invalid fich
08:59:45 c4fmcalltracker: invalid fich
08:59:45 c4fmcalltracker: invalid fich
08:59:45 c4fmcalltracker: invalid fich
08:59:45 c4fmcalltracker: invalid fich
08:59:45 c4fmcalltracker: invalid fich
08:59:46 c4fmcalltracker: invalid fich
08:59:46 c4fmcalltracker: invalid fich
08:59:46 c4fmcalltracker: invalid fich
08:59:46 c4fmcalltracker: invalid fich
08:59:47 c4fmcalltracker: invalid fich
08:59:47 c4fmcalltracker: got terminator
08:59:47 c4fmpacket: header
08:59:47 c4fmcalltracker: call ended, dur 5.7s ber 9.5% loss 0.0% rssi -126
08:59:47 homebrew: ping sent
08:59:47 homebrew: pong received
08:59:47 c4fmcall: tx confirm
08:59:47 c4fm4dmrcon: call end, timeout: 0
08:59:48 modem-djq: emptied, closing
08:59:50 nvmm: net check
08:59:51 dmrcalltracker[0]: prv voice call started, dst: 3138590 src: 9990 id: cae060c49caa72a8
08:59:51 nvmm: net check ok (25 ms)
08:59:51 c4fm4dmrcon: new call, cid cae060c49caa72a8
08:59:51 batt: stat: charge/100mA, 100% (new) (4108mV 33C)
08:59:52 c4fm4dmrcon: call start, using src callsign Parrot - P for this call
08:59:53 homebrew: ping sent
08:59:53 homebrew: pong received
08:59:56 dmrcalltracker[0]: call ended, dur 5.8s ber 0.0% loss 0.0% rssi 0
08:59:57 c4fm4dmrcon: call end, timeout: 0
08:59:58 modem-djq: emptied, closing
08:59:59 homebrew: ping sent
08:59:59 homebrew: pong received
09:00:01 batt: stat: charge/100mA, 100% (4108mV 33C)
09:00:02 c4fmcalltracker: invalid fich
09:00:02 c4fmcalltracker: invalid fich
09:00:02 c4fmcalltracker: missing callsigns for late entry
09:00:02 c4fmcalltracker: invalid fich
09:00:02 c4fmcalltracker: missing callsigns for late entry
09:00:02 c4fmcalltracker: missing callsigns for late entry
09:00:02 c4fmcalltracker: missing callsigns for late entry
09:00:02 c4fmcalltracker: invalid fich
09:00:02 c4fmcalltracker: missing callsigns for late entry
09:00:02 c4fmcalltracker: missing callsigns for late entry
09:00:03 c4fmcalltracker: missing callsigns for late entry
09:00:03 c4fmcalltracker: missing callsigns for late entry
09:00:03 c4fmcalltracker: invalid fich
09:00:03 c4fmcalltracker: missing callsigns for late entry
09:00:03 c4fmcalltracker: invalid fich
09:00:03 c4fmcalltracker: invalid fich
09:00:03 c4fmcalltracker: invalid fich
09:00:03 c4fmcalltracker: invalid fich
09:00:03 c4fmcalltracker: missing callsigns for late entry
09:00:03 c4fmcalltracker: invalid fich
09:00:04 c4fmcalltracker: invalid fich
09:00:04 c4fmcalltracker: invalid fich
09:00:04 c4fmcalltracker: missing callsigns for late entry
09:00:04 c4fmcalltracker: invalid fich
09:00:04 c4fmcalltracker: late entry
09:00:04 c4fmcalltracker: voice call started, dst: *****F0UHX dgid: 0 src: AI7HL id: d8d69ada3eb204a4
09:00:04 nvmm-csd: ignoring special callsign *****F0UHX
09:00:04 c4fm4dmrcon: new call, cid d8d69ada3eb204a4
09:00:04 c4fmcalltracker: invalid fich
09:00:04 c4fmcalltracker: invalid fich
09:00:05 c4fmcalltracker: invalid fich
09:00:05 c4fmcalltracker: invalid fich
09:00:05 c4fmcalltracker: invalid fich
09:00:05 c4fmcalltracker: invalid fich
09:00:05 homebrew: ping sent
09:00:05 homebrew: pong received
09:00:05 c4fm4dmrcon: call start, using ids dst 9990 src 3138590 for this prv call
09:00:05 c4fmcalltracker: invalid fich
09:00:05 c4fmcalltracker: invalid fich
09:00:05 c4fmcalltracker: invalid fich
09:00:05 c4fmcalltracker: invalid fich
09:00:05 c4fmcalltracker: invalid fich
09:00:05 c4fmcalltracker: invalid fich
09:00:06 c4fmcalltracker: invalid fich
09:00:06 c4fmcalltracker: invalid fich
09:00:06 c4fmcalltracker: invalid fich
09:00:06 c4fmcalltracker: invalid fich
09:00:06 c4fmcalltracker: invalid fich
09:00:06 c4fmcalltracker: invalid fich
09:00:06 c4fmcalltracker: invalid fich
09:00:06 c4fmcalltracker: invalid fich
09:00:06 c4fmcalltracker: invalid fich
09:00:06 c4fmcalltracker: invalid fich
09:00:07 c4fmcalltracker: invalid fich
09:00:07 c4fmcalltracker: invalid fich
09:00:07 c4fmcalltracker: invalid fich
09:00:07 c4fmcalltracker: invalid fich
09:00:07 c4fmcalltracker: invalid fich
09:00:07 c4fmcalltracker: invalid fich
09:00:07 c4fmcalltracker: invalid fich
09:00:07 c4fmcalltracker: invalid fich
09:00:07 batt: stat: charge/100mA, 100% (4108mV 33C)
09:00:07 c4fmcalltracker: call ended (timeout), dur 3.4s ber 1.1% loss 0.0% rssi -128
09:00:08 c4fm4dmrcon: call end, timeout: 1
09:00:11 batt: stat change: done/100mA, 100% (new) (4106mV 33C)
09:00:12 homebrew: ping sent
09:00:12 homebrew: pong received
09:00:12 dmrcalltracker[0]: prv voice call started, dst: 3138590 src: 9990 id: 962c5668723ce6d8
09:00:12 c4fm4dmrcon: new call, cid 962c5668723ce6d8
09:00:13 c4fm4dmrcon: call start, using src callsign Parrot - P for this call
09:00:15 dmrcalltracker[0]: call ended, dur 3.1s ber 0.1% loss 0.0% rssi 0
09:00:16 c4fm4dmrcon: call end, timeout: 0
09:00:17 modem-djq: emptied, closing
09:00:18 homebrew: ping sent
09:00:18 homebrew: pong received
User avatar
AI7HL
Posts: 30
Joined: Tue May 18, 2021 6:16 pm

Re: High BER and invalid fich error

Post by AI7HL »

As suggested, I tried upping the power. I also reloaded the firmware manually.

Turns out these errors also happen when cross mode between C4FM and D-Star.

The two main errors are:

c4fmcalltracker: missing callsigns for late entry

and

c4fmcalltracker: invalid fich
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 »

Please read this thread. viewtopic.php?t=3534
For example if I set my radio TX mode to voice wide (VW) I got "invalid fitch" messages also. Openspot modem mode was set to C4FM. If I set to my radio TX mode back to DN mode everythink working fine.

06:05:01 c4fmcalltracker: got header
06:05:01 c4fmcalltracker: got header
06:05:01 c4fmpacket: header
06:05:01 dst: *****F0Oq8 src: HA5OGR
06:05:01 dl: ul:
06:05:01 c4fmcalltracker: voice call started, dst: *****F0Oq8 dgid: 0 src: HA5OGR id: f630d8e81af2ea2c
06:05:01 nvmm-csd: ignoring special callsign *****F0Oq8
06:05:01 c4fm4dmrcon: new call, cid f630d8e81af2ea2c
06:05:01 homebrew: ping sent
06:05:01 homebrew: pong received
06:05:02 c4fm4dmrcon: call start, using ids dst 9990 src 2167002 for this prv call
06:05:03 nvmm: net check
06:05:03 nvmm: net check ok (16 ms)
06:05:07 c4fmcalltracker: invalid fich
06:05:07 batt: stat: done/500mA, 100% (new) (4068mV 35C)
06:05:07 homebrew: ping sent
06:05:07 homebrew: pong received
06:05:13 homebrew: ping sent
06:05:13 homebrew: pong received
06:05:17 batt: stat: done/500mA, 100% (new) (4074mV 35C)
06:05:19 homebrew: ping sent
06:05:19 homebrew: pong received
06:05:25 homebrew: ping sent
06:05:25 homebrew: pong received
06:05:27 batt: stat: done/500mA, 100% (new) (4072mV 35C)
06:05:30 c4fmcalltracker: invalid fich
06:05:31 c4fmcalltracker: got terminator
06:05:31 c4fmpacket: header
06:05:31 dst: *****F0Oq8 src: HA5OGR
06:05:31 c4fmcalltracker: call ended, dur 29.9s ber 1.9% loss 0.0% rssi -59
06:05:31 c4fmcall: tx confirm
06:05:31 homebrew: ping sent
06:05:31 homebrew: pong received
06:05:32 c4fm4dmrcon: call end, timeout: 0
06:05:32 modem-djq: emptied, closing
06:05:37 batt: stat: done/500mA, 100% (new) (4084mV 35C)
06:05:38 homebrew: ping sent
06:05:38 homebrew: pong received

Please double check your radio settings again. You wrote before this "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." Your TX mode changes is wrong. This changes the bandwidth of the analog transmission not the digital!
Attachments
FT-3DR VW mode.jpg
FT-3DR settings.jpg
Last edited by HA5OGR on Mon Nov 29, 2021 6:11 am, edited 1 time in total.
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: Mon Nov 29, 2021 5:30 am Please read this thread. viewtopic.php?t=3534
For example if I set my radio TX mode to voice wide (VW) I got "invalid fitch" messages also. Openspot modem mode was set to C4FM. If I set to my radio TX mode back to DN mode everythink working fine.
I think you are correct. I think the problem was that I had the radio set to auto detect the mode. Because I was scanning both digital frequencies and analog. At any rate, I changed a bunch of things including setting the mode to DN instead of auto. And I moved another device further away from the open spot that might’ve been causing some interference. And the errors seem to have stopped.

Thank you very much for your help .
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: Mon Nov 29, 2021 5:30 am Please double check your radio settings again. You wrote before this "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." Your TX mode changes is wrong. This changes the bandwidth of the analog transmission not the digital!
I only changed the FM bandwidth to get autocal to work. It didn’t work with it set to wide. It did work when it was set to narrow. As I mentioned, I did set it back when I was done.

The reason I never messed with that setting before is because I didn’t think it was for digital. It was just weird that it made the difference between autocal working and not working.
Post Reply