Difference between revisions of "Beremiz"
From ArmadeusWiki
(→Target connection) |
|||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
== Introduction == | == Introduction == | ||
| − | Beremiz is | + | Beremiz is a Free Software toolkit for automation. It conforms with [http://en.wikipedia.org/wiki/IEC_61131 IEC61131] languages and can graphically drive your system. |
| − | + | ||
| − | + | ||
| − | + | Beremiz is divided in two software: | |
| − | + | ||
| − | + | * '''Beremiz.py''': the graphical toolkit that run on the Host to drive the target, | |
| + | * '''Beremiz_service.py''': the target runtime that execute the code compiled by Beremiz.py and sent to it through network. | ||
| − | * | + | There are two tricky things to do to use Beremiz on APF* platforms : |
| − | * | + | * configure Beremiz.py to cross-compile binary for ARM, |
| + | * run Beremiz_service.py on APF. | ||
== Installation == | == Installation == | ||
| Line 18: | Line 16: | ||
=== Host === | === Host === | ||
| − | Host part of | + | Host part of Beremiz is installable through Armadeus Buildroot menuconfig : |
<pre class="host"> | <pre class="host"> | ||
| − | make menuconfig | + | $ make menuconfig |
</pre> | </pre> | ||
| − | Then select : | + | Then select: |
<pre class="config"> | <pre class="config"> | ||
| − | + | Target packages ---> | |
Development tools ---> | Development tools ---> | ||
[*] matiec | [*] matiec | ||
... | ... | ||
Graphic libraries and applications (graphic/text) ---> | Graphic libraries and applications (graphic/text) ---> | ||
| − | [*] beremiz framework | + | [*] beremiz framework |
</pre> | </pre> | ||
| − | + | * Build/install it: | |
<pre class="host"> | <pre class="host"> | ||
| − | make | + | $ make |
</pre> | </pre> | ||
| − | + | * Then to launch it: | |
<pre class="host"> | <pre class="host"> | ||
| − | python buildroot/output | + | $ python buildroot/output/host/opt/beremiz/Beremiz.py |
</pre> | </pre> | ||
| − | |||
| − | |||
| − | |||
=== Target === | === Target === | ||
| + | Python 2.7 and Pyro are required to run Beremiz_service.py: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
<pre class="host"> | <pre class="host"> | ||
| − | make menuconfig | + | $ make menuconfig |
</pre> | </pre> | ||
| − | + | ||
<pre class="config"> | <pre class="config"> | ||
| − | + | Target packages ---> | |
| + | ... | ||
Interpreter languages and scripting ---> | Interpreter languages and scripting ---> | ||
| + | ... | ||
[*] python | [*] python | ||
| − | + | external python modules ---> | |
| − | + | ... | |
| + | [*] python-pyro | ||
</pre> | </pre> | ||
| − | then | + | * then: |
<pre class="host"> | <pre class="host"> | ||
$ make | $ make | ||
</pre> | </pre> | ||
| − | ===== Install | + | ===== Install Beremiz_service.py ===== |
| − | + | ||
<pre class="host"> | <pre class="host"> | ||
| − | make menuconfig | + | $ make menuconfig |
</pre> | </pre> | ||
<pre class="config"> | <pre class="config"> | ||
| − | + | Target packages ---> | |
| − | + | ... | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Graphic libraries and applications (graphic/text) ---> | Graphic libraries and applications (graphic/text) ---> | ||
| + | ... | ||
[*] Beremiz runtime | [*] Beremiz runtime | ||
</pre> | </pre> | ||
| Line 98: | Line 83: | ||
* When Beremiz.py is launched on your Host, create or open a project then save it. | * When Beremiz.py is launched on your Host, create or open a project then save it. | ||
| − | * in project | + | * in project "Config" tab set the correct "URI_location": |
| − | URI_location | + | URI_location: PYRO://192.168.0.33:3000 |
Replace 192.168.0.33 by the IP of your APF28. | Replace 192.168.0.33 by the IP of your APF28. | ||
| Line 109: | Line 94: | ||
for linker and compiler. | for linker and compiler. | ||
| − | * You can then compile and | + | * You can then compile and transfer the program to the APF... |
== Links == | == Links == | ||
| − | |||
* [http://www.beremiz.org/ Home page of project]. | * [http://www.beremiz.org/ Home page of project]. | ||
| + | |||
| + | [[Category:Automation]] | ||
Latest revision as of 16:11, 31 July 2014
Contents
Introduction
Beremiz is a Free Software toolkit for automation. It conforms with IEC61131 languages and can graphically drive your system.
Beremiz is divided in two software:
- Beremiz.py: the graphical toolkit that run on the Host to drive the target,
- Beremiz_service.py: the target runtime that execute the code compiled by Beremiz.py and sent to it through network.
There are two tricky things to do to use Beremiz on APF* platforms :
- configure Beremiz.py to cross-compile binary for ARM,
- run Beremiz_service.py on APF.
Installation
Host
Host part of Beremiz is installable through Armadeus Buildroot menuconfig :
$ make menuconfig
Then select:
Target packages --->
Development tools --->
[*] matiec
...
Graphic libraries and applications (graphic/text) --->
[*] beremiz framework
- Build/install it:
$ make
- Then to launch it:
$ python buildroot/output/host/opt/beremiz/Beremiz.py
Target
Python 2.7 and Pyro are required to run Beremiz_service.py:
$ make menuconfig
Target packages --->
...
Interpreter languages and scripting --->
...
[*] python
external python modules --->
...
[*] python-pyro
- then:
$ make
Install Beremiz_service.py
$ make menuconfig
Target packages --->
...
Graphic libraries and applications (graphic/text) --->
...
[*] Beremiz runtime
Simple usage
Target connection
- When Beremiz.py is launched on your Host, create or open a project then save it.
- in project "Config" tab set the correct "URI_location":
URI_location: PYRO://192.168.0.33:3000
Replace 192.168.0.33 by the IP of your APF28.
- then clic on «connect» icon.
- You can compile your project and try to send it...
- To configure your compiler, go to project configuration (double clic on head of hierarchy) and adding the path of your compiled armgcc :
YOUR_ARMADEUS_PATH/buildroot/output/host/usr/bin/arm-buildroot-linux-uclibcgnueabi-gcc
for linker and compiler.
- You can then compile and transfer the program to the APF...