© MOBATIME
108 / 124
801203.10
D
Troubleshooting
Error
→
→
Solution / possible cause
1
DTS 4210 is
restarting
continuously.
Check if the network settings are correct,
especially the hostname and the gateway has to
be configured (when no gateway is available, the
own IP address can be used).
2
LAN LED (left one) is
off.
No connection to the network.
Check network cabling.
3
Opening the menu via
SSH is not possible or
DTS 4210. timecenter
is not or no longer
reachable via
network.
Check network settings in menu 2 Configuration
–> 5 Network (only possible with serial
connection):
- IP-Address, Subnet mask and Gateway must
be set correctly
- Interface should be set to Auto
- Check connection with "Ping"
- When earlier the menu was not correctly exited
(e.g. LAN cable removed), the menu can be
blocked up to 15 minutes.
4
Drift (ppm) of quartz
too high
The drift displayed in the menu
Status
→
Time
→
TIME
INFORMATION AND STATUS is
bigger than stated in the data
sheet.
•
The quartz drift is measured and corrected
continuously. After initial operation, it may take
up to 7 days until optimal accuracy is reached
(with GPS reception).
•
Time correction was carried out manually.
5
System software
update
The system software can be updated using FTP
client software or a USB stick (s. chapter 7
Updates).
Your MOBATIME service informs you of use and
necessity of a software update. If necessary,
they can provide the needed firmware file.
6
Needed information to
contact your
MOBATIME service
Device type, part number, production number
and serial number:
These details are given on the adhesive type
label.
If possible provide the following files for the
analysis:
All files from the directories
/var/log/
and
/etc/
and the file:
/ram/trim.log
.
To copy this files use FTP, e.g. Windows
Explorer with ftp://dts@[IP address], see chapter
7.6.
If the log files cannot be copied, please read
out the current software version:
The software version can be queried in the menu
1 STATUS/9 Versions of the software
Place and date of purchase and of
commissioning of the device.
Most comprehensive possible details of the
malfunction:
Describe the problem, possible causes,
measures taken, the system environment /
operating mode and configuration, etc.