Magnus VLF

Home | Contact Us | Submit Troubleshooting Info | Search | Help

GMCE Information

Overview

The Gibabit Master Control Electronics (GMCE) board is a systems control board that evolved from the Turbo Master Control Electronics (TMCE) board. Because the GMCE board communicates with the device workstation via a single ethernet cable, the SCSI cable and the two serial cables are not needed.

Advantages of the GMCE board include:

Faster data rate over copper Gigabit Ethernet—up to 600+ Mbits/sec
1.25 GHz fiber Ethernet link for the TH3 head
Faster CPU (200 MHz PowerPC) and more flash memory allows more firmware functionality
Option for an edge detect camera provided by two NTSC connectors
Reduced cost resulting from the elimination of the SCSI connections
Easier firmware installation and upgrade due to new architecture

GMCE context diagram

Cables

There are some minor cable changes (length only) between TMCE and GMCE. Major changes include:

No SCSI cable(s)
No RS232 cables
A Gigabit Ethernet cable (CAT 5E or CAT 6) connects the GMCE to the workstation. For dual-head devices, two Gigabit Ethernet cables are required—one for each GMCE board (master and slave).
This link carries all image data, RCON protocol and diagnostic commands/output.
An optional USB cable can be connected from the GMCE to a laptop, and will appear as a COM port running at 115200 baud (a USB driver must be installed first), providing diagnostic command access only. Otherwise, the GMCE has the same Hotlink and RS422 links to the head as a TMCE, and the same cable layout for carriage, drum, etc. as the TMCE. The GMCE provides SCON access to satellite boards via the CAN Bus just like the TMCE.

For cable part numbers, see Parts

Board

The GMCE board (503-08443F) looks similar to a TMCE board but there are some significant internal differences that you must be aware of:

NVS parameters are not stored on-board—they reside on the workstation in a binary file.
The product firmware is not written to an onboard flash—it resides on the workstation in a file.
Consequently, replacing a board is much easier, since you do not have to move NVS and onboard flash to the new board. A file on the workstation called C:\Creo\Firmware\CreoBootp.ini defines the NVS and product firmware file names and locations.
You must use the Test Plot Applet in Service Shell to do all test plots, especially GC plots.
All firmware (and software) components can be installed using a Controlled Release Installer.

GMCE board connectors and LEDs

J1: TH2 hotlink
J2: TH2 RS-422 control
J4:
J5:
J6:
J14:
J17:
J18:
J38: UDRC

J39:
J40:
J42: WS_COMM gigabit ethernet
J47:
J53:
J56:
J69: USB backup
U126: TH3 fibre optic

For details on the LED status, see GMCE Firmware and LED Reference.

NVS parameters

The GMCE does not have battery-backed RAM like the TMCE—the NVS parameters are downloaded to the GMCE when it is reset. The parameters are stored on the workstation in the C:\Creo\Firmware\GMCENVS00.bin file. This file name is in the CreoBootp.ini file. For dual-head systems there is another NVS file called GMCENVS01.bin for the slave GMCE board.
Whenever a parameter is changed by the product firmware or by a diagnostic command such as >>set media 1 name…, the entire NVS parameter set is uploaded to the workstation and replaces the contents of the GMCENVS00.bin file.

Some resulting actions of this architectural change include:

Simple back up of NVS by copying a file.
If the device is moved (for example, from production to a customer site), the NVS file must be moved—use the Site Installer CD for this.
The product firmware will not execute without a valid NVS file successfully downloaded to the board. If the workstation is restaged, the NVS parameter file must be preserved and restored.

Firmware

There are two main firmware components that run on the GMCE board:

Boot firmware, also called the GMCE core firmware, that executes whenever the board is reset.
The core firmware is stored in flash on the GMCE board. However, like the NVS parameters, the product firmware resides in a binary file on the workstation in the C:\Creo\Firmware folder. The file name is defined in the CreoBootp.ini file. Do not edit this file.
Product firmware, such as Magnus VLF, that executes to operate the device hardware.
Each time the GMCE board is reset, the product firmware binary is downloaded to the GMCE board and executed directly from RAM.

Some resulting actions of this architectural change include:

Simple upgrading of product firmware by replacing a file on the workstation.
If the workstation is restaged, the product firmware must be reinstalled on the workstation.
If the workstation is not running and connected to the device when the device is turned on, the device will remain in Boot mode—essentially inoperative.

To search for GMCE commands, parameters, and errors, use the MCE/GMCE search page.

