<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://wiki.iplog.eu/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Z013</id>
		<title>IPLOG - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="http://wiki.iplog.eu/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Z013"/>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/wiki/Special:Contributions/Z013"/>
		<updated>2026-04-03T19:28:25Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.30.0</generator>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=Firmware_Upgrade&amp;diff=1041</id>
		<title>Firmware Upgrade</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=Firmware_Upgrade&amp;diff=1041"/>
				<updated>2022-01-14T12:46:06Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In this document we will focus on Firmware Upgrade.&lt;br /&gt;
&lt;br /&gt;
== About Firmware == &lt;br /&gt;
&lt;br /&gt;
IPLOG-GAMA firmware is divided into three parts.&lt;br /&gt;
&lt;br /&gt;
'''Recovery image''' - This part is a read only image and used to possibility restore the system in the event of a main firmware fatal error of parts '''Firmware Image 1 and 2'''.&lt;br /&gt;
&lt;br /&gt;
'''Firmware Image 1 and 2''' - These two parts contain the main firmware images. One is marked as '''&amp;quot;current&amp;quot;''', this firmare is running at the present time. When the Firmware Upgrade starts the new Firmware Image is written to the second Image part which is not running. Thanks to this feature, the firmware that works properly can not be damaged. After a successful upload, the new one will startup with the next reboot and market as '''&amp;quot;current&amp;quot;'''. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== WEB interface Upgrade ==&lt;br /&gt;
&lt;br /&gt;
=== 1. Open &amp;quot;Upgrade&amp;quot; page === &lt;br /&gt;
[[File:Upgrade_Main_Page.png|800px]]&lt;br /&gt;
&lt;br /&gt;
'''Running''' - informs about right now running image (firmware version) &amp;lt;br&amp;gt;&lt;br /&gt;
'''Recovery''' - version of recovery image &amp;lt;br&amp;gt;&lt;br /&gt;
'''Image 1''' - version of Image 1 &amp;lt;br&amp;gt;&lt;br /&gt;
'''Image 2''' - version of Image 2 &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Upload new firmware ===&lt;br /&gt;
Press the &amp;quot;Choose File&amp;quot; button and enter the path to the new firmware file.&lt;br /&gt;
&lt;br /&gt;
[[File:Upgrade_File_Uploading.png|800px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. Upgrade button ===&lt;br /&gt;
Upgrade button starts to be in Yellow, press it.&lt;br /&gt;
&lt;br /&gt;
[[File:Upgrade_button.png|400px]]&lt;br /&gt;
&lt;br /&gt;
By press yellow upgrade button the upgrading process starts. &lt;br /&gt;
&lt;br /&gt;
[[File:Upgrade_Running.png|800px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 4. Reboot ===&lt;br /&gt;
In the end the device will be rebooted. The upgrade process is done.&lt;br /&gt;
&lt;br /&gt;
[[File:Upgrade_Reboot.png|800px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== BASH Upgrade ==&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
}}&lt;br /&gt;
Shows the current version of Recovery and Firmware images. &lt;br /&gt;
&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   recovery&lt;br /&gt;
version: 2.0.8811&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 1 (current)   //&amp;quot;current&amp;quot; label informs about right now running firmware&lt;br /&gt;
version: 12.0.8824&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 2&lt;br /&gt;
version: 12.0.8811&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Source of New Firmware Image =&lt;br /&gt;
&lt;br /&gt;
==  1. Remote Data Storage ==&lt;br /&gt;
&lt;br /&gt;
=== a) Windows ===&lt;br /&gt;
&lt;br /&gt;
To copy files between IPLOG-GAMA(Linux) and Windows there is a need a third-party tool. For example it is possible to use [https://winscp.net/eng/index.php WinSCP]. &lt;br /&gt;
&lt;br /&gt;
* Download, Install and Open the WinSCP.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Connection Configuration ====&lt;br /&gt;
&lt;br /&gt;
'''Host name''' - The IP address of IPLOG-GAMA, the default IP address is on the housing.&lt;br /&gt;
&lt;br /&gt;
'''User name''' - The default user name is '''root''' and without a password.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPConnection.png|300px]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Connection Warning ==== &lt;br /&gt;
&lt;br /&gt;
For every new connection there is a Warning message shown, if you trust this remote device, confirm by clicking the '''YES''' or '''NO''' and this new session will or will not be saved according to your choice.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPConnectionWarning.png|300px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Upload Firmware Image File (.tar) ====&lt;br /&gt;
&lt;br /&gt;
Select a source file with a new firmware image to upload to the IPLOG-GAMA and press the '''F5''' button to start the upload. For a target location use for example '''/tmp/''' folder. &lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPUploadFile.png|300px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
WinSCP Starts Image Uploading.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPCopiing.png|300px]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
After a Successful Upload Close the WinSCP Session.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== b) Linux ===&lt;br /&gt;
'''SCP or secure copy''' allows secure transferring of files between the local host and the remote host or between two remote hosts.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# scp root@192.168.6.61:/home/user/12.0.8958.tar /tmp/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Command '''scp''' copy file '''12.0.8958.tar''' of '''/home/user/''' folder to remote pc '''root'''(user)'''@192.168.6.61'''(ip address) to local folder '''/tmp/''' on IPLOG-GAMA.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== 2. Local USB ==&lt;br /&gt;
For USB there is not a direct command to copy files of USB to IPLOG-GAMA unit, therefore the USB must be &amp;quot;mounted&amp;quot; to some directory at the beginning.&lt;br /&gt;
 &lt;br /&gt;
Create a new folder(usb) to '''/mnt/''' directory by command '''mkdir'''.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# root@iplog:~# mkdir /mnt/usb/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Use the '''dmesg''' command which typically contains the messages produced by the device drivers.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# dmesg&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This prints the message buffer to the screen. The USB name is typically a '''sda1'''.&lt;br /&gt;
&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
usb 1-2: new high-speed USB device number 3 using atmel-ehci&lt;br /&gt;
usb 1-2: New USB device found, idVendor=090c, idProduct=1000&lt;br /&gt;
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3&lt;br /&gt;
usb 1-2: Product: USB DISK&lt;br /&gt;
usb 1-2: Manufacturer: SMI Corporation&lt;br /&gt;
usb 1-2: SerialNumber: AA04012700014703&lt;br /&gt;
usb-storage 1-2:1.0: USB Mass Storage device detected&lt;br /&gt;
scsi host0: usb-storage 1-2:1.0&lt;br /&gt;
scsi 0:0:0:0: Direct-Access     USB2.0   FlashDisk        1100 PQ: 0 ANSI: 0 CCS&lt;br /&gt;
sd 0:0:0:0: [sda] 1974272 512-byte logical blocks: (1.01 GB/964 MiB)&lt;br /&gt;
sd 0:0:0:0: [sda] Write Protect is off&lt;br /&gt;
sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00&lt;br /&gt;
sd 0:0:0:0: [sda] No Caching mode page found&lt;br /&gt;
sd 0:0:0:0: [sda] Assuming drive cache: write through&lt;br /&gt;
 sda: sda1&lt;br /&gt;
sd 0:0:0:0: [sda] Attached SCSI removable disk&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Mount the USB (sda1) to /mnt/usb directory&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# mount /dev/sda1 /mnt/usb/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Tip|TipText=Check the mnt/usb/ folder content by command '''root@iplog:~# ls /mnt/usb/'''}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Run Firmware Upgrade =&lt;br /&gt;
&lt;br /&gt;
Basic command to run the firmware upgrade.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /new_firmware_image_destination&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
How to run the firmware upgrade of ''' &amp;quot;Remote Data Storage&amp;quot; ''' examples (Windows or Linux).&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /tmp/12.0.8958.tar&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
How to run the firmware upgrade of ''' &amp;quot;Mount the Local USB&amp;quot; ''' example.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /mnt/usb/12.0.8958.tar&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example of the process of firmware upgrading.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=&lt;br /&gt;
FIRMWARE IMAGE&lt;br /&gt;
==============&lt;br /&gt;
filename:        /mnt/usb/12.0.8958.tar&lt;br /&gt;
type:            2&lt;br /&gt;
execute:         metel-firmware&lt;br /&gt;
executing:   /tmp/metel-firmware --skip-tar-script /mnt/usb/12.0.8958.tar&lt;br /&gt;
&lt;br /&gt;
FIRMWARE IMAGE&lt;br /&gt;
==============&lt;br /&gt;
filename:        /mnt/usb/12.0.8958.tar&lt;br /&gt;
type:            2&lt;br /&gt;
execute:         skip&lt;br /&gt;
&lt;br /&gt;
EEPROM&lt;br /&gt;
======&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
PARTITION&lt;br /&gt;
=========&lt;br /&gt;
total:           2&lt;br /&gt;
current:         3&lt;br /&gt;
partition 3:     valid&lt;br /&gt;
partition 4:     invalid&lt;br /&gt;
upgrade:         4&lt;br /&gt;
&lt;br /&gt;
UPGRADE&lt;br /&gt;
=======&lt;br /&gt;
partition 4 has been initialized&lt;br /&gt;
firmware has been extracted&lt;br /&gt;
writing dtb /tmp/iplog-g2_27042017_A0_io-uart_if-uarten.dtb&lt;br /&gt;
writing dtb /tmp/iplog-g2_27042017_A0_io-none_if-none.dtb&lt;br /&gt;
writing kernel /tmp/zImage&lt;br /&gt;
writing rootfs /tmp/rootfs.ubi&lt;br /&gt;
valid boot header to partition 4 has been added&lt;br /&gt;
invalid boot header to partition 3 has been added&lt;br /&gt;
=== UPGRADE DONE ===&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
After the firmware upgrade restart the device by command &amp;quot;reboot&amp;quot;&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# reboot&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Check the successful firmware upgrade.&lt;br /&gt;
The new firmware was uploaded to not runnig firmware image possition and after device reboot used as '''current''' (running).&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   recovery&lt;br /&gt;
version: 2.0.8811&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 1&lt;br /&gt;
version: 12.0.8824&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 2 (current)&lt;br /&gt;
version: 12.0.8958.tar&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=Firmware_Upgrade&amp;diff=1040</id>
		<title>Firmware Upgrade</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=Firmware_Upgrade&amp;diff=1040"/>
				<updated>2022-01-14T12:44:42Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In this document we will focus on Firmware Upgrade.&lt;br /&gt;
&lt;br /&gt;
== About Firmware == &lt;br /&gt;
&lt;br /&gt;
IPLOG-GAMA firmware is divided into three parts.&lt;br /&gt;
&lt;br /&gt;
'''Recovery image''' - This part is a read only image and used to possibility restore the system in the event of a main firmware fatal error of parts '''Firmware Image 1 and 2'''.&lt;br /&gt;
&lt;br /&gt;
'''Firmware Image 1 and 2''' - These two parts contain the main firmware images. One is marked as '''&amp;quot;current&amp;quot;''', this firmare is running at the present time. When the Firmware Upgrade starts the new Firmware Image is written to the second Image part which is not running. Thanks to this feature, the firmware that works properly can not be damaged. After a successful upload, the new one will startup with the next reboot and market as '''&amp;quot;current&amp;quot;'''. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== WEB interface Upgrade ==&lt;br /&gt;
&lt;br /&gt;
=== 1. Open &amp;quot;Upgrade&amp;quot; page === &lt;br /&gt;
[[File:Upgrade_Main_Page.png|800px]]&lt;br /&gt;
&lt;br /&gt;
'''Running''' - informs about right now running image (firmware version) &amp;lt;br&amp;gt;&lt;br /&gt;
'''Recovery''' - version of recovery image &amp;lt;br&amp;gt;&lt;br /&gt;
'''Image 1''' - version of Image 1 &amp;lt;br&amp;gt;&lt;br /&gt;
'''Image 2''' - version of Image 2 &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Upload new firmware ===&lt;br /&gt;
Press the &amp;quot;Choose File&amp;quot; button and enter the path to the new firmware file.&lt;br /&gt;
&lt;br /&gt;
[[File:Upgrade_File_Uploading.png|800px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. Upgrade button ===&lt;br /&gt;
Upgrade button starts to be in Yellow, press it.&lt;br /&gt;
&lt;br /&gt;
[[File:Upgrade_button.png|400px]]&lt;br /&gt;
&lt;br /&gt;
By press yellow upgrade button the upgrading process starts. &lt;br /&gt;
&lt;br /&gt;
[[File:Upgrade_Running.png|800px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 4. Reboot ===&lt;br /&gt;
At the end the device will be rebooted. The upgrade process is done.&lt;br /&gt;
&lt;br /&gt;
[[File:Upgrade_Reboot.png|800px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== BASH Upgrade ==&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
}}&lt;br /&gt;
Shows the current version of Recovery and Firmware images. &lt;br /&gt;
&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   recovery&lt;br /&gt;
version: 2.0.8811&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 1 (current)   //&amp;quot;current&amp;quot; label informs about right now running firmware&lt;br /&gt;
version: 12.0.8824&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 2&lt;br /&gt;
version: 12.0.8811&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Source of New Firmware Image =&lt;br /&gt;
&lt;br /&gt;
==  1. Remote Data Storage ==&lt;br /&gt;
&lt;br /&gt;
=== a) Windows ===&lt;br /&gt;
&lt;br /&gt;
To copy files between IPLOG-GAMA(Linux) and Windows there is a need a third-party tool. For example it is possible to use [https://winscp.net/eng/index.php WinSCP]. &lt;br /&gt;
&lt;br /&gt;
* Download, Install and Open the WinSCP.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Connection Configuration ====&lt;br /&gt;
&lt;br /&gt;
'''Host name''' - The IP address of IPLOG-GAMA, the default IP address is on the housing.&lt;br /&gt;
&lt;br /&gt;
'''User name''' - The default user name is '''root''' and without a password.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPConnection.png|300px]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Connection Warning ==== &lt;br /&gt;
&lt;br /&gt;
For every new connection there is a Warning message shown, if you trust this remote device, confirm by clicking the '''YES''' or '''NO''' and this new session will or will not be saved according to your choice.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPConnectionWarning.png|300px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Upload Firmware Image File (.tar) ====&lt;br /&gt;
&lt;br /&gt;
Select a source file with a new firmware image to upload to the IPLOG-GAMA and press the '''F5''' button to start the upload. For a target location use for example '''/tmp/''' folder. &lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPUploadFile.png|300px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
WinSCP Starts Image Uploading.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPCopiing.png|300px]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
After a Successful Upload Close the WinSCP Session.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== b) Linux ===&lt;br /&gt;
'''SCP or secure copy''' allows secure transferring of files between the local host and the remote host or between two remote hosts.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# scp root@192.168.6.61:/home/user/12.0.8958.tar /tmp/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Command '''scp''' copy file '''12.0.8958.tar''' of '''/home/user/''' folder to remote pc '''root'''(user)'''@192.168.6.61'''(ip address) to local folder '''/tmp/''' on IPLOG-GAMA.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== 2. Local USB ==&lt;br /&gt;
For USB there is not a direct command to copy files of USB to IPLOG-GAMA unit, therefore the USB must be &amp;quot;mounted&amp;quot; to some directory at the beginning.&lt;br /&gt;
 &lt;br /&gt;
Create a new folder(usb) to '''/mnt/''' directory by command '''mkdir'''.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# root@iplog:~# mkdir /mnt/usb/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Use the '''dmesg''' command which typically contains the messages produced by the device drivers.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# dmesg&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This prints the message buffer to the screen. The USB name is typically a '''sda1'''.&lt;br /&gt;
&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
usb 1-2: new high-speed USB device number 3 using atmel-ehci&lt;br /&gt;
usb 1-2: New USB device found, idVendor=090c, idProduct=1000&lt;br /&gt;
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3&lt;br /&gt;
usb 1-2: Product: USB DISK&lt;br /&gt;
usb 1-2: Manufacturer: SMI Corporation&lt;br /&gt;
usb 1-2: SerialNumber: AA04012700014703&lt;br /&gt;
usb-storage 1-2:1.0: USB Mass Storage device detected&lt;br /&gt;
scsi host0: usb-storage 1-2:1.0&lt;br /&gt;
scsi 0:0:0:0: Direct-Access     USB2.0   FlashDisk        1100 PQ: 0 ANSI: 0 CCS&lt;br /&gt;
sd 0:0:0:0: [sda] 1974272 512-byte logical blocks: (1.01 GB/964 MiB)&lt;br /&gt;
sd 0:0:0:0: [sda] Write Protect is off&lt;br /&gt;
sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00&lt;br /&gt;
sd 0:0:0:0: [sda] No Caching mode page found&lt;br /&gt;
sd 0:0:0:0: [sda] Assuming drive cache: write through&lt;br /&gt;
 sda: sda1&lt;br /&gt;
sd 0:0:0:0: [sda] Attached SCSI removable disk&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Mount the USB (sda1) to /mnt/usb directory&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# mount /dev/sda1 /mnt/usb/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Tip|TipText=Check the mnt/usb/ folder content by command '''root@iplog:~# ls /mnt/usb/'''}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Run Firmware Upgrade =&lt;br /&gt;
&lt;br /&gt;
Basic command to run the firmware upgrade.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /new_firmware_image_destination&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
How to run the firmware upgrade of ''' &amp;quot;Remote Data Storage&amp;quot; ''' examples (Windows or Linux).&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /tmp/12.0.8958.tar&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
How to run the firmware upgrade of ''' &amp;quot;Mount the Local USB&amp;quot; ''' example.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /mnt/usb/12.0.8958.tar&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example of the process of firmware upgrading.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=&lt;br /&gt;
FIRMWARE IMAGE&lt;br /&gt;
==============&lt;br /&gt;
filename:        /mnt/usb/12.0.8958.tar&lt;br /&gt;
type:            2&lt;br /&gt;
execute:         metel-firmware&lt;br /&gt;
executing:   /tmp/metel-firmware --skip-tar-script /mnt/usb/12.0.8958.tar&lt;br /&gt;
&lt;br /&gt;
FIRMWARE IMAGE&lt;br /&gt;
==============&lt;br /&gt;
filename:        /mnt/usb/12.0.8958.tar&lt;br /&gt;
type:            2&lt;br /&gt;
execute:         skip&lt;br /&gt;
&lt;br /&gt;
EEPROM&lt;br /&gt;
======&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
PARTITION&lt;br /&gt;
=========&lt;br /&gt;
total:           2&lt;br /&gt;
current:         3&lt;br /&gt;
partition 3:     valid&lt;br /&gt;
partition 4:     invalid&lt;br /&gt;
upgrade:         4&lt;br /&gt;
&lt;br /&gt;
UPGRADE&lt;br /&gt;
=======&lt;br /&gt;
partition 4 has been initialized&lt;br /&gt;
firmware has been extracted&lt;br /&gt;
writing dtb /tmp/iplog-g2_27042017_A0_io-uart_if-uarten.dtb&lt;br /&gt;
writing dtb /tmp/iplog-g2_27042017_A0_io-none_if-none.dtb&lt;br /&gt;
writing kernel /tmp/zImage&lt;br /&gt;
writing rootfs /tmp/rootfs.ubi&lt;br /&gt;
valid boot header to partition 4 has been added&lt;br /&gt;
invalid boot header to partition 3 has been added&lt;br /&gt;
=== UPGRADE DONE ===&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
After the firmware upgrade restart the device by command &amp;quot;reboot&amp;quot;&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# reboot&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Check the successful firmware upgrade.&lt;br /&gt;
The new firmware was uploaded to not runnig firmware image possition and after device reboot used as '''current''' (running).&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   recovery&lt;br /&gt;
version: 2.0.8811&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 1&lt;br /&gt;
version: 12.0.8824&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 2 (current)&lt;br /&gt;
version: 12.0.8958.tar&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=Firmware_Upgrade&amp;diff=1039</id>
		<title>Firmware Upgrade</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=Firmware_Upgrade&amp;diff=1039"/>
				<updated>2022-01-14T12:44:13Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In this document we will focus on Firmware Upgrade.&lt;br /&gt;
&lt;br /&gt;
== About Firmware == &lt;br /&gt;
&lt;br /&gt;
IPLOG-GAMA firmware is divided into three parts.&lt;br /&gt;
&lt;br /&gt;
'''Recovery image''' - This part is a read only image and used to possibility restore the system in the event of a main firmware fatal error of parts '''Firmware Image 1 and 2'''.&lt;br /&gt;
&lt;br /&gt;
'''Firmware Image 1 and 2''' - These two parts contain the main firmware images. One is marked as '''&amp;quot;current&amp;quot;''', this firmare is running at the present time. When the Firmware Upgrade starts the new Firmware Image is written to the second Image part which is not running. Thanks to this feature, the firmware that works properly can not be damaged. After a successful upload, the new one will startup with the next reboot and market as '''&amp;quot;current&amp;quot;'''. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Upgrade via WEB interface ==&lt;br /&gt;
&lt;br /&gt;
=== 1. Open &amp;quot;Upgrade&amp;quot; page === &lt;br /&gt;
[[File:Upgrade_Main_Page.png|800px]]&lt;br /&gt;
&lt;br /&gt;
'''Running''' - informs about right now running image (firmware version) &amp;lt;br&amp;gt;&lt;br /&gt;
'''Recovery''' - version of recovery image &amp;lt;br&amp;gt;&lt;br /&gt;
'''Image 1''' - version of Image 1 &amp;lt;br&amp;gt;&lt;br /&gt;
'''Image 2''' - version of Image 2 &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Upload new firmware ===&lt;br /&gt;
Press the &amp;quot;Choose File&amp;quot; button and enter the path to the new firmware file.&lt;br /&gt;
&lt;br /&gt;
[[File:Upgrade_File_Uploading.png|800px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. Upgrade button ===&lt;br /&gt;
Upgrade button starts to be in Yellow, press it.&lt;br /&gt;
&lt;br /&gt;
[[File:Upgrade_button.png|400px]]&lt;br /&gt;
&lt;br /&gt;
By press yellow upgrade button the upgrading process starts. &lt;br /&gt;
&lt;br /&gt;
[[File:Upgrade_Running.png|800px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 4. Reboot ===&lt;br /&gt;
At the end the device will be rebooted. The upgrade process is done.&lt;br /&gt;
&lt;br /&gt;
[[File:Upgrade_Reboot.png|800px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== BASH Upgrade ==&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
}}&lt;br /&gt;
Shows the current version of Recovery and Firmware images. &lt;br /&gt;
&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   recovery&lt;br /&gt;
version: 2.0.8811&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 1 (current)   //&amp;quot;current&amp;quot; label informs about right now running firmware&lt;br /&gt;
version: 12.0.8824&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 2&lt;br /&gt;
version: 12.0.8811&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Source of New Firmware Image =&lt;br /&gt;
&lt;br /&gt;
==  1. Remote Data Storage ==&lt;br /&gt;
&lt;br /&gt;
=== a) Windows ===&lt;br /&gt;
&lt;br /&gt;
To copy files between IPLOG-GAMA(Linux) and Windows there is a need a third-party tool. For example it is possible to use [https://winscp.net/eng/index.php WinSCP]. &lt;br /&gt;
&lt;br /&gt;
* Download, Install and Open the WinSCP.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Connection Configuration ====&lt;br /&gt;
&lt;br /&gt;
'''Host name''' - The IP address of IPLOG-GAMA, the default IP address is on the housing.&lt;br /&gt;
&lt;br /&gt;
'''User name''' - The default user name is '''root''' and without a password.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPConnection.png|300px]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Connection Warning ==== &lt;br /&gt;
&lt;br /&gt;
For every new connection there is a Warning message shown, if you trust this remote device, confirm by clicking the '''YES''' or '''NO''' and this new session will or will not be saved according to your choice.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPConnectionWarning.png|300px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Upload Firmware Image File (.tar) ====&lt;br /&gt;
&lt;br /&gt;
Select a source file with a new firmware image to upload to the IPLOG-GAMA and press the '''F5''' button to start the upload. For a target location use for example '''/tmp/''' folder. &lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPUploadFile.png|300px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
WinSCP Starts Image Uploading.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPCopiing.png|300px]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
After a Successful Upload Close the WinSCP Session.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== b) Linux ===&lt;br /&gt;
'''SCP or secure copy''' allows secure transferring of files between the local host and the remote host or between two remote hosts.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# scp root@192.168.6.61:/home/user/12.0.8958.tar /tmp/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Command '''scp''' copy file '''12.0.8958.tar''' of '''/home/user/''' folder to remote pc '''root'''(user)'''@192.168.6.61'''(ip address) to local folder '''/tmp/''' on IPLOG-GAMA.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== 2. Local USB ==&lt;br /&gt;
For USB there is not a direct command to copy files of USB to IPLOG-GAMA unit, therefore the USB must be &amp;quot;mounted&amp;quot; to some directory at the beginning.&lt;br /&gt;
 &lt;br /&gt;
Create a new folder(usb) to '''/mnt/''' directory by command '''mkdir'''.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# root@iplog:~# mkdir /mnt/usb/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Use the '''dmesg''' command which typically contains the messages produced by the device drivers.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# dmesg&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This prints the message buffer to the screen. The USB name is typically a '''sda1'''.&lt;br /&gt;
&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
usb 1-2: new high-speed USB device number 3 using atmel-ehci&lt;br /&gt;
usb 1-2: New USB device found, idVendor=090c, idProduct=1000&lt;br /&gt;
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3&lt;br /&gt;
usb 1-2: Product: USB DISK&lt;br /&gt;
usb 1-2: Manufacturer: SMI Corporation&lt;br /&gt;
usb 1-2: SerialNumber: AA04012700014703&lt;br /&gt;
usb-storage 1-2:1.0: USB Mass Storage device detected&lt;br /&gt;
scsi host0: usb-storage 1-2:1.0&lt;br /&gt;
scsi 0:0:0:0: Direct-Access     USB2.0   FlashDisk        1100 PQ: 0 ANSI: 0 CCS&lt;br /&gt;
sd 0:0:0:0: [sda] 1974272 512-byte logical blocks: (1.01 GB/964 MiB)&lt;br /&gt;
sd 0:0:0:0: [sda] Write Protect is off&lt;br /&gt;
sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00&lt;br /&gt;
sd 0:0:0:0: [sda] No Caching mode page found&lt;br /&gt;
sd 0:0:0:0: [sda] Assuming drive cache: write through&lt;br /&gt;
 sda: sda1&lt;br /&gt;
sd 0:0:0:0: [sda] Attached SCSI removable disk&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Mount the USB (sda1) to /mnt/usb directory&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# mount /dev/sda1 /mnt/usb/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Tip|TipText=Check the mnt/usb/ folder content by command '''root@iplog:~# ls /mnt/usb/'''}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Run Firmware Upgrade =&lt;br /&gt;
&lt;br /&gt;
Basic command to run the firmware upgrade.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /new_firmware_image_destination&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
How to run the firmware upgrade of ''' &amp;quot;Remote Data Storage&amp;quot; ''' examples (Windows or Linux).&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /tmp/12.0.8958.tar&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
How to run the firmware upgrade of ''' &amp;quot;Mount the Local USB&amp;quot; ''' example.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /mnt/usb/12.0.8958.tar&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example of the process of firmware upgrading.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=&lt;br /&gt;
FIRMWARE IMAGE&lt;br /&gt;
==============&lt;br /&gt;
filename:        /mnt/usb/12.0.8958.tar&lt;br /&gt;
type:            2&lt;br /&gt;
execute:         metel-firmware&lt;br /&gt;
executing:   /tmp/metel-firmware --skip-tar-script /mnt/usb/12.0.8958.tar&lt;br /&gt;
&lt;br /&gt;
FIRMWARE IMAGE&lt;br /&gt;
==============&lt;br /&gt;
filename:        /mnt/usb/12.0.8958.tar&lt;br /&gt;
type:            2&lt;br /&gt;
execute:         skip&lt;br /&gt;
&lt;br /&gt;
EEPROM&lt;br /&gt;
======&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
PARTITION&lt;br /&gt;
=========&lt;br /&gt;
total:           2&lt;br /&gt;
current:         3&lt;br /&gt;
partition 3:     valid&lt;br /&gt;
partition 4:     invalid&lt;br /&gt;
upgrade:         4&lt;br /&gt;
&lt;br /&gt;
UPGRADE&lt;br /&gt;
=======&lt;br /&gt;
partition 4 has been initialized&lt;br /&gt;
firmware has been extracted&lt;br /&gt;
writing dtb /tmp/iplog-g2_27042017_A0_io-uart_if-uarten.dtb&lt;br /&gt;
writing dtb /tmp/iplog-g2_27042017_A0_io-none_if-none.dtb&lt;br /&gt;
writing kernel /tmp/zImage&lt;br /&gt;
writing rootfs /tmp/rootfs.ubi&lt;br /&gt;
valid boot header to partition 4 has been added&lt;br /&gt;
invalid boot header to partition 3 has been added&lt;br /&gt;
=== UPGRADE DONE ===&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
After the firmware upgrade restart the device by command &amp;quot;reboot&amp;quot;&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# reboot&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Check the successful firmware upgrade.&lt;br /&gt;
The new firmware was uploaded to not runnig firmware image possition and after device reboot used as '''current''' (running).&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   recovery&lt;br /&gt;
version: 2.0.8811&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 1&lt;br /&gt;
version: 12.0.8824&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 2 (current)&lt;br /&gt;
version: 12.0.8958.tar&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=Firmware_Upgrade&amp;diff=1038</id>
		<title>Firmware Upgrade</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=Firmware_Upgrade&amp;diff=1038"/>
				<updated>2022-01-14T12:40:46Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In this document we will focus on Firmware Upgrade.&lt;br /&gt;
&lt;br /&gt;
== About Firmware == &lt;br /&gt;
&lt;br /&gt;
IPLOG-GAMA firmware is divided into three parts.&lt;br /&gt;
&lt;br /&gt;
'''Recovery image''' - This part is a read only image and used to possibility restore the system in the event of a main firmware fatal error of parts '''Firmware Image 1 and 2'''.&lt;br /&gt;
&lt;br /&gt;
'''Firmware Image 1 and 2''' - These two parts contain the main firmware images. One is marked as '''&amp;quot;current&amp;quot;''', this firmare is running at the present time. When the Firmware Upgrade starts the new Firmware Image is written to the second Image part which is not running. Thanks to this feature, the firmware that works properly can not be damaged. After a successful upload, the new one will startup with the next reboot and market as '''&amp;quot;current&amp;quot;'''. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Upgrade via WEB interface ==&lt;br /&gt;
=== 1. Open &amp;quot;Upgrade&amp;quot; page === &lt;br /&gt;
[[File:Upgrade_Main_Page.png|800px]]&lt;br /&gt;
&lt;br /&gt;
'''Running''' - informs about right now running image (firmware version) &amp;lt;br&amp;gt;&lt;br /&gt;
'''Recovery''' - version of recovery image &amp;lt;br&amp;gt;&lt;br /&gt;
'''Image 1''' - version of Image 1 &amp;lt;br&amp;gt;&lt;br /&gt;
'''Image 2''' - version of Image 2 &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Upload new firmware ===&lt;br /&gt;
Press the &amp;quot;Choose File&amp;quot; button and enter the path to the new firmware file.&lt;br /&gt;
&lt;br /&gt;
[[File:Upgrade_File_Uploading.png|800px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. Upgrade button ===&lt;br /&gt;
Upgrade button starts to be in Yellow, press it.&lt;br /&gt;
&lt;br /&gt;
[[File:Upgrade_button.png|800px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 4. Upgrade run ====&lt;br /&gt;
By press yellow upgrade button the upgrading process starts. &lt;br /&gt;
&lt;br /&gt;
[[File:Upgrade_Running.png|800px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 5. Reboot ===&lt;br /&gt;
At the end the device will be rebooted. The upgrade process is done.&lt;br /&gt;
&lt;br /&gt;
[[File:Upgrade_Reboot.png|800px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== BASH Upgrade ==&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
}}&lt;br /&gt;
Shows the current version of Recovery and Firmware images. &lt;br /&gt;
&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   recovery&lt;br /&gt;
version: 2.0.8811&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 1 (current)   //&amp;quot;current&amp;quot; label informs about right now running firmware&lt;br /&gt;
version: 12.0.8824&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 2&lt;br /&gt;
version: 12.0.8811&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Source of New Firmware Image =&lt;br /&gt;
&lt;br /&gt;
==  1. Remote Data Storage ==&lt;br /&gt;
&lt;br /&gt;
=== a) Windows ===&lt;br /&gt;
&lt;br /&gt;
To copy files between IPLOG-GAMA(Linux) and Windows there is a need a third-party tool. For example it is possible to use [https://winscp.net/eng/index.php WinSCP]. &lt;br /&gt;
&lt;br /&gt;
* Download, Install and Open the WinSCP.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Connection Configuration ====&lt;br /&gt;
&lt;br /&gt;
'''Host name''' - The IP address of IPLOG-GAMA, the default IP address is on the housing.&lt;br /&gt;
&lt;br /&gt;
'''User name''' - The default user name is '''root''' and without a password.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPConnection.png|300px]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Connection Warning ==== &lt;br /&gt;
&lt;br /&gt;
For every new connection there is a Warning message shown, if you trust this remote device, confirm by clicking the '''YES''' or '''NO''' and this new session will or will not be saved according to your choice.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPConnectionWarning.png|300px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Upload Firmware Image File (.tar) ====&lt;br /&gt;
&lt;br /&gt;
Select a source file with a new firmware image to upload to the IPLOG-GAMA and press the '''F5''' button to start the upload. For a target location use for example '''/tmp/''' folder. &lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPUploadFile.png|300px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
WinSCP Starts Image Uploading.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPCopiing.png|300px]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
After a Successful Upload Close the WinSCP Session.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== b) Linux ===&lt;br /&gt;
'''SCP or secure copy''' allows secure transferring of files between the local host and the remote host or between two remote hosts.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# scp root@192.168.6.61:/home/user/12.0.8958.tar /tmp/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Command '''scp''' copy file '''12.0.8958.tar''' of '''/home/user/''' folder to remote pc '''root'''(user)'''@192.168.6.61'''(ip address) to local folder '''/tmp/''' on IPLOG-GAMA.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== 2. Local USB ==&lt;br /&gt;
For USB there is not a direct command to copy files of USB to IPLOG-GAMA unit, therefore the USB must be &amp;quot;mounted&amp;quot; to some directory at the beginning.&lt;br /&gt;
 &lt;br /&gt;
Create a new folder(usb) to '''/mnt/''' directory by command '''mkdir'''.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# root@iplog:~# mkdir /mnt/usb/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Use the '''dmesg''' command which typically contains the messages produced by the device drivers.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# dmesg&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This prints the message buffer to the screen. The USB name is typically a '''sda1'''.&lt;br /&gt;
&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
usb 1-2: new high-speed USB device number 3 using atmel-ehci&lt;br /&gt;
usb 1-2: New USB device found, idVendor=090c, idProduct=1000&lt;br /&gt;
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3&lt;br /&gt;
usb 1-2: Product: USB DISK&lt;br /&gt;
usb 1-2: Manufacturer: SMI Corporation&lt;br /&gt;
usb 1-2: SerialNumber: AA04012700014703&lt;br /&gt;
usb-storage 1-2:1.0: USB Mass Storage device detected&lt;br /&gt;
scsi host0: usb-storage 1-2:1.0&lt;br /&gt;
scsi 0:0:0:0: Direct-Access     USB2.0   FlashDisk        1100 PQ: 0 ANSI: 0 CCS&lt;br /&gt;
sd 0:0:0:0: [sda] 1974272 512-byte logical blocks: (1.01 GB/964 MiB)&lt;br /&gt;
sd 0:0:0:0: [sda] Write Protect is off&lt;br /&gt;
sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00&lt;br /&gt;
sd 0:0:0:0: [sda] No Caching mode page found&lt;br /&gt;
sd 0:0:0:0: [sda] Assuming drive cache: write through&lt;br /&gt;
 sda: sda1&lt;br /&gt;
sd 0:0:0:0: [sda] Attached SCSI removable disk&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Mount the USB (sda1) to /mnt/usb directory&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# mount /dev/sda1 /mnt/usb/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Tip|TipText=Check the mnt/usb/ folder content by command '''root@iplog:~# ls /mnt/usb/'''}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Run Firmware Upgrade =&lt;br /&gt;
&lt;br /&gt;
Basic command to run the firmware upgrade.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /new_firmware_image_destination&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
How to run the firmware upgrade of ''' &amp;quot;Remote Data Storage&amp;quot; ''' examples (Windows or Linux).&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /tmp/12.0.8958.tar&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
How to run the firmware upgrade of ''' &amp;quot;Mount the Local USB&amp;quot; ''' example.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /mnt/usb/12.0.8958.tar&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example of the process of firmware upgrading.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=&lt;br /&gt;
FIRMWARE IMAGE&lt;br /&gt;
==============&lt;br /&gt;
filename:        /mnt/usb/12.0.8958.tar&lt;br /&gt;
type:            2&lt;br /&gt;
execute:         metel-firmware&lt;br /&gt;
executing:   /tmp/metel-firmware --skip-tar-script /mnt/usb/12.0.8958.tar&lt;br /&gt;
&lt;br /&gt;
FIRMWARE IMAGE&lt;br /&gt;
==============&lt;br /&gt;
filename:        /mnt/usb/12.0.8958.tar&lt;br /&gt;
type:            2&lt;br /&gt;
execute:         skip&lt;br /&gt;
&lt;br /&gt;
EEPROM&lt;br /&gt;
======&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
PARTITION&lt;br /&gt;
=========&lt;br /&gt;
total:           2&lt;br /&gt;
current:         3&lt;br /&gt;
partition 3:     valid&lt;br /&gt;
partition 4:     invalid&lt;br /&gt;
upgrade:         4&lt;br /&gt;
&lt;br /&gt;
UPGRADE&lt;br /&gt;
=======&lt;br /&gt;
partition 4 has been initialized&lt;br /&gt;
firmware has been extracted&lt;br /&gt;
writing dtb /tmp/iplog-g2_27042017_A0_io-uart_if-uarten.dtb&lt;br /&gt;
writing dtb /tmp/iplog-g2_27042017_A0_io-none_if-none.dtb&lt;br /&gt;
writing kernel /tmp/zImage&lt;br /&gt;
writing rootfs /tmp/rootfs.ubi&lt;br /&gt;
valid boot header to partition 4 has been added&lt;br /&gt;
invalid boot header to partition 3 has been added&lt;br /&gt;
=== UPGRADE DONE ===&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
After the firmware upgrade restart the device by command &amp;quot;reboot&amp;quot;&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# reboot&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Check the successful firmware upgrade.&lt;br /&gt;
The new firmware was uploaded to not runnig firmware image possition and after device reboot used as '''current''' (running).&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   recovery&lt;br /&gt;
version: 2.0.8811&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 1&lt;br /&gt;
version: 12.0.8824&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 2 (current)&lt;br /&gt;
version: 12.0.8958.tar&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=Firmware_Upgrade&amp;diff=1037</id>
		<title>Firmware Upgrade</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=Firmware_Upgrade&amp;diff=1037"/>
				<updated>2022-01-14T10:16:53Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In this document we will focus on Firmware Upgrade.&lt;br /&gt;
&lt;br /&gt;
== About Firmware == &lt;br /&gt;
&lt;br /&gt;
IPLOG-GAMA firmware is divided into three parts.&lt;br /&gt;
&lt;br /&gt;
'''Recovery image''' - This part is a read only image and used to possibility restore the system in the event of a main firmware fatal error of parts '''Firmware Image 1 and 2'''.&lt;br /&gt;
&lt;br /&gt;
'''Firmware Image 1 and 2''' - These two parts contain the main firmware images. One is marked as '''&amp;quot;current&amp;quot;''', this firmare is running at the present time. When the Firmware Upgrade starts the new Firmware Image is written to the second Image part which is not running. Thanks to this feature, the firmware that works properly can not be damaged. After a successful upload, the new one will startup with the next reboot and market as '''&amp;quot;current&amp;quot;'''. &lt;br /&gt;
&lt;br /&gt;
=== WEB Page ===&lt;br /&gt;
[[File:Upgrade_Main_Page.png|800px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== BASH ===&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
}}&lt;br /&gt;
Shows the current version of Recovery and Firmware images. &lt;br /&gt;
&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   recovery&lt;br /&gt;
version: 2.0.8811&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 1 (current)   //&amp;quot;current&amp;quot; label informs about right now running firmware&lt;br /&gt;
version: 12.0.8824&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 2&lt;br /&gt;
version: 12.0.8811&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Source of New Firmware Image =&lt;br /&gt;
&lt;br /&gt;
==  1. Remote Data Storage ==&lt;br /&gt;
&lt;br /&gt;
=== a) Windows ===&lt;br /&gt;
&lt;br /&gt;
To copy files between IPLOG-GAMA(Linux) and Windows there is a need a third-party tool. For example it is possible to use [https://winscp.net/eng/index.php WinSCP]. &lt;br /&gt;
&lt;br /&gt;
* Download, Install and Open the WinSCP.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Connection Configuration ====&lt;br /&gt;
&lt;br /&gt;
'''Host name''' - The IP address of IPLOG-GAMA, the default IP address is on the housing.&lt;br /&gt;
&lt;br /&gt;
'''User name''' - The default user name is '''root''' and without a password.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPConnection.png|300px]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Connection Warning ==== &lt;br /&gt;
&lt;br /&gt;
For every new connection there is a Warning message shown, if you trust this remote device, confirm by clicking the '''YES''' or '''NO''' and this new session will or will not be saved according to your choice.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPConnectionWarning.png|300px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Upload Firmware Image File (.tar) ====&lt;br /&gt;
&lt;br /&gt;
Select a source file with a new firmware image to upload to the IPLOG-GAMA and press the '''F5''' button to start the upload. For a target location use for example '''/tmp/''' folder. &lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPUploadFile.png|300px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
WinSCP Starts Image Uploading.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPCopiing.png|300px]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
After a Successful Upload Close the WinSCP Session.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== b) Linux ===&lt;br /&gt;
'''SCP or secure copy''' allows secure transferring of files between the local host and the remote host or between two remote hosts.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# scp root@192.168.6.61:/home/user/12.0.8958.tar /tmp/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Command '''scp''' copy file '''12.0.8958.tar''' of '''/home/user/''' folder to remote pc '''root'''(user)'''@192.168.6.61'''(ip address) to local folder '''/tmp/''' on IPLOG-GAMA.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== 2. Local USB ==&lt;br /&gt;
For USB there is not a direct command to copy files of USB to IPLOG-GAMA unit, therefore the USB must be &amp;quot;mounted&amp;quot; to some directory at the beginning.&lt;br /&gt;
 &lt;br /&gt;
Create a new folder(usb) to '''/mnt/''' directory by command '''mkdir'''.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# root@iplog:~# mkdir /mnt/usb/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Use the '''dmesg''' command which typically contains the messages produced by the device drivers.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# dmesg&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This prints the message buffer to the screen. The USB name is typically a '''sda1'''.&lt;br /&gt;
&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
usb 1-2: new high-speed USB device number 3 using atmel-ehci&lt;br /&gt;
usb 1-2: New USB device found, idVendor=090c, idProduct=1000&lt;br /&gt;
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3&lt;br /&gt;
usb 1-2: Product: USB DISK&lt;br /&gt;
usb 1-2: Manufacturer: SMI Corporation&lt;br /&gt;
usb 1-2: SerialNumber: AA04012700014703&lt;br /&gt;
usb-storage 1-2:1.0: USB Mass Storage device detected&lt;br /&gt;
scsi host0: usb-storage 1-2:1.0&lt;br /&gt;
scsi 0:0:0:0: Direct-Access     USB2.0   FlashDisk        1100 PQ: 0 ANSI: 0 CCS&lt;br /&gt;
sd 0:0:0:0: [sda] 1974272 512-byte logical blocks: (1.01 GB/964 MiB)&lt;br /&gt;
sd 0:0:0:0: [sda] Write Protect is off&lt;br /&gt;
sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00&lt;br /&gt;
sd 0:0:0:0: [sda] No Caching mode page found&lt;br /&gt;
sd 0:0:0:0: [sda] Assuming drive cache: write through&lt;br /&gt;
 sda: sda1&lt;br /&gt;
sd 0:0:0:0: [sda] Attached SCSI removable disk&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Mount the USB (sda1) to /mnt/usb directory&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# mount /dev/sda1 /mnt/usb/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Tip|TipText=Check the mnt/usb/ folder content by command '''root@iplog:~# ls /mnt/usb/'''}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Run Firmware Upgrade =&lt;br /&gt;
&lt;br /&gt;
Basic command to run the firmware upgrade.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /new_firmware_image_destination&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
How to run the firmware upgrade of ''' &amp;quot;Remote Data Storage&amp;quot; ''' examples (Windows or Linux).&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /tmp/12.0.8958.tar&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
How to run the firmware upgrade of ''' &amp;quot;Mount the Local USB&amp;quot; ''' example.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /mnt/usb/12.0.8958.tar&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example of the process of firmware upgrading.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=&lt;br /&gt;
FIRMWARE IMAGE&lt;br /&gt;
==============&lt;br /&gt;
filename:        /mnt/usb/12.0.8958.tar&lt;br /&gt;
type:            2&lt;br /&gt;
execute:         metel-firmware&lt;br /&gt;
executing:   /tmp/metel-firmware --skip-tar-script /mnt/usb/12.0.8958.tar&lt;br /&gt;
&lt;br /&gt;
FIRMWARE IMAGE&lt;br /&gt;
==============&lt;br /&gt;
filename:        /mnt/usb/12.0.8958.tar&lt;br /&gt;
type:            2&lt;br /&gt;
execute:         skip&lt;br /&gt;
&lt;br /&gt;
EEPROM&lt;br /&gt;
======&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
PARTITION&lt;br /&gt;
=========&lt;br /&gt;
total:           2&lt;br /&gt;
current:         3&lt;br /&gt;
partition 3:     valid&lt;br /&gt;
partition 4:     invalid&lt;br /&gt;
upgrade:         4&lt;br /&gt;
&lt;br /&gt;
UPGRADE&lt;br /&gt;
=======&lt;br /&gt;
partition 4 has been initialized&lt;br /&gt;
firmware has been extracted&lt;br /&gt;
writing dtb /tmp/iplog-g2_27042017_A0_io-uart_if-uarten.dtb&lt;br /&gt;
writing dtb /tmp/iplog-g2_27042017_A0_io-none_if-none.dtb&lt;br /&gt;
writing kernel /tmp/zImage&lt;br /&gt;
writing rootfs /tmp/rootfs.ubi&lt;br /&gt;
valid boot header to partition 4 has been added&lt;br /&gt;
invalid boot header to partition 3 has been added&lt;br /&gt;
=== UPGRADE DONE ===&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
After the firmware upgrade restart the device by command &amp;quot;reboot&amp;quot;&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# reboot&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Check the successful firmware upgrade.&lt;br /&gt;
The new firmware was uploaded to not runnig firmware image possition and after device reboot used as '''current''' (running).&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   recovery&lt;br /&gt;
version: 2.0.8811&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 1&lt;br /&gt;
version: 12.0.8824&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 2 (current)&lt;br /&gt;
version: 12.0.8958.tar&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=Firmware_Upgrade&amp;diff=1036</id>
		<title>Firmware Upgrade</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=Firmware_Upgrade&amp;diff=1036"/>
				<updated>2022-01-14T10:15:42Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In this document we will focus on Firmware Upgrade.&lt;br /&gt;
&lt;br /&gt;
== About Firmware == &lt;br /&gt;
&lt;br /&gt;
IPLOG-GAMA firmware is divided into three parts.&lt;br /&gt;
&lt;br /&gt;
'''Recovery image''' - This part is a read only image and used to possibility restore the system in the event of a main firmware fatal error of parts '''Firmware Image 1 and 2'''.&lt;br /&gt;
&lt;br /&gt;
'''Firmware Image 1 and 2''' - These two parts contain the main firmware images. One is marked as '''&amp;quot;current&amp;quot;''', this firmare is running at the present time. When the Firmware Upgrade starts the new Firmware Image is written to the second Image part which is not running. Thanks to this feature, the firmware that works properly can not be damaged. After a successful upload, the new one will startup with the next reboot and market as '''&amp;quot;current&amp;quot;'''. &lt;br /&gt;
&lt;br /&gt;
=== WEB Page ===&lt;br /&gt;
[[File:Upgrade_Main_Page.png|left|800px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== BASH ===&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
}}&lt;br /&gt;
Shows the current version of Recovery and Firmware images. &lt;br /&gt;
&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   recovery&lt;br /&gt;
version: 2.0.8811&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 1 (current)   //&amp;quot;current&amp;quot; label informs about right now running firmware&lt;br /&gt;
version: 12.0.8824&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 2&lt;br /&gt;
version: 12.0.8811&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Source of New Firmware Image =&lt;br /&gt;
&lt;br /&gt;
==  1. Remote Data Storage ==&lt;br /&gt;
&lt;br /&gt;
=== a) Windows ===&lt;br /&gt;
&lt;br /&gt;
To copy files between IPLOG-GAMA(Linux) and Windows there is a need a third-party tool. For example it is possible to use [https://winscp.net/eng/index.php WinSCP]. &lt;br /&gt;
&lt;br /&gt;
* Download, Install and Open the WinSCP.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Connection Configuration ====&lt;br /&gt;
&lt;br /&gt;
'''Host name''' - The IP address of IPLOG-GAMA, the default IP address is on the housing.&lt;br /&gt;
&lt;br /&gt;
'''User name''' - The default user name is '''root''' and without a password.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPConnection.png|300px]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Connection Warning ==== &lt;br /&gt;
&lt;br /&gt;
For every new connection there is a Warning message shown, if you trust this remote device, confirm by clicking the '''YES''' or '''NO''' and this new session will or will not be saved according to your choice.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPConnectionWarning.png|300px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Upload Firmware Image File (.tar) ====&lt;br /&gt;
&lt;br /&gt;
Select a source file with a new firmware image to upload to the IPLOG-GAMA and press the '''F5''' button to start the upload. For a target location use for example '''/tmp/''' folder. &lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPUploadFile.png|300px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
WinSCP Starts Image Uploading.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPCopiing.png|300px]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
After a Successful Upload Close the WinSCP Session.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== b) Linux ===&lt;br /&gt;
'''SCP or secure copy''' allows secure transferring of files between the local host and the remote host or between two remote hosts.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# scp root@192.168.6.61:/home/user/12.0.8958.tar /tmp/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Command '''scp''' copy file '''12.0.8958.tar''' of '''/home/user/''' folder to remote pc '''root'''(user)'''@192.168.6.61'''(ip address) to local folder '''/tmp/''' on IPLOG-GAMA.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== 2. Local USB ==&lt;br /&gt;
For USB there is not a direct command to copy files of USB to IPLOG-GAMA unit, therefore the USB must be &amp;quot;mounted&amp;quot; to some directory at the beginning.&lt;br /&gt;
 &lt;br /&gt;
