DXLog.net.DXC - Revision history

Sm7iun: /* Setup */

2025-07-13T15:20:43Z

Setup

← Older revision		Revision as of 15:20, 13 July 2025
Line 51:		Line 51:
	configuration panel and ''Default LAN'' in the cluster client.		configuration panel and ''Default LAN'' in the cluster client.

	The broadcast UDP port setting must be set the same as that in DXLog, usually 9888.<br>		The broadcast UDP port setting must be set the same as that used by all DXLog instances, usually 9888.<br>
	The station ID can be any name that is not used by another DXLog instance on the same network.		The station ID can be any name that is not used by another DXLog instance on the same network.

Sm7iun: /* Setup */

2025-04-21T04:32:22Z

Setup

← Older revision		Revision as of 04:32, 21 April 2025
Line 14:		Line 14:

	==Setup==		==Setup==
	When the program is first started you must set up the callsign you will use to connect to the cluster servers.		When the program is first started you must set up the callsign you will<br>
	Click on settings and user data		use to connect to the cluster servers. Click on settings and user data

Sm7iun: /* Setup */

2025-04-21T04:32:03Z

Setup

← Older revision		Revision as of 04:32, 21 April 2025
Line 21:		Line 21:


	~~Fill in~~ your callsign and click OK.		Enter your station's callsign and click OK.

			'''Important:''' Make sure this is the callsign you use on air.

			Tip: You can use a suffix (sometimes referred to as SSID) to allow more than<br>
			one cluster connection per callsign, e.g. SM7IUN-2, SM7IUN-3, etc.

	Next you must set up the network so the cluster client knows where to broadcast cluster data.		Next you must set up the network so the cluster client knows where to broadcast cluster data.

Sm7iun: /* Setup */

2025-04-21T04:29:43Z

Setup

← Older revision		Revision as of 04:29, 21 April 2025
Line 83:		Line 83:
	If you experience bad spots, such as a skimmer with bad frequency accuracy or an overly active pirate,<br>		If you experience bad spots, such as a skimmer with bad frequency accuracy or an overly active pirate,<br>
	you can blacklist them by clicking the ''Blacklist'' option. Enter the calls separated by space or comma.<br>		you can blacklist them by clicking the ''Blacklist'' option. Enter the calls separated by space or comma.<br>
	Do not include suffixes like -6 or -# to the callsigns. The ~~cluster client will strip such automatically~~.<br>		Do not include suffixes (a.k.a. SSID) like -6 or -# to the callsigns. The blacklist ignores those.<br>
	You can use wildcards. Asterisk <tt>*</tt> matches any number of non-space characters, including none.<br>		You can use wildcards. Asterisk <tt>*</tt> matches any number of non-space characters, including none.<br>
	A question mark <tt>?</tt> matches any non-space character.		A question mark <tt>?</tt> matches any non-space character.

	~~Tip: You can also use regular expressions for callsigns and spotters but be aware any <tt>?</tt> will be<br>~~
	~~converted to <tt>\S</tt> and any <tt></tt> will be converted to <tt>\S</tt>.~~

Sm7iun: /* Setup */

2025-04-20T18:43:53Z

Setup

← Older revision		Revision as of 18:43, 20 April 2025
Line 84:		Line 84:
	you can blacklist them by clicking the ''Blacklist'' option. Enter the calls separated by space or comma.<br>		you can blacklist them by clicking the ''Blacklist'' option. Enter the calls separated by space or comma.<br>
	Do not include suffixes like -6 or -# to the callsigns. The cluster client will strip such automatically.<br>		Do not include suffixes like -6 or -# to the callsigns. The cluster client will strip such automatically.<br>
	You can use wildcards. Asterisk matches any number of non-space characters, including none. A question mark<br>		You can use wildcards. Asterisk <tt>*</tt> matches any number of non-space characters, including none.<br>
	matches any non-space character.		A question mark <tt>?</tt> matches any non-space character.

	Tip: You can also use regular expressions for callsigns and spotters but be aware any "?" will be ~~converted~~<br>		Tip: You can also use regular expressions for callsigns and spotters but be aware any <tt>?</tt> will be<br>
	to "\S" and any "" will be converted to "\S".		converted to <tt>\S</tt> and any <tt></tt> will be converted to <tt>\S</tt>.

Sm7iun: /* Setup */

2025-04-20T18:41:44Z

Setup

