RTT 2.x

Sending digital message to SoemMaster

Hello everybody,

I've created the following program which connects to an etherCAT stack. The ports are connected to the SoemMaster component.

When I run this code, the analog output does send out an output voltage of 5 volt. However the digital out does not enable the first port.

Problem to connect Services

I try to figure out how to connect the service of one component to another component. Is there a way to do this with the deployer? I search in the documentation and I found nothing.

I try to make a test case with one ComponentA who requires service "display" and another ComponentB who provides the service "display". Click below to read the rest of this post.

Orocos - Ros

Hi,

Three weeks ago, I installed orocos-toolchain and went through the exercises for rtt2.x succesfully. Now I want to test the coupling between orocos and ros.

Ros cturtle is installed on my machine and I added the orocos_toolchain_ros stack using apt-get. After that, I removed the orocos-toolchain installation completely. Click below to read the rest of this post.

Orocos - Ros

Hi,

Three weeks ago, I installed orocos-toolchain and went through the exercises for rtt2.x succesfully. Now I want to test the coupling between orocos and ros.

Ros cturtle is installed on my machine and I added the orocos_toolchain_ros stack using apt-get. After that, I removed the orocos-toolchain installation completely. Click below to read the rest of this post.

[PATCH] New Services architecture.

Hello.

I would like to purpose a "new" Service Architecture.

The current patch (attached file) add a ServiceInterface base class that inherit the three interfaces (DataFlow, Configuration, and Operation). The Service and ServiceRequester inherit the ServiceInterface. Click below to read the rest of this post.

Configuring and Starting Components from an Orocos Script

Purpose

To start an Orocos application without writing a single XML file. Note: this syntax is only possible from RTT 2.2.0 on. pre-2.2.0 versions only support scripts in 'program' blocks.

You'll need to have the Scripting Chapter of the Component Builder's Manual at hand for clarifications on syntax and execution semantics.

How it works

We write one or more scripts that locate the components on the filesystem, create them in the application and connect and configure them. Click below to read the rest of this post.

OperationCaller send vector<double>

I'm trying to send operation to a remote TaskContext with a c++ application.

I use this code to send operation:

                try{
        TaskContext* taskContext = TaskContextProxy::Create("SpaceNav");
        OperationCaller<void(vector6)> func = taskContext->getOperation("setPosition");
        vector7 tmpvect(6,0);
        SendHandle<void(vector8)> handle = func.send(tmpvect);
        }
        catch(CORBA::Exception &e)
        {
            Logger::log() << Logger::Info << CORBA_EXCEPTION_INFO(e) << Logger::endl;
        }
When I use a operation with double as arguments, there is no problem, but when I... Click below to read the rest of this post.

Connecting ports of components distributed with CORBA

Purpose

Connecting an output port of one component with an input port of another component, where both components are distributed using the CORBA deployer application, deployer-corba.

How it works

Connecting data flow ports of components is done by defining connections (see Naming connections ). When components are distributed using the CORBA deployment component, you need to declare a proxy component in one of the deployers and connect to a port of that proxy. Click below to read the rest of this post.

Connect two ports with Deployer

Hello,

I have a ComponentA with a InputPort "manualCommandInput" and I have a ComponentB with the OutputPort "allSpaceNav".

I start the ComponentA with a deployer-corba. Click below to read the rest of this post.

NonPeriodic task, and operation with OwnThread option.

Hello.

I know it's a bad conception to try to add an OwnThread operation to a nonperiodic task, but i ran in this case by error.

So in the deployer :

 - while the task is running, the call of the operation never returns.
 - while the task is stopped, the call of the operation returns the good result.
 - while the task is in an fatal error case, it give me an unexpected exception.
I join a test case.

Would you tell me if it is what you expected ?

Thanks.

Paul.