Create a new folder(usb) to '''/mnt/''' directory by command '''mkdir'''.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# root@iplog:~# mkdir /mnt/usb/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Use the '''dmesg''' command which typically contains the messages produced by the device drivers.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# dmesg&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This prints the message buffer to the screen. The USB name is typically a '''sda1'''.&lt;br /&gt;
&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
usb 1-2: new high-speed USB device number 3 using atmel-ehci&lt;br /&gt;
usb 1-2: New USB device found, idVendor=090c, idProduct=1000&lt;br /&gt;
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3&lt;br /&gt;
usb 1-2: Product: USB DISK&lt;br /&gt;
usb 1-2: Manufacturer: SMI Corporation&lt;br /&gt;
usb 1-2: SerialNumber: AA04012700014703&lt;br /&gt;
usb-storage 1-2:1.0: USB Mass Storage device detected&lt;br /&gt;
scsi host0: usb-storage 1-2:1.0&lt;br /&gt;
scsi 0:0:0:0: Direct-Access     USB2.0   FlashDisk        1100 PQ: 0 ANSI: 0 CCS&lt;br /&gt;
sd 0:0:0:0: [sda] 1974272 512-byte logical blocks: (1.01 GB/964 MiB)&lt;br /&gt;
sd 0:0:0:0: [sda] Write Protect is off&lt;br /&gt;
sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00&lt;br /&gt;
sd 0:0:0:0: [sda] No Caching mode page found&lt;br /&gt;
sd 0:0:0:0: [sda] Assuming drive cache: write through&lt;br /&gt;
 sda: sda1&lt;br /&gt;
sd 0:0:0:0: [sda] Attached SCSI removable disk&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Mount the USB (sda1) to /mnt/usb directory&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# mount /dev/sda1 /mnt/usb/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Tip|TipText=Check the mnt/usb/ folder content by command '''root@iplog:~# ls /mnt/usb/'''}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Run Firmware Upgrade =&lt;br /&gt;
&lt;br /&gt;
Basic command to run the firmware upgrade.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /new_firmware_image_destination&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
How to run the firmware upgrade of ''' &amp;quot;Remote Data Storage&amp;quot; ''' examples (Windows or Linux).&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /tmp/12.0.8958.tar&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
How to run the firmware upgrade of ''' &amp;quot;Mount the Local USB&amp;quot; ''' example.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /mnt/usb/12.0.8958.tar&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example of the process of firmware upgrading.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=&lt;br /&gt;
FIRMWARE IMAGE&lt;br /&gt;
==============&lt;br /&gt;
filename:        /mnt/usb/12.0.8958.tar&lt;br /&gt;
type:            2&lt;br /&gt;
execute:         metel-firmware&lt;br /&gt;
executing:   /tmp/metel-firmware --skip-tar-script /mnt/usb/12.0.8958.tar&lt;br /&gt;
&lt;br /&gt;
FIRMWARE IMAGE&lt;br /&gt;
==============&lt;br /&gt;
filename:        /mnt/usb/12.0.8958.tar&lt;br /&gt;
type:            2&lt;br /&gt;
execute:         skip&lt;br /&gt;
&lt;br /&gt;
EEPROM&lt;br /&gt;
======&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
PARTITION&lt;br /&gt;
=========&lt;br /&gt;
total:           2&lt;br /&gt;
current:         3&lt;br /&gt;
partition 3:     valid&lt;br /&gt;
partition 4:     invalid&lt;br /&gt;
upgrade:         4&lt;br /&gt;
&lt;br /&gt;
UPGRADE&lt;br /&gt;
=======&lt;br /&gt;
partition 4 has been initialized&lt;br /&gt;
firmware has been extracted&lt;br /&gt;
writing dtb /tmp/iplog-g2_27042017_A0_io-uart_if-uarten.dtb&lt;br /&gt;
writing dtb /tmp/iplog-g2_27042017_A0_io-none_if-none.dtb&lt;br /&gt;
writing kernel /tmp/zImage&lt;br /&gt;
writing rootfs /tmp/rootfs.ubi&lt;br /&gt;
valid boot header to partition 4 has been added&lt;br /&gt;
invalid boot header to partition 3 has been added&lt;br /&gt;
=== UPGRADE DONE ===&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
After the firmware upgrade restart the device by command &amp;quot;reboot&amp;quot;&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# reboot&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Check the successful firmware upgrade.&lt;br /&gt;
The new firmware was uploaded to not runnig firmware image possition and after device reboot used as '''current''' (running).&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   recovery&lt;br /&gt;
version: 2.0.8811&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 1&lt;br /&gt;
version: 12.0.8824&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 2 (current)&lt;br /&gt;
version: 12.0.8958.tar&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=Firmware_Upgrade&amp;diff=1035</id>
		<title>Firmware Upgrade</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=Firmware_Upgrade&amp;diff=1035"/>
				<updated>2022-01-14T10:13:20Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In this document we will focus on Firmware Upgrade.&lt;br /&gt;
&lt;br /&gt;
== About Firmware == &lt;br /&gt;
&lt;br /&gt;
IPLOG-GAMA firmware is divided into three parts.&lt;br /&gt;
&lt;br /&gt;
'''Recovery image''' - This part is a read only image and used to possibility restore the system in the event of a main firmware fatal error of parts '''Firmware Image 1 and 2'''.&lt;br /&gt;
&lt;br /&gt;
'''Firmware Image 1 and 2''' - These two parts contain the main firmware images. One is marked as '''&amp;quot;current&amp;quot;''', this firmare is running at the present time. When the Firmware Upgrade starts the new Firmware Image is written to the second Image part which is not running. Thanks to this feature, the firmware that works properly can not be damaged. After a successful upload, the new one will startup with the next reboot and market as '''&amp;quot;current&amp;quot;'''. &lt;br /&gt;
&lt;br /&gt;
=== WEB Page ===&lt;br /&gt;
[[File:Upgrade_Main_Page.png|left|800px]] &amp;lt;br&amp;gt; &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== BASH ===&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
}}&lt;br /&gt;
Shows the current version of Recovery and Firmware images. &lt;br /&gt;
&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   recovery&lt;br /&gt;
version: 2.0.8811&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 1 (current)   //&amp;quot;current&amp;quot; label informs about right now running firmware&lt;br /&gt;
version: 12.0.8824&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 2&lt;br /&gt;
version: 12.0.8811&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Source of New Firmware Image =&lt;br /&gt;
&lt;br /&gt;
==  1. Remote Data Storage ==&lt;br /&gt;
&lt;br /&gt;
=== a) Windows ===&lt;br /&gt;
&lt;br /&gt;
To copy files between IPLOG-GAMA(Linux) and Windows there is a need a third-party tool. For example it is possible to use [https://winscp.net/eng/index.php WinSCP]. &lt;br /&gt;
&lt;br /&gt;
* Download, Install and Open the WinSCP.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Connection Configuration ====&lt;br /&gt;
&lt;br /&gt;
'''Host name''' - The IP address of IPLOG-GAMA, the default IP address is on the housing.&lt;br /&gt;
&lt;br /&gt;
'''User name''' - The default user name is '''root''' and without a password.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPConnection.png|300px]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Connection Warning ==== &lt;br /&gt;
&lt;br /&gt;
For every new connection there is a Warning message shown, if you trust this remote device, confirm by clicking the '''YES''' or '''NO''' and this new session will or will not be saved according to your choice.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPConnectionWarning.png|300px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Upload Firmware Image File (.tar) ====&lt;br /&gt;
&lt;br /&gt;
Select a source file with a new firmware image to upload to the IPLOG-GAMA and press the '''F5''' button to start the upload. For a target location use for example '''/tmp/''' folder. &lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPUploadFile.png|300px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
WinSCP Starts Image Uploading.&lt;br /&gt;
&lt;br /&gt;
[[File:WinSCPCopiing.png|300px]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
After a Successful Upload Close the WinSCP Session.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== b) Linux ===&lt;br /&gt;
'''SCP or secure copy''' allows secure transferring of files between the local host and the remote host or between two remote hosts.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# scp root@192.168.6.61:/home/user/12.0.8958.tar /tmp/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Command '''scp''' copy file '''12.0.8958.tar''' of '''/home/user/''' folder to remote pc '''root'''(user)'''@192.168.6.61'''(ip address) to local folder '''/tmp/''' on IPLOG-GAMA.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== 2. Local USB ==&lt;br /&gt;
For USB there is not a direct command to copy files of USB to IPLOG-GAMA unit, therefore the USB must be &amp;quot;mounted&amp;quot; to some directory at the beginning.&lt;br /&gt;
 &lt;br /&gt;
Create a new folder(usb) to '''/mnt/''' directory by command '''mkdir'''.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# root@iplog:~# mkdir /mnt/usb/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Use the '''dmesg''' command which typically contains the messages produced by the device drivers.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# dmesg&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This prints the message buffer to the screen. The USB name is typically a '''sda1'''.&lt;br /&gt;
&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
usb 1-2: new high-speed USB device number 3 using atmel-ehci&lt;br /&gt;
usb 1-2: New USB device found, idVendor=090c, idProduct=1000&lt;br /&gt;
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3&lt;br /&gt;
usb 1-2: Product: USB DISK&lt;br /&gt;
usb 1-2: Manufacturer: SMI Corporation&lt;br /&gt;
usb 1-2: SerialNumber: AA04012700014703&lt;br /&gt;
usb-storage 1-2:1.0: USB Mass Storage device detected&lt;br /&gt;
scsi host0: usb-storage 1-2:1.0&lt;br /&gt;
scsi 0:0:0:0: Direct-Access     USB2.0   FlashDisk        1100 PQ: 0 ANSI: 0 CCS&lt;br /&gt;
sd 0:0:0:0: [sda] 1974272 512-byte logical blocks: (1.01 GB/964 MiB)&lt;br /&gt;
sd 0:0:0:0: [sda] Write Protect is off&lt;br /&gt;
sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00&lt;br /&gt;
sd 0:0:0:0: [sda] No Caching mode page found&lt;br /&gt;
sd 0:0:0:0: [sda] Assuming drive cache: write through&lt;br /&gt;
 sda: sda1&lt;br /&gt;