← Older revision		Revision as of 18:41, 20 April 2025
Line 83:		Line 83:
	If you experience bad spots, such as a skimmer with bad frequency accuracy or an overly active pirate,<br>		If you experience bad spots, such as a skimmer with bad frequency accuracy or an overly active pirate,<br>
	you can blacklist them by clicking the ''Blacklist'' option. Enter the calls separated by space or comma.<br>		you can blacklist them by clicking the ''Blacklist'' option. Enter the calls separated by space or comma.<br>
	Do not include suffixes like -6 or -# to the callsigns. The cluster client will strip such automatically.		Do not include suffixes like -6 or -# to the callsigns. The cluster client will strip such automatically.<br>
	You can use wildcards. Asterisk matches any number of non-space characters, including none. A question mark		You can use wildcards. Asterisk matches any number of non-space characters, including none. A question mark<br>
	matches any non-space character.		matches any non-space character.

Sm7iun: /* Setup */

2025-04-20T18:41:15Z

Setup

← Older revision		Revision as of 18:41, 20 April 2025
Line 84:		Line 84:
	you can blacklist them by clicking the ''Blacklist'' option. Enter the calls separated by space or comma.<br>		you can blacklist them by clicking the ''Blacklist'' option. Enter the calls separated by space or comma.<br>
	Do not include suffixes like -6 or -# to the callsigns. The cluster client will strip such automatically.		Do not include suffixes like -6 or -# to the callsigns. The cluster client will strip such automatically.
			You can use wildcards. Asterisk matches any number of non-space characters, including none. A question mark
			matches any non-space character.

			Tip: You can also use regular expressions for callsigns and spotters but be aware any "?" will be converted<br>
			to "\S" and any "" will be converted to "\S".

Sm7iun at 05:13, 4 July 2024

2024-07-04T05:13:41Z

Sm7iun: /* Setup */

2024-06-03T21:18:30Z

Setup

← Older revision		Revision as of 21:18, 3 June 2024
Line 75:		Line 75:
	When connected to multiple cluster nodes you may receive a lot of duplicate spots. Checking<br>		When connected to multiple cluster nodes you may receive a lot of duplicate spots. Checking<br>
	''Ignore duplicated spots'' will prevent a station from being spotted more than once every three<br>		''Ignore duplicated spots'' will prevent a station from being spotted more than once every three<br>
	minutes. This will reduce the processor load of ~~both~~ DXLog ~~and~~ DXLog.net.DXC. Spots of ~~the callsign~~<br>		minutes. This will reduce the processor load of DXLog but increase that of DXLog.net.DXC. Spots of<br>
	used to log in to the cluster node will never be suppressed.		the callsign used to log in to the cluster node will never be suppressed.

	Make sure at least one of the cluster connection tabs has ''Cluster cmd'' checked. This check box controls		Make sure at least one of the cluster connection tabs has ''Cluster cmd'' checked. This check box controls<br>
	which cluster nodes receives spots posted by networked DXLog instances.		which cluster nodes receives spots posted by networked DXLog instances.

Sm7iun: /* Link supervision */

2023-08-28T09:30:16Z

Link supervision

← Older revision		Revision as of 09:30, 28 August 2023
Line 140:		Line 140:
	accept empty commands and will issue a (harmless) error message.		accept empty commands and will issue a (harmless) error message.

	'''~~NB.~~''' The watchdog is not active for local connections with addresses such as <tt>127.0.0.1</tt>,<br>		'''Important:''' The watchdog is not active for local connections with addresses such as <tt>127.0.0.1</tt>,<br>
	<tt>192.168..</tt>, or <tt>10...*</tt>.		<tt>192.168..</tt>, or <tt>10...*</tt>.

← Older revision		Revision as of 05:13, 4 July 2024
Line 1:		Line 1:
	==Program==		==Program==
	DXLog.net~~.DXC~~ is a multi connection DX cluster client for DXLog. It can handle multiple WAN connections to<br>		DXLog.net (Cluster) is a multi connection DX cluster client for DXLog. It can handle multiple WAN connections to<br>
	DX cluster nodes as well as to local CW skimmers.		DX cluster nodes as well as to local CW skimmers.

Line 6:		Line 6:
	network connected DXLog instances on the LAN.		network connected DXLog instances on the LAN.

	~~DXC~~ has the ability to automatically track a CAT controlled radio connected to one instance of DXLog on <br>		The cluster client has the ability to automatically track a CAT controlled radio connected to one instance of DXLog on <br>
	the LAN, this allows auto QSY of the local skimmer, provided the radio connected to the CW skimmer supports this.		the LAN, this allows auto QSY of the local skimmer, provided the radio connected to the CW skimmer supports this.

	To start click on the DXlog.net~~.DXC~~ icon on the desktop ~~of from the~~ start menu		To start, double click the DXlog.net (Cluster) icon on the desktop or use Windows' start menu

	[[image:dxlnetdxc.png]]		[[image:dxlnetdxc.png]]
