###################
4PointX IoT Gateway
###################






.. raw:: html

	<p>4PointX IoT Gateway device is used to collect data from Plant / Shop floor and send to 4PointX IIoT Workbench. The device is based on Raspberry Pi and contains necessary interfaces (RS-485, CAN, ETH etc.) for collecting and transferring data.</p>

.. raw:: html

	<img src='/docs/_static/media/Edge IoT Gateway.jpg'>



.. raw:: html

	<p>The following configuration is required to be performed on 4PointX IoT Gateway before it can be used for onboarding data.</p>

#. Change hostname
	#. Use the following naming convention for hostname: 4px-<app>-<site>-<plant>-<function>-<#> (e.g., 4px-ems-jsw_vjnr-crm1-pltcm-1)
	#. Set the hostname. 
		.. raw:: html
		
			<p>Linux command:</p>
		
		.. code-block:: bash
		
			vi /etc/hostname
		
		
	
	
	
#. Assign IP address
	#. Assign IP and reboot the device. Linux commands:
		.. code-block:: bash
		
			sudo vi /etc/network/interfaces #Comment pre-up line. See below for example setting.
			sudo reboot
		
		
		.. raw:: html
		
			<p>Example Settings:</p>
		
		.. code-block:: bash
		
			auto eth0
			iface eth0 inet static
			  address 192.168.1.42
			    netmask 255.255.255.0
			      gateway 192.168.1.1
			        dns-nameservers 1.1.1.1, 8.8.8.8
		
		
	
	
	
#. Sample setting: 
	.. raw:: html
	
		<img src='/docs/_static/media/ip setting.png'>
	
#. After reboot, confirm that the IP is set. Also note the MAC Address. Linux command:
	#. baship addr
	#. Sample output: 
		.. raw:: html
		
			<img src='/docs/_static/media/ip addr.png'>
		
	
	
	
#. Set the host
	#. Change the “management_host” and “data_brokers” parameters in settings.json file to include the appropriate 4PointX IIoT Workbench server IP and Ports, and reboot the device.
		.. code-block:: bash
		
			sudo vi /home/4px/4px.firmware/config/settings.json
			sudo reboot
		
		
		.. raw:: html
		
			<p>Example Settings:</p>
		
		.. code-block:: json
		
			{
			    "management_host": "34.9.188.179:443",
			    "data_brokers": [
			        "34.9.188.179:9092"
			    ],
			    "data_directory": "/home/4px/4px.data",
			    "module": "gateway"
			}
		
		
	
	
	



.. raw:: html

	<p>With these steps the device would be ready to be used for onboarding data.</p>



.. raw:: html

	<p>The following ports are relevant for the operation, configuration, and data communication of the 4PointX IoT Gateway. Ensure they are <strong>open</strong> on the firewall/router to allow seamless device-to-server connectivity.</p>

.. list-table::
	:header-rows: 1

	* - Port
	  - Protocol
	  - Direction
	  - Purpose
	  - Access
	  - Application  Protocol
	* - 443
	  - TCP
	  - Outbound
	  - For Configuration update
	  - Open
	  - HTTPS
	* - 9092
	  - TCP
	  - Outbound
	  - For Data streaming
	  - Open
	  - HTTPS
	* - 22
	  - TCP
	  - Inbound
	  - For Troubleshooting
	  - Open
	  - SSH




.. raw:: html

	<p>4PointX IoT Gateway can be deployed to collect data from various levels in a Plant network. At each level the Gateway is connected to a network Switch which in turn is connected to a Firewall. Port 443 and 9092 are required to be open in the Firewall for Outbound communication from 4PointX IoT Gateway (device) to 4PointX IIoT Workbench (server).</p>

.. raw:: html

	<p>The following diagram depicts the network deployment architecture.</p>

.. raw:: html

	<img src='/docs/_static/media/4PointX Network Architecture.png'>



.. list-table::
	:header-rows: 1

	* - Issue
	  - Symptoms
	  - Possible Causes
	  - Resolution Steps
	* - No Data Reaching Platform
	  - Dashboard shows no data
	  - Incorrect settings.json host or brokerNetwork issues (firewall, DNS)Kafka broker issue
	  - Verify IPs/ports in settings.jsonTest connectivity: ping, telnetCheck logs: tail -f /home/4px/4px.firmware/logs/<file-name>
	* - Time Drift / Incorrect Time
	  - Wrong timestampsDashboard shows future/past data
	  - Clock unsynchronized
	  - Run time sync script:python3 /home/4px/4px.firmware/time-sync.py Check system time:timedatectlEnsure timezone:sudo timedatectl set-timezone Asia/Kolkata


.. raw:: html

	<hr/>

.. toctree::