IBH Link IoT:Startup operations: Difference between revisions

From IBHsoftec Wiki English
Jump to navigation Jump to search
mNo edit summary
 
Line 2: Line 2:


The '''IBH Link IoT''' is designed for DIN rail mount:
The '''IBH Link IoT''' is designed for DIN rail mount:


[[Image:IBH_Link_IoT_rail_mount.png|600px]]
[[Image:IBH_Link_IoT_rail_mount.png|600px]]
Line 31: Line 32:
Default IP Address configuration:
Default IP Address configuration:
{| class="wikitable"
{| class="wikitable"
|-
|-
! Level !! Port !! Address
! Level !! Port !! Address
|-
|-
| Management level|| Port 1 || Host name: '''ibhlink-iot-<serial number>'''
 
| Management level|| Port 1 || Host name: '''ibhlink-iot_<serial number>'''
|-
|-
| Control level || Port 2 - 4 || '''192.168.1.14'''
| Control level || Port 2 - 4 || '''192.168.1.14'''
|}
|}
Line 58: Line 63:


[[Image:IBH_Link_IoT_Controlt_Level.png|772px]]
[[Image:IBH_Link_IoT_Controlt_Level.png|772px]]


== Assigment Token ==
== Assigment Token ==


After logging into the '''TeamViewer IoT Management Console''' the '''Assigment Token''' can be copied:
After logging in to the “”'[https://web.teamviewer.com/ TeamViewer Remote]''' page, once the '''[https://www.teamviewer.com/en-us/global/support/knowledge-base/teamviewer-remote/deployment/mass-deployment-user-guide/create-a-rollout-configuration-6-10/?msockid=386e3fc5ca1366d4128528eccb3667e9 rollout configuration]''' has been completed, the '''Assignment Token''' or the '''ID''' can be copied:
 
[[Image:IBH_Link_IoT_TW_Assigment_token_Menue.png|227px]]
 
[[Image:IBH_Link_IoT_TW_Assigment_token_Copy.png|701px]]
 
The token must be copied into the '''Assigment Token'' field and assigned:
 
[[Image:IBH_Link_IoT_TW_Assigment_token_Assign.png|637px]]
 
== IBH Net IoT Tray ==
 
The required '''IBH Link IoT''' driver is available free of charge on our homepage:
'''[http://download.ibhsoftec.com/neutral/IBHNet-IoT-Setup.exe IBH Link IoT Driver]'''
 
[[Image:IBH_Link_IoT_Start_Menue_Eng.png|310px]]
 
 
== Agents ==


With the menu item '''Agents''' the TeamViewer connections to the '''IBH Link IoT''' can be created:
[[Image:IBH_Link_IoT_Rollout-Setup.png|1200px]]


[[Image:IBH_Link_IoT_Tray_Agents_Eng.png|298px]]
The '''token''' or '''ID''' is then copied into the '''Assignment Token''' field and assigned:


[[Image:IBH_Link_IoT_Assign_Token_ID.png|1074px]]


The display name can be freely chosen. The '''TeamViewer ID''' to be used for each device can be seen in the web interface:
== IBH Net IoT Port Forwarding  ==
Once the '''IBH Link Iot''' has been connected, TeamViewer '''Port Forwarding''' can be set up:


[[Image:IBH_Link_IoT_Connect_Device.png|1324px]]


[[Image:IBH_Link_IoT_Short_Cuts.png|871px]]
Once the allocation in '''IBH Link IoT''' has been completed::


[[Image:IBH_Link_IoT_Remote_App_Control.png|1349px]]


== Connection setup ==
The '''TemaViewer''' port forwarding can be started as follows:


Via the IBH Link IoT Tray the connection can now be established:
[[Image:IBH_Link_IoT_Port_Forwarding.png|1262px]]


[[Image:IBH_Link_IoT_Tray_Connect.png|304px]]
In the example, port forwarding has been set up for a Remote Desktop connection (port '''3389''') and for accessing a Siemens PLC via the IBH Link S7++ on port '''102'''.<br>


As TIAPortal and Step®7 do not allow the entry of '''localhost (127.0.0.1)''', a free IP address must be assigned, which is then entered as the access address for online access.<br>
Example: Path in '''S5/S7AI for Windows®''':


[[Image:IBH_Link_IoT_Connection.png|633px]]
[[Image:IBH_Link_IoT_S57AI_Online.png|869px]]


After successful connection establishment, the IBH Link IoT appears as WireGuard tunnel in the Network Adapters:
<big>'''Important Note:'''</big><br>
If the '''TeamViewer VPN Tunnel''' is successfully activated, it will appear under '''Network Connections'''


[[Image:IBH_Link_IoT_WireGuard_Tunnel.png|264]]
[[Image:IBH_Link_IoT_TeamViewerTUN.png|320px]]


From now on, all controls that are connected via the control level of the IBH Link IoT are accessible via TeamViewer.
The properties of the '''TCP/IPv4''' address must remain set to '''DHCP'''!

Latest revision as of 11:36, 30 September 2026

Mounting and Connection

The IBH Link IoT is designed for DIN rail mount:



ATTENTION!

The IBH Link IoT requires a 12 - 36V DC power supply. Higher voltages may destroy the device. Pay attention to polarity.

Power supply: 24VDC / 0,2A


Configuration of the IP addresses

The administration can be made with a recent web browser over the Ethernet port 1 by using the host name http://ibhlink-iot_<serial number> (f.i. http://ibhlink-iot_000161)

or over the ports 2-4 by entering the default IP Address 192.168.1.14

On the PC the IBHNet-Iot driver is required. The Driver is available free of charge.

Default IP Address configuration:

Level Port Address
Management level Port 1 Host name: ibhlink-iot_<serial number>
Control level Port 2 - 4 192.168.1.14

Default Login:

admin

admin

Network: Management Level

Network configuration for Port 1 (Management level respectively Supervision Level):

Network: Control Level

Network configuration for Port 2 - 4 (Control Level respectively Machine Level):


Assigment Token

After logging in to the “”'TeamViewer Remote page, once the rollout configuration has been completed, the Assignment Token or the ID can be copied:

The token or ID is then copied into the Assignment Token field and assigned:

IBH Net IoT Port Forwarding

Once the IBH Link Iot has been connected, TeamViewer Port Forwarding can be set up:

Once the allocation in IBH Link IoT has been completed::

The TemaViewer port forwarding can be started as follows:

In the example, port forwarding has been set up for a Remote Desktop connection (port 3389) and for accessing a Siemens PLC via the IBH Link S7++ on port 102.

As TIAPortal and Step®7 do not allow the entry of localhost (127.0.0.1), a free IP address must be assigned, which is then entered as the access address for online access.
Example: Path in S5/S7AI for Windows®:

Important Note:
If the TeamViewer VPN Tunnel is successfully activated, it will appear under Network Connections

The properties of the TCP/IPv4 address must remain set to DHCP!