Virtual modes for x-ray detectors

Abstract

A detector, comprising a memory capable of storing a factory config file and a Virtual Mode Map (VMM) file. Wherein the detector is configured to load virtual modes from the VMM file for operation of the detector when the VMM file is present in the detector memory, and wherein the detector is configured to load modes from the factory config file for operation of the detector when no VMM file is present in memory. An application for using a factory configuration containing preset factory modes to create a VMM containing one or more virtual modes for operation of the detector. A single preset factory mode may be selected to provide multiple virtual modes. One or more parameters of the preset factory mode may be altered for each of the virtual modes.

Description

PRIORITY CLAIM

[0001] This application claims priority from US Patent Application 63 / 606,560, filed December 5, 2023, the contents of which are incorporated herein in their entirety.VIRTUAL MODES FOR X-RAY DETECTORS

[0002] X-ray detectors (such as Flat Panel Detectors (or FPDs)) may not permit sufficient customization of user modes and parameters for original equipment manufacturers (OEMs) and end users. Application programming interface (API) calls may be used to establish customer-specific modes.BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

[0003] FIG. 1 is a block diagram illustrating a virtual mode mapping application and process that can be used to create a Virtual Mode Map (or VMM) (for example, stored as a VMM file) containing customer-specific user modes and parameters from a single, factory-supplied configuration according to some embodiments.

[0004] FIG. 2 is a flowchart illustrating a method of creating a VMM to be used in an x-ray detector (such as an FPD) to provide customer-specific user modes and parameters according to some embodiments.

[0005] FIG. 3 is a block diagram of an x-ray detector configured to operate by loading a VMM file to control operation modes and parameters of the x-ray detector according to some embodiments.

[0006] FIG. 4 is a flowchart illustrating a method of using a VMM in an x-ray detector to provide customer-specific user modes and parameters according to some embodiments.DETAILED DESCRIPTION

[0007] Some embodiments relate to X-ray flat panel detectors (FPDs) with factory-supplied configurations (for example, configuration or “config” files) that provide operation modes and operation parameters for the FPD. FPDs may be used by original equipment manufacturers(OEMs) in a large number of different medical, industrial, and other devices to provide x-ray scanning and detection capabilities. Because of the many different applications, OEMs require the ability to configure the FPDs used in their equipment in a way that suits their specific needs.

[0008] FIG. 1 is a block diagram illustrating an application 10 and a process of creating a VMM 16 from a factory-supplied configuration 12 according to some embodiments. Referring to FIG. 1, FPDs may be supplied to customers with a single, factory-prepared config file 12. A defect map (not shown) may also be provided that identifies pixel defects in that particular FPD. An application 10, can be provided to the customer that permits them to select one or more operating modes 12A-FF from the config file 12 to use as virtual modes 16A-16FF of the FPD in their device. The config file 12 preferably provides a number of preset operation modes 12A, 12B, 12C, 12D, 12E, 12F, . . ., 12FF that have each been tested and validated by the factory. The parameters under which each of the modes 12A-FF can correctly operate can also be identified in and limited by the config file 12.

[0009] As illustrated in FIG. 1, according to some embodiments, customers (e.g., OEMs or other users) may be provided with the ability to create their own virtual modes for operating and controlling the FPD 300 (see FIG. 3) using the factory-supplied config file 12. An application (app) or other tool 10 may, for instance, be provided to permit the app user to create a Virtual Mode Map (VMM) file 16 that maps desired operating modes 12A-E from the config file 12 to user-selected positions in the VMM file 16. The app 10 can download the config file 12 from the FPD 300, for instance, receive the configuration 12 from the factory, or obtain the configuration 12 in some other manner (such as via the internet).

[0010] In operation, the app 10 can permit the app user to identify and select desired operating modes 12A-E from the config information 12 for inclusion in the VMM 16 at desired index 17 locations (and therefore in a desired order). The app 10 can also permit the user to duplicate desired modes 12C from the config information 12 by selecting them multiple times for inclusion in the VMM 16. The app 10 can further permit the user to omit any undesiredmodes 12F-FF by not selecting them for inclusion in the VMM 16. And the app 10 can further allow the user to modify various different parameters of the virtual operating modes 16A-FF, including, for instance, regions of interest (ROIs), frame rates, shared calibration (gain) maps, shared offset calibration maps, enabled / disabled corrections, internal / external sync, or any other desired parameters or features.

