Skip to main content

New laptop with Windows 10 needed Timy driver. Downloaded from Alge site and installed without issue. Windows does not 'see' Timy in Device Manager. Restart computer, issue resolved. Open SST, software says 'Timy connected' but is not receiving pulses. I downloaded and ran Alge Excelwriter, runs fine and sees pulses from Timy.

I'd thought about downloading and running ComToFile when I was on the Alge site for Timy driver, but it didn't list Win 10 as a supported OS, so I passed. Revisit the site now and download ComToFile anyway. Clicked a few buttons with German labels and and shut it down. Restart SST and hey whaddya know, we have a heartbeat and pulses are received with correct channel attribution.

After all these years, and with supposedly better OS platforms, we still have to run this obscure little utility (whose real purpose is unclear) to make our expensive piece of timing hardware talk to a computer. All very strange.

Anyway, I'm sure I'm not the first person to go this process with Windows 10. Just thought I'd post my experience for those who may go through this in the future. Please don't leave this work until the morning of a race!
Original Post
Some more info to ponder ...

Years ago, I tried making the switch from serial to USB when connecting a Timy to Windows XP PC. Went through the whole ComToFile thing, etc. I had nothing but trouble and went back to serial. Sometimes the PC would see the Timy, sometimes not -- it seemed like it also depended on which of the PC's USB ports I used.

Last season, we switched to Windows 10 laptops with no serial ports, and so again tried to make the switch to USB. It seemed to work, but then again I'd occasionally have problems. In the end, I decided to use a USB to serial converter cable, which worked flawlessly all season.

-- Mark

Add Reply

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