|
 xAP clocks have been surprisingly popular, people seem to like using them for testing. Here's yet another xAP clock, which outputs both GMT and local time in a variety of formats - perfect for presenting on a xAP Display. The display in the picture (left) is showing the "short" form of "pretty" time.
Enhanced versions of the clock, which derive their time from an authorative source are in the works - Ian Bird is working on a xAP enabled Rugby clock, and I intend to modify the existing xAP clock to provide optional support for GPS and teletext time sources.
Command Line Options
xap-clock [instance name] [network interface] [udp port] [debug level]
where:
instance name is the xAP instance name assigned to this clock instance. Typically this might identify the time source the clock connector is identified to. The default instance name is BigBen.
network interface is the network interface used for outgoing xAP messages. On a Linux and Windows PC host these are named eth0, eth1. Under OSX they are named ne0 etc. By default, eth0 is used. On a Windows PC which has multiple adapters installed, even if they are not active, eth0 may not represent the active interface - some experimentation may be required!
udp port is the UDP port xAP broadcasts on. By default xAP uses its officially allocated port, 3639. Using an alternative port can be useful during isolated testing, however. Be aware that the use of ports below 1024 will fail unless the application is run by a user with administrative privileges. The use of ports below 1024 therefore has security implications and is not recommend.
debug level determines the verbosity of the output written to stdout. Verbose output can be useful for debugging unexpected behaviour. By default, the debug level is 0. Increasing levels of detail may be specified, up to a maximum of 4.
Downloads
Clock source (requires xAP-lib)
Clock windows executable (requires cygwin dll)
Schema
Clock schema
|