[0011] Once the desired mode selection, mode index mapping, parameter selection, and parameter modification have all been performed in the app 10, the app 10 can save the resulting information as a VMM file 16 that can then be exported to the FPD 300.

[0012] Various benefits can be obtained through use of the app 10. Among other benefits, customers can be permitted to duplicate and modify a factory preset modes multiple times for inclusion in the VMM file 16. As illustrated in FIG. 1, for instance, a 2x2 operating mode 12C may be selected multiple (eg., three) times for inclusion in the VMM file 16, providing the first three virtual modes 16A, 16B, and 16C in the VMM file 16. Each time an operating mode 12A-FF is selected for inclusion in the VMM file 16, allowable parameters (including, for example, an ROI) may be changed to provide virtual operating modes 16A-FF having the specific functions (such as zoom and frame rate, for example) desired by the customer for that specific mode. For example, virtual modes 16A, 16B, and 16C can run the same 2x2 operating mode 12C from the config file 12 at different zoom magnifications and frame rates to provide rapidly accessible preset zoom modes for desired device operations.

[0013] It may be undesirable, however, to permit user modification of some parameters (such as binning, gain, and line timing, for instance), as changes to these parameters may cause attempted operation outside the permitted FPD specifications. Certain parameters may therefore need to be set and locked down in the config file 12 where they can be factory tested and validated to ensure proper functionality of the FPD. The factory config file 12 can be controlled, validated, and updated by the factory to ensure proper operation of all preset modes 12A-FF within the config file 12 as well as any virtual modes 16A-FF based on those preset modes 12A-FF. When updates are needed, they can be supplied to the customer or other uservia an updated config file 12 without affecting the customer’s virtual modes 16A-FF. Furthermore, in this manner, seamless and transparent updates can be provided to all users that supplement some user needs without affecting the functionality of other user’s devices.

[0014] FIG. 2 is a flow diagram illustrating a method of creating a VMM file 16 for providing virtual modes 16A-FF to an FPD 300. Referring additionally to FIG. 2, in some embodiments, an OEM or other user can be provided with an application (app) or other software tool 10 that would read the product config file 12 containing the preset factory modes 12A-FF from the detector 300 (see FIG. 3). Alternatively, the user could be provided with the config file 12 directly {e.g., either through a removable storage media or a downloadable file) to use in the app 10. The app 10 can be configured to run on a computer, a tablet, a smart phone, or any other computing device (not shown). Using the app 10, the user would have the ability to select which modes 12A-FF from any of the preset factory modes 12A-FF to include in its customized VMM file 16 and in what order to arrange the selected modes 16A- FF. A method of creating a virtual mode mapping index 17 and file 16 therefore begins by retrieving a config file 12 either directly from an FPD, from a factory -supplied storage device or web service, or from some other desired source, and then, in step 101, loading the config file 12 into an app (or other software program) 10.

[0015] In step 102, one or more desired modes 12A-FF can be selected from the config file 12 for inclusion as virtual modes 16A-FF. Any of the preset modes 12A-FF may be selected a desired number of times for inclusion as virtual modes 16A-FF. Other modes 12A-FF may be omitted entirely. In step 103, the virtual modes can be arranged in a desired order in which they can later be accessed from the FPD 300. In step 104, parameters of the virtual modes 16A-FF can be modified to provide specific desired functionality to each individual virtual mode 16A-FF. The user can therefore be given the ability to select the same factory preset mode eg., 12C) multiple times while also being given the ability to adjust certain parameters of the factory preset mode 12C in the corresponding virtual modes e.g., 16A-C) before inclusion in the VMM file 16.