To download and install firmware simulators, see the Control/settings page.

CreoBootp.ini

This configuration file defines the connection between the GMCE board and the workstation, and what firmware and NVS files to use. This file also contains the IP address of the GMCE board(s). Service Shell’s Host Configuration Wizard parses the CreoBootp.ini file to get this information to make setting up Service Shell easier. A software component called the Creo Bootp Server runs on the workstation. It reads this configuration file and coordinates the downloading of the NVS data and firmware binary.
This is a sensitive file and should not be edited directly. It is written by the GMCE Core Firmware Installer and the Product Firmware Installer.

Test Plot

On the TMCE, you use the plot command to image test plots, including GC plots. On the GMCE, you must use the Test Plot Applet (TPA) in Service Shell to accomplish this. This is because all raster manipulation is performed on the workstation, in a software component called Post Screening Raster Manipulation (PSRM). The PSRM component performs orthogonal and geometric correction on the data before it passes it to the GMCE board.
The plot command is still available, but only supports a small subset of plots available in TPA and provides no orthogonal and geometric correction. As a result, the series plot script in Service Shell cannot be used. TPA must be used for all series plots.

PSRM

The purpose of PSRM is to:

Manipulate Screened Raster Data (SRD) into Thermal Head Raster Data (THRD) that can be imaged by the device.
Provide a common datapath for clients that want to deliver SRD to the device. PSRM hides the different methods of delivery from the clients.
Generate test images from test patterns or from tiff test patterns.

The SRD is in GDAPI data format and is generated by a raster source such as workflow software (Prinergy or Prinergy Evo). The control software (DCAPI, Magnus800 Controller) provides PSRM all the necessary parameters on how the screened raster data is to be manipulated, as well as the starting and ending of jobs.
THRD is to be sent to a raster sink via high-speed interfaces. The raster sink can be GMCE, TMCE, IHIF(TBD), or a disk file. PSRM effectively provides a common datapath for GMCE and TMCE systems. As a result, the difference between GMCE and TMCE systems is transparent to the output device operator.

DCAPI

The Device Control Application Programming Interface (DCAPI) provides a common interface to the output device for Print Console and Service Tools. The DCAPI is a means of encapsulating common high level commands used to control output devices. This programming interface can be used by workstation applications to control the behavior of the device by sending commands like 'get the drum speed', or 'load this plate', or 'image this test plot'.
Why do we need it? We were starting to have numerous applications such as device controllers and service tools that needed to control the device, however each device required different commands and protocols to control it, and in many cases these were not well defined. Having one clean, dedicated interface that a programmer of these applications can use to communicate with any device – MCE, MPE, CIL based - goes a long way towards reducing code duplication, lower maintenance and quicker development cycles. So for example, a service tool that needs to load a plate only has to call a single command, while DCAPI does all the internal work of what parameters are relevant, how to structure them, and whether to send them to the device using Rcon, WSRIF or CIL protocol.

Controlled Release Installers

Each controlled release for GMCE-based products has a Controlled Release (CR) Installer. This installs all the software and firmware components in that controlled release by invoking installers for each individual component, including the Creo Bootp Server, GMCE Core Firmware, product firmware, and satellite firmware.
The CR installer must always be used to install the software and firmware components on GMCE devices.
For Thermal Head firmware, the CR Installer invokes the Service Shell upgrade script.

Workstation

There are several key changes to the device workstation that include:

DCAPI Server 2.0 handles the RCON link with the device.
Print Console 4.x and Test Plot Applet are both clients. This server provides an icon on the taskbar that expands into an administration dialog.
PSRM is a new component that performs orthogonal and GC corrections on the image data before passing it to the GMCE board.
Print Console 4 has a new user interface.
Print Console 4 requires Prinergy Evo for TIFF Downloader functionality. TIFF downloading was handled directly by Print Console in 3.x.
NVS parameters and product firmware reside on the worksation.

Connectivity Requirements

The device workstation requires an Intel Pro 1000MT, 1GB network card to communicate with the GMCE board via the ethernet cable (CAT 5E or CAT 6) that supports Jumbo Frame settings. Only the Intel Pro board is supported. To configure the Intel Pro 1000MT ethernet card on a workstation, see the GMCE Intel Pro/1000 MT Server Adapter Installation, Configuration, and Testing document.
For Magnus VLF, see also GMCE IP Addressing Scheme for Magnus VLF GMCE Devices and Workstations

Compatibility

The GMCE board is installed on all Series II Magnus VLF devices. For more information on Series II devices, see the Overview page. For Series II specific device upgrades, see the Procedures page.

