Sunday, September 25, 2016

Status 25 Sep

Next big event still expected to be the delivery of the hotspot.



ID Estimate Status Description
917 2016-08-10 FIXED Order NW Digital board
981 2016-09-11 WONTFIX KC8ARJ as repeater
983 2016-09-11 FIXED Order quality SD cards
986 2016-09-11 FIXED Validate LTE
982 2016-09-12 FIXED WiFi startup
994 2016-09-12 WONTFIX Investigate hang time control
978 2016-09-13 FIXED Select UDRC/Pi Case
984 2016-09-15 FIXED SD card receive
995 2016-09-15 WONTFIX Investigate hang time in source
979 2016-09-16 FIXED Receive UDRC/Pi Case
987 2016-09-19 FIXED Select LTE provider
980 2016-09-20 FIXED Modify/Install UDRC/Pi Case
988 2016-09-20 FIXED Order LTE Device
991 2016-09-27 ON_QA Log file strategy
989 2016-09-30 ASSIGNED Receive LTE device
990 2016-10-03 ASSIGNED Configure/Test LTE Device
985 2016-10-12 ASSIGNED Schedule 2030 install
992 2016-10-18 ASSIGNED Make backup SD
993 2016-10-19 ASSIGNED Move to 2030
996 2016-11-30 ASSIGNED Test 100 watt amp





ID Estimate Status Description
991 2016-09-27 ON_QA Log file strategy

2016-09-11 09:46:43:  
Develop a strategy to be sure that log files don't get excessive


2016-09-20 15:26:20:  
Looks like we can simply delete all the gzipped log files after
the backup has run.  Probably should decide about backing up the
system logs as well as the openDV logs,


2016-09-25 11:40:11:  
Backup logs to cimbaoth

