Company logo
Operating InstructionsSearchTable of contentsHome
 
 
Procedure for dealing with error messages
 
Error message text
Possible cause
How to fix the problem
Caution! The storage could not be initialized. If the problem still persists after a restart, please contact the service.
The database could not be created on the storage medium.
Restart the terminal.
Active profile cannot be removed!
An attempt was made to delete the currently selected machine profile.
Select another machine profile and then delete the desired machine profile.
Could not find DGPS configuration file!
The internal file containing the DGPS settings could not be found.
Contact our Service team in order to reinstall the software.
Test phase is expired. Please contact your dealer.
Test phase is expired.
Request a license.
Unlock the software.
Error!
 
Contact Customer service.
GPS signal has been lost!
The connection to the GPS receiver has been interrupted.
The position can no longer be determined.
Check and re-connect the cable connections to the GPS receiver.
GPS signal too weak!
The GPS signal quality is too weak, most likely due to shadowing.
Check the mounting of the GPS receiver and your current position. The receiver must be in open view to the sky.
No DGPS available!
No DGPS is available due to receiver shadowing.
Check the mounting of the GPS receiver and your current position. The receiver must be in open view to the sky.
No DGPS is available due to a failure of the correction data service, e.g. EGNOS.
Check the general availability of the service. For EGNOS/WAAS, check and set the proper correction satellites.
Could not read DGPS configuration from GPS receiver!
The serial connection to the GPS receiver has been interrupted.
Check and re-connect the cable connections to the GPS receiver.
Could not read e-Dif configuration from GPS receiver!
The serial connection to the GPS receiver has been interrupted.
Check and re-connect the cable connections to the GPS receiver.
Saving failed!
The storage medium was removed before or during saving.
Re-insert the storage medium and re-start the save process.
Writing is not allowed on the storage medium.
Disable write protection on the storage medium.
The storage medium is full or damaged.
Delete unnecessary data from the storage medium and try again.
Invalid status!
 
Contact Customer service.
No sections have been recognized!
No sections are configured in the ISOBUS job computer. Or the connected ISOBUS job computer does not support SECTION-Control.
If possible, configure the sections on the job computer. If the job computer does not support SECTION-Control, you cannot use it.
The implement does not have a working width!
The working width or geometry have not been configured in the ISOBUS job computer.
Configure the ISOBUS job computer.
Correctly set the working width in the job computer; contact the implement manufacturer.
No task started!
The ISOBUS-TC operating mode is configured to “Extended”. Therefore, TRACK-Leader expects a task.
No task was started in ISOBUS-TC.
Start a task in ISOBUS-TC or set the operating mode to “Standard” in ISOBUS-TC.
No valid device data recognized!
The working width or geometry have not been configured in the ISOBUS job computer.
Configure the ISOBUS job computer.
RTK signal lost!
No RTK signal is available due to signal shadowings.
The GPS receiver and base station must be in open view to the sky.
No mobile network reception.
 
You are too far away from the base station (or from a different signal source).
 
Device allocation is not set.
The connection between the Tractor-ECU and ISOBUS-TC has been deactivated.
Activate the connection between the Tractor-ECU and ISOBUS-TC in the Tractor-ECU application.
The device data is still loading.
If this message appears for a long time, the terminal is connected to a job computer that is not responding.
It is possible that you cannot use SECTION-Control with this job computer, because the job computer does not support SECTION-Control. Connect a different job computer to the terminal.
No connected job computer. Connect the job computer or select a machine profile in the Virtual ECU.
TRACK-Leader has not received any information through the connected job computer or there is no connected job computer.
 
Main memory is very low. Suspend your work and restart the terminal.
Too much working data (e.g. of applied areas) is stored in the main memory.
Restart the terminal.