From: michel.dagenais@polymtl.ca (Michel Dagenais)
Subject: [lttng-dev] introduction & usage of LTTNG in machinekit
Date: Mon, 27 Apr 2015 22:00:54 -0400 (EDT) [thread overview]
Message-ID: <574727031.14339994.1430186454057.JavaMail.zimbra@polymtl.ca> (raw)
In-Reply-To: <1024078202.13732013.1430137815501.JavaMail.zimbra@polymtl.ca>
> That said, the folks which have timing problems have not caught on yet.. it
> looks some more guidance, examples and a bit of a machinekit-specific
> writeup is needed, competing with the other 247 priority projects on my desk
> ;)
Many people interested in MachineKit wonder about the control platform to select, from the most inexpensive (Raspberry PI) with more latency issues to the more expensive (Intel with FPGA card), with many interesting alternatives in between. The big question is always the real-time response for a typical challenging target such as 5 axis servo + spindle (3 phase variable frequency). We have the ability with LTTng to diagnose such real-time problems and thus to properly tune and then evaluate these different solutions. At the same time, it provides a challenging testbed for the LTTng toolchain. Your comments and suggestions on the hardware setup to test are most welcome!
Here is my current list of popular and interesting hardware that we would like to try out and properly assess this Summer:
- Raspberry PI 2, low end and most inexpensive.
- BeagleBone Black and eventually BeagleBoard X15, slightly more expensive but very interesting for control applications with PRUs, PWM and eQEP.
- Combined ARM and FPGA with Xilinx chips like Zedboards. The Adapteva Parallela board comes with a Xilinx Z-7010 or Z-7020. You get a dual-core A9, and FPGA for custom logic for encoder inputs and PWM or step generation.
- Intel board (Atom or better, suggestions for model welcome) with parallel port I/O or any of the available FPGA I/O cards.
Indeed, while some of the platforms may work without additional hardware (BeagleBone or Zedboard), an FPGA board provides a robust and high performance solution. I have a MesaNet 5I20 but the PCI bus is becoming legacy. Many newer models are offered using high speed data connections which are very convenient but not normally relied upon for real-time work (USB and Ethernet). However, given their high speed and with a dedicated link, it may be workable. Again an excellent testbed for the LTTng toolchain and some hardware measurements. We could test:
- Mesanet 6I24 FPGA PCIe card with 72 GPIO (baseline for low latency)
- Mesanet 7I80HD FPGA Ethernet with 72GPIO
- Mesanet 7I61 FPGA USB with 96 GPIO
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20150427/ea505542/attachment.html>
prev parent reply other threads:[~2015-04-28 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <887B7027-5FE6-4D13-B35A-7DCBD785DC57@mah.priv.at>
[not found] ` <711173584.2718642.1427481342189.JavaMail.zimbra@polymtl.ca>
[not found] ` <8187A8CE-F16D-4CDE-B969-380DE308A8D5@mah.priv.at>
[not found] ` <826926538.3126946.1427639461728.JavaMail.zimbra@polymtl.ca>
[not found] ` <76BAB974-2B32-469C-82AD-4D5630AFA28E@mah.priv.at>
2015-04-26 13:31 ` Michel Dagenais
2015-04-27 11:41 ` Michael Haberler
2015-04-27 12:30 ` Michel Dagenais
2015-04-27 20:41 ` Michael Haberler
2015-04-27 21:40 ` Michel Dagenais
2015-04-28 2:00 ` Michel Dagenais [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=574727031.14339994.1430186454057.JavaMail.zimbra@polymtl.ca \
--to=michel.dagenais@polymtl.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox