(window.slotbydup=window.slotbydup || []).push({
id: '2014386',
container: s,
size: '234,60',
display: 'inlay-fix'
&&|&&0次下载&&|&&总30页&&|
您的计算机尚未安装Flash，点击安装&
如需下载到电脑，请使用积分（）
0人评价30页
0人评价30页
0人评价30页
0人评价4页
0人评价3页
所需积分：（友情提示：所有文档均可免费全文预览！下载之前请务必先预览阅读，以免误下载造成积分浪费！）
（多个标签用逗号分隔）
文不对题，内容与标题介绍不符
广告内容或内容过于简单
文档乱码或无法正常显示
若此文档涉嫌侵害了您的权利，请参照说明。
评价文档：CPC中文印刷社区 - 查看单个帖子 - Trendsetter 3244
Error Messages
查看单个帖子
永久封禁会员
等级: 五袋长老
会员ID：5146
注册: , 20:58
23个帖子获得51次感谢
警告次数: 2
警告等级: 7
Trendsetter 3244
Error Messages
Trendsetter 3244
Error Messages
See also Search Form
This content is generated by scripts that pull information directly from Firmware Engineering's support site. The scripts were last run: 31 Jan :02
Number Error Message
MISC: Reserved
MISC: Reserved
MISC: Reserved
MISC: Reserved
MISC: Reserved
MISC: Reserved
MISC: Reserved
MISC: Specified test is not defined
MISC: Workstation communications lost
MISC: Requested command is not defined
MISC: MPE Code checksum is faulty
MISC: LCA module checksum is faulty
MISC: LCA module incompatable format
MISC: Module not found in version list
MISC: Firmware module checksum is faulty
MISC: Error opening firmware module
MISC: Invalid or unneeded code bundled with firmware
MISC: Missing required code in the firmware bundle
MISC: Product version not found in version list
MISC: Invalid version of overwriting pattern
MISC: Code bank selected for loadingis current code bank
MISC: Flash memory program failed
MISC: Address &hex address& out of memory bank range
MISC: Unsupported memory type detected
MISC: Flash memory erase failed
MISC: Temperature log: Engine = &Celcius x 10& Leadscrew = &Celcius x 10&
MISC: Password not set!
MISC: NVS modified and saved, but not backed up!
MISC: Dongle not responding
MISC: Config: %s %s owner %s
RESET: cause unknown
RESET: induced by test submodule
RESET: induced by RESET opcode, possible warm reset requested at monitor
RESET: induced by loss of clock
RESET: induced by halt monitor
RESET: induced by software watchdog, possible cold reset requested at monitor
NVS: checksum error in &NVS subsystem& calibration block
NVS: checksum error in &NVS subsystem& configuration block
NVS: checksum error in mode &number& table
NVS: low battery in NVS detected
NVS: NVS automatically upgraded to version 2
NVS: subscan size nvs config parameter is invalid
WSCOMM: All faults cleared
WSCOMM: Invalid command letter
WSCOMM: Parameter syntax error
WSCOMM: Defined WS command is currently unsupported
WSCOMM: Character pacing timeout, WS transmitting too slowly
WSCOMM: too many characters in command string
WSCOMM: Could not open serial communications interface for workstation
WSCOMM: Resume or clear received when not suspended
WSCOMM: Command received for idle image ID
WSCOMM: Specified image ID is already active
WSCOMM: Maximum active image commands surpassed
WSCOMM: Resolution specified is not available
WSCOMM: Already aborting
WSCOMM: Abort received when no command active
WSCOMM: Already imaging
WSCOMM: Recorder is flushing, can't accept new commands
WSCOMM: Door is open
WSCOMM: Door is closed
WSCOMM: ABORT switch on
WSCOMM: ABORT switch off
WSCOMM: Operation aborted at recorder - check that abort switch is released
WSCOMM: Operation aborted by workstation
WSCOMM: ABORT complete
WSCOMM: Abort request not heeded within timeout, possible hung subsystem
WSCOMM: Task(s) &task codes& did not finish initializing on time
WSCOMM: Operation preempted
WSCOMM: Cassette bay door open
WSCOMM: Cassette bay door closed
WSCOMM: Resolution does not exist
WSCOMM: Image too wide for plate
WSCOMM: Workstation software error - Invalid packet number
WSCOMM: Workstation software error - Invalid total packets number
WSCOMM: Workstation software error - Out of sequence packet received
WSCOMM: Workstation software error - Invalid packet length
WSCOMM: Workstation software error - Invalid Media Imaging Mode ID (MIMID)
WSCOMM: Packet fails CRC check
WSCOMM: Total packet data exceeding firmware buffer capacity
MSG: Command parameter error
MSG: Parameter is out of range
MSG: Defined command is currently unsupported
MSG: Requested test pattern not defined
MSG: &subsystem& is already reserved
MSG: Reserved message in message pool
MSG: Task releasing message owned by another task
MSG: Task releasing unreserved message
MSG: Task sending message owned by another task
MSG: Task sending unreserved message
MSG: Task received message that was not sent
MSG: Reserved string in string pool
MSG: Task releasing unreserved string
MSG: Task releasing string owned by another task
MSG: Task reserving released string
MSG: &task name& timed out while waiting for command &hex command code&
MSG: &task name& received an invalid command (command = &hex command code&)
MSG: Wrong number of parameters
MSG: Inactive list sent
MSG: Unexpected list type sent
MSG: Invalid list entry number sent - Possible version incompatabilities
MSG: Plot mode not specified before plot parameters
MSG: Task received msg with unexpected id (code = %X)
MSG: suspended - waiting for Resume or Clear
MSG: plate thickness too large
MSG: one or both plate dimensions too large
MSG: media type out of range
MSG: one or both plate dimensions too small
MSG: media %d not supported
DRUM: Timeout on drum operation
DRUM: Illegal command state machine state
DRUM: Timeout waiting for drum move
DRUM: Received invalid command
DRUM: drum not initialized - can't execute that command
DRUM: Unexpected status returned from function
DRUM: Timeout during active braking
DRUM: Timeout on velocity settling
DRUM: Timeout on velocity acceleration
DRUM: Sample interrupt failure
DRUM: Servo amp fault
DRUM: Cable from motherboard to drum servo amp not detected
DRUM: Index not detected
DRUM: Extra Tach A pulse detected
DRUM: Missing Tach A pulse
DRUM: Extra Tach B pulse detected
DRUM: Missing Tach B pulse
DRUM: Drive direction incorrect - check motor wiring
DRUM: Tach encoder cable not detected
DRUM: Aborted
DRUM: Timeout on hold
DRUM: Motor current exceeded limit
DRUM: Velocity error - drum rotation blocked or PID gain settings wrong
DRUM: Position error is greater than 1000 ticks
DRUM: Hall velocity error - drum rotation blocked or PID gain settings wrong
DRUM: Timeout waiting for TPU hall sensor PW measurement
DRUM: Plate not loaded correctly on drum, obstruction detected below LEC actuator
DRUM: ALE actuators on drum
DRUM: Hall mode overspeed error - possible TPU failure
DRUM: Drum hall velocity does not match encoder velocity to within tolerance.
DRUM: Drum is spinning.
DRUM: Index detected prematurely - clean encoder disc or re-align encoder
DRUM: Drum won't settle with zero torque applied - requires drum cal
DRUM: Drum Position error during Velocity mode, (check acceleration setting)
DRUM: Drum velocity greater than xx rpm in Position mode, possible runaway
DRUM: LCA tick counter annomaly, premature index or spurious counter reset
DRUM: Drum Position error during Velocity mode, (extra index possible cause, check monitor values)
DRUM: Encoder counted extra ticks
DRUM: Index occurred at xx, more than 3 ticks before normal ticks per rotation
DRUM: Hall velocity error - more than 20 percent during drum init.
CARRIAGE: Limit switches reporting carriage is both HOME and AWAY
CARRIAGE: stuck in HOME position
CARRIAGE: stuck in AWAY position
CARRIAGE: unexpectedly arrived at HOME position
CARRIAGE: unexpectedly arrived at AWAY position - image size may have been too large
CARRIAGE: operation timed out
CARRIAGE: timed out while waiting for LCA position
CARRIAGE: position register not accurate
CARRIAGE: LCA's not configured at startup
CARRIAGE: ALE not taken out of reset
CARRIAGE: Unexpected error: 0x%x
CARRIAGE: could not find edge of platecheck that plate size is entered correctly
CARRIAGE: did not reach target speed
CARRIAGE: step synth position register reserved
CARRIAGE: Head Stage is at it's away position, unsafe to move carriage
CARRIAGE: ALE board timed out during carriage position read
CARRIAGE: Carriage state error. Current state: &description&, jog_count = &n& JOG = &number& PLOT = &number&
CARRIAGE: Carriage illegal dest. Current %lu, Dest %lu Stop Dist %lu
CARRIAGE: Specified Speed exceeds maximum of %lu
CARRIAGE: Carriage control board error: cable not detected or undervoltage
CARRIAGE: Carriage control board error: over current
CARRIAGE: Carriage control board error: over temperature
PROC: Processor not present or turned off
PROC: Processor is not ready
PROC: Processor fault requires immediate attn.
PROC: Processor warning will need attention
PROC: Processor type unknown
PROC: Illegal processor number used
HARDWARE: Carriage limit switch
HARDWARE: ALE is not plugged in
HARDWARE: DPE is not plugged in
HARDWARE: MPE LCA's not configured at startup
HARDWARE: DPE will not initialize, may be stuck in reset
HARDWARE: DPE LCA's not configured at startup
HARDWARE: Incorrect DPE version installed
HARDWARE: RAM DAC Incrementing Address Test fail - Address = &fault address&, Write data = &hex data&, Readdata = &hex data&
HARDWARE: DPE failure - dpath control write = &hex data&, read = &hex data&
HARDWARE: External Debris Blower Filters Not Present
HARDWARE: External Debris Blower Filters Full
HARDWARE: External Debris Blower Filters Almost Full (Vacuum Level %d is below %d)
HARDWARE: External Debris Blower System Blocked (Vacuum Level %d is above %d)
HARDWARE: External Debris Blower Not Connected or Filters Full (Vacuum Level %d is below %d)
HARDWARE: DBlower Filter Fault.
CABLE: HA-BP cbl, Carriage Home/Away
CABLE: EH-BP: Exposure Head - Backplane
CABLE: TE-BP: Tach Encoder - Backplane
CABLE: MD-BP: Drum Motor - Backplane
CABLE: Chiller/Blower sensor cbl.
CABLE: SPR-BP
CABLE: Operator Interface not connected
CABLE: Pushbutton not connected
CABLE: CD-D-BP: Carriage Drive Digital
CABLE: CD-A-BP: Carriage Drive Analog
CABLE: CM-CDB: Carriage Drive to Motor
CABLE: Sensors not connected (J7)
CABLE: Air Valves not connected (J20)
CABLE: LR plate sensor not connected (J3)
CABLE: Fly-off cable not connected (J2)
CABLE: Temp Sensors not connected (J13)
POWER: ALE +12V
POWER: ALE -12V
POWER: Carriage power
POWER: Carriage Amp Fault
POWER: Exposure Head power
POWER: Drum Amp Fault
POWER: TEE +24V
EHBOOT: internal message timeout
EHBOOT: datalink terminated the program sequence prematurely
EHBOOT: format error detected during data transfer
EHBOOT: sumcheck error detected during data transfer
EHBOOT: datalink programming sequence taking too long
EHBOOT: LOADER echo mismatch during bootstrap sequence
EHBOOT: LOADER not echoed during bootstrap sequence
EHBOOT: no break detected after forcing head into bootstrap mode
EHBOOT: cannot perform requested operation, no LOADER present
EHBOOT: LOADER prompt for next primitive did not arrive
EHBOOT: communications error
EHBOOT: failed to program location &hex data& with data &hex data&
EHBOOT: failed to erase device, stopped at location &hex data&
EHBOOT: failed to respond to programming command
EHBOOT: Timeout on byte &byte #& while waiting for exposure head to complete response string
EHBOOT: ENQ expected and not received
EHBOOT: ACK expected and not received
EHBOOT: incorrect response length
EHBOOT: incorrect version length
EHBOOT: incorrect version response in byte &byte #&
EHBOOT: incorrect response address
EHBOOT: incorrect response data
SAT: Satellite error cleared
SAT: Unknown Satellite Output Register: &hex number&
SAT: Satellite SW corrupted Buffer
SAT: Buffer Restore error during Output Command
SAT: QSPI error during configuration
SAT: Timeout during SPI enable
SAT: Timeout during QSPI disable
SAT: Timeout during SPI execution
SAT: SPI Mode Fault error
SAT: QSPI Update Watchdog timeout
SAT: &Satellite Board& Error: &Output Name&
SAT: Error Detection Error: Address &address&, Bit = &bit number&
SAT: Temperature Filter Error: Out of range
SAT: LUE Analog testpoint exceeded allowed maximum
SAT: LUE Analog testpoint exceeded allowed minimum
SAT: Engine Frame temperature out of range
SAT: Engine Leadscrew temperature out of range
SAT: Spare sensor 0 temperature out of range
SAT: Spare sensor 1 temperature out of range
SAT: Timeout waiting for conveyor roller speed to update
SAT: Timeout waiting for conveyor belt speed to update
SAT: Cassette Bay &bay number& invalid, autoloader currently configured for &max& bays
SAT: Cassette Bay &bay number& Error: &device&
SAT: PPE Analog testpoint exceeded allowed maximum
SAT: PPE Analog testpoint exceeded allowed minimum
SAT: Software error: invalid lamp state %d in sat_set_lamp_state()
SAT: Software error: invalid image task state %d in sat_update_lamps()
ALE: Autoloader is not initialized, possibly due to an opened door
ALE: plate loaded incorrectly, remove plate from drum
ALE: move clamps to park position, then select RESUME
ALE: remove plate from drum
ALE: remove plate partially on drum
ALE: trailing edge clamp status conflict, setting te state flag to&0|1&. ( &1& indicates &on drum&, &0& indicates &on tec backbone& )
ALE: trailing edge clamps failed to unlock
ALE: trailing edge clamps failed to lock
ALE: trailing edge clamps not on actuator
ALE: trailing edge clamps already on actuator, possible sensor or software error.
ALE: no plate on drum
ALE: timeout moving leading edge cylinder
ALE: timeout moving trailing edge cylinder
ALE: timeout moving roller cylinder
ALE: roller on drum
ALE: leading-edge actuator on drum
ALE: trailing-edge actuator on drum
ALE: timeout waiting for load button to be pressed
ALE: plate not detected on load ramp
ALE: plate larger than expected
ALE: plate smaller than expected
ALE: remove plate detected on load ramp
ALE: load ramp is tilted into drum no-fly zone
ALE: Please load plate
ALE: Please unload plate
IMAGE: update received after load started
IMAGE: task received incorrect ID
IMAGE: Inactive image task received image update
IMAGE: Total mainscan shift less than or equal to zero
IMAGE: Total subscan shift less than zero
IMAGE: Total mainscan shift too large
IMAGE: PLL is not able to track drum motion
IMAGE: PLL was not able to maintain drum motion tracking
IMAGE: Specified \&around drum\& image size too large
IMAGE: exposure too low
IMAGE: mainscan length must be a multiple of 16
IMAGE: command received when already suspended
IMAGE: plate exposed by open door
IMAGE: Stroke must be flat when calibrating scorr
IMAGE: Scorr must be initialized in current mode before calibrating
IMAGE: TPG not idle after imaging, DPE reset
IMAGE: Series plot completed
IMAGE: Series strip width is set to zero
IMAGE: Total number of retraces: &retraces&
IMAGE: DPE orthog slope less than 0, check plate rotation
IMAGE: DPE orthog slope larger than max, check plate rotation
IMAGE: Attempt to image B-side before A-side
IMAGE: Plate imaging has begun
IMAGE: Unable to initialize plot for mode set to 0 DPI
IMAGE: Negative media (inverted data) requires FDPE
HEAD: No mailbox defined for datalink task
HEAD: Error while sending to datalink mailbox
HEAD: Datalink synchronization lost
HEAD: Datalink failed while retrying send
HEAD: Datalink in programming mode, command not valid
HEAD: Datalink already in programming mode
HEAD: Datalink timed out waiting for break
HEAD: fault code = &hex data&, status byte = &hex data&
HEAD: command timed out
HEAD: task received unexpected head message &mailbox&, message code &msgtype&h
HEAD: command acknowledge fault = &hex number&
HEAD: couldn't find plate edge due to dirty edge strip on drum
HEAD: won't come online
HEAD: did not signal end of initialization
HEAD: is not responding
HEAD: break detected, exposure head has reset
HEAD: multiple edges detected - verify image position
HEAD: temperature out of range
HEAD: value out of range
HEAD: missing laser on parameters
HEAD: attempted write blocked
HEAD: failure to write to memory
HEAD: unsupported message
HEAD: message length incorrect
HEAD: invalid control message
HEAD: operation was aborted
HEAD: no more room in mailbox
HEAD: ran out of buffers
HEAD: all retries failed on chnl 0
HEAD: all retries failed on chnl 1
HEAD: sync lost on chnl 0
HEAD: sync lost on chnl 1
HEAD: CONFIG register incorrect
HEAD: flash memory checksum error
HEAD: LCA won't init for reprogram
HEAD: LCA won't admit being loaded
HEAD: SRAM memory check failure
HEAD: software error
HEAD: LCA config unavailable
HEAD: Light level too low for Beam Pointing
HEAD: Timeout waiting for LASER OK
HEAD: Light valve high voltage fault
HEAD: LV Positive 12V fault (bipolar)
LASER: Cannot continue, laser is not ready
PDB: Air Supply Below Threshold
SCSI: SCSI bus reset while imaging
SCSI: SCSI parity error while imaging, check plate for artifacts
SCSI: SCSI driver error, invalid initiator
SCSI: SCSI Driver Error, line &line number&
SCSI: SCSI asynchronous transfer requested, line &line number&
SCSI: timed out waiting for SCSI complete
TPG: memory overflow
TPG: too many scans
TPG: write to closed scan
TPG: write to unopened scan
TPG: write to undefined scan
TPG: close of closed scan
TPG: close of unopen scan
TPG: open of NULL scan
TPG: Undefined pattern number, use &list pattern&
TPG: Call with NULL pattern struct
TPG: Pattern write call error
TPG: Too many cells in pattern
TPG: timed out waiting for stripe to complete
LCA: DONE signal stuck low while programming
LCA: READY signal stuck low while programming
LCA: did not accept programming data
LCA: INIT signal stuck low while programming
LCA: INIT signal stuck high while programming
LCA: Required LCA file is not in firmware
LCA: Required LCA master file is not in firmware
LCA: Length of LCA diff file does not match master
SW: Ink Key buffers out of synch
SW: Image shutdown error
SW: NCO update timeout
SW: Resolution mode not defined
SW: Unknown ID code in firmware directory
SW: undefined subsystem in NVS list
SW: Could not open console interface for serial communications
SW: Could not open head interface for serial communications
SW: Could not open laser interface for serial communications
SW: Out of memory
SW: WS data list unexpectedly in use
SW: WS command pattern incorrect
SW: AL Sched: pick sync error
SW: AL Sched: unload sync error
SW: AL Sched: load sync error
SW: AL Sched: process sync error
SW: Unexpected SW failure - general exception
SW: executive call failed
SW: executive call tsk_create() failed
SW: executive call tsk_delete() failed
SW: executive call tsk_suspend() failed
SW: executive call tsk_resume() failed
SW: executive call tsk_set_priority() failed
SW: executive call mbx_create() failed
SW: executive call mbx_delete() failed
SW: executive call mbx_send() failed
SW: executive call mbx_receive() failed
SW: executive call mbx_flush() failed
SW: executive call buf_alloc() failed
SW: executive call buf_free() failed
SW: executive call tmr_create() failed
SW: executive call tmr_delete() failed
SW: executive call pip_create() failed
SW: executive call pip_delete() failed
SW: mbx_send failed, NULL mailbox
SW: mbx_send failed, mailbox full
SW: all tasks suspended
SW: Unexpected message in mailbox &mailbox name&, message code &hex message code&
SW: message buffer request failed
SW: message buffer release failed
SW: string buffer request failed
SW: string buffer release failed
SW: unexpected case - file:&filename& line:&line number&
SW: image command received by active task
SW: procedure call has invalid parameters
SW: status mask has duplicate flags defined
SW: Invalid status code for this command code: &hex command code&
SW: Unexpected message type for this command. type: &hex message type&
SW: Non-specific error
下列 3 位会员向 jsntpx 表示感谢:
&(), &(), &()Wargame Predicts Army Loses High Tech Edge & Breaking Defense - Defense industry news, analysis and commentary
Army soldiers training with laser sights and night vision devices.
ARMY WAR COLLEGE: A massive wargame held here this week to explore the “” of warfare in the 2030s demonstrated a stark truth — one that
— there’s no substitute for , no matter how much
the Army buys.
That’s an unsettling answer at a time when the deep, decade-long spending cuts called
threaten to slash both the Army’s numbers and the research and development money that ultimately gives birth to the most useful technology.
It takes a decade or two to
or to . So Army leaders are painfully aware that if they want to get ready for the 2030s, they need to make some key investments now. To do that they need to sell them to skeptical civilians at the very moment when
makes it all too tempting to slash programs that only pay off in the longer term.
It’s especially difficult for the Army, which than any other service over the past two decades. With
winding down, the
have a high-tech concept known as . The
is having an .
Precisely because the Army is the largest service, precisely because it is the most diverse, it spends the most time and effort getting all its internal factions to agree. By the time that anything like a vision has made the stations of the cross to get approval and input from all the requisite generals, it’s usually watered down and bloated up into cluttered, incoherent PowerPoint slides (“my instructions were to put all the ideas up there,” one briefer said) that are unintelligible to outsiders – including the people who sign the Army’s checks.
When I said this, in blunter terms, to a room full of generals, colonels, and senior Army civilians here, I was surprised by the response: a lot of rueful laughter, nodding heads, and — most surprising — a fist-bump from a two-star general.
It’s true, another two-star said. “Because we are the most complex and dysfunctional of the organizations in the Department of Defense, we have meandered all over the place,” the major-general sighed. One civilian official, he said, had even warned him that “one thing you’ve got to do is decide what you’re going to do: You can’t change your minds every year-and-a-half.”
This week’s wargames and the associated conference of senior officers – involving more than a hundred people from the Army, other services, civilian agencies, , and even an advisory body to the UN – are part of an Army program called “,” an ongoing effort to figure out the future of the service. The Army organizer, the Training And Doctrine Command (TRADOC), has given the other armed services, civilian agencies, and even me, a journalist, extraordinarily open access to some brutally honest discussions.
“I feel like I’m leading a root canal,” said one general moderating Thursday’s discussion.
“The Army is almost unique in its ability to have a self-critical discussion like this and be a true learning organization,” the Stimson Center’s
told me after we both participated in . “If you had a similar gathering at a civilian agency the culture would tend to produce talk of inputs rather than outputs, efforts made rather than results achieved. As the September 19 House hearing on Benghazi made clear, the
has no institutionalized process for lessons learned.” The Army has
devoted to dissecting what went wrong or right.
Facing An Ugly Future
The most striking case of the Army’s capacity for self-criticism that I saw came on Thursday afternoon, when a colonel and his staff briefed senior officers on how the wargames were going downstairs. (The fictional scenario was deemed too sensitive for me to sit in on the turn-by-turn planning, unlike , but I was allowed to attend the conference on the condition that I not identify any participant by name).
As in the past, TRADOC was actually running two wargames side-by-side, each fighting the same enemies in the same scenario but with significantly different assets on the American side. The “evolution force” assumed the Army sticks with its current
(although funding for it is in real danger): The only new systems in its arsenal would be ones whose key components have at least proven they can function in the lab. (The government calls this “ four” (TRL 4). The “innovation force,” however, assumed the Army had the funding – and enough luck – to get more radical technology ready in time, ranging from robotics to rapid deployment to “potential game changer technology in directed energy” (such as
to , and artillery ).
The high-tech option certainly got there faster: It deployed an “operationally significant” force to the crisis zone within 16 days, compared to 45 days for the less advanced alternative. True, the Army can already drop a battalion of paratroopers from the
anywhere on the planet overnight and deploy a full airborne brigade in 96 hours, but those are relatively lightly armed foot troops. It takes weeks or months to move in heavy artillery and armored vehicles. When airborne troops deployed to Saudi Arabia to deter Saddam Hussein’s armored legions from invading In 1990’s Operation Desert Shield they were described by an authoritative Pentagon study as “the speed bump.” Even if every single missile the 82nd carried destroyed an Iraqi tank, one veteran of the operation told the conference, “we were still short.” So closing that gap between the rapid-deploying light brigades and the slower-moving heavy hitters is crucial to the Army’s crisis response. Simply put, said one participant, “there’s less time for bad things to happen.”
Where things went sour was when the simulated US force actually closed for battle, even in the high-tech version. “When the innovative force met the enemy and got in, it just didn’t seem that technology gave you the advantage that you wanted,” said the colonel leading the briefing. Though he didn’t characterize what happened as a “defeat,” he acknowledged that progress stalled, calling it an “operational pause.”
Why? “I don’t know,” the colonel said, pointing out that the final turn of the game was still in progress and analysis had barely begun. “I just know it’s worth doing an [analysis] to break apart why the units had to stop. Were they overwhelmed?”
Diagnosing The Dangers
Institutions, like scientists, learn more from failure than from success, and the point of playing wargames is to push your force to the limit and see where it breaks so you can fix problems before they occur in real life. The Army is just beginning in-depth analysis of this week’s wargame, but first impressions suggest three major fault lines:
Part of the problem may be with the Army’s evolving concept for future warfare, “Integrated Distributed Operations.” IDO calls for fast-moving units to strike at multiple points, each moving independently rather forming a single battle front (hence “distributed”) but coordinating maneuvers and concentrating their fire (hence “integrated”) through . In part, the idea is to make up for smaller forces with superior speed and flexibility. But in the wargames, the enemy fought on doggedly against the more agile Americans and kept US units from joining forces.
“You didn’t get the shock [effect] you were looking for,” said the colonel, “and they couldn’t make [US-controlled areas] contiguous, even when they were reinforced over and over again.”
Part of the problem may be technology: Adversaries around the world are catching up. By the 2030s some countries – or well-connected
such as Hezbollah – may
in a few key areas.
“When you get to near tech parity,” said the colonel, “the engagements are intensive, they’re longer than what we were expecting to see, and… the way we’ve chosen to go in doesn’t allow the commander to have options.”
In a study of more than a dozen militarily relevant technologies, from armor protection to bioscience to robotics, the Army analysts predicted the US would stay on top throughout the 2030s in just two: the “” and “.” Barring additional investment, the study said, armor, robotics, and electromagnetic rail guns would remain solid areas of American advantage until about 2030, while computing, night vision, and drones (unmanned air vehicles) would stay in the US column only until sometime in the 2020s. , , and artillery of all kinds –
to rockets to conventional howitzers – were all areas where some adversaries might well have the edge on the United States already.
Overall, said one general, “we believe [that] our advantage is sustainable through the next two decades or so, but as you get into the
period [and] if we stay on this path, we very likely will put our soldiers in the future at risk. They will lose the competitive advantage that we’ve come to know and love.”
Even in the
where the Army was able to make additional investments in breakthrough technologies, however, the high-tech force still ran into trouble. A crucial problem was that we were sometimes just so badly outnumbered that no amount of technology could make up for it.
“We’re finding the mass, in certain situations, isn’t there,” said the colonel running the briefing.
The general was blunter: “We started running out of numbers,” he said. “At some point those numbers still matter.”
Three recent wargames and a RAND study all agreed the Army would need to field 20 combat brigades against a threat on the scale of , the general continued. But the Army is currently , which would leave very little margin for error or other simultaneous contingencies.
The mandatory
known as sequestration will make all this much worse.
So far, although the Army is in the process of shedding 80,000 soldiers – from 570,000 at the height of the Iraq war to a planned 490,000 in 2017 – it is mostly giving back its post-9/11 buildup and streamlining support functions such as headquarters and supply. In the current reorganization, “we just eliminated overhead,” the general said. But that plan predates sequestration.
As sequestration bite deeper, “we’re going to start seeing further reductions,” the general said. “It’s not just going to be brigade headquarters or a sustainment battalion, [but] the .”
Sign up and get Breaking Defense news in your inbox.
Editorial Staff
Deputy Editor
The official Congress website, from lawmakers to made laws.
Sign up and get Breaking Defense news in your inbox.
Copyright & 2016 Breaking Media, Inc. All rights reserved. Registration or use of this site constitutes acceptance of our}