<5. Function Test>
85
TI 34P02K35-02E Jun. 6, 2018-00
● Testing Communication Applications
Connections between an FCN-500 or FCN-RTU, which uses communication
application, and communication equipment can be tested in four steps as described
below.
1. Check physical hardware connection with communication equipment and
its setup
Check the cable connecting the FCN-500 or FCN-RTU and communication
equipment, as well as its wiring system.
The cable to be used varies with the equipment but the following general
checklist can be used.
Straight cable or cross cable
2-wire, 3-wire or 4-wire system
Pin assignment
This check is important as failure to establish communication with other
equipment is often due to improper cable and other physical connections, or
invalid connection-related settings.
2. Test communication application
After completing the checks described in step (1), check the operation of the
communication application.
Connect variables to the ERROR terminal and STATUS terminal of POUs used
in the creation of each communication application, and verify that no
communication error has been reported.
If any communication error is reported, check the error code stored in the
variable connected to the STATUS terminal, and fix the application.
3. Check mapping of received data
After ensuring the absence of communication error in step (2), check the
mapping of received data. Verify that data of the remote equipment is correctly
read and written.
4. Check application which uses received data
Steps (1) to (3) check the communication itself. After ensuring the absence of
communication problems, check the operation of the control application, which
makes use of the communication data.
Summary of Contents for STARDOM FCN-500
Page 2: ...Blank Page...
Page 10: ...Blank Page...
Page 32: ...Blank Page...
Page 36: ...TI 34P02K35 02E Jun 6 2018 00 Blank Page...
Page 76: ...TI 34P02K35 02E Jun 6 2018 00 Blank Page...
Page 163: ...Blank Page...
Page 221: ...Blank Page...
Page 225: ...Blank Page...