WAGO Visualization Datalogger 2.3.0 reports No configuration file on a PFC300 even though logging is active and two JSON files exist. The evidence does not establish a root cause; it shows that CSV generation works while the visualization cannot discover or accept its configuration. Troubleshoot the configuration-loading path separately from data logging.
Separate logging from visualization
The WagoAppDatalogger.FbDatalogger instance is producing Logfile_dp_2025_07.csv under /media/docker/CSV_Files, and the file is updated every 20 minutes. This confirms that the reported failure is not a complete logging failure. The unresolved function is configuration discovery by http://PFC300-IP/datalogger-visu/.
| Component | Observed result | Diagnostic meaning |
|---|---|---|
| Datalogger function block | CSV output exists | Logging is operating. |
| SD-card data path | /media/docker/CSV_Files |
The reported data destination is mounted and writable. |
| Visualization configuration | Two JSON files exist in /home/codesys_root/PlcLogic/config/datalogger-visu
|
File presence alone has not satisfied the application. |
| Visualization page | No configuration file |
The application is not discovering or accepting a usable configuration. |
Isolate configuration discovery
Do not treat the edited datalogger-visu.json as confirmed active configuration. The error can still occur if the application searches another runtime location, cannot access the file, expects a different filename, or rejects the JSON content. These are diagnostic hypotheses, not confirmed WAGO Datalogger 2.3.0 behaviors.
- Record the filenames, paths, file contents, ownership, and access permissions for both JSON files on the failing PFC300.
- Collect the same information from the PLC where the demo program works.
- Compare the complete files before changing more fields. Check filename spelling, JSON structure, configured CSV path, and every difference between the working and failing installations.
- Restore an unedited copy of the known-working demo configuration on the failing controller, preserving its exact filename and structure. Change only values required to point at the reported CSV location.
- Reload the visualization and check whether the message changes. If it remains
No configuration file, investigate runtime file location and access rather than CSV production.
Check installation and project differences
The reported package is install-wago-sysapp-dataplotter_2.3.0_arm64, installed through WBM on a PFC300. Confirm that the working controller uses the same package, application version, project components, and deployment method. The evidence does not show whether declaring only WagoAppDatalogger.FbDatalogger is sufficient to deploy visualization configuration, so use the working demo project as the authoritative comparison rather than guessing a missing block or setting.
Verify the correction
A successful repair must satisfy both independent functions: the page at http://PFC300-IP/datalogger-visu/ loads without No configuration file, and it displays values sourced from the CSV data under /media/docker/CSV_Files. Also confirm that Logfile_dp_2025_07.csv continues receiving its reported 20-minute updates after the configuration change.
FAQ
Why does WAGO Datalogger 2.3.0 say No configuration file when JSON files exist?
The evidence confirms file presence but not that the visualization discovers or accepts either file. Compare the exact filename, location, permissions, and JSON content with the working demo PLC.
Does an updated CSV file prove the Datalogger visualization is configured?
No. Logfile_dp_2025_07.csv updating every 20 minutes proves logging is active, while the visualization configuration remains a separate failure point.
What should I compare with the working PFC300 demo?
Compare the installed install-wago-sysapp-dataplotter_2.3.0_arm64 package, project components, deployment method, JSON filenames and contents, file access, and the configured path to /media/docker/CSV_Files.