Series II devices
Controlled release 3.0 and later
For details on the controlled releases, see the Control/settings page.
Automotion drum amplifier: any GMCE board version D or later will only work with the Automotion drum amplifier.

Trendsetter 400/800 and NEWS

The GMCE board is installed on all Trendsetter 400/800 III devices (serial numbers TGxxxx) and Trendsetter NEWS with serial numbers NGxxxx.

Controlled release 2.0 and later
For details on the controlled releases, see the Control/settings page.

Parts

GMCE board - 503-08443F
Intel Pro 1000MT, 1GB network card - 94-3221
For Magnus VLF:
- CAT 5E shielded ethernet cable 30 m - 216-00170
For Trendsetters:
- network cable 10 m - 220-01922A
- CAN bus cable that connects the PDB and the GMCE - 220-01689A
- UDRC adapter cable for GMCE - 220-01701A
- UDRC enable relay cable for GMCE - 220-01703A

Diagrams

Procedures

Replacing the GMCE board
Disconnect the GMCE board in the power box, remove it, install a new board, and plug in all the connectors. The replacement GMCE board does not require new product firmware or the old board’s NVS since they are both downloaded from the workstation every time a GMCE device starts up. However, you may need to update the Xilinx and boot code on the replacement board to match the Controlled Release for the device. Use the GMCE core firmware installer found in the controlled release folder of the device workstation to update the Xilinx and boot code versions.

Training

For training on the GMCE and supporting hardware and software, see the Trendsetter or Magnus VLF Reference page.

Troubleshooting

Contacts | DCAPI | GMCE | PSRM | Workstation

E-mail the GMCE Experts with your questions or problems relating to GMCE. Your e-mail will be directed to:

Greg Kervin - Device firmware
Lane Wilson - Core firmware
Craig Wilson - Print Console
Ran Katzman - DCAPI
Greg Brown - Service Shell
Jose Delgado - Connectivity
Steven Chiu - PSRM
Micle Zisman - Product support specialist - VLF
Al Edge - Product support specialist - VLF
Andrew So - Product support specialist - Trendsetter 400/800
Frank van Eerdt - Product support specialist - Trendsetter NEWS

Also, submit any troubleshooting cases that you would like to share with other CSEs stating the problems and solutions.

GMCE

GMCE firmware crashes on a Magnus VLF with TH3 firmware version 1.04.x when the door unlock command is issued. See CR4.01 patch 5.
GMCE stuck in boot mode
See GMCE Firmware and LED Reference Document (extracted from GMCE Firmware and LED Reference Document - pgs 11 to 13)
RCON Interface:Received invalid command code from workstation (Error 34810)
Multiple engine sensors not working (Magnus VLF)

DCAPI

DCAPI clients and server shutdown problems

PSRM

For PSRM troubleshooting errors, see the PSRM Errors document (719-00648A).

Workstation

FAQs

How do I find available COM ports?
See Finding Available COM Ports (extracted from SCON Firmware ver 1.20 Installer's Guide - pgs 24 to 27)
Where can I find information on SCON board status LEDS?
See SCON Boards Status LEDs (extracted from SCON Firmware ver 1.20 Installer's Guide - pgs 36 to 40)
How do I install the FTDI driver for the USB diagnostic connection?
See the Magnus VLF TMCE to GMCE Upgrade Procedure, Appendix A. Modify the driver path accordingly. For example, \Creo\Fimware\GMCE\Thermal_GMCE\GMCE Core\V1.26\FTDI driver
How do I reload the Creo bootp server and what do I do if the GMCE is stuck in boot mode?
See GMCE Firmware and LED Reference Document (extracted from GMCE Firmware and LED Reference Document - pgs 11 to 13)
How do I find out how TCP/IP ports are used?
TCP/IP Port Allocation and Configuration GMCE

Popups / Tool Tips for this Page

When the communications layer (DCAPI) is shutting down, Print Console sometimes crashes.
Workaround: Click OK in the Print Console “crash” dialog when the DCAPI server is shutting down. Print Console will then shut down. When DCAPI shuts down and Print Console handles the shutdown correctly, jobs will be cancelled because communication with the output device is lost.

If the network connection between the device and the workstation workstation is lost after an idle period, like overnight or other quiet period, then it could be that the network card is configured to save power by shutting down.
Solution: Go to Network Places for each network card and select Properties/Configure/Power Management. Uncheck the 'Allow the computer to turn off this device to save power option'.