Getting Started with My Ts Timer Manual
Most people open the manual and immediately get confused by the initialization sequence. The display flickers, the digits jump around, and you spend ten minutes wondering if the unit is broken. It is not broken. The first time you power it on, it runs through a self-test cycle that can look alarming if you are not expecting it. The manual covers this in section two, but honestly, section two is written for people who already know what they are looking at. I will walk you through what actually matters. The manual is essentially a reference document for a timing system that uses threshold sampling to capture events with millisecond precision. The device itself is straightforward — you connect the input probes, set your sampling rate, and arm it. The complexity lives in the configuration. You need to decide on the trigger threshold, the pre-trigger buffer size, and whether you are running single-shot or continuous mode. Getting these three wrong will either make your data useless or crash the acquisition software. I learned that the hard way on a project where I needed 0.5ms resolution but had configured the pre-trigger for only 2 milliseconds of capture window. Every event got cut off at the beginning. The manual's default settings page assumes you are working in a controlled lab environment with clean signals. If you are working in a real industrial setting with electrical noise, those defaults will give you garbage readings. You need to adjust the debounce filter and increase the hysteresis on the trigger comparator. The manual mentions this in a footnote on page 14, buried between two diagrams nobody reads.
Installation and Initial Setup
Download the software package from the manufacturer's site. It is roughly 180 megabytes and includes the driver, the acquisition program, and the manual in PDF format. Install the driver first. If you try to run the application before the driver is registered in your system, it will fail silently — no error message, just a blank connection screen. Run the installation as administrator on Windows, and make sure your USB connection is set to the correct COM port in the device manager before launching anything. Once the driver is installed, open the application and go to Device > Connection. Select your unit from the dropdown. If it does not appear, check that the power LED on the hardware is solid green, not blinking. A blinking LED means the unit is in bootloader mode, which happens if you held down the select button while powering on. Hold the select button for three seconds while it boots to exit bootloader mode.
Configuration Parameters That Actually Matter
There are seventeen configurable parameters in this system. Nine of them you will almost never touch. The four that matter are: Sampling Rate: Set this based on your event duration, not your interest level. A 10kHz sample rate captures events down to about 0.1 milliseconds. Going higher than 100kHz gives you diminishing returns and fills your buffer much faster. For most timing applications, 10kHz to 50kHz is the sweet spot. Trigger Threshold: This is the voltage level at which the timer considers an event to have occurred. Start at 50% of your signal's peak amplitude and adjust from there. If your signal has any overshoot or ringing, raising the threshold by 10% can eliminate false triggers without missing real events.
Get the Full Details
Pre-Trigger Buffer: This determines how much data before the trigger event you capture. Set it to at least 20% of your expected event duration. I once set this to 5% because I thought I knew better than the manual's recommendation. The result was a dataset that captured the tail end of every event but none of the onset. Completely unusable. Had to redo three days of testing. Post-Trigger Buffer: Same logic. Make sure you are capturing the full decay or response of the event, not just the trigger point. A common mistake is setting the post-trigger too short and then wondering why your pulse width measurements are consistently underestimated.
Calibration and Verification
Before you trust any data from this system, run a calibration check. The manual provides a built-in calibration routine accessible through the Diagnostics menu. It generates a known square wave and measures the system's response. Run this before every session, especially if the ambient temperature has changed by more than 5 degrees Celsius since your last use. Temperature drift affects the oscillator, and the manual does not emphasize this enough. If the calibration fails, do not proceed with measurements. Check your probe connections first — loose BNC cables are the most common cause of calibration failure. If the connections are secure and it still fails, try a different USB cable. Cheap cables with high resistance can cause voltage drop that mimics calibration errors.
Common Problems and Workarounds
One issue the manual barely addresses is buffer overflow during long acquisitions. If you are running continuous mode for more than ten minutes at high sample rates, the system will occasionally drop frames. The software will not warn you. It just silently overwrites old data. I discovered this when a client sent me a dataset that looked clean but had gaps in the timing records. I spent two days trying to figure out what was causing the gaps before realizing the buffer had overflowed. The workaround is simple: segment your acquisitions into shorter bursts with explicit save points between them. It adds a few minutes of manual work but prevents data loss. Another issue is electromagnetic interference from nearby equipment. If you see random spikes in your timing data that do not correspond to any real event, you likely have EMI. Shielded cables help, but sometimes the problem is ground loops. Try disconnecting other devices from the same power strip or using an isolated ground connection for the timer unit alone.
Data Export and Integration
The software supports CSV, MAT, and binary export formats. Use CSV for quick analysis in spreadsheet software. Use MAT if you are working in MATLAB, and binary if you need maximum fidelity with large datasets. The binary format preserves all timing metadata, including sub-sample interpolation data that gets stripped in CSV export. If you need microsecond-level precision in your final analysis, always use binary export. For automated workflows, the software includes a command-line interface. You can script acquisitions, trigger exports, and run batch calibrations without opening the GUI. The manual has a section on this, but it is sparse. The actual CLI reference is in a separate document on the manufacturer's website under Resources. It took me a while to find that.
When This System Is Not the Right Tool
This timer system excels at medium-speed event capture with moderate timing precision. It is not designed for sub-nanosecond measurements, and it is not meant for high-frequency signal acquisition above 1MHz. If you need those capabilities, you should be looking at a dedicated oscilloscope or a specialized time-interval analyzer. The manual implies broader capability than the hardware actually delivers, particularly in the marketing materials. Do not push this system beyond its specified operating range and expect clean results. For basic on-off timing applications where millisecond precision is not critical, a simpler mechanical or inexpensive digital timer will do the job faster and with less configuration overhead. The My Ts Timer Manual covers those use cases too, but the system's complexity is overkill for anything that does not require sub-millisecond accuracy and multi-channel synchronization.
