Troubleshooting
Why HMI SFTP Cannot See the SD Card Data Log Files
Short answer
On a PanelView Plus 7 Series B terminal, the SFTP service publishes internal storage only; the SD card and USB drives never appear to a remote client. A data log whose path root is removable media cannot be retrieved remotely until you redirect it to internal storage or copy it at the terminal with the file explorer application.
On this page
On a PanelView Plus 7 Series B terminal, SFTP reaches internal storage and nothing else. The SD card and USB flash drives never appear in a remote listing — not from any client, not under any account — and that is the documented behavior of the Series B file service, not a connection fault. A data log written to the card is invisible remotely, while the default FactoryTalk View ME Station logs under \Windows\Logs transfer fine because they sit on internal storage. Two fixes exist: redirect the data log to internal storage and collect it by SFTP, or copy the file at the terminal. What follows confirms which side of the boundary you are on, then walks the redirect and the verification.
Start with the terminal series #
Read the Series designation from the terminal label or the system information screen before touching the application. The series, not the catalog number alone, sets the remote-access path.
| What you read | What it means | What to do next |
|---|---|---|
| Series B; SFTP lists internal files but no card or USB | Documented Series B behavior | Check the configured log path |
| Series B; SFTP lists nothing at all | Connection, account or service fault | Fix the SFTP session before judging storage |
| Series A or another series | A different generation with its own service set | Read that terminal's documented file services |
When SFTP reaches nothing at all, work the connection first, with the same discipline as diagnosing intermittent HMI to PLC Ethernet comms hangs; storage is the wrong branch until a session lists anything.
Find where the log is actually written #
Station logs and application data logs are configured separately, and they do not have to share a home.
- Default Station logs sit in internal storage under
\Windows\Logs. That default says nothing about where your application's data log writes. - The application's destination is the Log File Path under Application Settings → Data Logging in the FactoryTalk View ME application. A removable destination such as
\USB Storage\Logsputs the file outside everything SFTP publishes on Series B. - Trigger one fresh record and compare timestamps before trusting an old file's location. A stale copy on removable media sends the investigation down the wrong branch.
The runtime validates the root itself: when the configured root is missing — media unplugged, or a second drive expected — logging halts with an error such as Data log failed, "\USB Storage2" doesn't exist. Check root path and re-trigger. That is a terminal-side stop, distinct from remote invisibility. With that error, no file is being written for anyone to retrieve.
Prove the boundary with two listings #
- From the PC, open the SFTP session to the terminal's address with the configured account.
- List an internal directory that holds a known file —
\Windows\Logsfor Station logs. - List the configured removable path, the card root in this case.
- Read the pair: internal files visible with the card absent confirms the boundary, and the transport, account and service are all healthy.
Swapping clients stops here. An automated script inherits the same published tree, so repeated tool changes burn time without changing the outcome once the internal listing succeeds.
Working the case: 2711P-T12W22D9P Series B with the log on the SD card #
Inputs:
- Terminal catalog number 2711P-T12W22D9P, Series B, read from the terminal label; the catalog number alone does not carry the series.
- Data log destination: the SD card, as set in the Log File Path under Application Settings → Data Logging.
- Station-log default:
\Windows\Logson internal storage, the documented default location.
Rule in words: the Series B SFTP service publishes exactly one storage root, internal storage. A file is reachable remotely only when its path resolves under that root, so a destination rooted on the SD card resolves under zero published roots.
Arithmetic, written out:
- Storage roots in play on this terminal: internal storage + SD card = 2.
- Roots published over SFTP: 1 of 2.
- Listings performed in the test: 2, one internal and one at the card root.
- Listings that returned files: 1.
- Published roots matching the configured log destination: 0 of 1.
Result: the session, the account and the network all pass, and the destination alone places the file outside the published tree.
Decision: zero matches is the threshold. No client, credential or script change raises it, so redirect the Log File Path to internal storage for unattended PC collection, or plan a local copy at the terminal. Had the internal listing also come back empty, the fault would sit in the SFTP session itself, not in storage.
Redirect the log to internal storage #
- Record the current Log File Path, the file-naming behavior, the retention setting and the time of the last good record.
- In Application Settings → Data Logging, set the Log File Path to an internal destination the SFTP account can list — chosen for the logging function, not inherited from the Station-log default.
- Apply the change through the normal FactoryTalk View ME deployment to the terminal.
- Trigger a record and confirm at the terminal that a new file or an updated timestamp appears at the internal destination.
- From the PC, list that directory over SFTP and download the new file.
- Set the application's retention against the free space the terminal reports. Internal storage now carries the runtime and the log history together, and one successful transfer does not protect it from filling later.
The collected file is not yet plain data. Native ME data-log files open in the FactoryTalk View File Viewer, and only closed files open — per the vendor's utility documentation you stop the running Machine Edition application to read the active file. Schedule that stop, because the terminal has no operator interface while the runtime is down, or collect after the file rolls over.
If removable media must stay in the plan #
Choose by who collects the file and how it will be read.
| Requirement | Route that works on Series B |
|---|---|
| Unattended collection from a PC | Internal storage plus SFTP retrieval |
| Onsite staff hand over media | Keep logging to the card; the file still needs the viewer on a licensed PC |
| Local copy without pulling the card | The File Explorer application in the Windows 10 IoT control panel moves files between internal storage, the SD card and USB, at the terminal |
| Copy built into the screens | A Data Store Plus control running a batch file copies finished log files to USB on a button press |
If the people onsite hold no viewer license, the file was always going to travel to the engineering PC — redirect to internal storage and pull it by SFTP instead of routing it through hands that cannot open it. Where recipients need plain data, a Data Store Plus control can write CSV directly and drop the viewer from the chain. If this storage boundary is the dealbreaker for the installation, carry it as a hard requirement when planning an HMI terminal replacement from an older operator panel.
Verify the collected file #
A visible directory proves only SFTP access; a downloaded file with current records proves the whole path.
- Compare file name, size and modification time between the terminal and the PC copy.
- Open the file in the FactoryTalk View File Viewer on the licensed station and confirm the test record's timestamp and values.
- Retrieve a second time and confirm logging continued through the collection.
- If the active file changed during transfer, collect again after the logging interval or after rollover instead of shipping a torn file.
Questions asked
Will a different SFTP client or an automated script see the SD card?
No. The Series B terminal's SFTP service decides what is published, and it publishes internal storage only. Every client, and every scheduled script running from one, sees the same tree. Changing tools, ports or credentials changes nothing until the log destination itself moves to internal storage.
Does the internal-storage-only rule apply to Series A terminals?
The limit is documented for Series B, which also offers SFTP only, with no plain-FTP option. Series A is an earlier hardware generation with its own software stack, so read that terminal's own documentation for its file services instead of assuming the same boundary.
How do I open the data log file once it reaches the PC?
Native FactoryTalk View ME data-log files open in the FactoryTalk View File Viewer on a licensed engineering station, and the viewer exports to CSV. Only closed files open, so the active file must be rolled over or the runtime stopped first. When recipients need plain data with no viewer in the chain, a Data Store Plus control can write CSV directly at the terminal.
The terminal says a USB storage path does not exist. Is that the SFTP problem?
No. That message, for example Data log failed, \USB Storage2 doesn't exist, means the runtime cannot find the configured root at the terminal: the medium is unplugged or the root name is wrong, and logging has stopped. Fix the path or reinsert the media first; remote visibility is a separate Series B limit.
Can operators copy log files to USB without walking the file explorer menus?
Yes. A Data Store Plus control on a graphic can run a batch file that copies finished log files to a USB drive on a button press, making removable-media collection a built-in action instead of a menu walk. The copy still happens at the terminal; it does not make the drive visible to SFTP.