Planmeca Romexis
Planmeca Romexis
EN
installation manual
10014600_20
TABLE OF CONTENTS
1 INTRODUCTION ................................................................................................................. 1
2 SYSTEM REQUIREMENTS ............................................................................................. 1
2.1 User account recommendations .................................................................................... 2
2.2 Network recommendations ............................................................................................ 2
2.3 Securing the image data ................................................................................................ 2
The manufacturer, assembler, and importer are responsible for the safety,
reliability and performance of the unit only if:
- installation, calibration, modification and repairs are carried out by qualified
authorized personnel
- electrical installations are carried out according to the appropriate
requirements such as IEC 60364
- equipment is used according to the operating instructions.
COPYRIGHT PLANMECA
Publication number 10014600 Revision 20
Released 18 June 2013
1 INTRODUCTION
This manual describes the installation and configuration processes for Planmeca Romexis
software revision 3.2.R, Planmeca Romexis Clinic Management software revision 3.2.R and MS
SQL Server 2012 Express, as well as the required Java components.
2 SYSTEM REQUIREMENTS
NOTE Please note that these system requirements are recommendations. Not meeting them may
lead to degraded performance.
RAM 3 GB 3GB
3D Imaging
3D viewing 3D acquisition
workstation workstation
ProMax 3D s: 8 GB ProMax 3D s: 8 GB
Common components
NOTE On Windows 7 and Windows 8 operating systems the UAC level must be less than 2.
The User Account which starts Planmeca Romexis Service on a 64-bit Operating System must
have a valid password set (not null).
The server client communication is based on Java RMI over TCP/IP, thus support for TCP/IP
protocol is required. Network bandwidth requirements are dominated by digital imaging
requirements. The retrieval of a digital 2D image for viewing requires a transfer of roughly 1 MB
of data over the network, while opening a 3D volume for viewing will require a transfer of 250 MB
of data, which thus creates a major load on the network and of course this transfer time
dominates the user observable system performance. Planmeca recommends that for 3D capture
and viewing a gigabit Ethernet should be utilized where possible.
NOTE Since the Java RMi protocol relies on multiple simultaneous TCP/IP connections at
random ports, RomexisService.exe needs to be allowed full access to all ports above and
including port 1024. Please refer to your fire wall user guide on how to best achieve this. If
a fire wall is not used in the Planmeca Romexis intranet this requirement can be ignored.
Image data can be secured by backing up the C:\Romexis_images\ folder. The patient database
should be secured using backup tools of the respective database engine. Refer to the Windows
Backup facility or the documentation of your backup solution.
3 KNOWN ISSUES
If the user account with which Planmeca Romexis Service is started does not have a valid
password set (not null) Romexis Server 12-bit JPEG coding does not work.
(SSL)
NOTE Components that differ in a 64-bit installation are marked with an extension "(64-bit)" in
the installer component selection dialog.
Common Components
• JRE 1.6.0 Update 38 Java Runtime Engine. Required on every Planmeca Romexis workstation.
(delivered within Romexis client and server installations)
Client
• VDDS, for integration with most of the German practice management systems: requires
PMBridge
Server
• MS.NET 2.0, 3.5 SP1 and MS.NET 4.0 (manual installation required prior to MS SQL Server
2012 Express installation)
Webstart
DxLoader
• DxLoader files, for database migration from Planmeca Dimaxis to Planmeca Romexis
Planlink
2. The License Agreement screen appears. Read the license and select I accept the terms of the
license agreement. Click Next to continue.
3. Select the language for software and click Next. Language can be changed in Planmeca
Romexis Configuration Application.
4. In the following window you may select either Express or Custom installation.
• In case only a single PC is used with ProSensor or intraoral camera device select Express
installation with predefined settings.
• If you want to choose which components to install select Custom installation and continue to
“Custom installation” on page 8.
• intraoral camera installation includes Planmeca Romexis client, server and database
• ProSensor Ethernet installation includes Planmeca Romexis client, server, database and DIDAPI
driver
• ProSensor USB installation includes Planmeca Romexis client, server, database and Didapi
driver and ProSensor USB driver (ProSensor USB driver installation requires user input during
the installation).
6. Click Next.
Custom installation
NOTE Planmeca Romexis installer detects and preselects the operating system architecture
automatically. The preselected option can be changed if the user feels that the
architecture is not equivalent to the actual operating system architecture.
NOTE Setting this value too high may prevent Planmeca Romexis client from starting. This
setting defines the Planmeca Romexis client Java virtual machine memory allocation (-
Xmx value) that is specified in the Romexis.bat startup file.
1 GB => -xmx600m
2 GB => -xmx1200m
3 - 5 GB => -xmx2500m
6 - 7 GB => -xmx4000m
8 – 9 GB => -xmx6000m
1. Check Server and Common Components option on the left side of the window. All needed
components are automatically selected on the right side of the screen. MS SQL Server 2012
Express is selected as the default database. Required MS.NET versions are installed if not found
on the target computer.
If you want to install Planmeca Romexis files for Webstart Installation on the server computer
check Romexis Webstart Server Files.
If you are installing Planmeca Romexis in Windows Server Domain (Domain Controller) select
the respective option and click Next. Otherwise select Normal Installation and click Next.
Define the destination folder for Planmeca Romexis Server installation and click Next.
* If a 32-bit installation is made on a 64-bit operating system, the default installation folder is C:\Program
Files (x86)\Planmeca\Romexis
Browse through the summary and verify that you have selected all wanted components.
1. Define the TCP/IP address of the database server computer and click OK. The default IP should
correspond with the IP address given to Planmeca Romexis Client as Planmeca Romexis Server
IP address. The default IP 127.0.0.1 equalling to local host is provided by default.
2. After giving the TCP/IP address Planmeca Romexis automatically continues installing the next
component on the list.
This procedure will install an instance of MS SQL Server 2012 Express on the server computer.
MS SQL Server 2012 Express depends on Microsoft .NET Framework versions 3.5 and 4.0,
which have to be installed manually prior to starting the MS SQL Server installation.
On Windows 8 operating system MS.NET MS.NET 3.5 SP1 can be enabled in Control Panel >
Programs and Features > Turn On/off Windows Features. This process requires internet access.
If no Internet connection is available, the .NET 3.5 SP1 framework can be installed using the
Windows installation DVD or ISO-image.
The installer packages of NET frameworks for other operating systems than Windows 8 for
manual installation can be found from the installation DVD’s folder \MSSQL:
• .NET 3.5 SP 1 installer for Windows Server 2008 and Windows Vista.
• .NET 4.0 installer for Windows Vista SP1, Windows Server 2008, Windows Server 2008 R2,
Windows 7 SP1, Windows Server 2008 R2 SP1.
MS.NET installations can be verified from Windows registry keys (type "regedit" in Windows
Terminal):
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework
Setup\NDP\v2.0.50727 (MS.NET 2.0)
SQL Server Management Studio, a graphical tool for managing SQL Server, is provided on the
Install CD and can be separately installed if needed. It can be found under:
For more information on how to back up MS SQL Server 2012 Express see 18 “SETTING UP
MS SQL SERVER 2012 EXPRESS BACKUP”
Planmeca Romexis Database for MS SQL Server is created using a separate setup instance,
which will start automatically after the MS SQL Server installation.
The Create Romexis Database option is automatically selected on the left side of the dialog
window.
3. InstallShield Wizard will ask for details of the Database Server and Instance to which Planmeca
Romexis database will be created. If the MS SQL Server installation was successful, the
Database Server drop-down list should contain the default Planmeca Romexis instance.
Select:
4. Connect using Windows authentication: You can also connect using SQL Server authentication
and the default login ID and password:
LoginID: sa
Password: pwr0mex!s
NOTE MS SQL Server Database Instance ROMEXIS sa password has been changed in version
2.1.R. The password in the older installations is pwr0mex1s.
6. By default, this database is set at a size of 10MB with a default growth rate of 10MB.
Image folders that contain the actual images are created under:
C:\romexis_images\
C:\romexis_cache\
C:\romexis_ergodata\
1. Click the Browse button to define the root folder for installation files and click Next.
3. In an update installation of the webstart server files, the installer asks if the user wants to
reconfigure the server configuration files' ip-addresses. If you select Yes, you are prompted for
new ip-address for he configuration files.
1. Start the Planmeca Romexis server service in the next opening window. Click Start Service.
3. Click Done.
1. Start the Planmeca Romexis server as in the previous chapter 6.1.10 “Starting the Planmeca
Romexis Server Service”. Click Start Service.
2. If a message box stating: Failed to make sure that the server is running! appears, click OK in the
message box to ignore the message.
The service will start automatically after rebooting the computer at the end of the installation.
3. Click Done.
1. Start the Planmeca Romexis server as in the previous chapter 6.1.10 “Starting the Planmeca
Romexis Server Service”. Click Start Service.
2. If an error message pops up stating Access denied, click Done and go to the folder C:Program
Files\Planmeca\RomexisServiceCtrl.exe right-click on the file RomexisServiceCtrl.exe and select
Run as Administrator.
1. Select Client Components and Common Components on the left and deselect Server
Components.
All required basic components for Client are automatically selected on the right side of the
window:
• Client program
• DIDAPI
and
To install DxLoader files for migration of Planmeca Dimaxis database to Planmeca Romexis
check DxLoader.
Browse through the summary and verify that you have selected all wanted components.
1. Define the destination folder (the default folder is C:\Program Files\Planmeca\Romexis) and click
Next.
* If a 32-bit installation is made on a 64-bit operating system, the default installation folder is C:\Program
Files (x86)\Planmeca\Romexis
It is not recommended to change the default destination folder.
1. Define the TCP/IP address of the database server computer and click OK. The default IP
127.0.0.1 equalling to local host is provided by default.
2. After having typed the TCP/IP address Planmeca Romexis automatically continues installing the
next component on the list.
If capturing images with 3rd party software via DIDAPI UI User Interface, select additionally
DIDAPI UI Support for Integrators
If capturing images via Planmeca TWAIN Source, select additionally Planmeca TWAIN Source.
Capture
If capturing images with ProSensor USB select additionally ProSensor USB Driver. This feature
is intended for ProSensor ControlBox version 2.0.1.R or newer.
3. Click Next.
4. Define the destination folder in the Choose Destination Location window and click Next.
6. After DIDAPI has been installed Planmeca Romexis automatically continues installing the next
component.
Define the TCP/IP address of the 3D server (Reconstruction PC) and click OK. The default
Reconstruction PC IP address 10.0.0.3 is provided by default.
Give a name for the connected Unit: This is the unit name shown in the clinic layout. If the name
field is left blank, the workstation name is used as default.
If the installer detects a previous pmbridge installation, it asks the user if the existing settings
should be overwritten or not.
If the answer is Yes, also the ini and batch files are overwritten in the installation in addition to
the dll and exe files.
Installation folder
C:\Program Files\Planmeca\Program\pmbridge\Program
7 FINALIZING INSTALLATION
1. Select View Romexis Installation Log and View Romexis Bulletin Folder and click Finish to
complete Planmeca Romexis Setup.
2. The following window appears. Select Yes and OK to reboot the computer.
3. After server installation, follow the instructions in chapter 8 “LICENSE INSTALLATION” on page
24 to enable the use of Planmeca Romexis.
Windows Start menu -> Programs -> Planmeca -> PlanLink Service Control.
5. To start Planmeca Romexis, double-click the Planmeca Romexis icon on the desktop or choose
Planmeca Romexis from the Windows Start menu -> Programs -> Planmeca -> Planmeca
Romexis.
8 LICENSE INSTALLATION
NOTE License installation is only possible on Romexis server computer.
1. To start the License Installer from Windows Start Menu click Programs -> Planmeca -> Install
Romexis License.
2. The License Installer will ask for the location of the license file which is provided on a separate
License CD when purchasing Planmeca Romexis. Select the folder in which the license file
(romexis.lic) can be found and choose Next.
3. Click Install.
4. After the installation is completed, remember to restart Planmeca Romexis Service in order to
activate the license installation.
NOTE A 32-bit installation on a 64-bit operating system cannot be updated directly to a 64-bit
version. First an uninstallation is required followed by a fresh 64-bit installation of
Planmeca Romexis.
3. Install Wizard will prompt for an update confirmation. Click Yes to continue.
4. Select the same components that you have installed in a fresh Server/Client/Standalone
installation.
Additionally, you can also select new features. If you are updating a server installation,
remember to select Romexis Database from the Server Components.*
NOTE Make sure to select all those Planmeca Romexis components that are installed on the
target computer. If you deselect a component that is already installed it will be removed
from the computer.
The Planmeca Romexis Cephalometric analysis module can be found under Client components
*Applies only to MS SQL Server databases. In case of Oracle or Solid database, deselect the options
MS SQL Server and Planmeca Romexis Database from Server Components and run the database
update scripts manually.
The installer automatically recognizes that Planmeca Romexis database already exists and
shows only the option Update Romexis Database. Click Next and follow the instructions in
section 6.1.8 “Planmeca Romexis Database Creation” on page 13.
NOTE The Implant Library should be installed only once to avoid multiple copies of default
implants.
10 POST CONFIGURATION
After Planmeca Romexis installation Java automatic update must be disabled in order to
eliminate version conflicts and update problems. Proceed as follows:
Browse to Windows Control Panel => Java => Advanced, and select Never Auto-Download.
Click OK.
Up to nine custom floorplans can be specified for the Clinic view. The floorplan graphics must be
in PNG format and approximately 1100 x 800 pixels (maximum) in size. The files must be named
floorplan1.png, ending in floorplan9.png, depending on how many floors are needed. Place the
files under Planmeca Romexis installation in the folder /sconfig/, replacing any previous
floorplan*.png files.
If PlanLink dental unit diagnostics is to be used make sure that the following settings are selected
in Planmeca Romexis Configuration Application under Start-Up > Server parameters > Server.
For more information on setting up PlanLink please see the “INSTALLING PLANLINK AGENT
SERVICE MANUALLY” on page 59 in this manual and the chapters F “ADMIN MODULE” on
page 1 and H “PLANMECA ROMEXIS CONFIGURATION APPLICATION” on page 1 in
Planmeca Romexis User’s manual.
The required Java-xmx and minimum memory settings for different setups are listed in the
following table.
If needed, modify the Romexis client memory setting accordingly in Romexis.bat file located in
the C:\Program Files\Planmeca\Romexis\client folder.
NOTE It is recommended that Planmeca Romexis is uninstalled only in case Planmeca Romexis
is no longer used on the respective computer.
The uninstallation can be started from Windows Control Panel -> Add/Remove Programs, by
selecting Planmeca Romexis from the Currently Installed Programs list, and clicking Remove.
Another option is to start Planmeca Romexis Installer from the Installation CD and select the
option Remove from the main selection dialog.
12 CLINIC MANAGEMENT
When the PlanLink Agent Service is active on the chair side PC all dental unit information is
automatically collected and stored into the central database in real time. The information
collected can be immediately reviewed from any workstation on the network.
Use these settings to specify whether the dental unit should be automatically locked when
PlanLink Agent exits (when shutting down the PC). For more information on how to control dental
unit locking settings see Planmeca dental unit manuals.
NOTE The error, chair and instrument use and instrument flushes are not recorder if PlanLink
Agent is not running.
When this option is selected the units always remain unlocked, even when the PC is shut down
and PlanLink Agent is not running.
The dental unit is automatically locked when PlanLink Agent is shut down. Use Compact i
service modes to configure how to open the lock if necessary.
Use these settings to specify whether to save the diagnostic events to the database or not. The
options are:
Notification period
If the unit has an error condition which is not negated in the time period set (default 5 minutes),
Planmeca Romexis Server sends an e-mail to all listeners assigned to listen to errors with that
error code.
The server can also be configured so that it does not send an e-mail with the same error code for
a certain time interval (default 60 minutes).
Each dental unit is connected to a chair side PC serial COM port with a Planmeca Planet cable.
PlanLink Agent Service must be running on each PC connected to a dental unit to record data
during use. The PlanLink Agent Service listens to activities on the dental unit and relays them to
Planmeca Romexis Server for storage into database for later reference. PlanLink Agent also
manages saving and restoring of dental unit settings to and from the unit to database. Therefore,
to ensure that a full log of use and hygiene procedures is collected, it is important that the
chairside PC is on and PlanLink Agent is running at all times when the dental unit is operated.
Planmeca Romexis Clinic Management Module is a desktop application that is used to view data
stored into Planmeca Romexis database. When a dental unit is accessed in Planmeca Romexis
Clinic Management Module, a connection to the PlanLink Agent Service in the adjacent chairside
PC is formed and any commands to the dental unit are relayed via the PlanLink Agent.
Click the Configure Layout button at the bottom of the screen. When in configuration mode,
each operatory is shown as a black rectangle that can contain a PC and a dental unit.
The control panel contains items for new operatories and lists of available chairside PCs and
dental units.
A PC or a dental unit becomes active in the list after it has first connected to the server. If a PC or
a dental unit is not available in the list, please verify that it is connected to Planmeca Romexis
Server.
To add operatories into a layout click and drag the operatory of desired orientation into the
layout. When all operatories have been added to the layout the operatories can be named to
match, for example, the names of the actual operatories at the clinic. After placing an operatory
you can drag and drop the corresponding PC and dental unit pair into it.
Multiple floor plans can be used for multi-floor, multi-clinic or other complex layouts by creating
multiple floor plan files in PNG format on the server.
The Update Firmware can be used to check the current version of dental unit software as well as
for uploading new firmware to the selected units.
To show the update options click the Update Firmware button. A list of all connected dental
units and their software version is shown at the bottom of the screen.
It is recommended to update maximum 10 to 20 dental units at a time. To select multiple units for
update hold down the Ctrl key while selecting the units.
To choose the software you want to update to the selected units use the Find Files button.
Browse to the *.MOT file that contains the new software. To update the units click on Update
Selected Units.
This Quick installation guide describes the Planmeca Compact i Touch software update for
Planmeca Romexis Clinic management module.
NOTE This manual is valid for Windows 7 / XP / Vista and Windows 2000 operating systems.
1. Insert the USB memory stick for Planmeca Compact i Touch software update to the Planmeca
Romexis Server computer USB port.
3. Note the USB drive letter (J). Select the option Open folder to view files.
4. The security question “Do you want to allow the following program to make changes to this
computer?” appears. Select Yes.
If you are prompted for an administrator password or confirmation, type the password or provide
confirmation.
3. Go to the USB-drive and find the correct drive letter in Windows Explorer.
7. Go to Planmeca Romexis Clinic management module and check from the Unit Monitoring and
Info tabs that the instructions and Touch panel have been successfully updated.
2. The current service mode is shown on the virtual unit control panel and the possible values are
listed and described on the bottom right of the screen.
3. To change settings, use the virtual control panel in the same way as when changing settings at
the actual unit.
4. To exit the service mode, either click on the wrench icon or the Program icon on the virtual
control panel.
OR
NOTE Before accessing service mode on a unit remotely, make sure that nobody is currently
using the unit.
15 DIDAPI CONFIG
This section describes how to use the Planmeca DidapiConfig application for configuring
Planmeca ProMax, ProOne, Proline, ProSensor and Dixi X-ray systems.
NOTE Please see the X-ray unit manuals for availability of specific features.
NOTE All systems have separate technical manuals, which should be used in conjunction with
this one.
NOTE Some settings are common to all devices whereas others are device specific. Thus the
contents of the tab images used may be different from the contents in the corresponding
tab of a specific device. In case the settings can be applied only to (a) specific device/s it
is indicated next to the title in question.
2. In the following window select the device you would like to configure.
15.2 Summary
• Operating system
• Computer name
• User name
• Processor
15.2.2 Didapi
NOTE All the following paths are requested from Didapi.dll. Thus the paths are the ones used by
Didapi.
Didapi version
Didapi.dll path
The path where the DidapiConfig and the exposure programs using the Didapi.dll are stored.
In 64 bit Windows operating system the Didapi.dll file is in the format Didapi_64.dll and in the 32
bit Windows operating system in format Didapi.dll. For simplicity the format Didapi.dll is used
when referring to both systems.
Sometimes there might be several Didapi.dll files (backups or old/erroneous installations. The
currently used Didpi.dll file is shown in this folder.
The path where the IP settings are stored. This path can be configured in the Network settings
tab, see section 15.5 “Network settings” on page 47.
The path where the sensor calibration files are stored. This path can be configured in the Log
tab, see section15.7 “Log” on page 51.
The path where the Didapi log is stored. This path can be configured in the Log tab, see section
15.7 “Log” on page 51.
Didapi.ini path
The path where the Didapi.ini file is stored. This path cannot be configured.
The folder where the images to be reprocessed are stored for supported devices. This path
cannot be configured.
Opens the Didapi.ini file where most settings modified by DidapiConfig software are stored.
To open the folder where the raw images are stored click this button .
In the Image processing tab you can set the preprocessing settings for:
• Dimax 2/3/4
and
• Cephalostatic images
The content of the Image processing tab depends on the currently selected device, see step 2 on
page 39.
The Planmeca ProMax, Proline and ProOne share the same settings, as only one device can be
configured at a time. However, only the settings relevant for the current device are shown. Thus
the number of tabs shown depends on the device that is been currently configured.
The settings in the Planmeca ProMax, Proline and ProOne Image processing tab do not affect
the Planmeca ProSensor and Dixi 1/2/3 settings which are also independent on each other.
NOTE Some settings might exclude each other, e.g. you must use either Auto levels settings or
Logarithmic mapping.
White
Defines the percentage of cumulative shades of grey that is left out of the contrast range from the
upper end of the contrast range.
Black
Defines the percentage of cumulative shades of grey that is left out of the contrast range from the
lower end of the contrast range.
Midtones (gamma)
Adjusts the gamma curve of the image. Values below 1 will darken the image whereas the values
above 1 will brighten it. When set to 1 the value is not altered.
SCurve
The SCurve processing is a step where the difference of raw data from image to image is
compensated. The SCurve defines a look up table to convert 16-bit data into 12-bit.
The raw data values are different depending on exposure values, patient thickness, x-ray tube,
CCD camera, filtering, aging, etc.
As the position of the curve is changed less radiation moves the curve leftwards and higher dose
moves the curve rightwards. The SCurve searches the histogram and converts or compresses
the data to 12-bit scale - into values between 0 and 4095.
Threshold values define how easily the sensor detects the start of an exposure. Normally default
values should always be used. If image is triggered without radiation, increasing the threshold
value could solve the problem. If exposure is missed or image integration starts too late, lower
threshold value might help.
15.3.5 Soft tissue filter enabled (Planmeca ProCeph and Cephalostatic only)
The scale is from 1,5 to 10. Values above 1 will brighten the image.
Dental Image Contrast Enhancement (DICE) adjusts and optimizes the contrast of the image
automatically and brings out image details on the entire grey scale.
To set DICE on or off separately for different image modalities check the DICE check boxes.
With panoramic and cephalometric images DICE is selected by default.
NOTE The AGC setting is shared between PAN, Bitewing, TOMO/TMJ and CEPH tabs.
The Automatic Gain Control (AGC) is supported by later Dimax2 and all Dimax3 sensors. It is
recommended to activate the AGC if the sensor supporting this option is used.
Automatic Gain Control (AGC) optimizes digital sensor sensitivity to produce excellent image
quality regardless of tissue and bone thickness.
In this field you can select the method the sensor uses to detect when an exposure is taken.
Auto exposure
Threshold values define how easily the sensor detects the start of an exposure. Normally default
values should always be used. If image is triggered without radiation, increasing the threshold
value could solve the problem. If exposure is missed or image integration starts too late, lower
threshold value might help.
Exposure time
Maximum time for exposure. Sensor stays in image integration mode this long. Set this value to
maximum exposure time used on clinic. Setting too high exposure time results in noisier images.
Setting exposure time lower than used exposure time, results blurred image.
Preheat time
The x-ray tube preheat time The default value is usually good with Planmeca Intra.
Default IP ports:
ProMax: 10.0.0.1:5000
RecoPC: 10.0.0.3:5000
SmartPan: 10.0.0.3:5003
Proline: 192.168.0.135:5120
ProOne: 192.168.0.135:5120
Dixi1/2/3: 192.168.0.135:5120
The IP address and the IP port for Planmeca Promax, ProOne and Proline need to be set when
starting to use the device.
For Planmeca Proline and Dixi1/2/3 the box port also needs to be set.
The IP Port for RecoPC and ProMax is always 5000 and 5003 for SmartPan.
Ping IP
Once the IP address has been configured you can test the connection by clicking the Ping IP
button.
Activate IP
Only one Promax/Proone/Proline ethernet device can be activated at a time. The IP addresses of
the currently activated devices are shown at the bottom of the start page.
and
Clicking the activate IP buttons activates the current device and stores its IP address and
deactivates the IP address of the ProMax/Proline/ProOne or ProSensor/Dixi123 devices. The
user will be prompted.
For example if ProMax has been selected the ProMax IP address will be activated and stored
whereas the Proline and ProOne IP addresses (if active) are disabled. The Ethernet settings field
and the Activate IP button are disabled.
When the IP address of the device is active the address fields are active and the IP address can
be set or changed. The Activate IP button is inactive (grey) and cannot be used.
When the IP address of the device is not active the address fields cannot be set or changed. The
Activate IP button is active and can be used.
The Planmeca ProSensor Planet cable is an optional feature of Planmeca Intra X-ray unit that is
used for connecting the device to a computer, as in Planmeca ProSensor there is no connection
for Planmeca Intra. When the planet cable is connected Planmeca Intra sends exposure
parameters to Planmeca Romexis. The exposure parameters used with Planmeca ProSensor
are voltage (kV), current (mA), exposure time (s) and DAP (mGy2cm2)
The Planet cable can also be used to open/lock Planmeca Intra in case the locking mode has
been enabled in Planmeca Romexis. In this mode exposures cannot be taken if Planmeca
Romexis is not in exposure mode or if for example the exposure request of a student has not
been approved.
To connect Planmeca Intra to computer with Planet cable check Planmeca Planet cable
connected and enter the correct port in the port field.
Help
The Help button can be used to find the current COM ports are available follow the instruction in
the help window.
To open the Planet setup help window click the Help button. Follow the instruction and click OK
to exit.
In Mac operating system clicking the Help button opens the path to the corresponding device of
the Mac OS file system.
NOTE This path is automatically set. It is recommended not to change the default destination
folder. It must only be changed for a specific reason.
The IP addresses set in this tab are saved to location defined in the Path to configuration file
field. This path is device specific.
To activate the IP enter the IP Address and the IP Port in the respective fields and click Activate
IP.
To select the directory where the configuration files are stored click the Browse button.
To set the directory as default location click the Default location button.
To change the path select the path for the configuration file and click Apply.
Midtones (gamma)
Adjusts the gamma curve of the image. Values below 1 will darken the image whereas the values
above 1 will brighten it. When set to 1 the value is not altered.
This feature is intended for adjusting the gray levels (Gray) and the space (Lines) between
slices when using imaging modes producing several slices and printing the images on film.
15.7 Log
NOTE The log is NOT device specific. The Log tab is the same than the Log accessed from the
start menu.
The Log level setting determines how much information will be written to the log file.
NOTE It is recommended not to change the default destination folder. It must only be changed
for a specific reason.
To save a copy of the log file to a desired location click9 the Save copy as button.
To select a new path for a log file click the Browse button, select the new path and click Select
path.
Workstation ID
Log File Workstation ID sets the name of the current workstation’s DIDAPI log file.
15.7.2 Calibration
NOTE It is recommended not to change the default destination folder. It must only be changed
for a specific reason.
To define calibration file path click the Browse button and select the desired location.
To restore default calibration file path click the Default Location button.
To browse for calibration files and copy calibration files to a specific location click Install
calibration files. After selecting the files and clicking Install the selected files will be copied to
the location defined in the Calibration file path field.
NOTE With some sensors or devices the calibration files are automatically loaded from the
sensor during exposure. With the sensors or devices that the calibration files are not
automatically loaded the files must be installed, e.g. from the CD delivered with the
sensor.
X-ray device ethernet configurations are made in the ethernet configuration files, located in the
C:\Program Files\Planmeca\Didapi folder.
ProSensorEthernetConfig.txt
PromaxEthernetConfig.txt
ProOneEthernetConfig.txt
NOTE In older installations didapi files are located in the Dimaxis folder
C:\ProgramFiles\Planmeca\Dimaxis\Program
Edit the ethernet configuration file of the respective x-ray device in order to map x-ray devices to
Terminal Server client workstations.
As a terminal server client workstation name one can use either COMPUTERNAME or
CLIENTNAME of the client workstation.
Computername and/or clientname can be seen in Windows command line: Windows Start Menu
-> Run.. -> Type in "cmd" -> In the command line, type in "set".
xpprosensor1=192.168.0.1
xpprosensor2=192.168.0.2
xpprosensor3=192.168.0.3
NOTE Each terminal server client must have access to the Didapi folder and a working network
connection to the x-ray devices.
18.1 Introduction
This section describes how to set up backups for Planmeca Romexis MS SQL Express by
means of a scheduled execution of a Stored Procedure using a batch file and Windows
Scheduled Tasks service. For backups on other database engines refer to their respective
documentation.
18.2 Configuration
When Planmeca Romexis installer deploys MS SQL Server onto the server computer, it also
creates a Stored Procedure in the Planmeca Romexis instance that provides a facility to make
backups from the Planmeca Romexis database, and transaction logs. To call the Stored
Procedure a set of two SQL scripts and a batch file is provided on the Planmeca Romexis
installation CD in the following location:
InstallCD\Tools\backup\
C:\Program Files\Planmeca\Romexis\backup\
3. The following settings are provided in both files and should be adjusted in both to fit the local
backup needs. “1” denotes true while “0” denotes false:
• @backupfldr = ’:\romexis_images
Folder to write backup to, a subfolder 'romexis_db' is automatically created and used. This must
be changed to point to a safe location that is available for tape backup.
• @reportfldr = 'c:\romexis_cache’
As above but defines location for writing reports of the backup process.
• @checkattrib = 1
Defines if new backups should have their archive bit set. The Stored Procedure will automatically
delete backups older than defined by dbretainunit UNLESS the files have their archive bit set to
true. If this is left at “1”, the old backups should have their archive bit set to false when they are
backed up to another media to prevent the file system from being filled with backups.
• @dbretainunit = 'months'
Defines the period for which the backups should be preserved before automatic deletion. Can
be: minutes | hours | days | weeks | months | copies.
• @dbretainval = 2
Specifies how many dbretain units to keep old backups.
• @rptretainunit = 'copies'
Defines the period for which to retain reports for. Can be: minutes | hours | days | weeks | months
| copies.
• @rptretainval = 30
Specifies how many rptretainunits to keep reports.
• @report = 1
Flag to indicate whether to generate reports or not.
NOTE Remember to test the backup functionality after creating the task.
Use the Windows Scheduled Tasks service to setup a daily backup event as follows:
3. Double-click Add Scheduled Task to create a new task or on Windows 7 click Create Basic
Task..
4. Proceed with the Scheduled Task Wizard and choose Browse to select the program. Browse to
run_romexis_backups.bat that you have copied to an appropriate location.
(e.g. C:\Program Files\Planmeca\Romexis\backup\).
On Windows 7 additionally add the path to the backup script folder to the field Start in (optional).
5. On Windows 7 after creation of the task, go to Task properties and check the Run with highest
privileges option.
6. Select the appropriate operating system in the Configure for drop-down menu.
8. Specify a convenient Start time to run the backups, such as after midnight when there is no
other activity.
9. Click Next and specify a user and password to run the backups under.
This is preferably a local backup account that has limited permissions. It should also be a
persistent account since if the account is removed the backups will stop working.
11.Double-click on the Task you just created to double check the configuration.
12.Right-click on the Task and choose Run to test the functionality of your setup.
NOTE Administrator rights are required as PlanLink Agent needs to be registered as a Windows
service.
1. Install PlanLink using Planmeca Romexis installer. By default it will be installed here:
C:\Program Files\Planmeca\PlanLink\
2. Configure the values in planlink-config.xml appropriately. You should only modify the values
within double quotes (““) and leave the quotes in place:
<dental-unit-proxy>
<comm-port name="COM1" />
Not configurable
<dental-unit name="Dental_Unit_123" />
Unique name for the connected Unit that is shown in the Romexis Clinic
module. If left empty (<dental-unit name="" />) then computer name
is used instead.
<listen-to port="6811" />
TCP/IP port at which the Agent will listen for incoming connections.
Leave at default “6811”.
<auto-connect-to ip-address="134.192.80.12" port="6812"/>
Romexis server IP address to which the Agent connects at system start.
Only modify the
ip-address attribute value.
<code-base url="http://134.192.80.12:8081/PMUAPI_classes.jar"/>
Romexis server IP address from where the Agent fetches required
components. Only modify the IP-component of the url attribute value,
leaving the port and path at default.
<class-server ip-address="134.192.80.12" port="8081"/>
Romexis server IP address from where the Agent acquires Java classes.
</dental-unit-proxy>
3. Launch RomexisServiceCtrl.exe
4. Check that the correct Java Virtual Machine is selected and that an appropriate amount of
Maximum Memory has been defined. Note that these settings are saved into the
RomexisService.ini file that resides in the same folder.
5. Click Start Service to register the PlanLink Agent Service as a Windows service. You can check
the status of the newly created service via Administrative Tools - Services.
6. Make sure that PlanLink is excepted in the Windows Firewall by creating an entry for
RomexisService.exe as shown below. RomexisService.exe is a Windows service wrapper
component for the PlanLink Java code.
The UnitSoftwareUpgrader.exe is a small utility designed to assist the user in upgrading the
software. It can also be used to upgrade PlanLink-enabled units.
NOTE Administrator rights are required if PlanLink service is installed on the chairside PC since
the service needs to be stopped (as it has COM port in use).
1. Make UnitSoftwareUpgrader.exe and all related files available on the chairside PC using a USB
stick or the like.
2. Make sure that the unit is connected to the chairside PC and is switched on. The unit must be
connected to COM1. You can check and change the COM-port using Windows Device Manager.
3. Execute UnitSoftwareUpgrader.exe.
4. Click Upgrade Unit Software to start the upgrade process. If PlanLink Agent Service has been
installed on the chairside PC, it will be automatically stopped for the duration of the upgrade to
free the COM-port. It will also be automatically restarted after the upgrade has finished.
5. If the unit does not have PlanLink-enabled software, it must be switched off manually and back
on again when the progress windows states “RESETting Dental Unit”. If the unit already has
PlanLink-enabled software, the reset will take place automatically.
6. The upgrade will take approximately 200 seconds after which the unit automatically resets itself.
7. You can now close the progress window and the Unit Software Upgrader utility.
8. Reset the unit and check the boot prompt on the instrument console to see that the correct
version is installed.
9. Enable PlanLink (PMUAPI) communication on the unit by setting the service mode 210 to value
1.
NOTE After first installing PlanLink-enabled dental unit software, service mode 211 is at value 8
by default. This must be changed to value 16 for clinical use. Other modes may cause
hazard to the patient.
1. To enable PlanLink communication on the unit, enter service mode and set service mode value
n.210 to 1.
2. To disable all dental unit remote control, set the service mode n.211 value to 16. Note, however,
that this mode still allows recording information from the dental unit using PlanLink.
n. 211 PMUAPI remote operation locked features (0 - 31, default 8). The value is a sum of the
numbers below:
2 Programming locked
4 Keyboard locked
If the value is <8, a notification on the touch panel indicates that the remote operation is enabled.
2 Programming locked
4 Keyboard locked
64 Operation locked
NOTE Be very careful when setting locally locked settings. The settings will take effect after the
unit is restarted.
21.3 Select how to freeze intraoral camera image from foot control
n.98
This service mode is used to select how intraoral camera images are frozen using the foot
control.
NOTE The service modes in the old foot control are the same as 0 - 3 except for vertical pedal
operation. If the value is set to 2 pushing the pedal to the left will freeze the image and
pushing it to the left again will unfreeze the image. Pushing the pedal to the right will save
the image.
Service
mode
23.1 Introduction
This section describes the installation of Planmeca Romexis Implant Library software version 3..
NOTE If you’re using Oracle or Solid server database see chapter “Manual installation” on
page 70.
• ~ 4 GB of free space.
Planmeca Romexis Implant Library CD currently contains implant data from the following
manufacturers:*
NOTE *Planmeca Romexis Implant Library installer Read Me file contains the most updated list
of the implant manufacturers.
1. Insert the Planmeca Romexis Implant Library CD into the disk drive.
3. In the Licence Agreement window select I accept the terms of the licence agreement and click
Next.
4. Select Romexis Implant Library by checking the box and click Next.
5. In the opening window, select Planmeca Romexis installation folder as the destination folder by
clicking Browse. The default folder is C:\Program Files\Planmeca\Romexis .
6. Make sure you have selected ROMEXIS Database Server. Click Next.
7. After the installation, verify that the realistic implants can be seen in Planmeca Romexis
software. To check the list of implants open the Planmeca Romexis 3D Module and click on the
Implant tab, then select Implant Library.
1. Browse to the folder \setup on the Planmeca Romexis Implant Library installation CD.
2. Copy the folder \geometries with all its subfolders to the folder where Planmeca Romexis Server
is installed. The default path is C:\Program Files\Planmcea\Romexis\geometries
3. Run the batch file all_implants.bat from the folder that corresponds to the installed Planmeca
Romexis database server type.*
setup\sql\sql.ora (Oracle)
setup\sql\sql.solid (Solid)
4. After the installation, verify that the realistic implants can be seen in Planmeca Romexis
software. To check the list of implants open the Planmeca Romexis 3D Module and click on the
Implant tab, then select Implant Library.
NOTE * If you are using Planmeca Romexis Database that was originally installed with the old sa
password0
Planmeca Romexis installer detects Adobe Acrobat and Adobe Reader installations and
configures Planmeca Romexis to open the Planmeca Romexis User’s manual (PFD format) with
the respected software.
To configure the PFD reader manually after the installation of Planmeca Romexis, edit the file
/Planmeca/Romexis/sconfig/manual_config.xml_EDIT as follows:
2. Make sure the key application default-path contains the path to the executable file of Adobe
Acrobat or Adobe Reader.
3. Make sure that the line <locale language="en" doc-file="Romexis_um.pdf"/> of the language in
use contains the name of the user’s manual to be used with the respected language, and that is
found in the /manuals folder of the Planmeca Romexis folder structure.
25 TROUBLESHOOTING
Start Romexis Service Control with Administrator privileges by right-clicking on the file and
selecting Run as administrator
If Planmeca Romexis server service does not start check that the parameter JVM Path of the file
RomexisService.ini in the folder server is the following:
In 32-bit OS:
In 64-bit OS:
25.2 DidapiConfig
or
• System level Environment variable ”PATH” contains the path to the folder where Didapi.dll file is
stored. Check that this environment variable exists and Didapi.dll path:
C:\Program Files\Planmeca\Didapi is set there.
• Reading/writing is permitted.
• Didapi.log can be found in the Didapi.ini that has been correctly set. The default path is
ProgramData\Planmeca\Logs Didapi.ini [LOGFILE]: LogFilePath=
• Check that the WorkstationID makes sense. Try to remove if set. It is empty by default. Didapi.ini
[LOGFILE]: WorkstationID=
The folder where the Images folder is created is missing or reading/editing is not permitted.
The users Temp folder cannot be found or no rights are admitted. This is an operation system
related problem.
• Check from the operation system settings why the Temp folder cannot be found.
To support other software companies and their developers to integrate their software, Planmeca
has created interface standards and libraries.
Pmbridge interface provides a simple way of data transfer between Planmeca Romexis and
practice management software of another company. Pmbridge functions as a "bridge" and
passes necessary patient information to Planmeca Romexis imaging software and images from
Planmeca Romexis to the third party software.
For integrators who do not need image transition from Planmeca Romexis to practice
management software a lighter solution called DxStart is also available .
C:\Program Files\Planmeca\Romexis\pmbridge
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppPaths\Dimaxis.
exe (Value Name: Path)
64-bit Windows:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\App
Paths\Dimaxis.exe (Value Name: Path)
64-bit Windows:
NOTE According to Pmbridge SDK instructions, practice management software has to add the
folder 'Program' to the path obtained from registry. That is why the complete path is not
found from the registry.
NOTE Pmbridge installation updates the Dimaxis.exe registry key to point to Romexis pmbridge
folder. This disables Pmbridge use with Dimaxis. If pmbridge is still desired to be used
with Dimaxis, the respective registry key should be changed to point to Dimaxis pmbridge
folder.
C:\Program Files\Planmeca\Romexis\pmbridge\Program
A.3 Users
Pmbridge user group permissions can be altered to pmbridge user needs in Planmeca Romexis
Admin Module. For more information see Planmeca Romexis user’s manual.¨
Planmeca Romexis installer creates a user group Pmbridge Users and a user Pmbridge to
Planmeca Romexis database. When starting Planmeca Romexis via pmbridge, the respected
user is automatically selected (Romexis.bat file's parameters uid (user id) and pwd (password)
found from the pmbridge installation folder).
If launching of Planmeca Romexis via PMBridge is not working use manual setup.
The existence of the path to the Planmeca Romexis’s Pmbridge.dll directory needs to be verified.
For historical reasons, the path is saved in Dimaxis registry key. To obtain the path, open the
Windows registry:
2. In the Run window, enter the command <regedit> to open the Registry Editor.
(In Vista the command <regedit> needs to be entered in the Start Search box)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App
Paths\Dimaxis.exe
64-bit Windows:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\App
Paths\Dimaxis.exe (Value Name: Path)
2. Right-click the App Paths key and select New and Key. Name the created key as Dimaxis.exe
3. Right-click the Dimaxis.exe key and select New and String Value. Name the created string
value as Path
4. To modify the created path double-click on the Path and enter the Value Data: e.g. C:\Program
Files\Planmeca\Romexis\Pmbridge
The Path of the Dimaxis.exe defines the location of the PmBridge files.
5. After having verified or created the Dimaxis.exe key, verify that the pmbridge files exist in the
following folder C: \Program Files\Planmeca\Romexis\pmbridge\Program You will find the files
on your Planmeca Romexis Installation CD (..\Tools\pmbridge).
7. To edit the file right-click on the file name and select edit with the left mouse button.
A window with the Planmeca Romexis directory text opens:
cd C:\Program Files\Planmeca\Romexis\client
If the text after @ start does not conform to the directory of the freshly installed Planmeca
Romexis version the directory text needs to be changed.
9. Change the xmx memory reservation to conform to Planmeca Romexis client configuration
recommendations.
11.Select the tab Local Settings and check PMBRIDGE Enabled in the section of Practice
Management Software Interface (PMBRIDGE). The port number is 1501.
12.Continue to set up the PmBridge connection in the Practice Management Software. Refer to the
appropriate manual to proceed.
Set up of VDDS
VDDS Bridge interface is the integration for most German practice management software. VDDS
can be installed from the Planmeca Romexis installation CD's folder \tools\VDDS
NOTE These instructions are meant for Romexis installation with MS SQL Server 2005 Express.
1. Insert the Planmeca Romexis installation DVD into the drive and start Planmeca Romexis
installation.
3. Select all necessary components and deselect Romexis Database component. Click Next.
5. After the installation is completed, navigate to installation DVD's folder \MSSQL\romexis_db\ and
start Romexis Database installer by double-clicking the file Setup.exe.
6. In the opening window select Other Scripts, check Create Database File and click Next.
7. In the Database Server dialog, make sure to select the following default options:
8. Click Next.
12.Copy the Romexis database files Romexis_db.MDF and Romexis_db.LDF to the folder
C:\Program Files (x86)\MS SQL Server\MSSQL.1\MSSQL\Data\.
14.To start Planmeca Romexis MS SQL Server instance go to the installation DVD's folder
\MSSQL\romexis_db\db_files.
16.After the service is running again, navigate to installation DVD's folder \MSSQL\romexis_db\.
18.Select Other Scripts, check the option Create Database Users, and click Next.
19.Copy the folder romexis_images with all its sub folders from the installation DVD's folder
\MSSQL\romexis_db\db_files\ to the local system root C:\romexis_images.
An example installation of the system is shown on the figure below. PC can also be connected
via internal network.
PM Compact Unit
Hub
PM ethernet
adapter LAN
Planet
PC
1. Open the cuspidor door and remove the electronics control box cover.
2. Connect the Planet cable to the connector located on the left upper corner of the Main PCB.
3. Connect the other end of the Planet cable to the adapter box (white arrows) Attach the box to the
cuspidor support plate (black arrow). Connect the ethernet cable to the adapter box (grey arrow).
1. Route the ethernet cable from the cuspidor to local area network (LAN).
2. Connect the dental unit’s adapter with an ethernet cable to the PC located on the 10.0.0.x
subnet. The dental unit default IP is 10.0.0.1. This must be changed to the clients IP network
configuration.
3. Open the web browser and enter 10.0.0.1 to the address field.
6. Enter the new IP address to the IP address field. The netmask is entered to the IP address field
in format “10.0.0.1 255.255.255.0”.
9. Connect the PC to the dental unit equipped with new IP address to check that the connection
functions. NOTE! Change also your PC IP address to the same Subnet.
1. Start the Planmeca Romexis Configuration application. The user name is sysadm and password
is promax.
This function will search all ethernet connected dental units. New dental units will appear
automatically on the window. To change the dental unit names click Update.
If the search function does not find the dental unit, it can be manually added by clicking the Add
button.
Enter the needed information to the window that appears. Note, that the name, IP address and
Planmeca Romexis server port must be unique. The dental unit IP must be same as entered to
the web browser in step 2 on page 84.
The Planmeca Romexis server port can be any port that has not been in use before.
6. Check on the Server tab that the Planmeca Romexis Server Diagnostic is enabled.
Select the Server tab and restart Planmeca Romexis server: first click Stop service, then Start
service.
2 1
This configuration needs to be performed if the dental unit is equipped with intraoral camera and
the camera freeze function is used.
After the dental unit is connected to Planmeca Romexis Server, it can be configured in Planmeca
Romexis Client.
1. Open the Admin module. Select the desired dental unit from the list (unit equipped with intraoral
camera).
4. Restart Planmeca Romexis client. The intraoral camera freeze function can now be used.
Select Clinic module application. Select Clinic monitoring tab. The names of all the dental units
connected to Planmeca Romexis server are shown at the bottom of the window. Drag and drop
the dental units to the clinic layout. Create a layout if it does not exist.
This tool is used to transfer the database from one location to another for example in case the
client wants to change from one operating system to another or merge two different databases
together.
NOTE Refer to Romexis installation manual for MacOS when transferring database from / to a
Romexis on MacOS.
NOTE When merging databases together, identical patients in different databases are not
merged together by database tool.
NOTE The source and destination databases need to be updated to the same Romexis software
version.
NOTE It is highly recommended to backup the original database(s) before using the Database
tool.
NOTE If realistic implants, crowns or STL imports have been added to the source database's
images, the folder /Planmeca/Romexis/geometries and all its subfolders have to be copied
to the target server computer.
NOTE It is recommended to shut down other processes and executable files not needed to
ensure the database tool has sufficient amount of free memory.
2. Start Romexis Service for Database tool by launching the following script:
start_romexis_server_for_database_tool.bat
Export_Romexis_database.bat
4. Choose the folder where to export the database files by clicking the Browse button.
This may take a few minutes. When export is completed the message Tables were serialised to
file X appears.
7. Copy the output folder containing the *.serial files to the media that will be used to move the
database to another system (if the folder is not there already).
8. Copy the Romexis image file folders into the same folder with the*.serial files:
c:\romexis_cache,
c:\romexis_ergodata
c:\romexis_images
NOTE The database transfer tool renames imported duplicate usernames and device names.
NOTE A statistics window is shown at the end of a merge/import and an export. This page
shows the amount of exported or imported lines in each table. Also renamed duplicate
user names and duplicate device names are listed.
Make a new Planmeca Romexis installation under the same version that was in use when
exporting the data.
NOTE Do not run the script if merging two databases together! The script will empty the target
database.
2. Remove all lines from each table in the target database and reset the tables’ indexing to zero by
running the following script:
\Clear_Romexis_database.bat
NOTE This script can be run only once. If it is ran twice the database indexes get corrupted and
have to be re-installed.
3. Start Romexis server for Database tool by launching the following script:
start_romexis_server_for_database_tool.bat
Import_Romexis_database.bat
5. Choose the location of serialized (*.serial) files by clicking the Browse button.
This may take a few minutes. When serialization is completed the message
Files were de-serialized to database appears.
Patient merging is done using external ID of the patient. Also inactivated patient images will be
taken into account.
7. Open Romexis client and verify that the database has been successfully moved to the new
computer.