430-817 #606, 5th Dongyoung Venturestel, 199-32, Anyang 7-dong, City/Area. In 2012, Smithfield announced a 15-race sponsorship with Richard Petty Motorsports (RPM) and driver Aric Almirola driving the No. 43 Ford Fusion in the NASCAR Sprint Cup Series. The sponsorship was increased to 30 races beginning in 2014. Smithfield rotates its brands on the car, featuring Smithfield, Eckrich, Farmland, Gwaltney, and Nathan's.
Vericom Global Solutions is an equal opportunity employer and does not unlawfully discriminate in employment. Qualified applicants are considered for all positions without regard to age, race, color, marital status, religion, national origin, veteran’s status, disability, or any other legally protected class. Vericom Global Solutions encourages our customers to contact us regarding any questions you have about the business. Please send us your comments/questions, along with any other information that you might require regarding our products or services. Our Customer Support team is available during normal business hours: Monday-Friday: 8:00am - 8. There's a wonderfully simple yet attractive instrument layout with a 7000-rpm tachometer, 180-mph speedometer, and warning-lamp binnacles centered in front of the driver.
By Richard Tackett with reporting by David Hubbard
Vericom LLC has been providing precise, easy-to-use engineering test systems for 35 years.
In 1984, Roger McCumber, along with fellow ‘hot rod’ and drag-racing enthusiasts, wanted to create a device to test the speeds of performance cars and motorcycles. That lead to the development of one of the very first electronic accelerometers.
“Once Roger developed the accelerometer, his fellow car enthusiasts started asking for devices of their own,” said Todd Schaeffer. “So Vericom started as a business focused on hot-rod enthusiasts.”
This led to the creation of the VC200 – Vericom’s first commercialized motion and vehicle performance testing system.
Over time, users of the system pointed out to McCumber that Vericom’s precision test computers would work well in other fields. It stood to reason that if the Vericom system could measure an object’s speed, it could also measure an object’s braking capability and deceleration. Eventually, Vericom testing systems became commonplace in the police forensics field and runway friction testing.
In the 1990s, the VC200 evolved into the Vericom VC2000 and then again into the VC3000. The VC3000 included the addition of an advanced graphing and analysis tool that allowed users to review the details of their test data. Today, the Vericom VC4000 Brake Meter and VC4000 family of precision test instruments have seen widespread adoption in public transportation for its accuracy, simplicity, and affordability in determining vehicle braking capability as compliance to Federal and State regulations.
Breaking into transit
It was the company’s initial expansion into police and law enforcement which precipitated its entry into the public transportation market, Schaeffer said.
“Many of the police inspectors using the technology were also commercial vehicle inspectors,” he said. “Our entry into the public transit market was a direct result of those end-users’ prior experience with our product.”
Per Section §393.52 of the Federal Motor Carrier Safety Act, when testing brake performance, any motor vehicle must be capable of stopping from 20 miles per hour within a designated distance. The customers required to comply with that regulation needed a simple, affordable, high-performance brake meter, Schaeffer said.
The Vericom VC4000 Brake Meter mounts easily to a vehicle via suction cup, and brake testing is activated by pressing two buttons. Each test on the meter takes about 10 seconds. Upon completion, the display screen immediately notifies the driver whether the vehicle’s brake system passed or failed.
“Our customers do not need a lot of extraneous information,” Schaeffer said. “They’re interested in whether their vehicles passed or failed based on the Federal and State standards.”
The system assesses a vehicle’s stopping distance and braking rate (which is also known as the deceleration rate).Testing with a Vericom unit can also indicate when a braking system is ready to for replacement or service.
Vericom’s transit business expanded throughout the 1990s, and the early- to mid-aughts saw the Vericom VC4000 Brake Meter and VC4000 PC become the adopted standards for testing brake performance across the U.S. – including for standardized commercial vehicle testing in New York and New Jersey.
“Our transit business really grew when New York, New Jersey, parts of California, Texas, and some of the other states with the bigger transit organizations started to adopt Vericom technology,” Schaeffer said.
In addition to public transit agencies, Vericom’s family of products are also widely used by several Departments of Transportation across the country. For example, the Midwest Roadside Safety Facility of Lincoln, Nebraska, uses the VC4000 DAQ, often utilized in accident reconstruction, in full-scale crash tests of roadside safety devices.
The products also see notable use at the New York Department of Transportation, Jacksonville’s Institute of Police Technology and Management, and the Northwestern University Traffic Institute in Evanston, Illinois.
As the company grew, it added the sensors needed to test more the complicated motion that occurs in buses, trolleys, and trains.Some newer transit buses have large batteries mounted to their roofs.For roof-mounted battery applications, transit engineers and maintenance professionals need a tool that can easily test the ‘side’ rotation a bus may experience when a large weight, such as a battery, on the roof of the bus.
“We are proud that Vericom provides the solution for these new needs,” Schaeffer said. “As vehicles develop, the technology surrounding them needs to advance as well.”
More sophisticated analysis software, and the ability to connect pressure sensors to the Vericom test systems, were also added in recent years.
1984: Roger McCumber and fellow ‘hot rod’ enthusiasts develop one of the first electronic accelerometers.
1990s: Vericom products become popular with law enforcement agencies, which used the brake meters for accident reconstruction.
2000s: Transit agencies begin adopting Vericom technology due to its accuracy and easy-to-use design.
2019: Vericom continues to innovate, enhancing its product family to better meet its customers’ needs.
Setting the standard
Schaeffer said the key to the Vericom product family’s success is not only the devices’ precision, but the fact that they can reduce complex problems into simple solutions.
“We provide technical engineering test systems that are simple and easy to use,” he said. “The Vericom units are intended for the professional that needs the answer quickly and avoid unnecessary data. Other similar test systems dump all the data on the user with no assistance in providing the answer needed.”
“We’re proud that our customers say, ‘It’s easy, it works when I need it to work, and it gives me accurate information,’” he added.
Looking ahead, Schaeffer said that Vericom’s plans for the future are to continue serving its customers with sophisticated engineering and test systems that are easy to use and provide consistent results they can trust.
“When we talk to customers, we always try to solve their problems with a tool that is easy to use and delivers the test results that are clear and understandable,” he said.
As an example, Schaeffer pointed to a feature on the company’s latest V-SenseTM product: the pass/fail user setting. He explained that many transit customers need to achieve a certain braking deceleration rate when testing brake systems. To further simplify the process, Vericom introduced the new setting so a user can standardize the pass/fail limit.After a test is competed, the operator will quick see a green or red screen to indicate whether a vehicle passed.
“That seems like it’s such a simple thing, but it’s a big deal to the operator,” Schaeffer said. “We try to take our customers’ technical issues and make them practical, by asking ourselves, ‘Can we add some sort of feature, sensor, or capability that continues to simplify their lives?’”-->
Driver Verifier monitors Windows kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject Windows drivers to a variety of stresses and tests to find improper behavior. You can configure which tests to run, which allows you to put a driver through heavy stress loads or through more streamlined testing. You can also run Driver Verifier on multiple drivers simultaneously, or on one driver at a time.
- Running Driver Verifier could cause the computer to crash.
- You should only run Driver Verifier on computers that you are using for testing and debugging.
- You must be in the Administrators group on the computer to use Driver Verifier.
- Driver Verifier is not included in Windows 10 S, so we recommend testing driver behavior on Windows 10 instead.
Where can I download Driver Verifier?
You don't need to download Driver Verifier, because it is included with most versions of Windows in %WinDir%system32 as Verifier.exe. (Driver Verifier is not included with Windows 10 S.) Driver Verifier is not distributed separately as a download package.
For information about changes in Driver Verifier for Windows 10 and previous versions of Windows, see Driver Verifier: What's New.
When to use Driver Verifier
Run Driver Verifier throughout development and testing of your driver. More specifically, use Driver Verifier for the following purposes:
To find problems early in the development cycle, when they are easier and less costly to correct.
For troubleshooting and debugging test failures and computer crashes.
To monitor behavior when you deploy a driver for testing using the WDK, Visual Studio, and the tests from the Windows Hardware Lab Kit (Windows HLK) or Windows Hardware Certification Kit (for Windows 8.1). For more information about testing drivers, see Testing a Driver.
How to start Driver Verifier
You should only run Driver Verifier on test computers, or on computers that you are testing and debugging. To get the most benefit from Driver Verifier, you should use a kernel debugger and connect to the test computer. For more information about debugging tools, see Debugging Tools for Windows (WinDbg, KD, CDB, NTSD).
Start a Command Prompt window by selecting Run as administrator, and type verifier to open Driver Verifier Manager.
Select Create standard settings (the default task), and select Next.
You can also choose Create custom settings to select from predefined settings, or to select individual options. For more information, see Driver Verifier options and rule classes and Selecting Driver Verifier Options.
Under Select what drivers to verify, choose one of the selection schemes described in the following table.
Option Recommended use Automatically select unsigned drivers
Useful for testing on computers that are running versions of Windows that do not require signed drivers.
Automatically select drivers built for older versions of Windows
Useful for testing driver compatibility with newer versions of Windows.
Automatically select all drivers installed on this computer
Provides maximum coverage in terms of the number of drivers that are tested on a system. This option is useful for test scenarios where a driver can interact with other devices or drivers on a system.
This option can also exhaust the resources available for Special Pool and some resource tracking. Testing all drivers can also adversely affect system performance.
Select driver names from a list
In most cases, you will want to specify which drivers to test.
Selecting all drivers in a device stack allows the Enhanced I/O Verification option to track objects and check compliance because an I/O request packet (IRP) is passed between each of the drivers in the stack, which allows for a greater level of detail to be provided when an error is detected.
Select a single driver if you are running a test scenario that measures system or driver performance metrics, or if you want to allocate the greatest number of resources available for detecting memory corruption or resource tracking issues (such as deadlocks or mutexes). The Special Pool and I/O Verification options are more effective when used on one driver at a time.
If you chose Select driver names from a list, select Next, and then select one or more specific drivers.
Select Finish, and then restart the computer.
You can also run Driver Verifier in a Command Prompt window without starting Driver Verifier Manager. For example, to run Driver Verifier with the standard settings on a driver called myDriver.sys, you would use the following command:
For more information about command line options, see Driver Verifier Command Syntax.
How to control Driver Verifier
You can use either Driver Verifier Manager or a command line to control Driver Verifier. To start Driver Verifier Manager, see How to start Driver Verifier, earlier in this topic.
For each of the following actions, you can use Driver Verifier Manager or enter a command line.
To stop or reset Driver Verifier
In Driver Verifier Manager, select Delete existing settings, and then select Finish.
Enter the following command at a command prompt:
Restart the computer.
To view Driver Verifier statistics
In Driver Verifier Manager, select Display information about the currently verified drivers, and then select Next. Continuing to select Next displays additional information.
Enter the following command at a command prompt:
To view Driver Verifier settings
In Driver Verifier Manager, select Display existing settings, and then select Next.
Enter the following command at a command prompt:
How to debug Driver Verifier violations
To get the most benefit from Driver Verifier, you should use a kernel debugger and connect it to the test computer. For an overview of debugging tools for Windows, see Debugging Tools for Windows (WinDbg, KD, CDB, NTSD).
If Driver Verifier detects a violation, it generates a bug check to stop the computer. This is to provide you with the most information possible for debugging the issue. When you have a kernel debugger connected to a test computer that is running Driver Verifier, and Driver Verifier detects a violation, Windows breaks into the debugger and displays a brief description of the error.
All violations detected by Driver Verifier result in bug checks. Common bug check codes include the following:
For more information, see Handling a Bug Check When Driver Verifier is Enabled. For tips about debugging Bug Check 0xC4, see Debugging Bug Check 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION.
When you start a new debugging session, use the debugger extension command, !analyze. In kernel mode, the !analyze command displays information about the most recent bug check. To display additional information, to help identify the faulting driver, add option -v to the command at the kd> prompt:
Vericom Driver Download
In addition to !analyze, you can enter the following debugger extensions at the kd> prompt to view information that is specific to Driver Verifier:
!verifier dumps captured Driver Verifier statistics. Use !verifier -? to display all of the available options.
!deadlock displays information related to locks or objects tracked by Driver Verifier's deadlock detection feature. Use !deadlock -? to display all of the available options.
!iovirp [address] displays information related to an IRP tracked by I/O Verifier. For example:
!ruleinfo [RuleID] displays information related to the DDI compliance checking rule that was violated. (RuleID is always the first argument to the bug check.) All rule IDs from DDI compliance checking are in the form 0x200nn. For example: