User's Manual
Table Of Contents
- Introduction
- Installation and Setup
- Operation
- PC Utilities
- Bluetooth® Configuration
- Technical Specifications
- Commands
- B.1 Syntax Conventions
- B.2 BTCONTROL Enable/Disable Bluetooth
- B.3 COM Configure COM Port
- B.4 FRESET Clear Selected Data from NVM and Reset
- B.5 LOG Request Logs from the Receiver
- B.6 PDPFILTER Enable, disable or reset the PDP filter
- B.7 PDPMODE Select the PDP mode and dynamics
- B.8 RADARCFG Configure the ER output
- B.9 RESET Performs a hardware reset
- B.10 SBASCONTROL Set SBAS test mode and PRN
- Logs
- Replacement Parts
34 SMART-MR10 User Manual Rev 0B
Chapter 3 Operation
3.2.2 Communicating with the Receiver Using CDU
Launch the CDU program and select Device | Open from its main menu. The Open Configuration
window appears. Figure 7, below, shows an Open Configuration window with three possible
configurations already set up. Your configurations may be different or you may have none at all, in
which case, the Open Configuration window is empty.
Figure 7: Open Configuration Window
Refer to CDU’s help file by selecting the Help | Contents menu. 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,
or
[COM2] if connected to COM2 port,
Any of the above prompts indicate that the receiver is ready and waiting for command input.
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 the command FRESET STANDARD. You should now be able to use your original
communication port again.