Test engineers who have developed automated test systems with USB-based instruments probably won't upgrade for a very long time. Why introduce a new variable that might bring a system down. There could be timing problems, as Eric Bogatin wrote in العاب كرتون نتورك
MB: Renew Computers is a business near my home in Northern Calif that refurbishes older computers that people brought in for recycling. A 2-3 year old laptop or desktop comes with software and a warranty for about $200-250, depending on what you're looking for. They're doing a nice business -- friendly folks with a service department you just gotta love.
Our test customers (and our software customers) often have difficultly putting together and maintaining a USB Gold Tree for interop testing. The specified equipment can be hard to find, and you almost have to be a certified test lab to be sure that what you have matches the current USB-IF reference.
The gold tree is relatively inexpensive, and it's reasonable for anybody serious about USB testing to have one inhouse. The test equipment for USB 3 pre-compliance testing (or even for USB 2 pre-compliance testing) is quite expensive. Smaller groups will find that it's hard to justify purchasing the gear. But it's still important to test! One alternative is to engage a USB certified test lab -- most labs offer some kind of pre-screening or pre-compliance test service. Even if USB logo certification is not an important marketing requirement, these tests are important.
Coming back to your question, Janine about "horror stories on compliance testing" -- I think the bigger horror stories relate to our customers who didn't do compliance testing as part of their product development cycle, and then found that their products had unacceptable failure rates in the field.
I buy old Dell D600 laptops froim eBay. First one (now spare parts) cost $330. Latest one cost under $100 with a 3x larger hard drive. I have two others, though one is showing signs of mechanical problems.
For watching streaming video, an iPad2 does a better job.
I'm with you, Measurement Blues. I have a couple over very stable XP machines that won't die. Whenever I get tempted to buy a new computer, I find I'd rather spend the cash on fixing the roof or taking a weekend trip. It's not just engineers, I think....there are millions of consumers who used to snap up every new gizmo and are now giving second thoughts to making such major purchases. And then there is the generational thing: I know scores of people under 30, but very few of them would consider buying a laptop today (never mind a desktop machine). I'm not sure what impact those changes will have on the adoption of USB 3.0, but it seems like it is bound to slow it down. Thoughts?
Test engineers who have developed automated test systems with USB-based instruments probably won't upgrade for a very long time. Why introduce a new variable that might bring a system down. There could be timing problems, as Eric Bogatin wrote in USB: Not Always Universal.
>Does anyone know when this is expected to be commonplace in devices?
It will take several years as people upgrade their computers. Some might add USB 3.0 through an adapter for a desktop computer. The rest of us will porbably get USB 3 with or next computer. Me? I'm still running XP computers and will until they die. Engineers aren't usually the early adapters. Instead, we find way to keep our old equipment running.
I recently bought an external Hard drive that's USB 3.0 equipped. I run it at USB 2.0 speeds.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.