#!/bin/sh -x
FILENAME=`date +'%Y%m%d-opendv.tar.gz'`
FILENAME2=`date +'%Y%m%d-log.tar.gz'`
NODE="71.10.153.139"
#
*****************************************************************
# REMOVE THIS LINE WHEN ON ANOTHER NETWORK
#
*****************************************************************
NODE="cimbaoth"
TARGET="/backup03/backup/kc8arj/"
tar -czf ${FILENAME} /etc/opendv/*
tar -czf ${FILENAME2} /var/log/opendv/*
scp ${FILENAME} backup@${NODE}:${TARGET}
scp ${FILENAME2} backup@${NODE}:${TARGET}
rm -f ${FILENAME} ${FILENAME2}

Clear out old logs on Mondays

#!/bin/sh

rm /var/log/opendv/*log.?.gz

And finally the crontab:

MAILTO=root@localhost.localdomain
# Edit this file to introduce tasks to be run by cron.
# 
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
# 
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').# 
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
# 
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless
redirected).
# 
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
# 
# For more information see the manual pages of crontab(5) and
cron(8)
# 
# m h  dom mon dow   command
#
# Backup logs each night 3 minutes before midnight zulu
#
57 23 * * *               /root/backitup
#
# Clear out gzipped logs each Monday right after backup
#
59 23 * * 1   /root/cleanLogs



ID Estimate Status Description
989 2016-09-30 Receive LTE device

2016-09-12 10:29:54:  
Wait for delivery of LTE hotspot/service.


2016-09-20 14:35:08:  
Date adjusted to promised delivery



ID Estimate Status Description
990 2016-10-03 Configure/Test LTE Device

2016-09-12 10:30:32:  
Configure the Pi to use the hotspot network, adjust the backup
scheme for the external address, test repeater using LTE hotspot.



ID Estimate Status Description
985 2016-10-12 Schedule 2030 install

2016-09-12 10:30:56:  
Schedule a time to move the repeater to 2030



ID Estimate Status Description
992 2016-10-18 Make backup SD

2016-09-11 09:49:16:  
Need to create a backup SD card immediately before taking
repeater to site


2016-09-12 10:32:15:  
Create a backup of the SD card.  Moved date to the day before
install since this wants to be the LAST thing we do.



ID Estimate Status Description
993 2016-10-19 Move to 2030

2016-09-12 10:54:35:  
Install the repeater at the permanent site at 2030 building.



ID Estimate Status Description
996 2016-11-30 Test 100 watt amp

2016-09-12 10:49:37:  
Repeater will initially be set for 20 watts. It is unknown at
this time whether the addition of an external amplifier will
result in excess desense. After the repeater is at the site, an
amp will be tested for coverage.





Tuesday, September 20, 2016

Status 20 Sep

ID Estimate Status Description
917 2016-08-10 FIXED Order NW Digital board
981 2016-09-11 WONTFIX KC8ARJ as repeater
983 2016-09-11 FIXED Order quality SD cards
986 2016-09-11 FIXED Validate LTE
982 2016-09-12 FIXED WiFi startup
994 2016-09-12 WONTFIX Investigate hang time control
978 2016-09-13 FIXED Select UDRC/Pi Case
984 2016-09-15 FIXED SD card receive
995 2016-09-15 WONTFIX Investigate hang time in source
979 2016-09-16 FIXED Receive UDRC/Pi Case
987 2016-09-19 FIXED Select LTE provider
988 2016-09-20 FIXED Order LTE Device
991 2016-09-28 ASSIGNED Log file strategy
989 2016-09-30 ASSIGNED Receive LTE device
990 2016-10-03 ASSIGNED Configure/Test LTE Device
985 2016-10-12 ASSIGNED Schedule 2030 install
980 2016-10-12 ASSIGNED Modify/Install UDRC/Pi Case
992 2016-10-18 ASSIGNED Make backup SD
993 2016-10-19 ASSIGNED Move to 2030
996 2016-11-30 ASSIGNED Test 100 watt amp





ID Estimate Status Description
991 2016-09-28 Log file strategy

2016-09-11 09:46:43:  
Develop a strategy to be sure that log files don't get excessive



ID Estimate Status Description
989 2016-09-30 Receive LTE device

2016-09-12 10:29:54:  
Wait for delivery of LTE hotspot/service.


2016-09-20 14:35:08:  
Date adjusted to promised delivery



ID Estimate Status Description
990 2016-10-03 Configure/Test LTE Device

2016-09-12 10:30:32:  
Configure the Pi to use the hotspot network, adjust the backup
scheme for the external address, test repeater using LTE hotspot.



ID Estimate Status Description
985 2016-10-12 Schedule 2030 install

2016-09-12 10:30:56:  
Schedule a time to move the repeater to 2030



ID Estimate Status Description
980 2016-10-12 Modify/Install UDRC/Pi Case

2016-09-11 09:27:25:  
Indication is that case will need some modification


2016-09-16 14:29:46:  
Case with one spacer fits Pi + UDRC, *but*
- Supplied screws not long enough with spacer
- Light pipes in the wrong place (Pi 2?)


2016-09-16 16:13:25:  
Looks like it works without spacer.

Light pipe goes to Bluetooth antenna instead of LEDs.  Will want
to drill some holes so we can see the LEDs.


2016-09-20 14:46:02:  
Will stick with the MCM case.  Works just fine.



ID Estimate Status Description
992 2016-10-18 Make backup SD

2016-09-11 09:49:16:  
Need to create a backup SD card immediately before taking
repeater to site


2016-09-12 10:32:15:  
Create a backup of the SD card.  Moved date to the day before
install since this wants to be the LAST thing we do.



ID Estimate Status Description
993 2016-10-19 Move to 2030

2016-09-12 10:54:35:  
Install the repeater at the permanent site at 2030 building.



ID Estimate Status Description
996 2016-11-30 Test 100 watt amp

2016-09-12 10:49:37:  
Repeater will initially be set for 20 watts. It is unknown at
this time whether the addition of an external amplifier will
result in excess desense. After the repeater is at the site, an
amp will be tested for coverage.




Friday, September 16, 2016

UDRC in MCM Case

I thought the MCM case was going to require the addition of one, or maybe two, spacers.  When the case arrived, I nibbled out a space for the DB-15 that connects to the DR1-X, and also for the DIN connector which sticks out too far to leave covered up.

The top of the connectors still stuck above the top of the case, so I nibbled out a bit of a spacer (I had ordered two) to clear the connectors.  All went together pretty well, except, the screws that hold the case together weren't long enough with the spacer in place.  These were quite long, skinny self-tapping screws and I doubt whether I could get them locally.  So I stuck it together with tape for the time being, and it seemed decent.

Then it occurred to me that the cutout in the spacer was quite small, perhaps I could make it work without the spacer.  Turns out the spacer sticks down into the case farther than the lid, so the modifications to the lid were even smaller.


Kind of a pity that the other stuff couldn't stay covered up; the only thing we need is the DB-15.

MCM has available optional covers for the ends of the case; one to cover the USB ports and RJ-45, with a knock out for the RJ-45

And on the other end, a little cover for the SD card.  There is even a light pipe, but instead of leading to the LEDs it goes to something that appears to be the Bluetooth antenna.  This is unfortunate because the LEDs are important.


Still, not really a bad little package.  I think it will work for now. Might need to drill a hole or two for the LEDs.

Status 16 Sep

So, some progress in the past few days

Estimates for completed tasks have been changed to reflect the time they were completed. Completed tasks have been dropped from the long report.

ID Estimate Status Description
917 2016-08-10 FIXED Order NW Digital board
981 2016-09-11 WONTFIX KC8ARJ as repeater
983 2016-09-11 FIXED Order quality SD cards
986 2016-09-11 FIXED Validate LTE
982 2016-09-12 FIXED WiFi startup
994 2016-09-12 WONTFIX Investigate hang time control
978 2016-09-13 FIXED Select UDRC/Pi Case
984 2016-09-15 FIXED SD card receive
995 2016-09-15 WONTFIX Investigate hang time in source
979 2016-09-16 FIXED Receive UDRC/Pi Case
987 2016-09-19 ASSIGNED Select LTE provider
988 2016-09-20 ASSIGNED Order LTE Device
989 2016-09-27 ASSIGNED Receive LTE device
991 2016-09-28 ASSIGNED Log file strategy
990 2016-10-03 ASSIGNED Configure/Test LTE Device
985 2016-10-12 ASSIGNED Schedule 2030 install
980 2016-10-12 ASSIGNED Modify/Install UDRC/Pi Case
992 2016-10-18 ASSIGNED Make backup SD
993 2016-10-19 ASSIGNED Move to 2030
996 2016-11-30 ASSIGNED Test 100 watt amp


Dependency tree Sep 16 1830Z


ID Estimate Status Description
987 2016-09-19 Select LTE provider

2016-09-12 10:29:17:  
There are a number of LTE providers that can provide quite low
cost for limited data quantity.  Estimate it would be hard to use
up 1Gb per month.


2016-09-16 12:22:11:  
Karma looks to be the winner.

They rely on Sprint's WiMax, not actual LTE but several sources
claim excellent coverage where we need it.  Their little hotspot
is $79 and they charge $14 per gig of data which doesn't expire. 
That means with our probable usage of under a quarter gig a
month, they are under four bucks a month.

Freedom Spot is another cheapie.  The hotspot is $100 but when
done you can send it back for a full refund providing you have
kept all the packaging.  Their monthly charge for a half-gig is
zero!  Also WiMax.  You can also pay $10 per month for a gig,
although totally free sounds appealing but suspicious.

Verizon's cheapest prepaid plan appears to be $35/2 months, not
clear what the hotspot actually costs. Looks like maybe a $50
hotspot, $18/month not so bad if we can cancel quickly. We know
Verizon coverage is good.



ID Estimate Status Description
988 2016-09-20 Order LTE Device

2016-09-12 10:29:37:  
Place order for LTE hotspot



ID Estimate Status Description
989 2016-09-27 Receive LTE device

2016-09-12 10:29:54:  
Wait for delivery of LTE hotspot/service.



ID Estimate Status Description
991 2016-09-28 Log file strategy

2016-09-11 09:46:43:  
Develop a strategy to be sure that log files don't get excessive



ID Estimate Status Description
990 2016-10-03 Configure/Test LTE Device

2016-09-12 10:30:32:  
Configure the Pi to use the hotspot network, adjust the backup
scheme for the external address, test repeater using LTE hotspot.



ID Estimate Status Description
985 2016-10-12 Schedule 2030 install

2016-09-12 10:30:56:  
Schedule a time to move the repeater to 2030



ID Estimate Status Description
980 2016-10-12 Modify/Install UDRC/Pi Case

2016-09-11 09:27:25:  
Indication is that case will need some modification


2016-09-16 14:29:46:  
Case with one spacer fits Pi + UDRC, *but*
- Supplied screws not long enough with spacer
- Light pipes in the wrong place (Pi 2?)



ID Estimate Status Description
992 2016-10-18 Make backup SD

2016-09-11 09:49:16:  
Need to create a backup SD card immediately before taking
repeater to site


2016-09-12 10:32:15:  
Create a backup of the SD card.  Moved date to the day before
install since this wants to be the LAST thing we do.



ID Estimate Status Description
993 2016-10-19 Move to 2030

2016-09-12 10:54:35:  
Install the repeater at the permanent site at 2030 building.



ID Estimate Status Description
996 2016-11-30 Test 100 watt amp

2016-09-12 10:49:37:  
Repeater will initially be set for 20 watts. It is unknown at
this time whether the addition of an external amplifier will
result in excess desense. After the repeater is at the site, an
amp will be tested for coverage.



MCM case with UDRC installed

Tuesday, September 13, 2016

Status 13 Sep 16

ID Estimate Status Description
917 2016-08-12 FIXED Order NW Digital board
994 2016-09-10 WONTFIX Investigate hang time control
986 2016-09-12 FIXED Validate LTE
982 2016-09-15 FIXED WiFi startup
981 2016-09-16 WONTFIX KC8ARJ as repeater
978 2016-09-16 FIXED Select UDRC/Pi Case
983 2016-09-19 FIXED Order quality SD cards
987 2016-09-19 ASSIGNED Select LTE provider
988 2016-09-20 ASSIGNED Order LTE Device
989 2016-09-27 ASSIGNED Receive LTE device
991 2016-09-28 ASSIGNED Log file strategy
995 2016-09-28 ASSIGNED Investigate hang time in source
984 2016-09-29 ASSIGNED SD card receive
979 2016-09-30 ASSIGNED Receive UDRC/Pi Case
990 2016-10-03 ASSIGNED Configure/Test LTE Device
985 2016-10-12 ASSIGNED Schedule 2030 install
980 2016-10-12 ASSIGNED Modify/Install UDRC/Pi Case
992 2016-10-18 ASSIGNED Make backup SD
993 2016-10-19 ASSIGNED Move to 2030
996 2016-11-30 ASSIGNED Test 100 watt amp




ID Estimate Status Description
917 2016-08-12 FIXED Order NW Digital board

2016-08-08 14:19:41:  
Product page info below screen cap visible portion


Open Source Applications  Supported by Others:

    dstarrepeater (and optionally ircddbgateway)
    DIREWOLF 1200/9600 AX25

The UDRC is a Raspberry Pi HAT containing all of the necessary
hardware to directly interface to a radio or repeater.

The UDRC is compliant with the Raspberry Pi HAT Specification
and has the ID EEPROM which directly loads the device table for
the UDRC on boot up. The Ideal Diode circuit allows the Pi to be
powered by either the Micro USB jack or external 12VDC.

Direct Connection to the Yaesu DR1-X Repeater is available with
the HD-15 Cable and adds D-STAR Capability to your Fusion
Repeater. This cable must have all 15 pins wired straight
through.

Alternatively the Mini DIN-6 Cable can be used to connect to the
Data Port on a standard HF/VHF/UHF Radio. This cable must have
all 6 pins wired straight through.


2016-08-08 14:21:15:  
From: PayPal 
To: John McDonough 
Subject: Your receipt for payment to NW Digital Radio
Date: Mon, 08 Aug 2016 11:13:45 -0700 (08/08/2016 02:13:45 PM)

 
  
 
You paid $96.05 USD to
NW Digital Radio

  
  
 
Thanks for using PayPal, John McDonough


2016-08-10 18:45:15:  
Got an "Order Complete" email, whatever that means



ID Estimate Status Description
994 2016-09-10 WONTFIX Investigate hang time control

2016-09-11 11:16:21:  
Not much found in config panel.


2016-09-12 08:17:08:  
No real opportunities in configuration panel.  Need to
investigate source.



ID Estimate Status Description
986 2016-09-12 FIXED Validate LTE

2016-09-11 09:39:11:  
Tether repeater off phone to validate LTE utility


2016-09-11 20:06:02:  
No link tethering from phone. Able to ssh in through phone when
also tethered and connection looks good

root@KC8ARJ:~# ifconfig
eth0      Link encap:Ethernet  HWaddr b8:27:eb:49:40:f2  
          inet6 addr: fe80::523:94ec:2a31:756e/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:2529 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2529 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:164814 (160.9 KiB)  TX bytes:164814 (160.9
KiB)

wlan0     Link encap:Ethernet  HWaddr b8:27:eb:1c:15:a7  
          inet addr:192.168.43.162  Bcast:192.168.43.255 
Mask:255.255.255.0
          inet6 addr: fe80::625a:8382:b7d2:1582/64 Scope:Link
          inet6 addr: 2600:1007:b02b:bbfb:e670:e28b:6efd:6417/64
Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2152 errors:0 dropped:134 overruns:0 frame:0
          TX packets:1931 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1538428 (1.4 MiB)  TX bytes:241161 (235.5 KiB)

Linking looking a little shaky:

M: 2016-09-11 23:50:21: Linking KC8ARJ B at startup to REF024 C
M: 2016-09-11 23:50:29: D-Plus ACK message received from REF024 C
M: 2016-09-11 23:50:29: D-Plus link to REF024 C established
M: 2016-09-11 23:51:21: D-Plus link to REF024 C has failed (poll
inactivity)
M: 2016-09-11 23:51:21: D-Plus link to REF024 C has failed,
relinking
M: 2016-09-12 00:00:45: Link command from KC8ARJ B to REF030 C
issued via UR Call by WB8RCR  
M: 2016-09-12 00:00:45: D-Plus ACK message received from REF030 C
M: 2016-09-12 00:00:45: D-Plus link to REF030 C established

It looks like it may just take some time for the LTE link to
settle down

M: 2016-09-12 00:04:39: Link command from KC8ARJ B to REF024 C
issued via UR Call by WB8RCR  
M: 2016-09-12 00:04:39: D-Plus ACK message received from REF024 C
M: 2016-09-12 00:04:39: D-Plus link to REF024 C established


2016-09-11 20:26:46:  
Not all is sweetness and light:

M: 2016-09-12 00:09:50: Link command from KC8ARJ B to REF001 C
issued via UR Call by WB8RCR  
M: 2016-09-12 00:10:20: D-Plus link to REF001 C has failed to
connect
M: 2016-09-12 00:10:51: D-Plus link to REF001 C has failed to
connect
M: 2016-09-12 00:11:21: D-Plus link to REF001 C has failed to
connect
M: 2016-09-12 00:11:52: D-Plus link to REF001 C has failed to
connect
M: 2016-09-12 00:12:22: D-Plus link to REF001 C has failed to
connect
M: 2016-09-12 00:12:53: D-Plus link to REF001 C has failed to
connect
M: 2016-09-12 00:13:23: D-Plus link to REF001 C has failed to
connect
M: 2016-09-12 00:13:54: D-Plus link to REF001 C has failed to
connect
M: 2016-09-12 00:14:24: D-Plus link to REF001 C has failed to
connect

But then, maybe it is just REF001

M: 2016-09-12 00:15:20: Link command from KC8ARJ B to REF030 C
issued via UR Call by WB8RCR  
M: 2016-09-12 00:15:20: D-Plus ACK message received from REF030 C
M: 2016-09-12 00:15:20: D-Plus link to REF030 C established


2016-09-11 20:39:49:  
Well, that worked pretty nice.  Shut off the WiFi hotspot and
immediately reconnected via the house WiFi (which was set as a
lower priority)

M: 2016-09-12 00:38:17: D-Plus link to REF030 C has failed (poll
inactivity)
M: 2016-09-12 00:38:17: D-Plus link to REF030 C has failed,
relinking
M: 2016-09-12 00:38:17: D-Plus ACK message received from REF030 C
M: 2016-09-12 00:38:17: D-Plus link to REF030 C established



ID Estimate Status Description
982 2016-09-15 FIXED WiFi startup

2016-09-11 09:31:24:  
Clean up WiFi startup at boot


2016-09-12 08:18:52:  
Starting automatically from interfaces allows selection of
network based on priority.  Good solution.



ID Estimate Status Description
981 2016-09-16 WONTFIX KC8ARJ as repeater

2016-09-11 09:29:55:  
KC8ARJ shows as a hotspot on dashboards, rather than as a
repeater.  Why is that?


2016-09-11 11:04:22:  
Posted a message in the UDRC board


2016-09-11 11:40:08:  
Normal behavior.



ID Estimate Status Description
978 2016-09-16 FIXED Select UDRC/Pi Case

2016-09-11 09:24:23:  
Decide on a case


2016-09-12 14:28:59:  
John Jays likes this one

http://smile.amazon.com/gp/aw/d/B016954T3I/ref=mp_s_a_1_1?qid=1465094927&sr=8-1&pi=SX200_QL40&keywords=hifiberry+case

$14.97 - apparently takes a little work.


2016-09-12 14:33:07:  
Mike Morneau suggests

http://www.mcmelectronics.com/product/83-16355
$4.97

with the possible addition of spacers

http://www.mcmelectronics.com/product/83-16386
$2.29

He indicates holes for the VGA and DIN connectors would need to
be routed out.

I suspect the same with the case Hays suggests


2016-09-12 14:38:37:  
Looks like the MCM case might also want a shroud for the USB
connectors and possibly the SD port.  Probably nice for an
unattended installation.  Also looks as though there might be a
light pipe.


2016-09-12 21:56:01:  
From:     auto-confirm@amazon.com 
Reply-to: auto-confirm@amazon.com
To:       wb8rcr@arrl.net
Subject:  Your Amazon.com order of Raspberry Pi 3 Model B... and
1 more item.
Date:     Tue, 13 Sep 2016 00:00:19 +0000 (09/12/2016 08:00:19
PM)


Amazon.com Order Confirmation
www.amazon.com/ref=TE_simp_tex_h
_______________________________________________________________________________________

Hello JOHN MCDONOUGH,

Thank you for shopping with us. You ordered  "Raspberry Pi 3
Model B..."  and 1 other item. 
Well send a confirmation when your items ship.


View or manage your orders in Your Orders:
https://www.amazon.com/gp/css/order-details?orderId=103-4845455-0913016&eoid=1%3A1%3AsZtOklBjvHvISHNY7uyHv0Mme2nX6cvsS8FpAUCYaalGx8nUzHHVkQujQqEfvPVBAM74KCYZwzU1IcPLDGWHeNgcjx4%2BUJ8XoJi8fEhashiLglhPhjoRXdI7MUy%2F5NbfKkAyfdkFvUprgqHqrT4886USfVWc%2FVzxTpx7Dj5L30%2FosWtruGQbGW0GWJ%2BOdjkdPv5mzIwLmy4dp853Xo6Cmo%2B2U2kH%2B27a1ON%2B6wt%2BV7QvUCt6%2F3DKJdhcYCHQVCYzKDex7W0DZIX7DiHGgL4N5XEUxGzivgUvoJZ%2BnaaTQKDgNAqlcLsVeHEhW8lH%2BtWWrUQiPZMb2aqKDTF1%2BK2mrw%3D%3D&ref_=TE_simp_od

Details
Order #103-4845455-0913016

    Arriving:
    Monday, September 19

    Ship to:
    John J. McDonough
    2211 LAUREL LN...
        
    
    Total Before Tax: $58.88                     
    Estimated Tax: $0.00

    Order Total: $58.88

=======================================================================================


We hope to see you again soon.

Amazon.com
www.amazon.com/ref=TE_simp_tex_ty
_______________________________________________________________________________________

The payment for your invoice is processed by Amazon Payments,
Inc. P.O. Box 81226 Seattle, Washington 98108-1226. If you need
more information, please contact (866) 216-1075.
 
Unless otherwise noted, items sold by Amazon.com LLC  are subject
to sales tax in select states in accordance with the applicable
laws of that state. If your order contains one or more items from
a seller other than Amazon.com LLC , it may be subject to state
and local sales tax, depending upon the seller's business
policies and the location of their operations. Learn more about
tax and seller information at:
http://www.amazon.com/gp/help/customer/display.html/ref=TE_simp_tex_tx?ie=UTF8&nodeId=201133270

This email was sent from a notification-only address that cannot
accept incoming email. Please do not reply to this message.


2016-09-12 21:56:58:  
From:    talk@mcmelectronics.com
To:      wb8rcr@arrl.net
Subject: MCM Electronics Confirmation - Order #W001578800
Date:    12 Sep 2016 21:02:53 -0400



Thank you for placing your order with MCM Electronics.
Your order has been submitted and will be processed shortly. 

Order Information
Order Number:  W001578800 on 9/12/2016 9:01:20 PM
Email Address: wb8rcr@arrl.net
Payment Type: Credit Card
Product Total: $12.65
Shipping: $7.99 - 00 Super Saver Shipping
Tax: $0.00
Order Total: $20.64


Order Line Items
1 
83-16355 - Blue Raspberry Pi Enclosure for B+ and Pi 2 Model B
$4.59
$4.59
2 
83-16386 - Blue Spacer for 83-16355 for B+ and Pi 2 Model B
$2.29
$4.58
1 
83-16391 - Blue USB Port Cover for 83-16355 for B+ and Pi 2 Model
B
$1.99
$1.99
1 
83-16396 - Blue SD Port Cover for 83-16355 for B+ and Pi 2 Model
B
$1.49
$1.49

Common Questions
How do I print an invoice or track my order status?
Visit mcmelectronics.com and login to your account at the top of
any page. Don't have an online account with MCM? Visit our
website and click "Track Your Order" at the top of any page.

When will my order ship?
In stock orders typically ship the next business day after being
entered.

How can I return an item?
Visit mcmelectronics.com/content/en-US/help/returns for more
information regarding returns.
Please note, this transactional email message was sent from a
notification-only address that cannot accept incoming email.
Please do not reply to this message.
Shipping charges are subject to change. Any ground order over 50
pounds or any air shipment over 25 pounds will be charged carrier
chart rate.
           
********************************Disclaimer***********************************
The preceding e-mail message (including any attachments) contains
information that may be confidential, be protected by the
attorney-client
or other applicable privileges, or constitute non-public
information. It
is intended to be conveyed only to the designated recipient(s).
If you are
not an intended recipient of this message, please notify the
sender by
replying to this message and then delete it from your system.
Use,
dissemination, distribution, or reproduction of this message by
unintended
recipients is not authorized and may be unlawful.
*****************************************************************************


2016-09-13 08:01:46:  
2 cases ordered, one should work



ID Estimate Status Description
983 2016-09-19 FIXED Order quality SD cards

2016-09-11 09:33:37:  
Need a Class 10, 8G SD card, preferably SanDisk or Kingston


2016-09-11 11:13:08:  
One of these looks like a possibility:

http://www.newegg.com/Product/Product.aspx?Item=9SIA12K1RK3174&cm_re=sdhc_class_10-_-9SIA12K1RK3174-_-Product

http://www.newegg.com/Product/Product.aspx?Item=9SIA12K4830573&cm_re=sdhc_class_10-_-0DF-0005-00JN6-_-Product

Both 18 day delivery, one ships from Taiwan, the other from the
U.S.  The U.S. one is a little more expensive and a little
slower, although we don't care about speed nearly as much as
life.


2016-09-11 11:14:00:  
Also

http://www.newegg.com/Product/Product.aspx?Item=9SIA12K4830573&cm_re=sdhc_class_10-_-0DF-0005-00JN6-_-Product

Also 18 days from Hong Kong.



ID Estimate Status Description
987 2016-09-19 Select LTE provider

2016-09-12 10:29:17:  
There are a number of LTE providers that can provide quite low
cost for limited data quantity.  Estimate it would be hard to use
up 1Gb per month.



ID Estimate Status Description
988 2016-09-20 Order LTE Device

2016-09-12 10:29:37:  
Place order for LTE hotspot



ID Estimate Status Description
989 2016-09-27 Receive LTE device

2016-09-12 10:29:54:  
Wait for delivery of LTE hotspot/service.



ID Estimate Status Description
991 2016-09-28 Log file strategy

2016-09-11 09:46:43:  
Develop a strategy to be sure that log files don't get excessive



ID Estimate Status Description
995 2016-09-28 Investigate hang time in source

2016-09-11 11:17:29:  
See if the source has any ability to control PTT when in analog.


2016-09-12 17:16:04:  
git clone https://github.com/mcdermj/OpenDV.git


2016-09-12 17:25:03:  
It looks as though the hang time is set in the code, 1000 must
not be 1000 seconds, milliseconds would be reasonable, but I
don't see 1000ms happening, so....

DStarRepeaterTXRXThread.cpp:m_activeHangTimer(1000U),


2016-09-12 17:42:19:  
There is a configuration line

activeHangTime=4

and a fair bit of code around it.  The configuration panel has a
slider for that which indicates the value is in seconds. 
However, the code defaults it to 1000 (unsigned) so milliseconds
would make more sense.

Setting activeHangTime to 1000 causes the repeater to refuse to
transmit.



ID Estimate Status Description
984 2016-09-29 SD card receive

2016-09-11 09:35:02:  
SD card received


2016-09-11 13:23:20:  
Readjust date to max expected shipping on 983


2016-09-12 17:45:31:  
One of the cards has apparently shipped. (Ordered two different
types). Looks like it shipped from Kalifornia.  At this point,
only shipping label created, carrier has apparently not picked up

Customer ID: wb8rcr@arrl.net Account Number: 10554662
Dear John J McDonough,
Thank you for shopping at Newegg Marketplace.

Your tracking number has been generated. Please see below for
your order information and tracking number. 

Shipping Summary:
Sales Order Number: 214262769
Seller: 3C Expert
Carrier: USPS

Item List:
Item Number: Item Description: Quantity:
9SIA12K4830573 SanDisk Ultra 8GB Micro SD SDHC SDXC Class 10
Memory Card 48MB/s 2

Tracking Number:
9400110200828143918593 
 
Shipped from 1F, No 239, SongRen Rd
Shipping Time:9/12/2016 10:28:02 AM 
 

Once You Know, You Newegg.

Your Newegg Marketplace Customer Service Team



ID Estimate Status Description
979 2016-09-30 Receive UDRC/Pi Case

2016-09-11 09:25:39:  
Wait for delivery


2016-09-12 21:57:49:  
Amazon claims Sep 19 delivery



ID Estimate Status Description
990 2016-10-03 Configure/Test LTE Device

2016-09-12 10:30:32:  
Configure the Pi to use the hotspot network, adjust the backup
scheme for the external address, test repeater using LTE hotspot.



ID Estimate Status Description
985 2016-10-12 Schedule 2030 install

2016-09-12 10:30:56:  
Schedule a time to move the repeater to 2030



ID Estimate Status Description
980 2016-10-12 Modify/Install UDRC/Pi Case

2016-09-11 09:27:25:  
Indication is that case will need some modification



ID Estimate Status Description
992 2016-10-18 Make backup SD

2016-09-11 09:49:16:  
Need to create a backup SD card immediately before taking
repeater to site


2016-09-12 10:32:15:  
Create a backup of the SD card.  Moved date to the day before
install since this wants to be the LAST thing we do.



ID Estimate Status Description
993 2016-10-19 Move to 2030

2016-09-12 10:54:35:  
Install the repeater at the permanent site at 2030 building.



ID Estimate Status Description
996 2016-11-30 Test 100 watt amp

2016-09-12 10:49:37:  
Repeater will initially be set for 20 watts. It is unknown at
this time whether the addition of an external amplifier will
result in excess desense. After the repeater is at the site, an
amp will be tested for coverage.

Monday, September 12, 2016

Detailed To Do

Summary to-do list

ID Estimate Status Description
917 2016-08-12 FIXED Order NW Digital board
994 2016-09-10 WONTFIX Investigate hang time control
986 2016-09-12 FIXED Validate LTE
982 2016-09-15 FIXED WiFi startup
981 2016-09-16 WONTFIX KC8ARJ as repeater
978 2016-09-16 ASSIGNED Select UDRC/Pi Case
983 2016-09-19 FIXED Order quality SD cards
987 2016-09-19 ASSIGNED Select LTE provider
988 2016-09-20 ASSIGNED Order LTE Device
989 2016-09-27 ASSIGNED Receive LTE device
991 2016-09-28 ASSIGNED Log file strategy
995 2016-09-28 ASSIGNED Investigate hang time in source
984 2016-09-29 ASSIGNED SD card receive
979 2016-09-30 ASSIGNED Receive UDRC/Pi Case
990 2016-10-03 ASSIGNED Configure/Test LTE Device
985 2016-10-12 ASSIGNED Schedule 2030 install
980 2016-10-12 ASSIGNED Modify/Install UDRC/Pi Case
992 2016-10-18 ASSIGNED Make backup SD
993 2016-10-19 ASSIGNED Move to 2030
996 2016-11-30 ASSIGNED Test 100 watt amp

The following are the full descriptions of the various to-do items, including those completed, in order of estimated completion, as of September 12:


ID Estimate Status Description
917 2016-08-12 FIXED Order NW Digital board

2016-08-08 14:19:41:  
Product page info below screen cap visible portion


Open Source Applications  Supported by Others:

    dstarrepeater (and optionally ircddbgateway)
    DIREWOLF 1200/9600 AX25

The UDRC is a Raspberry Pi HAT containing all of the necessary
hardware to directly interface to a radio or repeater.

The UDRC is compliant with the Raspberry Pi HAT Specification
and has the ID EEPROM which directly loads the device table for
the UDRC on boot up. The Ideal Diode circuit allows the Pi to be
powered by either the Micro USB jack or external 12VDC.

Direct Connection to the Yaesu DR1-X Repeater is available with
the HD-15 Cable and adds D-STAR Capability to your Fusion
Repeater. This cable must have all 15 pins wired straight
through.

Alternatively the Mini DIN-6 Cable can be used to connect to the
Data Port on a standard HF/VHF/UHF Radio. This cable must have
all 6 pins wired straight through.


2016-08-08 14:21:15:  
From: PayPal 
To: John McDonough 
Subject: Your receipt for payment to NW Digital Radio
Date: Mon, 08 Aug 2016 11:13:45 -0700 (08/08/2016 02:13:45 PM)

 
  
 
You paid $96.05 USD to
NW Digital Radio

  
  
 
Thanks for using PayPal, John McDonough


2016-08-10 18:45:15:  
Got an "Order Complete" email, whatever that means



ID Estimate Status Description
994 2016-09-10 WONTFIX Investigate hang time control

2016-09-11 11:16:21:  
Not much found in config panel.


2016-09-12 08:17:08:  
No real opportunities in configuration panel.  Need to
investigate source.



ID Estimate Status Description
986 2016-09-12 FIXED Validate LTE

2016-09-11 09:39:11:  
Tether repeater off phone to validate LTE utility


2016-09-11 20:06:02:  
No link tethering from phone. Able to ssh in through phone when
also tethered and connection looks good

root@KC8ARJ:~# ifconfig
eth0      Link encap:Ethernet  HWaddr b8:27:eb:49:40:f2  
          inet6 addr: fe80::523:94ec:2a31:756e/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:2529 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2529 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:164814 (160.9 KiB)  TX bytes:164814 (160.9
KiB)

wlan0     Link encap:Ethernet  HWaddr b8:27:eb:1c:15:a7  
          inet addr:192.168.43.162  Bcast:192.168.43.255 
Mask:255.255.255.0
          inet6 addr: fe80::625a:8382:b7d2:1582/64 Scope:Link
          inet6 addr: 2600:1007:b02b:bbfb:e670:e28b:6efd:6417/64
Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2152 errors:0 dropped:134 overruns:0 frame:0
          TX packets:1931 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1538428 (1.4 MiB)  TX bytes:241161 (235.5 KiB)

Linking looking a little shaky:

M: 2016-09-11 23:50:21: Linking KC8ARJ B at startup to REF024 C
M: 2016-09-11 23:50:29: D-Plus ACK message received from REF024 C
M: 2016-09-11 23:50:29: D-Plus link to REF024 C established
M: 2016-09-11 23:51:21: D-Plus link to REF024 C has failed (poll
inactivity)
M: 2016-09-11 23:51:21: D-Plus link to REF024 C has failed,
relinking
M: 2016-09-12 00:00:45: Link command from KC8ARJ B to REF030 C
issued via UR Call by WB8RCR  
M: 2016-09-12 00:00:45: D-Plus ACK message received from REF030 C
M: 2016-09-12 00:00:45: D-Plus link to REF030 C established

It looks like it may just take some time for the LTE link to
settle down

M: 2016-09-12 00:04:39: Link command from KC8ARJ B to REF024 C
issued via UR Call by WB8RCR  
M: 2016-09-12 00:04:39: D-Plus ACK message received from REF024 C
M: 2016-09-12 00:04:39: D-Plus link to REF024 C established


2016-09-11 20:26:46:  
Not all is sweetness and light:

M: 2016-09-12 00:09:50: Link command from KC8ARJ B to REF001 C
issued via UR Call by WB8RCR  
M: 2016-09-12 00:10:20: D-Plus link to REF001 C has failed to
connect
M: 2016-09-12 00:10:51: D-Plus link to REF001 C has failed to
connect
M: 2016-09-12 00:11:21: D-Plus link to REF001 C has failed to
connect
M: 2016-09-12 00:11:52: D-Plus link to REF001 C has failed to
connect
M: 2016-09-12 00:12:22: D-Plus link to REF001 C has failed to
connect
M: 2016-09-12 00:12:53: D-Plus link to REF001 C has failed to
connect
M: 2016-09-12 00:13:23: D-Plus link to REF001 C has failed to
connect
M: 2016-09-12 00:13:54: D-Plus link to REF001 C has failed to
connect
M: 2016-09-12 00:14:24: D-Plus link to REF001 C has failed to
connect

But then, maybe it is just REF001

M: 2016-09-12 00:15:20: Link command from KC8ARJ B to REF030 C
issued via UR Call by WB8RCR  
M: 2016-09-12 00:15:20: D-Plus ACK message received from REF030 C
M: 2016-09-12 00:15:20: D-Plus link to REF030 C established


2016-09-11 20:39:49:  
Well, that worked pretty nice.  Shut off the WiFi hotspot and
immediately reconnected via the house WiFi (which was set as a
lower priority)

M: 2016-09-12 00:38:17: D-Plus link to REF030 C has failed (poll
inactivity)
M: 2016-09-12 00:38:17: D-Plus link to REF030 C has failed,
relinking
M: 2016-09-12 00:38:17: D-Plus ACK message received from REF030 C
M: 2016-09-12 00:38:17: D-Plus link to REF030 C established



ID Estimate Status Description
982 2016-09-15 FIXED WiFi startup

2016-09-11 09:31:24:  
Clean up WiFi startup at boot


2016-09-12 08:18:52:  
Starting automatically from interfaces allows selection of
network based on priority.  Good solution.



ID Estimate Status Description
981 2016-09-16 WONTFIX KC8ARJ as repeater

2016-09-11 09:29:55:  
KC8ARJ shows as a hotspot on dashboards, rather than as a
repeater.  Why is that?


2016-09-11 11:04:22:  
Posted a message in the UDRC board


2016-09-11 11:40:08:  
Normal behavior.



ID Estimate Status Description
978 2016-09-16 Select UDRC/Pi Case

2016-09-11 09:24:23:  
Decide on a case



ID Estimate Status Description
983 2016-09-19 FIXED Order quality SD cards

2016-09-11 09:33:37:  
Need a Class 10, 8G SD card, preferably SanDisk or Kingston


2016-09-11 11:13:08:  
One of these looks like a possibility:

http://www.newegg.com/Product/Product.aspx?Item=9SIA12K1RK3174&cm_re=sdhc_class_10-_-9SIA12K1RK3174-_-Product

http://www.newegg.com/Product/Product.aspx?Item=9SIA12K4830573&cm_re=sdhc_class_10-_-0DF-0005-00JN6-_-Product

Both 18 day delivery, one ships from Taiwan, the other from the
U.S.  The U.S. one is a little more expensive and a little
slower, although we don't care about speed nearly as much as
life.


2016-09-11 11:14:00:  
Also

http://www.newegg.com/Product/Product.aspx?Item=9SIA12K4830573&cm_re=sdhc_class_10-_-0DF-0005-00JN6-_-Product

Also 18 days from Hong Kong.



ID Estimate Status Description
987 2016-09-19 Select LTE provider

2016-09-12 10:29:17:  
There are a number of LTE providers that can provide quite low
cost for limited data quantity.  Estimate it would be hard to use
up 1Gb per month.



ID Estimate Status Description
988 2016-09-20 Order LTE Device

2016-09-12 10:29:37:  
Place order for LTE hotspot



ID Estimate Status Description
989 2016-09-27 Receive LTE device

2016-09-12 10:29:54:  
Wait for delivery of LTE hotspot/service.



ID Estimate Status Description
991 2016-09-28 Log file strategy

2016-09-11 09:46:43:  
Develop a strategy to be sure that log files don't get excessive



ID Estimate Status Description
995 2016-09-28 Investigate hang time in source

2016-09-11 11:17:29:  
See if the source has any ability to control PTT when in analog.



ID Estimate Status Description
984 2016-09-29 SD card receive

2016-09-11 09:35:02:  
SD card received


2016-09-11 13:23:20:  
Readjust date to max expected shipping on 983



ID Estimate Status Description
979 2016-09-30 Receive UDRC/Pi Case

2016-09-11 09:25:39:  
Wait for delivery



ID Estimate Status Description
990 2016-10-03 Configure/Test LTE Device

2016-09-12 10:30:32:  
Configure the Pi to use the hotspot network, adjust the backup
scheme for the external address, test repeater using LTE hotspot.



ID Estimate Status Description
985 2016-10-12 Schedule 2030 install

2016-09-12 10:30:56:  
Schedule a time to move the repeater to 2030



ID Estimate Status Description
980 2016-10-12 Modify/Install UDRC/Pi Case

2016-09-11 09:27:25:  
Indication is that case will need some modification



ID Estimate Status Description
992 2016-10-18 Make backup SD

2016-09-11 09:49:16:  
Need to create a backup SD card immediately before taking
repeater to site


2016-09-12 10:32:15:  
Create a backup of the SD card.  Moved date to the day before
install since this wants to be the LAST thing we do.



ID Estimate Status Description
993 2016-10-19 Move to 2030

2016-09-12 10:54:35:  
Install the repeater at the permanent site at 2030 building.



ID Estimate Status Description
996 2016-11-30 Test 100 watt amp

2016-09-12 10:49:37:  
Repeater will initially be set for 20 watts. It is unknown at
this time whether the addition of an external amplifier will
result in excess desense. After the repeater is at the site, an
amp will be tested for coverage.

Sunday, September 11, 2016

LTE Testing

I kind of expect that it may take a little while to get proper Internet up to the site, so I thought I might get an LTE hot spot for the interim. D-STAR repeaters don't require a lot of data, so that kind of service can be fairly inexpensive.  By my calculations, we would have to work hard to use even 1GB per month.

So a couple of tests.  First thing was to configure the Pi to us WiFi instead of my wired Internet.  That turned out to not be terribly difficult.  I had previously tried unsuccessfully to get the Pi 3 internal Wifi working without success.  Apparently I hadn't tried hard enough.  Turned out a little man page exploration and it took off.

But then I ran across a note on setting it up on the UDRC message board.  Their way was a lot nicer than mine, so I tried it out and it worked fine.

One slick thing is that the configuration file lets you specify different priorities for different WiFi networks.  So I added my cell phone's hotspot in at a higher priority.  I then rebooted the Pi to force it to disconnect, and was able to validate that it had connected to the phone's network.  That was actually a bit tricky because without another network, figuring out the Pi's IP address was a bit of a trail of bread crumbs.  The phone seems to give out random IPs, unlike my router which assigns them sequentially making it easy to guess.



It seemed a little unhappy a first, but after a while it started to work fine.  I worried about it at first, but then I realized that all the various gateways need to get comfortable with the new external IP.  After a few minutes, everything worked fine.

I had a nice QSO with a station in West Virginia, throughout the repeater continued to report 0% bit error rate, audio was perfect, so as expected, it looks like the LTE is plenty good.

I got curious how resilient it would be changing networks, so I turned off the cell phone hotspot and almost immediately it reconnected to the home WiFi and picked up where it left off.

So it looks like an LTE connection will be quite reasonable.  A lot of people use DVAPs and DV-Megas tethered from their cell phones, but I wanted to prove to myself that it was going to work with this hardware.


D-PRS

Many D-STAR radios include a GPS.  When an operator chooses, his location can be transmitted as part of his data.  Some radios will pop up a screen that shows you the location relative to where you are, as well as the call.


Reflectors include a Last Heard list.  When a station is heard who has included his GPS the call shows up in orange.  Clicking on the call will link to a map, just like APRS.


ToDo List 11 Sep 2016

I keep my todo list in bugzilla. It allows me to keep various documentation associated with each item, to keep estimates of how much time I need to spend, and to track relationships between items.  The image below is the current list of items associated with the repeater.  This will change frequently, and I'll post new copies here somewhat less frequently.


Gray means an item is complete. As before, click on the image to see it in a size you can actually read.

As of 2016-09-11:

ID Estimate Status Description
917 2016-08-12 FIXED Order NW Digital board
994 2016-09-10 WONTFIX Investigate hang time control
986 2016-09-12 FIXED Validate LTE
982 2016-09-15 FIXED WiFi startup
981 2016-09-16 FIXED KC8ARJ as repeater
978 2016-09-16 Select UDRC/Pi Case
983 2016-09-19 FIXED Order quality SD cards
987 2016-09-19 Select LTE provider
988 2016-09-20 Order LTE Device
989 2016-09-27 Receive LTE device
991 2016-09-28 Log file strategy
995 2016-09-28 Investigate hang time in source
984 2016-09-29 SD card receive
979 2016-09-30 Receive UDRC/Pi Case
990 2016-10-03 Configure/Test LTE Device
992 2016-10-06 Make backup SD
985 2016-10-12 Schedule 2030 install
980 2016-10-12 Modify/Install UDRC/Pi Case
993 2016-10-19 Move to 2030

Repeater "Modules"

D-STAR repeaters can have a number of so-called modules.  Each module is indicated by a letter after the call.  Typically, the letter tells you about the module.  The convention is:

A - 23 cm
B - 70 cm
C - 2 meter
D - 23 cm high-speed data
G - Gateway

These letters actually could be anything, but in practice the only place you see an exception is where a repeater might have multiple modules on one band.

Any useful repeater will have at least a band module and a gateway.  KC8ARJ has a B and a G module.  A surprising number of Michigan repeaters have four, and two have all five.

The letter is the seventh character of the call.  A lot of radios and software have a separate field for the module.  If you are linking to a repeater with a short call, you might have to add spaces.  For example, to link to the 2 meter module of the Battle Creek machine:

    W8DF  CL

That's 2 spaces between the call and the module, forcing the module into position 7 and the command into position 8.

Reflectors also have modules, but in the case of reflectors, the letter has no meaning other than to separate different conversations on the same host. If you look at the three REF024 entries you can see all have the same dashboard and uplink speed (click on the image to enlarge):


And all the modules are combined on the same dashboard:







D-STAR Reflectors and links

The D-STAR network has a whole bunch of reflectors.  These reflectors add a lot of capability, and really are what makes D-STAR fun.  The repeater is configured to connect to REF024C after an hour of inactivity.  REF024C is an open reflector used mainly in Michigan.  It is a relatively quiet reflector, although a call will often scare up a QSO.  The REF024 reflectors are hosted at the Owosso repeater, W8SHI.

Two other interesting reflectors are REF001C, the so-called MegaRepeater, and REF030C, a reflector that links a lot of U.S. repeaters.  Both of these are quite busy.  REF001C is so busy that, if you want to rag chew, it is recommended you move off to REF004C.

A complete list of REF reflectors can be found here.

Each of the reflectors has a dashboard that tells you who is linked to the reflector.  The dashboard for REF0024 is here, and for REF001, here. There are also CCS, DCS, XRF and XLX reflectors, but the REF reflectors seem to be the most used.

There is a list of D-STAR repeaters here.

Some stations have turned on "visibility" for their radios, and in that case, you can see whenever they press the PTT here. There is also a link to tell you how to turn on visibility for your radio if you wish.


Current Configuration

The block diagram of the current configuration is shown here:


The repeater is currently running at 20 watts.  The UDRC connects to the repeater through its remote port, and mounts on the Raspberry Pi's 40-pin connector.

The Pi is running the 'Compass' image which was provided by NW Digital and uses the G4KLX dstarrepeaterd deamon and the ircddbgatewayd daemon to connect to the D-STAR network.

Once we move it to the official site it will have heliax to a better antenna and a whole lot more height.




Hello

There is a lot of stuff I should/might share about what is going on with the repeater.  Much of it will be overkill for lots of folks, but the terminally curious will always want to know more.

It is real easy to create one of these blogs, just about as easy as sending an email, and if I put it here, anyone who gets interested can find it easily.  So, I'll try to keep this up to date with our progress.

To begin with, some basics you already know.  The repeater is on 444.350+. It will answer analog with a 131.8PL, or digital with the correct codes.

For D-STAR:

Normal connection
URCALL: CQCQCQ
RPT1:   KC8ARJ B
RPT2:   KC8ARJ G

To ask the repeater what it may be linked to
URCALL:        I
That's an I preceded by seven spaces.  RPT1 and RPT2 same as before.

The eighth character of URCALL is a command, in addition to an I, you can use a U to unlink the repeater, and an E to cause it to echo back what you say.

An L is used to link, but it must be preceded by what you want to link to, so
URCALL:  REF001CL
to link to the "megarepeater", REF001C

To use any of these commands, program your radio for the command, wait for the repeater to be silent, and then key the mike for a little over a second.  For the E, talk for a few seconds.  In most cases the repeater will give an audio and a slow data response so watch the scrolling field at the bottom of your screen.