Purchasing & Downloads
When you purchase or rent a ProSig® licence, you receive the installation files and a hardware licence protection device (for a single workstation or server). As part of the maintenance agreement, we ensure that our software remains operational in your company and provide fast, expert user support.
Our terms and conditions are available on request through our Support.
You can find the current system requirements further down the page. If your configuration differs, please contact our Support.
What's New
The release notes summarize new features and bug fixes for ProSig and Classic. Entries are organized by sprint and area and include titles, support or online LOP references, and a description of each change.
Known issues
This overview describes known issues with their support or online LOP ID, product area, title and description. Workarounds are included where available.
FAQ
The FAQ brings together answers to common questions from day-to-day work with ProSig. Questions are organized by date, product version and category, and cover both Classic and EPU.
Feature lists
Feature list – Classic
The Classic feature list maps commands to Ribbonbar menus, descriptions and online help references. It includes, among others, functions for blocks, layers, project synchronization and track construction.
Feature list – EPU
The EPU feature list maps commands to Ribbonbar menus, descriptions and online help references. It includes, among others, tools for track layout and topology, attributes, display and zoom.
ProSig licensing (German)
Guides
Expand each guide to read its contents directly on this page. The original German PDF, including illustrations, is available to download.
Cable overview plan – route variants (German)
The route variants describe how many cable cores are routed to a destination and whether core groups share a cable or use separate cables.
Core-count route variant
- A: Cable cores run to the interlocking (ESTW).
- B: Shared specification, for example for bus or earth cores.
- C: Cable cores end at a cabinet, signal or similar location.
Core-group route variant
- 1: Core groups share one cable, for example power and data.
- 2: A core group uses a separate cable, for example a separate power supply.
- 3: No further cable-route variant is relevant.
KUP core groups: A denotes axle counter, AZSV axle-counter power supply, 1A 100-Hz output, 1E 100-Hz input, E earth core, EOW EOW object, FR and FS FTGS relay and supply sides, GÜ speed monitoring, I Indusi 500, S signal, SS key lock, SV power supply, W point drive and X unknown objects.
Examples
A_1.2_B1_4,A_1.3_B1_4,AZSV__A1_6describes two axle-counter core groups in bus networks 1.2 and 1.3, each with four cores, and six cores for axle-counter power. Data and supply cores run together to the interlocking.- Separate branch cables can be described with
AZSV__A2_2for the power supply and, for example,A_1.2_B1_4for the data connection. I__C3_2denotes two Indusi cores ending at the next element; its route variant is C3.X__A1_2,X__A1_4describes two core groups with different core requirements for an unknown object.
ProSig cable catalogues are stored in the component files kup_kabk.sd[d,e,f.g]. Cable catalogue variants specify which DKLs may be used for an object and can be adapted to the interlocking type.
ProSig Classic – Displaying speed monitoring systems (German)
Under RIL 819.9002 (May 2012 edition), the components of a speed monitoring system are shown individually in the signalling layout plan. The signalling overview plan uses a simplified block diagram.
Layout and cable layout plans
After inserting an impact magnet, select its associated speed monitoring system (GÜ) in the object properties. The corresponding symbol is synchronised with the signalling overview plan. GÜ switch-on and switch-off magnets are read into the database and synchronised with other layout plans, but not as individual symbols in the overview plan.
For cabling in the cable overview plan, insert an additional compact GÜ because the individual components cannot be cabled separately. It may be moved outside the plot area.
Signalling overview plan
When a GÜ is assigned to an impact magnet in the layout plan, the corresponding symbol is generated automatically in the overview plan. Symbols inserted directly from the “Track magnets” library in the overview plan are synchronised to layout plans in the same representation.
Required attributes
- FREQUENZ (FREQUENCY): required for the detailed representation as a track magnet.
- ÜBERWACHTE GESCHWINDIGKEIT (MONITORED SPEED): required for the combined GÜ representation. It can be entered in the impact magnet properties in the layout plan; it is displayed in the overview plan block diagram.
Existing assignments can be changed later. The block diagram is updated the next time the overview plan is opened. Older symbols can be edited in the same way without conversion. Redundant symbols can be deleted, and the updated block diagram moved to the correct position.
ProSig Classic – Kilometrage (German)
ProSig can determine the locations of signalling objects automatically. At least one kilometrage axis must be defined and the objects assigned to it. Each axis is uniquely assigned to a route and receives its route number.
Creating kilometrage axes
- Import from DB-GIS:
KM_GND_INimports kilometrage data from MDB files created by the German Railways GND-Edit. A polyline is created for each route and the route-related information is stored in the drawing.KM_SETZinserts kilometre and hectometre markers and kilometrage jumps at their calculated positions. - Manual construction: Draw a polyline for the axis. Insert kilometre, hectometre and jump markers using
BEZ_MARKorKMSTEINE. Then calculate the axis withKM_CALC; it is stored on a separate layer. - Adding axes to a project: When data is imported or calculated in a project drawing, the kilometrage data is automatically written to the project and made available to other project drawings.
Importing axes from a project
KM_IMPORT imports project axes into a drawing. In a layout plan, the route and coordinates are generated automatically. In an overview plan, first draw a polyline to represent the axis; its segments must be straight, although bends are allowed. The route number and the endpoint assigned the lowest kilometre value are required. Markers can then be created with KM_SETZ.
If object synchronisation jobs are pending during import, do not run them yet. After importing all required axes, run synchronisation with ABGLDBDWG so that objects can be positioned using their kilometrage and route.
Current route and location determination
When a drawing contains several routes, set one as the current route. Newly inserted objects are kilometraged relative to it. Use STR_AKT to view or change the current route. Locations are determined automatically when objects are inserted and updated when they are moved in project drawings. In drawings that are not project-linked, recalculate a location with STANDORT_K. The location is calculated by projecting the object insertion point onto the current route’s kilometrage axis.
Additional functions
STANDORTconfigures automatic location entry and its formatting.KM_PUNKTmarks a specified location on the axis and can transfer the point to a track section.KM_TEXTdetermines the location of a selected point and writes it as text.STR2STEINassigns a route number to kilometre markers, hectometre markers and kilometrage jumps. Recalculate the route withKM_CALCafterwards.
ProSig Classic – Renaming objects in construction phases (German)
A construction phase does not always require moving an entire object into another phase. Often only a label or an auxiliary signal aspect changes. In ProSig Classic, such text can be represented with general annotation blocks. These blocks synchronise across project drawings; additional plain text does not.
Example and prerequisites
In construction phase 2, signal ZR1 is renamed ZR2 and the track-clearance boundary G201/G301 is renamed G202/G302. The changes are made in a signalling layout plan belonging to an existing ProSig project.
Procedure
- Enter the new labels in the object properties of the signal and axle-counter point.
- Use
BEZ_MARKto insert a “General annotation” block for each label to be changed. Use this block, rather than additional plain text, to ensure synchronisation with the project. - Set the annotation block properties for the relevant object and scale. The PDF shows the applicable properties and display values.
- To prevent the old label showing through, use
OBJFRSTto place a masking area beneath each general annotation. - Insert annotation blocks for the old labels to represent their removal in construction phase 2 and set their text properties.
- Use
BAUZUSTto mark the old annotation blocks and masking areas for removal in phase 2. Mark the new annotations for insertion in phase 2 and, where required, as invisible from phase 3 onward.
Before switching phases, use BAUKONF to set the plan-specific options and layer representation. Invisible objects should not be displayed. Show the construction phases with BAULAY.
After synchronising with other project drawings
Synchronised annotations are placed on their assigned construction-phase layers. In layout plans, they use Gauss-Krüger coordinates; in overview plans, their positions are based on kilometrage. Masking areas are not synchronised and must be recreated in each project drawing. Adjust annotation blocks to the visible attributes if needed. Before displaying the phases, update the configuration with BAUKONF and then use BAULAY.
General annotation blocks can also be used for other visible object attributes and text that must be synchronised with project drawings.
ProSig Classic – ProSig project (German)
A ProSig project manages signalling objects in a project database and synchronises changes between assigned drawings and schedules. A project must be created and contain at least one drawing. Not every element is synchronised project-wide; exceptions include certain structures, signal bridges, cable-plan elements and level-crossing symbols. The cable overview plan is not supported as a separate project plan type.
Creating a project and assigning drawings
Use PROJMANAGER to organise projects and drawings. When creating a project, specify its storage location and name; the project folder is named ppj_<project name>. Assigned drawings are managed in encrypted form in this folder.
When the first drawing is added, its existing ProSig objects and relevant properties are written to the project. If the drawing contains multiple standards, synchronisation may be required once for each standard. Track layout is not imported automatically; use DBINGL when required.
When adding another drawing without ProSig objects, the project creates synchronisation jobs for the objects already stored. If the drawing already contains ProSig objects, the project assistant attempts to match drawing objects with database objects. Unmatched objects can be handled manually, deleted from the drawing or adopted as new project objects. Review and run the offered synchronisation jobs to keep the project drawing consistent.
Track layout and project copies
Track elements such as track axes, points and crossings are not imported automatically. Use DBINGL to import all or selected track elements; synchronisation jobs are created for other project drawings. To copy or hand over a project, copy the entire ppj folder.
Database-based project work
Changes to project-relevant signalling objects are written to the database and generate synchronisation jobs for other drawings. Jobs run when a drawing is opened or can be started manually with ABGLDBDWG. In overview plans, object positions are based on kilometrage. After assigning an overview plan, import the kilometrage axes before running synchronisation jobs. Location changes made in layout plans can be adjusted in overview plans with KM_KORR.
Synchronisation behaviour depends on the plan type. Layout and overview plans, for example, synchronise creation and deletion of ProSig objects, attribute values and construction-phase markings; position changes made in overview plans are not propagated to other drawings. Insulation plans mainly synchronise attribute values. The PDF contains the full plan-type tables.
Use DBATTE to view or change an object’s properties. OE edits attributes for a selection of objects. DBMARK marks the objects in a drawing that are linked to the project.
Checking a project
- Check that all drawings listed in the project manager have been provided.
- Review and run pending synchronisation jobs in all project drawings.
- Use
PROJPRUEFto check synchronisation between a drawing and the project database. - Use
ABGLDBDWGandDBINto check that data has been synchronised in both directions. - Use
PRUEFGGto check graphic groups and the AutoCAD drawing check to verify drawing integrity. - Periodically run
BEREINIGto remove unused data and avoid unnecessary file size.
System requirements
System requirements for Classic
Version: ProSig 6.42
Operating system: Microsoft® Windows® 10, 64-bit (with feature updates from 2019 onward)
Microsoft Office for Windows®: Microsoft® Office, 64-bit
Autodesk software: AutoCAD 2022 to 2024
.NET Framework: Version 4.5
HASP: The applicable HASP (Thales) system requirements apply; see ProSig Licensing.
ObjectDCL: The applicable ObjectDCL (Ductisoft) system requirements also apply.
Minimum hardware requirements:
- Hardware supported by Autodesk, including graphics card
- Memory: 12 GB RAM
- Free disk space: 2 GB
- Ports: USB interface
- Minimum display resolution: 1280 × 1024 pixels
- Recommended display resolution: 1920 × 1080 pixels (Full HD)
- Recommended number of displays: 2
Document date: 26 August 2026. All information is subject to change.
System requirements for EPU
Version: ProSig® EPU
Operating system: Microsoft® Windows® 11, 64-bit (including all service packs)
Microsoft Office for Windows®: Microsoft® Office, 64-bit (including all service packs)
Autodesk software: AutoCAD 2024 to 2026
.NET Framework: Version 8.0
HASP: The applicable HASP (Thales) system requirements apply; see ProSig Licensing.
ObjectDCL: The applicable ObjectDCL (Ductisoft) system requirements also apply.
Minimum hardware requirements:
- Hardware supported by Autodesk, including graphics card
- Memory: 16 GB RAM
- Free disk space: 2 GB
- Ports: USB interface
- Minimum display resolution: 1920 × 1080 pixels (Full HD)
- Recommended number of displays: 2
Performance: EPU processing speed depends on system characteristics (hardware, software and, where applicable, network) as well as the size and complexity of ProSig/CAD projects. An EPU project should not exceed 15,000 system objects. The medium-sized but fairly complex sample station “P-Hausen” contains 5,166 system objects (435 geo-edges, 29 switch elements and 132 signals). Consider splitting significantly larger projects into two or more projects.
Document date: 20 October 2026. All information is subject to change.