Emerson Exchange 365
Search
User
Site
Search
User
Replies
6 replies
Subscribers
5476 subscribers
Views
31414 views
Users
0 members are here
Recent DeltaV Community Connect Discussions
Zohaib Jahan
14 Dec 2022 5:20 PM
How to show Data from AMS to DeltaV Live
9 Replies
Zohaib Jahan
13 Dec 2022 7:08 PM
Layout and DisplaySet settings L1,2,3,4 hierarchy?
1 Reply
gennarogiura
11 Dec 2022 10:10 AM
Delta V 15 release date?
2 Replies
Cedric Dawnhawk
7 Dec 2022 11:14 PM
DeltaV Operate delay in starting
2 Replies
Invalid String
7 Dec 2022 10:00 PM
System Time on Operator Station
3 Replies
<
>
Similar Posts
Extract the logs on an SLS with telnet
Fwd: Net work binding when using 4 NIC
Emerson Exchange 2019 DeltaV Controller and I/O Hardware - Product Update sessions
Be sure to get to the DeltaV roadmap sessions
Control Studio Phantom session issue
Share
Fwd: Telnet session with DeltaV Controller
From:
krishna sen
<
[email protected]
>
Date: Sun, May 10, 2020 at 12:19 PM
Subject: Telnet session with DeltaV Controller
To: <
[email protected]
>
Dear all
Please let me know how can i open a telnet link with MQ controller and look in the Hardware event log ?
6 Replies
Hassan.hameed
10 May 2020 9:06 AM
You can go through diagnostic and select the required controller and right click select telnet after that follow list appear
krishna sen
10 May 2020 9:40 AM
Many many thanks for reply. Can I open telnet link with controller through command prompt ? If yes then what is the linking procedure.
Hassan.hameed
10 May 2020 9:53 AM
In reply to
krishna sen
:
No you cannot only from deltav explorer diagnostic can access to the telnet
krishna sen
10 May 2020 10:21 AM
Thx
Lun.Raznik
11 May 2020 3:41 PM
In reply to
krishna sen
:
telnet IP should work. For example, if IP of the controller is 10.4.0.10, then telnet 10.4.0.10 will open session to the controller.
Jason.Brumfield
16 May 2020 3:44 PM
as an adder, if you have redundant controllers, you have to drill down to the standby in diagnostics to remote the non active controller, each one has it's own telnet logs.