Project

General

Profile

Feature #2912

Javaberry platform implementation

Added by Anonymous over 3 years ago. Updated 12 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
04/04/2017
Due date:
% Done:

100%

Estimated time:

JavaberryUserHelp.pdf (1.4 MB) JavaberryUserHelp.pdf Anonymous, 05/18/2018 11:36 AM

History

#1 Updated by Anonymous over 3 years ago

  • % Done changed from 0 to 80

#2 Updated by Anonymous almost 3 years ago

  • % Done changed from 80 to 90

The deployment code is now done manually. Must be generated automatically.

#3 Updated by Anonymous over 2 years ago

  • Target version changed from AF3 2.12 RC1 (Feature Freeze) to AF3 2.13 RC1 (Feature Freeze)

#4 Updated by Anonymous over 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

The Javaberry platform implementation is finished.

One can do modeling of an application on AF3 for the Javaberry platform and one can generate code in Java
which will run on Raspberry PI. The peripherals used in this deployment are buttons, leds, LCD 2x16.

It was modeled in AF3 an application called Vehicle Control, which uses 4 buttons: 2 for speed control -
forward and backward, and 2 for direction control - left and right. There are a LCD 2x16, to which are sent
the values of speed and direction and 4 leds. After generating the deployment code, one must copy all the folders
to a new Java project, to add source and library folders to the project (Path Build) and to build the project.
After that the code is ready to run on Raspberry PI.

When sending to display some values there is no standard possibility to add some accompanying text,
as for example "Speed =", and for that it was used the field "Comment". In Comment for the port "speed"
one can write "Speed" and it will send to display the message: "Speed = {value}".

For future development can be added other peripherals like serial ports and all the devices which work
with serial ports and other types of displays and any other devices. For that it is necessary to add some
new code in the Platform Configuration class. This is the same as to add new peripherals for any OS -
one need to add drivers and some service applications.

The deployment editor should be improved.

#5 Updated by Anonymous over 2 years ago

For the output ports, which send values to peripherals, one must give names which begins with "lcd" or "led" or "dac". For example "lcd_row1" or "lcd1", "lcd_row2" or "lcd2", "led1", "led2", "dac1", "dac2" and so on.

To the input ports can be given any meaningful names, such as "button_left", or "left", "right", "forward", "backward".

(A short user help should be added.)

#6 Updated by Anonymous over 2 years ago

  • Target version changed from AF3 2.13 RC1 (Feature Freeze) to AF3 2.14 RC1 (Feature Freeze)

#7 Updated by Anonymous over 2 years ago

Added the file JavaberryUserHelp.pdf

#8 Updated by Johannes Eder over 1 year ago

  • Target version changed from AF3 2.14 RC1 (Feature Freeze) to Backlog

#9 Updated by Johannes Eder about 1 year ago

  • Assignee changed from Anonymous to Johannes Eder

#10 Updated by Simon Barner 12 months ago

  • Status changed from Resolved to Rejected
  • Assignee deleted (Johannes Eder)

All results (including the documentation attached to this issue) can be found here: https://git.fortiss.org/af3/javaberry/tree/master/org.fortiss.af3.platform.javaberry

Also available in: Atom PDF