IMDTouchKnowledge BaseShop main store

Troubleshooting

Why GP-Pro EX CSV export writes to the simulation folder

HMI and touchscreens Published 7 min read

Short answer

In GP-Pro EX simulation, CSV extraction from a sampling group works but writes the file into the simulation's internal folder, so the production directory you watch stays empty. Confirm the request completes, then look where the executing runtime actually writes — the simulation's internal folder during tests, the configured destination under WinGP on the site PC.

On this page
  1. Why is the CSV file not in the folder I am watching?
  2. Does a visible trend curve prove the export works?
  3. What do the USR100 and USR101 writes actually control?
  4. Where are the CSV settings I need to check?
  5. How many samples must exist before an export can produce a file?
  6. How do I run one controlled export test?
  7. Why does the site PC need its own WinGP verification?
  8. Questions asked

The export is not failing. In GP-Pro EX simulation, CSV extraction from a sampling group runs and creates the file — inside the simulation's internal folder rather than the production directory you are watching. That behavior leaves your folder empty while the data sits elsewhere, and pressing the button again cannot move it. Separate three things before touching the project: whether the group stored records, whether the export request was accepted, and which output folder the executing runtime actually resolved. This article walks those checks in order, explains what the word button's writes to USR100 and USR101 really control, and ends with the WinGP verification that proves the deployed destination on the site PC.

Why is the CSV file not in the folder I am watching? #

Because in GP-Pro EX simulation the extraction completes but the file is created in the simulation's internal folder, so the directory you configured for the deployed application stays empty — the export worked, just not where you looked.

Simulation and the deployed WinGP runtime are different execution contexts with their own storage. During a simulation test, checking only the folder configured for the deployed application gives a false failure indication: the file exists, in the other context's storage. Nothing about the button, its constants or the project logic moves that location; only switching the executing runtime does.

Decision: while testing in simulation, inspect the simulation's own output location for the file, and count the site destination as verified only after an export from WinGP itself.

Before changing a working project, rule out the fixes that cannot help:

Attempted fix Why it cannot work Deciding check
Pressing the export button repeatedly Repeated requests do not change the destination and can obscure the first request's result One request, then inspect the active runtime's output location
Changing the hexadecimal display format The value 1 is identical in hexadecimal and decimal; the base is presentation only Read the word value and its configured function
Incrementing USR101 again An increment helps only if that address has a role in the export configuration Read the address assignment in the group's CSV settings
Reworking the migrated trend The trend already works; display and file creation are separate functions Check stored samples and export settings first

Does a visible trend curve prove the export works? #

No — a displayed curve proves values reach the screen; it does not prove that sampling records were stored, that the export request was accepted, or that the file landed in the folder being checked.

CSV output needs three conditions, each verified in its own place:

  • Stored samples: the selected group holds a stored-sample count above zero before the request. Read it in the sampling display or the group's diagnostics.
  • Accepted request: the configured command value reaches its assigned control address. Observe the address online while the request is issued.
  • Writable destination: the executing runtime can write to the folder it resolved. Check the CSV destination settings against the actual filesystem of that runtime.

Decision: if all three hold and the file is still missing from your folder, it exists somewhere else — return to the first check and look where that runtime writes.

What do the USR100 and USR101 writes actually control? #

Only what the sampling group's CSV settings assign them — the word button writes the constant 1 to USR100 as a 16-bit hexadecimal value and increments USR101 by 1, but their export meaning comes entirely from the configured control-address roles.

Neither write is an export by itself. A word address becomes a command, a file-selection value or another control field only through the role assigned to it in the group's CSV control settings, so read that assignment before treating either address as the export interface.

Two consequences follow. Rewriting 1 into a word that already holds 1 produces no value transition, which matters if the export function triggers on a change of state rather than a maintained value. And an adjacent, incrementing address is not automatically part of the control structure: a counter that climbs proves the button fired, not that a file was written.

Decision: match each address to its documented role, then establish whether the request convention is a maintained value or a transition — do not change the button constants until both are known.

Where are the CSV settings I need to check? #

In the GP-Pro EX editor, open the Common Settings (R) menu and select Sampling (D) to list the registered sampling groups, then edit the group that feeds your curve and read its Display/Save in CSV settings.

In those settings you choose the format setting mode: Basic Settings applies one preset format for straightforward configuration, while Custom Settings exposes the individual output fields. For the full procedure of defining groups and their channels, see how to set up Pro-face historical trend channels.

Three things in those settings decide your missing file:

  • The destination and file-naming settings, matched to where the deployed runtime must write.
  • The control addresses for the request, the file selection and the status, matched to the button's actual writes rather than its label.
  • The group's data addresses, compared with the group the trend displays — the curve and the CSV must draw on the same captured data if the export is meant to reproduce the curve.

Decision: if the configured roles do not match the writes to USR100 and USR101, correct the assignment in the settings, not in the button.

How many samples must exist before an export can produce a file? #

