As all of you know who having been using the KA4RES D-Star repeater, we make use of a couple of Reflectors to link multiple repeaters for functions such as the SouthEastern D-Star Weather Net, the Florida State Hurricane Net and other more casual functions which require multi-repeater linking. This method of using Reflectors to link MULTIPLE repeaters is simple, yet effective.

We have always envisioned linking our 4 repeaters together for area-wide, simultaneous coverage from south of Daytona to north of Jacksonville, but weren’t quite sure how we would accomplish this task. Original plans called for the use of the Multi-Cast feature of D-Star, but we have since reconsidered. Use of Reflectors is a simpler and more fool-proof method.

But use of existing Reflectors might be problematic. We have had generous offers from the Georgia D-Star group to use the Reflector 030B port to link our repeaters, including in times of emergency. But we have reconsidered for the following reason – when a hurricane or storm comes thru Florida, it will require our repeater resources and the linking provided by the Reflector. But when the storm turns north to Georgia, our neighbors in Georgia will require THEIR resources (and their Reflector) to Respond to the calamity – while we are still in Response or Recovery mode. This severely limits our ability to continue to provide service to EOC’s and the state if Reflector resources are redirected for use in Georgia.

Therefore, I have elected to create our own D-Star Reflector (Reflector number to be assigned by Robin, AA4RC). As of Thursday 03-June, I have placed an order for a remote, dedicated server which will provide us three (3) Reflector ports. This will allow us to have a Resource Net (like the FL Hurricane Net) and two (2) Tactical Nets simultaneously. Any of our repeaters, as well as any others in the State (or country) will be able to connect to the reflector, at-will. Also, DV-Dongle and DVAP users will always be able to link into the Reflector to monitor any-and-all traffic.

The server has a 100Mbps bi-directional link to the Internet (yes, you read that right… ONE HUNDRED Megabit per second), with usage capped at 10,000 Gigabytes per month, so in times of non-emergency, we can leave all 4 repeaters connected to the reflector unless independent linking is required by any user. The server is located in a high-availability data-center environment, with multiple telecom carriers, N+1 air conditioning and N+2 power, including over 10 Diesel generators on-site. This is also the site where Reflector 030 is housed. In reality, our configuration is actually a bit larger than REF030 – since I anticipate that we will have more traffic at times, due to the probability of severe weather, wildfires and the like. Our friend Robin Cutshaw (AA4RC), the “guru” of D-Star and the inventor of the DV-Dongle, DVAP and the dPlus Linking system for D-Star has been advising us during the week regarding the hosting service – and he will be installing the Reflector software as soon as the technicians at NetDepot turn the system over to us later in the week.

I will tell you that this facility is quite expensive – our 1-time cost was in excess of $1,000 and the recurring expense is just over $150/month – but we feel that having our own Reflector is CRITICAL to our being able to control our own assets in times of crisis, as well as enabling day-to-day functions like linking our 4 repeaters on a full-time basis. But with all that, let us be clear – we are NOT soliciting contributions (we HATE handling other people’s money.. you know what I’m talking about) – but if you’d like to help, we would MUCH RATHER invite you to contribute your time, efforts and experience to maintaining the repeater hardware and system. ALL are invited to participate – there is no lack of things (Projects AND Tasks) that need to be done.

UPDATE: The server has been provisioned by NetDepot, our data center services provider. We have turned-over the credentials for the server to Robin and he will be starting the install of the Reflector software on Friday, 04-June.

Stay tuned – we will publish more information as the Reflector enters testing and as we open it for general use. I expect that it will be within the next 24-48 hours.