Hello Martin, as promised I have run some test with the older version PCWorx Engineer I had still my first AXC F 2152 controller (first demo release) and could therefore run the test. As I remembered, the issue with the slow speed is not present here. But I could venture and say, that by adding the new functions and re-working the firmware in the newer releases, the software gremlins have presented them self. Can happen, but should have been noticed during testing. Any way: as long as you working on it and make the improvements we should be happy. But that there has not been set a timeline for fixing the issue for good, that is concerning me. As few other users have made clear, the remote access via a VPN connection is a must and should prioritized accordingly. Or we end up in the same situation as with the BF-D LED - talked about it for a year and still nothing has happened. Peter Paul
Thanks Peter for the update. Here is the current status (12.02.2020): Regarding the “hanging” and “freezing” issue, it is also planned that a fix for this issue will appear in PLCnext Engineer version 2020.3, but this will not be certain until much closer to the release date. There will be no further updates available from the developers on this topic until after version 2020.3 is released (latest end of April), so I will schedule the next update to this thread at around that time. ~ Martin.
Hi Martin, thanks for the info.we will wait for the new release. @alexsanchez please read the complete post for the issue. It will explain the problem and show you, that the developer is working on the issue. We all wait for a fix to the problem and hope that the new release will solve the issues at hand. But as it is with all software and even hardware, some defects cannot be detected in lab testing. That is where we as user have to step in and give feedback. In this instance, it has taken longer to respond to the issue by de developer or it has been lost in the cases we have reported. Looking in to my notes, I have reported the issue as far back as March 2019. But forthe moment I’m content with a fix in version 2020.3. We will than have to see how good the fix is and report back to the developer via the forum here. I will hope that Martin keeps the post open, so we can report the results and keep track on the progress until the issue has been resolved completely Peter Paul
Hi Martin Is it looking to be fixed in the next release ? Any news about that? - Emil
In light of the COVID 19 crisis, remote access to controls became even more critical! Martin, can you please update on this? Hopefully it is now the priority for PLCNext updates. Thanks and be all safe! Alex
The developers have now been asked for a statement on this topic. I will post it here as soon as I have something. ~ Martin.
Here is the latest from the Product Manager, as of this morning (19.03.2020):
the fix/improvement for the online connection over VPN is sceduled for version 2020.3
… and version 2020.3 is scheduled to be released before the end of April. ~ Martin.
before the end of April? That is still a long time and we still have systems to support. I know that you guys working on the fix but still it puts us in a difficult position. But, lets hope for the best. And all of you - stay safe! Peter Paul
Update (19.04.2020): PLCnext Engineer version 2020.3, and the release notes, are now available for download. Please check this version of PLCnext Engineer on your VPN networks, and feel free to share the results here. ~ Martin.
Hi Martin I have been testing through a IXON IX3 Router and a Secomea SiteManager VPN this morning, and i haven’t seen the problems with high CPU load, like before. So Thumps up for that.
However, I have experienced the program “frezzing” for about 10sek, after a download change, but it came back to normal after that. - Emil
Hi Martin, Finally I had a chance to test this. And yes, it is very good now, the CPU usage for PLCEngineer stays at 3% on my laptop and the connection is responsive. I was only monitoring, haven’t tested download or anything else, but will try those soon. Thank you, Alex
Hi, At the moment i’m working on a plant in USA, from Denmark. and the only thing there is fixed is the high CPU load. Transfer a complete program takes about 5-7min! (not very big program)
I have contacted Carsten Weber about it, and he is working on it.
I’m able to transfer the firmware for the PLC on 110mb in 1.2min so i have speed on the VPN connection.
PLCnext Engineer 2020.3.1. and FW 2020.3.1 (3x 2152 controllers) Times to compare: Local connected - Full Download takes 20sek.
Local PLC on Secomea VPN - Full Donwload 60-70sek (Latency: Avg: 48.4 ms),
USA on Secomea VPN - Full Download 5-7min at it’s best. (have seen it up to 15min! ) (Latency: Avg: 150.3 ms)
USA on Secomea VPN - Filetransfer WinSCP 110mb 1.2min - Emil
To close the loop, was the issue fixed with the 2020.3 release?
Hi, if you see my post from 3 weeks ago so both Yes and no. At shorter distances it’s working. I can do VPN to my office and the PLCs there, but at the moment i’m working at a project in Denver USA, and there it’s near impossible to get it to work. I have weekly mails with the support team, and they are working on it, but the only date i have seen yet is something like 2021 release… So depending on the distance, it’s working, but longer distance it becomes almost impossible. A download can often take 10-20min! When debug is running, it get stuck for 1-5 minutes, before wakening up again. - Emil
Hi all, We are aware of the ongoing performance issues of PLCnext Engineer over VPN, as described by Emil. Our PLCnext Engineer developers are working on a permanent solution, but we do not have a timeframe at this point. I will post more information here as I receive it. ~ Martin.
I have seen the same inside Denmark. When the distance is shorter then 250km it works. Is it longer, well - better drive to the client. Why is the distance a problem? Should this not be the same all the way? Peter Paul
Hi Peter Paul. This is being investigated, but my guess is that each “hop” between internet routers adds some latency until it reaches a point that causes problems for PLCnext Engineer. I also guess that traffic between more distant sites - especially between continents - is more likely to experience a larger number of hops. I am not involved in the investigation, but I will add updates here when I get them. ~ Martin.
Update (10.08.2020): ==================================== Current test results:
* We have reproduced an issue where the UI freezes while PLCnext Engineer is connected to a controller via VPN. This will be fixed in an upcoming PLCnext Engineer hotfix. * We have observed poor communication performance during data exchange between PLCnext Engineer and the controller. This needs further investigation.
Hi Martin, thanx for the update. I had the same idea about the “hops” but could not put my finger on the issue. Lets hope the hotfix is helping to address the issue as a first step. I can only hope that this issue will have been put to rest with the next major release - I’m right that this will be the 2021.LTS? For the moment it isn’t much fun to drive to the clients for 15 minutes of work. Especially if I have to drive for hours. Peter Paul
the next major release - I’m right that this will be the 2021.LTS?
Yes, the next release will be 2021.0 LTS later this year, but I do not know if this issue will be entirely resolved in that release.
For the moment it isn’t much fun to drive to the clients for 15 minutes of work.
I am sure you have considered this alternative as a temporary work-around, but just in case others haven’t: If you set up a Windows PC on the customer site, and if that PC is running PLCnext Engineer, then you can open a remote desktop session on that PC over VPN, and you will avoid this issue completely. ~ Martin.