[0016] For example, if an OEM requires three separate 2x2 modes which operate at different frame rates, the OEM can select a preset factory 2x2 mode 12C multiple times for inclusion in the VMM file 16. For each virtual 2x2 mode 16A-C included in the VMM file, the OEM would have the ability to adjust various operating parameters for that mode, including the ROI, frame rate, shared calibration maps, etc. The OEM can thereby, for instance, create different quick access zoom modes based off of their specific application needs. Using this VMM file 16 creation application 10, the user is therefore able to configure the ROI (or other parameters) of any of the preset factory modes 12A-FF by adding the reduced ROI mode (or other modified mode) to the virtual mode index 17 contained in the VMM file 16.

[0017] The application 10 could also allow for virtual modes 16A-FF to share offset maps or gain maps. Shared gain maps, for example, could be useful when the user selects the same factory preset mode 12C for inclusion multiple times in the VMM file 16 (such as when operating the same mode at multiple frame rates and / or magnifications). Because all of these virtual modes 16A-C are derived from the same preset factory mode 12C settings, the gain map could be shared between each of these virtual modes 16A-C. This permits the user to perform a gain calibration in just one of the virtual modes 16A-C and then share that calibration with each of the other virtual modes 16A-C coming from the same factory preset mode 12C. The map may also be shared with the preset mode 12C itself. This can save valuable time during the FPD setup and calibration processes. Similarly, when the virtual modes 16A-C share a factory preset mode 12C, offset modes can be shared. Performing an offset calibration in one of the virtual modes 16A-C could update the offset for all of the virtual modes 16A-C sharing the same factory preset mode 12C, as well as for the factory preset mode 12C itself.

[0018] Once the desired modes 12A-FF from the config file 12 have been selected, arranged, and modified, the resulting virtual mode mapping index 17 is saved as part of a VMM file 16 to be exported to the FPD 300. The VMM file 16 can further include revision and tracking information and the application 10 can allow the user to input and retrieve the tracking and revision information from the VMM file 16 so the user can have the ability toidentify and distinguish the VMM file 16 from other VMM files 16. The user can also have the ability to load and edit VMM files 16 through the app 10.

[0019] In some embodiments, up to thirty-two modes 12A-FF may be provided in an index 13 of the factory config file 12. Likewise, up to thirty-two (32) virtual modes can be enabled, and an index 17 of between 0-31 could be used in the VMM file 16, with the OEM given the ability to select where each of the desired factory preset modes 12A-FF appear as a virtual mode 16A-FF in that index 17. Of course, more than thirty-two (32) modes may be provided for in some embodiments, but including additional modes may affect memory or other hardware requirements as well as the time it takes to load and switch between modes.

[0020] Once the VMM file 16 has been created and output to the FPD 300, the detector 300 would have the ability to read and use this file 16. FIG. 3 is a schematic block diagram of an FPD 300 according to some embodiments. Referring additionally to FIG. 3, an FPD 300 includes a memory 302 that stores the factory supplied config file 12 and the user-created VMM file 16. A boot-up module 304 includes a boot-up program that sets up the appropriate modes during start-up of the FPD 300. Specifically, the FPD 300 can be configured to detect and read the VMM file 16 upon boot-up to determine whether there are any user-configured virtual modes 16A-FF that should be used in place of the factory-supplied default config modes 12A-FF. If no VMM file 16 is found in the detector memory 302, the standard, factory- supplied configuration modes 12A-FF from the config file 12 can be used. If a VMM file 16 exists, however, only the virtual modes 16A-FF are loaded into the detector’s operational software 306 during the setup operation and not the original configuration modes 12A-FF. This can save valuable start-up time by only loading the user-desired and selected modes into the FPD 300 for use. The operating software 306 is provided to operate the detector 300 based on the modes and parameters loaded during the start-up operation.

