|
|
| Re: Forte Runtime for a PLC [message #1790186 is a reply to message #1790179] |
Wed, 06 June 2018 15:59   |
|
Hi,
maybe to add one thing to martins comment: In order to make a PLC programmable from 4diac-ide we need to port the 4diac run-time environment FORTE to the PLCs. This requires that a C++ compiler is available for the PLC (nowadays normally a dedicated gcc version) and that we can somehow upload and run this ported FORTE executable on the PLC. This is possible with many modern PLCs and we are happy to support you and if possible add it to our list of supported PLCs.
Cheers,
Alois
|
|
|
|
| Re: Forte Runtime for a PLC [message #1790317 is a reply to message #1790300] |
Fri, 08 June 2018 10:28 |
|
Hi Kenneth,
wow this is quite a list of questions. I'll try my best to answer them.
First of all I think it is important to point out that 4diac is an IEC 61499 implementation. IEC 61499 builds on top of IEC 61131-3 (i.e., the standard defining classical PLC programming languages). Although IEC 61499 builds on IEC 61131-3 it is not fully compatible. A good overview on both standards can be found on wikipedia [1, 2].
With that you can currently not take 4diac-ide to configure a PLC coming with its on run-time environment and set of FBs. Extending 4diac-ide for that would be quite an effort. Especially 4diac would need to know how to generate and download PLC configurations for your specific PLC.
The way 4diac took was to develop an own IEC 61499 run-time environment providing all the execution elements needed for executing IEC 61499 FBs. This execution environment assumes that there is a kind of operating or real-time operating system available on top of which the 4diac run-time environment, which we called FORTE, runs. To bring FORTE to a PLC as said above you need to compile FORTE for with a compiler dedicated for your hardware. Typically this means which processor the PLC has (e.g., arm, i386, SH, ...) and what operating system if any is available. Therefore for a specific PLC that means that you need some information on the internal structure of the PLC.
For example the Bosch PLC uses an intel chip with vxWorks. Therefore you need a gcc for intel and vxworks to compile a FORTE version for this PLC. The resulting binary is then loaded onto the PLC and executed there.
On the Wago PLC PFC 200 we have a Linux operating system with arm processor. Therefore the compiler is a gcc for arm and linux. We use the classical sftp to copy the FORTE binary there and can then execute it.
The IO access is also something very specific for the respective PLC and has to be implemented given the avaialbe means (e.g., Wago provides a library for accessing IO modules).
I hope this gives you a better idea on how the process works. Maybe a good starting point could be to make some experiments with 4diac on your PC or with a raspberrypi. I think this gives you a better idea on the capabilities and limitations of our environment.
If you can give us more information on the PLC maybe can even better support you. However I understand that you may don't want to disclose this in public. You can also send this to me in a private message if you like.
Cheers,
Alois
[1] https://en.wikipedia.org/wiki/IEC_61131-3
[2] https://en.wikipedia.org/wiki/IEC_61499
|
|
|
|
| Re: Forte Runtime for a PLC [message #1790485 is a reply to message #1790449] |
Mon, 11 June 2018 15:45 |
|
Hi Kenneth,
please have a look at the 4diac tutorials. Their you should find a detailed description on how to develop your own FBs with 4diac.
Regarding your make problem. The Mingw installer normally allows you to select also a make tool to install. Sometimes you have to add the path to mingw (e..,g C:\mingw64\bin) to the PATH environment variable.
|
|
|
|
| Re: Forte Runtime for a PLC [message #1790513 is a reply to message #1790503] |
Tue, 12 June 2018 08:42 |
|
Regarding building forte I think it would be great to see the output of the make command. Normally the forte.exe is in the not in the directory where you run make but in the src subdirectory of this location.
You can attache files to forum messages by not posting in the form that is per default below (i.e., with post quick reply) but by pressing the small reply button on the right. There you get a more elaborate form which allows attaching and embedding files.
If you do tests with precompiled fortes please use 1.8.4. the reason is that monitoring is enabled by default.
the output you are seeing is the how 4diac-ide is configuring the devices. In your example 31 commands are necessary to setup your blinking example in the device. Therefore also the numbers. however this output does not tell you anything about the running application. If you look at the last section of the tutorial's step 1 which is called Monitoring, you see an explanation of how you can watch your application executing in the application view.
I hope this helps.
cheers,
Alois
|
|
|
|
| Re: Forte Runtime for a PLC [message #1790546 is a reply to message #1790520] |
Tue, 12 June 2018 16:17 |
|
Hi,
AFAIK (I haven't used mingw for quite some time) after the build in the build output directory should be a directory called src and there you find forte.exe. however you need to not only call CMake (config7generrate) as this will only generate make files you need to call make in your build output directory to perform the build.
Regarding your questions. I think the problem is that you fist need to understand the PLCs in question. Even if you are targeting any PLC. Typically PLCs are configured by there respective tools and it is not documented how the tools are generated suitable configurations and/or code for the PLC.
So depending on the PLC type you would need to define some generation mechanism that takes the application in 4diac and generates the code for the respective PLC.
4diac itself offers quite some flexible mechanisms and extensions points to hook such generators into it. also the model is quite well defined in EMF. So this would be pretty easy.
The hard part is to find out what to generate. Just C/C++ will normally not be the solution. Also different PLCs may behave a little bit differently. So you need a very deep understanding on the operations of the specific PLC. Therefore for the same application you may need to generate different code.
So I think for starting taking one concrete PLC and learn would be good. Then later on the results may be generalized.
The above points where also the reason we wrote FORTE. We wanted a clear defined execution environment which will ensure the same behavior on all of our supported devices and sofar we got the best results by bringing FORTE to the different devices.
The intention of 4diac is that you can fully develop FBs and applications in 4diac and you don't need to do anything in C/C++. We even have now the experimental support for utilizing Lua as FB execution language. both C++ and Lua are hidden from the user who just works in 4diac. Only for bringing FORTE to devices C++ knowledge is required.
Cheers,
Alois
|
|
|
|
| Re: Forte Runtime for a PLC [message #1790605 is a reply to message #1790571] |
Wed, 13 June 2018 13:01 |
|
Hi,
getting some hands on experience with PLCs and 4diac will definitely help you in the task. Generating code for Siemens would be very interesting, but I think is also very challenging. What Siemens is calling SCL is based on the language Structured Text defined in IEC 61131-3. This language can also be used within 4diac FBs to define the algorithms of basic FBs. However please not it is not only about the FBs but also how they are connected and when they are executing (i.e., how events are delivered triggering FB execution).
Please note that our Lua approach has been implemented such that FORTE has been extended with a Lua engine. So only the contents of the FB are executed with Lua the rest (ie.., execution sequencing, scheduling, ... ) is handled by the standard FORTE.
EMF stands for Eclipse Modeling Framework which is commonly used in the Eclipse world for specifying models and operate on them.
The Node Mcu is a very interesting device. But I think maybe not the best start device as you may need quite some embedded knowledge to get FORTE running on it. Maybe a Raspi or something similar is a little bit easier to start.
Cheers,
Alois
Ps.: Regarding your monitoring: I think it would make sense to have this in a separate forum thread. If you get N/A it normally means that you have not a connection to your device (FORTE). Have you enabled monitoring? Or have you downloaded your application before monitoring?
|
|
|
|
| Re: Forte Runtime for a PLC [message #1790621 is a reply to message #1790613] |
Wed, 13 June 2018 16:01 |
|
Hi,
this time I really try to address all your points. Hopefully ;-)
Kenneth Carvalho wrote on Wed, 13 June 2018 14:55Hi Alois,
Thank you as always for all the information.
Alois : ...However please not it is not only about the FBs but also how they are connected and when they are executing (i.e., how events are delivered triggering FB execution).
If I understand right, I would need knowledge on how the FB's are connected in the Siemens model?.
Yes and how the execution model in the Siemens PLC is.
Kenneth Carvalho wrote on Wed, 13 June 2018 14:55
I had never heard of EMF...pardon my ignorance. So was EMF used to build the pallette and provide graphical representation and conversion
from Graphical to C++ code...
Yes EMF is the central element the 4diac-ide. The different XML files are parsed into EMF models the code generators, editors, views operate on the EMF models and the chagnes are then saved back to the XML files.
Kenneth Carvalho wrote on Wed, 13 June 2018 14:55
Also one question missed out is a statement from your earlier email connected to this context I presume...
"4diac itself offers quite some flexible mechanisms and extensions points to hook such generators into it...". Kindly elaborate based on the same context.
4diac utilize for that Eclipse extension points. I fear we don't have to much documentation on that. But for starting it is definitly good to have a look in the Eclipse platform documetnation on how to implement extension points and how to add menus. For example you can have a 3rd party plugin for 4diac which would add a pulldown menu item that is shown when you right click on a 4daic elemetn and you can have then code that is invoked independant from any 4daic code.
Kenneth Carvalho wrote on Wed, 13 June 2018 14:55
The LUA engine approach sounds great...so scripting engines can be extensions to FORTE, wow makes the RTE very powerful.
So can there be a scripting engine for Structured Text or SCL and include that with FORTE and make proprietary FBs execute?
Yes indeed it is. It is even more then that. If you have existing Structured text code you can add this to 4diac FBs and we automatically generate C++ or Lua code from that.
Kenneth Carvalho wrote on Wed, 13 June 2018 14:55
Please find attached with this email an RTF document showing screen shots
of my CMAKE and FORTE configurations. I am using mingw-64 the one which is suitable for both 32 and 64 bit systems. My system is windows 10 64 bit OS.
Although the configuration/generation steps go through successfully..when I try connecting this EXE file for running the BlinkTest tutorial app...the console just terminates without response but when I used the Forte RTE that came with 1.3.3 version ...that worked.
Kindly suggest any changes that i need to make to the configurations to get the right EXE file.
After you've run CMake you only get Makefiles as output. You still need to run make to generate FORTE exe. For this, as described in the docs, open a shell in your build output directory (in your case org.eclispe.fordiac.forte-1.9.1\new) and type make there. Then the compilation process should run and produce a forte.exe
Kenneth Carvalho wrote on Wed, 13 June 2018 14:55
P.S. Which forum should I post the monitoring question on...?
in this forum but in a seperate thread.
Kenneth Carvalho wrote on Wed, 13 June 2018 14:55
Quick question, I did not run Forte RTE while monitoring is it needed?
Monitroing is used to connect to a running application on a running FORTE (local or in a PLC). So in order to monitor something you need a running forte and you need to download your application to it first.
So I hope I've got everything now.
Cheers,
Alois
|
|
|
|
|
|
|
|
|
|
|
| Re: Forte Runtime for a PLC [message #1790800 is a reply to message #1790777] |
Mon, 18 June 2018 07:49 |
|
Hi Ken,
there are several Eclipse projects supporting you with such tasks. I don't know them by heart but if you google "Eclipse EMF Model to text transformation" then you should find some of them. I think we are using xtend/xpand for the lua generation. You can find this in the org.eclipse.fordiac.ide.export.forte_lua plugin of 4diac-ide.
Cheers,
Alois
|
|
|
| Re: Forte Runtime for a PLC [message #1790828 is a reply to message #1790800] |
Mon, 18 June 2018 16:04 |
 Kenneth Carvalho
Messages: 38
Registered: June 2018 |
Member |
|
|
Hi Alois,
I have followed the tutorial step by step for customizing a new
function block. Trying to figure out how to write an exporter for
Structured Text for this function block.
Kindly direct me on how I could go about writing this exporter which
would be seen as the third option of the exporter choices apart
from Forte and Lua.
I assume that this would be a plugin to be developed but how would
I connect the model of the new function block to the structured text
to be created.
Also how can I show this New Function Block as part of the Palette
so that it could be dragged into a new application.
Regards,
Ken
P.S. : Parallel task I am trying to get the Blink Test Application run on a Raspberry pi . Would any of the board models work or should I purchase
something specific.
[Updated on: Tue, 19 June 2018 11:32] Report message to a moderator |
|
|
| Re: Forte Runtime for a PLC [message #1790891 is a reply to message #1790828] |
Tue, 19 June 2018 20:19 |
|
Hi Ken,
I'm not sure if I understand what you would like today. In 4diac speak when we talk about an exporter we mean that we have an FB developed in 4diac (see the tutorials on FB development) and generate some code based on the FB.
In 4diac FBs are stored as XML files following the definitions of IEC 61499-2 Annex A. If you look into your project's folders you will see all these files. They have the file ending .fbt and you can open them with any text editor, or in 4diac with right-click open with -> text editor.
Regards,
Alois
P.S.: AFAIK any raspi should do it
|
|
|
| Re: Forte Runtime for a PLC [message #1790906 is a reply to message #1790891] |
Wed, 20 June 2018 05:10 |
Kenneth Carvalho
Messages: 38
Registered: June 2018 |
Member |
|
|
Hi Alois,
Thank you for that understanding. I am a bit confused since I am trying to
tackle two tasks,
1 is to customize a function block for a plc and
show it in the 4diac UI for selection and then have an export option that
converts the FB graphical interface into structured code.
2 Run a tutorial app like BlinkTest on a raspberry pi successfully.
In this email I am focussing on task 2..
I have 2 screen shots attached one shows that I have completed the
UI design as per the tutorial for BlinkTest for Sysfs(Raspi) .
Second shows that when I try to export I dont see the FBs that were created in the App, instead I see all the FB on the right.
So what do I select before clicking export
Where do I copy this generated code in Forte (Folder?).
If you have a link for this please share..
Thanks,
Ken
P.S: In the hours after writing this email ...I downloaded the raspberry pi toolchain on my laptop which runs windows 10 and I tried to create a Forte.exe without
any application code in it.
Although the final message in the make.exe says ...Built Target Forte...there
is a warning throughout the build and there is no Forte.exe within the src directory only there is a file named "forte" with no extension.
The screen shots for this are in Raspi-Forte-Build-Shots.doc
[Updated on: Wed, 20 June 2018 10:18] Report message to a moderator |
|
|
|
| Re: Forte Runtime for a PLC [message #1790972 is a reply to message #1790965] |
Wed, 20 June 2018 19:56 |
|
Hi Ken,
No in AnnexA of IEC 6499-2 a format for storing IEC 61499 defintions in XML is defined. This is used by 4diac for storing your FBs. If you have IEC 61131-3 FBs they are typically already in Structured Text. Why would you like to generate structured text code for them?
We currently have no way of reading any IEC 61131-3 FB representation nor an EMF model. If you would like to do something like this in addition to the exporter you would also need to extend our EMF model towards IEC 61131-3 fbs (or better restrict), which should be possible and write a loader that loads IEC 61131-3 FB files into this model. This can be done but I'm not sure if it is worth the effort. Maybe 4diac is then not the project you are looking for. Did you have a look on the Beremiz project.
For RASPI we are not generating C++ code for applications. Applications are dynamically generated in the deployment process by sending configuration commands to the device. You can see the configuration commands we are using in the deployment console.
What you need to compile is a FORTE with the set of FB types you would like it to contain and load the resulting binary onto the raspi and run it. As said above you can then download different applications to this FORTE instance as long as you are only using FB types you compiled into your FORTE.
Cheers,
Alois
P.S.: Please have a look on this forum thread https://www.eclipse.org/forums/index.php/t/1093628/. Maybe there you find already answers.
|
|
|
|
| Re: Forte Runtime for a PLC [message #1791034 is a reply to message #1790987] |
Thu, 21 June 2018 16:18 |
|
|
The process for Raspi is the same as for the local blinky tutorial. The differences are that instead of compiling FORTE for windows you need to crosscompile it. Instead of running on your pc the resulting forte.exe you need to put the forte executable on your raspi (e..g, sftp) and start it on your RASPI. Then in your system configuration you change the MGR_ID of your device to the IP address of your raspi and during download 4diac-ide will open a TCP connection to the running FORTE on your raspi and send the application configuration to it.
|
|
|
|
|
| Re: Forte Runtime for a PLC [message #1791159 is a reply to message #1791149] |
Mon, 25 June 2018 10:28 |
|
Hi,
i must confess I never used RASPI IOs myself.
Regarding your build issue. As i posted in the other post I mentioned above you need to run mvn clean install in the directory "plugins/org.eclipse.fordiac.ide.master"
|
|
|
|
|
|
| Re: Forte Runtime for a PLC [message #1791226 is a reply to message #1791225] |
Tue, 26 June 2018 10:24 |
|
Hi,
great that raspi is working for you. Any hint what was the cause of the problem.
Regarding the export problem. Please have a look at the different export plugins. These should give you an idea how how cpp code is generated for the FB and the Structured Text code inside of the FB.
Cheers,
Alois
|
|
|
|
|
| Re: Forte Runtime for a PLC [message #1791373 is a reply to message #1791359] |
Thu, 28 June 2018 12:27 |
|
Hi,
Very strange that the maven build is not working for you. We use that to generate the official 4diac releases.
Regarding your ide build times. You only need to run the maven build when you want to generate a full 4diac binary package. you can also directly run 4diac-ide from eclipse for testing. I do this all the time. I think it is described in the docs that you need to open the product file, press syncronize and launch. You only need to do this for the first time. This automatically creates a launch configuration and successive launches you can also perform from the run button (green play button) in the toolbar.
Cheers,
Alois
|
|
|
|
| Re: Forte Runtime for a PLC [message #1791436 is a reply to message #1791407] |
Fri, 29 June 2018 10:03 |
|
Hi,
I'm not very sure about the plugin thing. I think your plugin has to be referenced by a feature that is part of your product.
Regarding the template and tool lib issue. The problem is that when using a target platform, eclipse is downloading a dedicated eclipse environment for the build. This has the great advantage that you get a clean build and test environment. This helped us a lot to fix dependency issues. however then the place where your eclipse.exe is is not the right place for putting the templates and tool lib any more. The right place is the directory which is mentioned in the console output. It should be something like:
"your workspace path"/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool
We really need to update the the docs here.
Alois
|
|
|
| Re: Forte Runtime for a PLC [message #1791493 is a reply to message #1791436] |
Sat, 30 June 2018 17:40 |
Kenneth Carvalho
Messages: 38
Registered: June 2018 |
Member |
|
|
Hi Alois,
Thank you for that response, it really helped.
I was able to resolve the template and tool library issue by manually copying the folders within the path you specified.
Also your solution for integrating the plugin with a feature has also
worked.
Could you please guide me on the use of Xtext and Xpand in this project
since I am totally unaware of both these tools.
I read that XText is a tool for creating a domain specific language
and XPand is a code generator used by XText. Can you elaborate
in the context of 4Diac?
Also how was the design of this tool done in terms of what was the model based upon and how does it go from there, as in for a novice if one has to navigate through the source code to understand it in the
visualization of the design, what would be the path?
Regards,
Ken
[Updated on: Sun, 01 July 2018 14:32] Report message to a moderator |
|
|
|
| Re: Forte Runtime for a PLC [message #1791764 is a reply to message #1791589] |
Thu, 05 July 2018 06:21 |
Kenneth Carvalho
Messages: 38
Registered: June 2018 |
Member |
|
|
Hello Alois,
Actually as you know there is a package org....xtext.fbt which is containing
xtext xtend and mwe2 file.
If you could even briefly describe how these are being used it would
be very helpful to put the pieces together or maybe direct me to someone
who knows these technologies and their usage in this context that would be
nice.
Also in case you would like to email any links for docs or more detailed
information that could not fit in the blog, my email address is
kencarvo@gmail.com.
Regards,
Ken
[Updated on: Thu, 05 July 2018 06:23] Report message to a moderator |
|
|
| Re: Forte Runtime for a PLC [message #1791809 is a reply to message #1791764] |
Thu, 05 July 2018 13:59 |
|
Hi Ken,
sorry my last post was written a bit in a hurry. The problem is that all docs we have are public. Many different people have been working on the IDE code. Also I myself hat to learn the structure and the code the hard way by starting fixing minor bugs and reading the Eclipse Platform docs. Especially the latter was very helpful for me. For the graphical editors we are currently using GEF Legacy. There is a very good open IBM Redbook for getting started and understanding the concepts [1] and for more advanced topics I can recommend Vainolo's blog [2]. But i really hope that manage to migrate to the lates version of GEF. For new editors I would recommend to directly start with GEF 5.
XTend is also used in different places. The plugin you are mentioning is a support plugin for linking the interface variables of a FB to the ST model. This is used for the XText-based ST editors in 4diac-ide. I think for you it would be better to have a look at the export plugins, espeically the lua export plugin as the lua export is fully written in XTend.
I hope this helps.
Alois
[1] http://www.redbooks.ibm.com/abstracts/sg246302.html?Open
[2] https://www.vainolo.com/tutorials/gef-tutorials/
|
|
|
| Re: Forte Runtime for a PLC [message #1791844 is a reply to message #1791809] |
Fri, 06 July 2018 07:48 |
Kenneth Carvalho
Messages: 38
Registered: June 2018 |
Member |
|
|
Hi Alois,
Thank you for that awesome response. I was really wondering how do I go
about doing this. I was reading the basics of XText yesterday from that
site and this email of yours really helps. BTW where is this XText based
ST editor found in 4Diac??
If you have the IBM redbook link kindly share.
I will go through the LUA plugin in the meanwhile to understand
XTend.
I have no knowledge on GEF but would like to incorporate my own
FBD into 4Diac in IEC61131 mode.
Also in a different context, someone asked me on VXWorks in Rockwell
that is 4Diac setup to do that.
I read in a forum comment that Forte supports VXWorks but then I had
the question how do you build Forte source code to get the Forte.exe
for the Rockwell PLC. I know that it will be determined by the Platform
on which VXWorks runs whether its ARM or POWER or Intel but is
there a crosscompilers to build it on Windows 64 and what modules
are to be configured.
Thanks as always
Regards
Ken
[Updated on: Fri, 06 July 2018 07:50] Report message to a moderator |
|
|
| Re: Forte Runtime for a PLC [message #1791876 is a reply to message #1791844] |
Fri, 06 July 2018 12:15 |
|
Hi,
the Xtext editor is found when you are editing basic FB algorithms. It is explained in tutorial Step 4.
The IBM redbook can be downloaded via the link I provided.
In general FORTE has been ported to vxWorks. however to get this running on Rockwell PLC you need the toolchain and support from Rockwell.
Cheers,
Alois
|
|
|
| Re: Forte Runtime for a PLC [message #1791886 is a reply to message #1791876] |
Fri, 06 July 2018 13:55 |
Kenneth Carvalho
Messages: 38
Registered: June 2018 |
Member |
|
|
Hi Alois,
Sorry, I overlooked the links that you provided.
I went through the tutorial, yes in fact when i
was mailing this question I remembered this algorithm window
point but thought there is more to it for ST entry.
I had a question a few days ago that I had forgotten in this
context. When I have made a Custom FB, is it possible to get
the FB code in ST form like BEGIN END...VARS and ALGORITHM code?
----------------------------------------------------------------
When you say that Forte has been ported to VxWorks, my question is
for Raspi, when I compiled Forte the SYSFS module had to be enabled.
Are there any settings that I need to do in order to port the
Forte to VxWorks.
But actually I am confused.
My Final goal is to run a 4Diac designed app on a Rockwell PLC via
Forte.
Currently I dont have information on which PLC exactly, I will come
to know shortly and would share the same with you.
So if the Rockwell PLC is running on VxWorks, I would need to know
the platform architecture right?? like ARM or INTEL and then get
a gcc compiler accordingly.
I am ignorant about the toolchain and support needed from Rockwell,
is this freely available and on what basis do I search on Google for this
if it is?.
Regards,
Ken
|
|
|
| Re: Forte Runtime for a PLC [message #1791911 is a reply to message #1791886] |
Fri, 06 July 2018 18:57 |
|
hi,
I think I don't understand what you mean with that question:
Quote:I had a question a few days ago that I had forgotten in this
context. When I have made a Custom FB, is it possible to get
the FB code in ST form like BEGIN END...VARS and ALGORITHM code?
Could you please expand a bit.
vxWorks toolchains are as far as I know not freely available but you have to get them from the Windriver.
|
|
|
|
| Re: Forte Runtime for a PLC [message #1791927 is a reply to message #1791925] |
Sat, 07 July 2018 16:05 |
|
Hi Ken,
I really feal that we are running in circles here.
Yes you can get the ST code from the FBs. Maybe you just have a look on one of the FBT files and open them with a text editor. There you can see what is inside of a IEC 61499 FB. You will note that there is more then just the ST code.
vxWorks is used by several PLC vendors. FORTE has been tested on the PLCs using vxWorks from Bachmann Electronic and Bosch Rexroth. Both provide Toolchains for their devices that will allow you to compile and run C++ based programms on their PLCs.
Yes you had a toolchain. You need not only the C++ compiler but a full toolchain consisting also from linker, binary tools, debugger, system libraries.
Alois
|
|
|
|
| Re: Forte Runtime for a PLC [message #1791977 is a reply to message #1791962] |
Mon, 09 July 2018 09:41 |
|
Hi,
as stated in some of my previous posts here. We are using ST only as language for algorithms. Therefore you can see ST only in the XML part dedicated to algorithms. For the rest of the IEC 61499 model you have to define and write your own translation to ST if you need this.
So var I've always got the toolchains from the PLC vendors. Eiter as part of their programming environment or as additional package.
Cheers,
Alois
|
|
|
| Re: Forte Runtime for a PLC [message #1792090 is a reply to message #1791977] |
Wed, 11 July 2018 08:00 |
Kenneth Carvalho
Messages: 38
Registered: June 2018 |
Member |
|
|
Hi Alois,
Crystal clear on the ST part and realize code would have to be written to get a custom
interpretation.
I have noticed that most PLC vendors are giving IDE to program and
communicate with their PLC's.
So even if I get a toolchain would it be possible to load the compiled
Forte executable into the PLC without using the intended software.
Please throw some light in this area.
Regards,
Ken
[Updated on: Wed, 11 July 2018 08:01] Report message to a moderator |
|
|
|
|
| Re: Forte Runtime for a PLC [message #1792226 is a reply to message #1792168] |
Thu, 12 July 2018 19:57 |
|
|
Yes you need to know what you are doing. Applications in VXWorks are definitly different from a classical Windows or Linux. But if you have access to VXWorks you can load and start modules there.
|
|
|
|
| Re: Forte Runtime for a PLC [message #1792290 is a reply to message #1792289] |
Sat, 14 July 2018 14:58 |
|
|
For FORTE we providing you already with nearly everything you need. Building FORTE for vxWorks is similar to cross compiling for Raspi. The only difference is to choose a different toolchain and select vxworks instead of posix as architecture. The you get a vxWorks module. The only thing that you have to add for your specific HW is to implement the IO access.
|
|
|
| Re: Forte Runtime for a PLC [message #1792711 is a reply to message #1792290] |
Mon, 23 July 2018 05:29 |
Kenneth Carvalho
Messages: 38
Registered: June 2018 |
Member |
|
|
Ok, now I am getting the gist of Forte. So if I understand your answer correctly, it is not enough to just compile the Forte code to run on the respective OS. In order for Forte to get the inputs of the PLC
and write to the outputs of the PLC additional code will have to be written to access these pins which would be specific to that PLC. Hope my understanding is correct.
So this code was already present for the Raspberry PI in sysfs right? And in case I need to get Forte running on something like rockwell logic5000 or similar counterparts I would have to write a separate
IO module as part of the kernel to access its pins. Please confirm if this is the route to undertake.
..Also I am curious about the Raspi since I got an application working with the GPIO pins...I assume the Forte code is able to access the GPIO registers to access the input/output of the pins..If this is correct does'nt it need knowledge of the register addresses in the code....I just looked into the BCM2835 datasheet and it shows register information for GPIO..but dont know how this is used by Forte to access the pins..Please enlighten..
[Updated on: Mon, 23 July 2018 06:25] Report message to a moderator |
|
|
|
|
|
|
|
|
|
Search
Help
Register
Login
Home
