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 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. 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)