Filter
Top Products
46 DL-V3 User Manual Rev 3
Chapter 3 Operation
Refer to CDU’s Help file by selecting the Help | Contents menu. See also Chapter 4, DL Explorer
starting on Page 56 for details of CDU’s DL Explorer tool. Ensure you can see the Console and ASCII
Messages windows by selecting them from the View menu.
When the receiver is first turned on, no data is transmitted from the COM ports except for the port
prompt. The Console window displays a port name:
[COM1] if connected to COM1 port,
[COM2] if connected to COM2 port,
or
[COM3] if connected to COM3 port
Any of the above prompts indicate that the receiver is ready and waiting for command input. The
screen may display other port names for other port types, for example USB1, USB2, USB3 or AUX.
1. You may also have to wait for output from receiver self tests. For example, on start-up,
the OEMV family receiver is set to log the RXSTATUSEVENTA log ONNEW on all
ports. Refer to the OEMV Family Firmware Reference Manual for more details.
2. If you find that CDU is unable to locate your OEMV family receiver, it may be that you
have previously used the SAVECONFIG command. In this case, try using a different
COM port to communicate to the receiver. Once communication has been established,
issue a FRESET STANDARD command. You should now be able to use your original
communication port again.
3. XCOM1, XCOM2 and XCOM3 virtual ports can be generated by the receiver. However they
are unlikely to appear as a port prompt as you cannot connect to these types of ports using
CDU. Also, they are not available with the COM command but may be used with other
commands, such as INTERFACEMODE and LOG. Refer to the OEMV Firmware Reference
Manual for the virtual ports available and details on the above mentioned logs.