Skip to main content

Hi all. Here at the Big Mountain we have 2 S4s and we are having the same problem with both of them. It is as follows (copied here from the S4 forum)

Ok, here's the deal:
When we connect wands and photocells to our S4, we use both the banana plug inputs (c0,c3,c6,c9) and the DIN inputs (A,B,C, aka c1,c4,c7). When we use the DIN inputs, we use cables that have been floating around our department since before any of us got here that have a DIN plug on one side and two banana plugs on the other, which we then connect to our eyes or wands. We also have a couple of longer cables with DIN connectors on both sides which we use for eyes. With every single one of these, we have no idea which pins are being used. I notice when reading other discussions on this forum that depending on which pins are active, you can get a start or a finish on the same port, but I don't understand this yet.

So. Other problems and the evident lack of knowledge on our part aside, here is the problem that we are having: With SplitSecond running and with the timing setup and test window open, we can see raw data coming in when we short all 7 ports (c0,c1/A,c3,c4/B,c6,c7/C,c9). It is all correctly labeled and formatted in the raw data window. However, when we open a race and try to time it (and yes we are mapping the inputs as we test this), this happens:

Using ports c0,c1/A,c3,and c4/B, with input mapping we can use any of these four ports to give us starts, finishes, and intervals. But, we cannot get starts, finishes, or intervals from ports c6,c7/C, or c9, no matter how they are mapped. (One of these is a DIN port, the other two are banana plugs) The reason this is so confusing to us is that we can get raw data from these ports, but we cannot get SplitSecond to recognize the raw data from just those three ports and convert them to starts, finishes, and intervals.

So, I can't imagine that it's anything but an issue with SplitSecond, although we have checked the connections inside the S4 as mentioned above and set it to reset its memory on every power on just to be sure.

Thanks guys,

Donnie
(and Josh)
Original Post
The S4 timer has maximum memory of 8000 times. No times will be transmitted to the PC if this limit is exceeded. Times will still be printed out ( one very good reason why the FIS/USSA requires a directly connected battery powered printer on all timers). The S4 manual deals with this situation on page 12. Please take the time to read it. You CANNOT deal with the problem once the race has begun! All S4 timers shipped from PST are set to ask the CLr JA question upon start up. By pressing the Red and Yellow buttons together you are clearing the memory. You will not use up the 8000 splits under normal circumstances. You may however if you have a tremendous number of false pulses do to faulty wiring, poorly shielded PC connections or static discharges. The FIS requirement of shutting down the timer and performing a resync for the next run certainly cuts down on the possiblities of memory overflow as well.

To set the S4 on Clr Ja

1)Hold the toggle switch up and turn timer on

2)Release toggle

3) Press toggle up once the timer stops the start up routine

4) Clr NEIN (no in german) will appear

5) Press the Yellow button once and CLr JA (yes in german) appears

6) Press Red and Yellow together to confirm and save Clr JA

7) The timer will now ask Clr JA when ever it is turned on again

Changing batteries should not cause the timer to lose the programming. Please be vigilent. Never let anyone start timing a race without clearing the memory.

You then need to make sure the S4 is set in Program 3 and you should be all set.

Add Reply

Post
×
×
×
×
Link copied to your clipboard.
×