[0021] FIG. 4 provides a schematic flow diagram illustrating a method of using a VMM file 16 in an x-ray detector 300 to provide customer-specific user modes 16A-FF and their associated parameters to the detector 300 according to some embodiments. Referringadditionally to FIG. 4, when the detector 300 boots, beginning with step 401, boot-up software in the detector 300 detects the presence of a VMM file 16, in step 402. If a VMM file 16 is determined to be present in memory 302 during step 403, the FPD 300 then loads the virtual modes 16A-FF for activation according to the index and other instructions in the VMM file 16 in step 404. Specifically, when loading the virtual modes 16A-FF, the detector 300 takes note of any ROI and frame rate changes along with calibration and offset map sharing defined in the VMM file 16. If no VMM file 16 is detected by the FPD 300, then, in step 405, the detector software will load and activate the preset factory modes 12A-FF (from the product config file 12). It is therefore not necessary for a customer to setup a VMM file 16 in advance. If desired, they could use the detector 300 with just the preset factory modes 12A-FF in the order set out in the product config file 12.

[0022] The following features could be added to a detector 300 Software Development Kit (SDK) to allow virtual modes to operate through the boot-up module 304 and operating software 306 in the detector 300: (1) Allowing the application 10 to transmit the VMM file 16 to the detector 300; (2) Allowing the application 10 to retrieve the config file 12 and VMM file 16 from the detector 300; (3) The ability to configure the virtual modes 16A-FF in the detector 300 to share offset maps with the inherited factory mode 12A-FF or other virtual modes 16A- FF; (4) The ability to configure the virtual modes 16A-FF to share gain maps with the inherited factory mode 12A-FF or other virtual modes 16A-FF in the detector 300; (5) The ability for virtual modes 16A-FF to inherit a base defect map from the corresponding factory mode 12A- FF in the detector 300; (6) Loading the factory preset product config file 12 into the detector 300 if no VMM file 16 is detected; and (7) Allowing the application 10 to detect the VMM version string from the VMM file 16 in the detector 300, thereby allowing the user to check file version and revision information of the VMM file 16 being used by the detector 300.

[0023] According to some embodiments, a method of creating a Virtual Mode Map (VMM) file 16 that can be used by an x-ray detector 300 to define operating modes and parameters for operating the operating modes of the x-ray detector comprises identifying possible operatingmodes 12A-FF from a factory-supplied config file 12; selecting one or more operating modes 12A-FF from the possible operating modes for inclusion as virtual modes 16A-FF in the VMM file 16; and outputting the VMM file 16.

[0024] According to some embodiments, the method may comprise selecting one or more parameters for operating the virtual modes 16A-FF; and modifying the selected parameters for operating the virtual modes 16A-FF before outputting the VMM file 16.

[0025] According to some embodiments, the method may comprise selecting a position for the virtual mode 16A-FF within an index 17 of the VMM file 16.

[0026] According to some embodiments, selecting one or more operating modes 16A-FF may comprise selecting one of the possible operating modes 12A-FF for inclusion multiple times as multiple different duplicated virtual modes 16A-FF in the VMM file 16.

[0027] According to some embodiments, parameters for operating the duplicated virtual modes 16A-C can be modified to distinguish each of the duplicated virtual modes 16A-C from the other duplicated virtual modes 16A-C.

[0028] According to some embodiments, at least one of the possible operating modes 12A- FF is not selected for inclusion as a virtual mode 16A-FF in the VMM file 16.

[0029] According to some embodiments, the method may include obtaining the factory- supplied config file 12 from the x-ray detector 300 before identifying possible operating modes 12A-FF.

[0030] According to some embodiments, outputting the VMM file 16 comprises outputting the VMM file 16 to the x-ray detector 300.

[0031] According to some embodiments, version information (such as a file string) can be included in the VMM file 16 that can be read by the x-ray detector 300.

[0032] According to some embodiments, the one or more parameters can include one or more of a region of interest, a frame rate, a calibration map sharing, an offset map sharing, and an internal / external sync.

[0033] According to some embodiments, an x-ray detector 300 comprises a memory 302 capable of storing a config file 12 and a Virtual Mode Map (VMM) file 16; a boot-up program 304 configured to detect the presence or absence of a VMM file 16 in the memory 302; wherein the boot-up program 304 is configured to load virtual modes 16A-FF from the VMM file 16 into the detector 300 to configure the operating modes and parameters of the detector 300 when the VMM file 16 is present in the memory 302; and wherein the boot-up program 304 is configured to load factory preset modes 12A-FF from the config file 12 into the detector 300 to configure the operating modes and parameters of the detector 300 when no VMM file 16 is present in the memory 302.

