Integrated robotics - log file directory setting

[Hudson]

Hello,

  One issue I have is how to set dynamic log file path like the OpconData \\%DataSetAccessHost%\OpconData$\, thank you.

[TimoGotsmann]

Hello,

if I understood correct, you got problems because two of your robot units try to write in the same log file and are referenced to the same folder. 
The most convenient way would be to move the log file into the "robot folder" which should be unique for every robot.

In your case that could be:

Robot folder 1  (file structure path): D:\OpconData\AssyRobot

Robot logging 1: D:\OpconData\AssyRobot\Logging.txt

Robot folder 2  (file structure path): D:\OpconData\Staubli

Robot logging 2: D:\OpconData\ Staubli \Logging.txt

The most convinient way would be to move the log file into the "robot folder" witch should be unique . 
That would be in youre case:

[Hudson]

Sorry about unclear, I mean that my station has a active mpad(has a windows system) and PLC is also a windows system, it means the log file is in the PLC, but need to open the log file via HMI, in this way, the path D:/ is the driver of the HMI, not the PLC's. so I want to set a dynamic path, because copy station' IP is different

[SteffenR-]

In general since Control plus Studio V5.8 includes environment variables that can be used in every object for every parameter:

You can also create your own environment variables, very helpful also for simulation:

But there is a limitation on file access with TwinCAT. TwinCAT can access only files with a local path "C:\..." or "D:\...", not on any network path (even if this path is targeting to the local harddisk) and not on any mapped network drive.

That is why this robot parameter must be a path like "D:\OpconData\...", see also our example project Digital Machine:

PS: If you are doing cyclic file backups of your target system data (e.g. with MES CyclicUpdate) I do not recommend to save the log file inside the main robot directory. Otherwise every log entry will trigger the backup routine: