Essenza Mars
Essenza Mars
g
E
s
n
m
ie
S
MAGNETOM
MR
Function Description
System
MAGNETOM ESSENZA
10130587
© Siemens 2006
The reproduction, transmission or use
of this document or its contents is not
permitted without express written
authority. Offenders will be liable for
damages. All rights, including rights
created by patent grant or registration
of a utility model or design, are
reserved.
Disclaimer
The installation and service of equipment described herein is to be performed by qualified
personnel who are employed by Siemens or one of its affiliates or who are otherwise autho-
rized by Siemens or one of its affiliates to provide such services.
Assemblers and other persons who are not employed by or otherwise directly affiliated with
or authorized by Siemens or one of its affiliates are directed to contact one of the local
offices of Siemens or one of its affiliates before attempting installation or service proce-
dures.
General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2 _______ Functional______________________________________________________ 8
Software Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Boot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Start-up Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Loadware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Stimo Function Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
PALI Function Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Sequence Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
RF Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
RF Safety WatchDog (RFSWD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Gradient Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Gradient Safety WatchDog (GSWD) -Stimulation Monitor . . . . . . . . . . . . . . . . . . . . 15
System Compensations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Dynamic Control Signals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Supervision and Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
System Standby Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Image Reconstruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3 _______ Hardware______________________________________________________ 20
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
MARS Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
PCI_STAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
PCI_RX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
FIBER_IO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
CAN Bus Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
CAN Bus Principle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Collision Detect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Electrical CANopen Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Optical CANopen Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
The system MAGNETOM ESSENZA integrates a new concept for the imager (formerly
called: MRIR) and measurement control (formerly called: AMC).
In former systems, these functionalities were realized with two separate computer systems.
The imager was a PC and the measurement control was a dedicated computer unit with its
own card cage and backplane. Communication between these two units and the Host took
place via Ethernet by means of a switch.
Now both functionalities are integrated into one computer system called MARS (Measure-
ment And Reconstruction System).
Fig. 1: AMC+MRIR=MARS
NOTE Please note that the software calls the MARS MCIR
Concept 1.1
Those familiar with other Tim systems like Avanto/Espree can compare them to
MAGNETOM ESSENZA as follows:
Tab. 1 MAGNETOM Avanto/Espree versus MAGNETOM ESSENZA
The background concept of the measurement control implemented in the MARS is princi-
pally the same as that of the AMC in the Avanto/Espree systems. In this concept, the
sequences (C++ programs) run in real time on the MARS computer, which then feeds the
DSP on the PCI_STAR with the sequence-specific tasks that then create the RF pulses,
gradient pulses, and sequence timing signals, including compensation. The modulation of
the RF pulses and demodulation of the MR echo pulses are also performed digitally in
accordance with the proven methods used in the previous system control unit. With the
improvement in performance of the latest DSP component, it was possible to integrate the
MARS components into just 3 boards, allowing for a very compact design.
The MARS functional description has been divided into two parts:
Functional - describes the functions performed by the MARS components.
Hardware - describes the individual hardware components and their tasks.
The next chapter (Functional) describes the functionalities of the MARS. Its responsibilities
can be grouped into the following tasks:
• Software download
• Sequence control
• Supervision and error handling
• Image reconstruction
Boot 0
After a boot is initiated, the MARS BIOS initializes the hardware and jumps into the Intel
Ethernet bootloader routine.
The Ethernet boot routine sends a DHCP request to the Host requesting an IP address as
well as the name and location of the operating system (OS) bootloader program file. The
Host evaluates the MAC address since it indicates which MARS computer is installed and
sends it the proper loader program.
Using the TFTP protocol, the MARS sends a request to the Host for the OS bootloader pro-
gram file. The Host also sends an FTP client program and BOOTP protocol routine needed
for the next steps. The MARS executes the OS loader routine after receipt.
The OS loader issues a BOOTP request for an IP address (the first was only temporary)
and the name and location of the OS files. They are sent back from the Host. The MARS
then uses the FTP protocol to retrieve the OS files from the Host.
Start-up Script 0
Once the OS has been loaded, it applies the environment variables, loads the necessary
drivers, and retrieves and executes a startup script from the Host which starts the four
MARS processes:
For detailed messages of the MARS activities, another trace can be started with
Main menu > System > Control > Tools > Save System Log-files
which starts the MR Savelog mechanism. Another way to start the MR Savelog mechanism
is via Windows Start menu:
Control+Esc > Start > Programs > MrSaveLog.
Messages will be logged into C:\MedCom\MriDiagnostics
Loadware 0
Once the MARS has booted, the Host queries each loadable component and delivers new
loadware, if necessary.
The PMU and CAN units also require loadware. This will initially be loaded and stored into
FLASH/EEPROMs at the factory or by a software update. Afterwards, only the loadware
version will be checked. A unit will be downloaded only if the version is not correct.
Parameters 0
For most units, the parameters required for measurements will be supplied.
To test the GSWD (gradient safety watchdog) hard- and software, a special Stimo-test
sequence will be run during the scanner start up. This sequence is parameterized with very
high gradient amplitudes so that when the gradient pulse is applied, it will exceed the limit
and the GSWD will cause a sequence abort. If an abort occurs, it signifies that the GSWD
is working.
To test the RFSWD/PALI hard- and software, a special PALI test sequence will be run dur-
ing the scanner start up. This sequence is parameterized with very low SAR limits so that
when the RF is applied, it will exceed the limit and the RFSWD will cause a sequence abort.
If an abort occurs, it signifies that the RFSWD/PALI is working.
RF Control 0
As the sequence progresses, the MARS feeds the DSP on the PCI_STAR board also
responsible for the generation of RF pulses with the corresponding requests and the RF
pulse amplitudes are generated (calculated) in real time. The pulse generation must also
include system-specific corrections and compensations, such as correction of RFPA
non-linearities and B0 field correction.
Dynamic timing signals must also be provided for RF components like RFPA (unblanking),
RFIS_60 (coil detuning), RCCS_60 (receive matrix switching), and BCCS (T/R switch) to
name a few. These sequence timing signals are generated by the PCI_STAR DSP on
request from the MARS.
The RF Safety WatchDog provides patient safety monitoring by measuring the specific
absorption rate (SAR) of the RF energy being irradiated into the patient. This energy
causes warming of the patient both locally and globally, that is, warming in the direct vicinity
of the transmitting coil. Global warming results on the basis of blood circulation. The
RFSWD must quantify the amount of heat-causing energy being applied to the patient, cal-
culate the distribution of these energies throughout the body, and check irradiation limits
which may have been exceeded. If any limit is reached, the RFSWD can disable the RF
transmission.
1. Look-ahead monitor
The first is a software look-ahead monitor running on the Host, which evaluates the
sequence and parameters (i.e., protocol) as they are selected and entered by the user. If
the look-ahead monitor detects that the protocol will cause excessive RF, it issues appro-
priate warnings and suggests new parameters to bring the SAR under the limit. A
sequence can be loaded and started only if it will not exceed the prescribed SAR limits.
There are two levels of SAR limits: normal mode (NM) and first level (FL). First level limits
are higher than those of normal mode and may be selected only if the user explicitly per-
mits.
2. Run-time monitor
The second process is realized in hardware and monitors the RF in real time. The actual
RF transmit pulses are sampled by directional couplers located in both the RF Power
Amplifier and the TALES, quantified, and fed back for calculation to the PALI-DSP on the
PCI_STAR board. The run-time RFSWD keeps a running tabulation of the applied RF
pulses. If for some reason limits are exceeded before the conclusion of the measurement,
the sequence will be terminated immediately.
Gradient Control 0
The gradient pulses are generated in much the same way as those for the RF. As the
sequence progresses, the MARS supplies the PCI_STAR DSP with requests for pulse gen-
eration of the logical slice selection, read-out, and phase encoding gradients. A rotation
matrix is then sent to the PCI_STAR DSP and is able to calculate the logical amplitudes
(SS - slice selection, RO - readout, PE - phase encoding) into the physical coordinates of
X, Y or Z. The DSP then corrects the eddy current, cross-term and B0 compensations
before sending the data to the gradient amplifier. The amplitude data for each axis is 20
bits, in addition certain timing and control signals are also sent. The communication
between gradient and MARS is realized by a high-speed fiber-optic connection from
MARS/PCI_STAR to GPA/STAR_NODE.
When gradient pulses are applied during an MR examination, the patient may experience
muscular stimulation. The cause is the development of electrical fields within the patient’s
nerve fibers, which are induced by the dynamic magnetic field generated by the gradient
coil. The magnitude of these induced electrical fields is, for any given sequence type, pro-
portional to the change of the magnetic field in time, expressed otherwise as dB/dt.
A stimulation occurs when a characteristic threshold of the electrical field is exceeded. The
corresponding dB/dt value needed to exceed this limit depends on the patient’s anatomy
and physiology, the geometrical and physical attributes of the gradient coil and the position
of the patient within this coil.
The ratio dB/dt is determined by the amplitude and rise time of the gradient pulses. During
actual imaging conditions, dB/dt is never constant, but depends on the sequence type and
sequence parameters (e.g., slice thickness, FoV, matrix size, TR, TE, number of slices,
etc.). The stimulation thresholds are further influenced by the timely organization of the
individual gradient pulses, the total number of pulses, their repetition time and the coinci-
dence of any or all three gradients at any one time.
The Gradient Safety WatchDog (GSWD), also called stimulation monitor (STIMO), pro-
vides safety against patient stimulation. The stimulation monitor (STIMO) is realized in
three parts:
• Look-ahead monitoring with a "SAFE Model"
• Look-ahead monitoring using the legal dB/dt limits
• Run-time monitoring with a "SAFE Model"
Look-ahead Monitor
The look-ahead monitor runs simultaneously with the parameterizing of a sequence. If
sequence parameters are chosen that will cause stimulation, a warning message is issued
to that effect and eventually changes are suggested that will prevent stimulation.
In the SAFE Model, the physiological stimulation is approximated by filtering the differenti-
ated gradient pulses. Each gradient pulse is differentiated and then filtered by applying at
least two exponential functions using two time constants. The filtered signals are then
added together using a weighting function and then compared to an established limit. The
established limits have been derived empirically through studies performed on real people.
If these limits are exceeded, stimulations are to be expected.
Run-time Monitoring
The actual values of the gradient currents are digitized on the D66 Opto-Link in the GSSU
and sent to the PCI_STAR over a high-speed fiber optic connection.
The DSP on the PCI_STAR calculates the actual gradient values and compares them to
stimulation limits. If a limit is exceeded, the GPA will be disabled.
System Compensations 0
Adjustments
Before a sequence measurement can begin, there are some system and patient-depen-
dent adjustments which have to be performed. They include:
• adjust frequency (Adj/Fre)
• adjust transmitter (Adj/Tra)
• adjust shim (3D Shim)
All of these adjustments are themselves sequences. The sequence is loaded into the
MARS and performed as any other sequence. The measured raw data will be evaluated in
the MARS, too.
3D Shim
The 3D Shim procedure measures the magnetic field, determines the field inhomogene-
ities and calculates the necessary corrections. The 1st order inhomogeneities (linear
terms) are compensated by driving an offset current through the gradient coils. The A(2,0)
term (2nd order term) is compensated by the E-Shim device. Unlike in Avanto systems, this
E-Shim is standard and contains only one channel. Unlike in the Espree systems, the
A(2,0) channel is not a supercon shim but uses a resistive shim coil.
Gradient delay
The gradient delay compensation for the three axes is also performed by the DSP on the
PCI_STAR. The necessary time parameters are determined in the tune-up procedure.
Various dynamic control signals required by several RF components and the gradient
amplifier are also generated by this DSP on the PCI_STAR board and sent by the
FIBER_IO.
During the sequence, the MARS supervises all components, assures the DSP is working
correctly or if the measurement has to be stopped in case of some functional or run-time
error. There are two main events that can cause an abort of the sequence:
• input of an error message from a unit
• the system state changes to ’not normal’
Error Messages can be generated by any of the units. If an error is detected, it will be clas-
sified and sent to the MARS. Here, depending on whether a sequence is running or not,
the MARS will decide what to do. The following error classes have been established:
• Information
• Warning and
• Error
In all cases the operator will be informed via a NUMARIS message and there will be a new
entry in the NUMARIS Eventlog. A running sequence will be stopped only in case there is
an ’Error’ classification.
Beside the error messages, there is a System State. For each of the following units, there
is status information available, detailing the current systems status. The units are the
RFAS, GPA, PTAB, MSUP, ICS, and the RFPA.
If any status bit changes, e.g., due to an overtemperature in the gradient coil or a malfunc-
tion in the chiller, the MARS will be informed automatically. This new status will be com-
pared with the predefined patterns for each of the units, representing the normal working
status. If the comparison shows that the system is not functioning properly, an error will be
created.
The MR signals coming from the RF system are demodulated as well as filtered at the
PCI_RX board in the MARS. The demodulated raw data will then be Fourier transformed
by the image reconstruction task of the MARS.
The MARS reconstruction tasks are:
• receive the measurement data from the RF system
• calculate the raw data during demodulation and filtering
• reconstruct the MR images
The measurement data are only temporarily stored on the hard drive and will be overwritten
sooner or later by new measurement data.
The MARS is located in the ECA cabinet and consists of the following components:
• PCI_STAR - responsible for RF pulses, gradient pulses, monitoring, and sequence
control.
• PCI_RX16_8 or PCI_RX16 - eight/sixteen MR signals can be received, digitally filtered
and demodulated.
• FIBER_IO - responsible for converting TTL control signals into fiber-optic signals and
vice versa.
• SAS controller - for the hard disk (temporary raw data store).
• Motherboard - the so-called MARS computer primarily responsible for image recon-
struction and communication to/from the Host.
NOTE The SAS controller is only used in the older MARS. The new
MARS_C uses a SATA disk (controller on motherboard).
Overview 0
The basis of the MARS computer is an ATX server motherboard design. The complete soft-
ware of the MARS computer is downloaded over the Ethernet and stored directly in the
onboard RAM. Since the connection to the host is a point-to-point connection, no switch is
needed.
The main features are:
• Dual core Opteron CPU (f > 2.2 GHz)
• 8 GB memory
• Ethernet 1 Gbits/s, 2 serial, 1 Parallel, 2 USB
• Linux operating system (OS) with real time extension
It includes all necessary peripheral device interfaces, including an on/off and reboot button.
Function 0
PCI_STAR 3.2
Overview 0
The PCI_STAR is a single board that fits into a PCI-X slot of the MARS. It offers the follow-
ing features:
• 1*500 MHz TigerSharc DSP
• a multifunctional FPGA
• 4 MB fast memory (SRAM)
• 2 high-speed serial links (800 Mbits/s)
• CANopen master functionality
Function 0
The following functions are performed on the PCI_STAR DSP and the FPGA:
• Calculation of the gradient pulse amplitudes in the logical coordinate system
• Conversion of the gradient pulse amplitudes from logical to physical coordinate system
(coordinate rotation operations)
• Eddy current compensation (ECC)
• Gradient delay
• B0 compensation
• Cross-term eddy current compensation
• Calculation and modulation of the RF pulse amplitudes
• Frequency-dependent RFPA correction curve compensation in amplitude and phase
• Frequency-dependent RFPA correction of modulator tolerances (frequency dependen-
cies of the 6 and 12 dB attenuators)
• Generation of control signals for RF and PDAU
• RFSWD (PALI algorithm)
• GSWD (STIMO algorithm)
• Providing two independent CANopen channels (CANopen-wake and CANopen-mute)
PCI_RX 3.3
Overview 0
The PCI_RX16(_8) is a single board that fits into a PCI slot of the MARS. It can receive up
to 16(8) RF channels. The board is identical to the version used in Avanto/Espree systems.
Function 0
The main task of the PCI_RX16(_8) board is to demodulate and filter the acquired digital
MR signals coming from the receiver board of the RFSU. Afterwards the signals of the dif-
ferent channels are sorted and transferred to the main memory of the MARS PC computer.
The main components of the PCI_RX16(_8) are :
• PCI interface
• PCI control
• SDRAM FIFO as a buffer to the PCI bus
• Receiver interfaces with high-speed fiber optic links
• 4(2) MOFIs for the demodulating and filtering of eight (four) respective receive channels
• PCI_STAR interface to control the PCI_RX while running a sequence
• Echo RAM buffer to store the MR signals
FIBER_IO 3.4
Overview 0
The FIBER_IO is mounted to the front side of the MARS box. It has no PCI-bus connection.
Most of the signals from/to the MARS are fiber optic signals that run via the FIBER_IO.
Function 0
The FIBER_IO serves primarily as an interface board. The functions found on this board
are:
• converting various electrical control signals to fiber optic and vice versa
• converting a RS-232 serial communication link to fiber optic and vice versa (used for
communication to the PMU front-end (PDAU)
• converting a V24 current-loop serial format for the Physio-Beeper
• 2 independent electric CANopen buses
• Trigger signal for oscilloscope
Controlling and monitoring of the peripheral units, e.g., MSUP, patient table etc., is done via
CAN bus.
The MAGNETOM ESSENZA provides three CAN buses:
• CANopen wake, controlling
- E-Shim
- ICS (cooling)
• CANopen mute controlling
- MSUP
- RFIS_60
- PTAB
- MPS (in case of ramping only)
• CANproprietary monitoring RFPA (DORA) only
The two CANopen buses (mute and wake) in the ECA are electric buses. The CANopen
bridge (COB) on the top left of the ECA cabinet converts the electric CANopen mute into
an optic CANopen mute and provides the old optic CANproprietary bus for the RFPA.
The CAN bus is a serial bus. It can be compared to the Ethernet hardware.
All units at the bus are connected to the same signal. Each unit can transmit and receive
data.
Collision Detect 0
In order to avoid collisions, all units will listen to the bus. If a unit wants to send data, it will
wait until there is no activity. In the event that two units start simultaneously, the unit with
the higher priority proceeds. When the bus is free, the other unit will start again. This func-
tion is available on each unit although it is shown only once in the drawing.
Addressing 0
All units listen to the bus and will respond only if the address in a telegram matches its own
unit ID. The individual 4 bit address for each unit is fixed with resistor networks.
The MAGNETOM ESSENZA uses a differential electrical CANopen bus (also called wired
CAN bus), that is, a three-wire system. One is ground/shielding, one is called CAN_high
and one is CAN_low. The CAN signal itself is derived from the difference between the
CAN_high and CAN_low signals.
It is very important that the CANopen bus be able to write and read simultaneously. How
does the optical CANopen bus accomplish this? The solution is to have two fiber optics. For
the electrical variation of the CANopen bus, there is one input for receiving (RX) and one
output for transmitting (TX). The RX signal is ’copied’ to the TX internally. When connected
to another station, the transmitted data come back in over the RX via the internal connec-
tion of the connected station.
NOTE The fiber optic cables connecting the various stations always
connect RX with TX and TX with RX.
The additional connection of the start and end point in the optical CANopen bus produces
a ring, leading to a breakdown because of a constant light on. This also happens if RX and
TX re-swapped at one unit!
There are LEDs on the RFIS_60 that indicate CAN bus activity. In the idle state, there is no
activity on the bus.
In the CAN topology diagram, you will find some CAN units called ’SLIO’ and others called
’Module’, which include a CAN and CPU.
• the SLIO is a serial-linked IO, which means it just has input and output ports; the func-
tionalities are hard-coded.
• The ’module’ has a processor and a loadable software program.
(Introduction / p. 4)
Information regarding MARS_C and 16 channel option added in chapter Introduction.
(Functional / p. 8)
Information regarding MARS_C and 16 channel option added in chapter Functional.
(Hardware / p. 20)
Information regarding MARS_C and 16 channel option added in chapter Hardware.