File Device - Migration to AS6.3

Hi everyone,
I’m currently facing several challenges while migrating from Automation Studio 4.12 to 6.3.

The latest issue I’m dealing with concerns the handling of File Devices.
In my project, I use file devices that are defined in the CPU configuration (for example, USER pointing to F:\), as well as dynamically created file devices using the DevLink function block, based on the current system configuration.
image

image

After downloading to the PLC, I get multiple errors in the Logger, all seemingly related to the file devices.

One concrete example is the use of the VideoPlayer widget, which relies on a file device defined in the CPU.
Similarly, I encounter errors for the file devices created dynamically with DevLink.
image

What precautions or adjustments should I consider to ensure correct file device handling in AS 6.3?

Thanks in advance!

Hi,

Did you try to change F:\ by USER_PATH ? This point directly on the USER partition of the PLC (works also on ARSim).

I have seen on a project that using USER as FileDevice name result as usable filedevice (TextPad widget).

I have replace USER by HD (Hard Drive) and I got no problem now.

Hope that could solve you issue :slight_smile:

Regards,
Florent

Hi Florent,
I tried replacing USER with both HD0 and USER_PATH, but unfortunately the issue is still there.

image

Any ideas on what else I could try? Thanks again for your help!

Yes there is a new configuration for FileDevice and mappView, by default you cannot access it from external:

Check the parameter “File device whitelist”, you can add your FileDevice name and it should work :slight_smile:

I know there is also things with new roles, but I don’t think it’s link with VideoPlayer, it’s more for MappFile!

Regards,
Florent

2 Likes

Thanks a lot, Florent – that was a big help!
Now I can move forward with the migration to AS6.

Talk to you soon!

1 Like

I’m glad I could help you solve your problem. :slight_smile:

Heads up: The AS6 migration script just got updated to include info about this as well!

Thanks to @phaehnel :slight_smile:

3 Likes