Updates

The 20140602 beta release of the ircDDB Gateway

Hi Folks

It's been a long time since the last beta release, so following feedback at Dayton and other things, here is a new beta with some new goodies included.

The changes are:

1. Add StarNet logging for remote control events.

2. Ensure that duplicate link requests don't initiate a status message. I don't know when this changed, but it's annoying. Re-issuing the same link command won't now generate a status message.

3. Stop taking DExtra addresses from xreflector.net. There is no definitive source of DExtra addresses so from now on, it's down to the local host files. For DCS xreflector.net is still definitive as opendstar.org is for D-Plus.

4. Added the "       W" and "       M" commands to send weather and messages respectively. This was a Dayton request. Issuing these commands, makes the gateway read the files named weather.dvtool and message.dvtool in the gateway users home directory respectively if they exist. They are read new every time so can be used for news. Along with a DV3000, generating your own dvtool files has never been easier, or cheaper!

I am beginning to suspect that some of the stability issues that people are seeing with the gateway are associated with running a STARnet Digital server within the gateway. I am minded to remove the STARnet Digital server from the gateway itself, and leaving the standalone version as it is.

Jonathan  G4KLX

The 20140305 beta release of the ircDDB Gateway

First of all sorry about the file notifications. This is a new feature on the upload page and I keep forgetting to untick it.

There are major internal changes in this release, and so please treat it with caution. I am in the process of reworking the ircDDB support and I think I have it back to where it was before I started, the next stage will be simplifying it and making it more efficient. The changes in this beta are:

1. Add IP address logging to the header logging. This is a legal requirement in some countries, and so the Headers.log file format has changed a little.

2. Added TextTransmit to Windows. It doesn't appear on the Start Menu under Windows as it is a command line only program, but it is installed.

3. Write the ircDDB Gateway and STARnet Server configuration files out under Windows. This matches the D-Star Repeater and is in the same format as used under Linux.

4. Rework the CIRCDDB library. As mentioned above.

5. CIRCDDB changes to have better compatibility with QuadNet. There are subtle differences between QuadNet and the official ircDDB system, causing the standard ircDDB library not to report correctly. This is not good. I fixed it in the library, but it shouldn't have happened at all. If you clone an existing system, please make sure that it is an exact clone please.

6. Add STARnet Digital group control to the command-line remote control program. Untested.....

So as I said be careful with this one.

Jonathan  G4KLX

The 20140203 beta release of the ircDDBGateway

Hi Folks

Not much in this one. Three main changes:

1. Timeout on network data is down to one second from two seconds. This is the timeout between the last packet being heard, and the gateway declaring that the remote end has gone away. This is only used when the end packet goes missing.

2. A new program named texttransmit which allows the sysop to transmit a text message out of one of the repeater ports. It must be run on the same machine as the gateway, and has the command syntax:

texttransmit <callsign> -text <text>

or

texttransmit <callsign> -file <filename>

The callsign is the callsign of the repeater port e.g. "GB7KLX B" (you can use underscores instead of spaces here) and the rest is straightforward. The text will typically be enclosed in quotes so that spaces can be included, and remember there is a twenty character limit. When reading from a file, only the first line of the file is read, and the twenty character limit also applies.

This program only exists under Linux, not Windows.

3. I have refreshed the D-Extra hosts file from VK4TUXs web site, but I only include the reflectors.

Jonathan  G4KLX

The 20140129 release of the D-Star repeater

Hi Folks

As mentioned in earlier e-mail I have create a package of all of the D-Star repeaters except for the new D-Star and Dummy repeaters, and re-added the DVAP Node and DV-RPTR Repeater. This is now in the Release directory of this Yahoo! group,

It probably represents the last release of these programs as work is now concentrating on making the new D-Star Repeater work as well, if not better, then these existing programs. However any major bugs will be fixed in these older programs.

The Dummy Repeater will appear in its own package fairly soon.

For reference, the programs are at a similar level to those in the 20131231 beta release, with the addition of the French and Australian callsign rejection code mentioned earlier this month.

Jonathan  G4KLX

The 20140117 beta release of the D-Star repeater

Hi Folks

A nice juicy beta version this morning. The changes are:

1. Block Australian foundation class and French novice callsigns from using the repeaters. This is hard coded in all of the repeater versions, callsigns of the form VKnFxxx and F0xxx aren't able to access any of the repeater types via RF as per their licence conditions. Sysops can sleep soundly at night. If the D-Star repeaters near the borders of France also use this version then the French novice callsigns won't be able to bypass their licence conditions by operating across borders.

2. Removed the optional delay on the DV-RPTR V1 modem. This was for a stillborn project of mine, it was separate from TX Delay which remains, this should affect no one :-)

3. Removed the DVAP Node and DV-RPTR Repeater. Their functionality is included in the newer D-Star Repeater so it's time to retire them. Existing installations using them will continue to work. All future hardware types will only be supported by the D-Star Repeater unless they are sufficiently different, for example DD mode.

4. Added the DVMEGA hardware. Speaking of new hardware, Guus PE1PLM is working on some new hardware which sounds very exciting, I am happy to include explicit support for it within my software. This is the first version so it is possible that more changes will be made, but feedback has been good so far.

So that's it for now.

Jonathan  G4KLX