Tango on an embedded system

# 9 years ago
sblanch	I've suggested you the scpi because there is a device already made. Other options perhaps can be found in the Communications set of device servers in the repository.

# 9 years ago
alexandre	I'm ok to use it but I don't know how… Could you give some explanation? may be with a scheme or something like that.

# 9 years ago
raph38130	you definitely can't run any DeviceServer on mbed target (lack of resource : embedding Tango requires multithreading capabilities that mbed-rtos can not achieve, and in addition to linux OS, some "exotic libraries" (high efficiency sockets : zmq, omniorb4 middleware) are required ; BTW raspberry pi is ok to built an inexpensive and powerfull (pi2)tango server) so what you need is to build is a bridge between your mbed peripheral and a TangoDeviceServer host running linux (preferably) or windows (use visualstudio 2012, not 2013) links between the two can be RS232-COM, ethernet, (or even i2c, spi, … look for SeriaLine DeviceServer code source then from a remote machine(tango enabled), with Jive, you connect, using LAN, to your host (tango enabled, running your custom DeviceServer or SerialLine) which is itself connected to mbed by COM. see this example (arduino in place of mbed) your tango host (any linux machine 32/64 bits) can be a virtual machine (virtualbox or vmware) : easy to build on ubuntu (sudo apt-get install libtango8-dev and some other pacakges and your are done). We have even a vdi if you want. This is the way to go. keep on, You will learn a lot with Tango Edited 9 years ago

# 9 years ago

raph38130

you definitely can't run any DeviceServer on mbed target (lack of resource : embedding Tango requires multithreading capabilities that mbed-rtos can not achieve, and in addition to linux OS, some "exotic libraries" (high efficiency sockets : zmq, omniorb4 middleware) are required ; BTW raspberry pi is ok to built an inexpensive and powerfull (pi2)tango server)

so what you need is to build is a bridge between your mbed peripheral and a TangoDeviceServer host running linux (preferably) or windows (use visualstudio 2012, not 2013)

links between the two can be RS232-COM, ethernet, (or even i2c, spi, … smile

look for SeriaLine DeviceServer code source

then from a remote machine(tango enabled), with Jive, you connect, using LAN, to your host (tango enabled, running your custom DeviceServer or SerialLine) which is itself connected to mbed by COM.

see this example (arduino in place of mbed)

your tango host (any linux machine 32/64 bits) can be a virtual machine (virtualbox or vmware) : easy to build on ubuntu (sudo apt-get install libtango8-dev and some other pacakges and your are done). We have even a vdi if you want.

This is the way to go.
keep on, You will learn a lot with Tango

Edited 9 years ago

# 9 years ago
alexandre	Thank you raph38130! So if I resume: —————- ——————- ————- \| Remote machine \|——————–>\| Tango Device Host \|——-TCP/IP——->\| Mbed System \| \| (JIVE) \| \| —————— ————- —————- \| \| ——————- ————- —————–>\| Tango Device Host \|——-TCP/IP——->\| Mbed System \| \| —————— ————- \| ——————- ————- —————–>\| Tango Device Host \|——-TCP/IP——->\| Mbed System \| \| —————— ————- Is it like that? If true, it seems to be difficult to me because I have a lot of same embedded system. So I can't have a lot of Tango device Host. I'm reading your document now.

# 9 years ago

alexandre

# 9 years ago
alexandre	Oops sorry Remote machine -> Tango Device Host -TCP/IP—> Mbed System -> Tango Device Host -TCP/IP—> Mbed System -> Tango Device Host -TCP/IP—> Mbed System

# 9 years ago
raph38130	alexandre Thank you raph38130! So if I resume: —————- LAN ——————- \| Remote machine \|——————–>\| Tango DS Host with \| (JIVE) \| multiple instance —————- of the same DS ————- could even be on device server —————— \|——-TCP/IP——->\| Mbed System \| \| ————- \| \| ————- \|——-TCP/IP——->\| Mbed System \| \| ————- \| ————- \|——-TCP/IP——->\| Mbed System \| ————- you must understand that a DS is automatically instanced for each device. You do not need to create extra thread. Tango do it for you Is it like that? If true, it seems to be difficult to me because I have a lot of same embedded system. So I can't have a lot of Tango device Host. I'm reading your document now.

# 9 years ago

raph38130

alexandre
Thank you raph38130!

So if I resume:

—————- LAN ——————-
| Remote machine |——————–>| Tango DS Host with
| (JIVE) | multiple instance
—————- of the same DS ————-
could even be on device server —————— |——-TCP/IP——->| Mbed System |
| ————-
|
| ————-
|——-TCP/IP——->| Mbed System |
| ————-
| ————-
|——-TCP/IP——->| Mbed System |
————-

you must understand that a DS is automatically instanced for each device. You do not need to create extra thread. Tango do it for you

Is it like that?
If true, it seems to be difficult to me because I have a lot of same embedded system. So I can't have a lot of Tango device Host.

I'm reading your document now.

# 9 years ago
raph38130	sorry I can't post image … previous sketch should be resized (edit to see actual size) Edited 9 years ago

# 9 years ago
alexandre	yes me too I can't post image

# 9 years ago
raph38130	BTW where are you working/studying ?

# 9 years ago
alexandre	France/Le Mans Why?