• Fortin Support
• Drivers Fortin Electronic Ignition
• Drivers Fortin Electronics

• Coming up this fall, Fortin will introduce the first phase of its data bypass solution for both Volkswagen and Audi vehicles as well as a custom fit T-Harness solution. Fortin Electronic Systems is a world leading developer and manufacturer of integrated consumer solutions for vehicle control and connectivity.
• Fortin Electronic Systems is a world leading developer and manufacturer of integrated consumer solutions for vehicle control and connectivity. Driver door triger - Questions & Answers hi i have the 2008 ford fusion,is the driver door triger same as door pin FL?
• Twenty years ago, the first versions of the technology now known as electronic onboard recorders (EOBRs) required drivers to use portable storage devices to transfer logs from the truck to the office.

FlashLink Manager is a remote starter, bypass module and alarm system installation software for Fortin Electronic Systems products and solutions. 4-wire Fortin 2-way datalink port for data-to-data (RS-232) communication with datalink equipped remote-starters and security-systems. 2 20-wire general purpose plug for wire-to-wire connections with non-datalink equipped remote-starters and security-systems.

Digital signatures are based on Microsoft public key infrastructure technology, which is based on Microsoft Authenticode combined with an infrastructure of trusted certification authorities (CAs). Authenticode, which is based on industry standards, allows vendors, or software publishers, to sign either a file or a collection of files (such as a driver package) by using a code-signing digital certificate that is issued by a CA.

Windows uses a valid digital signature to verify the following:

• The file, or the collection of files, is signed.

• The signer is trusted.

• The certification authority that authenticated the signer is trusted.

• The collection of files was not altered after it was published.

For example, this signing process for a driver package involves the following:

• A publisher obtains an X.509 digital certificate from a CA. An Authenticode certificate is also referred to as a signing certificate. A signing certificate is a set of data that identifies a publisher, and is issued by a CA only after the CA has verified the identity of the publisher. A CA can be a Microsoft CA, a third-party commercial CA, or an Enterprise CA.

  The signing certificate is used to sign the catalog file of a driver package or to embed a signature in a driver file. Certificates that identify trusted publishers and trusted CAs are installed in certificate stores that are maintained by Windows.

• The signing certificate includes a private key and a public key, which is known as the key pair. The private key is used to sign the catalog file of a driver package or to embed a signature in a driver file. The public key is used to verify the signature of a driver package's catalog file or a signature that is embedded in a driver file.

• To sign a catalog file or to embed a signature in a file, the signing process first generates a cryptographic hash, or thumbprint, of the file. The signing process then encrypts the file thumbprint with a private key and adds the thumbprint to the file.

  The signing process also adds information about the publisher and the CA that issued the signing certificate. The digital signature is added to the file in a section of the file that is not processed when the file thumbprint is generated.

• To verify the digital signature of a file, Windows extracts the information about the publisher and the CA and uses the public key to decrypt the encrypted file thumbprint.

  Windows accepts the integrity of the file and the authenticity of the publisher only if the following are true:

  • The decrypted thumbprint matches the thumbprint of the file.
  • The certificate of the publisher is installed in the Trusted Publishers certificate store.
  • The root certificate of the CA that issued the publisher's certificate is installed in the Trusted Root Certification Authorities certificate store.

For more information about how the Plug and Play (PnP) device installation uses the digital signature of a driver package'scatalog file, see Digital Signatures and PnP Device Installation.

For more information about Microsoft public key infrastructure technology, code signing, and digital signatures, see Introduction to Code Signing and Code Signing Best Practices.

Much has changed during the time fleets have used paperless, electronic logs. Twenty years ago, the first versions of the technology now known as electronic onboard recorders (EOBRs) required drivers to use portable storage devices to transfer logs from the truck to the office. Logbooks were paperless, but fleet managers had no real-time visibility of drivers’ hours-of-service (HOS) status.

