Applies to:
WaveView Connect, WaveRadar Rex, Datawell systems, pressure/airgap sensors, multi-sensor deployments.
Explanation:
The WVC configuration XML file defines inputs, drivers, processing modules, motion compensation, outputs, and logging behaviour Major sections include , , , , , and . WVC reads this file when the service or standalone instance starts; any change requires a restart of the relevant instance, especially in service mode.
WVC has a basic setup wizard, and a more advanced configurator built into the software. These tools create the conf.xml file. Backup or copy of this file is useful for system restoration and fault finding.
For a newly installed system, it is sensible to create a basic configuration and then modify using the advanced tool.
Conf.xml can be manually written, but care must be taken to include correct syntax and format.
Additional notes:
Use version control and XML validation before deploying configuration changes offshore.
Multi-Service Installations and Parallel Processing Pipelines
Troubleshooting:
- If changes appear to have no effect → verify which XML file the running service actually uses and restart that service or instance.
- If WVC fails to start after an edit → validate XML syntax with an external tool; mismatched tags or illegal characters can prevent loading.
- If a driver does not start → double‑check baud rate, parity, and for the associated input block.
- If outputs are missing → confirm the block is present, paths exist, and the user account has write permissions.
- If multiple services overwrite logs → assign unique filenames and directory paths in each configuration file. Maintaining a version-controlled repository for XML configurations allows quick rollback to a known‑good state in case of mistakes.