IMDTouchKnowledge BaseShop main store

Troubleshooting

Fixing Vijeo Designer Error 1850 Secondary Drive Not Found

HMI and touchscreens Published 5 min read

Short answer

Error 1850 on an HMIG3U appears because the project assigns a data file to a Secondary or Optional drive this target does not define; it supports only the Main drive with an SD card. Move the data file's location to Main, rebuild, and the download completes. No hardware switch enables the missing locations.

On this page
  1. What Error 1850 actually reports
  2. Why the Secondary and Optional fields are greyed out
  3. Move the data file to Main and download again
  4. What the SD card is actually for on this target
  5. When a secondary drive is real but missing or full
  6. The decision for each case
  7. Questions asked

Error 1850 stops the download because the project points a data file at a drive the HMIG3U does not have. In Vijeo Designer V6.2 this target supports exactly one data location — Main, used with an SD card — so a text file assigned to Secondary or Optional fails the build with Error 1850 before anything reaches the panel. Set the file's data location back to Main, rebuild, and the download completes. The greyed-out Secondary and Optional boxes in the Property Inspector are not a switch you have failed to find; this screen type simply does not offer those locations, and nothing on the panel changes that.

What Error 1850 actually reports #

Schneider Electric's FAQ for this error, FA194422, gives the full text: "Error 1850: [Target] [target name] Secondary drive is full or not found. Check the Data File location setting." The check runs on the PC while Vijeo Designer generates the application for transfer, which is why the download never starts. Two conditions raise it: a data location points at a drive that is not present, or the drive that is present cannot hold both the user application and the data files. On the HMIG3U you are in the first case with a twist — the drive is "not present" because the target does not define it at all.

Why the Secondary and Optional fields are greyed out #

Vijeo Designer builds the data-location list from the target type selected in the navigator, and the help entry for this screen type says it does not use Secondary or Optional drives — only the Main drive with an SD card. The Property Inspector greys out the two fields because there is nothing valid to enter in them, not because a setting elsewhere is switched off. The panel's port complement — one mini-USB port, two standard USB ports, one SD card slot — does not add data locations; ports and data locations are separate layers in the target definition.

Because the capability list belongs to the target itself, look-alike problems have a different root: when a whole target family is absent from the development environment, that is a catalog problem, covered in getting the HMIGXO family into the Vijeo Designer catalog, not a data-location problem.

Data location HMIG3U support Decision
Main Supported; the help ties this target's storage to the SD card Keep every data file here
Secondary Not defined for this screen type; field greyed out Never assign a file to it
Optional Not defined for this screen type; field greyed out Never assign a file to it

Move the data file to Main and download again #

  1. Open the property configuration of the text file that the Text Display object reads.
  2. Change its data location from Secondary or Optional to Main.
  3. Rebuild the project so the generator re-evaluates every data location.
  4. Download to the HMIG3U and confirm that Error 1850 no longer appears and the Text Display object shows the file's contents.

Leave the panel powered for the entire download. The vendor's guidance for this error says not to switch the target off, and a transfer cut by power loss turns a software error into a recovery job.

What the SD card is actually for on this target #

The reason for wanting Secondary was sound: put the text file on removable media so the test procedure can be edited without touching the application. The help text closes that door on this target. Main with an SD card is one storage scheme, and nothing documented for this screen type provides a runtime path syntax that would let a Text Display object pick up an externally edited file from the card. Treat the text file as part of the project — edit it in Vijeo Designer, rebuild, re-download. If data logging later moves onto card storage and you want those files over the network, the traps are collected in why HMI SFTP cannot see the SD card data log files.

When a secondary drive is real but missing or full #

Not every target behaves like the HMIG3U. On families that do declare a Secondary drive, that drive lives on the SD card, and the documented card guidance for the HMIGTO family is SDHC Class 10 up to 32 GB. There, Error 1850 usually means no card is seated: power down, insert the card, power up, retry. The "full" half of the message is the rarer case, because the card must hold the user application and the data files together.

Worked example with illustrative sizes: a user application of 24 MB plus data files of 11 MB needs 24 + 11 = 35 MB on the secondary drive. A 32 GB card stores roughly 32,000 MB, so the requirement uses 35 / 32,000 ≈ 0.11% of it. At these sizes capacity is never the constraint — if the error persists with a sound card seated, the cause is the data-location assignment, not space.

The decision for each case #

  • HMIG3U with a file assigned to Secondary or Optional: move it to Main, rebuild, download. The hardware is not faulty and no switch is hidden.
  • HMIG3U with a field-editable file as the goal: not offered by this target; edit the file inside the project and re-download the application.
  • Target with a real Secondary drive on SD: seat an SDHC Class 10 card up to 32 GB; if the error returns, verify the card can hold the application plus the data files before looking deeper.

Questions asked

Can I create a Secondary drive by plugging a USB stick into the HMIG3U?

No. The data-location list is fixed by the target type in Vijeo Designer, not by what is plugged into the ports, and the HMIG3U declares only Main with an SD card. A flash drive in a standard USB port never registers as Secondary, so Error 1850 keeps appearing until the location is set back to Main. The ports still work for transfer and peripherals; they just do not become data locations.

What SD card should I use on a target that has a real Secondary drive?

Where a family documents its Secondary drive on the SD card, the HMIGTO family for example, the published guidance is an SDHC Class 10 card up to 32 GB. Faster or larger cards buy nothing for data files. The only capacity rule that matters is that the card must hold the user application and the data files together, which leaves a 32 GB card overwhelmingly spare at typical project sizes.

Can operators edit the Text Display file without a new download?

Not through Secondary or Optional on an HMIG3U, because the target does not define them. The documented scheme is Main with an SD card, and no runtime path syntax for an externally edited Text Display file exists in the documentation for this screen type. The file stays inside the project, so any edit goes through a rebuild and a re-download. The re-download replaces the application image the panel loads; it does not touch anything else on the unit.

Does Error 1850 mean the HMIG3U hardware has failed?

No. The check runs in Vijeo Designer on the PC while the application is generated, so the failed build never reached the panel, which keeps running whatever application it already holds. Nothing needs replacing or opening up. Correct the data location to Main and the same panel, with the same ports and card slot, downloads normally.

Keep reading

  • Troubleshooting

    Fixing Goto Display Buttons Locked by HMI Global Connections

    While the Global Connections remote display number is active — its DINT tag still holding 21 — FactoryTalk View ME disables every other form of navigation, so Goto Display buttons stay dead whether or not the popup is visible. Write 21 with a one-shot on bit A and let a startup macro on display 21 reset the tag to 0; the popup stays up and the buttons respond.

    HMI and touchscreens

  • Troubleshooting

    Why an HMI Transfer Fails in Initial Start Mode Despite Ping

    Ping success proves only that the panel's IP stack answers. On a new Magelis XBTG in Initial Start Mode, run three checks in order: build in the engineering version that still supports the target (Vijeo Designer 6.2 for XBTG), clear the license so the download command activates, then load runtime and application over one transport at a time.

    HMI and touchscreens

  • Troubleshooting

    Fixing FATAL ERROR 11 Touchscreen Controller Not Found

    FATAL ERROR 11 is the machine application's touch-initialization routine timing out because the touch controller never answered, not a dead panel. Check four things in order: the overlay tail and connector, each 4-wire electrode under 50 ohms; the DOS driver files on the PCMCIA boot card; the controller's power-on string at 9600 baud 8N1; and the +5 V rail, which must sit between 4.75 and 5.25 V.

    HMI and touchscreens