Today, the benefits of EOBR technology reach far beyond the use of paperless logbooks. For many fleets, the technology plays an integral role in fleet operations through the use of intelligent onboard computing, wireless communications and advanced reporting functionality.

Through wireless connectivity, fleet managers now have instant visibility of vehicles and drivers’ HOS status, along with other safety and performance information, says Tom Flies, senior vice president of product management for Xata Corp. The company offers EOBR applications in its Xatanet wireless fleet operations system.

Fortin Support

Fleets have the flexibility to set up their own parameters for how they wish to monitor HOS information. The moment a violation occurs, exception alerts can pop into the e-mail inbox or cell phone of a fleet manager. Fleets can use Xatanet to help prevent violations by issuing advance alerts, such as when a driver is still en route with less than one hour of available drive time remaining, Flies says. Combined with other information available in Xatanet’s Web-based reporting tools, fleets can gain new insights into the safety and performance of their operations and take immediate corrective actions, Flies says.

Another trend is the integration of HOS information into fleet dispatch, routing and load planning systems. Dispatch software providers are using PeopleNet’s XML-based open interface to capture available hours for each driver into their own software, says Bridget Fortin, product development manager for PeopleNet. Through the integration, fleet managers can ensure that drivers have the proper hours before making load assignments. Once load assignments are made, fleets can login to the PeopleNet Fleet Manager website to view a variety of reports, such as a violation detection report, and drill down into the details to see how it occurred, Fortin says.

Cadec recently launched a software-as-a-service (SaaS) platform called PowerVue. Through PowerVue’s Web interface, XML-based Web services technology and Oracle-driven business intelligence tools, customers can fully integrate HOS information with various fleet management applications, says Steve Katz, director of strategic accounts for Cadec.

One of the standard reports in PowerVue shows the available hours for each driver. Fleets can use the information as a reference tool, import it directly into their planning system, or set up automatic queries through XML Web services.

“We are making information available so it can be used more intensely,” Katz says. Cadec also recently launched a new touchsreen display, the Series 100, for use with its PowerVue system. Cadec manufactures the Series 100 hardware itself, Katz says.

Later this year, Qualcomm plans to release a new business intelligence tool that will help fleets better manage the data collected from vehicles and drivers via onboard computing, including EOBR data. With real-time connectivity to the vehicle and drivers’ HOS status, fleet managers can optimize what loads they assign to drivers based on historic averages for the runtime of a trip, says Norm Ellis, vice president and general manager of transportation and logistics for Qualcomm Enterprise Services.

The business intelligence platform from Qualcomm will help fleets combine HOS information with other driver safety information, including hard braking and lane changes, to truly understand risk rather than merely focusing on HOS compliance, Ellis says.

Vendors continue to make EOBR information more intelligent and flexible to use, but the technology also continues to become more affordable and portable. Last year, Turnpike Global Technologies launched a new feature that makes electronic logs available on Java-based cell phones and Windows mobile devices.

Turnpike uses a small vehicle-mounted computer with GPS functionality called Route Tracker. Through a link to the vehicle’s databus, Route Tracker captures odometer readings and driver/vehicle performance information. The electronic HOS application resides on a handset and communicates with Route Tracker through a robust, wireless Bluetooth connection, says Kelly Frey, Turnpike’s executive vice president of sales. Drivers login to the HOS application by entering a personal identification number, and the application in the handset is synchronized automatically with Route Tracker.

In February, Turnpike launched a Sprint product whereby Sprint customers can add Turnpike services directly to their Sprint invoice. Customers pay $35 per month to have Route Tracker’s Web-based mapping, engine diagnostics, automated IFTA reporting and electronic HOS on a Sprint handset. The handheld electronic HOS application is 100 percent compliant with DOT regulation 395.15, the company says.

Wireless communications, intelligent computing and reporting, and low-cost offerings all point to EOBR technology having a bright future in the industry. Automating paper logbooks is just the tip of the iceberg.

Drivers Fortin Electronic Ignition

Drivers Fortin Electronics