I often have bad experience with Tektronix product’s design (user convenience, reliability and repairability issues), and the by policy poor support for discontinued products. So far I have yet to get a chance to say good things about Tektronix while Agilent blew them out of water in these 4 areas.
Nonetheless, I have something good to say about Tektronix today. I have a DPO4000 series oscilloscope that the knob and busing popped out during shipping and disappeared, so I had to order them from Tektronix.
The operator on the phone noticed the part numbers and was aware that it’s a common problem that the jog shuttle’s knob and busing (for the Wave Inspector feature) often come loose, and offered to send it to me for free. That’s excellent customer service. The part that I admired the most is that they proactively acknowledged their design weakness and make amends.
Seems like Tektronix takes good care of their customers as long as the models are still supported. Definitely a redeeming quality!
I’d like to charge my phone and use USB devices at the same time, but it seems like it requires a 64.9kOhm resistor from sensor ID pin (micro USB) to ground. Instead of melting a USB-OTG cable, I bought this adapter (schematics here)
so that I can have direct access to the ID pin. This is a USB 3.0 give that I have a Galaxy Note 3. The same principles apply to the USB 2.0 versions for Galaxy Note 4.
According to this website, fsa9480_i2c.h has the table for the resistor ID values. Turns out 64.9kOhm is the one for both charging (slowly) and using USB devices (like mouse, network adapter, etc.).
Windows has a path length limit that are typically at the order of 250 (260 for Windows 10) that’s a pain in the butt when moving files. Despite you can override it, it’s no fun when you copy a jillion files just to find out a few can’t make it because the path is too long and you have to find out which ones are not copied!
There’s a short command to check if the path exceed certain number of characters, which I recommend testing for 240 character so you can at least have a 10+ character folder on the root folder to put the files in:
powershell: cmd /c dir /s /b |? {$_.length -gt 240}
Turns out it’s a common problem when dual-booting Windows and Linux, they keep changing the hardware system clock on each other (unless you live in GMT+0 zone) because Windows assume the system time is the one at the set timezone while Linux think the system time is the UTC+0 time (and offset it afterwards).
Linux updates the time through NTP server blindly while Windows 7 check if the current time is within 1hr from the NTP server to avoid unintended time changes (I have to give Microsoft credit for that). EDIT: Windows 10 blindly updates the time like Linux too.
The easy solution is to have Linux follow Windows’ suit:
