National FIS Software : Timing Setup - Revision history

CJT: /* Snowboard Halfpipe and Slopestyle Scoring */

2012-04-24T18:07:38Z

Snowboard Halfpipe and Slopestyle Scoring

← Older revision		Revision as of 13:07, 24 April 2012
Line 31:		Line 31:

	===Snowboard Halfpipe and Slopestyle Scoring===		===Snowboard Halfpipe and Slopestyle Scoring===
	* With Keypads<br/> Scoring with keypads requires a [[Keys_%26_Licenses\|Timing License and key]] and your timer(s) must be set to [[Timers\|Summit Systems SRT1000]]. For a package of the needed hardware and support to use Judges Keypads with the software, contact Todd Rebhan at Pyramid Sports.		Scoring with keypads requires a [[Keys_%26_Licenses\|Timing License and key]] and your timer(s) must be set to [[Timers\|Summit Systems SRT1000]]. For a package of the needed hardware and support to use Judges Keypads with the software, contact Todd Rebhan at Pyramid Sports.
	** Setting up the SRT 1000 Timer		*Setting up the SRT 1000 Timer
	*** Make sure the SplitSecond timing key is connected to your computer.		*** Make sure the SplitSecond timing key is connected to your computer.
	*** Open the software and choose the "Timing" tab.		*** Open the software and choose the "Timing" tab.

CJT at 18:06, 24 April 2012

2012-04-24T18:06:24Z

