Python and CoDeSys

2020-02-27T14:54:59.353000Z

That is what i was searching for. Endless THANKS

Python and CoDeSys

2020-02-27T14:54:58.739000Z

Originally created by: M.Schaber

Hi, aoj,

The Project itsself also has an export_native method, which allows to pass a list of objects to export, as well as an recursive parameter to include child objects.

Simply exporting the whole project could be done with a command like:

proj.export_native(proj.get_children(), "d:\testination.export", true)

Python and CoDeSys

2020-02-27T14:54:57.107000Z

Hi Markus,
thanks a lot for your help.
One more question
The following code is a part of my ExportScript:```

proj = projects.open(pfad)
device = proj.find('Device', recursive = False)[0]
device.export_native(destination=utils.temp(File), recursive = True)
print ("exporting finished")

```As you can see the script exports the object Device. What about if I have in my project 50 objects to export? Is it possible to export the whole project?

Thanks

Python and CoDeSys

2020-02-27T14:54:56.487000Z

Originally created by: M.Schaber

Hi, aoj,

aoj hat geschrieben:
What should I change to make fail-proof? And for the case if I dont know in which directory is saved, is it possible to run it without giving the directory in the method?

AFAICS, there's no perfect approach for this, as there can be several CoDeSys version installed in parallel, and the script cannot guess which one you wanted to start.

I know the following approaches which all are being used in the field:

Note that the directory containing a script is usually contained in the search path. Additionally, in most cases, a python script or module can detect its own directory using a construct like the following:

scriptdir = os.path.abspath(os.path.dirname(__file__))

You can use this to find the directory of the Export_New.py script if it is installed in the same directory (or relative path) to the first script.

HTH,
Markus

Python and CoDeSys

2020-02-27T14:54:55.876000Z

your methods of searching the CoDeSys.exe is not fail-proof: If several CoDeSys versions are installed in different directories in "C:\Program Files", your script will match the first CoDeSys.exe it can find, and this is not necessarily the one matching the profile you give.

What should I change to make fail-proof? And for the case if I dont know in which directory is saved, is it possible to run it without giving the directory in the method?

Python and CoDeSys

2020-02-27T14:54:54.184000Z

Originally created by: M.Schaber

Hi, AOJ,

The building of the command line is not related to the subprocess-module, it is just a normal string operation. You could do the following:

codesys = runProcess("CoDeSys.exe")
exportscript = PythonScript("Export.py")
commandline = '"%s" --Profile="CoDeSys V3.4 SP4 Patch 1" --runscript="%s"' % (codesys, exportscript)
subprocess.call(commandline)

The % operator for string formatting is documented in the python documentation: http://docs.python.org/library/stdtypes.html#string-formatting-operations

Another way would be to use string concatenation:

commandline = '"' + codesys + '" --Profile="CoDeSys V3.4 SP4 Patch 1" --runscript="' + exportscript + '"'

Btw, your methods of searching the CoDeSys.exe is not fail-proof: If several CoDeSys versions are installed in different directories in "C:\Program Files", your script will match the first CoDeSys.exe it can find, and this is not necessarily the one matching the profile you give.

HTH,
Markus

Python and CoDeSys

2020-02-27T14:54:53.540000Z

I have one more question Is it possible to run CoDeSys without giving the directory of CoDeSys.exe in my method?

Python and CoDeSys

2020-02-27T14:54:52.856000Z

Markus you are my hero
I didnt know how to build the CoDeSys command line using the subprocess-Modul. Now it is working. Thank you again and wish you a nice day.

AOJ

Python and CoDeSys

2020-02-27T14:54:51.219000Z

Originally created by: M.Schaber

Hi,

In your first post, you had the following code:

subprocess.call(r'"C:\Program Files (x86)\3S CoDeSys\CoDeSys\Common\CoDeSys.exe" --Profile="CoDeSys V3.4 SP4 Patch 1" --runscript="D:\-----Python32\Export_New.py"')

This code shows how the command line to start CoDeSys has to be built together. Then, you should build the CoDeSys command line using this pattern.

Why do you to call CoDeSys without arguments, and afterwards try to start the script outside of CoDeSys with os.system instead?

Try something like the following:

codesys = runProcess("CoDeSys.exe")
exportscript = PythonScript("Export.py")
subprocess.call('"%s" --Profile="CoDeSys V3.4 SP4 Patch 1" --runscript="%s"' % (codesys, exportscript))

HTH,
Markus

Python and CoDeSys

2020-02-27T14:54:50.642000Z

Hi M.Schaber,

I am trying to call the two functions with the following code:```

codesys = "CoDeSys.exe"
subprocess.call(runProcess(r"%s" % codesys))
exportscript = "Export.py"
os.system(PythonScript(exportscript))

```

The project doesnt get exported because the second script deosnt get run from inside of the CoDeSys environment. Is it now more clear?

Recent posts to Python and CoDeSys

Python and CoDeSys

Python and CoDeSys

Python and CoDeSys

Python and CoDeSys

Python and CoDeSys

Python and CoDeSys

Python and CoDeSys

Python and CoDeSys

Python and CoDeSys

Python and CoDeSys