CROSSIG FAQ
Installation
When starting CROSSIG the following error messages appear :
The messages show up when the initialization files are missing (Signal group models, configuration files, layouts, etc.). A reason can be an installtion as an “Update” instead of “Full Installation” (setupCrossigVx_x_x.exe) , also there was no former installtion within the choosen installation path (“setupCrossigUpdateVx_x_xTox_x_x.exe does not contain initialisation files anyway). CROSSIG can be started and used but it is not possible to save individual settings.
An installation as a “Full Installation” solves this problem.
Another reason can be that the path to the initialization files (INI folder) is not set correctly. With the installation the INI-files are written directly to the installation path. You can set the path via the Settings.
The license file can be downloaded via the customer login. It has the following name:
liz_croAA_BBBBB__CV1_CMC_CMC_CMC_CMC_CMC_CMC_TC___s__DDD.zip
- AA: Version number e.g. 62 (license file for CROSSIG 6.2.x
- BBBBB: Customer number e.g. 01450
- C: Number of modules as part of the license e.g. CM2 (Coordinnation) or T1 Trends Test station
- DDD: Customer name
A wrong license file will lead to the following error message:
Basic Supply
Fixed Time
openTRELAN
Problem:
I received a supply file (*.KNO) from another CROSSIG workstation and cannot compile it on my CROSSIG workstation. I get the following ERROR message:
*** Warning *** vxe-file “c:\\Non existing path\\intersection name.vxe” cannot be written!
*** Warning *** vxe-file nil cannot be written!
*** ERROR *** Error when creating vxe-file!
Solution:
CROSSIG remembers the path that was last used to create the VXE file. The error occurs if this path does not exist on the computer, is not writable or not reachable.
An existing path must be selected via the folder symbol.
TRENDS Test Station
When starting the TRENDS Test Station the following message appears:
*** FATAL *** Program number is not initialized! P = 11. (754)
*** FATAL *** Major error – session has to be terminated.
Problem:
The called fixed time program does not exists or is not supplied as a variant 0.
Solution:
Either you call an existing signal program with the variant 0 or an existing program is moved to the called number with variant 0.
Ribbon Fixed Time Control->Administration (Section Signal programs)->Mark signal program and “Move”
->Confirm changes with “OK”
NTA Lexicon
Problem:
The following error message appears in the test station after a longer test session:
*** ERROR *** Incorrect value for assignment to variable! Variable = VARG2HC, Value = 32010. (135)
*** ERROR *** Major error – session has to be terminated.
Solution:
The message appears if a value higher than 3200 is handed over to the Historical function HystCy().
From the experience this is most likely the tlfx counter. The reason is that the logic got stuck within a loop. Most probably a question box needs a different coparation or the YES/NO exits have to be switched.
For detailed information this needs a closer look into the result files of the TRENDS Test Station (SIP/SYP). Or the VAD-Debugger.
Problem:
The following error message appears in the test station:
*** ERROR *** Incorrect value for assignment to variable! Variable = VERROR, Value = 32020. (135)
*** ERROR *** Major error – session has to be terminated.
Solution:
The internal “Lexicon” function TimeCalc(), which is used by the functions WTG(), ATEqual(), ATLess() and ATGreater() among others, causes this error intentionally when a non-existent interstage is handed over to the functions.
The calls of these functions must therefore be checked!!!
This behavior is not described in Lexicon Version 1.0 (August 2018).
After importing the lexicon I one of the following error messages from the compiler appear:
*** ERROR *** [xxxx] unallowed detector name (name is not in table)
*** ERROR *** [AG(TRT(21P)>0)A9] unallowed character(s) after signal group name
*** ERROR *** [Kxxxxx] Variable not defined in a table
All detectors that are defined as obligatory (“Must”) in the lexicon have to be defined in the detector table (see page 19 of the lexicon description from August 2018).
All of the obligatory constants have to be supplied in the constants table KTAB (see page 16-18 of the lexicon description from August 2018).
The lexicon also uses fixed signal group names for the public transport. These are 20, 21, 20P and 21P.
To be able to compile an intersection with an imported lexicon the detectors, the signal group and the constants have to exist, as the lexicon refers to them.