
ZENO
®
-3200 USER MANUAL
Coastal Environmental Systems (206) 682-6048
Page 238
Troubleshooting the RECEIVE Command Format Specifier
Once communication is established with a sensor, but the individual data fields cannot be parsed,
the problem is with the primary RECEIVE command that parses the received string. Observe
closely the message that has been received in the single string and compare it with the Format
Specifier in the primary RECEIVE parsing line.
Key Tips to Writing an Effective Format Specifier
1. Keep the Format Specifier as simple as possible, but ensure you can still be able to identify
the start of the message. It is not necessary to completely read a received sensor message--
ending characters that contribute no data don't need to be parsed unless they are needed to
identify a message.
2. Store the entire string received from a sensor and output it in the Data Retrieval Menu. Look
for any non-printable characters or control characters that may need to be included as part of
the Format Specifier for parsing the string accurately. Also, verify that the string outputted
from the sensor is the expected string. If the sensor is configurable, make sure it is configured
properly.
3. Avoid using checksum verification until the base sensor string is parsed correctly. If the
starting and stopping points for checksum verification are not set correctly, ZENOSOFT®
will not accept the string because the checksums will be invalid.
12.3. CONFIGURATIONS WITH MULTIPLE SERIAL SENSORS
Any sensor suite that includes multiple serial sensors can become complicated when determining not only
which communication ports to use, but also the timing of how data will be collected from each serial
sensor.
The following steps will simplify the creation of a configuration with multiple serial sensors.
1. Match each serial sensor to the supported serial sensor types in the ZENO
®
-3200. Any serial sensor
that is not directly supported can be handled by the USI.
2. Identify the port type of each serial sensor whether it is RS232, RS485, TTL or radio. Make special
note of any serial sensor that can support multiple port types.
3. Do not mix serial sensors with different communications protocols on the same multi-drop
communications link (RS485 or radio) unless necessary. If the port type of more than one serial
sensor is multi-drop (RS485 or radio) and they communicate using different protocols, there may be
difficulty in connecting them to the same multi-drop port on the ZENO
®
-3200. Different protocols
may cause interference on the same multi-drop communications link.
4. Coastal Environmental Systems recommends that any communications port that is being used with a
serial sensor should be excluded from using the User Interface.
279
Allowing the User Interface Task
to access the communications port that is being used for a serial sensor may inhibit the ZENO
®
-3200
from retrieving data from the serial sensor.
5. Do not mix serial sensor data collection with bi-directional User Interface communication on the
same communications port. Using bi-directional communication with the User Interface on the same
279
Refer to Section 6.12.
Kommentare zu diesen Handbüchern