Networking

APIP / DCM / MPS / MNR / TMX

Order-No.: DD+DIS068.98E August 98

*1Q1JVS1* Rev. 1.3

1 Piece Q1JVS MA1

printed in Germany
 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

7 Glossary

ACR-NEMA American College of Radiology - National Electrical Manufacturers

Association List of contents
AMDI -C Agfa Medical Digital Interface -Control
ANSI Ammerican National Standards Institute
AOS Adonis Operating System
APIP Agfa Picture Archiving Protocol
1 General Introduction ...................................................................................... 4
ASCII (American Standard Code for Information Interchange) The predominant
method for encoding 7-bit characters on a personal computer. HTML, tags 2 APIP ................................................................................................................. 8
and URLs must be in ASCII. 3 DICOM ............................................................................................................. 8
CAD Compact Acquisition Module (A+B Module of the MG) 3.1 Introduction................................................................................................ 8
3.2 IMOS DICOM configurator rev. 2.3.1 or higher .......................................... 11
CR Computer Radiography
3.3 Adjustments on DICOM Modality Side ....................................................... 15
DICOM Digital Imaging and Communication in Medicine 3.4 Checklist for Drystar / MG3000 DICOM installation problems .................... 16
ECU Embedded Controller Unit (C Module) 3.5 How to configure DICOM manually............................................................ 16
Ethernet Frequently spread technologies for LANs (Local Area Networks) 4 Postscript........................................................................................................ 21
4.1 Introduction................................................................................................ 21
FTP (File Transfer Protocol) The Internet service that transfers files from one 4.2 Imos Postscript / MNR Configurator Screen: ............................................. 23
computer to another. 4.3 Remark to page size.................................................................................. 23
IMOS Image Monitor Software 4.4 Readme Files MPS / MNR......................................................................... 24
Internet address See network location. 4.5 Troubleshooting MPS ................................................................................ 28
4.6 Drivers for MPS / MNR .............................................................................. 29
IP (Internet Protocol) Internet software that divides data into packets for
5 TMX Application ............................................................................................. 30
transmission over the Internet. Computers must run IP to communicate
across the Internet. See also TCP. 5.1 TMX: General ............................................................................................ 30
5.2 Mail message ............................................................................................ 30
IP-Adresse (Internet Protocol Adress) The standard method which identifies an internet 5.3 Manual TIFF / MAIL installation ................................................................. 30
connected computer. 5.4 TIFF/MAIL Configuration driver_name ...................................................... 31
ISDN Integrated Services Digital Network 6 Appendix ......................................................................................................... 35
ISR Interface Status Report 6.1 Troubleshooting Ethernet Connections ...................................................... 35
LAN 6.2 Nice to know about RTT tables... ............................................................... 35
(Local Area Network) Networktechnologie, designed to connect computers
over short distances. It is possible to connect the LAN with the internet or to 7 Glossary .......................................................................................................... 38
make a configuration into an intranet.
Lp/lpr Line printer daemon on workstations
LR Laser Recorder
LUT Look Up Table
Mailto The Internet protocol that is used to send electronic mail.
MFRI Multi Format Receiver Interface
MG Medical Gateway
MIME type (Multipurpose Internet Mail Extensions type) A method used by Web
browsers to associate files of a certain type with helper applications that
display files of that type.
MNR MeGa Network Reader
MPS MeGa Postscript
PACS Picture Archiving and Communication System
PAP Printer Access Protocoll. Print protocoll above ethertalk for Appletalk
printers

05.01.00 page 38 of 39 05.01.00 page 3 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

1 General Introduction MFP_ARTIDS Description:

Meanwhile we have a few different configurators for configuration of the different pins of the A list of art ids for which MFS message broadcast is not allowed or needed. This is the case for
MG3000, Drystar 2000 or Drystar 3000. workstations, like AS, PS, RS, or even between MGs interconnected via an ISDN telephone line, in
order to keep costs to a minimum.
What is a pin?
For those art ids entered in the list, an mfp server is started, which simulates the MFX behaviour of
A pin is an input or an output, locally or via network. It is a piece of software, that can be the remote station. Each art id is a decimal number, multiple art ids are separated by a comma
connected to a piece of hardware, e.g. a VSI interface or a network interface (BEN + MAU).
Theoretically, from software point of view, we could configure pin 1 to 10 as inputs, pin 11 to Example:
20 as outputs (always only pin 11 is used!) and pin 21 to 30 as network input/output. e.g. An AS3000 is set in art id 3
and a PS5000 is set in art id 5.
-
For those art ids entered in the list, an mfp server is started, which simulates the MFX behaviour of
the remote station.

Required Setting NVF Entry

---------------- ---------
3,5 mfp_artids 3,5

Attention: This is not necessary in case the correct dest_type is entered in the ART table: dest_type
= 0 for AS and RS / dest_type = 4406 for PS.

Sketch 1: Pin Assignments on MG3000 / Drystar 2000 / Drystar 3000

How many pins can be used simultaneously?

The max. number of inputs is limited to 9. The input pins are divided among no_amods (number of acquisition
modules) and no_nmods (number of network modules), to be set in the SYS component's configuration table.
(NVE SYSXXX00 no_amods, no_nmods)
Example: For a Drystar 3000 the number of no_amods is 4 (3 VME inputs + 1 local keypad) leaving 5 possible
no_nmods. Usually the first nmod is for APIP, leaving thus only 4 possible no_nmods for other network
applications, e.g., DICOM.
Following pin assignments can be distinguished:
Device Input Output Network (Input / Output)
MG3000 (LR3300 Controller) Pin 1 to 3 Pin 11 Pin 21 to 26
Drystar 2000 Pin 1 to 3* Pin 11 Pin 21 to 26
Drystar 3000 Pin 1 to 4** Pin 11 Pin 21 to 25
*Drystar 2000 Input Pin Assignment:
Pin # Used for...
1 VSI or MFRI Interface
2 Local Keypad (TIF driver)
3 VSI or RDS
**Drystar 3000 Input Pin Assignment
Pin # Used for...
1 VSI or MFRI Interface
2 VSI or MFRI Interface
3 VSI or MFRI Interface
4 Local Keypad (TIF driver)

05.01.00 page 4 of 39 05.01.00 page 37 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Pins 1 to 4 as well as 11 and 21 (=APIP by convention) are configured by MeGaCon.
Pins 22 to 30 are configured via the IMOS DICOM, MPS*** or TMX**** configurator.

***MPS = MeGa Postscript

****TMX = Tiff Mail Extension
For a complete list of abbreviations and expressions see the glossary.

Programming RTT (for to send to 192....; =class C):

subnet_mask "[Link]" This is an entry for NO subnetting
...destination "[Link]" ..reach ANY destination overthere
...gateway "[Link]" ..reach them via Router [Link]

Programming RTT (for to send to 134....; =class B):

subnet_mask "[Link]" This is an entry for NO subnetting
...destination "[Link]" ..reach ANY destination overthere
...gateway "[Link]" ..reach them via Router [Link]

Now let us exchange network cluster 192..... (class C) by a network

cluster class A, e.g. 27.x.y.z: Sketch 2: Usage of the different configurators

Programming RTT (for to send to 27....; =class A): The image formats and protocols that can be configured with the different configurators are
subnet_mask "[Link]" This is an entry for NO subnetting displayed in the next 2 sketches:
...destination "[Link]" ..reach ANY destination over there
...gateway "[Link]" ..reach them via Router [Link]

You can make up to 9 such definitions.

If you want just certain destinations to be reachable via the router, you can specify them explicitly, as
follows:
...[0]destination "[Link]"
...[0]gateway "[Link]"
...[1]destination "[Link]"
...[1]gateway "[Link]"
...

Further parts of the table:

arp_table You don't have to do anything here.
hosts_table This is for your convenience, when you would like to reach some of the remote
destinations by hostname, not by IP, and the hostnames are not listed in the ART tables.
Example:
...[0]hostname "mg11" Sketch 3: The file formats for image transmission
...[0]hostaddress "[Link]"
...

Remark for ISDN applications:

MFX parameter "mfp_artids" for ISDN connections and Ethernet connection to workstations (only
valid for MeGa3P30 and higher).

Please see enclosed part of the documentation on your PC in the "mg30" shell: MG documentation:
Operating system: MFX: mfp_artids

05.01.00 page 36 of 39 05.01.00 page 5 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
6 Appendix
6.1 Troubleshooting Ethernet Connections

Symptom: You configured a network, but no printing via Ethernet is possible. Enclosed some hints,
how to troubleshoot.

Possible reasons:
HARDWARE
• cable (not RG-58; short circuit; not connected, not terminated by 50 Ohm terminator)
• BEN board (Fuse;....)
• Transceiver (see green LED = power. Off means BEN or Trans. problem)
• Drop cable, internal MG3000 Ethernet cable.

