Table of Contents
Advertisement
DDE Server User's Guide
•
The communication port does not exist on the PC running the DDE
Server. Reconfigure topics that are configured with this port to another
port. This problem may be caused by improper configuration of the RS-
485 card driver (if you are using some special multiport card). Please
refer to the card driver's configuration manual.
•
The port is already being used by another application. Close any other
applications on the machine and restart the Server.
•
The port may not be working. Test the port with a communication
program such as HyperTerminal.
No Write to Individual Discrete Bits
The client tried writing to individual bits of a read/write register, which is
not allowed.
Open comm for <comm port> failed
This error may be followed by one of the following error messages:
•
Invalid or unsupported ID <comm port> — The port is not
supported or the port ID is bad. Check the ID of the port to which the
devices are connected and reconfigure the topics with the correct port
ID.
•
Device already open <comm port> — Try restarting the Server. If the
problem persists, the port may be in use by another application.
•
Device not open <comm port> — Try restarting the Server.
•
Unable to allocate queues — Try restarting the Server.
•
Error in default parameters — The default parameters set for the port
in the DDE Server configuration or other programs are bad.
•
Hardware not present or already allocated <comm port> — Port
hardware is not available. If there is a communication port-disabling
facility (some notebook PCs have this facility to save power), enable
the ports, reboot the machine, and try starting the Server again.
•
Invalid byte size — The byte size is invalid.
•
Unsupported baud rate — The baud rate that was programmed is not
supported by the communication port. Please refer to the
communication port hardware reference for supported baud rates.
•
Unknown error from OpenComm: <error code> — Try restarting
the Server.
RegFormat Name is INVALID
The register name(either as mnemonic equivalent or as item name) is not
valid.
Retrieve command time not occurred <device name>
This error occurs when the Waveform client sends the RetrieveWFC
command very soon after it has sent the TriggerWFC command. Introduce
a small delay (approx. 5 seconds) before issuing the RetrieveWFC
command to the Server. This will allow the device to collect waveform data
properly.
RetrieveWFR : Got out of range values for depth, range is 1-3
Chapter Five - Troubleshooting • • • • 63
Advertisement
Table of Contents
