Hello.
I'm trying to transfer file via IEC 104 driver between two WinCC OA server and client projects (using WinCC OA v3.15).
Directories "data","iecOut"(server),"iecIn"(client) are specified in config files.
Now i'm sending 122 type command from the client and get an answer (120 type command) from the server.
But in server log file "opening file error".
Note from server log file:
WCCOAiec (2), 2018.10.12 14:38:25.673, SYS, SEVERE, 14/iecError, ?????? ??? ???????? ????? (Opening file error) "data/iecOut/1_1".
WCCOAiec2:IecFileTrans::fileRequestStart 2018.10.12;14:38:25:652 "Type 122 COA 1 IOA 1 filename 1 secname 1 qualifier 1"
WCCOAiec2:IecFileTrans::procSelectFile 2018.10.12;14:38:25:696 send FileReady: "Type 120 COA 1 IOA 1 filename 1 secname 0 qualifier 128"
I don't understand what's wrong and how it should work properly.
IEC 104 File Transfer
- Gertjan van Schijndel
- Posts:634
- Joined: Mon Aug 02, 2010 10:37 am
Re: IEC 104 File Transfer
The IEC file retrieval command contains a file and section number, which results in the driver trying to read the file '_' from the '/'.
In the case of the error message this file does not exist or cannot be opened.
Why do you want to use IEC drivers for file transfer?
Why not use the native WinCC OA protocol (as done by 'fileSync' script for between redu servers)? And/or http (as done with the Desktop UI)?
In the case of the error message this file does not exist or cannot be opened.
Why do you want to use IEC drivers for file transfer?
Why not use the native WinCC OA protocol (as done by 'fileSync' script for between redu servers)? And/or http (as done with the Desktop UI)?
- tsvetkov
- Posts:4
- Joined: Wed Jul 06, 2016 7:26 am
Re: IEC 104 File Transfer
I use connection "WinCC OA 104 Client WinCC OA 104 Server" just to check the functionality. Instead of "WinCC OA 104 Sever" then it will be a different program.
I understand that this is error about the first segment (section) of the file "1".
But Wincc OA Help doesn't say anything about the formation of these segments besides names. How to divide files into segments? I named files as "1_1", "1_2" etc, but error is the same.
Where can i find more information or maybe another example, cause example from help don't work.
I understand that this is error about the first segment (section) of the file "1".
But Wincc OA Help doesn't say anything about the formation of these segments besides names. How to divide files into segments? I named files as "1_1", "1_2" etc, but error is the same.
Where can i find more information or maybe another example, cause example from help don't work.
- alug
- Posts:42
- Joined: Mon Oct 18, 2010 11:00 am
Re: IEC 104 File Transfer
Hallo,
the IEC specification does not define how file sections are combined to a file. This is a local matter of the IEC client and the IEC server.
We choose to store each section in a separate file. Therefore the file names must be _.
So the file names 1_1 and 1_2 are correct. The content of the files does not matter.
Have you set the entry ftRootDir in your config file?
From the error message I see that this is set to "data".
Can you try an absolute path.
best regards
Andreas
the IEC specification does not define how file sections are combined to a file. This is a local matter of the IEC client and the IEC server.
We choose to store each section in a separate file. Therefore the file names must be _.
So the file names 1_1 and 1_2 are correct. The content of the files does not matter.
Have you set the entry ftRootDir in your config file?
From the error message I see that this is set to "data".
Can you try an absolute path.
best regards
Andreas
- ZEVs
- Posts:16
- Joined: Thu Dec 06, 2012 8:21 pm
Re: IEC 104 File Transfer
Hello, little more detailes
1.IEC104 server config
ftRootDir = "data"
ftOutSubDir = "iecOut"
IEC104 client config
ftRootDir = "data"
ftInSubDir = "iecIn"
2.File (filename is "1") contains text (sequence if numbers), file is devided on 2 segments ("1_1", "1_2"), each about 100 bytes.
3.Query form client.
for internal datapoint of IEC driver address is set: IECTARGET-122.0.1.0.0.1
command : 122 0.1 1 1
4. After server recieves 122 its log contains
WCCOAiec (2), 2018.10.24 11:21:03.835, SYS, SEVERE, 14/iecError, ?????? ??? ???????? ????? "data/iecOut/1_1".
WCCOAiec2:IecFileTrans::fileRequestStart 2018.10.24;11:21:03:834 "Type 122 COA 1 IOA 1 filename 1 secname 1 qualifier 1"
WCCOAiec2:IecFileTrans::procSelectFile 2018.10.24;11:21:03:836 send FileReady: "Type 120 COA 1 IOA 1 filename 1 secname 0 qualifier 128"
client Log :
WCCOAiec (2), 2018.10.24 11:21:03:836, SYS, SEVERE, 3/iecError, .... "Type 120 COA 1 IOA 1 filename 1 secname 0 qualifier 128" ... "WaitFileReady".
1.IEC104 server config
ftRootDir = "data"
ftOutSubDir = "iecOut"
IEC104 client config
ftRootDir = "data"
ftInSubDir = "iecIn"
2.File (filename is "1") contains text (sequence if numbers), file is devided on 2 segments ("1_1", "1_2"), each about 100 bytes.
3.Query form client.
for internal datapoint of IEC driver address is set: IECTARGET-122.0.1.0.0.1
command : 122 0.1 1 1
4. After server recieves 122 its log contains
WCCOAiec (2), 2018.10.24 11:21:03.835, SYS, SEVERE, 14/iecError, ?????? ??? ???????? ????? "data/iecOut/1_1".
WCCOAiec2:IecFileTrans::fileRequestStart 2018.10.24;11:21:03:834 "Type 122 COA 1 IOA 1 filename 1 secname 1 qualifier 1"
WCCOAiec2:IecFileTrans::procSelectFile 2018.10.24;11:21:03:836 send FileReady: "Type 120 COA 1 IOA 1 filename 1 secname 0 qualifier 128"
client Log :
WCCOAiec (2), 2018.10.24 11:21:03:836, SYS, SEVERE, 3/iecError, .... "Type 120 COA 1 IOA 1 filename 1 secname 0 qualifier 128" ... "WaitFileReady".
- alug
- Posts:42
- Joined: Mon Oct 18, 2010 11:00 am
Re: IEC 104 File Transfer
Hello,
the problem is that "ftRootDir" is no absolute path.
So either remove this entry, because the /data directory is the default in any case
or specify an absolute path
e.g.
ftRootDir = "d:/a/b/c"
best regards
Andreas
the problem is that "ftRootDir" is no absolute path.
So either remove this entry, because the /data directory is the default in any case
or specify an absolute path
e.g.
ftRootDir = "d:/a/b/c"
best regards
Andreas