[0034] According to some embodiments, the x-ray detector 300 includes software 306 configured to detect and provide version information from the VMM file 16 when requested by a user.

[0035] According to some embodiments, the x-ray detector 300 comprises software 306 configured to share one or more gain calibration or offset maps between two or more virtual modes 16A-FF and between a virtual mode 16A-FF and a preset factory mode 12A-FF when instructed to do so by information contained in the VMM file 16.

[0036] According to some embodiments, the x-ray detector 300 comprises software 304 configured to provide a base defect map from a factory preset mode 12A-FF in the config file 12 to a corresponding virtual mode 16A-FF in the VMM file 16.

[0037] According to some embodiments, the x-ray detector 300 comprises software 306 configured to provide the config file 12 from the detector memory 302 to an application 10 when requested by a user.

[0038] According to some embodiments, a method of operating an x-ray detector 300 includes initiating a boot-up sequence when the x-ray detector 300 is powered-up; detecting whether a Virtual Mode Map (VMM) file 16 comprising one or more virtual modes 16A-FF derived from one or more factory preset modes 12A-FF is present in a memory 302 of the x- ray detector 300; and loading the one or more virtual modes 16A-FF from the VMM file 16into the x-ray detector 300 to operate the x-ray detector 300 when the VMM file 16 is present in the detector memory 302.

[0039] According to some embodiments, the method includes loading factory preset modes 12A-FF from a config file 12 containing a plurality of factory preset modes 12A-FF into the x- ray detector 300 to operate the x-ray detector 300 when no VMM file 16 is detected in the memory 302 of the x-ray detector 300.

[0040] According to some embodiments, the method includes providing VMM file version information to a user upon request when the VMM file 16 is present in the x-ray detector 300 memory 302.

[0041] According to some embodiments, the method includes providing the config file 12 to a user to permit creation of a VMM file 16.

[0042] According to some embodiments, the method includes providing a defect map from a factory preset mode 12A-FF to a corresponding virtual mode 16A-FF.

[0043] According to some embodiments, a method of creating a Virtual Mode Map (VMM) for 16 an x-ray detector 300 to define operating modes and parameters of the x-ray detector 300, includes identifying a predetermined operating mode of the x-ray detector from a factory- supplied configuration 12 and selecting the predetermined operating mode 12A-FF for operating the x-ray detector 300 for inclusion as a virtual mode 16A-FF in the VMM.

[0044] According to some embodiments, the method can further include selecting one or more parameters, the parameter at least partially responsible for operating the x-ray detector, for operating the virtual mode 16A-FF and modifying the selected parameters for operating the virtual mode 16A-FF for inclusion in the VMM 16.

[0045] According to some embodiments, the one or more parameters include one or more of a region of interest, a frame rate, a calibration map sharing, an offset calibration map sharing, enabled / disabled corrections, and an internal / external sync.

[0046] According to some embodiments, the method can include selecting a position for the virtual mode 16A-FF within an index of the VMM 16.

[0047] According to some embodiments, selecting the predetermined operating mode 12A-FF comprises including the predetermined operating mode 12A-FF multiple times as multiple different duplicated virtual modes 16A-FF in the VMM 16.

[0048] According to some embodiments, parameters for operating the duplicated virtual modes 16A-FF are modified to distinguish each of the duplicated virtual modes 16A-FF from the other duplicated virtual modes 16A-FF.

[0049] According to some embodiments, identifying a predetermined operating mode 12A-FF comprises identifying a plurality of predetermined operating modes 12A-FF and wherein at least one of the predetermined operating modes 12A-FF is not selected for inclusion as a virtual mode 16A-FF in the VMM 16.

[0050] According to some embodiments, the method further includes obtaining the factory-supplied configuration 12 from the x-ray detector 300 before identifying the predetermined operating mode 12A-FF.