Line 23:		Line 23:
	Fill in your callsign and click OK.		Fill in your callsign and click OK.

	Next you must set up the network so ~~DXlog.net.DXC~~ knows where to broadcast cluster data.		Next you must set up the network so the cluster client knows where to broadcast cluster data.

	Click on settings and Network.		Click on settings and Network.
Line 31:		Line 31:


	At first use, ~~DXLog.net.DXC~~ automatically determines the correct IP address to broadcast spots to all computers on the local LAN.		At first use, the client automatically determines the correct IP address to broadcast spots to all computers on the local LAN.

	Clicking the ''LAN defaults'' button will reset the three fields to factory settings which is the default<br>		Clicking the ''LAN defaults'' button will reset the three fields to factory settings which is the default<br>
Line 44:		Line 44:
	If you are using multiple computers or a stand alone PC for cluster connectivity then they must be on the same<br>		If you are using multiple computers or a stand alone PC for cluster connectivity then they must be on the same<br>
	subnet and the correct IP must be used. This is easiest achieved by clicking the ''Default'' button in DXLog's network<br>		subnet and the correct IP must be used. This is easiest achieved by clicking the ''Default'' button in DXLog's network<br>
	configuration panel and ''Default LAN'' in ~~DXLog~~.~~net.DXC~~		configuration panel and ''Default LAN'' in the cluster client.

	The broadcast UDP port setting must be set the same as that in DXLog, usually 9888.<br>		The broadcast UDP port setting must be set the same as that in DXLog, usually 9888.<br>
Line 75:		Line 75:
	When connected to multiple cluster nodes you may receive a lot of duplicate spots. Checking<br>		When connected to multiple cluster nodes you may receive a lot of duplicate spots. Checking<br>
	''Ignore duplicated spots'' will prevent a station from being spotted more than once every three<br>		''Ignore duplicated spots'' will prevent a station from being spotted more than once every three<br>
	minutes. This will reduce the processor load of DXLog but increase that of ~~DXLog~~.~~net.DXC. Spots of~~<br>		minutes. This will reduce the processor load of DXLog but increase that of the cluster client.<br>
	the callsign used to log in to the cluster node will never be suppressed.		Spots of the callsign used to log in to the cluster node will never be suppressed.

	Make sure at least one of the cluster connection tabs has ''Cluster cmd'' checked. This check box controls<br>		Make sure at least one of the cluster connection tabs has ''Cluster cmd'' checked. This check box controls<br>
Line 83:		Line 83:
	If you experience bad spots, such as a skimmer with bad frequency accuracy or an overly active pirate,<br>		If you experience bad spots, such as a skimmer with bad frequency accuracy or an overly active pirate,<br>
	you can blacklist them by clicking the ''Blacklist'' option. Enter the calls separated by space or comma.<br>		you can blacklist them by clicking the ''Blacklist'' option. Enter the calls separated by space or comma.<br>
	Do not include suffixes like -6 or -# to the callsigns. ~~DXLog.net.DXC~~ will strip such automatically.		Do not include suffixes like -6 or -# to the callsigns. The cluster client will strip such automatically.


Line 101:		Line 101:
	cluster node.		cluster node.

	To control a local, single-band CW skimmer ~~DXLog.net.DXC~~ can send automatic QSY commands.<br>		To control a local, single-band CW skimmer the cluster client can send automatic QSY commands.<br>
	If you want to use this feature, decide which DXLog station you want CW Skimmer to track,<br>		If you want to use this feature, decide which DXLog station you want CW Skimmer to track,<br>
	click on "Track station" on the local skimmers tab and enter its station ID into the box and press enter.<br>		click on "Track station" on the local skimmers tab and enter its station ID into the box and press enter.<br>
Line 121:		Line 121:


	Now if you open ~~DXcluster~~ monitor on all LAN network connected DXLog you should see the data from ~~DXlog.net.DXC~~ flowing.		Now if you open DX cluster monitor on all LAN network connected DXLog you should see the data from the cluster client flowing.

	At the bottom of the window you have 10 user definable buttons that can send commands to the cluster node.<br>		At the bottom of the window you have 10 user definable buttons that can send commands to the cluster node.<br>