Difference between revisions of "2410"
(created) |
(+client timeout) |
||
| Line 1: | Line 1: | ||
[[File:2410.jpg|thumb|Model 2410]] | [[File:2410.jpg|thumb|Model 2410]] | ||
Model 2410 is a compact open-frame module that interfaces 48 general-purpose TTL/CMOS compatible digital input/output (DIO) signals to Ethernet. It features edge detection, PWM output mode and other functions that offload work from the host computer in measurement and control applications. | Model 2410 is a compact open-frame module that interfaces 48 general-purpose TTL/CMOS compatible digital input/output (DIO) signals to Ethernet. It features edge detection, PWM output mode and other functions that offload work from the host computer in measurement and control applications. | ||
| + | |||
| + | ==Timeouts== | ||
| + | ''I disabled the 2410 communication watchdog timer but the connection still times out after 5 minutes. Why is this happening?'' | ||
| + | |||
| + | The 2410's communication watchdog is disabled by sending <code>wto 0</code> to it. However, most telnet clients also have their own inactivity timer, which is set to a default interval (typically 5 minutes). Consequently, the telnet client will independently close the connection when the session is idle for longer than its own timer interval. To resolve this, you must reconfigure your telnet client to use a different interval. | ||
Revision as of 10:00, 26 May 2016
Model 2410 is a compact open-frame module that interfaces 48 general-purpose TTL/CMOS compatible digital input/output (DIO) signals to Ethernet. It features edge detection, PWM output mode and other functions that offload work from the host computer in measurement and control applications.
Timeouts
I disabled the 2410 communication watchdog timer but the connection still times out after 5 minutes. Why is this happening?
The 2410's communication watchdog is disabled by sending wto 0 to it. However, most telnet clients also have their own inactivity timer, which is set to a default interval (typically 5 minutes). Consequently, the telnet client will independently close the connection when the session is idle for longer than its own timer interval. To resolve this, you must reconfigure your telnet client to use a different interval.