SOFTWARE
• Ethernet not configured
• Problem in ART table (mismatch of small/capital letters; typing error;
• mismatch of apip_dest_names.
• Not enough diskspace for the network user 4 (or 5 to 9) in MG3000 where you want to print
Sketch 4: The Network Protocols for Image Transmission image.

Tools for troubleshooting:

The following table shall give an overview, which configurator is used for what network image format
TROUBLESHOOTING HARDWARE
and network protocol:

start "rem" (logbook). Type "go" and have a look to the first page of information. You should get
something like:
Configurator Pin Network Image Format TNX ethernet address 00-66-00-27-6f-00 (=BEN ethernet adddress)
Protocol TNX selftest MAC okay (=one function of BEN SONIC chip)
TNX selftest ENDEC okay (=encoder/decoder function of SONIC
MeGaCON 21 APIP APIP chip)
TNX selftest cable okay (=check of fuse and cable)
DICOM 22 to 26* DICOM DICOM
TROUBLESHOOTING SOFTWARE
MPS with [Link] 22 to 26* LP/LPR AGFA Postscript or
look to the whole customization list: type NVE at the AOS shell prompt. You have to get
floppy ETHXXX21 driver at the end. Otherwise it seems that Ethernet is disabled.
FTP Picker Postscript
type "adv" to get the whole list of all Ethernet nodes in your network ("adv" means "advertise").

PAP Comment: "adv" is much better than using "ping", because you do not have to know the other nodes
addresses or names.
MPS with [Link] 22 to 26* FTP TIFF or
floppy 6.2 Nice to know about RTT tables...
LPR SUNRASTER When do you need an RTT table:
Whenever you have to connect two or more network clusters having different Network-IDs, e.g.
TMX 22 to 26* SMTP TIFF 192.9.200.x and 134.3.x.y by means of a router.
*Drystar 3000 only up to pin 25! We have to distinguish between 3 different network classes:
(1) Class A: 0......127 Host definition: last 9 figures
All configurators except MeGaCON are explained later on. For a description of IMOS MeGaCON, (2) Class B: 128....191 Host definition: last 6 figures
DICOM and Postscript Configurator see the corresponding Windows Helpfile. (3) Class C: 192....254 Host definition: last 3 figures

Example: Here is the programming of RTT to reach any destination in 192.9.201.x from 134.3.x.y via
the Router and vice verse.
The IP-address of the router is [Link] respectively e.g. [Link].

05.01.00 page 6 of 39 05.01.00 page 35 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Enclosed a graphical overview of the different configurators:

=Example:
Required Setting NVF Entry
Salesman@[Link]
President@[Link]
IMOS
MG3000 IMOS
MG3000 IMOS
MG3000
MGC10126 OEM34155 SDK2.10
mail_from a:\winstall a:\winstall a:\setup
1/2 1/2 1/2

=Description:
Give your mail account name. This name is used to identify the sender of the E-mail message. Most
mail servers do not check on this name.
IMOS IMOS [Link]
MG3000
DICOM2.31 MG3000 MG3000
MPS2.33
=Example: a:\winstall a:\winstall
1/3 1/2 1/1

Required Setting NVF Entry

NiceGuy@[Link] Attention:
SW Versions are subject
to change.
See DIGIMAIL* for updates.
*DIGIMAIL = Bulletin Board MG3000.
Modem no. +49 89 6207 7777

Hard MPS32935
MG3000 MNR32925
MG3000
MPS32941
disk
1/1 1/1

[Link]
Image Formats:
AGFA + Picker Postscript Image Formats: TIFF + Sunraster
Protocols: PAP + lp/lpr + FTP Protocols: lp/lpr + FTP

Overview of the different configurators

05.01.00 page 34 of 39 05.01.00 page 7 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
ribbon proc_type 2

2 APIP processor color

black/white proc_color 0
APIP (Agfa Picture Archiving Protocol) is the CMY proc_color 1
standard network language. It is used for CMYK proc_color 2
APIP communication between AGFA devices via network.
It is normally configured on pin 21 (see drawing). specs

MG =Description:
Drystar The specification parameter of the output device to be simulated.
3000
=Example:
[Link]
Required Setting NVF Entry
left margin specs_lm xxxx
top margin specs_tm xxxx
3 DICOM width specs_w xxxx
3.1 Introduction height specs_h xxxx
pixels per meter specs_ppm xxxx
DICOM = ,,DIGITAL IMAGING AND COMMUNICATION IN MEDICINE". Since 1983 the American College of lines per meter specs_lpm xxxx
Radiology- ACR- and the National Electrical Manufacturers- NEMA- try to create a standard for density units specs_dunit xxxx
transmission of photos and added information in-between digital systems. AGFA is an active ICM input bits per pixel specs_inbit xxxx
member of this team. The third version of this standard is called DICOM. AOM output bits per pixel specs_vbits xxxx
typical exposure time in 1/10 sec specs_exptime xxxx
Overview of DICOM functions typical cycle time in 1/10 sec specs_cyctime xxxx
Function Ability as user Ability as provider number of print passes specs_no_passess xxxx
number of dispensers specs_no_disp xxxx
Query Call up a database Ability to receive image data from an processor device code specs_proc xxxx
external system process time specs_proc_time xxxx

Retrieve External call up of the own At a query it is possible to transmit mail_artid

database image data to an external system
=Description:
Storage Transmission of image data to an Storage of image data on a specified Use Simple Mail Transfer Protocol (SMTP) to send the tiff images via E-mail. To activate this
external system for storage database service, set mail_artid to a valid ART index, different from 0. If using the interactive tio command at
the MG prompt, the value is used to find the mail server. If used as a C-module component, then the
Print Transmission of picture data to an Provides for others to print out on the mail_artid is taken from the NJE message, but mail_artid should still be different from 0. Also, set the
Management external system to print out own or associated system port number in the ART index used to 25, which is the reserved port number for SMTP.
To de-activate tiff E-mail, set mail_artid to 0.
Drystar 2000 and Drystar 3000 are so far only used as DICOM "print providers" (= DICOM devices
print on the printers). The MG3000 can also be used as storage user for ADC and IMPAX (= =Example:
MG3000 sends patient folders in DICOM format to ADC PS station and IMPAX).
Required Setting NVF Entry
3.1.1 AGFA supports DICOM 3.0: art id 1 contains the hostname of the mail server:
In General: mail_artid 1
-DICOM3 gives no guarantee for "interoperability" (of 2 DICOM devices)
-DICOM3 is no plug-and-play environment mail_to
-DICOM3 is no guarantee for consistent image quality
=Description:
Give the name of the mail user, for whom the E-mail is intended for. Other synonyms for mail user
are, mail account name or mail recipient name. This name should be a valid and registered name in
the mail server, otherwise the E-mail cannot be delivered.

05.01.00 page 8 of 39 05.01.00 page 33 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

dispenser (0..4)

=Description:

The size and the shape of the dispensers (0..4) Of coarse, the monitor compo nent has no
dispensers, but the B module will only send an image to a component if the B module knows that the
component is able to handle the image. The check is done by comparing the image size with the
dispenser size and the requested medium type with the medium type of the sheets in the dispenser.
Therefore up to five dispensers can be defined in terms of medium size and medium type to be able
to receive images from the B module.

=Example:

Required Setting NVF Entry

medium sizes
NO SIZE for dispenser x disp_size_x 0
8 x 10 for dispenser x disp_size_x 1
10 x 14 for dispenser x disp_size_x 2
11 x 14 for dispenser x disp_size_x 3 Sketch 5: APIP and DICOM in a network
14 x 17 for dispenser x disp_size_x 4
14 x 14 for dispenser x disp_size_x 5
A4 for dispenser x disp_size_x 6 The number of pins used for network
A3 for dispenser x disp_size_x 7 connections has nothing to do with
changes in hardware:
medium types
NO TYPE for dispenser x disp_type_x 0 We are using for all network connections
paper for dispenser x disp_type_x 1 the network interface (= BEN + MAU
OHT for dispenser x disp_type_x 2 board) as hardware platform.
clear for dispenser x disp_type_x 3
blue for dispenser x disp_type_x 4

medium orientation The DICOM configurator configures pin

portrait for dispenser x disp_orient_x 0 22 for DICOM. If more than 2
landscape for dispenser x disp_orient_x 1 associations are chosen the according
numbers of pins is used (i.e. 2
default associations: Pin 22 and 23, and so on...)
8 x 10 for dispenser 0 disp_size_0 1
blue for dispenser 0 disp_type_0 4
portrait for dispenser 0 disp_orient_0 0
14 x 17 for dispenser 1 disp_size_1 4
blue for dispenser 1 disp_type_1 4
portrait for dispenser 1 disp_orient_1 0

processor
Sketch 6: MG3000 from Hardware and Software Point of View
=Description:
The output processor characterisation in terms of the processor type and the color or black/white
classification.

=Example:

Required Setting NVF Entry

processor type
no_processor proc_type 0
liquid proc_type 1

05.01.00 page 32 of 39 05.01.00 page 9 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

TMXXXX<Output>
mail_artid <Art Table>
mail_to "DoctorX"
mail_from "mg3000"

ARTXXX00 <Art Table>

apip_dest "Mail"
dest_type 0
available 1
n_io_id 12 (Corresponds with TMX output i.e. 12 if TMX is configured on output 12 )
e_io_id 12
port 25 (SMTP)
hostname "MailServer" (Name of Mail Server)
inet_addr "[Link]" (IP Address for Mail Server, this is not always the
same as the IP address of the PC on which the doctor
is working on.)

Sketch 7: Two DICOM modalities in a network. The application determines the output and ART Table to configure. If TMX is reconfigured on the
same machine, then the existing TMX output and ART table are used.
The parameters, ART n_io_id and e_io_id, are set to the TMX output.
Tio parameter TMX mail_artid is set to the TMX ART Table.
In the case of a virgin configuration no_cmods is incremented and no_nmods in incremented if
no_nmods < 1.

5.4 TIFF/MAIL Configuration driver_name

=Description:
The name of the driver that is dealing with TIFF file format.

=Example:
Required Setting NVF Entry
[Link] driver_name "[Link]"

tprio

=Description:
Sketch 8: One or two associations for two DICOM Modalities. Task priority. Priorities run from 10, (high prio) to 255 (low prio).
Do not change this value, unless it is discussed with the MeGa software team.

=Example:

Required Setting NVF Entry

100 tprio 100

pathname

=Description:
The directory root, at which tiff files are created.

=Example:
Required Setting NVF Entry
D:/ pathname D:/

05.01.00 page 10 of 39 05.01.00 page 31 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

Difference between one or more DICOM PMS Associations. Example: 3 DICOM Modalities
5 TMX Application connected to an LR3300 Controller

5.1 TMX: General One Association 2 Associations for 3 3 Associations for 3

An MG3000 Medical Gateway can convert images captured from one of the local inputs to TIFF files, for all 3 DICOM DICOM PMS DICOM PMS
which are then sent via Electronic Mail (E-mail) to a doctor's mailbox. There is one E-mail message PMS Modalities Modalities Modalities
per converted image to TIFF file. The TIFF file is added to the E-mail message as an MIME 1.0 Which pins are 22 22 and 23 22 and 23 and 24
attachment, and encoded in base64 encoding. The MG3000 uses the Simple Mail Transfer Protocol used:
(SMTP) from RFC 822, with Multipurpose Internet Mail Extensions (MIME) from RFC 1521. Advantage Less memory usage At least 2 of 3 All 3 modalities can
in LR3300 modalities can have have access to the
Controller access to the LR3300 LR3300 controller
SMPT SMPT
controller whenever it whenever it is needed.
is needed.
Mail Disadvantage If one modality More memory usage in Even more memory
MG Server makes an LR3300 controller usage in LR3300
association, the controller
others have to wait
E-Mail.
Sender: MG3000 until it is released
Attachement: 1 TIF File Which E:\acq5 PMS22 E:\acq5 PMS22 E:\acq5 PMS22
subdirectories E:\acq6 PMS23 E:\acq6 PMS23
Modality are created on E:\acq7 PMS24
E:
5.2 Mail message
An E-mail consists of a subject, a body and an optional attachment. 3.1.2 How to get the DICOM floppy:
Order it via ABC code:
Subject -3V8QZ MG3 DATA INPUT SERVICES DICOM FIRST (=first DICOM connection);software floppy
The subject contains the patient id. IMOS DCM229 (or higher) + licence agreement; DICOM conformance statement +newsletter,
Installation instructions, LCD-keypad if not yet available.
Mail Body -3V8S4 MG3 DATA INPUT SERVICES DICOM SUBS (= subsequent connections); licence
The mail body contains following text: agreement (without floppy; DICOM conformance statement +newsletter, installation instructions)

"Hello,
3.2 IMOS DICOM configurator rev. 2.3.1 or higher
With this mail, you receive a number of TIFF image files. IMOS DICOM 2.31 or higher can only be used for MeGa3P30, MeGa3P31 and MeGa3P32. For
The image files are in base64 encoding format. MeGa2P20 the previous IMOS configurator rev.1.00 has to be used (Upgrade to MeGa3P31
In case of transmission problems, contact your supporting recommended!)
network systems' administrator. If you order DICOM you will get the comfortable Windows based DICOM configurator. It
automatically detects the installed software, either MeGa3P30, MeGa3P31 or MeGa3P32 and
Bye!" downloads the corresponding DCM zipfile (DCM31522 for MeGa3P30 or DCM31550 for MeGa3P31
or DCM32942 (or higher)) to the C: drive of the controller.

Attachment A brief instruction how to use the configurator:

The TIFF file is added as an attachment. • Insert floppy 1 into the PC floppy drive and select "File → execute / run → a:\winstall"
• Start IMOS DICOM by double clicking on the IMOS DICOM icon
• The following screen will be displayed
5.3 Manual TIFF / MAIL installation

SYSXXX00

no_nmods ? (incremented if no_nmods < 1)

no_cmods ? (increment for virgin configuration)

CMNXXX<Output>
cmnprg_name "[Link]"

05.01.00 page 30 of 39 05.01.00 page 11 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

4.6 Drivers for MPS / MNR

Example: 1 APIP connection. 2 DICOM PMS connection. 1 connection via LP. 1 connection via
FTP. 1 connection via PAP.
ETHXXX21 {0..0}
CMNXXX22 {0..0}
PMSXXX22 {0..0}
CMNXXX23 {0..0}
PMSXXX23 {0..0}
CMNXXX24 {0..0}
CMNXXX25 {0..0}
CMNXXX26 {0..0}
PAPXXX26 (0..0)

DRY_3_32_C:\> nve CMNXXX23

cmnprg_name "[Link]"
>
DRY_3_32_C:\> nve CMNXXX24
cmnprg_name "[Link]"
>
DRY_3_32_C:\> nve CMNXXX25
cmnprg_name "[Link]"
>
DRY_3_32_C:\> nve CMNXXX26
Screen 1 cmnprg_name "[Link]"

• Screen 1 guides you through the program. Select first Setup Port (if required), the INSTALL, then 4.6.1 MPS / MNR Image Parameter Settings: Where to find them again (in DSP11)
CONFIGURE and so on. EDIT PMS PROFILE is only necessary, in case you want to change a
certain setting of the PMS default parameters. DRY_3_32_D:\> type dspxxx11.u00
• At INSTALL the corresponding DCM file gets downloaded. 00
dsp_virgin_cfg 0
• After selection of CONFIGURE, the following screen will be displayed:
film_backg 0 255 255 255 Film Backround values for black&white,
RGB
policy 999 Printable area dependend
pagesize 957 1163 = 33.77 x 41 cm
cs_table 10010 user_taste 100 / cs_table 10

Screen 2

Note: The selection PMS and 1 association is just an example!

05.01.00 page 12 of 39 05.01.00 page 29 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