More than zero — the deciding quantity is the stored-sample count of the selected group, because CSV output can only write records the group has already captured, and a changing display value can exist without a usable history.

Worked example with illustrative inputs: a group sampling on a 10-second cycle, run for an 8-minute test. That is 8 min × 60 s/min = 480 s of acquisition; 480 s ÷ 10 s per cycle = 48 cycles; counting the sample taken at the start, 49 stored records. A diagnostic reading of 49 records means the export has data to write. A reading of 0 means the missing file is an acquisition problem, and no destination or button change will fix it — check the sampling condition, cycle or event, against the test period instead.

The same stored-data question decides longer deployments, where retention limits rather than test length set the count: see verifying HMI historical trend retention before committing.

How do I run one controlled export test? #

Confirm four things — the executing environment, the selected group, the stored samples and the configured destination — then issue exactly one export request and look for the file where that runtime actually writes.

  1. Record the executing environment, simulation or WinGP, because it decides which output location to inspect.
  2. Identify the group: confirm which sampling group supplies the displayed curve and which group the CSV command exports, and compare their data addresses.
  3. Generate recognizable samples: run the acquisition long enough to store several changing values — with the 10-second cycle above, 8 minutes stores 49 records. If the test values must come from the process, use a controlled change on an offline or simulated controller, never a forced output on a machine that will run.
  4. Read the CSV configuration: destination, file naming and the assigned control addresses, matched to the button's writes.
  5. Issue exactly one export request. Observe USR100 and USR101 before and after the press, and watch any configured status or error indication.
  6. Inspect the file where that runtime writes — the simulation's internal location during a simulation test, the configured destination under WinGP — and check its modification time and contents.
  7. If no file appears, resolve the output path and the runtime's write access before repeating the request; a second press adds no information.

Why does the site PC need its own WinGP verification? #

Because a successful simulation export proves the project's function in simulation only — the deployed destination, the runtime's write access and the account that starts WinGP all remain untested until you export once from the site PC.

WinGP is the runtime engine that executes GP-Pro EX screen data on a Windows PC, so the site supervision runs in a different context from the editor's simulation — the same gap that appears when testing HMI simulation against a live PLC. Close it in the deployed context:

  • Run the deployed project in WinGP and capture a fresh set of identifiable samples.
  • Request one CSV export and locate the file in the destination that runtime uses.
  • Compare the exported values, and the timestamps if configured, against the trend over the same period.
  • Export a second time and compare names and modification times, to learn whether your naming settings create a new file or update an existing one.
  • Repeat under the account and startup method used for normal supervision, because a different account can have different folder access.

Decision: a current CSV containing the expected records closes the issue — request and destination work together. A CSV that exists but holds old records points back to group selection, acquisition timing or file-selection behavior, not to the destination.

Questions asked

Can I redirect the simulation's CSV output to my project folder?

No documented GP-Pro EX setting redirects the simulation's internal output location, so do not build the test around it. Verify the export function in simulation and accept where the file lands there, then prove the real destination with one export from WinGP, which writes to the configured folder under the account running the runtime.

Could the missing file mean the migration to GP-Pro EX was incomplete?

No. The trend and the real-time behavior already prove the migrated data path works. CSV extraction is a separate function that depends on the sampling group's stored records and on the executing runtime's output folder, so a missing file points at those two, not at the transfer itself.

How do I tell whether an export creates a new file or overwrites the old one?

Read the file-naming settings in the group's CSV configuration, then confirm by test: export twice with a short gap and compare names and modification times in the destination. Two distinct names mean one file per request; a single name with an updated modification time means the same file is rewritten.

Can I add the pump name and product number to the CSV later?

Yes, as long as those fields become part of what the sampling group records — text shown beside the trend is not captured unless the group includes it. Add the identity words when you define the group, or associate them explicitly with the exported records, so one export carries both process values and identity.

Keep reading

  • How-to

    How to set up Pro-face historical trend channels in GP-Pro EX

    The channel selector reads undetermined because a historical trend pen can only select channels from a saved sampling group. In GP-Pro EX, open Common Settings, create the Sampling group with your RSLogix 5000 tags, then bind the trend pens to those logged channels. No PLC-side buffer list is needed.

    HMI and touchscreens

  • Troubleshooting

    Why HMI Data Logs Export Bool True as -1

    A Comfort Panel USB data log shows -1 for a true Boolean because the export serializes the all-ones bit pattern as a signed value. Assign the literals 1 and 0 conditionally into a separate numeric tag and log that tag; a direct copy into an Int or UInt keeps the -1. Verify the change in the raw CSV with a text editor.

    HMI and touchscreens

  • Troubleshooting

    Why WinCC 7.5 Runtime Fails Under a New Windows User

    Runtime failing under a newly created Windows account while Explorer opens is a Windows security-context problem, not a WinCC project problem. Put the account in the SIMATIC HMI group, sign out fully, verify effective access to the project, and after an Admin password change update the logon identities of services and scheduled tasks.

    HMI and touchscreens