[0051] According to some embodiments, the method further includes outputting the VMM 16 to the x-ray detector 300.

[0052] According to some embodiments, the method further comprises including version information in the VMM 16 that can be read by the x-ray detector 300 and provided to a user.

[0053] According to some embodiments, an x-ray detector 300 comprises a memory 302 capable of storing a config file 12 and a Virtual Mode Map (VMM) file 16 and a program configured to detect the presence or absence of the VMM file 16 in the memory 302. The program is configured to load virtual modes from 16A-FF the VMM file 16 into the x-ray detector 300 to configure the operating modes and parameters of the x-ray detector 300 when the VMM file 16 is present in the memory 302. The program is configured to load factory preset modes 12A-FF from the config file 12 into the x-ray detector 300 to configure the operating modes and parameters of the x-ray detector 300 when no VMM file 12 is present in the memory.

[0054] According to some embodiments, the x-ray detector 300 further includes software configured to detect and provide version information from the VMM file 16 when requested by a user.

[0055] According to some embodiments, the x-ray detector further comprises software configured to share one or more gain calibration or offset maps between two or more virtual modes 16A-FF and between a virtual mode 16A-FF and a preset factory mode 12A-FF when instructed to do so by the VMM file 16.

[0056] According to some embodiments, the x-ray detector includes software configured to provide a base defect map from a factory preset mode 16A-FF in the config file 12 to a corresponding virtual mode 16A-FF in the VMM file 16.

[0057] According to some embodiments, the x-ray detector further includes software configured to provide the config file 12 from the memory 302 to an application 10 when requested by a user.

[0058] According to some embodiments, a method of operating an x-ray detector 300 includes detecting whether a Virtual Mode Map (VMM) 16 comprising one or more virtual modes 16A-FF derived from one or more factory preset modes 12A-FF is present in a memory 302 of the x-ray detector 300; and loading the one or more virtual modes 16A-FF from the VMM 16 into the x-ray detector 300 to operate the x-ray detector 300 when the VMM 16 is present in the detector memory 302.

[0059] According to some embodiments, the method further includes loading one or more factory preset modes 12A-FF from a configuration 12 containing one or more factory preset modes 12A-FF into the x-ray detector 300 to operate the x-ray detector 300 when no VMM 16 is detected in the memory 302 of the x-ray detector 300.

[0060] According to some embodiments, the method can include providing VMM version information to a user upon request when the VMM 16 is present in the x-ray detector memory 302.

[0061] According to some embodiments, the method includes providing the factory- supplied configuration 12 to a user to permit creation of the VMM 16.

[0062] According to some embodiments, the method includes providing a defect map from the factory preset modes 12A-FF to corresponding virtual modes 16A-FF.

[0063] Although the structures, devices, methods, and systems have been described in accordance with particular embodiments, one of ordinary skill in the art will readily recognize that many variations to the particular embodiments are possible, and any variations should therefore be considered to be within the spirit and scope disclosed herein. Accordingly, many modifications may be made by one of ordinary skill in the art without departing from the spirit and scope of the appended claims.

[0064] The claims following this written disclosure are hereby expressly incorporated into the present written disclosure, with each claim standing on its own as a separate embodiment. This disclosure includes all permutations of the independent claims with their dependent claims. Moreover, additional embodiments capable of derivation from the independent and dependent claims that follow are also expressly incorporated into the present written description. These additional embodiments are determined by replacing the dependency of a given dependent claim with the phrase “any of the claims beginning with claim [x] and ending with the claim that immediately precedes this one,” where the bracketed term “[x]” is replaced with the number of the most recently recited independent claim. For example, for the first claim set that begins with independent claim 1, claim 4 can depend from either of claims 1 and 3, with these separate dependencies yielding two distinct embodiments; claim 5 can depend from any one of claims 1, 3, or 4, with these separate dependencies yielding three distinct embodiments; claim 6 can depend from any one of claims 1, 3, 4, or 5, with these separate dependencies yielding four distinct embodiments; and so on.

