Posts: 39
Threads: 14
Joined: Mar 2017
Reputation:
1
If I understand integration with ETS correctly, the only way to export GAs from ETS and import into LM (or at least) spaceLYnk is via the OPC/ESF export format from ETS. This is an archaic export format from the stone age (ETS3) and one consequence is that the data point types are not imported into spaceLYnk. In a project with 500+ GAs, it becomes a very tedious task to manually correct the data point types wherever needed for visualization/scripting purposes.
Any plans to rather use the more modern XML format type from ETS, thereby being more aligned with the current year of 2018 and making our lives easier?
:-)
Thanks in advance
Posts: 39
Threads: 14
Joined: Mar 2017
Reputation:
1
Wow. Sounds absolutely marvellous. Do you know if it works with the spaceLYnk also? Could simply try, but do not want to risk jeopardizing my half-finished project.
Sent from my iPhone using Tapatalk
Posts: 1764
Threads: 6
Joined: Jul 2015
Reputation:
117
Hi,
Nope, SL has no json import option but you don’t need it in my opinion.
Just import the ESF and after import filter on object type and use mass edit to change them to the desired object type in one handling. On all projects this is a 20 second task so i don’t see the problem here..
BR,
Erwin
Posts: 1764
Threads: 6
Joined: Jul 2015
Reputation:
117
Hi,
I use (S), (D) , (V) etc as suffix in my ETS adresses so i don’t need to know the middle adresses, but in your case you could end up with # tat is correct.
I have a script to load the JSON from the FTP location and that result in same as using import button (:
Altough i never use it..
BR,
Erwin
Posts: 39
Threads: 14
Joined: Mar 2017
Reputation:
1
Would it be possible to ask for a copy of the script?
Thanks
Christian
Sent from my iPhone using Tapatalk