Arinc 629 ethernet converter
US-2015373154-A1 · Dec 24, 2015 · US
US10042688B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10042688-B2 |
| Application number | US-201615058834-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 2, 2016 |
| Priority date | Mar 2, 2016 |
| Publication date | Aug 7, 2018 |
| Grant date | Aug 7, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A self-diagnostic device driver includes a memory that stores machine instructions and a processor coupled to the memory that executes the machine instructions to record an operational history associated with the device driver. The processor further executes the machine instructions to detect an error associated with the device driver, remove an associated driver from service, and automatically replicate a sequence of device driver operations corresponding to a segment of the operational history immediately preceding detection of the error. The processor also executes the machine instructions to automatically record a diagnostic history associated with the device driver while replicating the sequence of device driver operations. After the sequence has been replicated, the device is returned to service.
Opening claim text (preview).
What is claimed is: 1. An apparatus for self-diagnosis using a device driver, comprising: a memory that stores machine instructions; and a processor coupled to the memory and configured to execute the machine instructions, wherein the machine instructions, when executed, cause the processor to: implement the device driver as an interface between a first hardware device and a host computer; record an operational history associated with the device driver; detect an error associated with the device driver; and responsive to detecting the error and without user intervention, automatically stop the first hardware device from servicing the host computer, automatically replicate a sequence of device driver operations corresponding to a segment of the operational history that precedes detection of the error by repeating performance of the sequence of the device driver operations, automatically record a diagnostic history associated with the device driver while replicating the sequence of device driver operations, and instruct the first hardware device to resume servicing the host computer. 2. The apparatus of claim 1 , wherein the device driver is further implemented as an interface between the host computer and a second hardware device, and wherein the machine instructions, when executed, further cause the processor to suspend, responsive to detecting the error, normal operations of the first hardware device while the sequence of device driver operations are automatically replicated, and while continuing normal operations of the second hardware device, and resume normal operations of the first hardware device after the sequence of device driver operations has been automatically replicated. 3. The apparatus of claim 1 , wherein the machine instructions, when executed, further cause the processor to duplicate the error while the sequence of device driver operations are automatically replicated. 4. The apparatus of claim 1 , wherein the machine instructions, when executed, further cause the processor to configure a control setting, wherein the sequence of device driver operations are automatically replicated and automatically recorded based on the control setting currently being configured to enable self-diagnosis. 5. The apparatus of claim 1 , wherein the apparatus does not require an intervention by an operator to automatically replicate and automatically record the sequence of device driver operations. 6. The apparatus of claim 1 , wherein the operational history corresponds to a period of normal operation of the first hardware device. 7. The apparatus of claim 1 , wherein recording the operational history includes recording device driver operations associated with a plurality of processes associated with the host computer. 8. A method, comprising: implementing a device driver as an interface between a first hardware device and a host computer; recording an operational history associated with the device driver; detecting an error associated with the device driver; responsive to detecting the error and without user intervention, automatically suspending access to the first hardware device from a host computer, automatically replicating a sequence of device driver operations corresponding to a segment of the operational history that precedes detection of the error by repeating performance of the sequence of the device driver operations, automatically recording a diagnostic history associated with the device driver while replicating the sequence of device driver operations, and resuming access to the first hardware device from the host computer. 9. The method of claim 8 , wherein the device driver is further implemented as an interface between the host computer and a second hardware device, the method further comprising: suspending, responsive to detecting the error, normal operations of the first hardware device associated with the device driver while automatically replicating the sequence of device driver operations, while continuing normal operations of the second hardware device and allowing access to the second hardware device from the host computer; and resuming normal operations of the first hardware device after automatically replicating the sequence of device driver operations. 10. The method of claim 8 , further comprising duplicating the error while automatically replicating the sequence of device driver operations. 11. The method of claim 8 , further comprising configuring a control setting, wherein the automatically replicating and automatically recording are only performed based on the control setting currently being configured to enable self-diagnosis. 12. The method of claim 8 , wherein the segment of the operational history corresponds to a predetermined period of time. 13. The method of claim 8 , wherein the segment of the operational history corresponds to a predetermined number of device driver operations. 14. The method of claim 8 , wherein automatically replicating and automatically recording do not require an intervention by an operator. 15. The method of claim 8 , further comprising sending a command from the device driver to a device communicatively connected with a host computer, wherein the device driver is executed on the host computer. 16. The method of claim 8 , wherein the operational history corresponds to a period of normal operation of the first hardware device. 17. The method of claim 8 , wherein recording the operational history includes recording at least one of a system call received by the device driver from an operating system associated with the host computer, a command sent to the first hardware device from the device driver, or a routine executed by the device driver. 18. The method of claim 8 , wherein recording the operational history includes recording device driver operations associated with a plurality of processes associated with the host computer. 19. A computer program product for self-diagnosis of a device driver, comprising: a non-transitory, computer-readable storage medium encoded with instructions adapted to be executed by a processor to implement operations, comprising: implementing a device driver as an interface between a first hardware device and a host system; recording an operational history associated with the device driver; detecting an error associated with the device driver; responsive to detecting the error and without user intervention, automatically suspending access to the first hardware device from a host system, automatically replicating a sequence of device driver operations corresponding to a segment of the operational history that precedes detection of the error by repeating performance of the sequence of the device driver operations, automatically recording a diagnostic history associated with the device driver while replicating the sequence of device driver operations, and resuming access to the first hardware device from the host system. 20. The computer program product of claim 19 , wherein the device driver is further implemented as an interface between the host system and a second hardware device, and wherein the operations further comprise: suspending, responsive to detecting the error, normal operations of the first hardware device associated with the device driver while automatically replicating the sequence of device driver operations, while continuing normal operations of the second hardware device and allowing access to the second hardware device from the host system; and resuming normal operations of the first hardware device a
for interfaces, buses · CPC title
Error or fault reporting or storing · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.