[0065] Recitation in the claims of the term “first” with respect to a feature or element does not necessarily imply the existence of a second or additional such feature or element. Elements specifically recited in means-plus-function format, if any, are intended to beconstrued to cover the corresponding structure, material, or acts described herein and equivalents thereof in accordance with 35 U.S.C. § 112(f). Embodiments of the invention in which an exclusive property or privilege is claimed are defined as follows.

Claims

CLAIMS1. A method of creating a Virtual Mode Map (VMM) for an x-ray detector to define operating modes and parameters of the x-ray detector, the method comprising: identifying a predetermined operating mode of the x-ray detector from a factory- supplied configuration; and selecting the predetermined operating mode for operating the x-ray detector for inclusion as a virtual mode in the VMM.

2. The method of claim 1, further comprising: selecting one or more parameters for operating the virtual mode, the parameter at least partially responsible for operating the x-ray detector; and modifying the selected parameters for operating the virtual mode for inclusion in the VMM.

3. The method of claim 2, wherein: the one or more parameters include one or more of a region of interest, a frame rate, a calibration map sharing, an offset calibration map sharing, enabled / disabled corrections, and an internal / external sync.

4. The method of claim 1, further comprising: selecting a position for the virtual mode within an index of the VMM.

5. The method of claim 1, wherein: selecting the predetermined operating mode comprises including the predetermined operating mode multiple times as multiple different duplicated virtual modes in the VMM.

6. The method of claim 4, wherein parameters for operating the duplicated virtual modes are modified to distinguish each of the duplicated virtual modes from the other duplicated virtual modes.

7. The method of claim 1, wherein: identifying a predetermined operating mode comprises identifying a plurality of predetermined operating modes and wherein at least one of the predetermined operating modes is not selected for inclusion as a virtual mode in the VMM.

8. The method of claim 1, further comprising obtaining the factory-supplied configuration from the x-ray detector before identifying the predetermined operating mode.

9. The method of claim 1, further comprising: outputting the VMM to the x-ray detector.

10. The method of claim 1, further comprising: including version information in the VMM that can be read by the x-ray detector and provided to a user.

11. An x-ray detector comprising: a memory capable of storing a config file and a Virtual Mode Map (VMM) file; a program configured to detect the presence or absence of the VMM file in the memory; wherein the program is configured to load virtual modes from the VMM file into the x-ray detector to configure the operating modes and parameters of the x-ray detector when the VMM file is present in the memory; andwherein the program is configured to load factory preset modes from the config file into the x-ray detector to configure the operating modes and parameters of the x-ray detector when no VMM file is present in the memory.

12. The x-ray detector of claim 11, further comprising software configured to detect and provide version information from the VMM file when requested by a user.

13. The x-ray detector of claim 11, further comprising software configured to share one or more gain calibration or offset maps between two or more virtual modes and between a virtual mode and a preset factory mode when instructed to do so by the VMM file.

14. The x-ray detector of claim 11, further comprising software configured to provide a base defect map from a factory preset mode in the config file to a corresponding virtual mode in the VMM file.

15. The x-ray detector of claim 11, further comprising software configured to provide the config file from the memory to an application when requested by a user.

16. A method of operating an x-ray detector, said method comprising: detecting whether a Virtual Mode Map (VMM) comprising one or more virtual modes derived from one or more factory preset modes is present in a memory of the x-ray detector; and loading the one or more virtual modes from the VMM into the x-ray detector to operate the x-ray detector when the VMM is present in the detector memory.

17. The method of claim 16, further comprising: loading one or more factory preset modes from a configuration containing one or more of factory preset modes into the x-ray detector to operate the x-ray detector when no VMM is detected in the memory of the x-ray detector.

18. The method of claim 17, further comprising: providing VMM version information to a user upon request when the VMM is present in the x-ray detector memory.

19. The method of claim 17, further comprising: providing the factory-supplied configuration to a user to permit creation of the VMM.

20. The method of claim 16, further comprising: providing a defect map from the factory preset modes to corresponding virtual modes.

Images