Great news that PhaROS got the 3rd price of the Innovation Technology Awards @ ESUG 2018.
Santiago Bragagnolo, Luc Fabresse, Pablo Estéfo, Sang Xuan Le and Noury Bouraqadi.
Congrats to all contributors!
Great news that PhaROS got the 3rd price of the Innovation Technology Awards @ ESUG 2018.
Santiago Bragagnolo, Luc Fabresse, Pablo Estéfo, Sang Xuan Le and Noury Bouraqadi.
Congrats to all contributors!
We have a PhaROS driver for the Robulab.
To install:
curl http://car.mines-douai.fr/scripts/Robulab | bash
roslaunch robulab bringup.launch
Enjoy PhaROS for Robulab development!
Some of our students work on this project. They used Pharo and ROS to make Nao write arbitrary words. Since the robot motion is not very precise, they made up a simple but smart solution to allow the robot can push the page after writing each letter.
PharoJS won the second prize at the ESUG 2015 Innovation Technology Awards.
We are glad to announce PharoJS, which is an infrastructure to run Pharo code on top of JavaScript. The goal of PharoJS is to allow developers benefit from the power of Pharo while targeting platforms that support JavaScript.
For example, PharoJS can be used to develop client side web applications. It can also be used to support cross-platform mobile apps based on Phone Gap.
PharoJS is freely available under MIT License. It can be dowloaded from SmalltalkHub.
A group of our students implemented this nice Writer Robot as part of a project where they learn programming using Phratch.
An example of a robotic guide at Ecole des Mines de Douai.
In this tutorial we will show you how to programs robot behaviour on using Live Robot Programming over PhaROS.
Create a ROS node that consumes /kompai2/pose
and /kompai/scan
and publish in /command_velocity
. To do this, just executing this:
LrpharosPackage uniqueInstance
Create an instance of the RobulabBridge
class
RobulabBridge uniqueInstance
RobulabBridge
and check that its instance variable laserData
is not nil and its values change over the time.Ok, so now we can start writing the behavior. First we will need some variables, those are: robulab
to manage the robot and some constants such as: f_vel
as linear velocity, t_vel
for angular velocity, and min_distance
as the minimum distance between the robot and an obstacle.
(var robulab := [RobulabBridgr uniqueInstance ])
(var min_distance := [0.5])
(var f_vel := [0.25])
(var t_vel := [0.5])
We define the state machine called Tito.
What we want to the robot is to go forward unless there is an obstacle in front of it so it should stop and turn to avoid it.
This could be modelled in a abstractly as two states: forward
and avoid
.
(machine Tito
;; States
(state forward
(onentry [robulab value forward: f_vel value])
)
(state stop
(onentry [robulab value stop])
)
;; Transitions
(on obstacle forward -> stop t-avoid)
(on noObstacle avoid -> forward t-forward)
;; Events
(event obstacle [robulab value isThereAnObstacle: min_distance value])
(event noObstacle [(robulab value isThereAnObstacle: min_distance value) not])
)
Finally, to run it, just start the machine on the forward
state.
(spawn Tito forward)
Let’s add an avoiding behavior. A simple one might be turning until it detects there is no obstacle and go forward again.
Then a simple behavior that match the avoidance requisite is:
RobotBridge
provides two methods to detect obstacles on the left and right part of the front of the robot: RobotBridge>>isThereARightObstacle:
and RobotBridge>>isThereALeftObstacle:
Then, the idea is to turn left if there is an obstacle in the front-right, or, turn right if there is an obstacle in the front-left.
Add the following states
(state turnLeft
(onentry [robulab value turn: t_vel value])
)
(state turnRight
(onentry [robulab value turn: t_vel value negated])
)
Add the corresponding transitions
(on rightObstacle stop -> turnLeft t-lturn)
(on leftObstacle stop -> turnRight t-rturn)
(on noObstacle turnLeft -> stop t-tlstop)
(on noObstacle turnRight -> stop t-trstop)
And add the events
(event rightObstacle [robulab value isThereARightObstacle: minDistance value])
(event leftObstacle [robulab value isThereALeftObstacle: minDistance value])
Updated version of LRP it is not necessary to add value
after a variable.
Then,
(onentry [robulab value turn: t_vel value negated])
is turned to
(onentry [robulab turn: t_vel negated])
making it more readable.
The objective of this tutorial is to be able to create a behaviour for the Robulab described using Live Robot Programming. The LRP program transparently uses PhaROS to communicate with the Robulab.
Open the image you created on the previous step and download the LRP code1
Gofer it
smalltalkhubUser: 'jfabry' project: 'LiveRobotProgramming';
configuration;
loadDevelopment
Download the code with the example by executing the following snippet on a workspace:
Gofer new smalltalkhubUser: 'mcamp'
project: 'RobotExperiments';
package: 'LrpharosPackage';
load.
Let’s check everything is ok before launching LRP UI:
roscore
is running.ProcessesCleaner clean
.Our example needs a PhaROS node subscribed to /kompai2/pose
and another node publishing on /command_velocity
, to do so you need to create a instance of LrpharosPackage
. Due to the live feature of LRP, it needs to have an unique instance of the package (which contains the nodes).
LrpharosPackage uniqueInstance
Open the LRP UI by right-clicking the World and selecting ** Live Robot Programming **. It will open a window like this:
Now, copy&paste the following script into the left pane (You can find it also in LrpharosPackage class>>lrpSimple
)
(var robulab := [LrpharosPackage uniqueInstance])
(var stop := [0])
(machine simple
(state forward
(onentry [robulab value forward: 0.1])
)
(state stop
(onentry [robulab value stop])
)
(state finish
(onentry [robulab value stop])
)
(on forceStop *-> finish t-finish)
(event forceStop [stop value = 1])
(ontime 2000 forward -> stop t-f)
(ontime 1000 stop -> forward t-s)
)
It should look something like this
Now we are almost close to launch the script. Before that you should be aware to have ways to stop it in an emergency case: have a remote joystick or just switch it off.
To trigger it add the following line at the end of the script:
(spawn simple forward)
Et voilà! The robot will start moving forward and then stop as the two steps.
An alternatively way to stop the robot using the LRP UI is by setting the stop
variable to 1 in the ** Variables: ** pane.
After stopping the robot, if you want to re-start it you have to click Reset Int. button in the bottom of the left pane.
LRP uses Roassal visualization engine for displaying the machines, states and transitions. After LRP is installed, you should run do a few simple steps in order to avoid a small-but-hard-to-solve bug related to fonts. You can fix it in less than 1 minute following the instructions here.
Each time you need to clean the proccesses through ProcessesCleaner clean
, the LRP process is terminated. Then you have to close the window after doing it.
Everytime you create a kompai node (through PureROS new scriptKompai1
or scriptKompai2
) you should then reset the LRP singleton by executing:
LrpharosPackage reset.
This way the LrpharosPackage instance will be bound to the correct kompai node.
Slides of my presentation given at ESUG 2014 conference are available online (see below). It’s about Robot software development using the Pharo dynamic language. It includes a quick overview of PhaROS our bridge to the ROS, as well as BoTest our framework for TDD for robotics applications. The video is also available on Youtube (see below) thanks to ESUG student volunteers. Note it is in two parts.