← Older revision		Revision as of 13:06, 24 April 2012
Line 29:		Line 29:
	** You've selected the wrong serial port on the computer.		** You've selected the wrong serial port on the computer.
	** Your cable isn't made for interfacing to Split Second. '''Note:''' Just because the cable you have works with some other piece of software doesn't guarantee it will work with Split Second. This is because different software expects different handshaking protocols which can change,depending on the wiring configuration. If everything works great with another application and it doesn't work with Split Second, it's probably the cable. Please contact your timing supplier and request a cable that will work with Split Second.		** Your cable isn't made for interfacing to Split Second. '''Note:''' Just because the cable you have works with some other piece of software doesn't guarantee it will work with Split Second. This is because different software expects different handshaking protocols which can change,depending on the wiring configuration. If everything works great with another application and it doesn't work with Split Second, it's probably the cable. Please contact your timing supplier and request a cable that will work with Split Second.

			===Snowboard Halfpipe and Slopestyle Scoring===
			* With Keypads<br/> Scoring with keypads requires a [[Keys_%26_Licenses\|Timing License and key]] and your timer(s) must be set to [[Timers\|Summit Systems SRT1000]]. For a package of the needed hardware and support to use Judges Keypads with the software, contact Todd Rebhan at Pyramid Sports.
			** Setting up the SRT 1000 Timer
			*** Make sure the SplitSecond timing key is connected to your computer.
			*** Open the software and choose the "Timing" tab.
			*** Select the appropriate interface (Summit Systems SRT1000) from the Serial Port Menu. The serial port should be set to serial Port 1.
			*** Select the number of total devices being used. i.e., 5 will be used for a judging panel of 4 with a Head Judge.
			*** Click the "Initialize SRT 1000 timer(s)" button. You should hear three short beeps from the timers. Confirm that each timer is showing approximately the same time.
			**** NOTE: This will clear out any existing scores from the SRTs.

Geoff at 15:24, 4 January 2010

2010-01-04T15:24:08Z

← Older revision		Revision as of 10:24, 4 January 2010
Line 1:		Line 1:
	==Setup & Test==		==Setup & Test==

	This screen is accessed via the menu at Timing\|Setup & Test.		This screen is accessed via the menu at ''Timing\|Setup & Test''.


Line 15:		Line 15:
	===Raw Data===		===Raw Data===

	As explained on the screen, the right section shows the raw data coming from the timer. This will typically be channel and time of day information, in various formats, depending on the timer being used. Many timers need to be configured in a specific way for the software to interpret the data correctly. Some timers also have the ability to operate in different baud rates (transmission speed from the timer to the computer. The rate has to be selected in the software to match the timer.		As explained on the screen, the right section shows the raw data coming from the timer. This will typically be channel and time of day information in various formats, depending on the timer being used. Many timers need to be configured in a specific way for the software to interpret the data correctly. Some timers also have the ability to operate in different baud rates (transmission speed from the timer to the computer. The rate has to be selected in the software to match the timer.

	===Problem Solving===		===Problem Solving===
Line 23:		Line 23:
	** The wrong timer is selected in the software.		** The wrong timer is selected in the software.
	** The timer is not configured as the software expects (see the information on specific timers).		** The timer is not configured as the software expects (see the information on specific timers).
	** The mapping is wrong. Click on the Input Mapping button to select how various inputs get used.		** The mapping is wrong. Click on the ''Input Mapping'' button to select how various inputs get used.

	* If you see nothing at all in the raw data section; it's probably one of the following:		* If you see nothing at all in the raw data section; it's probably one of the following:

Geoff: Protected "National FIS Software : Timing Setup" [edit=sysop:move=sysop]

2009-11-25T03:39:58Z

Protected "National FIS Software : Timing Setup" [edit=sysop:move=sysop]

← Older revision	Revision as of 22:39, 24 November 2009
(No difference)

Geoff: /* Raw Data */

2009-11-25T03:38:37Z

Raw Data

← Older revision		Revision as of 22:38, 24 November 2009
Line 15:		Line 15:
	===Raw Data===		===Raw Data===

	As explained on the screen, the right section shows the raw data coming from the timer. This will typically be channel and time of day information, in various formats, depending on the timer being used. Many timers need to be configured in a specific way for the software to interpret the data correctly. Some timers also have the ability to operate in different baud rates (transmission speed from the timer to the computer, The rate has to be selected in the software to match the timer.		As explained on the screen, the right section shows the raw data coming from the timer. This will typically be channel and time of day information, in various formats, depending on the timer being used. Many timers need to be configured in a specific way for the software to interpret the data correctly. Some timers also have the ability to operate in different baud rates (transmission speed from the timer to the computer. The rate has to be selected in the software to match the timer.

	===Problem Solving===		===Problem Solving===

75.69.72.54 at 17:58, 20 November 2009

2009-11-20T17:58:48Z

Geoff: /* Raw Data */

2009-10-16T23:43:48Z

Raw Data

← Older revision		Revision as of 18:43, 16 October 2009
Line 16:		Line 16:

	As explained on the screen the right section shows the raw data coming from the timer. This will typically be channel and time of day information in various formats depending on the timer being used. Many timers need to be configured in a specific way for the software to interpret the data correctly. Some timers also have the ability to operate in different baud rates (transmission speed from the timer to the computer) and the rate has to be selected in the software to match the timer.		As explained on the screen the right section shows the raw data coming from the timer. This will typically be channel and time of day information in various formats depending on the timer being used. Many timers need to be configured in a specific way for the software to interpret the data correctly. Some timers also have the ability to operate in different baud rates (transmission speed from the timer to the computer) and the rate has to be selected in the software to match the timer.

			===Problem Solving===

	* If you see raw data but it's totally unreadable (lots of numbers and brackets) it's probably because the baud rate selected in the software doesn't match that of the timer.		* If you see raw data but it's totally unreadable (lots of numbers and brackets) it's probably because the baud rate selected in the software doesn't match that of the timer.

Geoff: /* Raw Data */

2009-10-16T23:42:40Z

Raw Data

← Older revision		Revision as of 18:42, 16 October 2009
Line 16:		Line 16:

	As explained on the screen the right section shows the raw data coming from the timer. This will typically be channel and time of day information in various formats depending on the timer being used. Many timers need to be configured in a specific way for the software to interpret the data correctly. Some timers also have the ability to operate in different baud rates (transmission speed from the timer to the computer) and the rate has to be selected in the software to match the timer.		As explained on the screen the right section shows the raw data coming from the timer. This will typically be channel and time of day information in various formats depending on the timer being used. Many timers need to be configured in a specific way for the software to interpret the data correctly. Some timers also have the ability to operate in different baud rates (transmission speed from the timer to the computer) and the rate has to be selected in the software to match the timer.

	* If you see raw data but it's totally unreadable (lots of numbers and brackets) it's probably because the baud rate selected in the software doesn't match that of the timer.		* If you see raw data but it's totally unreadable (lots of numbers and brackets) it's probably because the baud rate selected in the software doesn't match that of the timer.
	* If you see information that's readable in the raw data but nothing comes up as starts and finishes it's probably one of the following:		* If you see information that's readable in the raw data but nothing comes up as starts and finishes it's probably one of the following:
Line 21:		Line 22:
	** The timer is not configured as the software expects (see the information on specific timers).		** The timer is not configured as the software expects (see the information on specific timers).
	** The mapping is wrong. Click on the Input Mapping button to select how various inputs get used.		** The mapping is wrong. Click on the Input Mapping button to select how various inputs get used.

			* If you see nothing at all in the raw data section it's probably one of the following:
			** You've selected the wrong timer.
			** You've selected the wrong serial port on the computer.
			** Your cable isn't made for interfacing to Split Second. '''Note:''' Just because the cable you have works with some other piece of software doesn't guarantee it will work with Split Second. This is because different software expects different handshaking protocols which can change depending on the wiring configuration. If everything works great with another application and it doesn't work with Split Second, it's probably the cable. Please contact your timing supplier and request a cable that will work with Split Second.

Geoff at 18:31, 16 October 2009

2009-10-16T18:31:59Z

← Older revision		Revision as of 13:31, 16 October 2009
Line 6:		Line 6:
	<div style="background-color:LightGray; -moz-border-radius:15px;">		<div style="background-color:LightGray; -moz-border-radius:15px;">
	::'''NOTE:'''<br>		::'''NOTE:'''<br>
	::* If you don't get times on this screen (look for starts and finishes on the left section as shown below) then you will not get times coming into the timing screen. If things aren't working stay in this screen until they're solved.		::* To make sure the timing interface is working you should always start on this page, and do test starts and finishes. If you don't get times on this screen (look for starts and finishes on the left section as shown below) then you will not get times coming into the timing screen. If things aren't working stay in this screen until they're solved.
	</div>		</div>


	[[image:NatFIS_SetupTest.jpg\|center]]		[[image:NatFIS_SetupTest.jpg\|center]]


			===Raw Data===

			As explained on the screen the right section shows the raw data coming from the timer. This will typically be channel and time of day information in various formats depending on the timer being used. Many timers need to be configured in a specific way for the software to interpret the data correctly. Some timers also have the ability to operate in different baud rates (transmission speed from the timer to the computer) and the rate has to be selected in the software to match the timer.
			* If you see raw data but it's totally unreadable (lots of numbers and brackets) it's probably because the baud rate selected in the software doesn't match that of the timer.
			* If you see information that's readable in the raw data but nothing comes up as starts and finishes it's probably one of the following:
			** The wrong timer is selected in the software.
			** The timer is not configured as the software expects (see the information on specific timers).
			** The mapping is wrong. Click on the Input Mapping button to select how various inputs get used.

Geoff at 18:02, 16 October 2009

2009-10-16T18:02:27Z

← Older revision		Revision as of 13:02, 16 October 2009
Line 1:		Line 1:
	==~~Timing~~ Setup==		==Setup & Test==

	This screen is accessed via the menu at Timing\|Setup & Test.		This screen is accessed via the menu at Timing\|Setup & Test.

← Older revision		Revision as of 12:58, 20 November 2009
Line 6:		Line 6:
	<div style="background-color:LightGray; -moz-border-radius:15px;">		<div style="background-color:LightGray; -moz-border-radius:15px;">
	::'''NOTE:'''<br>		::'''NOTE:'''<br>
	::* To make sure the timing interface is working you should always start on this page, and do test starts and finishes. If you don't get times on this screen (look for starts and finishes on the left section as shown below) then you will not get times coming into the timing screen. If things aren't working stay in this screen until they're solved.		::* To make sure the timing interface is working, you should always start on this page and do test starts and finishes. If you don't get times on this screen (look for starts and finishes on the left section as shown below), then you will not get times coming into the timing screen. If things aren't working, stay in this screen until they're solved.
	</div>		</div>

Line 15:		Line 15:
	===Raw Data===		===Raw Data===

	As explained on the screen the right section shows the raw data coming from the timer. This will typically be channel and time of day information in various formats depending on the timer being used. Many timers need to be configured in a specific way for the software to interpret the data correctly. Some timers also have the ability to operate in different baud rates (transmission speed from the timer to the computer~~) and the~~ rate has to be selected in the software to match the timer.		As explained on the screen, the right section shows the raw data coming from the timer. This will typically be channel and time of day information, in various formats, depending on the timer being used. Many timers need to be configured in a specific way for the software to interpret the data correctly. Some timers also have the ability to operate in different baud rates (transmission speed from the timer to the computer, The rate has to be selected in the software to match the timer.

	===Problem Solving===		===Problem Solving===

	* If you see raw data but it's totally unreadable (lots of numbers and brackets) it's probably because the baud rate selected in the software doesn't match that of the timer.		* If you see raw data but it's totally unreadable (lots of numbers and brackets); it's probably because the baud rate selected in the software doesn't match that of the timer.
	* If you see information that's readable in the raw data but nothing comes up as starts and finishes it's probably one of the following:		* If you see information that's readable in the raw data but nothing comes up as starts and finishes; it's probably one of the following:
	** The wrong timer is selected in the software.		** The wrong timer is selected in the software.
	** The timer is not configured as the software expects (see the information on specific timers).		** The timer is not configured as the software expects (see the information on specific timers).
	** The mapping is wrong. Click on the Input Mapping button to select how various inputs get used.		** The mapping is wrong. Click on the Input Mapping button to select how various inputs get used.

	* If you see nothing at all in the raw data section it's probably one of the following:		* If you see nothing at all in the raw data section; it's probably one of the following:
	** You've selected the wrong timer.		** You've selected the wrong timer.
	** You've selected the wrong serial port on the computer.		** You've selected the wrong serial port on the computer.
	** Your cable isn't made for interfacing to Split Second. '''Note:''' Just because the cable you have works with some other piece of software doesn't guarantee it will work with Split Second. This is because different software expects different handshaking protocols which can change depending on the wiring configuration. If everything works great with another application and it doesn't work with Split Second, it's probably the cable. Please contact your timing supplier and request a cable that will work with Split Second.		** Your cable isn't made for interfacing to Split Second. '''Note:''' Just because the cable you have works with some other piece of software doesn't guarantee it will work with Split Second. This is because different software expects different handshaking protocols which can change,depending on the wiring configuration. If everything works great with another application and it doesn't work with Split Second, it's probably the cable. Please contact your timing supplier and request a cable that will work with Split Second.