User's Manual
Table Of Contents
- Chapter 1 General Information
- Chapter 2 System Setup
- Chapter 3 System Tuning
- Chapter 4 Windows CE .NET 4.2
- Figure 4.1: Windows CE on TPC-60S
- 4.1 TPC Utilities
- 4.2 Networking
- 4.2.1 Network via Ethernet
- 4.2.2 Network via Serial Port
- Figure 4.24: PC Connection
- Figure 4.25: PC Connection Properties
- Figure 4.26: Change Connection
- Figure 4.27: Change Connection
- Figure 4.28: COM1 Set
- Figure 4.29: Microsoft ActiveSync
- Figure 4.30: Select Connection Setting
- Figure 4.31: Configure Connection Setting
- Figure 4.32: Get Connected
- Figure 4.33: Run Repllog.exe on the TPC
- Figure 4.34: Connection on the TPC
- Figure 4.35: Connection on the Host PC
- Figure 4.36: Explore the TPC
- 4.2.3 Network via USB Client Port
- 4.3 Application Program Development
- 4.4 Wireless LAN Utility for TPC-61S
- Appendix A Watchdog Timer Programming
- Appendix B Fuse Specifications
- Appendix C Pin Assignments
TPC-60S Series User Manual 54
Appendix A Watchdog Timer
Programming
There is a built-in watchdog timer in the TPC-60S series. You can access
it through the WIN32 API. TPC-60S panel computers provide a WDT
driver to allow users to enable/disable the Watchdog timer. The driver
name is “WDT1:”. Programmers must open this driver before using the
resources. Then programmers can use DeviceIOControl functions to
enable/disable Watchdog timer. The introduction below includes the
DeviceIOControl, the definition of the parameter and an example.
A.1 DeviceIOControl
This function sends a control code directly to a specified device driver,
causing the corresponding device to perform the specified operation.
BOOL DeviceIoControl(
HANDLE hDevice,
DWORD dwIoControlCode,
LPVOID lpInBuffer,
DWORD nInBufferSize,
LPVOID lpOutBuffer,
DWORD nOutBufferSize,
LPDWORD lpBytesReturned,
LPOVERLAPPED lpOverlapped );
Parameters:
• hDevice
[in] Handle to the device that is to perform the operation. Call the Cre-
ateFile function to obtain a device handle.
• dwIoControlCode
[in] Specifies the control code for the operation. This value identifies
the specific operation to be performed and the type of device on which
the operation is to be performed. No specific values are defined for the
dwIoControlCode parameter. However, the writer of a custom device
driver can define IOCTL_XXXX control codes, per the CTL_CODE
macro. These control codes can then be advertised, and an application
can use these control codes with DeviceIoControl to perform driver-
specific functions.










