Omron NB3Q-TW00B Startup Manual Manual page 114

6 Maintenance and Troubleshooting
3
Why is the communication between the HMI and slave Unit slow and how to improve it
The possible causes of a slow communication:
(a) There are too many components on a single screen communicating with the slave Unit,
(b) The macro uses too many sentences which call addresses of the slave Units directly. It
(c) In the screens such as Common Sheet too many timers are deployed;
(d) Too many background components such as Data Log, XY Graph and Data History are
(e) Alarm and Event Registration addresses are too many and discontinuous;
(f) Too many PLC control components are used;
(g) On-site Interference;
(h) Too many vector font formats are used. Try not to use too many vector font formats in a
(i)
(j)
(k) There are too many controllers communicating with the PT and too many
Solutions:
(a) Components on a single screen communicating with the slave Unit should be as few as
(b) Try to keep the addresses of the components on a single screen communicating with
(c) Try to use PT's internal addresses as variables for macro. If there is a need for
(d) Keep a minimum of number of channels of background components such as Data Log,
(e) Try to keep Alarm and Event Registration addresses continuous;
(f) Do not use too many PLC control components;
(g) Use a shielded cable for the communication cable. Keep it at least 10 CM away from
(h) Try to use less vector fonts and use bitmaps instead when creating screens. Even if
4
PLC No Response: what is the meaning of XX-XX-X
XX-XX-X means: PT number - PLC station number - PT serial port number. For example, 00-
01-01 means the No.0 PT using the serial port COM1 loses communication connection to the
controller with the station number 1.
The serial port number is defined as: 01/02 represent COM1/COM2.
5
The causes for a project downloading failure
Downloading through USB fails:
Check whether hardware connections are still functioning well or not, then check through the
following factors
(a) USB driver is not installed successfully.
(b) USB driver has been corrupted. Find the driver at NB-Designer/driver and reinstall it;
(c) The USB cable has been damaged, so replace it;
(d) The USB port of the PT or the PC fails;
6-26
and besides, the addresses are discontinuous;
is recommended not to call addresses of the slave units directly in a macro program;
employed, and the background components are running all the time;
project to the utmost;
Too many bitmaps are used;
Too many screens pop up, such as direct screens and indirect screens;
communication addresses.
possible;
the slave Unit continuous;
exchanging data between the touch panel and slave Unit communication components,
resort to the data transmission function of the timer or data transmission components;
XY Graph and Data History components, etc. and make sampling periods as long as
possible;
power lines, and make sure the system is grounded properly;
you need to use vector fonts, use the vector fonts at minimum.
NB-series Programmable Terminals Startup Guide Manual(V109)