Hi, callsign is set to G1KEA and the DStar rpt1 call is set to G1KEA-D.
I have always stayed away from having gateway and hotspot on same reflector. In the past I have had one on DCS and the other on REF as defaults.
It's puzzling me. My regular hotspot has been switched of a couple of weeks whilst I got this JumboSpot configured and working on DMR and DStar for someone. When he has it I'll enter his call and change to -B in Dstar config.
Repeater REF connection - What am I doing wrong?
Re: Repeater REF connection - What am I doing wrong?
So tonight I finished setting up and testing the JumboSpot. It's working reliably on DMR for it's new owner and now has his callsign in and ready to go to a new home.
I powered my hotspot back on which is a Pi2 with DVMega shield running Pi-Star 3.4.17, DMR and DStar enabled and has Rpt1 call set to G1KEA D as was the JumboSpot. Strangely I am now connecting to REF001C however I still cannot connect on the gateway radio as G1KEA C. Never used to have a problem, I cannot see how it can be a callsign issue as why has G1KEA D started working but G1KEA C not? Any ideas anyone?
I powered my hotspot back on which is a Pi2 with DVMega shield running Pi-Star 3.4.17, DMR and DStar enabled and has Rpt1 call set to G1KEA D as was the JumboSpot. Strangely I am now connecting to REF001C however I still cannot connect on the gateway radio as G1KEA C. Never used to have a problem, I cannot see how it can be a callsign issue as why has G1KEA D started working but G1KEA C not? Any ideas anyone?
Re: Repeater REF connection - What am I doing wrong?
If your installation is set up with a C module the setting in the radios rpt1 field must match that. ie LLNLLL C
If it's set up as a D module rpt1 must read LLNLLL D
eg. my M1DNS B install won't be heard if I'm using the radio channel setup for my M1DNS C install. rpt1 must match what's setup in the installation.
Andrew M1DNS, (Mod)
If it's set up as a D module rpt1 must read LLNLLL D
eg. my M1DNS B install won't be heard if I'm using the radio channel setup for my M1DNS C install. rpt1 must match what's setup in the installation.
Andrew M1DNS, (Mod)
Andrew M1DNS.
Pi-star Admin Team.
Pi-star Admin Team.
Re: Repeater REF connection - What am I doing wrong?
Hi Andrew
There has been no change to the Pi-Star settings or radio settings for the 2m gateway using the DVMega GMSK modem board, it will connect fine to DCS so there isn't a problem with the two not passing commands to each other. The Pi has remained powered up 24/7 and it was working fine up until probably the time the JumboSpot turned up. However I also changed the broadband router too about the same time that turned up.
When I was given a JumboSpot to configure I turned my UHF DVMega hotspot off to save me reprogramming the radio for when setting the JumboSpot up. The configuration of the JumboSpot was the same as the DVMega hotspot and it worked other than DStar connection to REF (DCS fine) so again the settings were OK. The JumboSpot will not be used on DStar by it's new owner so i've disabled that, entered his callsign and DMR id etc and powered down. I've powered the DVMega hotspot back on with no changes made to anything and it works fine happily connecting to DPlus reflectors so totally baffled by the JumboSpot not connecting. I made sure only one hotspot was switched on at a time as they were configured for the same frequency and callsign/module.
I have had the GMSK modem Pi powered down for 24 hours now and just rebooted. Connecting fine to DCS, just tried DPlus and received the "Linked to REF079B message, could see it on my dashboard as connected, checked REF079B dashboard and in the last heard list and then I was disconnected and heard the message "Linking to REF079B". I have a log if you want me to send it to you. I also have the log for the DVMega hotspot that will connect and stay connected.
Adrian
There has been no change to the Pi-Star settings or radio settings for the 2m gateway using the DVMega GMSK modem board, it will connect fine to DCS so there isn't a problem with the two not passing commands to each other. The Pi has remained powered up 24/7 and it was working fine up until probably the time the JumboSpot turned up. However I also changed the broadband router too about the same time that turned up.
When I was given a JumboSpot to configure I turned my UHF DVMega hotspot off to save me reprogramming the radio for when setting the JumboSpot up. The configuration of the JumboSpot was the same as the DVMega hotspot and it worked other than DStar connection to REF (DCS fine) so again the settings were OK. The JumboSpot will not be used on DStar by it's new owner so i've disabled that, entered his callsign and DMR id etc and powered down. I've powered the DVMega hotspot back on with no changes made to anything and it works fine happily connecting to DPlus reflectors so totally baffled by the JumboSpot not connecting. I made sure only one hotspot was switched on at a time as they were configured for the same frequency and callsign/module.
I have had the GMSK modem Pi powered down for 24 hours now and just rebooted. Connecting fine to DCS, just tried DPlus and received the "Linked to REF079B message, could see it on my dashboard as connected, checked REF079B dashboard and in the last heard list and then I was disconnected and heard the message "Linking to REF079B". I have a log if you want me to send it to you. I also have the log for the DVMega hotspot that will connect and stay connected.
Adrian
Re: Repeater REF connection - What am I doing wrong?
Seems strange in it will connect with DCS but not DPlus ?
You mention a new router...
Check ur router has port forward at udp 20000-20009 pistar doesn't really need it, but ??
Check with ur ISP they aren't blocking any ports or services on ur service.
Also an idea. Change ur callsign in the setup to ur friends call.
Check if you can connect to DPlus REF's. using his call. ??
If you can't that tells us it's Ur side of the link. If you can it shows Ur call is being rejected by the network.
Andrew M1DNS, (Mod)
You mention a new router...
Check ur router has port forward at udp 20000-20009 pistar doesn't really need it, but ??
Check with ur ISP they aren't blocking any ports or services on ur service.
Also an idea. Change ur callsign in the setup to ur friends call.
Check if you can connect to DPlus REF's. using his call. ??
If you can't that tells us it's Ur side of the link. If you can it shows Ur call is being rejected by the network.
Andrew M1DNS, (Mod)
Andrew M1DNS.
Pi-star Admin Team.
Pi-star Admin Team.
Re: Repeater REF connection - What am I doing wrong?
The gateway connects, announces "Connected", can be seen on the REF dashboard and then I hear and see in the log "Connecting to..." I thought it may be a ports issue and added them to the router again. They were in the old router as over the years I have used various images other than Pi-Star. I would have thought if it was a ports issue though it would affect the hotspot and the MB6 gateway as well (there is no port forwarding for them).
The station who is having the JumboSpot does not use DStar and is not registered for the DStar network. The only thing i can think of is shutting down the hotspot, putting the hotspot module to the gateway and changing the Rpt1Call in the radio. That would prove if it is anything to do with a the gateway callsign+module at the reflector end, when I get chance i'll try it. As I said I do have the logs for the hotspot (MMDVM) that connects and the gateway (DstarRepeater) that doesn't. I don't have any logs for the JumboSpot (MMDVM) that didn't connect as that's going on Tuesday.
The station who is having the JumboSpot does not use DStar and is not registered for the DStar network. The only thing i can think of is shutting down the hotspot, putting the hotspot module to the gateway and changing the Rpt1Call in the radio. That would prove if it is anything to do with a the gateway callsign+module at the reflector end, when I get chance i'll try it. As I said I do have the logs for the hotspot (MMDVM) that connects and the gateway (DstarRepeater) that doesn't. I don't have any logs for the JumboSpot (MMDVM) that didn't connect as that's going on Tuesday.
Re: Repeater REF connection - What am I doing wrong?
Hang on so now we are referencing 3 different installs?
Ur confusing the sh1ite outta me
In plain text what connects, callsign:
In plain text what doesn't connect, callsign:
Andrew M1DNS, (Mod)
Ur confusing the sh1ite outta me
In plain text what connects, callsign:
In plain text what doesn't connect, callsign:
Andrew M1DNS, (Mod)
Andrew M1DNS.
Pi-star Admin Team.
Pi-star Admin Team.
Re: Repeater REF connection - What am I doing wrong?
Hi Andrew
Yes as per my earlier post but I do have a fourth just to confuse you even more
What connects:
G1KEA module D - both to DCS & DPlus
MB6IKW module B - both to DCS & DPlus
What doesn't connect:
G1KEA module C - not to DPlus only DCS
I have never had a problem over the years I've had gateways / hotspots, never used the same module instance on two gateways at the same time.
Personal VHF Gateway: G1KEA-C, DVMega GMSK modem & Pi 2, Pi-Star 3.4.13 running DStarRepeater - DCS ok, REF not connecting. This gateway has worked fine in the past.
Public UHF Gateway: MB6IKW-B, Zum-Radio MMDVM modem & Pi 3, Pi-Star 4.0.0. RC3, running MMDVMHost DStar and DMR enabled - works fine DCS & DPlus
Hotspot: G1KEA-D, DVMega shield & Pi 2, Pi-Star 3.4.17, running MMDVMHost DStar and DMR enabled - works fine DCS & DPlus
The above hotspot was powered down to build and test the JumboSpot which did have a problem with DPlus.
Hotspot: G1KEA-D, JumboSpot & Pi Zero, Pi-Star 4.0.0. RC3, running MMDVMHost DStar and DMR enabled - DCS ok, REF not connecting
I cannot see it being a callsign / module issue on DPlus as G1KEA-D works on one hotspot but not the other rememering only one is switched on so no conflicts. The JumboSpot will be used in DMR mode only so that is going to new owner tomorrow so no more time to experiment with that.
I thought it wouldn't be a ports issue with the ISP as two out of three work fine. I even put 4.0.0 RC3 and configured from fresh on the Pi with the problem and I still have a problem. I even tried changing to module E but still the same issue. It's back to C now.
My next step is to try the personal gateway G1KEA module C through my mobile phone to see if it connects then. Busy at work this week so don't know when I'll get chance to try it. Sorry if it's confusing you but it's baffling me,
Re: Repeater REF connection - What am I doing wrong?
Strange, for sure.
Just looked at DSTAR registrations and Ur call registration looks fine as does the gateway call (however it does have a additional A terminal registered to it) ??
Post the log files you have collated here and maybe something in them will give a clue.
Andrew M1DNS, (Mod)
Just looked at DSTAR registrations and Ur call registration looks fine as does the gateway call (however it does have a additional A terminal registered to it) ??
Post the log files you have collated here and maybe something in them will give a clue.
Andrew M1DNS, (Mod)
Andrew M1DNS.
Pi-star Admin Team.
Pi-star Admin Team.
Re: Repeater REF connection - What am I doing wrong?
Hi Andrew,
File from the 2m gateway with the problem,
Adrian
I: 2019-04-29 21:57:35: Starting D-Star Repeater daemon - 20170705_Pi-Star
I: 2019-04-29 21:57:35: Using wxWidgets 2.8.12 on Linux 4.9.35-v7+ armv7l
I: 2019-04-29 21:57:35: Callsign set to "G1KEA C", gateway set to "G1KEA G", mode: 1, ack: 2, restriction: 1, RPT1 validation: 1, DTMF blanking: 1, Error reply: 1
I: 2019-04-29 21:57:35: Gateway set to 127.0.0.1:20010, local set to 127.0.0.1:20011, name set to " "
I: 2019-04-29 21:57:35: Timeout set to 180 secs, ack time set to 500 ms
M: 2019-04-29 21:57:35: File /root/en_GB.ambe not readable
M: 2019-04-29 21:57:35: Reading /usr/local/etc/en_GB.ambe
M: 2019-04-29 21:57:35: File /root/en_GB.indx not readable
M: 2019-04-29 21:57:35: Reading /usr/local/etc/en_GB.indx
I: 2019-04-29 21:57:35: Beacon set to 14 mins, text set to "G1KEA C", voice set to 1, language set to 0
I: 2019-04-29 21:57:35: Announcement enabled: 0, time: 8 mins, record RPT1: " ", record RPT2: " ", delete RPT1: " ", delete RPT2: " "
I: 2019-04-29 21:57:35: Modem type set to "DVMEGA"
I: 2019-04-29 21:57:35: DVMEGA, port: /dev/ttyACM0, variant: 0, RX invert: 1, TX invert: 1, TX delay: 150 ms, rx frequency: 144887500 Hz, tx frequency: 144887500 Hz, power: 100 %
I: 2019-04-29 21:57:35: DVMEGA Firmware version: 1.51a, hardware: DV-MEGA R1.51A
M: 2019-04-29 21:57:35: Found modem path of ../../devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4:1.0/tty
I: 2019-04-29 21:57:35: Controller set to , config: 1, PTT invert: 0, active hang time: 0 ms
M: 2019-04-29 21:57:35: Starting DVMEGA Controller thread
I: 2019-04-29 21:57:35: Output 1 = 0, output 2 = 0, output 3 = 0, output 4 = 0
I: 2019-04-29 21:57:35: Control: enabled: 0, RPT1: , RPT2: , shutdown: , startup: , status1: , status2: , status3: , status4: , status5: , command1: = , command2: = , command3: = , command4: = , command5: = , command6: = , output1: , output2: , output3: , output4:
I: 2019-04-29 21:57:35: Frame logging set to 0, in /root
M: 2019-04-29 21:57:35: Poll text set to "linux_dvmega-20170705_pi-star"
M: 2019-04-29 21:57:35: Starting the D-Star repeater thread
M: 2019-04-29 21:57:59: Slow data set to "Not linked "
M: 2019-04-29 21:58:01: Network header received - My: G1KEA /INFO Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 21:58:01: Transmitting to - My: G1KEA /INFO Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 21:58:03: Stats for G1KEA Frames: 2.5s, Loss: 0.0%, Packets: 0/123
M: 2019-04-29 22:00:10: Radio header decoded - My: G1KEA /ID51 Your: DCS005BL Rpt1: G1KEA C Rpt2: G1KEA G Flags: 40 00 00
M: 2019-04-29 22:00:10: Slow data set to "Linking to DCS005 B "
M: 2019-04-29 22:00:10: Slow data set to "Linked to DCS005 B "
M: 2019-04-29 22:00:11: AMBE for G1KEA Frames: 1.4s, Silence: 0.0%, BER: 0.0%
M: 2019-04-29 22:00:12: Transmitting to - My: G1KEA C/ Your: G1KEA Rpt1: G1KEA G Rpt2: G1KEA C Flags: 01 00 00
M: 2019-04-29 22:00:13: Network header received - My: G1KEA /INFO Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 22:00:13: Transmitting to - My: G1KEA /INFO Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 22:00:20: Stats for G1KEA Frames: 7.2s, Loss: 0.0%, Packets: 0/362
M: 2019-04-29 22:06:44: Radio header decoded - My: G1KEA /ID51 Your: U Rpt1: G1KEA C Rpt2: G1KEA G Flags: 40 00 00
M: 2019-04-29 22:06:44: Slow data set to "Not linked "
M: 2019-04-29 22:06:44: AMBE for G1KEA Frames: 0.6s, Silence: 0.0%, BER: 0.0%
M: 2019-04-29 22:06:44: Transmitting to - My: G1KEA C/ Your: G1KEA Rpt1: G1KEA G Rpt2: G1KEA C Flags: 01 00 00
M: 2019-04-29 22:06:46: Network header received - My: G1KEA /INFO Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 22:06:46: Transmitting to - My: G1KEA /INFO Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 22:06:48: Stats for G1KEA Frames: 2.5s, Loss: 0.0%, Packets: 0/123
M: 2019-04-29 22:14:13: Radio header decoded - My: G1KEA /ID51 Your: REF001CL Rpt1: G1KEA C Rpt2: G1KEA G Flags: 40 00 00
M: 2019-04-29 22:14:13: Slow data set to "Linking to REF001 C "
M: 2019-04-29 22:14:13: Slow data set to "Linked to REF001 C "
M: 2019-04-29 22:14:14: AMBE for G1KEA Frames: 1.2s, Silence: 0.0%, BER: 0.0%
M: 2019-04-29 22:14:14: Transmitting to - My: G1KEA C/ Your: G1KEA Rpt1: G1KEA G Rpt2: G1KEA C Flags: 01 00 00
M: 2019-04-29 22:14:16: Network header received - My: G1KEA /INFO Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 22:14:16: Transmitting to - My: G1KEA /INFO Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 22:14:23: Stats for G1KEA Frames: 7.0s, Loss: 0.0%, Packets: 0/351
M: 2019-04-29 22:14:27: Network header received - My: 2E0RFV / Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 22:14:27: Transmitting to - My: 2E0RFV / Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 22:14:27: Stats for 2E0RFV Frames: 0.1s, Loss: 0.0%, Packets: 0/3
M: 2019-04-29 22:14:57: Slow data set to "Linking to REF001 C "
M: 2019-04-29 22:14:59: Network header received - My: G1KEA /INFO Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 22:14:59: Transmitting to - My: G1KEA /INFO Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 22:15:07: Stats
File from the 2m gateway with the problem,
Adrian
I: 2019-04-29 21:57:35: Starting D-Star Repeater daemon - 20170705_Pi-Star
I: 2019-04-29 21:57:35: Using wxWidgets 2.8.12 on Linux 4.9.35-v7+ armv7l
I: 2019-04-29 21:57:35: Callsign set to "G1KEA C", gateway set to "G1KEA G", mode: 1, ack: 2, restriction: 1, RPT1 validation: 1, DTMF blanking: 1, Error reply: 1
I: 2019-04-29 21:57:35: Gateway set to 127.0.0.1:20010, local set to 127.0.0.1:20011, name set to " "
I: 2019-04-29 21:57:35: Timeout set to 180 secs, ack time set to 500 ms
M: 2019-04-29 21:57:35: File /root/en_GB.ambe not readable
M: 2019-04-29 21:57:35: Reading /usr/local/etc/en_GB.ambe
M: 2019-04-29 21:57:35: File /root/en_GB.indx not readable
M: 2019-04-29 21:57:35: Reading /usr/local/etc/en_GB.indx
I: 2019-04-29 21:57:35: Beacon set to 14 mins, text set to "G1KEA C", voice set to 1, language set to 0
I: 2019-04-29 21:57:35: Announcement enabled: 0, time: 8 mins, record RPT1: " ", record RPT2: " ", delete RPT1: " ", delete RPT2: " "
I: 2019-04-29 21:57:35: Modem type set to "DVMEGA"
I: 2019-04-29 21:57:35: DVMEGA, port: /dev/ttyACM0, variant: 0, RX invert: 1, TX invert: 1, TX delay: 150 ms, rx frequency: 144887500 Hz, tx frequency: 144887500 Hz, power: 100 %
I: 2019-04-29 21:57:35: DVMEGA Firmware version: 1.51a, hardware: DV-MEGA R1.51A
M: 2019-04-29 21:57:35: Found modem path of ../../devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4:1.0/tty
I: 2019-04-29 21:57:35: Controller set to , config: 1, PTT invert: 0, active hang time: 0 ms
M: 2019-04-29 21:57:35: Starting DVMEGA Controller thread
I: 2019-04-29 21:57:35: Output 1 = 0, output 2 = 0, output 3 = 0, output 4 = 0
I: 2019-04-29 21:57:35: Control: enabled: 0, RPT1: , RPT2: , shutdown: , startup: , status1: , status2: , status3: , status4: , status5: , command1: = , command2: = , command3: = , command4: = , command5: = , command6: = , output1: , output2: , output3: , output4:
I: 2019-04-29 21:57:35: Frame logging set to 0, in /root
M: 2019-04-29 21:57:35: Poll text set to "linux_dvmega-20170705_pi-star"
M: 2019-04-29 21:57:35: Starting the D-Star repeater thread
M: 2019-04-29 21:57:59: Slow data set to "Not linked "
M: 2019-04-29 21:58:01: Network header received - My: G1KEA /INFO Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 21:58:01: Transmitting to - My: G1KEA /INFO Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 21:58:03: Stats for G1KEA Frames: 2.5s, Loss: 0.0%, Packets: 0/123
M: 2019-04-29 22:00:10: Radio header decoded - My: G1KEA /ID51 Your: DCS005BL Rpt1: G1KEA C Rpt2: G1KEA G Flags: 40 00 00
M: 2019-04-29 22:00:10: Slow data set to "Linking to DCS005 B "
M: 2019-04-29 22:00:10: Slow data set to "Linked to DCS005 B "
M: 2019-04-29 22:00:11: AMBE for G1KEA Frames: 1.4s, Silence: 0.0%, BER: 0.0%
M: 2019-04-29 22:00:12: Transmitting to - My: G1KEA C/ Your: G1KEA Rpt1: G1KEA G Rpt2: G1KEA C Flags: 01 00 00
M: 2019-04-29 22:00:13: Network header received - My: G1KEA /INFO Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 22:00:13: Transmitting to - My: G1KEA /INFO Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 22:00:20: Stats for G1KEA Frames: 7.2s, Loss: 0.0%, Packets: 0/362
M: 2019-04-29 22:06:44: Radio header decoded - My: G1KEA /ID51 Your: U Rpt1: G1KEA C Rpt2: G1KEA G Flags: 40 00 00
M: 2019-04-29 22:06:44: Slow data set to "Not linked "
M: 2019-04-29 22:06:44: AMBE for G1KEA Frames: 0.6s, Silence: 0.0%, BER: 0.0%
M: 2019-04-29 22:06:44: Transmitting to - My: G1KEA C/ Your: G1KEA Rpt1: G1KEA G Rpt2: G1KEA C Flags: 01 00 00
M: 2019-04-29 22:06:46: Network header received - My: G1KEA /INFO Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 22:06:46: Transmitting to - My: G1KEA /INFO Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 22:06:48: Stats for G1KEA Frames: 2.5s, Loss: 0.0%, Packets: 0/123
M: 2019-04-29 22:14:13: Radio header decoded - My: G1KEA /ID51 Your: REF001CL Rpt1: G1KEA C Rpt2: G1KEA G Flags: 40 00 00
M: 2019-04-29 22:14:13: Slow data set to "Linking to REF001 C "
M: 2019-04-29 22:14:13: Slow data set to "Linked to REF001 C "
M: 2019-04-29 22:14:14: AMBE for G1KEA Frames: 1.2s, Silence: 0.0%, BER: 0.0%
M: 2019-04-29 22:14:14: Transmitting to - My: G1KEA C/ Your: G1KEA Rpt1: G1KEA G Rpt2: G1KEA C Flags: 01 00 00
M: 2019-04-29 22:14:16: Network header received - My: G1KEA /INFO Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 22:14:16: Transmitting to - My: G1KEA /INFO Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 22:14:23: Stats for G1KEA Frames: 7.0s, Loss: 0.0%, Packets: 0/351
M: 2019-04-29 22:14:27: Network header received - My: 2E0RFV / Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 22:14:27: Transmitting to - My: 2E0RFV / Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 22:14:27: Stats for 2E0RFV Frames: 0.1s, Loss: 0.0%, Packets: 0/3
M: 2019-04-29 22:14:57: Slow data set to "Linking to REF001 C "
M: 2019-04-29 22:14:59: Network header received - My: G1KEA /INFO Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 22:14:59: Transmitting to - My: G1KEA /INFO Your: CQCQCQ Rpt1: G1KEA G Rpt2: G1KEA C Flags: 00 00 00
M: 2019-04-29 22:15:07: Stats