Delta ISPSoft — 2.4.3.2 Communication Parameter Setting - USB (Virtual COM)

Chapter 2 Starting and Setting ISPSoft If not sure about the communication protocol of the connected device, click Auto-detect to find out the parameter. When detection is successful, users can connect the device to a RS232 communication port selected with a RS232 cable, and click to automatically detect the communication protocol. If the communication protocol is successfully detected, its parameters will be automatically filled in the corresponding boxes in the confirm these two parameters before clicking auto-detect. section; however, the system will not auto-detect parameters for COM Port and ASCII / RTU , therefore, please (6) To setup parameters concerning responding time.

For Connect Retries, users need to setup the number of retry once connection error occurs, while for Connection Time-Out setting, the parameter concerns the time interval between retries. *. When changing a hardware device connected to a PC, users need to close the setting page concerning communication driver properties and re-start in order to obtain the new hardware communication device. 2.4.3.2 Communication Parameter Setting - USB (Virtual COM) Before starting the setup of USB type drivers, make sure: (a) The software for driver installation can be found in the computer. (b) The PC and PLC hosts has now established connection and is functioning. (1) Type the Driver Name .

To add special marks, only ‘_’ can be used. (2) For Connection Setup , select USB (Virtual COM) from the drop-down list for Type . (3) For COM Port , select the desired port for communication from the drop-down list. If (a) and (b) mentioned above is confirmed, the list will display the host device name and COM Port number. (4) To setup parameters concerning responding time. For Connect Retries, users need to setup the number of interval between retries. retry once connection error occurs, while for Connection Time-Out setting, the parameter concerns the time *. For more information regarding USB drivers in PLC hosts, please refer to appendix A . 2-47