<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">ah okay,<br>
but btw.<br>
you mentioned that the tasks are not within the same deployment.<br>
the only Linux in responsible (if they are periodic) for the
execution.<br>
Try to start everything with run scripts (including logger) and
with the same-policy. You will get the same behavior like in
syskit's start up.<br>
<br>
So solve the issue try to use the solution Alex mentioned, if the
camera would take too long to acquire the images.<br>
BUT i assume still you have a too high load on your system. Maybe
you have some high-speed sensors and sensor fusion components NOT
within the same deployment which leads into your problems.<br>
<br>
Maybe there are ways to influence the system behavior, but for
this you need to identify the components that took your power.<br>
You could use the task-scheduler, i added a new option for this to
debug execution times of tasks. <br>
<br>
Summarize:<br>
- make sure all high-speed sensor data within one deployment<br>
- separate processing components from this base chain<br>
- increase priority for important tasks<br>
- take a look on the system LOAD (not only the most-consuming
component)<br>
- debug components with the scheduler (or any way you prefer)<br>
- Make sure no TCP connection is active (Use MQueues instead of
corba, don't use the Task-inspector while debugging)<br>
<br>
Matthias<br>
<br>
On 17.12.2013 11:14, Elmar Berghöfer wrote:<br>
</div>
<blockquote cite="mid:52B023F0.5010807@dfki.de" type="cite">Hi,
<br>
<br>
Am 17.12.2013 11:08, schrieb Matthias Goldhoorn:
<br>
<blockquote type="cite">On 17.12.2013 11:07, Elmar Berghöfer
wrote:
<br>
<blockquote type="cite">No it just was a replacement of the
on-board robot PC by the laptop to make clear that it has
nothing to do with performance of the on-board pc.
<br>
</blockquote>
Who does the serial interface to the robot in this case. I
assume
<br>
<br>
- Laptop -> camera started
<br>
- Onboard-PC Serial interface for seekuhr
<br>
</blockquote>
no - Laptop -> connected to Robot controller (via usb-serial
converter).
<br>
<br>
Onboard PC not used in this scenario.
<br>
<br>
Test should just figure out if the "quite" low performance of the
on-board pc (even if theoretically should already be enough) is an
issue or not.
<br>
The Lapptop System has much more performance than the on-board pc.
<br>
<br>
Regards
<br>
Elmar
<br>
<br>
<blockquote type="cite">
<br>
Right, and there you got the same scheduling problems?
<br>
<br>
Matthias
<br>
<br>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Rock-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Rock-dev@dfki.de">Rock-dev@dfki.de</a>
<a class="moz-txt-link-freetext" href="http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev">http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Dipl.-Inf. Matthias Goldhoorn
Space and Underwater Robotic
Universität Bremen
FB 3 - Mathematik und Informatik
AG Robotik
Robert-Hooke-Straße 1
28359 Bremen, Germany
Zentrale: +49 421 178 45-6611
Besuchsadresse der Nebengeschäftstelle:
Robert-Hooke-Straße 5
28359 Bremen, Germany
Tel.: +49 421 178 45-4193
Empfang: +49 421 178 45-6600
Fax: +49 421 178 45-4150
E-Mail: <a class="moz-txt-link-abbreviated" href="mailto:matthias.goldhoorn@informatik.uni-bremen.de">matthias.goldhoorn@informatik.uni-bremen.de</a>
Weitere Informationen: <a class="moz-txt-link-freetext" href="http://www.informatik.uni-bremen.de/robotik">http://www.informatik.uni-bremen.de/robotik</a></pre>
</body>
</html>