PSO:
4.5 Troubleshooting MPS By checking the PSO (Storage SCU for SC - Secondary Capture - image and print parameters) box
the SC storage SCU application will be installed on the connected device. From MeGa 3.32 on the
1. Some general remarks in case a PS-file comes in the printer queue but PSO application will be installed. For previous MeGa releases the SNC application (which does not
is not printed out : support Print Storage) will be installed. One will still need to enter the APIP destination in the
- The processing of postscript files can take a while... correct ART table entry. PSO as well as SNC allow only one association.
To see if the processing is still busy, look at "d:/ps". This option has to be selected in case you want to send DICOM images to an IMPAX workstation.
Normally, there will be some files "...%img" which will grow while the Exception: If ADC (computed radiography) images are being sent to a workstation select "CRX"
processing is busy. (see below).
At the end of the processing, the files are deleted. CRX:
- try the same file on an office PS-printer (for example with ADOBE-PS) By checking the CRX (Storage SCU for CR - Computed Radiography - image parameters) box the
If it is not printed on such a printer, there is a big chance that the CR storage SCU application will be installed on the connected device. One will still need to enter
PS-file itself is suspected. the APIP destination in the correct ART table entry. CRX allows only one association. The CRX
- An easy way to find out if AgfaScript is able to understand a PS-file application is supported from MeGa 3.32 on.
(without any interference with This option has to be selected in case you have an ADC connected to the MG3000 (or Drystar
our acquisition,spooler and controler software) is as follows : 3000) and you want to send images (computed radiography) to an IMPAX workstation.
- reset the Drystar PMS:
- be sure the system is not starting up By checking the PMS (Print Manager SCP) box the Print SCP application will be installed on the
- go to d:/ps connected device. PMS allows up to 6 associations, minus the ones already taken for the installed
- type "pss" : you will see that AgfaScript is starting up with : network modules and/or PSO and/or CRX components. A check is made on the number of
AgfaScript 2000.000 16:15:43 Jun 20 1996 entered associations for the PMS component.
%%[ Warning: Kanji ProcSet not found ]%%
This option has to be selected in case you want to send any DICOM image to one of your printers
-- jobbegin --
(LR3300 / Drystar 2000 / Drystar 3000). One association is sufficient to serve several inputs.
- type "(filename) run"
- after a while following things should come out :
Note : depending on the needed application(s) it is possible to check only one, two or all three
%[ Error: Map type 3 rows 180 cols 1888 bits 8
different network configurations together.
%[ Error: xoffset 0 yoffset 0 nrofseps 3 cacheflag 0
%[ Error: Bitmap 0 rows 180 cols 1888 xoffset 0 yoffset 0
Select EDIT PMS Profile only in case you want to customize one or more of the modalities
%[ Error: bits 8 rmus_row 472 tail_rels 0 rmus 84960
0x4f16b0 connected via DICOM. Attention: This only works for MeGa3P32! Example: You want to have
annotations for a certain input or you want to have a different taste look up table (i.e. a different
- if this is the case, AgfaScript is able to understand the PS-file. contrast setting). Note: Parameters changed with the EDIT PMS Profile screen only can be active,
- type "^D" or "^Z" to see "-- jobbegin --" if they are not sent from the connected modality. If they are sent from the connected modality they
- type "psexit" to return to shell will be ignored.

2. the PS job, printed out on our printer, doesn't have the same shape as
the original :
- one or more sides are cut off
- the image is reduced in one corner
- ...
Check the choosen policy :
- if 0 : it is normal that some info is cut off. The PS-job is discribed
for a full film size, but part of the film can't be printed.
- if 1 : indicates a severe problem in PS-job or MPS-software
- if 3 : check the default pagesize
With this policy, a PS-job with defined pagesize, is processed to fit on
the pagesize of the printer.
But if the PS-job doesn't contain a pagesize, we apply our default
pagesize.
Suppose a PS-job is made for A4, but it does not specify this pagesize in
the job, and our default pagesize is 8x10", then all parts of A4 that is
not covered by 8x10" will be lost before the processing is done to fit on
the pagesize of the printer.

05.01.00 page 28 of 39 05.01.00 page 13 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
- after a while following things should come out :
%[ Error: Map type 3 rows 180 cols 1888 bits 8
%[ Error: xoffset 0 yoffset 0 nrofseps 3 cacheflag 0
%[ Error: Bitmap 0 rows 180 cols 1888 xoffset 0 yoffset 0
%[ Error: bits 8 rmus_row 472 tail_rels 0 rmus 84960
0x4f16b0

- if this is the case, AgfaScript is able to understand the PS-

file.
- type "^D" or "^Z" to see "-- jobbegin --"
- type "psexit" to return to shell

Screen 3

Here you can see an example of an EDIT PMS PROFILER FILE session. The result of this session
will be a [Link] file, a FOR_CT2.PMS and FOR_CT1.PMS file.

Note: To every AE title you can make your own ".pms" file, already known from the .u00 files made
during customization. So every DICOM connection can be customized.

Explanation:
Example [Link] file Comment
[CT1] • CT1 and CT2 are the AE Titles of the connected modalities
IDF = C:/[Link]
CFG = D:/FOR_CT1.PMS • The Idf file (IDF = Image Display Format) is a layout mapping file,
that maps the DICOM layout to a certain AGFA layout (see example
[CT2] below)
IDF = C:/[Link] • The CFG file contains the PMS parameter settings for the
CFG = D:/FOR_CT2.PMS
corresponding AE title i.e. connected modality

Harddisk
[Link] (DCM layout mapping file)
Partition C:

Partition D:
[Link]
MG [CT1]
IDF = C:/[Link]
DICOM DICOM CFG = D:/FOR_CT1.PMS
Modality Modality
"CT1" "CT2" Partition E:
[CT2]
IDF = C:/[Link]
LR3300
wants dmax 2.8 CFG = D:/FOR_CT2.PMS
wants linear UTL
FOR_CT1.PMS
dbmax 28000

FOR_CT2.PMS
utl_id 1

05.01.00 page 14 of 39 05.01.00 page 27 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

put file Example .IDF File Comment

quit Example 1: The left part of the table is the DICOM layout
8INX10IN\PORTRAIT\STANDARD\1,1 1011
8INX10IN\PORTRAIT\STANDARD\2,1 1012
description. It is mapped to the AGFA layout
6. [Link] : ID. See file "[Link]" on the service PC for a
8INX10IN\PORTRAIT\STANDARD\1,2 1021
----------- 8INX10IN\PORTRAIT\STANDARD\2,2 1022 description of the layouts. This file has to be
"helper" for DSP to handle postscript files (level I and II) .............. edited on the laptop, can be renamed however
...............
as you want (e.g. [Link]) and downloaded
7. [Link] : to the C: partition again. Example: You want,
------------ Example 2: that whenever the layout 8x10 1/0 portrait is
"helper" for DSP to handle Picker postscript files (short term 8INX10IN\PORTRAIT\STANDARD\1,1 800 selected at the host side, the layout 1/0
implementation as in MEGA31) 8INX10IN\PORTRAIT\STANDARD\2,1 1012
portrait for Drystar 2000 is selected (= AGFA
These files must contain following items : 8INX10IN\PORTRAIT\STANDARD\1,2 1021
8INX10IN\PORTRAIT\STANDARD\2,2 1022 layout ID 800). Edit the corresponding line as
- line a : /draw.....
............... shown beneath in example 2.
ex.: "/drawcolorimage" ............... Before the file can be selected in the EDIT
line a+1 : xxx yyy z with xxx = width, yyy = heigt, z = #bits per
PROFILE Screen it must already be present
pixel ex.: "1280 1024 8"
on the C: partition.
- line b : draw
ex.: "drawcolorimage"
follewed by lines of hex numbers Currently (10/97) by default following IDF files do exist (they are downloaded with the
Following item may be included : [Link] file):
[Link] 7567 27-NOV-1996 16:00:56 rwx
- line c : "currentfile rgbmap readhexstring pop pop" PMS_3XX.IDF 2691 28-NOV-1996 9:57:38 rwx
followed by 6 digit hex numbers PMS_8XX.IDF 1041 27-NOV-1996 16:01:02 rwx
PMS_DI.IDF 3016 27-NOV-1996 16:01:08 rwx
8. [Link] :
-------------- Example .CFG file Comment
Ethertalk driver FOR_CT1.PMS In this case the Dmax is set to 2.8.
00
pms_virgin_cfg 0
The parameters defined in .pms files are only active in case they
9. [Link] : dbmax 28000 are not sent from the host!
------------ The file is automatically created with the DICOM configurator in
network interface that supports the Printer Access Protocol. the EDIT PMS Screen. Advanced users also can make a NVE on
e.g. PMSXXX22 and rename the so created .U00 file accordingly
10. [Link] : (e.g. [Link]).
----------------
stand alone test program to test the Printer Access Protocol. When finished with the EDIT PMS Profile screen (you also will be asked to edit the disk quota in
between) select CANCEL and CONNECT - EXIT to leave the DICOM configurator.
Remark : In case of any problems see sections
Some general remarks in case a PS-file comes in the Drystar queue but is • Checklist for Drystar / MG3000 DICOM installation problems
not printed out : • Troubleshooting DICOM connections
- The processing of postscript files can take a while...
To see if the processing is still busy, look at "d:/ps". 3.3 Adjustments on DICOM Modality Side
Normally, there will be some files "...%img" which will grow while the
processing is busy.
At the end of the processing, the files are deleted. After DICOM configuration tell the technician at the DICOM user side:
- try the same file on an office PS-printer (for example with ADOBE-PS)
• the inet_addr of ART0 (or 1, which has to be the same).
If it is not printed on such a printer, there is a big chance that the
PS-file itself is suspected. • the host_name of ART0 (or 1, which has to be the same)
- An easy way to find out if AgfaScript is able to understand a PS-file
(without any interference with • the "application entity title", what is the "apip_dest" of ART1
our acquisition,spooler and controler software) is as follows :
- reset the Drystar • the "listening port", what is port 104 (Parameter: local_port in PMSXXX22 and
- be sure the system is not starting up further)
- go to d:/ps
- type "pss" : you will see that AgfaScript is starting up with :
AgfaScript 2000.000 16:15:43 Jun 20 1996
%%[ Warning: Kanji ProcSet not found ]%%
-- jobbegin --
- type "(filename) run"

05.01.00 page 26 of 39 05.01.00 page 15 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Mixed types are allowed.
- lpm is keeping track of not supported items in "d:/[Link]"
3.4 Checklist for Drystar / MG3000 DICOM installation problems
All the questions below you have to answer with "yes", if you want to have a working DICOM usage :
connection:
lp menu file1 .... filen
• Is the application entity title (= "apip_dest" of ART1) set at DICOM host? (Recommendation: only
use uppercase. Use underscore (_) if two words. DICOM convention!. Example: DRYSTAR_3) with menu : !810
• Is "n_io_id" (and e_io_id) in ART1 set to 11? ...
!810
• Is "inet_addr" in ART0, ART1 and DICOM host the same?
or
• Is "hostname" in ART0, ART1 and DICOM host the same? (Hostname is not case sensitive, but
use only lowercase, to distinguish between hostname and ae_title = UNIX and TCP/IP lp menu file1 ... filen tail
convention. Example: drystar_3)
with menu : !810
• Is port in ART1 left at default, i.e. 3027? (only necessary for APIP network communication)
...
• Is the "local_port" in PMSXXX22 (and so on) as well as on DICOM host set to 104? (If DICOM and tail : !810
host is fixed to a certain port, enter this number in PMS).
4. [Link] :
• Is "ilut_vbpp_in" in NIPXXX11 set to "16", in case you have a 12 bit image sent from the DICOM ------------
host? (see below) image driver for Sun raster files.
helpers to print TIFF and RAS files ([Link], [Link]) can be found on
Troubleshooting DICOM: MEGA software.
From hardware point of view, there is no difference between DICOM and APIP. This means that
PING will be the most important command to check whether the physical connection is present. See 4.4.2 Readme File (status Nov. 97) of MPS Floppy
also APPENDIX: Troubleshooting Ethernet Connections, page 35. Contents of MPS
===============
1. [Link] :
For software problems please check [Link] message ASCI PMS.
------------
The most important document for troubleshooting will be the DICOM conformance statement
AgfaScript software
(delivered on the IMOS DICOM floppy in .PDF format: \IMOS\DCM\english\doc\) and the DICOM
conformance statement of the DICOM modality. By comparing both, you probably can find the
2. directory fonts/ with fonts for AgfaScript
reason for the problem.
---------------------------------------------
3. directory kernel/ with startup files for AgfaScript
DICOM configuration with IMOS DICOM configurator fails: "Too little memory...."
------------------------------------------------------
Symptom: You want to configure DICOM on Drystar 2000, Drystar 3000 or MG3000. At the end of
the configuration you get the message that the configuration was not successfull: Too little memory. 4. [Link] :
Reason: Memory management system in the controller was not able to give your device enough ------------
memory for DICOM. Most likely the installation is not released. Line Printer Deamon software
Possible Cure: use lp or lpr on workstation
1) Only use one association for the DICOM inputs. Or.... ex. lpr -P drystar file
2) Reconfigure the system for low memory consumption: Remove all inputs that are not used. lp -d drystar file
Example: In case you have input 3 configured for TPG, configure input 3 as "no physical input".
See also description of MeGa3P32 on Digimail ([Link]): There a memory consumption list 5. [Link] :
is included. -------------
ftpp works in combination with ftp (File transfer Protocol).
3.5 How to configure DICOM manually At startup, it creates a directory "d:/spool" (if it does not exist).
You never should configure DICOM manually. Only do it in case the DICOM configuration fails It looks each 30 sec in the directory "d:/spool" for a file, gives the
out of an unknown reason. file to the B module
and removes the file in "d:/spool".
− Download corresponding DCMXXXX zipfile (DCM31522 for MeGa3P30 or DCM31550 for
MeGa3P31 or DCM32942 (or higher)) to the C: drive of the controller. It is placed in the BE SURE THAT THE D: PARTITION IS BIG ENOUGH TO SPOOL THE IMAGE FILES.
\IMOS\DCM\BIN directory. Unzip it via e.g. "unzip -o [Link]" (unprot c: before).
− NVE SYSXXX00 use ftp on workstation
− change parameter no_nmods from 1 to 2 (assuming, that Ethernet APIP was already configured). ex. ftp [Link] or ftp drystar with login="Agfa" and
password="Printer"
bin

05.01.00 page 16 of 39 05.01.00 page 25 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
− If you want to configure more DICOM associations (max. will be 5) then change no_nmods (=
4.4 Readme Files MPS / MNR number of network modules) from 1 to 1 + x (where x = number of associations)
4.4.1 Readme File (status Nov. 97) of MNR Floppy − Change parameter nmodprog_name to "[Link]"
Contents of MNR − RESET the controller
=============== − Edit CMNXXX21, CMNXXX22 and so on:
1. [Link] : ∗ set cmnprg_name to [Link] for CMNXXX21
------------
∗ set cmnprg_name to [Link] (or CRX or PSO) for all DICOM inputs (from CMNXXX22
Line Printer Deamon software
on).
use lp or lpr on workstation
− RESET MG3000
ex. lpr -P drystar file
lp -d drystar file − Check if all modules are loaded
.......
2. [Link] : CMNXXX21
------------- ETHXXX21
ftpp works in combination with ftp (File transfer Protocol). CMNXXX22
At startup, it creates a directory "d:/spool" (if it does not exist). PMSXXX22
It looks each 30 sec in the directory "d:/spool" for a file, gives the
file to the B module and observe increase of subdirectories ACQX on E: partition or F: partition for Drystar 2000 and
and removes the file in "d:/spool". 3000. Also do not forget to check the disk space quota for those new users. The "util" parameter in
the [Link] file may need to be set to 900000.
BE SURE THAT THE D: PARTITION IS BIG ENOUGH TO SPOOL THE IMAGE FILES.
For customization of DICOM see the previous and following sections.
use ftp on workstation
ex. ftp [Link] or ftp drystar with login="Agfa" and 3.5.1 SYS parameters with DICOM (example: 4 associations)
password="Printer" Example of Drystar 3000:
bin DI3_D:\> nve SYSXXX00
put file mode 1
quit minbuf 106 106 46 0
maxbuf 108 108 48 0
3. [Link] : mmstasks 31
------------ bmod_qsize 50
"helper" for DSP to handle "LPD + menu file + image files" cmod_qsize 50
- supported items in menu file : no_cmods 1
- "format string" cmodprg_name "[Link]"
a line with "string agfa_layout_id" must be found in file
bmodprg_name "[Link]"
"c:/[Link]"
ex.: command on workstation : no_amods 4 4 acquisition modules. Must be a Drystar 3000! (input 4 = local
lp -d drystar menu [Link] [Link] keypad)
menu file contains : amodprg_name "[Link]"
!810 mmslog 1
format 2-up no_nmods 5 Example: 5 network modules: e.g. 1 APIP, 1 PSO, 1 CRX, 2
... PMS
!810 nmodprg_name "[Link]"
"c:/[Link]" contains : mms_turbo_delay 600
2-up 3021 mfxprg_name "[Link]"
4-up 3022 mfsprg_name "[Link]"
... tnxprg_name "[Link]"
=> [Link] and [Link] will be printed on layout 3021.

- "exposure positive/negative" : sets the image polarity

- "dmin [Link]" : sets dmin value on film
- "dmax [Link]" : sets dmax value on film
- "orientation portrait/landscape" : defines an image rotation
- "curve xxx" : defines a user taste (kanamori=100;linear=200;..)
- "interpolation magnif_type smooth_factor"
- "xmax xxx" : defines the image width for binary images
- "ymax yyy" : defines the image height for binary images
- image file can be PS-, TIF-, RAS- or binary file.

05.01.00 page 24 of 39 05.01.00 page 17 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

4.2 Imos Postscript / MNR Configurator Screen:

3.5.2 Loaded Drivers with DICOM and MeGa3P32
(In this example of Drystar 3000: 1 association PSO; 1 association CRX, 2 associations PMS)
Driver Comment
ARTXXX00 {0..23} APIP Routing Table
SYSXXX00 {0..0} SYSTEMS driver
MGAXXX00 {0..0}
MFSXXX00 {0..0}
RTTXXX00 {0..0}
ETSXXX00 {0..0}
NETXXX00 {0..0} Network Driver
MFXXXX00 {0..0}
CANXXX00 {0..0} CAN Bus driver
BMDXXX31 {0..0}
ACQXXX01 {0..0}
TIFXXX01 {0..0} Input 1 = TIF!
Postscript Configuration Screen: Depending on the MNR Configuration Screen: Depending on the
MNUXXX01 {0..64}
installed SW in the MG3000 (MNR or MPS) different installed SW in the MG3000 (MNR or MPS) different
LCDXXX01 {0..0} menus are enabled or disabled. menus are enabled or disabled.
ACQXXX02 {0..0}
TIFXXX02 {0..0} Input 2 = TIF!
Only very little customization is necessary with the
MNUXXX02 {0..64}
Postscript / MNR SW installed:
LCDXXX02 {0..0}

Select a colortable for Drystar 2000 (1 - 20) to
ACQXXX03 {0..0} Input 3 not used adjust the colors
ACQXXX04 {0..0}
Select a user taste sub_id (70-230) to change
TIFXXX04 {0..0} the contrast of the image.
MNUXXX04 {0..64}
Select Film Background to adjust the density /
ULDXXX04 {0..0} Input 4 = local display (= TIF) color of the film background.
CMNXXX11 {0..0} Drivers for the print engine (up to ALFXXX11)
CPEXXX11 {0..0}
ICDXXX11 {0..0}
NIPXXX11 {0..0}
DSPXXX11 {0..0}
CPDXXX11 {0..0}
ICIXXX11 {0..0}
ALFXXX11 {0..0}
DR3XXX11 {0..0} 4.3 Remark to page size
TIFXXX40 {0..0} Normally, a ps job defines for which pagesize it is made. Then there are no problems: If the policy is
CMNXXX21 {0..0} best fit, the jobs is always printed :
ETHXXX21 {0..0} APIP network driver • if the pagesize of printer is smaller the image is reduced to fit on film
CMNXXX22 {0..0} • if the pagesize of the printer is bigger the image is centered on film
PSOXXX22 {0..0} PSO (= Storage SCU for SC; I+P) DICOM driver • if the policy is dispenser (or printable area) dependent, the job is printed if the right film is in the
ALFXXX22 {0..0} printer.
CMNXXX23 {0..0}
CRXXXX23 {0..0} CRX (= Storage SCU for CR; I) DICOM driver
CMNXXX24 {0..0}
PMSXXX24 {0..0} PMS (= Print Management) DICOM driver
CMNXXX25 {0..0}
PMSXXX25 {0..0} PMS (= Print Management) DICOM driver
If the ps job does NOT contain the pagesize, we define a default pagesize, so that the previous rules can be
applied.
The dimension is, as defined in PS, 1/72th of an inch (one inch equals 2,54 cm;
example: 21 cm x 27 cm =
8,27" x 10,62" = 595 x 765 (PS page units)

05.01.00 page 18 of 39 05.01.00 page 23 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

3.5.3 Where to tweak for DICOM (adjustments)

[Link] PSO
Parameter Comment
IMOS
MG3000 mms_pso 10 4 2 10 0 0
MPS2.33
a:\winstall
1/2
max_pdu_length 65536
calling_AE The application entity title. It may differ from ART1 "apip_dest" : Set it at
Attention:
"MG3000_PSO" DICOM host or change it here (only use uppercase. Use underscore (_) if
SW Versions are subject two words. DICOM convention!)
to change.
See DIGIMAIL* for updates. prio 100
*DIGIMAIL = Bulletin Board MG3000.
Modem no. +49 89 6207 7777 UID_stem "[Link].1"
extra_logging 0
apip2dicom
"[Link]"
Hard MPS32935
MG3000 MNR32925
MG3000 offline 0
MPS32941
disk
1/1 1/1
dicomDirPath "m:"
patient name "" Some workstations need a patient name. In this case enter here e.g. "Mr.
Image Formats:
[Link]
AGFA + Picker Postscript Image Formats: TIFF + S Anonymous"
Protocols: PAP + lp/lpr + FTP Protocols: lp/lpr +

[Link] CRX
Overview MPS mms_crx 1 1 1 0 0 0
Component / Image PRG Description Protocol max_pdu_length 65536
File Format Name calling_AE "MG3000_CR" The application entity title. It may differ from ART1 "apip_dest" :
Set it at DICOM host or change it here (only use uppercase. Use
AGFA [Link] A clone from postscript from LPD or FTP underscore (_) if two words. DICOM convention!)
Postscript Adobe or PAP prio 100
UID_stem "[Link].1"
Picker [Link] Short term postscript LPD or FTP extra_logging 0
Postscript implementation. Works only for or PAP apip2dicom "[Link]"
Picker and Park Medical. process_img 1 1= log e relativ image. 0 = od. 2 = od relative. Do not modify. ADC
will change this parameter at runtime.
Currently (June 98) MPS32941 has to be used together with ECU32936
MPS32935 has to be used together with ECU32932 (IMOS PS takes care for it: It looks to the
installed ECU version and compares it with the file "[Link]" on the Postscript ZIP file floppy.) [Link] PMS
local_port 104 "local_port" must be the same in PMSXXX2Y as well as on
Overview MNR DICOM host. If DICOM host is fixed to a certain port, enter this
Component / Image PRG Description Protocol number here.
File Format Name mms_pms 10 3 2 10
max_pdu_length 65536
TIFF or [Link] or [Link] Sending TIF or Sunraster images LPD or FTP extra_logging 0
Sunraster via LPD or FTP modality "AM"
patient_id_stem "MG" *
Menu Support [Link] Emulation of the Helios interface LPD UID_stem "[Link].1"
media_sizes 255 *
Currently (June 97) MNR32932 has to be used together with ECU32932 (IMOS PS takes care for it: if_using_pmstst 0
It looks to the installed ECU version and compares it with the file "[Link]" on the MNR ZIP file nevent_enabled 0
floppy.) film_type 0 *
no_copies 1 *
film_backg 255 0 0 0 *
non_exp 255 0 0 0 *
magnif_type 2 *
smooth_factor 140 *

05.01.00 page 22 of 39 05.01.00 page 19 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
4 Postscript
dbmin 100 *
dbmax 35000 * 4.1 Introduction
cs_table 0 * The postscript configurator is able to configure Postscript, TIFF or Sunraster image format as
trim_flag 1 * network input. As network protocol lp/lpr, ftp or pap can be used.
trim 200 0 0 0 *
utl_id 3 *
utl_subid 0 *
printer_type 1
text_flag 0 *
annotation1 "" *
annotation2 "" *
annotation3 "" *
annotation4 "" *
annotation5 "[Link]" *
annotation6 "" *
polarity 0 *
rotation 0 *
metric_printing 0 *
image_numbering 0 *
bw_w_center 128 *
bw_w_width 255 *
color_window 100 *
color_level 0 *
resolution 10000 *
ipl_id 0
ipl_subid 0
add_WL 0 Sketch 8: File Formats for Network Image Transmission
*See MG3000 documentation section 3 for an explanation
Attention: Those parameters are only used if not sent from the modality.

Sketch 9: Network Protocols for Image Transmission

Depending on the floppy, that is inserted in the PC or device floppy drive, different network modules
can be installed:
05.01.00 page 20 of 39 05.01.00 page 21 of 39
 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
4 Postscript
dbmin 100 *
dbmax 35000 * 4.1 Introduction
cs_table 0 * The postscript configurator is able to configure Postscript, TIFF or Sunraster image format as
trim_flag 1 * network input. As network protocol lp/lpr, ftp or pap can be used.
trim 200 0 0 0 *
utl_id 3 *
utl_subid 0 *
printer_type 1
text_flag 0 *
annotation1 "" *
annotation2 "" *
annotation3 "" *
annotation4 "" *
annotation5 "[Link]" *
annotation6 "" *
polarity 0 *
rotation 0 *
metric_printing 0 *
image_numbering 0 *
bw_w_center 128 *
bw_w_width 255 *
color_window 100 *
color_level 0 *
resolution 10000 *
ipl_id 0
ipl_subid 0
add_WL 0 Sketch 8: File Formats for Network Image Transmission
*See MG3000 documentation section 3 for an explanation
Attention: Those parameters are only used if not sent from the modality.

Sketch 9: Network Protocols for Image Transmission

Depending on the floppy, that is inserted in the PC or device floppy drive, different network modules
can be installed:
05.01.00 page 20 of 39 05.01.00 page 21 of 39
 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

3.5.3 Where to tweak for DICOM (adjustments)

[Link] PSO
Parameter Comment
IMOS
MG3000 mms_pso 10 4 2 10 0 0
MPS2.33
a:\winstall
1/2
max_pdu_length 65536
calling_AE The application entity title. It may differ from ART1 "apip_dest" : Set it at
Attention:
"MG3000_PSO" DICOM host or change it here (only use uppercase. Use underscore (_) if
SW Versions are subject two words. DICOM convention!)
to change.
See DIGIMAIL* for updates. prio 100
*DIGIMAIL = Bulletin Board MG3000.
Modem no. +49 89 6207 7777 UID_stem "[Link].1"
extra_logging 0
apip2dicom
"[Link]"
Hard MPS32935
MG3000 MNR32925
MG3000 offline 0
MPS32941
disk
1/1 1/1
dicomDirPath "m:"
patient name "" Some workstations need a patient name. In this case enter here e.g. "Mr.
Image Formats:
[Link]
AGFA + Picker Postscript Image Formats: TIFF + S Anonymous"
Protocols: PAP + lp/lpr + FTP Protocols: lp/lpr +

[Link] CRX
Overview MPS mms_crx 1 1 1 0 0 0
Component / Image PRG Description Protocol max_pdu_length 65536
File Format Name calling_AE "MG3000_CR" The application entity title. It may differ from ART1 "apip_dest" :
Set it at DICOM host or change it here (only use uppercase. Use
AGFA [Link] A clone from postscript from LPD or FTP underscore (_) if two words. DICOM convention!)
Postscript Adobe or PAP prio 100
UID_stem "[Link].1"
Picker [Link] Short term postscript LPD or FTP extra_logging 0
Postscript implementation. Works only for or PAP apip2dicom "[Link]"
Picker and Park Medical. process_img 1 1= log e relativ image. 0 = od. 2 = od relative. Do not modify. ADC
will change this parameter at runtime.
Currently (June 98) MPS32941 has to be used together with ECU32936
MPS32935 has to be used together with ECU32932 (IMOS PS takes care for it: It looks to the
installed ECU version and compares it with the file "[Link]" on the Postscript ZIP file floppy.) [Link] PMS
local_port 104 "local_port" must be the same in PMSXXX2Y as well as on
Overview MNR DICOM host. If DICOM host is fixed to a certain port, enter this
Component / Image PRG Description Protocol number here.
File Format Name mms_pms 10 3 2 10
max_pdu_length 65536
TIFF or [Link] or [Link] Sending TIF or Sunraster images LPD or FTP extra_logging 0
Sunraster via LPD or FTP modality "AM"
patient_id_stem "MG" *
Menu Support [Link] Emulation of the Helios interface LPD UID_stem "[Link].1"
media_sizes 255 *
Currently (June 97) MNR32932 has to be used together with ECU32932 (IMOS PS takes care for it: if_using_pmstst 0
It looks to the installed ECU version and compares it with the file "[Link]" on the MNR ZIP file nevent_enabled 0
floppy.) film_type 0 *
no_copies 1 *
film_backg 255 0 0 0 *
non_exp 255 0 0 0 *
magnif_type 2 *
smooth_factor 140 *

05.01.00 page 22 of 39 05.01.00 page 19 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

4.2 Imos Postscript / MNR Configurator Screen:

3.5.2 Loaded Drivers with DICOM and MeGa3P32
(In this example of Drystar 3000: 1 association PSO; 1 association CRX, 2 associations PMS)
Driver Comment
ARTXXX00 {0..23} APIP Routing Table
SYSXXX00 {0..0} SYSTEMS driver
MGAXXX00 {0..0}
MFSXXX00 {0..0}
RTTXXX00 {0..0}
ETSXXX00 {0..0}
NETXXX00 {0..0} Network Driver
MFXXXX00 {0..0}
CANXXX00 {0..0} CAN Bus driver
BMDXXX31 {0..0}
ACQXXX01 {0..0}
TIFXXX01 {0..0} Input 1 = TIF!
Postscript Configuration Screen: Depending on the MNR Configuration Screen: Depending on the
MNUXXX01 {0..64}
installed SW in the MG3000 (MNR or MPS) different installed SW in the MG3000 (MNR or MPS) different
LCDXXX01 {0..0} menus are enabled or disabled. menus are enabled or disabled.
ACQXXX02 {0..0}
TIFXXX02 {0..0} Input 2 = TIF!
Only very little customization is necessary with the
MNUXXX02 {0..64}
Postscript / MNR SW installed:
LCDXXX02 {0..0}

Select a colortable for Drystar 2000 (1 - 20) to
ACQXXX03 {0..0} Input 3 not used adjust the colors
ACQXXX04 {0..0}
Select a user taste sub_id (70-230) to change
TIFXXX04 {0..0} the contrast of the image.
MNUXXX04 {0..64}
Select Film Background to adjust the density /
ULDXXX04 {0..0} Input 4 = local display (= TIF) color of the film background.
CMNXXX11 {0..0} Drivers for the print engine (up to ALFXXX11)
CPEXXX11 {0..0}
ICDXXX11 {0..0}
NIPXXX11 {0..0}
DSPXXX11 {0..0}
CPDXXX11 {0..0}
ICIXXX11 {0..0}
ALFXXX11 {0..0}
DR3XXX11 {0..0} 4.3 Remark to page size
TIFXXX40 {0..0} Normally, a ps job defines for which pagesize it is made. Then there are no problems: If the policy is
CMNXXX21 {0..0} best fit, the jobs is always printed :
ETHXXX21 {0..0} APIP network driver • if the pagesize of printer is smaller the image is reduced to fit on film
CMNXXX22 {0..0} • if the pagesize of the printer is bigger the image is centered on film
PSOXXX22 {0..0} PSO (= Storage SCU for SC; I+P) DICOM driver • if the policy is dispenser (or printable area) dependent, the job is printed if the right film is in the
ALFXXX22 {0..0} printer.
CMNXXX23 {0..0}
CRXXXX23 {0..0} CRX (= Storage SCU for CR; I) DICOM driver
CMNXXX24 {0..0}
PMSXXX24 {0..0} PMS (= Print Management) DICOM driver
CMNXXX25 {0..0}
PMSXXX25 {0..0} PMS (= Print Management) DICOM driver
If the ps job does NOT contain the pagesize, we define a default pagesize, so that the previous rules can be
applied.
The dimension is, as defined in PS, 1/72th of an inch (one inch equals 2,54 cm;
example: 21 cm x 27 cm =
8,27" x 10,62" = 595 x 765 (PS page units)

05.01.00 page 18 of 39 05.01.00 page 23 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
− If you want to configure more DICOM associations (max. will be 5) then change no_nmods (=
4.4 Readme Files MPS / MNR number of network modules) from 1 to 1 + x (where x = number of associations)
4.4.1 Readme File (status Nov. 97) of MNR Floppy − Change parameter nmodprog_name to "[Link]"
Contents of MNR − RESET the controller
=============== − Edit CMNXXX21, CMNXXX22 and so on:
1. [Link] : ∗ set cmnprg_name to [Link] for CMNXXX21
------------
∗ set cmnprg_name to [Link] (or CRX or PSO) for all DICOM inputs (from CMNXXX22
Line Printer Deamon software
on).
use lp or lpr on workstation
− RESET MG3000
ex. lpr -P drystar file
lp -d drystar file − Check if all modules are loaded
.......
2. [Link] : CMNXXX21
------------- ETHXXX21
ftpp works in combination with ftp (File transfer Protocol). CMNXXX22
At startup, it creates a directory "d:/spool" (if it does not exist). PMSXXX22
It looks each 30 sec in the directory "d:/spool" for a file, gives the
file to the B module and observe increase of subdirectories ACQX on E: partition or F: partition for Drystar 2000 and
and removes the file in "d:/spool". 3000. Also do not forget to check the disk space quota for those new users. The "util" parameter in
the [Link] file may need to be set to 900000.
BE SURE THAT THE D: PARTITION IS BIG ENOUGH TO SPOOL THE IMAGE FILES.
For customization of DICOM see the previous and following sections.
use ftp on workstation
ex. ftp [Link] or ftp drystar with login="Agfa" and 3.5.1 SYS parameters with DICOM (example: 4 associations)
password="Printer" Example of Drystar 3000:
bin DI3_D:\> nve SYSXXX00
put file mode 1
quit minbuf 106 106 46 0
maxbuf 108 108 48 0
3. [Link] : mmstasks 31
------------ bmod_qsize 50
"helper" for DSP to handle "LPD + menu file + image files" cmod_qsize 50
- supported items in menu file : no_cmods 1
- "format string" cmodprg_name "[Link]"
a line with "string agfa_layout_id" must be found in file
bmodprg_name "[Link]"
"c:/[Link]"
ex.: command on workstation : no_amods 4 4 acquisition modules. Must be a Drystar 3000! (input 4 = local
lp -d drystar menu [Link] [Link] keypad)
menu file contains : amodprg_name "[Link]"
!810 mmslog 1
format 2-up no_nmods 5 Example: 5 network modules: e.g. 1 APIP, 1 PSO, 1 CRX, 2
... PMS
!810 nmodprg_name "[Link]"
"c:/[Link]" contains : mms_turbo_delay 600
2-up 3021 mfxprg_name "[Link]"
4-up 3022 mfsprg_name "[Link]"
... tnxprg_name "[Link]"
=> [Link] and [Link] will be printed on layout 3021.

- "exposure positive/negative" : sets the image polarity

- "dmin [Link]" : sets dmin value on film
- "dmax [Link]" : sets dmax value on film
- "orientation portrait/landscape" : defines an image rotation
- "curve xxx" : defines a user taste (kanamori=100;linear=200;..)
- "interpolation magnif_type smooth_factor"
- "xmax xxx" : defines the image width for binary images
- "ymax yyy" : defines the image height for binary images
- image file can be PS-, TIF-, RAS- or binary file.

05.01.00 page 24 of 39 05.01.00 page 17 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Mixed types are allowed.
- lpm is keeping track of not supported items in "d:/[Link]"
3.4 Checklist for Drystar / MG3000 DICOM installation problems
All the questions below you have to answer with "yes", if you want to have a working DICOM usage :
connection:
lp menu file1 .... filen
• Is the application entity title (= "apip_dest" of ART1) set at DICOM host? (Recommendation: only
use uppercase. Use underscore (_) if two words. DICOM convention!. Example: DRYSTAR_3) with menu : !810
• Is "n_io_id" (and e_io_id) in ART1 set to 11? ...
!810
• Is "inet_addr" in ART0, ART1 and DICOM host the same?
or
• Is "hostname" in ART0, ART1 and DICOM host the same? (Hostname is not case sensitive, but
use only lowercase, to distinguish between hostname and ae_title = UNIX and TCP/IP lp menu file1 ... filen tail
convention. Example: drystar_3)
with menu : !810
• Is port in ART1 left at default, i.e. 3027? (only necessary for APIP network communication)
...
• Is the "local_port" in PMSXXX22 (and so on) as well as on DICOM host set to 104? (If DICOM and tail : !810
host is fixed to a certain port, enter this number in PMS).
4. [Link] :
• Is "ilut_vbpp_in" in NIPXXX11 set to "16", in case you have a 12 bit image sent from the DICOM ------------
host? (see below) image driver for Sun raster files.
helpers to print TIFF and RAS files ([Link], [Link]) can be found on
Troubleshooting DICOM: MEGA software.
From hardware point of view, there is no difference between DICOM and APIP. This means that
PING will be the most important command to check whether the physical connection is present. See 4.4.2 Readme File (status Nov. 97) of MPS Floppy
also APPENDIX: Troubleshooting Ethernet Connections, page 35. Contents of MPS
===============
1. [Link] :
For software problems please check [Link] message ASCI PMS.
------------
The most important document for troubleshooting will be the DICOM conformance statement
AgfaScript software
(delivered on the IMOS DICOM floppy in .PDF format: \IMOS\DCM\english\doc\) and the DICOM
conformance statement of the DICOM modality. By comparing both, you probably can find the
2. directory fonts/ with fonts for AgfaScript
reason for the problem.
---------------------------------------------
3. directory kernel/ with startup files for AgfaScript
DICOM configuration with IMOS DICOM configurator fails: "Too little memory...."
------------------------------------------------------
Symptom: You want to configure DICOM on Drystar 2000, Drystar 3000 or MG3000. At the end of
the configuration you get the message that the configuration was not successfull: Too little memory. 4. [Link] :
Reason: Memory management system in the controller was not able to give your device enough ------------
memory for DICOM. Most likely the installation is not released. Line Printer Deamon software
Possible Cure: use lp or lpr on workstation
1) Only use one association for the DICOM inputs. Or.... ex. lpr -P drystar file
2) Reconfigure the system for low memory consumption: Remove all inputs that are not used. lp -d drystar file
Example: In case you have input 3 configured for TPG, configure input 3 as "no physical input".
See also description of MeGa3P32 on Digimail ([Link]): There a memory consumption list 5. [Link] :
is included. -------------
ftpp works in combination with ftp (File transfer Protocol).
3.5 How to configure DICOM manually At startup, it creates a directory "d:/spool" (if it does not exist).
You never should configure DICOM manually. Only do it in case the DICOM configuration fails It looks each 30 sec in the directory "d:/spool" for a file, gives the
out of an unknown reason. file to the B module
and removes the file in "d:/spool".
− Download corresponding DCMXXXX zipfile (DCM31522 for MeGa3P30 or DCM31550 for
MeGa3P31 or DCM32942 (or higher)) to the C: drive of the controller. It is placed in the BE SURE THAT THE D: PARTITION IS BIG ENOUGH TO SPOOL THE IMAGE FILES.
\IMOS\DCM\BIN directory. Unzip it via e.g. "unzip -o [Link]" (unprot c: before).
− NVE SYSXXX00 use ftp on workstation
− change parameter no_nmods from 1 to 2 (assuming, that Ethernet APIP was already configured). ex. ftp [Link] or ftp drystar with login="Agfa" and
password="Printer"
bin

05.01.00 page 16 of 39 05.01.00 page 25 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

put file Example .IDF File Comment

quit Example 1: The left part of the table is the DICOM layout
8INX10IN\PORTRAIT\STANDARD\1,1 1011
8INX10IN\PORTRAIT\STANDARD\2,1 1012
description. It is mapped to the AGFA layout
6. [Link] : ID. See file "[Link]" on the service PC for a
8INX10IN\PORTRAIT\STANDARD\1,2 1021
----------- 8INX10IN\PORTRAIT\STANDARD\2,2 1022 description of the layouts. This file has to be
"helper" for DSP to handle postscript files (level I and II) .............. edited on the laptop, can be renamed however
...............
as you want (e.g. [Link]) and downloaded
7. [Link] : to the C: partition again. Example: You want,
------------ Example 2: that whenever the layout 8x10 1/0 portrait is
"helper" for DSP to handle Picker postscript files (short term 8INX10IN\PORTRAIT\STANDARD\1,1 800 selected at the host side, the layout 1/0
implementation as in MEGA31) 8INX10IN\PORTRAIT\STANDARD\2,1 1012
portrait for Drystar 2000 is selected (= AGFA
These files must contain following items : 8INX10IN\PORTRAIT\STANDARD\1,2 1021
8INX10IN\PORTRAIT\STANDARD\2,2 1022 layout ID 800). Edit the corresponding line as
- line a : /draw.....
............... shown beneath in example 2.
ex.: "/drawcolorimage" ............... Before the file can be selected in the EDIT
line a+1 : xxx yyy z with xxx = width, yyy = heigt, z = #bits per
PROFILE Screen it must already be present
pixel ex.: "1280 1024 8"
on the C: partition.
- line b : draw
ex.: "drawcolorimage"
follewed by lines of hex numbers Currently (10/97) by default following IDF files do exist (they are downloaded with the
Following item may be included : [Link] file):
[Link] 7567 27-NOV-1996 16:00:56 rwx
- line c : "currentfile rgbmap readhexstring pop pop" PMS_3XX.IDF 2691 28-NOV-1996 9:57:38 rwx
followed by 6 digit hex numbers PMS_8XX.IDF 1041 27-NOV-1996 16:01:02 rwx
PMS_DI.IDF 3016 27-NOV-1996 16:01:08 rwx
8. [Link] :
-------------- Example .CFG file Comment
Ethertalk driver FOR_CT1.PMS In this case the Dmax is set to 2.8.
00
pms_virgin_cfg 0
The parameters defined in .pms files are only active in case they
9. [Link] : dbmax 28000 are not sent from the host!
------------ The file is automatically created with the DICOM configurator in
network interface that supports the Printer Access Protocol. the EDIT PMS Screen. Advanced users also can make a NVE on
e.g. PMSXXX22 and rename the so created .U00 file accordingly
10. [Link] : (e.g. [Link]).
----------------
stand alone test program to test the Printer Access Protocol. When finished with the EDIT PMS Profile screen (you also will be asked to edit the disk quota in
between) select CANCEL and CONNECT - EXIT to leave the DICOM configurator.
Remark : In case of any problems see sections
Some general remarks in case a PS-file comes in the Drystar queue but is • Checklist for Drystar / MG3000 DICOM installation problems
not printed out : • Troubleshooting DICOM connections
- The processing of postscript files can take a while...
To see if the processing is still busy, look at "d:/ps". 3.3 Adjustments on DICOM Modality Side
Normally, there will be some files "...%img" which will grow while the
processing is busy.
At the end of the processing, the files are deleted. After DICOM configuration tell the technician at the DICOM user side:
- try the same file on an office PS-printer (for example with ADOBE-PS)
• the inet_addr of ART0 (or 1, which has to be the same).
If it is not printed on such a printer, there is a big chance that the
PS-file itself is suspected. • the host_name of ART0 (or 1, which has to be the same)
- An easy way to find out if AgfaScript is able to understand a PS-file
(without any interference with • the "application entity title", what is the "apip_dest" of ART1
our acquisition,spooler and controler software) is as follows :
- reset the Drystar • the "listening port", what is port 104 (Parameter: local_port in PMSXXX22 and
- be sure the system is not starting up further)
- go to d:/ps
- type "pss" : you will see that AgfaScript is starting up with :
AgfaScript 2000.000 16:15:43 Jun 20 1996
%%[ Warning: Kanji ProcSet not found ]%%
-- jobbegin --
- type "(filename) run"

05.01.00 page 26 of 39 05.01.00 page 15 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
- after a while following things should come out :
%[ Error: Map type 3 rows 180 cols 1888 bits 8
%[ Error: xoffset 0 yoffset 0 nrofseps 3 cacheflag 0
%[ Error: Bitmap 0 rows 180 cols 1888 xoffset 0 yoffset 0
%[ Error: bits 8 rmus_row 472 tail_rels 0 rmus 84960
0x4f16b0

- if this is the case, AgfaScript is able to understand the PS-

file.
- type "^D" or "^Z" to see "-- jobbegin --"
- type "psexit" to return to shell

Screen 3

Here you can see an example of an EDIT PMS PROFILER FILE session. The result of this session
will be a [Link] file, a FOR_CT2.PMS and FOR_CT1.PMS file.

Note: To every AE title you can make your own ".pms" file, already known from the .u00 files made
during customization. So every DICOM connection can be customized.

Explanation:
Example [Link] file Comment
[CT1] • CT1 and CT2 are the AE Titles of the connected modalities
IDF = C:/[Link]
CFG = D:/FOR_CT1.PMS • The Idf file (IDF = Image Display Format) is a layout mapping file,
that maps the DICOM layout to a certain AGFA layout (see example
[CT2] below)
IDF = C:/[Link] • The CFG file contains the PMS parameter settings for the
CFG = D:/FOR_CT2.PMS
corresponding AE title i.e. connected modality

Harddisk
[Link] (DCM layout mapping file)
Partition C:

Partition D:
[Link]
MG [CT1]
IDF = C:/[Link]
DICOM DICOM CFG = D:/FOR_CT1.PMS
Modality Modality
"CT1" "CT2" Partition E:
[CT2]
IDF = C:/[Link]
LR3300
wants dmax 2.8 CFG = D:/FOR_CT2.PMS
wants linear UTL
FOR_CT1.PMS
dbmax 28000

FOR_CT2.PMS
utl_id 1

05.01.00 page 14 of 39 05.01.00 page 27 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

PSO:
4.5 Troubleshooting MPS By checking the PSO (Storage SCU for SC - Secondary Capture - image and print parameters) box
the SC storage SCU application will be installed on the connected device. From MeGa 3.32 on the
1. Some general remarks in case a PS-file comes in the printer queue but PSO application will be installed. For previous MeGa releases the SNC application (which does not
is not printed out : support Print Storage) will be installed. One will still need to enter the APIP destination in the
- The processing of postscript files can take a while... correct ART table entry. PSO as well as SNC allow only one association.
To see if the processing is still busy, look at "d:/ps". This option has to be selected in case you want to send DICOM images to an IMPAX workstation.
Normally, there will be some files "...%img" which will grow while the Exception: If ADC (computed radiography) images are being sent to a workstation select "CRX"
processing is busy. (see below).
At the end of the processing, the files are deleted. CRX:
- try the same file on an office PS-printer (for example with ADOBE-PS) By checking the CRX (Storage SCU for CR - Computed Radiography - image parameters) box the
If it is not printed on such a printer, there is a big chance that the CR storage SCU application will be installed on the connected device. One will still need to enter
PS-file itself is suspected. the APIP destination in the correct ART table entry. CRX allows only one association. The CRX
- An easy way to find out if AgfaScript is able to understand a PS-file application is supported from MeGa 3.32 on.
(without any interference with This option has to be selected in case you have an ADC connected to the MG3000 (or Drystar
our acquisition,spooler and controler software) is as follows : 3000) and you want to send images (computed radiography) to an IMPAX workstation.
- reset the Drystar PMS:
- be sure the system is not starting up By checking the PMS (Print Manager SCP) box the Print SCP application will be installed on the
- go to d:/ps connected device. PMS allows up to 6 associations, minus the ones already taken for the installed
- type "pss" : you will see that AgfaScript is starting up with : network modules and/or PSO and/or CRX components. A check is made on the number of
AgfaScript 2000.000 16:15:43 Jun 20 1996 entered associations for the PMS component.
%%[ Warning: Kanji ProcSet not found ]%%
This option has to be selected in case you want to send any DICOM image to one of your printers
-- jobbegin --
(LR3300 / Drystar 2000 / Drystar 3000). One association is sufficient to serve several inputs.
- type "(filename) run"
- after a while following things should come out :
Note : depending on the needed application(s) it is possible to check only one, two or all three
%[ Error: Map type 3 rows 180 cols 1888 bits 8
different network configurations together.
%[ Error: xoffset 0 yoffset 0 nrofseps 3 cacheflag 0
%[ Error: Bitmap 0 rows 180 cols 1888 xoffset 0 yoffset 0
Select EDIT PMS Profile only in case you want to customize one or more of the modalities
%[ Error: bits 8 rmus_row 472 tail_rels 0 rmus 84960
0x4f16b0 connected via DICOM. Attention: This only works for MeGa3P32! Example: You want to have
annotations for a certain input or you want to have a different taste look up table (i.e. a different
- if this is the case, AgfaScript is able to understand the PS-file. contrast setting). Note: Parameters changed with the EDIT PMS Profile screen only can be active,
- type "^D" or "^Z" to see "-- jobbegin --" if they are not sent from the connected modality. If they are sent from the connected modality they
- type "psexit" to return to shell will be ignored.

2. the PS job, printed out on our printer, doesn't have the same shape as
the original :
- one or more sides are cut off
- the image is reduced in one corner
- ...
Check the choosen policy :
- if 0 : it is normal that some info is cut off. The PS-job is discribed
for a full film size, but part of the film can't be printed.
- if 1 : indicates a severe problem in PS-job or MPS-software
- if 3 : check the default pagesize
With this policy, a PS-job with defined pagesize, is processed to fit on
the pagesize of the printer.
But if the PS-job doesn't contain a pagesize, we apply our default
pagesize.
Suppose a PS-job is made for A4, but it does not specify this pagesize in
the job, and our default pagesize is 8x10", then all parts of A4 that is
not covered by 8x10" will be lost before the processing is done to fit on
the pagesize of the printer.

05.01.00 page 28 of 39 05.01.00 page 13 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

4.6 Drivers for MPS / MNR

Example: 1 APIP connection. 2 DICOM PMS connection. 1 connection via LP. 1 connection via
FTP. 1 connection via PAP.
ETHXXX21 {0..0}
CMNXXX22 {0..0}
PMSXXX22 {0..0}
CMNXXX23 {0..0}
PMSXXX23 {0..0}
CMNXXX24 {0..0}
CMNXXX25 {0..0}
CMNXXX26 {0..0}
PAPXXX26 (0..0)

DRY_3_32_C:\> nve CMNXXX23

cmnprg_name "[Link]"
>
DRY_3_32_C:\> nve CMNXXX24
cmnprg_name "[Link]"
>
DRY_3_32_C:\> nve CMNXXX25
cmnprg_name "[Link]"
>
DRY_3_32_C:\> nve CMNXXX26
Screen 1 cmnprg_name "[Link]"

• Screen 1 guides you through the program. Select first Setup Port (if required), the INSTALL, then 4.6.1 MPS / MNR Image Parameter Settings: Where to find them again (in DSP11)
CONFIGURE and so on. EDIT PMS PROFILE is only necessary, in case you want to change a
certain setting of the PMS default parameters. DRY_3_32_D:\> type dspxxx11.u00
• At INSTALL the corresponding DCM file gets downloaded. 00
dsp_virgin_cfg 0
• After selection of CONFIGURE, the following screen will be displayed:
film_backg 0 255 255 255 Film Backround values for black&white,
RGB
policy 999 Printable area dependend
pagesize 957 1163 = 33.77 x 41 cm
cs_table 10010 user_taste 100 / cs_table 10

Screen 2

Note: The selection PMS and 1 association is just an example!

05.01.00 page 12 of 39 05.01.00 page 29 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

Difference between one or more DICOM PMS Associations. Example: 3 DICOM Modalities
5 TMX Application connected to an LR3300 Controller

5.1 TMX: General One Association 2 Associations for 3 3 Associations for 3

An MG3000 Medical Gateway can convert images captured from one of the local inputs to TIFF files, for all 3 DICOM DICOM PMS DICOM PMS
which are then sent via Electronic Mail (E-mail) to a doctor's mailbox. There is one E-mail message PMS Modalities Modalities Modalities
per converted image to TIFF file. The TIFF file is added to the E-mail message as an MIME 1.0 Which pins are 22 22 and 23 22 and 23 and 24
attachment, and encoded in base64 encoding. The MG3000 uses the Simple Mail Transfer Protocol used:
(SMTP) from RFC 822, with Multipurpose Internet Mail Extensions (MIME) from RFC 1521. Advantage Less memory usage At least 2 of 3 All 3 modalities can
in LR3300 modalities can have have access to the
Controller access to the LR3300 LR3300 controller
SMPT SMPT
controller whenever it whenever it is needed.
is needed.
Mail Disadvantage If one modality More memory usage in Even more memory
MG Server makes an LR3300 controller usage in LR3300
association, the controller
others have to wait
E-Mail.
Sender: MG3000 until it is released
Attachement: 1 TIF File Which E:\acq5 PMS22 E:\acq5 PMS22 E:\acq5 PMS22
subdirectories E:\acq6 PMS23 E:\acq6 PMS23
Modality are created on E:\acq7 PMS24
E:
5.2 Mail message
An E-mail consists of a subject, a body and an optional attachment. 3.1.2 How to get the DICOM floppy:
Order it via ABC code:
Subject -3V8QZ MG3 DATA INPUT SERVICES DICOM FIRST (=first DICOM connection);software floppy
The subject contains the patient id. IMOS DCM229 (or higher) + licence agreement; DICOM conformance statement +newsletter,
Installation instructions, LCD-keypad if not yet available.
Mail Body -3V8S4 MG3 DATA INPUT SERVICES DICOM SUBS (= subsequent connections); licence
The mail body contains following text: agreement (without floppy; DICOM conformance statement +newsletter, installation instructions)

"Hello,
3.2 IMOS DICOM configurator rev. 2.3.1 or higher
With this mail, you receive a number of TIFF image files. IMOS DICOM 2.31 or higher can only be used for MeGa3P30, MeGa3P31 and MeGa3P32. For
The image files are in base64 encoding format. MeGa2P20 the previous IMOS configurator rev.1.00 has to be used (Upgrade to MeGa3P31
In case of transmission problems, contact your supporting recommended!)
network systems' administrator. If you order DICOM you will get the comfortable Windows based DICOM configurator. It
automatically detects the installed software, either MeGa3P30, MeGa3P31 or MeGa3P32 and
Bye!" downloads the corresponding DCM zipfile (DCM31522 for MeGa3P30 or DCM31550 for MeGa3P31
or DCM32942 (or higher)) to the C: drive of the controller.

Attachment A brief instruction how to use the configurator:

The TIFF file is added as an attachment. • Insert floppy 1 into the PC floppy drive and select "File → execute / run → a:\winstall"
• Start IMOS DICOM by double clicking on the IMOS DICOM icon
• The following screen will be displayed
5.3 Manual TIFF / MAIL installation

SYSXXX00

no_nmods ? (incremented if no_nmods < 1)

no_cmods ? (increment for virgin configuration)

CMNXXX<Output>
cmnprg_name "[Link]"

05.01.00 page 30 of 39 05.01.00 page 11 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

TMXXXX<Output>
mail_artid <Art Table>
mail_to "DoctorX"
mail_from "mg3000"

ARTXXX00 <Art Table>

apip_dest "Mail"
dest_type 0
available 1
n_io_id 12 (Corresponds with TMX output i.e. 12 if TMX is configured on output 12 )
e_io_id 12
port 25 (SMTP)
hostname "MailServer" (Name of Mail Server)
inet_addr "[Link]" (IP Address for Mail Server, this is not always the
same as the IP address of the PC on which the doctor
is working on.)

Sketch 7: Two DICOM modalities in a network. The application determines the output and ART Table to configure. If TMX is reconfigured on the
same machine, then the existing TMX output and ART table are used.
The parameters, ART n_io_id and e_io_id, are set to the TMX output.
Tio parameter TMX mail_artid is set to the TMX ART Table.
In the case of a virgin configuration no_cmods is incremented and no_nmods in incremented if
no_nmods < 1.

5.4 TIFF/MAIL Configuration driver_name

=Description:
The name of the driver that is dealing with TIFF file format.

=Example:
Required Setting NVF Entry
[Link] driver_name "[Link]"

tprio

=Description:
Sketch 8: One or two associations for two DICOM Modalities. Task priority. Priorities run from 10, (high prio) to 255 (low prio).
Do not change this value, unless it is discussed with the MeGa software team.

=Example:

Required Setting NVF Entry

100 tprio 100

pathname

=Description:
The directory root, at which tiff files are created.

=Example:
Required Setting NVF Entry
D:/ pathname D:/

05.01.00 page 10 of 39 05.01.00 page 31 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

dispenser (0..4)

=Description:

The size and the shape of the dispensers (0..4) Of coarse, the monitor compo nent has no
dispensers, but the B module will only send an image to a component if the B module knows that the
component is able to handle the image. The check is done by comparing the image size with the
dispenser size and the requested medium type with the medium type of the sheets in the dispenser.
Therefore up to five dispensers can be defined in terms of medium size and medium type to be able
to receive images from the B module.

=Example:

Required Setting NVF Entry

medium sizes
NO SIZE for dispenser x disp_size_x 0
8 x 10 for dispenser x disp_size_x 1
10 x 14 for dispenser x disp_size_x 2
11 x 14 for dispenser x disp_size_x 3 Sketch 5: APIP and DICOM in a network
14 x 17 for dispenser x disp_size_x 4
14 x 14 for dispenser x disp_size_x 5
A4 for dispenser x disp_size_x 6 The number of pins used for network
A3 for dispenser x disp_size_x 7 connections has nothing to do with
changes in hardware:
medium types
NO TYPE for dispenser x disp_type_x 0 We are using for all network connections
paper for dispenser x disp_type_x 1 the network interface (= BEN + MAU
OHT for dispenser x disp_type_x 2 board) as hardware platform.
clear for dispenser x disp_type_x 3
blue for dispenser x disp_type_x 4

medium orientation The DICOM configurator configures pin

portrait for dispenser x disp_orient_x 0 22 for DICOM. If more than 2
landscape for dispenser x disp_orient_x 1 associations are chosen the according
numbers of pins is used (i.e. 2
default associations: Pin 22 and 23, and so on...)
8 x 10 for dispenser 0 disp_size_0 1
blue for dispenser 0 disp_type_0 4
portrait for dispenser 0 disp_orient_0 0
14 x 17 for dispenser 1 disp_size_1 4
blue for dispenser 1 disp_type_1 4
portrait for dispenser 1 disp_orient_1 0

processor
Sketch 6: MG3000 from Hardware and Software Point of View
=Description:
The output processor characterisation in terms of the processor type and the color or black/white
classification.

=Example:

Required Setting NVF Entry

processor type
no_processor proc_type 0
liquid proc_type 1

05.01.00 page 32 of 39 05.01.00 page 9 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
ribbon proc_type 2

2 APIP processor color

black/white proc_color 0
APIP (Agfa Picture Archiving Protocol) is the CMY proc_color 1
standard network language. It is used for CMYK proc_color 2
APIP communication between AGFA devices via network.
It is normally configured on pin 21 (see drawing). specs

MG =Description:
Drystar The specification parameter of the output device to be simulated.
3000
=Example:
[Link]
Required Setting NVF Entry
left margin specs_lm xxxx
top margin specs_tm xxxx
3 DICOM width specs_w xxxx
3.1 Introduction height specs_h xxxx
pixels per meter specs_ppm xxxx
DICOM = ,,DIGITAL IMAGING AND COMMUNICATION IN MEDICINE". Since 1983 the American College of lines per meter specs_lpm xxxx
Radiology- ACR- and the National Electrical Manufacturers- NEMA- try to create a standard for density units specs_dunit xxxx
transmission of photos and added information in-between digital systems. AGFA is an active ICM input bits per pixel specs_inbit xxxx
member of this team. The third version of this standard is called DICOM. AOM output bits per pixel specs_vbits xxxx
typical exposure time in 1/10 sec specs_exptime xxxx
Overview of DICOM functions typical cycle time in 1/10 sec specs_cyctime xxxx
Function Ability as user Ability as provider number of print passes specs_no_passess xxxx
number of dispensers specs_no_disp xxxx
Query Call up a database Ability to receive image data from an processor device code specs_proc xxxx
external system process time specs_proc_time xxxx

Retrieve External call up of the own At a query it is possible to transmit mail_artid

database image data to an external system
=Description:
Storage Transmission of image data to an Storage of image data on a specified Use Simple Mail Transfer Protocol (SMTP) to send the tiff images via E-mail. To activate this
external system for storage database service, set mail_artid to a valid ART index, different from 0. If using the interactive tio command at
the MG prompt, the value is used to find the mail server. If used as a C-module component, then the
Print Transmission of picture data to an Provides for others to print out on the mail_artid is taken from the NJE message, but mail_artid should still be different from 0. Also, set the
Management external system to print out own or associated system port number in the ART index used to 25, which is the reserved port number for SMTP.
To de-activate tiff E-mail, set mail_artid to 0.
Drystar 2000 and Drystar 3000 are so far only used as DICOM "print providers" (= DICOM devices
print on the printers). The MG3000 can also be used as storage user for ADC and IMPAX (= =Example:
MG3000 sends patient folders in DICOM format to ADC PS station and IMPAX).
Required Setting NVF Entry
3.1.1 AGFA supports DICOM 3.0: art id 1 contains the hostname of the mail server:
In General: mail_artid 1
-DICOM3 gives no guarantee for "interoperability" (of 2 DICOM devices)
-DICOM3 is no plug-and-play environment mail_to
-DICOM3 is no guarantee for consistent image quality
=Description:
Give the name of the mail user, for whom the E-mail is intended for. Other synonyms for mail user
are, mail account name or mail recipient name. This name should be a valid and registered name in
the mail server, otherwise the E-mail cannot be delivered.

05.01.00 page 8 of 39 05.01.00 page 33 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Enclosed a graphical overview of the different configurators:

=Example:
Required Setting NVF Entry
Salesman@[Link]
President@[Link]
IMOS
MG3000 IMOS
MG3000 IMOS
MG3000
MGC10126 OEM34155 SDK2.10
mail_from a:\winstall a:\winstall a:\setup
1/2 1/2 1/2

=Description:
Give your mail account name. This name is used to identify the sender of the E-mail message. Most
mail servers do not check on this name.
IMOS IMOS [Link]
MG3000
DICOM2.31 MG3000 MG3000
MPS2.33
=Example: a:\winstall a:\winstall
1/3 1/2 1/1

Required Setting NVF Entry

NiceGuy@[Link] Attention:
SW Versions are subject
to change.
See DIGIMAIL* for updates.
*DIGIMAIL = Bulletin Board MG3000.
Modem no. +49 89 6207 7777

Hard MPS32935
MG3000 MNR32925
MG3000
MPS32941
disk
1/1 1/1

[Link]
Image Formats:
AGFA + Picker Postscript Image Formats: TIFF + Sunraster
Protocols: PAP + lp/lpr + FTP Protocols: lp/lpr + FTP

Overview of the different configurators

05.01.00 page 34 of 39 05.01.00 page 7 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
6 Appendix
6.1 Troubleshooting Ethernet Connections

Symptom: You configured a network, but no printing via Ethernet is possible. Enclosed some hints,
how to troubleshoot.

Possible reasons:
HARDWARE
• cable (not RG-58; short circuit; not connected, not terminated by 50 Ohm terminator)
• BEN board (Fuse;....)
• Transceiver (see green LED = power. Off means BEN or Trans. problem)
• Drop cable, internal MG3000 Ethernet cable.

SOFTWARE
• Ethernet not configured
• Problem in ART table (mismatch of small/capital letters; typing error;
• mismatch of apip_dest_names.
• Not enough diskspace for the network user 4 (or 5 to 9) in MG3000 where you want to print
Sketch 4: The Network Protocols for Image Transmission image.

Tools for troubleshooting:

The following table shall give an overview, which configurator is used for what network image format
TROUBLESHOOTING HARDWARE
and network protocol:

start "rem" (logbook). Type "go" and have a look to the first page of information. You should get
something like:
Configurator Pin Network Image Format TNX ethernet address 00-66-00-27-6f-00 (=BEN ethernet adddress)
Protocol TNX selftest MAC okay (=one function of BEN SONIC chip)
TNX selftest ENDEC okay (=encoder/decoder function of SONIC
MeGaCON 21 APIP APIP chip)
TNX selftest cable okay (=check of fuse and cable)
DICOM 22 to 26* DICOM DICOM
TROUBLESHOOTING SOFTWARE
MPS with [Link] 22 to 26* LP/LPR AGFA Postscript or
look to the whole customization list: type NVE at the AOS shell prompt. You have to get
floppy ETHXXX21 driver at the end. Otherwise it seems that Ethernet is disabled.
FTP Picker Postscript
type "adv" to get the whole list of all Ethernet nodes in your network ("adv" means "advertise").

PAP Comment: "adv" is much better than using "ping", because you do not have to know the other nodes
addresses or names.
MPS with [Link] 22 to 26* FTP TIFF or
floppy 6.2 Nice to know about RTT tables...
LPR SUNRASTER When do you need an RTT table:
Whenever you have to connect two or more network clusters having different Network-IDs, e.g.
TMX 22 to 26* SMTP TIFF 192.9.200.x and 134.3.x.y by means of a router.
*Drystar 3000 only up to pin 25! We have to distinguish between 3 different network classes:
(1) Class A: 0......127 Host definition: last 9 figures
All configurators except MeGaCON are explained later on. For a description of IMOS MeGaCON, (2) Class B: 128....191 Host definition: last 6 figures
DICOM and Postscript Configurator see the corresponding Windows Helpfile. (3) Class C: 192....254 Host definition: last 3 figures

Example: Here is the programming of RTT to reach any destination in 192.9.201.x from 134.3.x.y via
the Router and vice verse.
The IP-address of the router is [Link] respectively e.g. [Link].

05.01.00 page 6 of 39 05.01.00 page 35 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Pins 1 to 4 as well as 11 and 21 (=APIP by convention) are configured by MeGaCon.
Pins 22 to 30 are configured via the IMOS DICOM, MPS*** or TMX**** configurator.

***MPS = MeGa Postscript

****TMX = Tiff Mail Extension
For a complete list of abbreviations and expressions see the glossary.

Programming RTT (for to send to 192....; =class C):

subnet_mask "[Link]" This is an entry for NO subnetting
...destination "[Link]" ..reach ANY destination overthere
...gateway "[Link]" ..reach them via Router [Link]

Programming RTT (for to send to 134....; =class B):

subnet_mask "[Link]" This is an entry for NO subnetting
...destination "[Link]" ..reach ANY destination overthere
...gateway "[Link]" ..reach them via Router [Link]

Now let us exchange network cluster 192..... (class C) by a network

cluster class A, e.g. 27.x.y.z: Sketch 2: Usage of the different configurators

Programming RTT (for to send to 27....; =class A): The image formats and protocols that can be configured with the different configurators are
subnet_mask "[Link]" This is an entry for NO subnetting displayed in the next 2 sketches:
...destination "[Link]" ..reach ANY destination over there
...gateway "[Link]" ..reach them via Router [Link]

You can make up to 9 such definitions.

If you want just certain destinations to be reachable via the router, you can specify them explicitly, as
follows:
...[0]destination "[Link]"
...[0]gateway "[Link]"
...[1]destination "[Link]"
...[1]gateway "[Link]"
...

Further parts of the table:

arp_table You don't have to do anything here.
hosts_table This is for your convenience, when you would like to reach some of the remote
destinations by hostname, not by IP, and the hostnames are not listed in the ART tables.
Example:
...[0]hostname "mg11" Sketch 3: The file formats for image transmission
...[0]hostaddress "[Link]"
...

Remark for ISDN applications:

MFX parameter "mfp_artids" for ISDN connections and Ethernet connection to workstations (only
valid for MeGa3P30 and higher).

Please see enclosed part of the documentation on your PC in the "mg30" shell: MG documentation:
Operating system: MFX: mfp_artids

05.01.00 page 36 of 39 05.01.00 page 5 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

1 General Introduction MFP_ARTIDS Description:

Meanwhile we have a few different configurators for configuration of the different pins of the A list of art ids for which MFS message broadcast is not allowed or needed. This is the case for
MG3000, Drystar 2000 or Drystar 3000. workstations, like AS, PS, RS, or even between MGs interconnected via an ISDN telephone line, in
order to keep costs to a minimum.
What is a pin?
For those art ids entered in the list, an mfp server is started, which simulates the MFX behaviour of
A pin is an input or an output, locally or via network. It is a piece of software, that can be the remote station. Each art id is a decimal number, multiple art ids are separated by a comma
connected to a piece of hardware, e.g. a VSI interface or a network interface (BEN + MAU).
Theoretically, from software point of view, we could configure pin 1 to 10 as inputs, pin 11 to Example:
20 as outputs (always only pin 11 is used!) and pin 21 to 30 as network input/output. e.g. An AS3000 is set in art id 3
and a PS5000 is set in art id 5.
-
For those art ids entered in the list, an mfp server is started, which simulates the MFX behaviour of
the remote station.

Required Setting NVF Entry

---------------- ---------
3,5 mfp_artids 3,5

Attention: This is not necessary in case the correct dest_type is entered in the ART table: dest_type
= 0 for AS and RS / dest_type = 4406 for PS.

Sketch 1: Pin Assignments on MG3000 / Drystar 2000 / Drystar 3000

How many pins can be used simultaneously?

The max. number of inputs is limited to 9. The input pins are divided among no_amods (number of acquisition
modules) and no_nmods (number of network modules), to be set in the SYS component's configuration table.
(NVE SYSXXX00 no_amods, no_nmods)
Example: For a Drystar 3000 the number of no_amods is 4 (3 VME inputs + 1 local keypad) leaving 5 possible
no_nmods. Usually the first nmod is for APIP, leaving thus only 4 possible no_nmods for other network
applications, e.g., DICOM.
Following pin assignments can be distinguished:
Device Input Output Network (Input / Output)
MG3000 (LR3300 Controller) Pin 1 to 3 Pin 11 Pin 21 to 26
Drystar 2000 Pin 1 to 3* Pin 11 Pin 21 to 26
Drystar 3000 Pin 1 to 4** Pin 11 Pin 21 to 25
*Drystar 2000 Input Pin Assignment:
Pin # Used for...
1 VSI or MFRI Interface
2 Local Keypad (TIF driver)
3 VSI or RDS
**Drystar 3000 Input Pin Assignment
Pin # Used for...
1 VSI or MFRI Interface
2 VSI or MFRI Interface
3 VSI or MFRI Interface
4 Local Keypad (TIF driver)

05.01.00 page 4 of 39 05.01.00 page 37 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

7 Glossary

ACR-NEMA American College of Radiology - National Electrical Manufacturers

Association List of contents
AMDI -C Agfa Medical Digital Interface -Control
ANSI Ammerican National Standards Institute
AOS Adonis Operating System
APIP Agfa Picture Archiving Protocol
1 General Introduction ...................................................................................... 4
ASCII (American Standard Code for Information Interchange) The predominant
method for encoding 7-bit characters on a personal computer. HTML, tags 2 APIP ................................................................................................................. 8
and URLs must be in ASCII. 3 DICOM ............................................................................................................. 8
CAD Compact Acquisition Module (A+B Module of the MG) 3.1 Introduction................................................................................................ 8
3.2 IMOS DICOM configurator rev. 2.3.1 or higher .......................................... 11
CR Computer Radiography
3.3 Adjustments on DICOM Modality Side ....................................................... 15
DICOM Digital Imaging and Communication in Medicine 3.4 Checklist for Drystar / MG3000 DICOM installation problems .................... 16
ECU Embedded Controller Unit (C Module) 3.5 How to configure DICOM manually............................................................ 16
Ethernet Frequently spread technologies for LANs (Local Area Networks) 4 Postscript........................................................................................................ 21
4.1 Introduction................................................................................................ 21
FTP (File Transfer Protocol) The Internet service that transfers files from one 4.2 Imos Postscript / MNR Configurator Screen: ............................................. 23
computer to another. 4.3 Remark to page size.................................................................................. 23
IMOS Image Monitor Software 4.4 Readme Files MPS / MNR......................................................................... 24
Internet address See network location. 4.5 Troubleshooting MPS ................................................................................ 28
4.6 Drivers for MPS / MNR .............................................................................. 29
IP (Internet Protocol) Internet software that divides data into packets for
5 TMX Application ............................................................................................. 30
transmission over the Internet. Computers must run IP to communicate
across the Internet. See also TCP. 5.1 TMX: General ............................................................................................ 30
5.2 Mail message ............................................................................................ 30
IP-Adresse (Internet Protocol Adress) The standard method which identifies an internet 5.3 Manual TIFF / MAIL installation ................................................................. 30
connected computer. 5.4 TIFF/MAIL Configuration driver_name ...................................................... 31
ISDN Integrated Services Digital Network 6 Appendix ......................................................................................................... 35
ISR Interface Status Report 6.1 Troubleshooting Ethernet Connections ...................................................... 35
LAN 6.2 Nice to know about RTT tables... ............................................................... 35
(Local Area Network) Networktechnologie, designed to connect computers
over short distances. It is possible to connect the LAN with the internet or to 7 Glossary .......................................................................................................... 38
make a configuration into an intranet.
Lp/lpr Line printer daemon on workstations
LR Laser Recorder
LUT Look Up Table
Mailto The Internet protocol that is used to send electronic mail.
MFRI Multi Format Receiver Interface
MG Medical Gateway
MIME type (Multipurpose Internet Mail Extensions type) A method used by Web
browsers to associate files of a certain type with helper applications that
display files of that type.
MNR MeGa Network Reader
MPS MeGa Postscript
PACS Picture Archiving and Communication System
PAP Printer Access Protocoll. Print protocoll above ethertalk for Appletalk
printers

05.01.00 page 38 of 39 05.01.00 page 3 of 39

 Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E
Networking: APIP / DCM / MPS / MNR / TMX DD+DIS068.98E

Pin A pin is an input or an output, locally or via network. It is a piece of

software, that can be connected to a piece of hardware, e.g. a VSI interface
or a network interface (BEN + MAU)
R&D Research and Development
RAM Random Access Memory
RAS Fileformat for screen images of SUN Microsystems.
SMTP (Simple Mail Transport Protocol) The Internet protocol, specified by RFC
821, that governs the exchange of electronic mail.
TCP (Transmission Control Protocol) Internet networking software that controls
the transmission of packets of data over the Internet. Among its tasks, TCP
checks for lost packets, put the data from multiple packets into the correct
order, and requests that missing or damaged packets be resent. Computers
must run TCP to communicate with World Wide Web servers.
TCP/IP Transport Control Protocol / Internet Protocol. Common Protocol for
Networks. Used in the Internet
TMX TIFF Mail Extension
UTP Unshielded Twisted Pair
VME Versa Module Euro
VSI Video Synapse Interface

05.01.00 page 2 of 39 05.01.00 page 39 of 39