sd 0:0:0:0: [sda] Attached SCSI removable disk&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Mount the USB (sda1) to /mnt/usb directory&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# mount /dev/sda1 /mnt/usb/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Tip|TipText=Check the mnt/usb/ folder content by command '''root@iplog:~# ls /mnt/usb/'''}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Run Firmware Upgrade =&lt;br /&gt;
&lt;br /&gt;
Basic command to run the firmware upgrade.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /new_firmware_image_destination&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
How to run the firmware upgrade of ''' &amp;quot;Remote Data Storage&amp;quot; ''' examples (Windows or Linux).&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /tmp/12.0.8958.tar&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
How to run the firmware upgrade of ''' &amp;quot;Mount the Local USB&amp;quot; ''' example.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware /mnt/usb/12.0.8958.tar&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example of the process of firmware upgrading.&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=&lt;br /&gt;
FIRMWARE IMAGE&lt;br /&gt;
==============&lt;br /&gt;
filename:        /mnt/usb/12.0.8958.tar&lt;br /&gt;
type:            2&lt;br /&gt;
execute:         metel-firmware&lt;br /&gt;
executing:   /tmp/metel-firmware --skip-tar-script /mnt/usb/12.0.8958.tar&lt;br /&gt;
&lt;br /&gt;
FIRMWARE IMAGE&lt;br /&gt;
==============&lt;br /&gt;
filename:        /mnt/usb/12.0.8958.tar&lt;br /&gt;
type:            2&lt;br /&gt;
execute:         skip&lt;br /&gt;
&lt;br /&gt;
EEPROM&lt;br /&gt;
======&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
.&lt;br /&gt;
PARTITION&lt;br /&gt;
=========&lt;br /&gt;
total:           2&lt;br /&gt;
current:         3&lt;br /&gt;
partition 3:     valid&lt;br /&gt;
partition 4:     invalid&lt;br /&gt;
upgrade:         4&lt;br /&gt;
&lt;br /&gt;
UPGRADE&lt;br /&gt;
=======&lt;br /&gt;
partition 4 has been initialized&lt;br /&gt;
firmware has been extracted&lt;br /&gt;
writing dtb /tmp/iplog-g2_27042017_A0_io-uart_if-uarten.dtb&lt;br /&gt;
writing dtb /tmp/iplog-g2_27042017_A0_io-none_if-none.dtb&lt;br /&gt;
writing kernel /tmp/zImage&lt;br /&gt;
writing rootfs /tmp/rootfs.ubi&lt;br /&gt;
valid boot header to partition 4 has been added&lt;br /&gt;
invalid boot header to partition 3 has been added&lt;br /&gt;
=== UPGRADE DONE ===&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
After the firmware upgrade restart the device by command &amp;quot;reboot&amp;quot;&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# reboot&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Check the successful firmware upgrade.&lt;br /&gt;
The new firmware was uploaded to not runnig firmware image possition and after device reboot used as '''current''' (running).&lt;br /&gt;
{{NotePre&lt;br /&gt;
|text=root@iplog:~# metel-firmware-version&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   recovery&lt;br /&gt;
version: 2.0.8811&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 1&lt;br /&gt;
version: 12.0.8824&lt;br /&gt;
&lt;br /&gt;
FIRMWARE&lt;br /&gt;
========&lt;br /&gt;
image:   image 2 (current)&lt;br /&gt;
version: 12.0.8958.tar&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=File:Upgrade_Running.png&amp;diff=1034</id>
		<title>File:Upgrade Running.png</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=File:Upgrade_Running.png&amp;diff=1034"/>
				<updated>2022-01-14T10:04:52Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=File:Upgrade_Reboot.png&amp;diff=1033</id>
		<title>File:Upgrade Reboot.png</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=File:Upgrade_Reboot.png&amp;diff=1033"/>
				<updated>2022-01-14T10:04:38Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=File:Upgrade_Main_Page.png&amp;diff=1032</id>
		<title>File:Upgrade Main Page.png</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=File:Upgrade_Main_Page.png&amp;diff=1032"/>
				<updated>2022-01-14T10:04:25Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=File:Upgrade_File_Uploading.png&amp;diff=1031</id>
		<title>File:Upgrade File Uploading.png</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=File:Upgrade_File_Uploading.png&amp;diff=1031"/>
				<updated>2022-01-14T10:04:12Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=File:Upgrade_button.png&amp;diff=1030</id>
		<title>File:Upgrade button.png</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=File:Upgrade_button.png&amp;diff=1030"/>
				<updated>2022-01-14T10:03:43Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1029</id>
		<title>NTPD</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1029"/>
				<updated>2022-01-14T08:47:47Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= NTPD (Network Time Procokol Daemon) =&lt;br /&gt;
== Description ==&lt;br /&gt;
The '''NTPD''' program is an operating-system daemon that sets and maintains a computer system's time in synchronization with Internet-standard time servers. It is a complete implementation of the Network Time Protocol (NTP) version 4, but retains compatibility with versions 1, 2, and 3 as defined by RFC 1059, RFC 1119, and RFC 1305, respectively. ntpd performs most computations in 64-bit floating point arithmetic and uses 64-bit fixed point operations only when necessary to preserve the ultimate precision, about 232 picoseconds. While ordinary workstations and networks cannot achieve the ultimate precision as of 2015, future processors and networks may require it.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== NTPD Installation ==&lt;br /&gt;
To install '''NTPD package''' simply use the following commands:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 1. Update List of Available Packages ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg update&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Update Process:&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/Packages.gz.&lt;br /&gt;
 Updated source 'base'.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/firmware/Packages.gz.&lt;br /&gt;
 Updated source 'firmware'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Choose one of the available packages ===&lt;br /&gt;
'''metel-ntpd-server-internet'''&lt;br /&gt;
- NTP server, package contains configuration as  [[NTPD#2. With Connetion to Remote NTP Servers|&amp;quot;Synchronization to two internet NTP servers&amp;quot;]] (synchronization to internet NTP servers).&lt;br /&gt;
&lt;br /&gt;
'''metel-ntpd-standalone-server'''&lt;br /&gt;
- NTP server, package contains configuration as  [[NTPD#1. Standalone NTP server|&amp;quot;Standalone NTP server&amp;quot;]] (without synchronization to internet NTP servers).&lt;br /&gt;
&lt;br /&gt;
'''ntpd'''&lt;br /&gt;
- NTP server, package with  [[NTPD#3. Install NTPD Package|&amp;quot;Linux default configuration&amp;quot;]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. Install NTPD Packages ===&lt;br /&gt;
==== a) metel-ntpd-server-internet ====&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install metel-ntpd-server-internet&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Package Installing:&lt;br /&gt;
 Installing metel-ntpd-server-internet (0.0.1-12326) on root.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/metel-ntpd-server-internet_0.0.1-12326_all.ipk.&lt;br /&gt;
 Installing ntpd (4.2.8p9-12326) on root.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/ntpd_4.2.8p9-12326_all.ipk.&lt;br /&gt;
 Stopping ntpd: FAIL&lt;br /&gt;
 Configuring ntpd.&lt;br /&gt;
 Starting ntpd: OK&lt;br /&gt;
 Configuring metel-ntpd-server-internet.&lt;br /&gt;
 Restarting ntpd:&lt;br /&gt;
 Stopping ntpd: OK&lt;br /&gt;
 Starting ntpd: OK&lt;br /&gt;
After installation the NTPD daemon automatically starts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== b) metel-ntpd-standalone-server ====&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install metel-ntpd-standalone-server&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Package Installing:&lt;br /&gt;
 Installing metel-ntpd-standalone-server (0.0.1-12326) on root.&lt;br /&gt;
 Installing ntpd (4.2.8p9-12326) on root.&lt;br /&gt;
 Stopping ntpd: FAIL&lt;br /&gt;
 Configuring ntpd.&lt;br /&gt;
 Starting ntpd: OK&lt;br /&gt;
 Configuring metel-ntpd-standalone-server.&lt;br /&gt;
 Restarting ntpd:&lt;br /&gt;
 Stopping ntpd: OK&lt;br /&gt;
 Starting ntpd: OK&lt;br /&gt;
After installation the NTPD daemon automatically starts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== c) ntpd ====&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install ntpd&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Package Installing:&lt;br /&gt;
 Installing ntpd (4.2.8p9-9671.212083251) on root.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/ntpd_4.2.8p9-9671.212083251_all.ipk.&lt;br /&gt;
 Configuring ntpd.&lt;br /&gt;
&lt;br /&gt;
When the instalation is complete, start the NTP daemon by command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# /etc/init.d/S49ntp start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText= Every time the configuration file '''/etc/ntp.conf''' is changed, restart the service '''S49ntp''' by command '''/etc/init.d/S49ntp restart'''!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Examples ==&lt;br /&gt;
This section provides several examples of the '''/etc/ntp.conf''' configuration file.&lt;br /&gt;
&lt;br /&gt;
=== 1. Standalone NTP server ===&lt;br /&gt;
The following configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - No synchronization to internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command: &lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcar&lt;br /&gt;
  &lt;br /&gt;
 # create a local NTP server&lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. With Connetion to Remote NTP Servers ===&lt;br /&gt;
The example shows the optimal configuration for the Czech Republic. &lt;br /&gt;
&lt;br /&gt;
This configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - Synchronization to two internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File Content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcard&lt;br /&gt;
 &lt;br /&gt;
 server tik.cesnet.cz&lt;br /&gt;
 server tak.cesnet.cz&lt;br /&gt;
 &lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10 refid ILOG&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
 #end-of-file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Diagnostics ==&lt;br /&gt;
=== NTPQ ===&lt;br /&gt;
The '''ntpq''' utility program is used to query NTP servers which implement the recommended NTP mode 6 control message format about the current state and to request changes in that state.&lt;br /&gt;
&lt;br /&gt;
[http://doc.ntp.org/4.2.8p9/ntpq.html NTPQ Home Page]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre|text= root@iplog:~# watch ntpq -p -n&lt;br /&gt;
}}&lt;br /&gt;
NTPQ Parameters:&lt;br /&gt;
&lt;br /&gt;
: '''watch''' - Every 2s: ntpq -p -n&lt;br /&gt;
&lt;br /&gt;
: '''-p''' - Print current status&lt;br /&gt;
&lt;br /&gt;
: '''-n''' - Disable DNS resolving&lt;br /&gt;
&lt;br /&gt;
 Every 2s: ntpq -p -n                                        2019-08-01 10:00:12&lt;br /&gt;
 &lt;br /&gt;
      remote           refid      st t when poll reach   delay   offset  jitter&lt;br /&gt;
 ==============================================================================&lt;br /&gt;
  127.127.1.0     .ILOG.          10 l  41m   64    0    0.000    0.000   0.000&lt;br /&gt;
 +195.113.144.201 195.113.144.238  2 u   92  128  377   12.307    2.212   1.333&lt;br /&gt;
 *195.113.144.238 .GPS.            1 u   20  128  377   11.039    4.785   1.630&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This section is a copy from https://pthree.org/2013/11/05/real-life-ntp/.&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
&lt;br /&gt;
:    • '''remote''' – The remote server you wish to synchronize your clock with&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot; &amp;quot; Discarded as not valid. It is possible that you will be unable to communicate with the remote machine (it's not online), this time source is a &amp;quot;.LOCL.&amp;quot; refid time source, it's a high stratum server, or the remote server is using this computer as an NTP server.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;x&amp;quot; Discarded by the intersection algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;.&amp;quot; Discarded by table overflow (not used).&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;-&amp;quot; Discarded by the cluster algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;+&amp;quot; Included in the combined algorithm. This is a good candidate if the current server we are synchronizing with is discarded for any reason.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;#&amp;quot; Good remote server to be used as an alternative backup. This is only shown if you have more than 10 remote servers.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;*&amp;quot; The current system peer. The computer is using this remote server as its time source to synchronize the clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;o&amp;quot; Pulse per second (PPS) peer. This is generally used with GPS time sources, although any time source delivering a PPS will do. This tally code and the previous tally code &amp;quot;*&amp;quot; will not be displayed simultaneously.&lt;br /&gt;
&lt;br /&gt;
:    • '''refid''' – The upstream stratum to the remote server. For stratum 1 servers, this will be the stratum 0 source.&lt;br /&gt;
&lt;br /&gt;
:    • '''st''' – The stratum level, 0 through 16.&lt;br /&gt;
&lt;br /&gt;
:    • '''t''' –  The type of connection. &lt;br /&gt;
&lt;br /&gt;
:        ◦ l = local reference clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ u = unicast (most common)&lt;br /&gt;
&lt;br /&gt;
:        ◦ m = multicast&lt;br /&gt;
&lt;br /&gt;
:        ◦ b = broadcast&lt;br /&gt;
&lt;br /&gt;
:    • '''when''' – The last time when the server was queried for the time. Default is seconds, or &amp;quot;m&amp;quot; will be displayed for minutes, &amp;quot;h&amp;quot; for hours and &amp;quot;d&amp;quot; for days.&lt;br /&gt;
&lt;br /&gt;
:    • '''poll''' – How often the server is queried for the time, with a minimum of 8 seconds to a maximum of 36 hours. It's also displayed as a value from a power of two. Typically, it's between 64 seconds and 1024 seconds.&lt;br /&gt;
&lt;br /&gt;
:    • '''reach''' – This is an 8-bit left shift octal value that shows the success and failure rate of communicating with the remote server. Success means the bit is set, failure means the bit is not set. 377 is the highest value.&lt;br /&gt;
&lt;br /&gt;
:    • '''delay''' – This value is displayed in milliseconds, and shows the round trip time (RTT) of your computer communicating with the remote server.&lt;br /&gt;
&lt;br /&gt;
:    • '''offset''' –  This value is displayed in milliseconds, using root mean squares, and shows how far off your clock is from the reported time the server gave you. It can be positive or negative.&lt;br /&gt;
&lt;br /&gt;
:    • '''jitter''' – This number is an absolute value in milliseconds, showing the root mean squared deviation of your offsets.&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1028</id>
		<title>NTPD</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1028"/>
				<updated>2022-01-14T08:35:55Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= NTPD (Network Time Procokol Daemon) =&lt;br /&gt;
== Description ==&lt;br /&gt;
The '''NTPD''' program is an operating-system daemon that sets and maintains a computer system's time in synchronization with Internet-standard time servers. It is a complete implementation of the Network Time Protocol (NTP) version 4, but retains compatibility with versions 1, 2, and 3 as defined by RFC 1059, RFC 1119, and RFC 1305, respectively. ntpd performs most computations in 64-bit floating point arithmetic and uses 64-bit fixed point operations only when necessary to preserve the ultimate precision, about 232 picoseconds. While ordinary workstations and networks cannot achieve the ultimate precision as of 2015, future processors and networks may require it.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== NTPD Installation ==&lt;br /&gt;
To install '''NTPD package''' simply use the following commands:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 1. Update List of Available Packages ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg update&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Update Process:&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/Packages.gz.&lt;br /&gt;
 Updated source 'base'.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/firmware/Packages.gz.&lt;br /&gt;
 Updated source 'firmware'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Choose one of the available packages ===&lt;br /&gt;
'''metel-ntpd-server-internet''' &amp;lt;br&amp;gt;&lt;br /&gt;
NTP server, package contains configuration as  [[NTPD#2. With Connetion to Remote NTP Servers|&amp;quot;Synchronization to two internet NTP servers&amp;quot;]] (synchronization to internet NTP servers).&lt;br /&gt;
&lt;br /&gt;
'''metel-ntpd-standalone-server''' &amp;lt;br&amp;gt;&lt;br /&gt;
NTP server, package contains configuration as  [[NTPD#1. Standalone NTP server|&amp;quot;Standalone NTP server&amp;quot;]] (without synchronization to internet NTP servers).&lt;br /&gt;
&lt;br /&gt;
'''ntpd''' &amp;lt;br&amp;gt;&lt;br /&gt;
NTP server, package with  [[NTPD#3. Install NTPD Package|&amp;quot;Linux default configuration&amp;quot;]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. How to Install NTPD Packages ===&lt;br /&gt;
==== a) metel-ntpd-server-internet ====&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install metel-ntpd-server-internet&lt;br /&gt;
}}&lt;br /&gt;
After installation the NTPD daemon automatically starts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== b) metel-ntpd-standalone-server ====&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install metel-ntpd-standalone-server&lt;br /&gt;
}}&lt;br /&gt;
After installation the NTPD daemon automatically starts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== c) ntpd ====&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install ntpd&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example of Package Installing:&lt;br /&gt;
 Installing ntpd (4.2.8p9-9671.212083251) on root.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/ntpd_4.2.8p9-9671.212083251_all.ipk.&lt;br /&gt;
 Configuring ntpd.&lt;br /&gt;
&lt;br /&gt;
When the instalation is complete, start the NTP daemon by command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# /etc/init.d/S49ntp start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText= Every time the configuration file '''/etc/ntp.conf''' is changed, restart the service '''S49ntp''' by command '''/etc/init.d/S49ntp restart'''!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Examples ==&lt;br /&gt;
This section provides several examples of the '''/etc/ntp.conf''' configuration file.&lt;br /&gt;
&lt;br /&gt;
=== 1. Standalone NTP server ===&lt;br /&gt;
The following configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - No synchronization to internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command: &lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcar&lt;br /&gt;
  &lt;br /&gt;
 # create a local NTP server&lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. With Connetion to Remote NTP Servers ===&lt;br /&gt;
The example shows the optimal configuration for the Czech Republic. &lt;br /&gt;
&lt;br /&gt;
This configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - Synchronization to two internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File Content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcard&lt;br /&gt;
 &lt;br /&gt;
 server tik.cesnet.cz&lt;br /&gt;
 server tak.cesnet.cz&lt;br /&gt;
 &lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10 refid ILOG&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
 #end-of-file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Diagnostics ==&lt;br /&gt;
=== NTPQ ===&lt;br /&gt;
The '''ntpq''' utility program is used to query NTP servers which implement the recommended NTP mode 6 control message format about the current state and to request changes in that state.&lt;br /&gt;
&lt;br /&gt;
[http://doc.ntp.org/4.2.8p9/ntpq.html NTPQ Home Page]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre|text= root@iplog:~# watch ntpq -p -n&lt;br /&gt;
}}&lt;br /&gt;
NTPQ Parameters:&lt;br /&gt;
&lt;br /&gt;
: '''watch''' - Every 2s: ntpq -p -n&lt;br /&gt;
&lt;br /&gt;
: '''-p''' - Print current status&lt;br /&gt;
&lt;br /&gt;
: '''-n''' - Disable DNS resolving&lt;br /&gt;
&lt;br /&gt;
 Every 2s: ntpq -p -n                                        2019-08-01 10:00:12&lt;br /&gt;
 &lt;br /&gt;
      remote           refid      st t when poll reach   delay   offset  jitter&lt;br /&gt;
 ==============================================================================&lt;br /&gt;
  127.127.1.0     .ILOG.          10 l  41m   64    0    0.000    0.000   0.000&lt;br /&gt;
 +195.113.144.201 195.113.144.238  2 u   92  128  377   12.307    2.212   1.333&lt;br /&gt;
 *195.113.144.238 .GPS.            1 u   20  128  377   11.039    4.785   1.630&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This section is a copy from https://pthree.org/2013/11/05/real-life-ntp/.&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
&lt;br /&gt;
:    • '''remote''' – The remote server you wish to synchronize your clock with&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot; &amp;quot; Discarded as not valid. It is possible that you will be unable to communicate with the remote machine (it's not online), this time source is a &amp;quot;.LOCL.&amp;quot; refid time source, it's a high stratum server, or the remote server is using this computer as an NTP server.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;x&amp;quot; Discarded by the intersection algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;.&amp;quot; Discarded by table overflow (not used).&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;-&amp;quot; Discarded by the cluster algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;+&amp;quot; Included in the combined algorithm. This is a good candidate if the current server we are synchronizing with is discarded for any reason.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;#&amp;quot; Good remote server to be used as an alternative backup. This is only shown if you have more than 10 remote servers.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;*&amp;quot; The current system peer. The computer is using this remote server as its time source to synchronize the clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;o&amp;quot; Pulse per second (PPS) peer. This is generally used with GPS time sources, although any time source delivering a PPS will do. This tally code and the previous tally code &amp;quot;*&amp;quot; will not be displayed simultaneously.&lt;br /&gt;
&lt;br /&gt;
:    • '''refid''' – The upstream stratum to the remote server. For stratum 1 servers, this will be the stratum 0 source.&lt;br /&gt;
&lt;br /&gt;
:    • '''st''' – The stratum level, 0 through 16.&lt;br /&gt;
&lt;br /&gt;
:    • '''t''' –  The type of connection. &lt;br /&gt;
&lt;br /&gt;
:        ◦ l = local reference clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ u = unicast (most common)&lt;br /&gt;
&lt;br /&gt;
:        ◦ m = multicast&lt;br /&gt;
&lt;br /&gt;
:        ◦ b = broadcast&lt;br /&gt;
&lt;br /&gt;
:    • '''when''' – The last time when the server was queried for the time. Default is seconds, or &amp;quot;m&amp;quot; will be displayed for minutes, &amp;quot;h&amp;quot; for hours and &amp;quot;d&amp;quot; for days.&lt;br /&gt;
&lt;br /&gt;
:    • '''poll''' – How often the server is queried for the time, with a minimum of 8 seconds to a maximum of 36 hours. It's also displayed as a value from a power of two. Typically, it's between 64 seconds and 1024 seconds.&lt;br /&gt;
&lt;br /&gt;
:    • '''reach''' – This is an 8-bit left shift octal value that shows the success and failure rate of communicating with the remote server. Success means the bit is set, failure means the bit is not set. 377 is the highest value.&lt;br /&gt;
&lt;br /&gt;
:    • '''delay''' – This value is displayed in milliseconds, and shows the round trip time (RTT) of your computer communicating with the remote server.&lt;br /&gt;
&lt;br /&gt;
:    • '''offset''' –  This value is displayed in milliseconds, using root mean squares, and shows how far off your clock is from the reported time the server gave you. It can be positive or negative.&lt;br /&gt;
&lt;br /&gt;
:    • '''jitter''' – This number is an absolute value in milliseconds, showing the root mean squared deviation of your offsets.&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1027</id>
		<title>NTPD</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1027"/>
				<updated>2022-01-14T08:25:58Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= NTPD (Network Time Procokol Daemon) =&lt;br /&gt;
== Description ==&lt;br /&gt;
The '''NTPD''' program is an operating-system daemon that sets and maintains a computer system's time in synchronization with Internet-standard time servers. It is a complete implementation of the Network Time Protocol (NTP) version 4, but retains compatibility with versions 1, 2, and 3 as defined by RFC 1059, RFC 1119, and RFC 1305, respectively. ntpd performs most computations in 64-bit floating point arithmetic and uses 64-bit fixed point operations only when necessary to preserve the ultimate precision, about 232 picoseconds. While ordinary workstations and networks cannot achieve the ultimate precision as of 2015, future processors and networks may require it.&lt;br /&gt;
&lt;br /&gt;
== NTPD Installation ==&lt;br /&gt;
To install '''NTPD package''' simply use the following commands:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 1. Update List of Available Packages ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg update&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Update Process:&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/Packages.gz.&lt;br /&gt;
 Updated source 'base'.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/firmware/Packages.gz.&lt;br /&gt;
 Updated source 'firmware'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Choose one of the available packages ===&lt;br /&gt;
metel-ntpd-server-internet&lt;br /&gt;
NTP server, package contains configuration as  [[NTPD#2. With Connetion to Remote NTP Servers|&amp;quot;Synchronization to two internet NTP servers&amp;quot;]] (synchronization to internet NTP servers).&lt;br /&gt;
&lt;br /&gt;
metel-ntpd-standalone-server&lt;br /&gt;
NTP server, package contains configuration as  [[NTPD#1. Standalone NTP server|&amp;quot;Standalone NTP server&amp;quot;]] (without synchronization to internet NTP servers).&lt;br /&gt;
&lt;br /&gt;
ntpd&lt;br /&gt;
NTP server, package with  [[NTPD#3. Install NTPD Package|&amp;quot;Linux default configuration&amp;quot;]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. How to Install NTPD Packages ===&lt;br /&gt;
==== a) metel-ntpd-server-internet ====&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install metel-ntpd-server-internet&lt;br /&gt;
}}&lt;br /&gt;
After installation the NTPD daemon automatically starts.&lt;br /&gt;
&lt;br /&gt;
==== b) metel-ntpd-standalone-server ====&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install metel-ntpd-standalone-server&lt;br /&gt;
}}&lt;br /&gt;
After installation the NTPD daemon automatically starts.&lt;br /&gt;
&lt;br /&gt;
==== c) ntpd ====&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install ntpd&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Package Installing:&lt;br /&gt;
 Installing ntpd (4.2.8p9-9671.212083251) on root.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/ntpd_4.2.8p9-9671.212083251_all.ipk.&lt;br /&gt;
 Configuring ntpd.&lt;br /&gt;
&lt;br /&gt;
When the instalation is complete, start the NTP daemon by command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# /etc/init.d/S49ntp start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText= Every time the configuration file '''/etc/ntp.conf''' is changed, restart the service '''S49ntp''' by command '''/etc/init.d/S49ntp restart'''!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Examples ==&lt;br /&gt;
This section provides several examples of the '''/etc/ntp.conf''' configuration file.&lt;br /&gt;
&lt;br /&gt;
=== 1. Standalone NTP server ===&lt;br /&gt;
The following configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - No synchronization to internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command: &lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcar&lt;br /&gt;
  &lt;br /&gt;
 # create a local NTP server&lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. With Connetion to Remote NTP Servers ===&lt;br /&gt;
The example shows the optimal configuration for the Czech Republic. &lt;br /&gt;
&lt;br /&gt;
This configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - Synchronization to two internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File Content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcard&lt;br /&gt;
 &lt;br /&gt;
 server tik.cesnet.cz&lt;br /&gt;
 server tak.cesnet.cz&lt;br /&gt;
 &lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10 refid ILOG&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
 #end-of-file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Diagnostics ==&lt;br /&gt;
=== NTPQ ===&lt;br /&gt;
The '''ntpq''' utility program is used to query NTP servers which implement the recommended NTP mode 6 control message format about the current state and to request changes in that state.&lt;br /&gt;
&lt;br /&gt;
[http://doc.ntp.org/4.2.8p9/ntpq.html NTPQ Home Page]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre|text= root@iplog:~# watch ntpq -p -n&lt;br /&gt;
}}&lt;br /&gt;
NTPQ Parameters:&lt;br /&gt;
&lt;br /&gt;
: '''watch''' - Every 2s: ntpq -p -n&lt;br /&gt;
&lt;br /&gt;
: '''-p''' - Print current status&lt;br /&gt;
&lt;br /&gt;
: '''-n''' - Disable DNS resolving&lt;br /&gt;
&lt;br /&gt;
 Every 2s: ntpq -p -n                                        2019-08-01 10:00:12&lt;br /&gt;
 &lt;br /&gt;
      remote           refid      st t when poll reach   delay   offset  jitter&lt;br /&gt;
 ==============================================================================&lt;br /&gt;
  127.127.1.0     .ILOG.          10 l  41m   64    0    0.000    0.000   0.000&lt;br /&gt;
 +195.113.144.201 195.113.144.238  2 u   92  128  377   12.307    2.212   1.333&lt;br /&gt;
 *195.113.144.238 .GPS.            1 u   20  128  377   11.039    4.785   1.630&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This section is a copy from https://pthree.org/2013/11/05/real-life-ntp/.&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
&lt;br /&gt;
:    • '''remote''' – The remote server you wish to synchronize your clock with&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot; &amp;quot; Discarded as not valid. It is possible that you will be unable to communicate with the remote machine (it's not online), this time source is a &amp;quot;.LOCL.&amp;quot; refid time source, it's a high stratum server, or the remote server is using this computer as an NTP server.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;x&amp;quot; Discarded by the intersection algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;.&amp;quot; Discarded by table overflow (not used).&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;-&amp;quot; Discarded by the cluster algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;+&amp;quot; Included in the combined algorithm. This is a good candidate if the current server we are synchronizing with is discarded for any reason.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;#&amp;quot; Good remote server to be used as an alternative backup. This is only shown if you have more than 10 remote servers.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;*&amp;quot; The current system peer. The computer is using this remote server as its time source to synchronize the clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;o&amp;quot; Pulse per second (PPS) peer. This is generally used with GPS time sources, although any time source delivering a PPS will do. This tally code and the previous tally code &amp;quot;*&amp;quot; will not be displayed simultaneously.&lt;br /&gt;
&lt;br /&gt;
:    • '''refid''' – The upstream stratum to the remote server. For stratum 1 servers, this will be the stratum 0 source.&lt;br /&gt;
&lt;br /&gt;
:    • '''st''' – The stratum level, 0 through 16.&lt;br /&gt;
&lt;br /&gt;
:    • '''t''' –  The type of connection. &lt;br /&gt;
&lt;br /&gt;
:        ◦ l = local reference clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ u = unicast (most common)&lt;br /&gt;
&lt;br /&gt;
:        ◦ m = multicast&lt;br /&gt;
&lt;br /&gt;
:        ◦ b = broadcast&lt;br /&gt;
&lt;br /&gt;
:    • '''when''' – The last time when the server was queried for the time. Default is seconds, or &amp;quot;m&amp;quot; will be displayed for minutes, &amp;quot;h&amp;quot; for hours and &amp;quot;d&amp;quot; for days.&lt;br /&gt;
&lt;br /&gt;
:    • '''poll''' – How often the server is queried for the time, with a minimum of 8 seconds to a maximum of 36 hours. It's also displayed as a value from a power of two. Typically, it's between 64 seconds and 1024 seconds.&lt;br /&gt;
&lt;br /&gt;
:    • '''reach''' – This is an 8-bit left shift octal value that shows the success and failure rate of communicating with the remote server. Success means the bit is set, failure means the bit is not set. 377 is the highest value.&lt;br /&gt;
&lt;br /&gt;
:    • '''delay''' – This value is displayed in milliseconds, and shows the round trip time (RTT) of your computer communicating with the remote server.&lt;br /&gt;
&lt;br /&gt;
:    • '''offset''' –  This value is displayed in milliseconds, using root mean squares, and shows how far off your clock is from the reported time the server gave you. It can be positive or negative.&lt;br /&gt;
&lt;br /&gt;
:    • '''jitter''' – This number is an absolute value in milliseconds, showing the root mean squared deviation of your offsets.&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1026</id>
		<title>NTPD</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1026"/>
				<updated>2022-01-14T08:09:29Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= NTPD (Network Time Procokol Daemon) =&lt;br /&gt;
== Description ==&lt;br /&gt;
The '''NTPD''' program is an operating-system daemon that sets and maintains a computer system's time in synchronization with Internet-standard time servers. It is a complete implementation of the Network Time Protocol (NTP) version 4, but retains compatibility with versions 1, 2, and 3 as defined by RFC 1059, RFC 1119, and RFC 1305, respectively. ntpd performs most computations in 64-bit floating point arithmetic and uses 64-bit fixed point operations only when necessary to preserve the ultimate precision, about 232 picoseconds. While ordinary workstations and networks cannot achieve the ultimate precision as of 2015, future processors and networks may require it.&lt;br /&gt;
&lt;br /&gt;
== NTPD Installation ==&lt;br /&gt;
To install '''NTPD package''' simply use the following commands:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 1. Update List of Available Packages ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg update&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Update Process:&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/Packages.gz.&lt;br /&gt;
 Updated source 'base'.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/firmware/Packages.gz.&lt;br /&gt;
 Updated source 'firmware'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Choose one of the available packages ===&lt;br /&gt;
==== ntpd ====&lt;br /&gt;
NTP server, package with  [[NTPD#3. Install NTPD Package|&amp;quot;Linux default configuration&amp;quot;]].&lt;br /&gt;
&lt;br /&gt;
==== metel-ntpd-server-internet ====&lt;br /&gt;
NTP server, package contains configuration as  [[NTPD#2. With Connetion to Remote NTP Servers|&amp;quot;Synchronization to two internet NTP servers&amp;quot;]] (synchronization to internet NTP servers).&lt;br /&gt;
&lt;br /&gt;
==== metel-ntpd-standalone-server ====&lt;br /&gt;
NTP server, package contains configuration as  [[NTPD#1. Standalone NTP server|&amp;quot;Standalone NTP server&amp;quot;]] (without synchronization to internet NTP servers).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. Install NTPD Package ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install ntpd&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Package Installing:&lt;br /&gt;
 Installing ntpd (4.2.8p9-9671.212083251) on root.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/ntpd_4.2.8p9-9671.212083251_all.ipk.&lt;br /&gt;
 Configuring ntpd.&lt;br /&gt;
&lt;br /&gt;
When the instalation is complete, start the NTP daemon by command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# /etc/init.d/S49ntp start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText= Every time the configuration file '''/etc/ntp.conf''' is changed, restart the service '''S49ntp''' by command '''/etc/init.d/S49ntp restart'''!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Examples ==&lt;br /&gt;
This section provides several examples of the '''/etc/ntp.conf''' configuration file.&lt;br /&gt;
&lt;br /&gt;
=== 1. Standalone NTP server ===&lt;br /&gt;
The following configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - No synchronization to internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command: &lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcar&lt;br /&gt;
  &lt;br /&gt;
 # create a local NTP server&lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. With Connetion to Remote NTP Servers ===&lt;br /&gt;
The example shows the optimal configuration for the Czech Republic. &lt;br /&gt;
&lt;br /&gt;
This configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - Synchronization to two internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File Content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcard&lt;br /&gt;
 &lt;br /&gt;
 server tik.cesnet.cz&lt;br /&gt;
 server tak.cesnet.cz&lt;br /&gt;
 &lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10 refid ILOG&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
 #end-of-file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Diagnostics ==&lt;br /&gt;
=== NTPQ ===&lt;br /&gt;
The '''ntpq''' utility program is used to query NTP servers which implement the recommended NTP mode 6 control message format about the current state and to request changes in that state.&lt;br /&gt;
&lt;br /&gt;
[http://doc.ntp.org/4.2.8p9/ntpq.html NTPQ Home Page]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre|text= root@iplog:~# watch ntpq -p -n&lt;br /&gt;
}}&lt;br /&gt;
NTPQ Parameters:&lt;br /&gt;
&lt;br /&gt;
: '''watch''' - Every 2s: ntpq -p -n&lt;br /&gt;
&lt;br /&gt;
: '''-p''' - Print current status&lt;br /&gt;
&lt;br /&gt;
: '''-n''' - Disable DNS resolving&lt;br /&gt;
&lt;br /&gt;
 Every 2s: ntpq -p -n                                        2019-08-01 10:00:12&lt;br /&gt;
 &lt;br /&gt;
      remote           refid      st t when poll reach   delay   offset  jitter&lt;br /&gt;
 ==============================================================================&lt;br /&gt;
  127.127.1.0     .ILOG.          10 l  41m   64    0    0.000    0.000   0.000&lt;br /&gt;
 +195.113.144.201 195.113.144.238  2 u   92  128  377   12.307    2.212   1.333&lt;br /&gt;
 *195.113.144.238 .GPS.            1 u   20  128  377   11.039    4.785   1.630&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This section is a copy from https://pthree.org/2013/11/05/real-life-ntp/.&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
&lt;br /&gt;
:    • '''remote''' – The remote server you wish to synchronize your clock with&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot; &amp;quot; Discarded as not valid. It is possible that you will be unable to communicate with the remote machine (it's not online), this time source is a &amp;quot;.LOCL.&amp;quot; refid time source, it's a high stratum server, or the remote server is using this computer as an NTP server.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;x&amp;quot; Discarded by the intersection algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;.&amp;quot; Discarded by table overflow (not used).&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;-&amp;quot; Discarded by the cluster algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;+&amp;quot; Included in the combined algorithm. This is a good candidate if the current server we are synchronizing with is discarded for any reason.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;#&amp;quot; Good remote server to be used as an alternative backup. This is only shown if you have more than 10 remote servers.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;*&amp;quot; The current system peer. The computer is using this remote server as its time source to synchronize the clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;o&amp;quot; Pulse per second (PPS) peer. This is generally used with GPS time sources, although any time source delivering a PPS will do. This tally code and the previous tally code &amp;quot;*&amp;quot; will not be displayed simultaneously.&lt;br /&gt;
&lt;br /&gt;
:    • '''refid''' – The upstream stratum to the remote server. For stratum 1 servers, this will be the stratum 0 source.&lt;br /&gt;
&lt;br /&gt;
:    • '''st''' – The stratum level, 0 through 16.&lt;br /&gt;
&lt;br /&gt;
:    • '''t''' –  The type of connection. &lt;br /&gt;
&lt;br /&gt;
:        ◦ l = local reference clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ u = unicast (most common)&lt;br /&gt;
&lt;br /&gt;
:        ◦ m = multicast&lt;br /&gt;
&lt;br /&gt;
:        ◦ b = broadcast&lt;br /&gt;
&lt;br /&gt;
:    • '''when''' – The last time when the server was queried for the time. Default is seconds, or &amp;quot;m&amp;quot; will be displayed for minutes, &amp;quot;h&amp;quot; for hours and &amp;quot;d&amp;quot; for days.&lt;br /&gt;
&lt;br /&gt;
:    • '''poll''' – How often the server is queried for the time, with a minimum of 8 seconds to a maximum of 36 hours. It's also displayed as a value from a power of two. Typically, it's between 64 seconds and 1024 seconds.&lt;br /&gt;
&lt;br /&gt;
:    • '''reach''' – This is an 8-bit left shift octal value that shows the success and failure rate of communicating with the remote server. Success means the bit is set, failure means the bit is not set. 377 is the highest value.&lt;br /&gt;
&lt;br /&gt;
:    • '''delay''' – This value is displayed in milliseconds, and shows the round trip time (RTT) of your computer communicating with the remote server.&lt;br /&gt;
&lt;br /&gt;
:    • '''offset''' –  This value is displayed in milliseconds, using root mean squares, and shows how far off your clock is from the reported time the server gave you. It can be positive or negative.&lt;br /&gt;
&lt;br /&gt;
:    • '''jitter''' – This number is an absolute value in milliseconds, showing the root mean squared deviation of your offsets.&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1025</id>
		<title>NTPD</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1025"/>
				<updated>2022-01-14T08:08:54Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= NTPD (Network Time Procokol Daemon) =&lt;br /&gt;
== Description ==&lt;br /&gt;
The '''NTPD''' program is an operating-system daemon that sets and maintains a computer system's time in synchronization with Internet-standard time servers. It is a complete implementation of the Network Time Protocol (NTP) version 4, but retains compatibility with versions 1, 2, and 3 as defined by RFC 1059, RFC 1119, and RFC 1305, respectively. ntpd performs most computations in 64-bit floating point arithmetic and uses 64-bit fixed point operations only when necessary to preserve the ultimate precision, about 232 picoseconds. While ordinary workstations and networks cannot achieve the ultimate precision as of 2015, future processors and networks may require it.&lt;br /&gt;
&lt;br /&gt;
== NTPD Installation ==&lt;br /&gt;
To install '''NTPD package''' simply use the following commands:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 1. Update List of Available Packages ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg update&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Update Process:&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/Packages.gz.&lt;br /&gt;
 Updated source 'base'.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/firmware/Packages.gz.&lt;br /&gt;
 Updated source 'firmware'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Choose one of the available packages ===&lt;br /&gt;
==== ntpd ====&lt;br /&gt;
NTPD server, package with  [[NTPD#3. Install NTPD Package|&amp;quot;Linux default configuration&amp;quot;]].&lt;br /&gt;
&lt;br /&gt;
==== metel-ntpd-server-internet ====&lt;br /&gt;
NTPD server, package contains configuration as  [[NTPD#2. With Connetion to Remote NTP Servers|&amp;quot;Synchronization to two internet NTP servers&amp;quot;]] (synchronization to internet NTP servers).&lt;br /&gt;
&lt;br /&gt;
==== metel-ntpd-standalone-server ====&lt;br /&gt;
NTPD server, package contains configuration as  [[NTPD#1. Standalone NTP server|&amp;quot;Standalone NTP server&amp;quot;]] (without synchronization to internet NTP servers).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. Install NTPD Package ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install ntpd&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Package Installing:&lt;br /&gt;
 Installing ntpd (4.2.8p9-9671.212083251) on root.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/ntpd_4.2.8p9-9671.212083251_all.ipk.&lt;br /&gt;
 Configuring ntpd.&lt;br /&gt;
&lt;br /&gt;
When the instalation is complete, start the NTP daemon by command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# /etc/init.d/S49ntp start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText= Every time the configuration file '''/etc/ntp.conf''' is changed, restart the service '''S49ntp''' by command '''/etc/init.d/S49ntp restart'''!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Examples ==&lt;br /&gt;
This section provides several examples of the '''/etc/ntp.conf''' configuration file.&lt;br /&gt;
&lt;br /&gt;
=== 1. Standalone NTP server ===&lt;br /&gt;
The following configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - No synchronization to internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command: &lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcar&lt;br /&gt;
  &lt;br /&gt;
 # create a local NTP server&lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. With Connetion to Remote NTP Servers ===&lt;br /&gt;
The example shows the optimal configuration for the Czech Republic. &lt;br /&gt;
&lt;br /&gt;
This configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - Synchronization to two internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File Content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcard&lt;br /&gt;
 &lt;br /&gt;
 server tik.cesnet.cz&lt;br /&gt;
 server tak.cesnet.cz&lt;br /&gt;
 &lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10 refid ILOG&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
 #end-of-file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Diagnostics ==&lt;br /&gt;
=== NTPQ ===&lt;br /&gt;
The '''ntpq''' utility program is used to query NTP servers which implement the recommended NTP mode 6 control message format about the current state and to request changes in that state.&lt;br /&gt;
&lt;br /&gt;
[http://doc.ntp.org/4.2.8p9/ntpq.html NTPQ Home Page]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre|text= root@iplog:~# watch ntpq -p -n&lt;br /&gt;
}}&lt;br /&gt;
NTPQ Parameters:&lt;br /&gt;
&lt;br /&gt;
: '''watch''' - Every 2s: ntpq -p -n&lt;br /&gt;
&lt;br /&gt;
: '''-p''' - Print current status&lt;br /&gt;
&lt;br /&gt;
: '''-n''' - Disable DNS resolving&lt;br /&gt;
&lt;br /&gt;
 Every 2s: ntpq -p -n                                        2019-08-01 10:00:12&lt;br /&gt;
 &lt;br /&gt;
      remote           refid      st t when poll reach   delay   offset  jitter&lt;br /&gt;
 ==============================================================================&lt;br /&gt;
  127.127.1.0     .ILOG.          10 l  41m   64    0    0.000    0.000   0.000&lt;br /&gt;
 +195.113.144.201 195.113.144.238  2 u   92  128  377   12.307    2.212   1.333&lt;br /&gt;
 *195.113.144.238 .GPS.            1 u   20  128  377   11.039    4.785   1.630&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This section is a copy from https://pthree.org/2013/11/05/real-life-ntp/.&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
&lt;br /&gt;
:    • '''remote''' – The remote server you wish to synchronize your clock with&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot; &amp;quot; Discarded as not valid. It is possible that you will be unable to communicate with the remote machine (it's not online), this time source is a &amp;quot;.LOCL.&amp;quot; refid time source, it's a high stratum server, or the remote server is using this computer as an NTP server.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;x&amp;quot; Discarded by the intersection algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;.&amp;quot; Discarded by table overflow (not used).&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;-&amp;quot; Discarded by the cluster algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;+&amp;quot; Included in the combined algorithm. This is a good candidate if the current server we are synchronizing with is discarded for any reason.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;#&amp;quot; Good remote server to be used as an alternative backup. This is only shown if you have more than 10 remote servers.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;*&amp;quot; The current system peer. The computer is using this remote server as its time source to synchronize the clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;o&amp;quot; Pulse per second (PPS) peer. This is generally used with GPS time sources, although any time source delivering a PPS will do. This tally code and the previous tally code &amp;quot;*&amp;quot; will not be displayed simultaneously.&lt;br /&gt;
&lt;br /&gt;
:    • '''refid''' – The upstream stratum to the remote server. For stratum 1 servers, this will be the stratum 0 source.&lt;br /&gt;
&lt;br /&gt;
:    • '''st''' – The stratum level, 0 through 16.&lt;br /&gt;
&lt;br /&gt;
:    • '''t''' –  The type of connection. &lt;br /&gt;
&lt;br /&gt;
:        ◦ l = local reference clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ u = unicast (most common)&lt;br /&gt;
&lt;br /&gt;
:        ◦ m = multicast&lt;br /&gt;
&lt;br /&gt;
:        ◦ b = broadcast&lt;br /&gt;
&lt;br /&gt;
:    • '''when''' – The last time when the server was queried for the time. Default is seconds, or &amp;quot;m&amp;quot; will be displayed for minutes, &amp;quot;h&amp;quot; for hours and &amp;quot;d&amp;quot; for days.&lt;br /&gt;
&lt;br /&gt;
:    • '''poll''' – How often the server is queried for the time, with a minimum of 8 seconds to a maximum of 36 hours. It's also displayed as a value from a power of two. Typically, it's between 64 seconds and 1024 seconds.&lt;br /&gt;
&lt;br /&gt;
:    • '''reach''' – This is an 8-bit left shift octal value that shows the success and failure rate of communicating with the remote server. Success means the bit is set, failure means the bit is not set. 377 is the highest value.&lt;br /&gt;
&lt;br /&gt;
:    • '''delay''' – This value is displayed in milliseconds, and shows the round trip time (RTT) of your computer communicating with the remote server.&lt;br /&gt;
&lt;br /&gt;
:    • '''offset''' –  This value is displayed in milliseconds, using root mean squares, and shows how far off your clock is from the reported time the server gave you. It can be positive or negative.&lt;br /&gt;
&lt;br /&gt;
:    • '''jitter''' – This number is an absolute value in milliseconds, showing the root mean squared deviation of your offsets.&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1024</id>
		<title>NTPD</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1024"/>
				<updated>2022-01-14T08:08:15Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= NTPD (Network Time Procokol Daemon) =&lt;br /&gt;
== Description ==&lt;br /&gt;
The '''NTPD''' program is an operating-system daemon that sets and maintains a computer system's time in synchronization with Internet-standard time servers. It is a complete implementation of the Network Time Protocol (NTP) version 4, but retains compatibility with versions 1, 2, and 3 as defined by RFC 1059, RFC 1119, and RFC 1305, respectively. ntpd performs most computations in 64-bit floating point arithmetic and uses 64-bit fixed point operations only when necessary to preserve the ultimate precision, about 232 picoseconds. While ordinary workstations and networks cannot achieve the ultimate precision as of 2015, future processors and networks may require it.&lt;br /&gt;
&lt;br /&gt;
== NTPD Installation ==&lt;br /&gt;
To install '''NTPD package''' simply use the following commands:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 1. Update List of Available Packages ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg update&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Update Process:&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/Packages.gz.&lt;br /&gt;
 Updated source 'base'.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/firmware/Packages.gz.&lt;br /&gt;
 Updated source 'firmware'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Choose one of the available packages ===&lt;br /&gt;
==== ntpd ====&lt;br /&gt;
NTPD server package with  [[NTPD#3. Install NTPD Package|&amp;quot;Linux default configuration&amp;quot;]].&lt;br /&gt;
&lt;br /&gt;
==== metel-ntpd-server-internet ====&lt;br /&gt;
NTPD server package contains configuration as  [[NTPD#2. With Connetion to Remote NTP Servers|&amp;quot;Synchronization to two internet NTP servers&amp;quot;]] (synchronization to internet NTP servers).&lt;br /&gt;
==== metel-ntpd-standalone-server ====&lt;br /&gt;
NTPD server package contains configuration as  [[NTPD#1. Standalone NTP server|&amp;quot;Standalone NTP server&amp;quot;]] (without synchronization to internet NTP servers).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. Install NTPD Package ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install ntpd&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Package Installing:&lt;br /&gt;
 Installing ntpd (4.2.8p9-9671.212083251) on root.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/ntpd_4.2.8p9-9671.212083251_all.ipk.&lt;br /&gt;
 Configuring ntpd.&lt;br /&gt;
&lt;br /&gt;
When the instalation is complete, start the NTP daemon by command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# /etc/init.d/S49ntp start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText= Every time the configuration file '''/etc/ntp.conf''' is changed, restart the service '''S49ntp''' by command '''/etc/init.d/S49ntp restart'''!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Examples ==&lt;br /&gt;
This section provides several examples of the '''/etc/ntp.conf''' configuration file.&lt;br /&gt;
&lt;br /&gt;
=== 1. Standalone NTP server ===&lt;br /&gt;
The following configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - No synchronization to internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command: &lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcar&lt;br /&gt;
  &lt;br /&gt;
 # create a local NTP server&lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. With Connetion to Remote NTP Servers ===&lt;br /&gt;
The example shows the optimal configuration for the Czech Republic. &lt;br /&gt;
&lt;br /&gt;
This configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - Synchronization to two internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File Content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcard&lt;br /&gt;
 &lt;br /&gt;
 server tik.cesnet.cz&lt;br /&gt;
 server tak.cesnet.cz&lt;br /&gt;
 &lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10 refid ILOG&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
 #end-of-file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Diagnostics ==&lt;br /&gt;
=== NTPQ ===&lt;br /&gt;
The '''ntpq''' utility program is used to query NTP servers which implement the recommended NTP mode 6 control message format about the current state and to request changes in that state.&lt;br /&gt;
&lt;br /&gt;
[http://doc.ntp.org/4.2.8p9/ntpq.html NTPQ Home Page]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre|text= root@iplog:~# watch ntpq -p -n&lt;br /&gt;
}}&lt;br /&gt;
NTPQ Parameters:&lt;br /&gt;
&lt;br /&gt;
: '''watch''' - Every 2s: ntpq -p -n&lt;br /&gt;
&lt;br /&gt;
: '''-p''' - Print current status&lt;br /&gt;
&lt;br /&gt;
: '''-n''' - Disable DNS resolving&lt;br /&gt;
&lt;br /&gt;
 Every 2s: ntpq -p -n                                        2019-08-01 10:00:12&lt;br /&gt;
 &lt;br /&gt;
      remote           refid      st t when poll reach   delay   offset  jitter&lt;br /&gt;
 ==============================================================================&lt;br /&gt;
  127.127.1.0     .ILOG.          10 l  41m   64    0    0.000    0.000   0.000&lt;br /&gt;
 +195.113.144.201 195.113.144.238  2 u   92  128  377   12.307    2.212   1.333&lt;br /&gt;
 *195.113.144.238 .GPS.            1 u   20  128  377   11.039    4.785   1.630&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This section is a copy from https://pthree.org/2013/11/05/real-life-ntp/.&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
&lt;br /&gt;
:    • '''remote''' – The remote server you wish to synchronize your clock with&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot; &amp;quot; Discarded as not valid. It is possible that you will be unable to communicate with the remote machine (it's not online), this time source is a &amp;quot;.LOCL.&amp;quot; refid time source, it's a high stratum server, or the remote server is using this computer as an NTP server.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;x&amp;quot; Discarded by the intersection algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;.&amp;quot; Discarded by table overflow (not used).&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;-&amp;quot; Discarded by the cluster algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;+&amp;quot; Included in the combined algorithm. This is a good candidate if the current server we are synchronizing with is discarded for any reason.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;#&amp;quot; Good remote server to be used as an alternative backup. This is only shown if you have more than 10 remote servers.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;*&amp;quot; The current system peer. The computer is using this remote server as its time source to synchronize the clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;o&amp;quot; Pulse per second (PPS) peer. This is generally used with GPS time sources, although any time source delivering a PPS will do. This tally code and the previous tally code &amp;quot;*&amp;quot; will not be displayed simultaneously.&lt;br /&gt;
&lt;br /&gt;
:    • '''refid''' – The upstream stratum to the remote server. For stratum 1 servers, this will be the stratum 0 source.&lt;br /&gt;
&lt;br /&gt;
:    • '''st''' – The stratum level, 0 through 16.&lt;br /&gt;
&lt;br /&gt;
:    • '''t''' –  The type of connection. &lt;br /&gt;
&lt;br /&gt;
:        ◦ l = local reference clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ u = unicast (most common)&lt;br /&gt;
&lt;br /&gt;
:        ◦ m = multicast&lt;br /&gt;
&lt;br /&gt;
:        ◦ b = broadcast&lt;br /&gt;
&lt;br /&gt;
:    • '''when''' – The last time when the server was queried for the time. Default is seconds, or &amp;quot;m&amp;quot; will be displayed for minutes, &amp;quot;h&amp;quot; for hours and &amp;quot;d&amp;quot; for days.&lt;br /&gt;
&lt;br /&gt;
:    • '''poll''' – How often the server is queried for the time, with a minimum of 8 seconds to a maximum of 36 hours. It's also displayed as a value from a power of two. Typically, it's between 64 seconds and 1024 seconds.&lt;br /&gt;
&lt;br /&gt;
:    • '''reach''' – This is an 8-bit left shift octal value that shows the success and failure rate of communicating with the remote server. Success means the bit is set, failure means the bit is not set. 377 is the highest value.&lt;br /&gt;
&lt;br /&gt;
:    • '''delay''' – This value is displayed in milliseconds, and shows the round trip time (RTT) of your computer communicating with the remote server.&lt;br /&gt;
&lt;br /&gt;
:    • '''offset''' –  This value is displayed in milliseconds, using root mean squares, and shows how far off your clock is from the reported time the server gave you. It can be positive or negative.&lt;br /&gt;
&lt;br /&gt;
:    • '''jitter''' – This number is an absolute value in milliseconds, showing the root mean squared deviation of your offsets.&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1023</id>
		<title>NTPD</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1023"/>
				<updated>2022-01-14T08:07:58Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= NTPD (Network Time Procokol Daemon) =&lt;br /&gt;
== Description ==&lt;br /&gt;
The '''NTPD''' program is an operating-system daemon that sets and maintains a computer system's time in synchronization with Internet-standard time servers. It is a complete implementation of the Network Time Protocol (NTP) version 4, but retains compatibility with versions 1, 2, and 3 as defined by RFC 1059, RFC 1119, and RFC 1305, respectively. ntpd performs most computations in 64-bit floating point arithmetic and uses 64-bit fixed point operations only when necessary to preserve the ultimate precision, about 232 picoseconds. While ordinary workstations and networks cannot achieve the ultimate precision as of 2015, future processors and networks may require it.&lt;br /&gt;
&lt;br /&gt;
== NTPD Installation ==&lt;br /&gt;
To install '''NTPD package''' simply use the following commands:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 1. Update List of Available Packages ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg update&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Update Process:&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/Packages.gz.&lt;br /&gt;
 Updated source 'base'.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/firmware/Packages.gz.&lt;br /&gt;
 Updated source 'firmware'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Choose one of the available packages ===&lt;br /&gt;
==== ntpd ====&lt;br /&gt;
NTPD server package with  [[NTPD#3. Install NTPD Package|&amp;quot;Linux default configuration&amp;quot;]].&lt;br /&gt;
&lt;br /&gt;
==== metel-ntpd-server-internet ====&lt;br /&gt;
NTPD server package contains configuration as  [[NTPD#2. With Connetion to Remote NTP Servers|&amp;quot;Synchronization to two internet NTP servers&amp;quot;]] (synchronization to internet NTP servers).&lt;br /&gt;
==== metel-ntpd-standalone-server ====&lt;br /&gt;
NTPD server package contains configuration as  [[NTPD#1. Standalone NTP server|&amp;quot;Standalone NTP server&amp;quot;]](without synchronization to internet NTP servers).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. Install NTPD Package ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install ntpd&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Package Installing:&lt;br /&gt;
 Installing ntpd (4.2.8p9-9671.212083251) on root.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/ntpd_4.2.8p9-9671.212083251_all.ipk.&lt;br /&gt;
 Configuring ntpd.&lt;br /&gt;
&lt;br /&gt;
When the instalation is complete, start the NTP daemon by command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# /etc/init.d/S49ntp start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText= Every time the configuration file '''/etc/ntp.conf''' is changed, restart the service '''S49ntp''' by command '''/etc/init.d/S49ntp restart'''!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Examples ==&lt;br /&gt;
This section provides several examples of the '''/etc/ntp.conf''' configuration file.&lt;br /&gt;
&lt;br /&gt;
=== 1. Standalone NTP server ===&lt;br /&gt;
The following configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - No synchronization to internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command: &lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcar&lt;br /&gt;
  &lt;br /&gt;
 # create a local NTP server&lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. With Connetion to Remote NTP Servers ===&lt;br /&gt;
The example shows the optimal configuration for the Czech Republic. &lt;br /&gt;
&lt;br /&gt;
This configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - Synchronization to two internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File Content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcard&lt;br /&gt;
 &lt;br /&gt;
 server tik.cesnet.cz&lt;br /&gt;
 server tak.cesnet.cz&lt;br /&gt;
 &lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10 refid ILOG&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
 #end-of-file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Diagnostics ==&lt;br /&gt;
=== NTPQ ===&lt;br /&gt;
The '''ntpq''' utility program is used to query NTP servers which implement the recommended NTP mode 6 control message format about the current state and to request changes in that state.&lt;br /&gt;
&lt;br /&gt;
[http://doc.ntp.org/4.2.8p9/ntpq.html NTPQ Home Page]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre|text= root@iplog:~# watch ntpq -p -n&lt;br /&gt;
}}&lt;br /&gt;
NTPQ Parameters:&lt;br /&gt;
&lt;br /&gt;
: '''watch''' - Every 2s: ntpq -p -n&lt;br /&gt;
&lt;br /&gt;
: '''-p''' - Print current status&lt;br /&gt;
&lt;br /&gt;
: '''-n''' - Disable DNS resolving&lt;br /&gt;
&lt;br /&gt;
 Every 2s: ntpq -p -n                                        2019-08-01 10:00:12&lt;br /&gt;
 &lt;br /&gt;
      remote           refid      st t when poll reach   delay   offset  jitter&lt;br /&gt;
 ==============================================================================&lt;br /&gt;
  127.127.1.0     .ILOG.          10 l  41m   64    0    0.000    0.000   0.000&lt;br /&gt;
 +195.113.144.201 195.113.144.238  2 u   92  128  377   12.307    2.212   1.333&lt;br /&gt;
 *195.113.144.238 .GPS.            1 u   20  128  377   11.039    4.785   1.630&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This section is a copy from https://pthree.org/2013/11/05/real-life-ntp/.&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
&lt;br /&gt;
:    • '''remote''' – The remote server you wish to synchronize your clock with&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot; &amp;quot; Discarded as not valid. It is possible that you will be unable to communicate with the remote machine (it's not online), this time source is a &amp;quot;.LOCL.&amp;quot; refid time source, it's a high stratum server, or the remote server is using this computer as an NTP server.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;x&amp;quot; Discarded by the intersection algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;.&amp;quot; Discarded by table overflow (not used).&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;-&amp;quot; Discarded by the cluster algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;+&amp;quot; Included in the combined algorithm. This is a good candidate if the current server we are synchronizing with is discarded for any reason.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;#&amp;quot; Good remote server to be used as an alternative backup. This is only shown if you have more than 10 remote servers.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;*&amp;quot; The current system peer. The computer is using this remote server as its time source to synchronize the clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;o&amp;quot; Pulse per second (PPS) peer. This is generally used with GPS time sources, although any time source delivering a PPS will do. This tally code and the previous tally code &amp;quot;*&amp;quot; will not be displayed simultaneously.&lt;br /&gt;
&lt;br /&gt;
:    • '''refid''' – The upstream stratum to the remote server. For stratum 1 servers, this will be the stratum 0 source.&lt;br /&gt;
&lt;br /&gt;
:    • '''st''' – The stratum level, 0 through 16.&lt;br /&gt;
&lt;br /&gt;
:    • '''t''' –  The type of connection. &lt;br /&gt;
&lt;br /&gt;
:        ◦ l = local reference clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ u = unicast (most common)&lt;br /&gt;
&lt;br /&gt;
:        ◦ m = multicast&lt;br /&gt;
&lt;br /&gt;
:        ◦ b = broadcast&lt;br /&gt;
&lt;br /&gt;
:    • '''when''' – The last time when the server was queried for the time. Default is seconds, or &amp;quot;m&amp;quot; will be displayed for minutes, &amp;quot;h&amp;quot; for hours and &amp;quot;d&amp;quot; for days.&lt;br /&gt;
&lt;br /&gt;
:    • '''poll''' – How often the server is queried for the time, with a minimum of 8 seconds to a maximum of 36 hours. It's also displayed as a value from a power of two. Typically, it's between 64 seconds and 1024 seconds.&lt;br /&gt;
&lt;br /&gt;
:    • '''reach''' – This is an 8-bit left shift octal value that shows the success and failure rate of communicating with the remote server. Success means the bit is set, failure means the bit is not set. 377 is the highest value.&lt;br /&gt;
&lt;br /&gt;
:    • '''delay''' – This value is displayed in milliseconds, and shows the round trip time (RTT) of your computer communicating with the remote server.&lt;br /&gt;
&lt;br /&gt;
:    • '''offset''' –  This value is displayed in milliseconds, using root mean squares, and shows how far off your clock is from the reported time the server gave you. It can be positive or negative.&lt;br /&gt;
&lt;br /&gt;
:    • '''jitter''' – This number is an absolute value in milliseconds, showing the root mean squared deviation of your offsets.&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1022</id>
		<title>NTPD</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1022"/>
				<updated>2022-01-14T08:04:30Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= NTPD (Network Time Procokol Daemon) =&lt;br /&gt;
== Description ==&lt;br /&gt;
The '''NTPD''' program is an operating-system daemon that sets and maintains a computer system's time in synchronization with Internet-standard time servers. It is a complete implementation of the Network Time Protocol (NTP) version 4, but retains compatibility with versions 1, 2, and 3 as defined by RFC 1059, RFC 1119, and RFC 1305, respectively. ntpd performs most computations in 64-bit floating point arithmetic and uses 64-bit fixed point operations only when necessary to preserve the ultimate precision, about 232 picoseconds. While ordinary workstations and networks cannot achieve the ultimate precision as of 2015, future processors and networks may require it.&lt;br /&gt;
&lt;br /&gt;
== NTPD Installation ==&lt;br /&gt;
To install '''NTPD package''' simply use the following commands:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 1. Update List of Available Packages ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg update&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Update Process:&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/Packages.gz.&lt;br /&gt;
 Updated source 'base'.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/firmware/Packages.gz.&lt;br /&gt;
 Updated source 'firmware'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Choose one of the available packages ===&lt;br /&gt;
==== ntpd ====&lt;br /&gt;
NTPD server package with  [[NTPD#3. Install NTPD Package|&amp;quot;Linux default configuration&amp;quot;]].&lt;br /&gt;
&lt;br /&gt;
==== metel-ntpd-server-internet ====&lt;br /&gt;
NTPD server package contains configuration as  [[NTPD#2. With Connetion to Remote NTP Servers|&amp;quot;Synchronization to two internet NTP servers&amp;quot;]], with synchronization to two internet NTP servers.&lt;br /&gt;
==== metel-ntpd-standalone-server ====&lt;br /&gt;
NTPD server package contains configuration as  [[NTPD#1. Standalone NTP server|&amp;quot;Standalone NTP server&amp;quot;]], without synchronization to internet NTP servers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. Install NTPD Package ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install ntpd&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Package Installing:&lt;br /&gt;
 Installing ntpd (4.2.8p9-9671.212083251) on root.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/ntpd_4.2.8p9-9671.212083251_all.ipk.&lt;br /&gt;
 Configuring ntpd.&lt;br /&gt;
&lt;br /&gt;
When the instalation is complete, start the NTP daemon by command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# /etc/init.d/S49ntp start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText= Every time the configuration file '''/etc/ntp.conf''' is changed, restart the service '''S49ntp''' by command '''/etc/init.d/S49ntp restart'''!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Examples ==&lt;br /&gt;
This section provides several examples of the '''/etc/ntp.conf''' configuration file.&lt;br /&gt;
&lt;br /&gt;
=== 1. Standalone NTP server ===&lt;br /&gt;
The following configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - No synchronization to internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command: &lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcar&lt;br /&gt;
  &lt;br /&gt;
 # create a local NTP server&lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. With Connetion to Remote NTP Servers ===&lt;br /&gt;
The example shows the optimal configuration for the Czech Republic. &lt;br /&gt;
&lt;br /&gt;
This configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - Synchronization to two internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File Content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcard&lt;br /&gt;
 &lt;br /&gt;
 server tik.cesnet.cz&lt;br /&gt;
 server tak.cesnet.cz&lt;br /&gt;
 &lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10 refid ILOG&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
 #end-of-file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Diagnostics ==&lt;br /&gt;
=== NTPQ ===&lt;br /&gt;
The '''ntpq''' utility program is used to query NTP servers which implement the recommended NTP mode 6 control message format about the current state and to request changes in that state.&lt;br /&gt;
&lt;br /&gt;
[http://doc.ntp.org/4.2.8p9/ntpq.html NTPQ Home Page]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre|text= root@iplog:~# watch ntpq -p -n&lt;br /&gt;
}}&lt;br /&gt;
NTPQ Parameters:&lt;br /&gt;
&lt;br /&gt;
: '''watch''' - Every 2s: ntpq -p -n&lt;br /&gt;
&lt;br /&gt;
: '''-p''' - Print current status&lt;br /&gt;
&lt;br /&gt;
: '''-n''' - Disable DNS resolving&lt;br /&gt;
&lt;br /&gt;
 Every 2s: ntpq -p -n                                        2019-08-01 10:00:12&lt;br /&gt;
 &lt;br /&gt;
      remote           refid      st t when poll reach   delay   offset  jitter&lt;br /&gt;
 ==============================================================================&lt;br /&gt;
  127.127.1.0     .ILOG.          10 l  41m   64    0    0.000    0.000   0.000&lt;br /&gt;
 +195.113.144.201 195.113.144.238  2 u   92  128  377   12.307    2.212   1.333&lt;br /&gt;
 *195.113.144.238 .GPS.            1 u   20  128  377   11.039    4.785   1.630&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This section is a copy from https://pthree.org/2013/11/05/real-life-ntp/.&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
&lt;br /&gt;
:    • '''remote''' – The remote server you wish to synchronize your clock with&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot; &amp;quot; Discarded as not valid. It is possible that you will be unable to communicate with the remote machine (it's not online), this time source is a &amp;quot;.LOCL.&amp;quot; refid time source, it's a high stratum server, or the remote server is using this computer as an NTP server.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;x&amp;quot; Discarded by the intersection algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;.&amp;quot; Discarded by table overflow (not used).&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;-&amp;quot; Discarded by the cluster algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;+&amp;quot; Included in the combined algorithm. This is a good candidate if the current server we are synchronizing with is discarded for any reason.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;#&amp;quot; Good remote server to be used as an alternative backup. This is only shown if you have more than 10 remote servers.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;*&amp;quot; The current system peer. The computer is using this remote server as its time source to synchronize the clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;o&amp;quot; Pulse per second (PPS) peer. This is generally used with GPS time sources, although any time source delivering a PPS will do. This tally code and the previous tally code &amp;quot;*&amp;quot; will not be displayed simultaneously.&lt;br /&gt;
&lt;br /&gt;
:    • '''refid''' – The upstream stratum to the remote server. For stratum 1 servers, this will be the stratum 0 source.&lt;br /&gt;
&lt;br /&gt;
:    • '''st''' – The stratum level, 0 through 16.&lt;br /&gt;
&lt;br /&gt;
:    • '''t''' –  The type of connection. &lt;br /&gt;
&lt;br /&gt;
:        ◦ l = local reference clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ u = unicast (most common)&lt;br /&gt;
&lt;br /&gt;
:        ◦ m = multicast&lt;br /&gt;
&lt;br /&gt;
:        ◦ b = broadcast&lt;br /&gt;
&lt;br /&gt;
:    • '''when''' – The last time when the server was queried for the time. Default is seconds, or &amp;quot;m&amp;quot; will be displayed for minutes, &amp;quot;h&amp;quot; for hours and &amp;quot;d&amp;quot; for days.&lt;br /&gt;
&lt;br /&gt;
:    • '''poll''' – How often the server is queried for the time, with a minimum of 8 seconds to a maximum of 36 hours. It's also displayed as a value from a power of two. Typically, it's between 64 seconds and 1024 seconds.&lt;br /&gt;
&lt;br /&gt;
:    • '''reach''' – This is an 8-bit left shift octal value that shows the success and failure rate of communicating with the remote server. Success means the bit is set, failure means the bit is not set. 377 is the highest value.&lt;br /&gt;
&lt;br /&gt;
:    • '''delay''' – This value is displayed in milliseconds, and shows the round trip time (RTT) of your computer communicating with the remote server.&lt;br /&gt;
&lt;br /&gt;
:    • '''offset''' –  This value is displayed in milliseconds, using root mean squares, and shows how far off your clock is from the reported time the server gave you. It can be positive or negative.&lt;br /&gt;
&lt;br /&gt;
:    • '''jitter''' – This number is an absolute value in milliseconds, showing the root mean squared deviation of your offsets.&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1021</id>
		<title>NTPD</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1021"/>
				<updated>2022-01-14T08:04:07Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= NTPD (Network Time Procokol Daemon) =&lt;br /&gt;
== Description ==&lt;br /&gt;
The '''NTPD''' program is an operating-system daemon that sets and maintains a computer system's time in synchronization with Internet-standard time servers. It is a complete implementation of the Network Time Protocol (NTP) version 4, but retains compatibility with versions 1, 2, and 3 as defined by RFC 1059, RFC 1119, and RFC 1305, respectively. ntpd performs most computations in 64-bit floating point arithmetic and uses 64-bit fixed point operations only when necessary to preserve the ultimate precision, about 232 picoseconds. While ordinary workstations and networks cannot achieve the ultimate precision as of 2015, future processors and networks may require it.&lt;br /&gt;
&lt;br /&gt;
== NTPD Installation ==&lt;br /&gt;
To install '''NTPD package''' simply use the following commands:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 1. Update List of Available Packages ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg update&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Update Process:&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/Packages.gz.&lt;br /&gt;
 Updated source 'base'.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/firmware/Packages.gz.&lt;br /&gt;
 Updated source 'firmware'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Choose one of the available packages ===&lt;br /&gt;
==== ntpd ====&lt;br /&gt;
NTPD server package with  [[NTPD#3. Install NTPD Package|&amp;quot;Linux default configuration&amp;quot;]].&lt;br /&gt;
&lt;br /&gt;
==== metel-ntpd-server-internet ====&lt;br /&gt;
NTPD server package contains configuration as  [[NTPD#2. With Connetion to Remote NTP Servers|&amp;quot;Synchronization to two internet NTP servers&amp;quot;]], with synchronization to two internet NTP servers.&lt;br /&gt;
==== metel-ntpd-standalone-server ====&lt;br /&gt;
NTPD server package contains configuration as  [[NTPD#1. Standalone NTP server|&amp;quot;Standalone NTP server&amp;quot;]], without synchronization to internet NTP servers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. Install NTPD Package ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install ntpd&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Package Installing:&lt;br /&gt;
 Installing ntpd (4.2.8p9-9671.212083251) on root.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/ntpd_4.2.8p9-9671.212083251_all.ipk.&lt;br /&gt;
 Configuring ntpd.&lt;br /&gt;
&lt;br /&gt;
When the instalation is complete, start the NTP daemon by command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# /etc/init.d/S49ntp start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText= Every time the configuration file '''/etc/ntp.conf''' is changed, restart the service '''S49ntp''' by command '''/etc/init.d/S49ntp restart'''!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Examples ==&lt;br /&gt;
This section provides several examples of the '''/etc/ntp.conf''' configuration file.&lt;br /&gt;
&lt;br /&gt;
=== 1. Standalone NTP server ===&lt;br /&gt;
The following configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - No synchronization to internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command: &lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcar&lt;br /&gt;
  &lt;br /&gt;
 # create a local NTP server&lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. With Connetion to Remote NTP Servers ===&lt;br /&gt;
The example shows the optimal configuration for the Czech Republic. &lt;br /&gt;
&lt;br /&gt;
This configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - Synchronization to two internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File Content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcard&lt;br /&gt;
 &lt;br /&gt;
 server tik.cesnet.cz&lt;br /&gt;
 server tak.cesnet.cz&lt;br /&gt;
 &lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10 refid ILOG&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
 #end-of-file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Diagnostics ==&lt;br /&gt;
=== NTPQ ===&lt;br /&gt;
The '''ntpq''' utility program is used to query NTP servers which implement the recommended NTP mode 6 control message format about the current state and to request changes in that state.&lt;br /&gt;
&lt;br /&gt;
[http://doc.ntp.org/4.2.8p9/ntpq.html NTPQ Home Page]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre|text= root@iplog:~# watch ntpq -p -n&lt;br /&gt;
}}&lt;br /&gt;
NTPQ Parameters:&lt;br /&gt;
&lt;br /&gt;
: '''watch''' - Every 2s: ntpq -p -n&lt;br /&gt;
&lt;br /&gt;
: '''-p''' - Print current status&lt;br /&gt;
&lt;br /&gt;
: '''-n''' - Disable DNS resolving&lt;br /&gt;
&lt;br /&gt;
 Every 2s: ntpq -p -n                                        2019-08-01 10:00:12&lt;br /&gt;
 &lt;br /&gt;
      remote           refid      st t when poll reach   delay   offset  jitter&lt;br /&gt;
 ==============================================================================&lt;br /&gt;
  127.127.1.0     .ILOG.          10 l  41m   64    0    0.000    0.000   0.000&lt;br /&gt;
 +195.113.144.201 195.113.144.238  2 u   92  128  377   12.307    2.212   1.333&lt;br /&gt;
 *195.113.144.238 .GPS.            1 u   20  128  377   11.039    4.785   1.630&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This section is a copy from https://pthree.org/2013/11/05/real-life-ntp/.&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
&lt;br /&gt;
:    • '''remote''' – The remote server you wish to synchronize your clock with&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot; &amp;quot; Discarded as not valid. It is possible that you will be unable to communicate with the remote machine (it's not online), this time source is a &amp;quot;.LOCL.&amp;quot; refid time source, it's a high stratum server, or the remote server is using this computer as an NTP server.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;x&amp;quot; Discarded by the intersection algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;.&amp;quot; Discarded by table overflow (not used).&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;-&amp;quot; Discarded by the cluster algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;+&amp;quot; Included in the combined algorithm. This is a good candidate if the current server we are synchronizing with is discarded for any reason.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;#&amp;quot; Good remote server to be used as an alternative backup. This is only shown if you have more than 10 remote servers.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;*&amp;quot; The current system peer. The computer is using this remote server as its time source to synchronize the clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;o&amp;quot; Pulse per second (PPS) peer. This is generally used with GPS time sources, although any time source delivering a PPS will do. This tally code and the previous tally code &amp;quot;*&amp;quot; will not be displayed simultaneously.&lt;br /&gt;
&lt;br /&gt;
:    • '''refid''' – The upstream stratum to the remote server. For stratum 1 servers, this will be the stratum 0 source.&lt;br /&gt;
&lt;br /&gt;
:    • '''st''' – The stratum level, 0 through 16.&lt;br /&gt;
&lt;br /&gt;
:    • '''t''' –  The type of connection. &lt;br /&gt;
&lt;br /&gt;
:        ◦ l = local reference clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ u = unicast (most common)&lt;br /&gt;
&lt;br /&gt;
:        ◦ m = multicast&lt;br /&gt;
&lt;br /&gt;
:        ◦ b = broadcast&lt;br /&gt;
&lt;br /&gt;
:    • '''when''' – The last time when the server was queried for the time. Default is seconds, or &amp;quot;m&amp;quot; will be displayed for minutes, &amp;quot;h&amp;quot; for hours and &amp;quot;d&amp;quot; for days.&lt;br /&gt;
&lt;br /&gt;
:    • '''poll''' – How often the server is queried for the time, with a minimum of 8 seconds to a maximum of 36 hours. It's also displayed as a value from a power of two. Typically, it's between 64 seconds and 1024 seconds.&lt;br /&gt;
&lt;br /&gt;
:    • '''reach''' – This is an 8-bit left shift octal value that shows the success and failure rate of communicating with the remote server. Success means the bit is set, failure means the bit is not set. 377 is the highest value.&lt;br /&gt;
&lt;br /&gt;
:    • '''delay''' – This value is displayed in milliseconds, and shows the round trip time (RTT) of your computer communicating with the remote server.&lt;br /&gt;
&lt;br /&gt;
:    • '''offset''' –  This value is displayed in milliseconds, using root mean squares, and shows how far off your clock is from the reported time the server gave you. It can be positive or negative.&lt;br /&gt;
&lt;br /&gt;
:    • '''jitter''' – This number is an absolute value in milliseconds, showing the root mean squared deviation of your offsets.&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1020</id>
		<title>NTPD</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1020"/>
				<updated>2022-01-14T08:02:50Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= NTPD (Network Time Procokol Daemon) =&lt;br /&gt;
== Description ==&lt;br /&gt;
The '''NTPD''' program is an operating-system daemon that sets and maintains a computer system's time in synchronization with Internet-standard time servers. It is a complete implementation of the Network Time Protocol (NTP) version 4, but retains compatibility with versions 1, 2, and 3 as defined by RFC 1059, RFC 1119, and RFC 1305, respectively. ntpd performs most computations in 64-bit floating point arithmetic and uses 64-bit fixed point operations only when necessary to preserve the ultimate precision, about 232 picoseconds. While ordinary workstations and networks cannot achieve the ultimate precision as of 2015, future processors and networks may require it.&lt;br /&gt;
&lt;br /&gt;
== NTPD Installation ==&lt;br /&gt;
To install '''NTPD package''' simply use the following commands:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 1. Update List of Available Packages ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg update&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Update Process:&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/Packages.gz.&lt;br /&gt;
 Updated source 'base'.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/firmware/Packages.gz.&lt;br /&gt;
 Updated source 'firmware'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Choose one of the available packages ===&lt;br /&gt;
==== ntpd ====&lt;br /&gt;
- NTPD server package with  [[NTPD#3. Install NTPD Package|&amp;quot;Linux default configuration&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
==== metel-ntpd-server-internet ====&lt;br /&gt;
- NTPD server package contains configuration as  [[NTPD#2. With Connetion to Remote NTP Servers|&amp;quot;Synchronization to two internet NTP servers&amp;quot;]], with synchronization to two internet NTP servers&lt;br /&gt;
==== metel-ntpd-standalone-server ====&lt;br /&gt;
- NTPD server package contains configuration as  [[NTPD#1. Standalone NTP server|&amp;quot;Standalone NTP server&amp;quot;]], without synchronization to internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. Install NTPD Package ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install ntpd&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Package Installing:&lt;br /&gt;
 Installing ntpd (4.2.8p9-9671.212083251) on root.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/ntpd_4.2.8p9-9671.212083251_all.ipk.&lt;br /&gt;
 Configuring ntpd.&lt;br /&gt;
&lt;br /&gt;
When the instalation is complete, start the NTP daemon by command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# /etc/init.d/S49ntp start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText= Every time the configuration file '''/etc/ntp.conf''' is changed, restart the service '''S49ntp''' by command '''/etc/init.d/S49ntp restart'''!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Examples ==&lt;br /&gt;
This section provides several examples of the '''/etc/ntp.conf''' configuration file.&lt;br /&gt;
&lt;br /&gt;
=== 1. Standalone NTP server ===&lt;br /&gt;
The following configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - No synchronization to internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command: &lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcar&lt;br /&gt;
  &lt;br /&gt;
 # create a local NTP server&lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. With Connetion to Remote NTP Servers ===&lt;br /&gt;
The example shows the optimal configuration for the Czech Republic. &lt;br /&gt;
&lt;br /&gt;
This configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - Synchronization to two internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File Content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcard&lt;br /&gt;
 &lt;br /&gt;
 server tik.cesnet.cz&lt;br /&gt;
 server tak.cesnet.cz&lt;br /&gt;
 &lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10 refid ILOG&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
 #end-of-file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Diagnostics ==&lt;br /&gt;
=== NTPQ ===&lt;br /&gt;
The '''ntpq''' utility program is used to query NTP servers which implement the recommended NTP mode 6 control message format about the current state and to request changes in that state.&lt;br /&gt;
&lt;br /&gt;
[http://doc.ntp.org/4.2.8p9/ntpq.html NTPQ Home Page]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre|text= root@iplog:~# watch ntpq -p -n&lt;br /&gt;
}}&lt;br /&gt;
NTPQ Parameters:&lt;br /&gt;
&lt;br /&gt;
: '''watch''' - Every 2s: ntpq -p -n&lt;br /&gt;
&lt;br /&gt;
: '''-p''' - Print current status&lt;br /&gt;
&lt;br /&gt;
: '''-n''' - Disable DNS resolving&lt;br /&gt;
&lt;br /&gt;
 Every 2s: ntpq -p -n                                        2019-08-01 10:00:12&lt;br /&gt;
 &lt;br /&gt;
      remote           refid      st t when poll reach   delay   offset  jitter&lt;br /&gt;
 ==============================================================================&lt;br /&gt;
  127.127.1.0     .ILOG.          10 l  41m   64    0    0.000    0.000   0.000&lt;br /&gt;
 +195.113.144.201 195.113.144.238  2 u   92  128  377   12.307    2.212   1.333&lt;br /&gt;
 *195.113.144.238 .GPS.            1 u   20  128  377   11.039    4.785   1.630&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This section is a copy from https://pthree.org/2013/11/05/real-life-ntp/.&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
&lt;br /&gt;
:    • '''remote''' – The remote server you wish to synchronize your clock with&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot; &amp;quot; Discarded as not valid. It is possible that you will be unable to communicate with the remote machine (it's not online), this time source is a &amp;quot;.LOCL.&amp;quot; refid time source, it's a high stratum server, or the remote server is using this computer as an NTP server.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;x&amp;quot; Discarded by the intersection algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;.&amp;quot; Discarded by table overflow (not used).&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;-&amp;quot; Discarded by the cluster algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;+&amp;quot; Included in the combined algorithm. This is a good candidate if the current server we are synchronizing with is discarded for any reason.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;#&amp;quot; Good remote server to be used as an alternative backup. This is only shown if you have more than 10 remote servers.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;*&amp;quot; The current system peer. The computer is using this remote server as its time source to synchronize the clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;o&amp;quot; Pulse per second (PPS) peer. This is generally used with GPS time sources, although any time source delivering a PPS will do. This tally code and the previous tally code &amp;quot;*&amp;quot; will not be displayed simultaneously.&lt;br /&gt;
&lt;br /&gt;
:    • '''refid''' – The upstream stratum to the remote server. For stratum 1 servers, this will be the stratum 0 source.&lt;br /&gt;
&lt;br /&gt;
:    • '''st''' – The stratum level, 0 through 16.&lt;br /&gt;
&lt;br /&gt;
:    • '''t''' –  The type of connection. &lt;br /&gt;
&lt;br /&gt;
:        ◦ l = local reference clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ u = unicast (most common)&lt;br /&gt;
&lt;br /&gt;
:        ◦ m = multicast&lt;br /&gt;
&lt;br /&gt;
:        ◦ b = broadcast&lt;br /&gt;
&lt;br /&gt;
:    • '''when''' – The last time when the server was queried for the time. Default is seconds, or &amp;quot;m&amp;quot; will be displayed for minutes, &amp;quot;h&amp;quot; for hours and &amp;quot;d&amp;quot; for days.&lt;br /&gt;
&lt;br /&gt;
:    • '''poll''' – How often the server is queried for the time, with a minimum of 8 seconds to a maximum of 36 hours. It's also displayed as a value from a power of two. Typically, it's between 64 seconds and 1024 seconds.&lt;br /&gt;
&lt;br /&gt;
:    • '''reach''' – This is an 8-bit left shift octal value that shows the success and failure rate of communicating with the remote server. Success means the bit is set, failure means the bit is not set. 377 is the highest value.&lt;br /&gt;
&lt;br /&gt;
:    • '''delay''' – This value is displayed in milliseconds, and shows the round trip time (RTT) of your computer communicating with the remote server.&lt;br /&gt;
&lt;br /&gt;
:    • '''offset''' –  This value is displayed in milliseconds, using root mean squares, and shows how far off your clock is from the reported time the server gave you. It can be positive or negative.&lt;br /&gt;
&lt;br /&gt;
:    • '''jitter''' – This number is an absolute value in milliseconds, showing the root mean squared deviation of your offsets.&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1019</id>
		<title>NTPD</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1019"/>
				<updated>2022-01-14T08:00:13Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= NTPD (Network Time Procokol Daemon) =&lt;br /&gt;
== Description ==&lt;br /&gt;
The '''NTPD''' program is an operating-system daemon that sets and maintains a computer system's time in synchronization with Internet-standard time servers. It is a complete implementation of the Network Time Protocol (NTP) version 4, but retains compatibility with versions 1, 2, and 3 as defined by RFC 1059, RFC 1119, and RFC 1305, respectively. ntpd performs most computations in 64-bit floating point arithmetic and uses 64-bit fixed point operations only when necessary to preserve the ultimate precision, about 232 picoseconds. While ordinary workstations and networks cannot achieve the ultimate precision as of 2015, future processors and networks may require it.&lt;br /&gt;
&lt;br /&gt;
== NTPD Installation ==&lt;br /&gt;
To install '''NTPD package''' simply use the following commands:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 1. Update List of Available Packages ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg update&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Update Process:&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/Packages.gz.&lt;br /&gt;
 Updated source 'base'.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/firmware/Packages.gz.&lt;br /&gt;
 Updated source 'firmware'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Choose one of the available packages ===&lt;br /&gt;
==== ntpd ====&lt;br /&gt;
- NTPD server package with  [[NTPD#3. Install NTPD Package|&amp;quot;Linux default configuration&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
==== metel-ntpd-server-internet ====&lt;br /&gt;
- NTPD server package contains configuration as  [[NTPD#2. With Connetion to Remote NTP Servers|&amp;quot;Synchronization to two internet NTP servers&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
==== metel-ntpd-standalone-server ====&lt;br /&gt;
- NTPD server package contains configuration as  [[NTPD#1. Standalone NTP server|&amp;quot;Standalone NTP server&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. Install NTPD Package ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install ntpd&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Package Installing:&lt;br /&gt;
 Installing ntpd (4.2.8p9-9671.212083251) on root.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/ntpd_4.2.8p9-9671.212083251_all.ipk.&lt;br /&gt;
 Configuring ntpd.&lt;br /&gt;
&lt;br /&gt;
When the instalation is complete, start the NTP daemon by command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# /etc/init.d/S49ntp start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText= Every time the configuration file '''/etc/ntp.conf''' is changed, restart the service '''S49ntp''' by command '''/etc/init.d/S49ntp restart'''!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Examples ==&lt;br /&gt;
This section provides several examples of the '''/etc/ntp.conf''' configuration file.&lt;br /&gt;
&lt;br /&gt;
=== 1. Standalone NTP server ===&lt;br /&gt;
The following configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - No synchronization to internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command: &lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcar&lt;br /&gt;
  &lt;br /&gt;
 # create a local NTP server&lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. With Connetion to Remote NTP Servers ===&lt;br /&gt;
The example shows the optimal configuration for the Czech Republic. &lt;br /&gt;
&lt;br /&gt;
This configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - Synchronization to two internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File Content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcard&lt;br /&gt;
 &lt;br /&gt;
 server tik.cesnet.cz&lt;br /&gt;
 server tak.cesnet.cz&lt;br /&gt;
 &lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10 refid ILOG&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
 #end-of-file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Diagnostics ==&lt;br /&gt;
=== NTPQ ===&lt;br /&gt;
The '''ntpq''' utility program is used to query NTP servers which implement the recommended NTP mode 6 control message format about the current state and to request changes in that state.&lt;br /&gt;
&lt;br /&gt;
[http://doc.ntp.org/4.2.8p9/ntpq.html NTPQ Home Page]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre|text= root@iplog:~# watch ntpq -p -n&lt;br /&gt;
}}&lt;br /&gt;
NTPQ Parameters:&lt;br /&gt;
&lt;br /&gt;
: '''watch''' - Every 2s: ntpq -p -n&lt;br /&gt;
&lt;br /&gt;
: '''-p''' - Print current status&lt;br /&gt;
&lt;br /&gt;
: '''-n''' - Disable DNS resolving&lt;br /&gt;
&lt;br /&gt;
 Every 2s: ntpq -p -n                                        2019-08-01 10:00:12&lt;br /&gt;
 &lt;br /&gt;
      remote           refid      st t when poll reach   delay   offset  jitter&lt;br /&gt;
 ==============================================================================&lt;br /&gt;
  127.127.1.0     .ILOG.          10 l  41m   64    0    0.000    0.000   0.000&lt;br /&gt;
 +195.113.144.201 195.113.144.238  2 u   92  128  377   12.307    2.212   1.333&lt;br /&gt;
 *195.113.144.238 .GPS.            1 u   20  128  377   11.039    4.785   1.630&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This section is a copy from https://pthree.org/2013/11/05/real-life-ntp/.&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
&lt;br /&gt;
:    • '''remote''' – The remote server you wish to synchronize your clock with&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot; &amp;quot; Discarded as not valid. It is possible that you will be unable to communicate with the remote machine (it's not online), this time source is a &amp;quot;.LOCL.&amp;quot; refid time source, it's a high stratum server, or the remote server is using this computer as an NTP server.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;x&amp;quot; Discarded by the intersection algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;.&amp;quot; Discarded by table overflow (not used).&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;-&amp;quot; Discarded by the cluster algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;+&amp;quot; Included in the combined algorithm. This is a good candidate if the current server we are synchronizing with is discarded for any reason.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;#&amp;quot; Good remote server to be used as an alternative backup. This is only shown if you have more than 10 remote servers.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;*&amp;quot; The current system peer. The computer is using this remote server as its time source to synchronize the clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;o&amp;quot; Pulse per second (PPS) peer. This is generally used with GPS time sources, although any time source delivering a PPS will do. This tally code and the previous tally code &amp;quot;*&amp;quot; will not be displayed simultaneously.&lt;br /&gt;
&lt;br /&gt;
:    • '''refid''' – The upstream stratum to the remote server. For stratum 1 servers, this will be the stratum 0 source.&lt;br /&gt;
&lt;br /&gt;
:    • '''st''' – The stratum level, 0 through 16.&lt;br /&gt;
&lt;br /&gt;
:    • '''t''' –  The type of connection. &lt;br /&gt;
&lt;br /&gt;
:        ◦ l = local reference clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ u = unicast (most common)&lt;br /&gt;
&lt;br /&gt;
:        ◦ m = multicast&lt;br /&gt;
&lt;br /&gt;
:        ◦ b = broadcast&lt;br /&gt;
&lt;br /&gt;
:    • '''when''' – The last time when the server was queried for the time. Default is seconds, or &amp;quot;m&amp;quot; will be displayed for minutes, &amp;quot;h&amp;quot; for hours and &amp;quot;d&amp;quot; for days.&lt;br /&gt;
&lt;br /&gt;
:    • '''poll''' – How often the server is queried for the time, with a minimum of 8 seconds to a maximum of 36 hours. It's also displayed as a value from a power of two. Typically, it's between 64 seconds and 1024 seconds.&lt;br /&gt;
&lt;br /&gt;
:    • '''reach''' – This is an 8-bit left shift octal value that shows the success and failure rate of communicating with the remote server. Success means the bit is set, failure means the bit is not set. 377 is the highest value.&lt;br /&gt;
&lt;br /&gt;
:    • '''delay''' – This value is displayed in milliseconds, and shows the round trip time (RTT) of your computer communicating with the remote server.&lt;br /&gt;
&lt;br /&gt;
:    • '''offset''' –  This value is displayed in milliseconds, using root mean squares, and shows how far off your clock is from the reported time the server gave you. It can be positive or negative.&lt;br /&gt;
&lt;br /&gt;
:    • '''jitter''' – This number is an absolute value in milliseconds, showing the root mean squared deviation of your offsets.&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1018</id>
		<title>NTPD</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1018"/>
				<updated>2022-01-14T07:59:19Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= NTPD (Network Time Procokol Daemon) =&lt;br /&gt;
== Description ==&lt;br /&gt;
The '''NTPD''' program is an operating-system daemon that sets and maintains a computer system's time in synchronization with Internet-standard time servers. It is a complete implementation of the Network Time Protocol (NTP) version 4, but retains compatibility with versions 1, 2, and 3 as defined by RFC 1059, RFC 1119, and RFC 1305, respectively. ntpd performs most computations in 64-bit floating point arithmetic and uses 64-bit fixed point operations only when necessary to preserve the ultimate precision, about 232 picoseconds. While ordinary workstations and networks cannot achieve the ultimate precision as of 2015, future processors and networks may require it.&lt;br /&gt;
&lt;br /&gt;
== NTPD Installation ==&lt;br /&gt;
To install '''NTPD package''' simply use the following commands:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 1. Update List of Available Packages ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg update&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Update Process:&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/Packages.gz.&lt;br /&gt;
 Updated source 'base'.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/firmware/Packages.gz.&lt;br /&gt;
 Updated source 'firmware'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Choose one of the available packages ===&lt;br /&gt;
==== ntpd ====&lt;br /&gt;
- NTPD server package with [[NTPD#3. Install NTPD Package|linux default configuration]]&lt;br /&gt;
&lt;br /&gt;
==== metel-ntpd-server-internet ====&lt;br /&gt;
- NTPD server package contains configuration as [[NTPD#2. With Connetion to Remote NTP Servers|&amp;quot;Synchronization to two internet NTP servers&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
==== metel-ntpd-standalone-server ====&lt;br /&gt;
- NTPD server package contains configuration as [[NTPD#1. Standalone NTP server|&amp;quot;Standalone NTP server&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. Install NTPD Package ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install ntpd&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Package Installing:&lt;br /&gt;
 Installing ntpd (4.2.8p9-9671.212083251) on root.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/ntpd_4.2.8p9-9671.212083251_all.ipk.&lt;br /&gt;
 Configuring ntpd.&lt;br /&gt;
&lt;br /&gt;
When the instalation is complete, start the NTP daemon by command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# /etc/init.d/S49ntp start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText= Every time the configuration file '''/etc/ntp.conf''' is changed, restart the service '''S49ntp''' by command '''/etc/init.d/S49ntp restart'''!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Examples ==&lt;br /&gt;
This section provides several examples of the '''/etc/ntp.conf''' configuration file.&lt;br /&gt;
&lt;br /&gt;
=== 1. Standalone NTP server ===&lt;br /&gt;
The following configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - No synchronization to internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command: &lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcar&lt;br /&gt;
  &lt;br /&gt;
 # create a local NTP server&lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. With Connetion to Remote NTP Servers ===&lt;br /&gt;
The example shows the optimal configuration for the Czech Republic. &lt;br /&gt;
&lt;br /&gt;
This configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - Synchronization to two internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File Content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcard&lt;br /&gt;
 &lt;br /&gt;
 server tik.cesnet.cz&lt;br /&gt;
 server tak.cesnet.cz&lt;br /&gt;
 &lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10 refid ILOG&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
 #end-of-file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Diagnostics ==&lt;br /&gt;
=== NTPQ ===&lt;br /&gt;
The '''ntpq''' utility program is used to query NTP servers which implement the recommended NTP mode 6 control message format about the current state and to request changes in that state.&lt;br /&gt;
&lt;br /&gt;
[http://doc.ntp.org/4.2.8p9/ntpq.html NTPQ Home Page]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre|text= root@iplog:~# watch ntpq -p -n&lt;br /&gt;
}}&lt;br /&gt;
NTPQ Parameters:&lt;br /&gt;
&lt;br /&gt;
: '''watch''' - Every 2s: ntpq -p -n&lt;br /&gt;
&lt;br /&gt;
: '''-p''' - Print current status&lt;br /&gt;
&lt;br /&gt;
: '''-n''' - Disable DNS resolving&lt;br /&gt;
&lt;br /&gt;
 Every 2s: ntpq -p -n                                        2019-08-01 10:00:12&lt;br /&gt;
 &lt;br /&gt;
      remote           refid      st t when poll reach   delay   offset  jitter&lt;br /&gt;
 ==============================================================================&lt;br /&gt;
  127.127.1.0     .ILOG.          10 l  41m   64    0    0.000    0.000   0.000&lt;br /&gt;
 +195.113.144.201 195.113.144.238  2 u   92  128  377   12.307    2.212   1.333&lt;br /&gt;
 *195.113.144.238 .GPS.            1 u   20  128  377   11.039    4.785   1.630&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This section is a copy from https://pthree.org/2013/11/05/real-life-ntp/.&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
&lt;br /&gt;
:    • '''remote''' – The remote server you wish to synchronize your clock with&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot; &amp;quot; Discarded as not valid. It is possible that you will be unable to communicate with the remote machine (it's not online), this time source is a &amp;quot;.LOCL.&amp;quot; refid time source, it's a high stratum server, or the remote server is using this computer as an NTP server.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;x&amp;quot; Discarded by the intersection algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;.&amp;quot; Discarded by table overflow (not used).&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;-&amp;quot; Discarded by the cluster algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;+&amp;quot; Included in the combined algorithm. This is a good candidate if the current server we are synchronizing with is discarded for any reason.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;#&amp;quot; Good remote server to be used as an alternative backup. This is only shown if you have more than 10 remote servers.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;*&amp;quot; The current system peer. The computer is using this remote server as its time source to synchronize the clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;o&amp;quot; Pulse per second (PPS) peer. This is generally used with GPS time sources, although any time source delivering a PPS will do. This tally code and the previous tally code &amp;quot;*&amp;quot; will not be displayed simultaneously.&lt;br /&gt;
&lt;br /&gt;
:    • '''refid''' – The upstream stratum to the remote server. For stratum 1 servers, this will be the stratum 0 source.&lt;br /&gt;
&lt;br /&gt;
:    • '''st''' – The stratum level, 0 through 16.&lt;br /&gt;
&lt;br /&gt;
:    • '''t''' –  The type of connection. &lt;br /&gt;
&lt;br /&gt;
:        ◦ l = local reference clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ u = unicast (most common)&lt;br /&gt;
&lt;br /&gt;
:        ◦ m = multicast&lt;br /&gt;
&lt;br /&gt;
:        ◦ b = broadcast&lt;br /&gt;
&lt;br /&gt;
:    • '''when''' – The last time when the server was queried for the time. Default is seconds, or &amp;quot;m&amp;quot; will be displayed for minutes, &amp;quot;h&amp;quot; for hours and &amp;quot;d&amp;quot; for days.&lt;br /&gt;
&lt;br /&gt;
:    • '''poll''' – How often the server is queried for the time, with a minimum of 8 seconds to a maximum of 36 hours. It's also displayed as a value from a power of two. Typically, it's between 64 seconds and 1024 seconds.&lt;br /&gt;
&lt;br /&gt;
:    • '''reach''' – This is an 8-bit left shift octal value that shows the success and failure rate of communicating with the remote server. Success means the bit is set, failure means the bit is not set. 377 is the highest value.&lt;br /&gt;
&lt;br /&gt;
:    • '''delay''' – This value is displayed in milliseconds, and shows the round trip time (RTT) of your computer communicating with the remote server.&lt;br /&gt;
&lt;br /&gt;
:    • '''offset''' –  This value is displayed in milliseconds, using root mean squares, and shows how far off your clock is from the reported time the server gave you. It can be positive or negative.&lt;br /&gt;
&lt;br /&gt;
:    • '''jitter''' – This number is an absolute value in milliseconds, showing the root mean squared deviation of your offsets.&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1017</id>
		<title>NTPD</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1017"/>
				<updated>2022-01-14T07:56:03Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= NTPD (Network Time Procokol Daemon) =&lt;br /&gt;
== Description ==&lt;br /&gt;
The '''NTPD''' program is an operating-system daemon that sets and maintains a computer system's time in synchronization with Internet-standard time servers. It is a complete implementation of the Network Time Protocol (NTP) version 4, but retains compatibility with versions 1, 2, and 3 as defined by RFC 1059, RFC 1119, and RFC 1305, respectively. ntpd performs most computations in 64-bit floating point arithmetic and uses 64-bit fixed point operations only when necessary to preserve the ultimate precision, about 232 picoseconds. While ordinary workstations and networks cannot achieve the ultimate precision as of 2015, future processors and networks may require it.&lt;br /&gt;
&lt;br /&gt;
== NTPD Installation ==&lt;br /&gt;
To install '''NTPD package''' simply use the following commands:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 1. Update List of Available Packages ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg update&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Update Process:&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/Packages.gz.&lt;br /&gt;
 Updated source 'base'.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/firmware/Packages.gz.&lt;br /&gt;
 Updated source 'firmware'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Choose one of the available packages ===&lt;br /&gt;
==== [[NTPD#3. Install NTPD Package|ntpd]] ====&lt;br /&gt;
- NTPD server package with linux default configuration&lt;br /&gt;
&lt;br /&gt;
==== [[NTPD#2. With Connetion to Remote NTP Servers|metel-ntpd-server-internet]] ====&lt;br /&gt;
- NTPD server package contains configuration as &amp;quot;Synchronization to two internet NTP servers&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==== [[NTPD#1. Standalone NTP server|metel-ntpd-standalone-server]] ====&lt;br /&gt;
- NTPD server package contains configuration as &amp;quot;Standalone NTP server&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. Install NTPD Package ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install ntpd&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Package Installing:&lt;br /&gt;
 Installing ntpd (4.2.8p9-9671.212083251) on root.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/ntpd_4.2.8p9-9671.212083251_all.ipk.&lt;br /&gt;
 Configuring ntpd.&lt;br /&gt;
&lt;br /&gt;
When the instalation is complete, start the NTP daemon by command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# /etc/init.d/S49ntp start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText= Every time the configuration file '''/etc/ntp.conf''' is changed, restart the service '''S49ntp''' by command '''/etc/init.d/S49ntp restart'''!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Examples ==&lt;br /&gt;
This section provides several examples of the '''/etc/ntp.conf''' configuration file.&lt;br /&gt;
&lt;br /&gt;
=== 1. Standalone NTP server ===&lt;br /&gt;
The following configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - No synchronization to internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command: &lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcar&lt;br /&gt;
  &lt;br /&gt;
 # create a local NTP server&lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. With Connetion to Remote NTP Servers ===&lt;br /&gt;
The example shows the optimal configuration for the Czech Republic. &lt;br /&gt;
&lt;br /&gt;
This configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - Synchronization to two internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File Content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcard&lt;br /&gt;
 &lt;br /&gt;
 server tik.cesnet.cz&lt;br /&gt;
 server tak.cesnet.cz&lt;br /&gt;
 &lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10 refid ILOG&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
 #end-of-file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Diagnostics ==&lt;br /&gt;
=== NTPQ ===&lt;br /&gt;
The '''ntpq''' utility program is used to query NTP servers which implement the recommended NTP mode 6 control message format about the current state and to request changes in that state.&lt;br /&gt;
&lt;br /&gt;
[http://doc.ntp.org/4.2.8p9/ntpq.html NTPQ Home Page]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre|text= root@iplog:~# watch ntpq -p -n&lt;br /&gt;
}}&lt;br /&gt;
NTPQ Parameters:&lt;br /&gt;
&lt;br /&gt;
: '''watch''' - Every 2s: ntpq -p -n&lt;br /&gt;
&lt;br /&gt;
: '''-p''' - Print current status&lt;br /&gt;
&lt;br /&gt;
: '''-n''' - Disable DNS resolving&lt;br /&gt;
&lt;br /&gt;
 Every 2s: ntpq -p -n                                        2019-08-01 10:00:12&lt;br /&gt;
 &lt;br /&gt;
      remote           refid      st t when poll reach   delay   offset  jitter&lt;br /&gt;
 ==============================================================================&lt;br /&gt;
  127.127.1.0     .ILOG.          10 l  41m   64    0    0.000    0.000   0.000&lt;br /&gt;
 +195.113.144.201 195.113.144.238  2 u   92  128  377   12.307    2.212   1.333&lt;br /&gt;
 *195.113.144.238 .GPS.            1 u   20  128  377   11.039    4.785   1.630&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This section is a copy from https://pthree.org/2013/11/05/real-life-ntp/.&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
&lt;br /&gt;
:    • '''remote''' – The remote server you wish to synchronize your clock with&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot; &amp;quot; Discarded as not valid. It is possible that you will be unable to communicate with the remote machine (it's not online), this time source is a &amp;quot;.LOCL.&amp;quot; refid time source, it's a high stratum server, or the remote server is using this computer as an NTP server.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;x&amp;quot; Discarded by the intersection algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;.&amp;quot; Discarded by table overflow (not used).&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;-&amp;quot; Discarded by the cluster algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;+&amp;quot; Included in the combined algorithm. This is a good candidate if the current server we are synchronizing with is discarded for any reason.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;#&amp;quot; Good remote server to be used as an alternative backup. This is only shown if you have more than 10 remote servers.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;*&amp;quot; The current system peer. The computer is using this remote server as its time source to synchronize the clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;o&amp;quot; Pulse per second (PPS) peer. This is generally used with GPS time sources, although any time source delivering a PPS will do. This tally code and the previous tally code &amp;quot;*&amp;quot; will not be displayed simultaneously.&lt;br /&gt;
&lt;br /&gt;
:    • '''refid''' – The upstream stratum to the remote server. For stratum 1 servers, this will be the stratum 0 source.&lt;br /&gt;
&lt;br /&gt;
:    • '''st''' – The stratum level, 0 through 16.&lt;br /&gt;
&lt;br /&gt;
:    • '''t''' –  The type of connection. &lt;br /&gt;
&lt;br /&gt;
:        ◦ l = local reference clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ u = unicast (most common)&lt;br /&gt;
&lt;br /&gt;
:        ◦ m = multicast&lt;br /&gt;
&lt;br /&gt;
:        ◦ b = broadcast&lt;br /&gt;
&lt;br /&gt;
:    • '''when''' – The last time when the server was queried for the time. Default is seconds, or &amp;quot;m&amp;quot; will be displayed for minutes, &amp;quot;h&amp;quot; for hours and &amp;quot;d&amp;quot; for days.&lt;br /&gt;
&lt;br /&gt;
:    • '''poll''' – How often the server is queried for the time, with a minimum of 8 seconds to a maximum of 36 hours. It's also displayed as a value from a power of two. Typically, it's between 64 seconds and 1024 seconds.&lt;br /&gt;
&lt;br /&gt;
:    • '''reach''' – This is an 8-bit left shift octal value that shows the success and failure rate of communicating with the remote server. Success means the bit is set, failure means the bit is not set. 377 is the highest value.&lt;br /&gt;
&lt;br /&gt;
:    • '''delay''' – This value is displayed in milliseconds, and shows the round trip time (RTT) of your computer communicating with the remote server.&lt;br /&gt;
&lt;br /&gt;
:    • '''offset''' –  This value is displayed in milliseconds, using root mean squares, and shows how far off your clock is from the reported time the server gave you. It can be positive or negative.&lt;br /&gt;
&lt;br /&gt;
:    • '''jitter''' – This number is an absolute value in milliseconds, showing the root mean squared deviation of your offsets.&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1016</id>
		<title>NTPD</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1016"/>
				<updated>2022-01-14T07:55:10Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= NTPD (Network Time Procokol Daemon) =&lt;br /&gt;
== Description ==&lt;br /&gt;
The '''NTPD''' program is an operating-system daemon that sets and maintains a computer system's time in synchronization with Internet-standard time servers. It is a complete implementation of the Network Time Protocol (NTP) version 4, but retains compatibility with versions 1, 2, and 3 as defined by RFC 1059, RFC 1119, and RFC 1305, respectively. ntpd performs most computations in 64-bit floating point arithmetic and uses 64-bit fixed point operations only when necessary to preserve the ultimate precision, about 232 picoseconds. While ordinary workstations and networks cannot achieve the ultimate precision as of 2015, future processors and networks may require it.&lt;br /&gt;
&lt;br /&gt;
== NTPD Installation ==&lt;br /&gt;
To install '''NTPD package''' simply use the following commands:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 1. Update List of Available Packages ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg update&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Update Process:&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/Packages.gz.&lt;br /&gt;
 Updated source 'base'.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/firmware/Packages.gz.&lt;br /&gt;
 Updated source 'firmware'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Choose one of the available packages ===&lt;br /&gt;
==== [[NTPD#3. Install NTPD Package|ntpd]] ====&lt;br /&gt;
- server package with linux default configuration&lt;br /&gt;
&lt;br /&gt;
==== [[NTPD#2. With Connetion to Remote NTP Servers|metel-ntpd-server-internet]] ====&lt;br /&gt;
- server package contains configuration as &amp;quot;Synchronization to two internet NTP servers&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==== [[NTPD#1. Standalone NTP server|metel-ntpd-standalone-server]] ====&lt;br /&gt;
- server package contains configuration as &amp;quot;Standalone NTP server&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. Install NTPD Package ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install ntpd&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Package Installing:&lt;br /&gt;
 Installing ntpd (4.2.8p9-9671.212083251) on root.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/ntpd_4.2.8p9-9671.212083251_all.ipk.&lt;br /&gt;
 Configuring ntpd.&lt;br /&gt;
&lt;br /&gt;
When the instalation is complete, start the NTP daemon by command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# /etc/init.d/S49ntp start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText= Every time the configuration file '''/etc/ntp.conf''' is changed, restart the service '''S49ntp''' by command '''/etc/init.d/S49ntp restart'''!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Examples ==&lt;br /&gt;
This section provides several examples of the '''/etc/ntp.conf''' configuration file.&lt;br /&gt;
&lt;br /&gt;
=== 1. Standalone NTP server ===&lt;br /&gt;
The following configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - No synchronization to internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command: &lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcar&lt;br /&gt;
  &lt;br /&gt;
 # create a local NTP server&lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. With Connetion to Remote NTP Servers ===&lt;br /&gt;
The example shows the optimal configuration for the Czech Republic. &lt;br /&gt;
&lt;br /&gt;
This configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - Synchronization to two internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File Content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcard&lt;br /&gt;
 &lt;br /&gt;
 server tik.cesnet.cz&lt;br /&gt;
 server tak.cesnet.cz&lt;br /&gt;
 &lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10 refid ILOG&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
 #end-of-file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Diagnostics ==&lt;br /&gt;
=== NTPQ ===&lt;br /&gt;
The '''ntpq''' utility program is used to query NTP servers which implement the recommended NTP mode 6 control message format about the current state and to request changes in that state.&lt;br /&gt;
&lt;br /&gt;
[http://doc.ntp.org/4.2.8p9/ntpq.html NTPQ Home Page]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre|text= root@iplog:~# watch ntpq -p -n&lt;br /&gt;
}}&lt;br /&gt;
NTPQ Parameters:&lt;br /&gt;
&lt;br /&gt;
: '''watch''' - Every 2s: ntpq -p -n&lt;br /&gt;
&lt;br /&gt;
: '''-p''' - Print current status&lt;br /&gt;
&lt;br /&gt;
: '''-n''' - Disable DNS resolving&lt;br /&gt;
&lt;br /&gt;
 Every 2s: ntpq -p -n                                        2019-08-01 10:00:12&lt;br /&gt;
 &lt;br /&gt;
      remote           refid      st t when poll reach   delay   offset  jitter&lt;br /&gt;
 ==============================================================================&lt;br /&gt;
  127.127.1.0     .ILOG.          10 l  41m   64    0    0.000    0.000   0.000&lt;br /&gt;
 +195.113.144.201 195.113.144.238  2 u   92  128  377   12.307    2.212   1.333&lt;br /&gt;
 *195.113.144.238 .GPS.            1 u   20  128  377   11.039    4.785   1.630&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This section is a copy from https://pthree.org/2013/11/05/real-life-ntp/.&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
&lt;br /&gt;
:    • '''remote''' – The remote server you wish to synchronize your clock with&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot; &amp;quot; Discarded as not valid. It is possible that you will be unable to communicate with the remote machine (it's not online), this time source is a &amp;quot;.LOCL.&amp;quot; refid time source, it's a high stratum server, or the remote server is using this computer as an NTP server.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;x&amp;quot; Discarded by the intersection algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;.&amp;quot; Discarded by table overflow (not used).&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;-&amp;quot; Discarded by the cluster algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;+&amp;quot; Included in the combined algorithm. This is a good candidate if the current server we are synchronizing with is discarded for any reason.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;#&amp;quot; Good remote server to be used as an alternative backup. This is only shown if you have more than 10 remote servers.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;*&amp;quot; The current system peer. The computer is using this remote server as its time source to synchronize the clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;o&amp;quot; Pulse per second (PPS) peer. This is generally used with GPS time sources, although any time source delivering a PPS will do. This tally code and the previous tally code &amp;quot;*&amp;quot; will not be displayed simultaneously.&lt;br /&gt;
&lt;br /&gt;
:    • '''refid''' – The upstream stratum to the remote server. For stratum 1 servers, this will be the stratum 0 source.&lt;br /&gt;
&lt;br /&gt;
:    • '''st''' – The stratum level, 0 through 16.&lt;br /&gt;
&lt;br /&gt;
:    • '''t''' –  The type of connection. &lt;br /&gt;
&lt;br /&gt;
:        ◦ l = local reference clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ u = unicast (most common)&lt;br /&gt;
&lt;br /&gt;
:        ◦ m = multicast&lt;br /&gt;
&lt;br /&gt;
:        ◦ b = broadcast&lt;br /&gt;
&lt;br /&gt;
:    • '''when''' – The last time when the server was queried for the time. Default is seconds, or &amp;quot;m&amp;quot; will be displayed for minutes, &amp;quot;h&amp;quot; for hours and &amp;quot;d&amp;quot; for days.&lt;br /&gt;
&lt;br /&gt;
:    • '''poll''' – How often the server is queried for the time, with a minimum of 8 seconds to a maximum of 36 hours. It's also displayed as a value from a power of two. Typically, it's between 64 seconds and 1024 seconds.&lt;br /&gt;
&lt;br /&gt;
:    • '''reach''' – This is an 8-bit left shift octal value that shows the success and failure rate of communicating with the remote server. Success means the bit is set, failure means the bit is not set. 377 is the highest value.&lt;br /&gt;
&lt;br /&gt;
:    • '''delay''' – This value is displayed in milliseconds, and shows the round trip time (RTT) of your computer communicating with the remote server.&lt;br /&gt;
&lt;br /&gt;
:    • '''offset''' –  This value is displayed in milliseconds, using root mean squares, and shows how far off your clock is from the reported time the server gave you. It can be positive or negative.&lt;br /&gt;
&lt;br /&gt;
:    • '''jitter''' – This number is an absolute value in milliseconds, showing the root mean squared deviation of your offsets.&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1015</id>
		<title>NTPD</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1015"/>
				<updated>2022-01-14T07:54:50Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= NTPD (Network Time Procokol Daemon) =&lt;br /&gt;
== Description ==&lt;br /&gt;
The '''NTPD''' program is an operating-system daemon that sets and maintains a computer system's time in synchronization with Internet-standard time servers. It is a complete implementation of the Network Time Protocol (NTP) version 4, but retains compatibility with versions 1, 2, and 3 as defined by RFC 1059, RFC 1119, and RFC 1305, respectively. ntpd performs most computations in 64-bit floating point arithmetic and uses 64-bit fixed point operations only when necessary to preserve the ultimate precision, about 232 picoseconds. While ordinary workstations and networks cannot achieve the ultimate precision as of 2015, future processors and networks may require it.&lt;br /&gt;
&lt;br /&gt;
== NTPD Installation ==&lt;br /&gt;
To install '''NTPD package''' simply use the following commands:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 1. Update List of Available Packages ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg update&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Update Process:&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/Packages.gz.&lt;br /&gt;
 Updated source 'base'.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/firmware/Packages.gz.&lt;br /&gt;
 Updated source 'firmware'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Choose one of the available packages ===&lt;br /&gt;
==== [[NTPD#3. Install NTPD Package|ntpd]] ====&lt;br /&gt;
- server package with linux default configuration&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== [[NTPD#2. With Connetion to Remote NTP Servers|metel-ntpd-server-internet]] ====&lt;br /&gt;
- server package contains configuration as &amp;quot;Synchronization to two internet NTP servers&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== [[NTPD#1. Standalone NTP server|metel-ntpd-standalone-server]] ====&lt;br /&gt;
- server package contains configuration as &amp;quot;Standalone NTP server&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. Install NTPD Package ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install ntpd&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Package Installing:&lt;br /&gt;
 Installing ntpd (4.2.8p9-9671.212083251) on root.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/ntpd_4.2.8p9-9671.212083251_all.ipk.&lt;br /&gt;
 Configuring ntpd.&lt;br /&gt;
&lt;br /&gt;
When the instalation is complete, start the NTP daemon by command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# /etc/init.d/S49ntp start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText= Every time the configuration file '''/etc/ntp.conf''' is changed, restart the service '''S49ntp''' by command '''/etc/init.d/S49ntp restart'''!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Examples ==&lt;br /&gt;
This section provides several examples of the '''/etc/ntp.conf''' configuration file.&lt;br /&gt;
&lt;br /&gt;
=== 1. Standalone NTP server ===&lt;br /&gt;
The following configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - No synchronization to internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command: &lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcar&lt;br /&gt;
  &lt;br /&gt;
 # create a local NTP server&lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. With Connetion to Remote NTP Servers ===&lt;br /&gt;
The example shows the optimal configuration for the Czech Republic. &lt;br /&gt;
&lt;br /&gt;
This configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - Synchronization to two internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File Content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcard&lt;br /&gt;
 &lt;br /&gt;
 server tik.cesnet.cz&lt;br /&gt;
 server tak.cesnet.cz&lt;br /&gt;
 &lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10 refid ILOG&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
 #end-of-file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Diagnostics ==&lt;br /&gt;
=== NTPQ ===&lt;br /&gt;
The '''ntpq''' utility program is used to query NTP servers which implement the recommended NTP mode 6 control message format about the current state and to request changes in that state.&lt;br /&gt;
&lt;br /&gt;
[http://doc.ntp.org/4.2.8p9/ntpq.html NTPQ Home Page]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre|text= root@iplog:~# watch ntpq -p -n&lt;br /&gt;
}}&lt;br /&gt;
NTPQ Parameters:&lt;br /&gt;
&lt;br /&gt;
: '''watch''' - Every 2s: ntpq -p -n&lt;br /&gt;
&lt;br /&gt;
: '''-p''' - Print current status&lt;br /&gt;
&lt;br /&gt;
: '''-n''' - Disable DNS resolving&lt;br /&gt;
&lt;br /&gt;
 Every 2s: ntpq -p -n                                        2019-08-01 10:00:12&lt;br /&gt;
 &lt;br /&gt;
      remote           refid      st t when poll reach   delay   offset  jitter&lt;br /&gt;
 ==============================================================================&lt;br /&gt;
  127.127.1.0     .ILOG.          10 l  41m   64    0    0.000    0.000   0.000&lt;br /&gt;
 +195.113.144.201 195.113.144.238  2 u   92  128  377   12.307    2.212   1.333&lt;br /&gt;
 *195.113.144.238 .GPS.            1 u   20  128  377   11.039    4.785   1.630&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This section is a copy from https://pthree.org/2013/11/05/real-life-ntp/.&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
&lt;br /&gt;
:    • '''remote''' – The remote server you wish to synchronize your clock with&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot; &amp;quot; Discarded as not valid. It is possible that you will be unable to communicate with the remote machine (it's not online), this time source is a &amp;quot;.LOCL.&amp;quot; refid time source, it's a high stratum server, or the remote server is using this computer as an NTP server.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;x&amp;quot; Discarded by the intersection algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;.&amp;quot; Discarded by table overflow (not used).&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;-&amp;quot; Discarded by the cluster algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;+&amp;quot; Included in the combined algorithm. This is a good candidate if the current server we are synchronizing with is discarded for any reason.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;#&amp;quot; Good remote server to be used as an alternative backup. This is only shown if you have more than 10 remote servers.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;*&amp;quot; The current system peer. The computer is using this remote server as its time source to synchronize the clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;o&amp;quot; Pulse per second (PPS) peer. This is generally used with GPS time sources, although any time source delivering a PPS will do. This tally code and the previous tally code &amp;quot;*&amp;quot; will not be displayed simultaneously.&lt;br /&gt;
&lt;br /&gt;
:    • '''refid''' – The upstream stratum to the remote server. For stratum 1 servers, this will be the stratum 0 source.&lt;br /&gt;
&lt;br /&gt;
:    • '''st''' – The stratum level, 0 through 16.&lt;br /&gt;
&lt;br /&gt;
:    • '''t''' –  The type of connection. &lt;br /&gt;
&lt;br /&gt;
:        ◦ l = local reference clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ u = unicast (most common)&lt;br /&gt;
&lt;br /&gt;
:        ◦ m = multicast&lt;br /&gt;
&lt;br /&gt;
:        ◦ b = broadcast&lt;br /&gt;
&lt;br /&gt;
:    • '''when''' – The last time when the server was queried for the time. Default is seconds, or &amp;quot;m&amp;quot; will be displayed for minutes, &amp;quot;h&amp;quot; for hours and &amp;quot;d&amp;quot; for days.&lt;br /&gt;
&lt;br /&gt;
:    • '''poll''' – How often the server is queried for the time, with a minimum of 8 seconds to a maximum of 36 hours. It's also displayed as a value from a power of two. Typically, it's between 64 seconds and 1024 seconds.&lt;br /&gt;
&lt;br /&gt;
:    • '''reach''' – This is an 8-bit left shift octal value that shows the success and failure rate of communicating with the remote server. Success means the bit is set, failure means the bit is not set. 377 is the highest value.&lt;br /&gt;
&lt;br /&gt;
:    • '''delay''' – This value is displayed in milliseconds, and shows the round trip time (RTT) of your computer communicating with the remote server.&lt;br /&gt;
&lt;br /&gt;
:    • '''offset''' –  This value is displayed in milliseconds, using root mean squares, and shows how far off your clock is from the reported time the server gave you. It can be positive or negative.&lt;br /&gt;
&lt;br /&gt;
:    • '''jitter''' – This number is an absolute value in milliseconds, showing the root mean squared deviation of your offsets.&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1014</id>
		<title>NTPD</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1014"/>
				<updated>2022-01-14T07:53:07Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= NTPD (Network Time Procokol Daemon) =&lt;br /&gt;
== Description ==&lt;br /&gt;
The '''NTPD''' program is an operating-system daemon that sets and maintains a computer system's time in synchronization with Internet-standard time servers. It is a complete implementation of the Network Time Protocol (NTP) version 4, but retains compatibility with versions 1, 2, and 3 as defined by RFC 1059, RFC 1119, and RFC 1305, respectively. ntpd performs most computations in 64-bit floating point arithmetic and uses 64-bit fixed point operations only when necessary to preserve the ultimate precision, about 232 picoseconds. While ordinary workstations and networks cannot achieve the ultimate precision as of 2015, future processors and networks may require it.&lt;br /&gt;
&lt;br /&gt;
== NTPD Installation ==&lt;br /&gt;
To install '''NTPD package''' simply use the following commands:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 1. Update List of Available Packages ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg update&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Update Process:&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/Packages.gz.&lt;br /&gt;
 Updated source 'base'.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/firmware/Packages.gz.&lt;br /&gt;
 Updated source 'firmware'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Choose one of the available packages ===&lt;br /&gt;
==== [[NTPD#Install NTPD Package|ntpd]] ====&lt;br /&gt;
- server package with linux default configuration&lt;br /&gt;
&lt;br /&gt;
==== [[NTPD#2. With Connetion to Remote NTP Servers|metel-ntpd-server-internet]] ====&lt;br /&gt;
- server package contains configuration as &amp;quot;Synchronization to two internet NTP servers&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==== [[NTPD#1. Standalone NTP server|metel-ntpd-standalone-server]] ====&lt;br /&gt;
- server package contains configuration as &amp;quot;Standalone NTP server&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. Install NTPD Package ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install ntpd&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Package Installing:&lt;br /&gt;
 Installing ntpd (4.2.8p9-9671.212083251) on root.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/ntpd_4.2.8p9-9671.212083251_all.ipk.&lt;br /&gt;
 Configuring ntpd.&lt;br /&gt;
&lt;br /&gt;
When the instalation is complete, start the NTP daemon by command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# /etc/init.d/S49ntp start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText= Every time the configuration file '''/etc/ntp.conf''' is changed, restart the service '''S49ntp''' by command '''/etc/init.d/S49ntp restart'''!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Examples ==&lt;br /&gt;
This section provides several examples of the '''/etc/ntp.conf''' configuration file.&lt;br /&gt;
&lt;br /&gt;
=== 1. Standalone NTP server ===&lt;br /&gt;
The following configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - No synchronization to internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command: &lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcar&lt;br /&gt;
  &lt;br /&gt;
 # create a local NTP server&lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. With Connetion to Remote NTP Servers ===&lt;br /&gt;
The example shows the optimal configuration for the Czech Republic. &lt;br /&gt;
&lt;br /&gt;
This configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - Synchronization to two internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File Content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcard&lt;br /&gt;
 &lt;br /&gt;
 server tik.cesnet.cz&lt;br /&gt;
 server tak.cesnet.cz&lt;br /&gt;
 &lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10 refid ILOG&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
 #end-of-file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Diagnostics ==&lt;br /&gt;
=== NTPQ ===&lt;br /&gt;
The '''ntpq''' utility program is used to query NTP servers which implement the recommended NTP mode 6 control message format about the current state and to request changes in that state.&lt;br /&gt;
&lt;br /&gt;
[http://doc.ntp.org/4.2.8p9/ntpq.html NTPQ Home Page]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre|text= root@iplog:~# watch ntpq -p -n&lt;br /&gt;
}}&lt;br /&gt;
NTPQ Parameters:&lt;br /&gt;
&lt;br /&gt;
: '''watch''' - Every 2s: ntpq -p -n&lt;br /&gt;
&lt;br /&gt;
: '''-p''' - Print current status&lt;br /&gt;
&lt;br /&gt;
: '''-n''' - Disable DNS resolving&lt;br /&gt;
&lt;br /&gt;
 Every 2s: ntpq -p -n                                        2019-08-01 10:00:12&lt;br /&gt;
 &lt;br /&gt;
      remote           refid      st t when poll reach   delay   offset  jitter&lt;br /&gt;
 ==============================================================================&lt;br /&gt;
  127.127.1.0     .ILOG.          10 l  41m   64    0    0.000    0.000   0.000&lt;br /&gt;
 +195.113.144.201 195.113.144.238  2 u   92  128  377   12.307    2.212   1.333&lt;br /&gt;
 *195.113.144.238 .GPS.            1 u   20  128  377   11.039    4.785   1.630&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This section is a copy from https://pthree.org/2013/11/05/real-life-ntp/.&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
&lt;br /&gt;
:    • '''remote''' – The remote server you wish to synchronize your clock with&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot; &amp;quot; Discarded as not valid. It is possible that you will be unable to communicate with the remote machine (it's not online), this time source is a &amp;quot;.LOCL.&amp;quot; refid time source, it's a high stratum server, or the remote server is using this computer as an NTP server.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;x&amp;quot; Discarded by the intersection algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;.&amp;quot; Discarded by table overflow (not used).&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;-&amp;quot; Discarded by the cluster algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;+&amp;quot; Included in the combined algorithm. This is a good candidate if the current server we are synchronizing with is discarded for any reason.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;#&amp;quot; Good remote server to be used as an alternative backup. This is only shown if you have more than 10 remote servers.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;*&amp;quot; The current system peer. The computer is using this remote server as its time source to synchronize the clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;o&amp;quot; Pulse per second (PPS) peer. This is generally used with GPS time sources, although any time source delivering a PPS will do. This tally code and the previous tally code &amp;quot;*&amp;quot; will not be displayed simultaneously.&lt;br /&gt;
&lt;br /&gt;
:    • '''refid''' – The upstream stratum to the remote server. For stratum 1 servers, this will be the stratum 0 source.&lt;br /&gt;
&lt;br /&gt;
:    • '''st''' – The stratum level, 0 through 16.&lt;br /&gt;
&lt;br /&gt;
:    • '''t''' –  The type of connection. &lt;br /&gt;
&lt;br /&gt;
:        ◦ l = local reference clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ u = unicast (most common)&lt;br /&gt;
&lt;br /&gt;
:        ◦ m = multicast&lt;br /&gt;
&lt;br /&gt;
:        ◦ b = broadcast&lt;br /&gt;
&lt;br /&gt;
:    • '''when''' – The last time when the server was queried for the time. Default is seconds, or &amp;quot;m&amp;quot; will be displayed for minutes, &amp;quot;h&amp;quot; for hours and &amp;quot;d&amp;quot; for days.&lt;br /&gt;
&lt;br /&gt;
:    • '''poll''' – How often the server is queried for the time, with a minimum of 8 seconds to a maximum of 36 hours. It's also displayed as a value from a power of two. Typically, it's between 64 seconds and 1024 seconds.&lt;br /&gt;
&lt;br /&gt;
:    • '''reach''' – This is an 8-bit left shift octal value that shows the success and failure rate of communicating with the remote server. Success means the bit is set, failure means the bit is not set. 377 is the highest value.&lt;br /&gt;
&lt;br /&gt;
:    • '''delay''' – This value is displayed in milliseconds, and shows the round trip time (RTT) of your computer communicating with the remote server.&lt;br /&gt;
&lt;br /&gt;
:    • '''offset''' –  This value is displayed in milliseconds, using root mean squares, and shows how far off your clock is from the reported time the server gave you. It can be positive or negative.&lt;br /&gt;
&lt;br /&gt;
:    • '''jitter''' – This number is an absolute value in milliseconds, showing the root mean squared deviation of your offsets.&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1013</id>
		<title>NTPD</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1013"/>
				<updated>2022-01-14T07:51:44Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= NTPD (Network Time Procokol Daemon) =&lt;br /&gt;
== Description ==&lt;br /&gt;
The '''NTPD''' program is an operating-system daemon that sets and maintains a computer system's time in synchronization with Internet-standard time servers. It is a complete implementation of the Network Time Protocol (NTP) version 4, but retains compatibility with versions 1, 2, and 3 as defined by RFC 1059, RFC 1119, and RFC 1305, respectively. ntpd performs most computations in 64-bit floating point arithmetic and uses 64-bit fixed point operations only when necessary to preserve the ultimate precision, about 232 picoseconds. While ordinary workstations and networks cannot achieve the ultimate precision as of 2015, future processors and networks may require it.&lt;br /&gt;
&lt;br /&gt;
== NTPD Installation ==&lt;br /&gt;
To install '''NTPD package''' simply use the following commands:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 1. Update List of Available Packages ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg update&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Update Process:&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/Packages.gz.&lt;br /&gt;
 Updated source 'base'.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/firmware/Packages.gz.&lt;br /&gt;
 Updated source 'firmware'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Choose one of the available packages ===&lt;br /&gt;
[[NTPD (Network Time Procokol Daemon)#Install NTPD Package|ntpd]]&lt;br /&gt;
- server package with linux default configuration&lt;br /&gt;
&lt;br /&gt;
==== [[NTPD (Network Time Procokol Daemon)#2. With Connetion to Remote NTP Servers|metel-ntpd-server-internet]] ====&lt;br /&gt;
- server package contains configuration as &amp;quot;Synchronization to two internet NTP servers&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==== [[NTPD (Network Time Procokol Daemon)#1. Standalone NTP server|metel-ntpd-standalone-server]] ====&lt;br /&gt;
- server package contains configuration as &amp;quot;Standalone NTP server&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. Install NTPD Package ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install ntpd&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Package Installing:&lt;br /&gt;
 Installing ntpd (4.2.8p9-9671.212083251) on root.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/ntpd_4.2.8p9-9671.212083251_all.ipk.&lt;br /&gt;
 Configuring ntpd.&lt;br /&gt;
&lt;br /&gt;
When the instalation is complete, start the NTP daemon by command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# /etc/init.d/S49ntp start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText= Every time the configuration file '''/etc/ntp.conf''' is changed, restart the service '''S49ntp''' by command '''/etc/init.d/S49ntp restart'''!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Examples ==&lt;br /&gt;
This section provides several examples of the '''/etc/ntp.conf''' configuration file.&lt;br /&gt;
&lt;br /&gt;
=== 1. Standalone NTP server ===&lt;br /&gt;
The following configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - No synchronization to internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command: &lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcar&lt;br /&gt;
  &lt;br /&gt;
 # create a local NTP server&lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. With Connetion to Remote NTP Servers ===&lt;br /&gt;
The example shows the optimal configuration for the Czech Republic. &lt;br /&gt;
&lt;br /&gt;
This configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - Synchronization to two internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File Content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcard&lt;br /&gt;
 &lt;br /&gt;
 server tik.cesnet.cz&lt;br /&gt;
 server tak.cesnet.cz&lt;br /&gt;
 &lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10 refid ILOG&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
 #end-of-file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Diagnostics ==&lt;br /&gt;
=== NTPQ ===&lt;br /&gt;
The '''ntpq''' utility program is used to query NTP servers which implement the recommended NTP mode 6 control message format about the current state and to request changes in that state.&lt;br /&gt;
&lt;br /&gt;
[http://doc.ntp.org/4.2.8p9/ntpq.html NTPQ Home Page]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre|text= root@iplog:~# watch ntpq -p -n&lt;br /&gt;
}}&lt;br /&gt;
NTPQ Parameters:&lt;br /&gt;
&lt;br /&gt;
: '''watch''' - Every 2s: ntpq -p -n&lt;br /&gt;
&lt;br /&gt;
: '''-p''' - Print current status&lt;br /&gt;
&lt;br /&gt;
: '''-n''' - Disable DNS resolving&lt;br /&gt;
&lt;br /&gt;
 Every 2s: ntpq -p -n                                        2019-08-01 10:00:12&lt;br /&gt;
 &lt;br /&gt;
      remote           refid      st t when poll reach   delay   offset  jitter&lt;br /&gt;
 ==============================================================================&lt;br /&gt;
  127.127.1.0     .ILOG.          10 l  41m   64    0    0.000    0.000   0.000&lt;br /&gt;
 +195.113.144.201 195.113.144.238  2 u   92  128  377   12.307    2.212   1.333&lt;br /&gt;
 *195.113.144.238 .GPS.            1 u   20  128  377   11.039    4.785   1.630&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This section is a copy from https://pthree.org/2013/11/05/real-life-ntp/.&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
&lt;br /&gt;
:    • '''remote''' – The remote server you wish to synchronize your clock with&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot; &amp;quot; Discarded as not valid. It is possible that you will be unable to communicate with the remote machine (it's not online), this time source is a &amp;quot;.LOCL.&amp;quot; refid time source, it's a high stratum server, or the remote server is using this computer as an NTP server.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;x&amp;quot; Discarded by the intersection algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;.&amp;quot; Discarded by table overflow (not used).&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;-&amp;quot; Discarded by the cluster algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;+&amp;quot; Included in the combined algorithm. This is a good candidate if the current server we are synchronizing with is discarded for any reason.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;#&amp;quot; Good remote server to be used as an alternative backup. This is only shown if you have more than 10 remote servers.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;*&amp;quot; The current system peer. The computer is using this remote server as its time source to synchronize the clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;o&amp;quot; Pulse per second (PPS) peer. This is generally used with GPS time sources, although any time source delivering a PPS will do. This tally code and the previous tally code &amp;quot;*&amp;quot; will not be displayed simultaneously.&lt;br /&gt;
&lt;br /&gt;
:    • '''refid''' – The upstream stratum to the remote server. For stratum 1 servers, this will be the stratum 0 source.&lt;br /&gt;
&lt;br /&gt;
:    • '''st''' – The stratum level, 0 through 16.&lt;br /&gt;
&lt;br /&gt;
:    • '''t''' –  The type of connection. &lt;br /&gt;
&lt;br /&gt;
:        ◦ l = local reference clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ u = unicast (most common)&lt;br /&gt;
&lt;br /&gt;
:        ◦ m = multicast&lt;br /&gt;
&lt;br /&gt;
:        ◦ b = broadcast&lt;br /&gt;
&lt;br /&gt;
:    • '''when''' – The last time when the server was queried for the time. Default is seconds, or &amp;quot;m&amp;quot; will be displayed for minutes, &amp;quot;h&amp;quot; for hours and &amp;quot;d&amp;quot; for days.&lt;br /&gt;
&lt;br /&gt;
:    • '''poll''' – How often the server is queried for the time, with a minimum of 8 seconds to a maximum of 36 hours. It's also displayed as a value from a power of two. Typically, it's between 64 seconds and 1024 seconds.&lt;br /&gt;
&lt;br /&gt;
:    • '''reach''' – This is an 8-bit left shift octal value that shows the success and failure rate of communicating with the remote server. Success means the bit is set, failure means the bit is not set. 377 is the highest value.&lt;br /&gt;
&lt;br /&gt;
:    • '''delay''' – This value is displayed in milliseconds, and shows the round trip time (RTT) of your computer communicating with the remote server.&lt;br /&gt;
&lt;br /&gt;
:    • '''offset''' –  This value is displayed in milliseconds, using root mean squares, and shows how far off your clock is from the reported time the server gave you. It can be positive or negative.&lt;br /&gt;
&lt;br /&gt;
:    • '''jitter''' – This number is an absolute value in milliseconds, showing the root mean squared deviation of your offsets.&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1012</id>
		<title>NTPD</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=NTPD&amp;diff=1012"/>
				<updated>2022-01-14T07:51:06Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= NTPD (Network Time Procokol Daemon) =&lt;br /&gt;
== Description ==&lt;br /&gt;
The '''NTPD''' program is an operating-system daemon that sets and maintains a computer system's time in synchronization with Internet-standard time servers. It is a complete implementation of the Network Time Protocol (NTP) version 4, but retains compatibility with versions 1, 2, and 3 as defined by RFC 1059, RFC 1119, and RFC 1305, respectively. ntpd performs most computations in 64-bit floating point arithmetic and uses 64-bit fixed point operations only when necessary to preserve the ultimate precision, about 232 picoseconds. While ordinary workstations and networks cannot achieve the ultimate precision as of 2015, future processors and networks may require it.&lt;br /&gt;
&lt;br /&gt;
== NTPD Installation ==&lt;br /&gt;
To install '''NTPD package''' simply use the following commands:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 1. Update List of Available Packages ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg update&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Update Process:&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/Packages.gz.&lt;br /&gt;
 Updated source 'base'.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/firmware/Packages.gz.&lt;br /&gt;
 Updated source 'firmware'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. Choose one of the available packages ===&lt;br /&gt;
==== [[NTPD (Network Time Procokol Daemon)#Install NTPD Package|ntpd]] ====&lt;br /&gt;
- server package with linux default configuration&lt;br /&gt;
&lt;br /&gt;
==== [[NTPD (Network Time Procokol Daemon)#2. With Connetion to Remote NTP Servers|metel-ntpd-server-internet]] ====&lt;br /&gt;
- server package contains configuration as &amp;quot;Synchronization to two internet NTP servers&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==== [[NTPD (Network Time Procokol Daemon)#1. Standalone NTP server|metel-ntpd-standalone-server]] ====&lt;br /&gt;
- server package contains configuration as &amp;quot;Standalone NTP server&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 3. Install NTPD Package ===&lt;br /&gt;
{{NotePre|text= root@iplog:~# opkg install ntpd&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Example of Package Installing:&lt;br /&gt;
 Installing ntpd (4.2.8p9-9671.212083251) on root.&lt;br /&gt;
 Downloading http://www.iplog.eu/opkg/base/ntpd_4.2.8p9-9671.212083251_all.ipk.&lt;br /&gt;
 Configuring ntpd.&lt;br /&gt;
&lt;br /&gt;
When the instalation is complete, start the NTP daemon by command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# /etc/init.d/S49ntp start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText= Every time the configuration file '''/etc/ntp.conf''' is changed, restart the service '''S49ntp''' by command '''/etc/init.d/S49ntp restart'''!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Examples ==&lt;br /&gt;
This section provides several examples of the '''/etc/ntp.conf''' configuration file.&lt;br /&gt;
&lt;br /&gt;
=== 1. Standalone NTP server ===&lt;br /&gt;
The following configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - No synchronization to internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command: &lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcar&lt;br /&gt;
  &lt;br /&gt;
 # create a local NTP server&lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 2. With Connetion to Remote NTP Servers ===&lt;br /&gt;
The example shows the optimal configuration for the Czech Republic. &lt;br /&gt;
&lt;br /&gt;
This configuration has the following features:&lt;br /&gt;
&lt;br /&gt;
: - Local NTP server with specified stratum 10&lt;br /&gt;
&lt;br /&gt;
: - Synchronization to two internet NTP servers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Editing Configuration File Command:&lt;br /&gt;
{{NotePre|text= root@iplog:~# vi /etc/ntp.conf&lt;br /&gt;
}}&lt;br /&gt;
File Content:&lt;br /&gt;
 restrict default&lt;br /&gt;
 #restrict source&lt;br /&gt;
 #interface listen wildcard&lt;br /&gt;
 &lt;br /&gt;
 server tik.cesnet.cz&lt;br /&gt;
 server tak.cesnet.cz&lt;br /&gt;
 &lt;br /&gt;
 server 127.127.1.0&lt;br /&gt;
 fudge 127.127.1.0 stratum 10 refid ILOG&lt;br /&gt;
 &lt;br /&gt;
 driftfile /tmp/ntp.drift&lt;br /&gt;
 #end-of-file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Diagnostics ==&lt;br /&gt;
=== NTPQ ===&lt;br /&gt;
The '''ntpq''' utility program is used to query NTP servers which implement the recommended NTP mode 6 control message format about the current state and to request changes in that state.&lt;br /&gt;
&lt;br /&gt;
[http://doc.ntp.org/4.2.8p9/ntpq.html NTPQ Home Page]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
{{NotePre|text= root@iplog:~# watch ntpq -p -n&lt;br /&gt;
}}&lt;br /&gt;
NTPQ Parameters:&lt;br /&gt;
&lt;br /&gt;
: '''watch''' - Every 2s: ntpq -p -n&lt;br /&gt;
&lt;br /&gt;
: '''-p''' - Print current status&lt;br /&gt;
&lt;br /&gt;
: '''-n''' - Disable DNS resolving&lt;br /&gt;
&lt;br /&gt;
 Every 2s: ntpq -p -n                                        2019-08-01 10:00:12&lt;br /&gt;
 &lt;br /&gt;
      remote           refid      st t when poll reach   delay   offset  jitter&lt;br /&gt;
 ==============================================================================&lt;br /&gt;
  127.127.1.0     .ILOG.          10 l  41m   64    0    0.000    0.000   0.000&lt;br /&gt;
 +195.113.144.201 195.113.144.238  2 u   92  128  377   12.307    2.212   1.333&lt;br /&gt;
 *195.113.144.238 .GPS.            1 u   20  128  377   11.039    4.785   1.630&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This section is a copy from https://pthree.org/2013/11/05/real-life-ntp/.&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
&lt;br /&gt;
:    • '''remote''' – The remote server you wish to synchronize your clock with&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot; &amp;quot; Discarded as not valid. It is possible that you will be unable to communicate with the remote machine (it's not online), this time source is a &amp;quot;.LOCL.&amp;quot; refid time source, it's a high stratum server, or the remote server is using this computer as an NTP server.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;x&amp;quot; Discarded by the intersection algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;.&amp;quot; Discarded by table overflow (not used).&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;-&amp;quot; Discarded by the cluster algorithm.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;+&amp;quot; Included in the combined algorithm. This is a good candidate if the current server we are synchronizing with is discarded for any reason.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;#&amp;quot; Good remote server to be used as an alternative backup. This is only shown if you have more than 10 remote servers.&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;*&amp;quot; The current system peer. The computer is using this remote server as its time source to synchronize the clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ &amp;quot;o&amp;quot; Pulse per second (PPS) peer. This is generally used with GPS time sources, although any time source delivering a PPS will do. This tally code and the previous tally code &amp;quot;*&amp;quot; will not be displayed simultaneously.&lt;br /&gt;
&lt;br /&gt;
:    • '''refid''' – The upstream stratum to the remote server. For stratum 1 servers, this will be the stratum 0 source.&lt;br /&gt;
&lt;br /&gt;
:    • '''st''' – The stratum level, 0 through 16.&lt;br /&gt;
&lt;br /&gt;
:    • '''t''' –  The type of connection. &lt;br /&gt;
&lt;br /&gt;
:        ◦ l = local reference clock&lt;br /&gt;
&lt;br /&gt;
:        ◦ u = unicast (most common)&lt;br /&gt;
&lt;br /&gt;
:        ◦ m = multicast&lt;br /&gt;
&lt;br /&gt;
:        ◦ b = broadcast&lt;br /&gt;
&lt;br /&gt;
:    • '''when''' – The last time when the server was queried for the time. Default is seconds, or &amp;quot;m&amp;quot; will be displayed for minutes, &amp;quot;h&amp;quot; for hours and &amp;quot;d&amp;quot; for days.&lt;br /&gt;
&lt;br /&gt;
:    • '''poll''' – How often the server is queried for the time, with a minimum of 8 seconds to a maximum of 36 hours. It's also displayed as a value from a power of two. Typically, it's between 64 seconds and 1024 seconds.&lt;br /&gt;
&lt;br /&gt;
:    • '''reach''' – This is an 8-bit left shift octal value that shows the success and failure rate of communicating with the remote server. Success means the bit is set, failure means the bit is not set. 377 is the highest value.&lt;br /&gt;
&lt;br /&gt;
:    • '''delay''' – This value is displayed in milliseconds, and shows the round trip time (RTT) of your computer communicating with the remote server.&lt;br /&gt;
&lt;br /&gt;
:    • '''offset''' –  This value is displayed in milliseconds, using root mean squares, and shows how far off your clock is from the reported time the server gave you. It can be positive or negative.&lt;br /&gt;
&lt;br /&gt;
:    • '''jitter''' – This number is an absolute value in milliseconds, showing the root mean squared deviation of your offsets.&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=Blocks_IPWatchdog&amp;diff=895</id>
		<title>Blocks IPWatchdog</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=Blocks_IPWatchdog&amp;diff=895"/>
				<updated>2020-05-21T04:17:29Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Description: ==&lt;br /&gt;
The IPWatchdog blocks are used to verify the availability of a remote IP address based on an ARP or ICMP query.&lt;br /&gt;
&lt;br /&gt;
[[Libraries for IEC 61131-3|Back to Libraries]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== IPWDG_ARP ===&lt;br /&gt;
Returns ARP ping status of a give IP ip address&lt;br /&gt;
&lt;br /&gt;
[[File:IPWDG_ARP.png]]&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
| colspan=&amp;quot;5&amp;quot; |[[Libraries for IEC 61131-3|Asynchronous interface]]&lt;br /&gt;
|-&lt;br /&gt;
|in&lt;br /&gt;
|IP_ADDR&lt;br /&gt;
|string&lt;br /&gt;
|&lt;br /&gt;
|IP address&lt;br /&gt;
|-&lt;br /&gt;
|in&lt;br /&gt;
|TMO_S&lt;br /&gt;
|int&lt;br /&gt;
|&lt;br /&gt;
|timeout in seconds&lt;br /&gt;
|-&lt;br /&gt;
|out&lt;br /&gt;
|Q&lt;br /&gt;
|bool&lt;br /&gt;
|&lt;br /&gt;
|status&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== IPWDG_ICMP ===&lt;br /&gt;
Returns ICMP ping status of a give ip address&lt;br /&gt;
&lt;br /&gt;
[[File:IPWDG_ARP.png]]&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
| colspan=&amp;quot;5&amp;quot; |[[Libraries for IEC 61131-3|Asynchronous interface]]&lt;br /&gt;
|-&lt;br /&gt;
|in&lt;br /&gt;
|IP_ADDR&lt;br /&gt;
|string&lt;br /&gt;
|&lt;br /&gt;
|IP address&lt;br /&gt;
|-&lt;br /&gt;
|in&lt;br /&gt;
|TMO_S&lt;br /&gt;
|int&lt;br /&gt;
|&lt;br /&gt;
|timeout in seconds&lt;br /&gt;
|-&lt;br /&gt;
|out&lt;br /&gt;
|Q&lt;br /&gt;
|bool&lt;br /&gt;
|&lt;br /&gt;
|status&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Block behavior:'''&lt;br /&gt;
&lt;br /&gt;
The pulse on EXEC triggers the IPWDG block. In the beginning a ICMP/ARP request is sent to the IP address. At the same time the BUSY output is changing the status of the log. 0 to 1, TMO_S running and the block is waiting for a response.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1. If a '''response is received''' during TMO_S, TMO_S it is reset. BUSY is set to log. 0, VALID is set to 1 (operation successful, output set) and Q is set to log. 1 (IP is available).&lt;br /&gt;
&lt;br /&gt;
2. If a '''response is not received''', BUSY remains in the log. 1 until TMO_S expires. After TMO_S expires BUSY goes to log.0, VALID goes to log.1 (operation successful, output set). Q remains in log. 0 (IP is not available).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Note:'''&lt;br /&gt;
'''EXEC''' should be set to a value greater than TMO_S to avoid unnecessary restarting when the block cycle is not completed and is waiting for TMO_S.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
GEN_PULSE generates a pulse every T#2s (2 seconds) to trigger the IPWDG block. During one cycle block it is waiting for an answer from the remote device (IP_ADDR) for TMO_S timer. If the remote device does not respond by this time, the output is set to log. 0. Otherwise, the output is set to log. 1.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''IPWDG_ICMP''' &lt;br /&gt;
&lt;br /&gt;
[[File:IPWDG_ICMP_Example.png]]&lt;br /&gt;
&lt;br /&gt;
'''IPWDG_ARP''' &lt;br /&gt;
&lt;br /&gt;
[[File:IPWDG_ARP_Example.png]]&lt;br /&gt;
&lt;br /&gt;
[[Libraries for IEC 61131-3|Back to Libraries]]&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=Sending_and_Receiving_SMS&amp;diff=894</id>
		<title>Sending and Receiving SMS</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=Sending_and_Receiving_SMS&amp;diff=894"/>
				<updated>2020-05-21T04:05:56Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Basic Overview ==&lt;br /&gt;
IPLOG-GAMA units with GSM / GPRS interface support receiving and sending of any SMS messages. Based on their content it is then possible to perform various tasks. The program logic is created by the user based on the IEC 61131-3 programming language. The [[METEL IEC 61131-3 IDE|METEL IEC 61131-3 IDE]] software is used for this purpose.&lt;br /&gt;
&lt;br /&gt;
SMS_TX/SMS_RX blocks are used for communication between the program and the user through the GSM network. It uses SMS messages to transmit and receive information.&lt;br /&gt;
&lt;br /&gt;
== Program Description ==&lt;br /&gt;
The program receives SMS messages based on SMS_RX function blocks, filters their content and source phone number. If the message was received from the correct number &amp;quot;Phone_Number&amp;quot; and contains the text &amp;quot;arm&amp;quot; or &amp;quot;disarm&amp;quot;, the output variable &amp;quot;arm_disarm&amp;quot; is set to log. 1 or 0.&lt;br /&gt;
The SMS_TX blocks sending the remote arm / disarm verification to the number from which the request was sent.&lt;br /&gt;
&lt;br /&gt;
== Programming ==&lt;br /&gt;
Create the program in METEL IEC 61131-3 IDE and upload it to the IPLOG.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:SMS_Example.png|600px]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Related Links: ==&lt;br /&gt;
How to create program: [http://wiki.iplog.eu/wiki/METEL_IEC_61131-3_IDE_Getting_Started Getting Started]&lt;br /&gt;
&lt;br /&gt;
Download: {{DownloadIEC61131-3}}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=SMS&amp;diff=893</id>
		<title>SMS</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=SMS&amp;diff=893"/>
				<updated>2020-05-21T03:57:06Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Description: ==&lt;br /&gt;
SMS_TX/SMS_RX blocks are used for communication between the program and the user through the GSM network. It uses SMS messages to transmit and receive information. &lt;br /&gt;
&lt;br /&gt;
[[Libraries for IEC 61131-3|Back to Libraries]]&lt;br /&gt;
&lt;br /&gt;
=== SMS_RX ===&lt;br /&gt;
Receive SMS messages.&lt;br /&gt;
&lt;br /&gt;
[[File:SMS_RX.png]]&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
| colspan=&amp;quot;5&amp;quot; |[[Libraries for IEC 61131-3|Asynchronous interface]]&lt;br /&gt;
|-&lt;br /&gt;
|out&lt;br /&gt;
|VALID&lt;br /&gt;
|bool&lt;br /&gt;
|&lt;br /&gt;
|indicates success operation and valid output&lt;br /&gt;
|-&lt;br /&gt;
|out&lt;br /&gt;
|FROM&lt;br /&gt;
|string&lt;br /&gt;
|&lt;br /&gt;
|source phone number&lt;br /&gt;
|-&lt;br /&gt;
|out&lt;br /&gt;
|TEXT&lt;br /&gt;
|string&lt;br /&gt;
|&lt;br /&gt;
|SMS content '''(ASCII)'''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== SMS_TX ===&lt;br /&gt;
Sends SMS messages.&lt;br /&gt;
&lt;br /&gt;
[[File:SMS_TX.png]]&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
| colspan=&amp;quot;5&amp;quot; |[[Libraries for IEC 61131-3|Asynchronous interface]]&lt;br /&gt;
|-&lt;br /&gt;
|in&lt;br /&gt;
|SEND&lt;br /&gt;
|bool r_edge&lt;br /&gt;
|&lt;br /&gt;
|rising edge starts new operation&lt;br /&gt;
|-&lt;br /&gt;
|in&lt;br /&gt;
|NUMBER&lt;br /&gt;
|string&lt;br /&gt;
|&lt;br /&gt;
|destination phone number&lt;br /&gt;
|-&lt;br /&gt;
|in&lt;br /&gt;
|TEXT&lt;br /&gt;
|string&lt;br /&gt;
|&lt;br /&gt;
|SMS content '''(ASCII)'''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Block behavior:'''&lt;br /&gt;
&lt;br /&gt;
'''SMS_RX''' - If a new incoming SMS is detected, a short pulse appears on the VALID output, the FROM and TEXT outputs are filled according to the SMS content.&lt;br /&gt;
&lt;br /&gt;
'''SMS_TX''' - If a rising edge is detected at the SEND input, an SMS message is sent to the phone number from NUMBER input and the text contains the text from the TEXT input.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Valid Phone Number Format ==&lt;br /&gt;
The '''NUMBER''' input is a STRING format, so the phone number is entered in single quotes.&lt;br /&gt;
&lt;br /&gt;
Example for Czech Republic: ''' '00420731523929' '''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''00''' - For international communication. According to the operator, it is possible to replace 00 with +, but not all countries support the + format. '''00 is recommended'''.&lt;br /&gt;
&lt;br /&gt;
'''420''' - International Code for Czech Republic. Use the international code for the country where the device is located.&lt;br /&gt;
&lt;br /&gt;
'''731523929''' - Phone number&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
'''SMS_RX'''&lt;br /&gt;
&lt;br /&gt;
Closing the bus0_001_re1 relay provided the SMS text is ON and has been received from Phone_Number.&lt;br /&gt;
&lt;br /&gt;
[[File:SMS_RX_Example.png]] &lt;br /&gt;
&lt;br /&gt;
'''SMS_TX'''&lt;br /&gt;
&lt;br /&gt;
Closing the tamper sends an SMS in the form &amp;quot;Door open&amp;quot; to the phone number Phone_Number.&lt;br /&gt;
&lt;br /&gt;
[[File:SMS_TX_Example.png]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Related links: ==&lt;br /&gt;
&lt;br /&gt;
Example: [[Sending and Receiving SMS | Sending and Receiving SMS]] &amp;lt;br&amp;gt;&lt;br /&gt;
Example: [https://www.metel.eu/en/newdesign/solutions?itemId=93 SMS Basic Example]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Libraries for IEC 61131-3|Back to Libraries]]&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=Welcome_to_IPLOG_wiki&amp;diff=846</id>
		<title>Welcome to IPLOG wiki</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=Welcome_to_IPLOG_wiki&amp;diff=846"/>
				<updated>2020-04-20T06:31:23Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The database which contains all public information about '''IPLOG-GAMA''' units and accessories.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
An IPLOG wiki is a webpage which is run using wiki software, known as a wiki engine. On this webpage, you can&lt;br /&gt;
&lt;br /&gt;
find all information which helps you to configure IPLOG-GAMA units and IO modules. All information contained have&lt;br /&gt;
&lt;br /&gt;
already been implemented. The pages will be constantly updated so Metel s.r.o. reserves the right for changes in information.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:IPLOGs.jpg|600px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== IPLOG-GAMA Overview ==&lt;br /&gt;
&lt;br /&gt;
*IPLOGs are Linux based PLCs with Support for Writing User Scripts&lt;br /&gt;
*IF Modules Support Modbus, M-BUS, RS485, RS232, 1-Wire and Other Standards&lt;br /&gt;
*IO Modules Support a Wide Variety of Analog I/O, Digital I/O and Relay Outputs&lt;br /&gt;
*Supported by IEC 61131-3 [[METEL IEC 61131-3 IDE]] and Graphical SIMULand GUI &lt;br /&gt;
*High Security is Assured by SSH, openVPN, SNMPv3 and Other Tools used by IT Experts&lt;br /&gt;
*Highly Durable Hardware with Integrated Overvoltage Protections&lt;br /&gt;
*Operating Range from −40°C to +70°C&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Mozilla_icon.png|16px]] '''[https://www.mozilla.org/cs/firefox/new/ Mozilla Firefox]''' has been verified for all functionality.&lt;br /&gt;
&lt;br /&gt;
{{Tip|TipText=How to '''get started''' can be found in the &amp;lt;span style=&amp;quot;font-size:15px;&amp;quot;&amp;gt; '''[[Configuration]]''' &amp;lt;/span&amp;gt;  section.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
More information about '''METEL s.r.o.''' products can be found on the following links:&lt;br /&gt;
&lt;br /&gt;
[http://www.metel.eu www.metel.eu]&lt;br /&gt;
&lt;br /&gt;
[https://www.youtube.com/channel/UCwvuGBqu01laE2mEqNsr28A www.youtube.com]&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=File:Mozilla_icon.png&amp;diff=845</id>
		<title>File:Mozilla icon.png</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=File:Mozilla_icon.png&amp;diff=845"/>
				<updated>2020-04-20T06:23:04Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=Welcome_to_IPLOG_wiki&amp;diff=844</id>
		<title>Welcome to IPLOG wiki</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=Welcome_to_IPLOG_wiki&amp;diff=844"/>
				<updated>2020-04-20T06:17:30Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The database which contains all public information about '''IPLOG-GAMA''' units and accessories.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
An IPLOG wiki is a webpage which is run using wiki software, known as a wiki engine. On this webpage, you can&lt;br /&gt;
&lt;br /&gt;
find all information which helps you to configure IPLOG-GAMA units and IO modules. All information contained have&lt;br /&gt;
&lt;br /&gt;
already been implemented. The pages will be constantly updated so Metel s.r.o. reserves the right for changes in information.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:IPLOGs.jpg|600px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== IPLOG-GAMA Overview ==&lt;br /&gt;
&lt;br /&gt;
*IPLOGs are Linux based PLCs with Support for Writing User Scripts&lt;br /&gt;
*IF Modules Support Modbus, M-BUS, RS485, RS232, 1-Wire and Other Standards&lt;br /&gt;
*IO Modules Support a Wide Variety of Analog I/O, Digital I/O and Relay Outputs&lt;br /&gt;
*Supported by IEC 61131-3 [[METEL IEC 61131-3 IDE]] and Graphical SIMULand GUI &lt;br /&gt;
*High Security is Assured by SSH, openVPN, SNMPv3 and Other Tools used by IT Experts&lt;br /&gt;
*Highly Durable Hardware with Integrated Overvoltage Protections&lt;br /&gt;
*Operating Range from −40°C to +70°C&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Recommendation: [https://www.mozilla.org/cs/firefox/new/ Mozilla Firefox]''' has been verified for all functionality.&lt;br /&gt;
&lt;br /&gt;
{{Tip|TipText=How to '''get started''' can be found in the &amp;lt;span style=&amp;quot;font-size:15px;&amp;quot;&amp;gt; '''[[Configuration]]''' &amp;lt;/span&amp;gt;  section.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
More information about '''METEL s.r.o.''' products can be found on the following links:&lt;br /&gt;
&lt;br /&gt;
[http://www.metel.eu www.metel.eu]&lt;br /&gt;
&lt;br /&gt;
[https://www.youtube.com/channel/UCwvuGBqu01laE2mEqNsr28A www.youtube.com]&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=IF-15&amp;diff=843</id>
		<title>IF-15</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=IF-15&amp;diff=843"/>
				<updated>2020-04-17T04:48:59Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Modbus Registers ===&lt;br /&gt;
Below is a list of available MODBUS registers. The same register numbers are also used by the MIOS-2 protocol.&lt;br /&gt;
&lt;br /&gt;
=== Modbus Read / Write (0x17) Function ===&lt;br /&gt;
METEL IO modules have implemented the MODBUS function (0x17) Read/Write of Multiple registers. Typically it is required to have two separate requests (and responses) for:&lt;br /&gt;
&lt;br /&gt;
1. Writing of outputs via MODBUS function (0x16) Writing Multiple Registers&lt;br /&gt;
&lt;br /&gt;
2. Reading of inputs via MODBUS function (0x03) Read Holding Registers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This requires a total of 4 frames to be sent over MODBUS. If using 0x17 function only one request is needed for the reading and writing of outputs. This requires a total of 2 frames to be sent over MODBUS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Default Settings of Communication ===&lt;br /&gt;
Device ID: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
Baudrate: 115 200 &amp;lt;br /&amp;gt;&lt;br /&gt;
Parity: None &amp;lt;br /&amp;gt;&lt;br /&gt;
Data bits: 8 &amp;lt;br /&amp;gt;&lt;br /&gt;
Stop bits: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText=&lt;br /&gt;
The MODBUS address is the same as the address of the main device of which the IF module is part.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- MODBUS &amp;quot;IF-15(G) States of Inputs&amp;quot; registers table --&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|- style=&amp;quot;font-size: 17px;&amp;quot;&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; | Subject !! style=&amp;quot;width: 110px;&amp;quot; | Channel !! style=&amp;quot;width: 30px;&amp;quot; | Type !! style=&amp;quot;width: 30px;&amp;quot; | R/W !! style=&amp;quot;width: 230px;&amp;quot; | Value !! style=&amp;quot;width: 60px;&amp;quot; | Offset&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;5&amp;quot; style=&amp;quot;width: 90px;&amp;quot; | &amp;lt;span style=&amp;quot;font-size: 17px;&amp;quot;&amp;gt; '''IF-15(G) &amp;lt;br /&amp;gt; States of &amp;lt;br /&amp;gt; Inputs''' &amp;lt;/span&amp;gt; &lt;br /&gt;
|| Open Collector 1 || DO#33 || bit || RW || rowspan=&amp;quot;4&amp;quot; | 0 = inactive &amp;lt;br /&amp;gt; 1 = active || 4033&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 120px;&amp;quot; | Open Collector 2 || DO#34 || bit || RW || 4034&lt;br /&gt;
|-&lt;br /&gt;
| Open Collector 3 || DO#35 || bit || RW || 4035&lt;br /&gt;
|-&lt;br /&gt;
| Open Collector 4 || DO#36 || bit || RW || 4036&lt;br /&gt;
|-&lt;br /&gt;
| Outputs || DI#33 - DI#48 || u16 || R || 0x0000 - 0x000F || &lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=IF-14&amp;diff=842</id>
		<title>IF-14</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=IF-14&amp;diff=842"/>
				<updated>2020-04-17T04:48:20Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Modbus Registers ===&lt;br /&gt;
Below is a list of available MODBUS registers. The same register numbers are also used by the MIOS-2 protocol.&lt;br /&gt;
&lt;br /&gt;
=== Modbus Read / Write (0x17) Function ===&lt;br /&gt;
METEL IO modules have implemented the MODBUS function (0x17) Read/Write of Multiple registers. Typically it is required to have two separate requests (and responses) for:&lt;br /&gt;
&lt;br /&gt;
1. Writing of outputs via MODBUS function (0x16) Writing Multiple Registers&lt;br /&gt;
&lt;br /&gt;
2. Reading of inputs via MODBUS function (0x03) Read Holding Registers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This requires a total of 4 frames to be sent over MODBUS. If using 0x17 function only one request is needed for the reading and writing of outputs. This requires a total of 2 frames to be sent over MODBUS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Default Settings of Communication ===&lt;br /&gt;
Device ID: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
Baudrate: 115 200 &amp;lt;br /&amp;gt;&lt;br /&gt;
Parity: None &amp;lt;br /&amp;gt;&lt;br /&gt;
Data bits: 8 &amp;lt;br /&amp;gt;&lt;br /&gt;
Stop bits: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText=&lt;br /&gt;
The MODBUS address is the same as the address of the main device of which the IF module is part.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- MODBUS &amp;quot;IF-14G States of Inputs&amp;quot; registers table --&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|- style=&amp;quot;font-size: 17px;&amp;quot;&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; | Subject !! style=&amp;quot;width: 110px;&amp;quot; | Channel !! style=&amp;quot;width: 30px;&amp;quot; | Type !! style=&amp;quot;width: 30px;&amp;quot; | R/W !! style=&amp;quot;width: 230px;&amp;quot; | Value !! style=&amp;quot;width: 60px;&amp;quot; | Offset&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;5&amp;quot; style=&amp;quot;width: 90px;&amp;quot; | &amp;lt;span style=&amp;quot;font-size: 17px;&amp;quot;&amp;gt; '''IF-14G &amp;lt;br /&amp;gt; States of &amp;lt;br /&amp;gt; Inputs''' &amp;lt;/span&amp;gt; &lt;br /&gt;
|| Digital Input 1 || DI#33 || bit || R || rowspan=&amp;quot;4&amp;quot; | 0 = inactive &amp;lt;br /&amp;gt; 1 = active || 3033&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 120px;&amp;quot; | Digital Input 2 || DI#34 || bit || R || 3034&lt;br /&gt;
|-&lt;br /&gt;
| Digital Input 3 || DI#35 || bit || R || 3035&lt;br /&gt;
|-&lt;br /&gt;
| Digital Input 4 || DI#36 || bit || R || 3036&lt;br /&gt;
|-&lt;br /&gt;
| Inputs || DI#33 - DI#48 || u16 || R || 0x0000 - 0x000F || &lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=IF-12&amp;diff=841</id>
		<title>IF-12</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=IF-12&amp;diff=841"/>
				<updated>2020-04-17T04:47:26Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Modbus Registers ===&lt;br /&gt;
Below is a list of available MODBUS registers. The same register numbers are also used by the MIOS-2 protocol.&lt;br /&gt;
&lt;br /&gt;
=== Modbus Read / Write (0x17) Function ===&lt;br /&gt;
METEL IO modules have implemented the MODBUS function (0x17) Read/Write of Multiple registers. Typically it is required to have two separate requests (and responses) for:&lt;br /&gt;
&lt;br /&gt;
1. Writing of outputs via MODBUS function (0x16) Writing Multiple Registers&lt;br /&gt;
&lt;br /&gt;
2. Reading of inputs via MODBUS function (0x03) Read Holding Registers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This requires a total of 4 frames to be sent over MODBUS. If using 0x17 function only one request is needed for the reading and writing of outputs. This requires a total of 2 frames to be sent over MODBUS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Default Settings of Communication ===&lt;br /&gt;
Device ID: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
Baudrate: 115 200 &amp;lt;br /&amp;gt;&lt;br /&gt;
Parity: None &amp;lt;br /&amp;gt;&lt;br /&gt;
Data bits: 8 &amp;lt;br /&amp;gt;&lt;br /&gt;
Stop bits: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText=&lt;br /&gt;
The MODBUS address is the same as the address of the main device of which the IF module is part.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- MODBUS &amp;quot;IF-12 States of Inputs&amp;quot; registers table --&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|- style=&amp;quot;font-size: 17px;&amp;quot;&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; | Subject !! style=&amp;quot;width: 110px;&amp;quot; | Channel !! style=&amp;quot;width: 30px;&amp;quot; | Type !! style=&amp;quot;width: 30px;&amp;quot; | R/W !! style=&amp;quot;width: 230px;&amp;quot; | Value !! style=&amp;quot;width: 60px;&amp;quot; | Offset&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;9&amp;quot; style=&amp;quot;width: 90px;&amp;quot; | &amp;lt;span style=&amp;quot;font-size: 17px;&amp;quot;&amp;gt; '''IF-12 &amp;lt;br /&amp;gt; States of &amp;lt;br /&amp;gt; Inputs''' &amp;lt;/span&amp;gt; &lt;br /&gt;
|| Balanced Input 1 (bin) || DI#33 || bit || R || rowspan=&amp;quot;4&amp;quot; | 0 = inactive &amp;lt;br /&amp;gt; 1 = active || 3033&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 120px;&amp;quot; | Balanced Input 2 (bin) || DI#34 || bit || R || 3034&lt;br /&gt;
|-&lt;br /&gt;
| Balanced Input 3 (bin)|| DI#35 || u16 || R || 3035&lt;br /&gt;
|-&lt;br /&gt;
| Balanced Input 4 (bin)|| DI#36 || u16 || R || 3036&lt;br /&gt;
|-&lt;br /&gt;
| Balanced Input 1 || AI#33 || u16 || R || rowspan=&amp;quot;4&amp;quot; | 1000 = 1000Ω &amp;lt;br /&amp;gt; 0 = 0Ω || 5033&lt;br /&gt;
|-&lt;br /&gt;
| Balanced Input 2 || AI#34 || u16 || R || 5034&lt;br /&gt;
|-&lt;br /&gt;
| Balanced Input 3 || AI#35 || u16 || R || 5035&lt;br /&gt;
|-&lt;br /&gt;
| Balanced Input 4 || AI#36 || u16 || R || 5036&lt;br /&gt;
|-&lt;br /&gt;
| Inputs || DI#33 - DI#48 || u16 || R || 0x0000 - 0x000F || &lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=IF-12&amp;diff=840</id>
		<title>IF-12</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=IF-12&amp;diff=840"/>
				<updated>2020-04-17T04:47:08Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Modbus Registers ===&lt;br /&gt;
Below is a list of available MODBUS registers. The same register numbers are also used by the MIOS-2 protocol.&lt;br /&gt;
&lt;br /&gt;
=== Modbus Read / Write (0x17) Function ===&lt;br /&gt;
METEL IO modules have implemented the MODBUS function (0x17) Read/Write of Multiple registers. Typically it is required to have two separate requests (and responses) for:&lt;br /&gt;
&lt;br /&gt;
1. Writing of outputs via MODBUS function (0x16) Writing Multiple Registers&lt;br /&gt;
&lt;br /&gt;
2. Reading of inputs via MODBUS function (0x03) Read Holding Registers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This requires a total of 4 frames to be sent over MODBUS. If using 0x17 function only one request is needed for the reading and writing of outputs. This requires a total of 2 frames to be sent over MODBUS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Default Settings of Communication ===&lt;br /&gt;
Device ID: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
Baudrate: 115 200 &amp;lt;br /&amp;gt;&lt;br /&gt;
Parity: None &amp;lt;br /&amp;gt;&lt;br /&gt;
Data bits: 8 &amp;lt;br /&amp;gt;&lt;br /&gt;
Stop bits: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText=&lt;br /&gt;
The MODBUS address is the same as the address of the main device of which the IF module is part.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- MODBUS &amp;quot;IF-12 States of Inputs&amp;quot; registers table --&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|- style=&amp;quot;font-size: 17px;&amp;quot;&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; | Subject !! style=&amp;quot;width: 110px;&amp;quot; | Channel !! style=&amp;quot;width: 30px;&amp;quot; | Type !! style=&amp;quot;width: 30px;&amp;quot; | R/W !! style=&amp;quot;width: 230px;&amp;quot; | Value !! style=&amp;quot;width: 60px;&amp;quot; | Offset&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;8&amp;quot; style=&amp;quot;width: 90px;&amp;quot; | &amp;lt;span style=&amp;quot;font-size: 17px;&amp;quot;&amp;gt; '''IF-12 &amp;lt;br /&amp;gt; States of &amp;lt;br /&amp;gt; Inputs''' &amp;lt;/span&amp;gt; &lt;br /&gt;
|| Balanced Input 1 (bin) || DI#33 || bit || R || rowspan=&amp;quot;4&amp;quot; | 0 = inactive &amp;lt;br /&amp;gt; 1 = active || 3033&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 120px;&amp;quot; | Balanced Input 2 (bin) || DI#34 || bit || R || 3034&lt;br /&gt;
|-&lt;br /&gt;
| Balanced Input 3 (bin)|| DI#35 || u16 || R || 3035&lt;br /&gt;
|-&lt;br /&gt;
| Balanced Input 4 (bin)|| DI#36 || u16 || R || 3036&lt;br /&gt;
|-&lt;br /&gt;
| Balanced Input 1 || AI#33 || u16 || R || rowspan=&amp;quot;4&amp;quot; | 1000 = 1000Ω &amp;lt;br /&amp;gt; 0 = 0Ω || 5033&lt;br /&gt;
|-&lt;br /&gt;
| Balanced Input 2 || AI#34 || u16 || R || 5034&lt;br /&gt;
|-&lt;br /&gt;
| Balanced Input 3 || AI#35 || u16 || R || 5035&lt;br /&gt;
|-&lt;br /&gt;
| Balanced Input 4 || AI#36 || u16 || R || 5036&lt;br /&gt;
|-&lt;br /&gt;
| Inputs || DI#33 - DI#48 || u16 || R || 0x0000 - 0x000F || &lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=IF-11&amp;diff=839</id>
		<title>IF-11</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=IF-11&amp;diff=839"/>
				<updated>2020-04-17T04:46:04Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Modbus Registers ===&lt;br /&gt;
Below is a list of available MODBUS registers. The same register numbers are also used by the MIOS-2 protocol.&lt;br /&gt;
&lt;br /&gt;
=== Modbus Read / Write (0x17) Function ===&lt;br /&gt;
METEL IO modules have implemented the MODBUS function (0x17) Read/Write of Multiple registers. Typically it is required to have two separate requests (and responses) for:&lt;br /&gt;
&lt;br /&gt;
1. Writing of outputs via MODBUS function (0x16) Writing Multiple Registers&lt;br /&gt;
&lt;br /&gt;
2. Reading of inputs via MODBUS function (0x03) Read Holding Registers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This requires a total of 4 frames to be sent over MODBUS. If using 0x17 function only one request is needed for the reading and writing of outputs. This requires a total of 2 frames to be sent over MODBUS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Default Settings of Communication ===&lt;br /&gt;
Device ID: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
Baudrate: 115 200 &amp;lt;br /&amp;gt;&lt;br /&gt;
Parity: None &amp;lt;br /&amp;gt;&lt;br /&gt;
Data bits: 8 &amp;lt;br /&amp;gt;&lt;br /&gt;
Stop bits: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText=&lt;br /&gt;
The MODBUS address is the same as the address of the main device of which the IF module is part.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- MODBUS &amp;quot;IF-11 States of Inputs&amp;quot; registers table --&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|- style=&amp;quot;font-size: 17px;&amp;quot;&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; | Subject !! style=&amp;quot;width: 110px;&amp;quot; | Channel !! style=&amp;quot;width: 30px;&amp;quot; | Type !! style=&amp;quot;width: 30px;&amp;quot; | R/W !! style=&amp;quot;width: 230px;&amp;quot; | Value !! style=&amp;quot;width: 60px;&amp;quot; | Offset&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;5&amp;quot; style=&amp;quot;width: 90px;&amp;quot; | &amp;lt;span style=&amp;quot;font-size: 17px;&amp;quot;&amp;gt; '''IF-11 &amp;lt;br /&amp;gt; States of &amp;lt;br /&amp;gt; Inputs''' &amp;lt;/span&amp;gt; &lt;br /&gt;
|| Balanced Input 1 (bin) || DI#33 || bit || R || rowspan=&amp;quot;2&amp;quot; | 0 = inactive &amp;lt;br /&amp;gt; 1 = active || 3033&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 120px;&amp;quot; | Balanced Input 2 (bin) || DI#34 || bit || R || 3034&lt;br /&gt;
|-&lt;br /&gt;
| Balanced Input 1 || AI#33 || u16 || R || rowspan=&amp;quot;2&amp;quot; | 1000 = 1000Ω &amp;lt;br /&amp;gt; 0 = 0Ω || 5033&lt;br /&gt;
|-&lt;br /&gt;
| Balanced Input 2 || AI#34 || u16 || R || 5034&lt;br /&gt;
|-&lt;br /&gt;
| Inputs || DI#33 - DI#48 || u16 || R || 0x0000 - 0x0003 || &lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=IF-05&amp;diff=838</id>
		<title>IF-05</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=IF-05&amp;diff=838"/>
				<updated>2020-04-17T04:42:35Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Modbus Registers ===&lt;br /&gt;
Below is a list of available MODBUS registers. The same register numbers are also used by the MIOS-2 protocol.&lt;br /&gt;
&lt;br /&gt;
=== Modbus Read / Write (0x17) Function ===&lt;br /&gt;
METEL IO modules have implemented the MODBUS function (0x17) Read/Write of Multiple registers. Typically it is required to have two separate requests (and responses) for:&lt;br /&gt;
&lt;br /&gt;
1. Writing of outputs via MODBUS function (0x16) Writing Multiple Registers&lt;br /&gt;
&lt;br /&gt;
2. Reading of inputs via MODBUS function (0x03) Read Holding Registers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This requires a total of 4 frames to be sent over MODBUS. If using 0x17 function only one request is needed for the reading and writing of outputs. This requires a total of 2 frames to be sent over MODBUS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Default Settings of Communication ===&lt;br /&gt;
Device ID: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
Baudrate: 115 200 &amp;lt;br /&amp;gt;&lt;br /&gt;
Parity: None &amp;lt;br /&amp;gt;&lt;br /&gt;
Data bits: 8 &amp;lt;br /&amp;gt;&lt;br /&gt;
Stop bits: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText=&lt;br /&gt;
The MODBUS address is the same as the address of the main device of which the IF module is part.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- MODBUS &amp;quot;IF-05 States of Inputs&amp;quot; registers table --&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|- style=&amp;quot;font-size: 17px;&amp;quot;&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; | Subject !! style=&amp;quot;width: 110px;&amp;quot; | Channel !! style=&amp;quot;width: 30px;&amp;quot; | Type !! style=&amp;quot;width: 30px;&amp;quot; | R/W !! style=&amp;quot;width: 230px;&amp;quot; | Value !! style=&amp;quot;width: 60px;&amp;quot; | Offset&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;5&amp;quot; style=&amp;quot;width: 90px;&amp;quot; | &amp;lt;span style=&amp;quot;font-size: 17px;&amp;quot;&amp;gt; '''IF-05 &amp;lt;br /&amp;gt; States of &amp;lt;br /&amp;gt; Inputs''' &amp;lt;/span&amp;gt; &lt;br /&gt;
|| Balanced Input 1 (bin) || DI#33 || bit || R || rowspan=&amp;quot;2&amp;quot; | 0 = inactive &amp;lt;br /&amp;gt; 1 = active || 3033&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 120px;&amp;quot; | Balanced Input 2 (bin) || DI#34 || bit || R || 3034&lt;br /&gt;
|-&lt;br /&gt;
| Balanced Input 1 || AI#33 || u16 || R || rowspan=&amp;quot;2&amp;quot; | 1000 = 1000Ω &amp;lt;br /&amp;gt; 0 = 0Ω || 5033&lt;br /&gt;
|-&lt;br /&gt;
| Balanced Input 2 || AI#34 || u16 || R || 5034&lt;br /&gt;
|-&lt;br /&gt;
| Inputs || DI#33 - DI#48 || u16 || R || 0x0000 - 0x0003 || &lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=IF-05&amp;diff=837</id>
		<title>IF-05</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=IF-05&amp;diff=837"/>
				<updated>2020-04-17T04:42:12Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Modbus Registers ===&lt;br /&gt;
Below is a list of available MODBUS registers. The same register numbers are also used by the MIOS-2 protocol.&lt;br /&gt;
&lt;br /&gt;
=== Modbus Read / Write (0x17) Function ===&lt;br /&gt;
METEL IO modules have implemented the MODBUS function (0x17) Read/Write of Multiple registers. Typically it is required to have two separate requests (and responses) for:&lt;br /&gt;
&lt;br /&gt;
1. Writing of outputs via MODBUS function (0x16) Writing Multiple Registers&lt;br /&gt;
&lt;br /&gt;
2. Reading of inputs via MODBUS function (0x03) Read Holding Registers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This requires a total of 4 frames to be sent over MODBUS. If using 0x17 function only one request is needed for the reading and writing of outputs. This requires a total of 2 frames to be sent over MODBUS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Default Settings of Communication ===&lt;br /&gt;
Device ID: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
Baudrate: 115 200 &amp;lt;br /&amp;gt;&lt;br /&gt;
Parity: None &amp;lt;br /&amp;gt;&lt;br /&gt;
Data bits: 8 &amp;lt;br /&amp;gt;&lt;br /&gt;
Stop bits: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText=&lt;br /&gt;
The MODBUS address is the same as the address of the main device of which the IF module is part.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- MODBUS &amp;quot;IF-05 States of Inputs&amp;quot; registers table --&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|- style=&amp;quot;font-size: 17px;&amp;quot;&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; | Subject !! style=&amp;quot;width: 110px;&amp;quot; | Channel !! style=&amp;quot;width: 30px;&amp;quot; | Type !! style=&amp;quot;width: 30px;&amp;quot; | R/W !! style=&amp;quot;width: 230px;&amp;quot; | Value !! style=&amp;quot;width: 60px;&amp;quot; | Offset&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;4&amp;quot; style=&amp;quot;width: 90px;&amp;quot; | &amp;lt;span style=&amp;quot;font-size: 17px;&amp;quot;&amp;gt; '''IF-05 &amp;lt;br /&amp;gt; States of &amp;lt;br /&amp;gt; Inputs''' &amp;lt;/span&amp;gt; &lt;br /&gt;
|| Balanced Input 1 (bin) || DI#33 || bit || R || rowspan=&amp;quot;2&amp;quot; | 0 = inactive &amp;lt;br /&amp;gt; 1 = active || 3033&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 120px;&amp;quot; | Balanced Input 2 (bin) || DI#34 || bit || R || 3034&lt;br /&gt;
|-&lt;br /&gt;
| Balanced Input 1 || AI#33 || u16 || R || rowspan=&amp;quot;2&amp;quot; | 1000 = 1000Ω &amp;lt;br /&amp;gt; 0 = 0Ω || 5033&lt;br /&gt;
|-&lt;br /&gt;
| Balanced Input 2 || AI#34 || u16 || R || 5034&lt;br /&gt;
|-&lt;br /&gt;
| Inputs || DI#33 - DI#48 || u16 || R || 0x0000 - 0x0003 || &lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=IF-15&amp;diff=836</id>
		<title>IF-15</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=IF-15&amp;diff=836"/>
				<updated>2020-04-17T04:36:01Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Modbus Registers ===&lt;br /&gt;
Below is a list of available MODBUS registers. The same register numbers are also used by the MIOS-2 protocol.&lt;br /&gt;
&lt;br /&gt;
=== Modbus Read / Write (0x17) Function ===&lt;br /&gt;
METEL IO modules have implemented the MODBUS function (0x17) Read/Write of Multiple registers. Typically it is required to have two separate requests (and responses) for:&lt;br /&gt;
&lt;br /&gt;
1. Writing of outputs via MODBUS function (0x16) Writing Multiple Registers&lt;br /&gt;
&lt;br /&gt;
2. Reading of inputs via MODBUS function (0x03) Read Holding Registers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This requires a total of 4 frames to be sent over MODBUS. If using 0x17 function only one request is needed for the reading and writing of outputs. This requires a total of 2 frames to be sent over MODBUS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Default Settings of Communication ===&lt;br /&gt;
Device ID: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
Baudrate: 115 200 &amp;lt;br /&amp;gt;&lt;br /&gt;
Parity: None &amp;lt;br /&amp;gt;&lt;br /&gt;
Data bits: 8 &amp;lt;br /&amp;gt;&lt;br /&gt;
Stop bits: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText=&lt;br /&gt;
The MODBUS address is the same as the address of the main device of which the IF module is part.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- MODBUS &amp;quot;IF-15(G) States of Inputs&amp;quot; registers table --&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|- style=&amp;quot;font-size: 17px;&amp;quot;&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; | Subject !! style=&amp;quot;width: 110px;&amp;quot; | Channel !! style=&amp;quot;width: 30px;&amp;quot; | Type !! style=&amp;quot;width: 30px;&amp;quot; | R/W !! style=&amp;quot;width: 230px;&amp;quot; | Value !! style=&amp;quot;width: 60px;&amp;quot; | Offset&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;4&amp;quot; style=&amp;quot;width: 90px;&amp;quot; | &amp;lt;span style=&amp;quot;font-size: 17px;&amp;quot;&amp;gt; '''IF-15(G) &amp;lt;br /&amp;gt; States of &amp;lt;br /&amp;gt; Inputs''' &amp;lt;/span&amp;gt; &lt;br /&gt;
|| Open Collector 1 || DO#33 || bit || RW || rowspan=&amp;quot;4&amp;quot; | 0 = inactive &amp;lt;br /&amp;gt; 1 = active || 4033&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 120px;&amp;quot; | Open Collector 2 || DO#34 || bit || RW || 4034&lt;br /&gt;
|-&lt;br /&gt;
| Open Collector 3 || DO#35 || bit || RW || 4035&lt;br /&gt;
|-&lt;br /&gt;
| Open Collector 4 || DO#36 || bit || RW || 4036&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=IF-15&amp;diff=835</id>
		<title>IF-15</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=IF-15&amp;diff=835"/>
				<updated>2020-04-17T04:33:30Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: Created page with &amp;quot;=== Modbus Registers === Below is a list of available MODBUS registers. The same register numbers are also used by the MIOS-2 protocol.  === Modbus Read / Write (0x17) Functio...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Modbus Registers ===&lt;br /&gt;
Below is a list of available MODBUS registers. The same register numbers are also used by the MIOS-2 protocol.&lt;br /&gt;
&lt;br /&gt;
=== Modbus Read / Write (0x17) Function ===&lt;br /&gt;
METEL IO modules have implemented the MODBUS function (0x17) Read/Write of Multiple registers. Typically it is required to have two separate requests (and responses) for:&lt;br /&gt;
&lt;br /&gt;
1. Writing of outputs via MODBUS function (0x16) Writing Multiple Registers&lt;br /&gt;
&lt;br /&gt;
2. Reading of inputs via MODBUS function (0x03) Read Holding Registers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This requires a total of 4 frames to be sent over MODBUS. If using 0x17 function only one request is needed for the reading and writing of outputs. This requires a total of 2 frames to be sent over MODBUS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Default Settings of Communication ===&lt;br /&gt;
Device ID: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
Baudrate: 115 200 &amp;lt;br /&amp;gt;&lt;br /&gt;
Parity: None &amp;lt;br /&amp;gt;&lt;br /&gt;
Data bits: 8 &amp;lt;br /&amp;gt;&lt;br /&gt;
Stop bits: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText=&lt;br /&gt;
The MODBUS address is the same as the address of the main device of which the IF module is part.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- MODBUS &amp;quot;IF-15(G) States of Inputs&amp;quot; registers table --&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|- style=&amp;quot;font-size: 17px;&amp;quot;&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; | Subject !! style=&amp;quot;width: 110px;&amp;quot; | Channel !! style=&amp;quot;width: 30px;&amp;quot; | Type !! style=&amp;quot;width: 30px;&amp;quot; | R/W !! style=&amp;quot;width: 230px;&amp;quot; | Value !! style=&amp;quot;width: 60px;&amp;quot; | Offset&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;4&amp;quot; style=&amp;quot;width: 90px;&amp;quot; | &amp;lt;span style=&amp;quot;font-size: 17px;&amp;quot;&amp;gt; '''IF-15(G) &amp;lt;br /&amp;gt; States of &amp;lt;br /&amp;gt; Inputs''' &amp;lt;/span&amp;gt; &lt;br /&gt;
|| Open Collector 1 || DO#33 || bit || R || rowspan=&amp;quot;4&amp;quot; | 0 = inactive &amp;lt;br /&amp;gt; 1 = active || 3033&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 120px;&amp;quot; | Open Collector 2 || DO#34 || bit || R || 3034&lt;br /&gt;
|-&lt;br /&gt;
| Open Collector 3 || DO#35 || bit || R || 3035&lt;br /&gt;
|-&lt;br /&gt;
| Open Collector 4 || DO#36 || bit || R || 3036&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=Configuration&amp;diff=834</id>
		<title>Configuration</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=Configuration&amp;diff=834"/>
				<updated>2020-04-17T04:28:28Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{ycgu-cooltable-3&lt;br /&gt;
|title-left='''General'''&lt;br /&gt;
|title-center=&lt;br /&gt;
|title-right=&lt;br /&gt;
|content-left=&lt;br /&gt;
'''IPLOG-GAMA Tutorials'''&lt;br /&gt;
* [[QuickStart | QuickStart]]&lt;br /&gt;
* [[Firmware_Upgrade | Firmware Upgrade]]&lt;br /&gt;
* [[Reset_to_factory | Reset to Factory Default]]&lt;br /&gt;
* [[Backup_and_restore | Backup and Restore]]&lt;br /&gt;
* [[Recovery_mode | Recovery Mode]]&lt;br /&gt;
* [[MetelVPN_Support | MetelVPN Support]]&lt;br /&gt;
* [[OpenVPN | OpenVPN]]&lt;br /&gt;
* [[PIN_Check | PIN Check]]&lt;br /&gt;
* [[GPRS_Data | GPRS Data (IPLOG-G2)]]&lt;br /&gt;
* [[LTE_Data | LTE Data (IPLOG-G3)]]&lt;br /&gt;
* [[Users_Passwords | Users / Passwords]]&lt;br /&gt;
* [[NTPD | NTPD (Network Time Protokol)]]&lt;br /&gt;
* [[GRAFANA | GRAFANA]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|content-center=&lt;br /&gt;
&lt;br /&gt;
'''MODBUS registers'''&lt;br /&gt;
&lt;br /&gt;
* [[Buses | Buses ]]&lt;br /&gt;
&lt;br /&gt;
IO Modules&lt;br /&gt;
* [[AI4.1 | AI4.1 ]]&lt;br /&gt;
* [[AI8.1 | AI8.1 ]]&lt;br /&gt;
* [[AO8.1 | AO8.1 ]]&lt;br /&gt;
* [[BI8.1 | BI8.1 ]]&lt;br /&gt;
* [[BO8.1 | BO8.1 ]]&lt;br /&gt;
* [[DI8.1 | DI8.1 ]]&lt;br /&gt;
* [[PP8.1 | PP8.1 ]]&lt;br /&gt;
* [[RE8.1 | RE8.1 ]]&lt;br /&gt;
* [[RE8.2 | RE8.2 ]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
IF Modules&lt;br /&gt;
* [[IF-05 | IF-05]]&lt;br /&gt;
* [[IF-11 | IF-11]]&lt;br /&gt;
* [[IF-12 | IF-12]]&lt;br /&gt;
* [[IF-14 | IF-14G]]&lt;br /&gt;
* [[IF-15 | IF-15(G)]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|content-right=&lt;br /&gt;
'''Management tools'''&lt;br /&gt;
* [[Console_SSH | Console SSH (TCP/IP or USB)]]&lt;br /&gt;
* [[SIMULand.v4 | SIMULand.v4]]&lt;br /&gt;
* [[MIB_files | MIB Files]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Programming'''&lt;br /&gt;
* [[METEL_IEC_61131-3_IDE| METEL IEC 61131-3 IDE Basic Overview]]&lt;br /&gt;
* [[METEL IEC 61131-3 IDE Getting Started | METEL IEC 61131-3 IDE Getting Started]]&lt;br /&gt;
* [[Libraries for IEC 61131-3 | METEL IEC 61131-3 IDE Block Library]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''EXAMPLES - METEL IEC 61131-3 IDE'''&lt;br /&gt;
* [[Temperature and Humidity control | Temperature and Humidity Control ]]&lt;br /&gt;
* [[Switch Digital Inputs Reading | Switch Digital Inputs Reading ]]&lt;br /&gt;
* [[Sending and Receiving SMS | Sending and Receiving SMS ]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=IF-14&amp;diff=833</id>
		<title>IF-14</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=IF-14&amp;diff=833"/>
				<updated>2020-04-17T04:27:54Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Modbus Registers ===&lt;br /&gt;
Below is a list of available MODBUS registers. The same register numbers are also used by the MIOS-2 protocol.&lt;br /&gt;
&lt;br /&gt;
=== Modbus Read / Write (0x17) Function ===&lt;br /&gt;
METEL IO modules have implemented the MODBUS function (0x17) Read/Write of Multiple registers. Typically it is required to have two separate requests (and responses) for:&lt;br /&gt;
&lt;br /&gt;
1. Writing of outputs via MODBUS function (0x16) Writing Multiple Registers&lt;br /&gt;
&lt;br /&gt;
2. Reading of inputs via MODBUS function (0x03) Read Holding Registers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This requires a total of 4 frames to be sent over MODBUS. If using 0x17 function only one request is needed for the reading and writing of outputs. This requires a total of 2 frames to be sent over MODBUS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Default Settings of Communication ===&lt;br /&gt;
Device ID: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
Baudrate: 115 200 &amp;lt;br /&amp;gt;&lt;br /&gt;
Parity: None &amp;lt;br /&amp;gt;&lt;br /&gt;
Data bits: 8 &amp;lt;br /&amp;gt;&lt;br /&gt;
Stop bits: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText=&lt;br /&gt;
The MODBUS address is the same as the address of the main device of which the IF module is part.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- MODBUS &amp;quot;IF-14G States of Inputs&amp;quot; registers table --&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|- style=&amp;quot;font-size: 17px;&amp;quot;&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; | Subject !! style=&amp;quot;width: 110px;&amp;quot; | Channel !! style=&amp;quot;width: 30px;&amp;quot; | Type !! style=&amp;quot;width: 30px;&amp;quot; | R/W !! style=&amp;quot;width: 230px;&amp;quot; | Value !! style=&amp;quot;width: 60px;&amp;quot; | Offset&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;4&amp;quot; style=&amp;quot;width: 90px;&amp;quot; | &amp;lt;span style=&amp;quot;font-size: 17px;&amp;quot;&amp;gt; '''IF-14G &amp;lt;br /&amp;gt; States of &amp;lt;br /&amp;gt; Inputs''' &amp;lt;/span&amp;gt; &lt;br /&gt;
|| Digital Input 1 || DI#33 || bit || R || rowspan=&amp;quot;4&amp;quot; | 0 = inactive &amp;lt;br /&amp;gt; 1 = active || 3033&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 120px;&amp;quot; | Digital Input 2 || DI#34 || bit || R || 3034&lt;br /&gt;
|-&lt;br /&gt;
| Digital Input 3 || DI#35 || bit || R || 3035&lt;br /&gt;
|-&lt;br /&gt;
| Digital Input 4 || DI#36 || bit || R || 3036&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=IF-14&amp;diff=832</id>
		<title>IF-14</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=IF-14&amp;diff=832"/>
				<updated>2020-04-17T04:26:48Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Modbus Registers ===&lt;br /&gt;
Below is a list of available MODBUS registers. The same register numbers are also used by the MIOS-2 protocol.&lt;br /&gt;
&lt;br /&gt;
=== Modbus Read / Write (0x17) Function ===&lt;br /&gt;
METEL IO modules have implemented the MODBUS function (0x17) Read/Write of Multiple registers. Typically it is required to have two separate requests (and responses) for:&lt;br /&gt;
&lt;br /&gt;
1. Writing of outputs via MODBUS function (0x16) Writing Multiple Registers&lt;br /&gt;
&lt;br /&gt;
2. Reading of inputs via MODBUS function (0x03) Read Holding Registers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This requires a total of 4 frames to be sent over MODBUS. If using 0x17 function only one request is needed for the reading and writing of outputs. This requires a total of 2 frames to be sent over MODBUS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Default Settings of Communication ===&lt;br /&gt;
Device ID: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
Baudrate: 115 200 &amp;lt;br /&amp;gt;&lt;br /&gt;
Parity: None &amp;lt;br /&amp;gt;&lt;br /&gt;
Data bits: 8 &amp;lt;br /&amp;gt;&lt;br /&gt;
Stop bits: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText=&lt;br /&gt;
The MODBUS address is the same as the address of the main device of which the IF module is part.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- MODBUS &amp;quot;IF-14 States of Inputs&amp;quot; registers table --&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|- style=&amp;quot;font-size: 17px;&amp;quot;&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; | Subject !! style=&amp;quot;width: 110px;&amp;quot; | Channel !! style=&amp;quot;width: 30px;&amp;quot; | Type !! style=&amp;quot;width: 30px;&amp;quot; | R/W !! style=&amp;quot;width: 230px;&amp;quot; | Value !! style=&amp;quot;width: 60px;&amp;quot; | Offset&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;4&amp;quot; style=&amp;quot;width: 90px;&amp;quot; | &amp;lt;span style=&amp;quot;font-size: 17px;&amp;quot;&amp;gt; '''IF-14/14G &amp;lt;br /&amp;gt; States of &amp;lt;br /&amp;gt; Inputs''' &amp;lt;/span&amp;gt; &lt;br /&gt;
|| Digital Input 1 || DI#33 || bit || R || rowspan=&amp;quot;4&amp;quot; | 0 = inactive &amp;lt;br /&amp;gt; 1 = active || 3033&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 120px;&amp;quot; | Digital Input 2 || DI#34 || bit || R || 3034&lt;br /&gt;
|-&lt;br /&gt;
| Digital Input 3 || DI#35 || bit || R || 3035&lt;br /&gt;
|-&lt;br /&gt;
| Digital Input 4 || DI#36 || bit || R || 3036&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=IF-14&amp;diff=831</id>
		<title>IF-14</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=IF-14&amp;diff=831"/>
				<updated>2020-04-17T04:26:12Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Modbus Registers ===&lt;br /&gt;
Below is a list of available MODBUS registers. The same register numbers are also used by the MIOS-2 protocol.&lt;br /&gt;
&lt;br /&gt;
=== Modbus Read / Write (0x17) Function ===&lt;br /&gt;
METEL IO modules have implemented the MODBUS function (0x17) Read/Write of Multiple registers. Typically it is required to have two separate requests (and responses) for:&lt;br /&gt;
&lt;br /&gt;
1. Writing of outputs via MODBUS function (0x16) Writing Multiple Registers&lt;br /&gt;
&lt;br /&gt;
2. Reading of inputs via MODBUS function (0x03) Read Holding Registers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This requires a total of 4 frames to be sent over MODBUS. If using 0x17 function only one request is needed for the reading and writing of outputs. This requires a total of 2 frames to be sent over MODBUS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Default Settings of Communication ===&lt;br /&gt;
Device ID: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
Baudrate: 115 200 &amp;lt;br /&amp;gt;&lt;br /&gt;
Parity: None &amp;lt;br /&amp;gt;&lt;br /&gt;
Data bits: 8 &amp;lt;br /&amp;gt;&lt;br /&gt;
Stop bits: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText=&lt;br /&gt;
The MODBUS address is the same as the address of the main device of which the IF module is part.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- MODBUS &amp;quot;IF-14 States of Inputs&amp;quot; registers table --&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|- style=&amp;quot;font-size: 17px;&amp;quot;&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; | Subject !! style=&amp;quot;width: 110px;&amp;quot; | Channel !! style=&amp;quot;width: 30px;&amp;quot; | Type !! style=&amp;quot;width: 30px;&amp;quot; | R/W !! style=&amp;quot;width: 230px;&amp;quot; | Value !! style=&amp;quot;width: 60px;&amp;quot; | Offset&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;4&amp;quot; style=&amp;quot;width: 90px;&amp;quot; | &amp;lt;span style=&amp;quot;font-size: 17px;&amp;quot;&amp;gt; '''IF-14 &amp;lt;br /&amp;gt; States of &amp;lt;br /&amp;gt; Inputs''' &amp;lt;/span&amp;gt; &lt;br /&gt;
|| Digital Input 1 || DI#33 || bit || R || rowspan=&amp;quot;4&amp;quot; | 0 = inactive &amp;lt;br /&amp;gt; 1 = active || 3033&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 120px;&amp;quot; | Digital Input 2 || DI#34 || bit || R || 3034&lt;br /&gt;
|-&lt;br /&gt;
| Digital Input 3 || DI#35 || bit || R || 3035&lt;br /&gt;
|-&lt;br /&gt;
| Digital Input 4 || DI#36 || bit || R || 3036&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	<entry>
		<id>http://wiki.iplog.eu/index.php?title=IF-14&amp;diff=830</id>
		<title>IF-14</title>
		<link rel="alternate" type="text/html" href="http://wiki.iplog.eu/index.php?title=IF-14&amp;diff=830"/>
				<updated>2020-04-17T04:24:50Z</updated>
		
		<summary type="html">&lt;p&gt;Z013: Created page with &amp;quot;=== Modbus Registers === Below is a list of available MODBUS registers. The same register numbers are also used by the MIOS-2 protocol.  === Modbus Read / Write (0x17) Functio...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Modbus Registers ===&lt;br /&gt;
Below is a list of available MODBUS registers. The same register numbers are also used by the MIOS-2 protocol.&lt;br /&gt;
&lt;br /&gt;
=== Modbus Read / Write (0x17) Function ===&lt;br /&gt;
METEL IO modules have implemented the MODBUS function (0x17) Read/Write of Multiple registers. Typically it is required to have two separate requests (and responses) for:&lt;br /&gt;
&lt;br /&gt;
1. Writing of outputs via MODBUS function (0x16) Writing Multiple Registers&lt;br /&gt;
&lt;br /&gt;
2. Reading of inputs via MODBUS function (0x03) Read Holding Registers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This requires a total of 4 frames to be sent over MODBUS. If using 0x17 function only one request is needed for the reading and writing of outputs. This requires a total of 2 frames to be sent over MODBUS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Default Settings of Communication ===&lt;br /&gt;
Device ID: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
Baudrate: 115 200 &amp;lt;br /&amp;gt;&lt;br /&gt;
Parity: None &amp;lt;br /&amp;gt;&lt;br /&gt;
Data bits: 8 &amp;lt;br /&amp;gt;&lt;br /&gt;
Stop bits: 1 &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Note|NoteText=&lt;br /&gt;
The MODBUS address is the same as the address of the main device of which the IF module is part.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- MODBUS &amp;quot;IF-14 States of Inputs&amp;quot; registers table --&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|- style=&amp;quot;font-size: 17px;&amp;quot;&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; | Subject !! style=&amp;quot;width: 110px;&amp;quot; | Channel !! style=&amp;quot;width: 30px;&amp;quot; | Type !! style=&amp;quot;width: 30px;&amp;quot; | R/W !! style=&amp;quot;width: 230px;&amp;quot; | Value !! style=&amp;quot;width: 60px;&amp;quot; | Offset&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;4&amp;quot; style=&amp;quot;width: 90px;&amp;quot; | &amp;lt;span style=&amp;quot;font-size: 17px;&amp;quot;&amp;gt; '''IF-14 &amp;lt;br /&amp;gt; States of &amp;lt;br /&amp;gt; Inputs''' &amp;lt;/span&amp;gt; &lt;br /&gt;
|| Digital Input 1 || DI#33 || bit || R || rowspan=&amp;quot;4&amp;quot; | 0 = inactive &amp;lt;br /&amp;gt; 1 = active || 3033&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 120px;&amp;quot; | Digital Input 2 || DI#34 || bit || R || 3034&lt;br /&gt;
|-&lt;br /&gt;
| Digital Input 3 || DI#35 || u16 || R || 3035&lt;br /&gt;
|-&lt;br /&gt;
| Digital Input 4 || DI#36 || u16 || R || 3036&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Z013</name></author>	</entry>

	</feed>