EGX300 FTP problem

[sesa232858]

Hello,

Partner of us had a problem with couple EGX300s. They have written a program that connects to 40 EGX300s and pulls approx 400 CSV files from these alltogether. The EGX300s being wired parallel.

They say for couple CSVs they simply cannot download the file. (Error message they receive that the file doesn't exist or they have no access to it). Obviously they've checked and the file does exist.

They tried to delay the query thinking it might be the reason that the EGX300 writes the CSV file that momment they are trying to download it and also tried the access with different setups with always the same result.

They've got to the point where they could download ~350 CSV files out of the 400. For the EGXs for the rest 50 CSV files they started to decrease the data logged into those CSV files from 30 to 15 (so halved it) and that solved the problem with one EGX.

Now the problem is they still have 2 EGX300s where this problem stands. They would like to download alltogether 6 CSVs (so 3 per device) from which 2 they can download without a problem but the other 4 never works. They cannot descrease the number of CSVs anymore and the transfare rate really shouldn't be a problem.

They cannot download these said 4 CSV files through IE or FTP client either. He suggested as an idea that this problem feels like the EGX300 starts writing the CSV, adding new data to it but never finishes, thus the file always stay in temporary state or some sort.

Any experience, idea what could be the reason of this ? Should we just provide them 2 new EGX300s as it might have bad sector/fault in the memory ?

Thanks,

Daniel

[sesa82384_bridg]

In that case, why don't you use an FTP sever to receive all data from EGX and them process them?

Carlos Tangerino

carlos.tangerino@schneider-electric.com

+33 6 82 05 55 18

Sent from mobile device

[LaurentCoene]

Yes, is right. It would be easier to get the EGX to push the file so that you don't depend on the processes within the EGX. From what you are saying, the way you're working it seems too unreliable.

However, if you really do want to do a pull, in your code, you could check that the file downloaded properly and re-attempt until it works with a small delay between each attempt (and you probably should set a limit in the number of reattempt). Should work wonders! 🙂