sorry, reply and reply-all is to close together ;) On Mon, July 30, 2007 12:35, Jan Kiszka wrote: > Nadym Salem wrote: >> On Mon, July 30, 2007 11:14, Jan Kiszka wrote: >>> Nadym Salem wrote: >>>> On Mon, July 30, 2007 10:37, Jan Kiszka wrote: >>>>> Nadym Salem wrote: >>>>>> On Thu, July 26, 2007 14:05, Nadym Salem wrote: >>>>>>> On Thu, July 26, 2007 13:55, Jan Kiszka wrote: >>>>>>>> Nadym Salem schrieb: >>>>>>>>> Hi, >>>>>>>>> I have a master being connected to several clients using TDMA. I >>>>>>>>> have >>>>>>>>> the >>>>>>>>> need to include one of the clients on the same machine as the >>>>>>>>> master, >>>>>>>>> communicating via ethernet. >>>>>>>>> Thinking of the net as a logical ring, I see the problem of >>>>>>>>> having >>>>>>>>> to >>>>>>>>> interfaces on the master now. Do I get two rings in that case ? >>>>>>>>> And >>>>>>>>> if >>>>>>>>> so, >>>>>>>>> is there a way to avoid that, since my clients have to be >>>>>>>>> synchronous. >>>>>>>> I don't get your scenario yet. I assume it's still IP-less, using >>>>>>>> packet >>>>>>>> sockets, right? What is your precise problem with the rtloopback >>>>>>>> device >>>>>>>> for local delivery? >>>>>>> Right assumed, still the same scenario. Using the loopback device I >>>>>>> would >>>>>>> have two devices on the master. If I want to include one of the >>>>>>> slaves >>>>>>> on >>>>>>> the same machine as the master, how could I include the Slave into >>>>>>> the >>>>>>> same TDMA "ring" ? My idea would be, to create a new rtethx device >>>>>>> on >>>>>>> the >>>>>>> same network adapter. But I have no further idea how to solve that >>>>>>> situation. >>>>>>> If the scenario is still unclear, I could try to create a small >>>>>>> picture >>>>>>> ;) >>>>>> Bringing it up again. >>>>> Still no clue what your precise problem is, but here are some blind >>>>> comments: It doesn't matter regarding TDMA master/slave where the >>>>> application is running. You have the same TDMA API (via RTDM device >>>>> TDMA<n>) on all nodes, thus you can sync also locally on the master >>>>> clock. On the other hand RTmac/TDMA will not work over loopback, thus >>>>> you don't get anything like "two rings". >>>> The only thing I want is a master and a slave on the same machine, >>>> with >>>> additional slaves over ethernet. But I have no idea how to configure >>>> that. >>>> >>>> If I configure a master over rteth0 and want to configure a slave now >>>> the >>>> resource is busy. But I think I have to configure a slave anyhow, >>>> don't >>>> I >>>> ? >>> Don't confuse TDMA master/slave with your application's master and >>> slaves! You don't need to configure RTmac/TDMA in any special way if >>> you >>> put some application on the master node that behaves like a slave to >>> some other application on that node. In any case, you can't configure a >>> node to be TDMA master AND slave at the same time. >> >> Ok, I guess what I want is not possible then. I did differentiate the >> application's and the TDMA master and slave. >> >>> So, just set up a normal TDMA network consisting of physically separate >>> master and slave nodes and then distribute your application over that >>> nodes however you want. If things still remain unclear, try to sketch >>> your application program here or even post essential code. >> >> Ok, there is a jpg attached to that mail. >> Two scenarios, the lower one is clear. Two machines, two applications, >> one >> is TDMA master and one TDMA slave. >> The upper scenario is the same, but running the two applications on the >> same machine. I want both scenarios possible without changing anything >> on >> the application. >> >> So Application 1 has to send data to application two via rtnet (raw >> acces) >> on the same machine and other way round. > > As you want to connect two applications locally, there is no Ethernet > involved, of course. Only rt_loopback. And as you are using the _raw_ > access, you have to do _raw_ addressing as well, which includes to > specify the outgoing device. In the local case, this is no longer some > rtethX, but rtlo. Thus, some awareness is required in your application, > but that is likely already needed for the addressing via MAC, isn't it?
That's what I originally intented to do. Changing the addressing and the interfaces inside my applications is not a problem, just parameters. But then my communication between App1 (tdma master) and App2 over rtlo is separated from the communication from app1 (tdma master) and the other slaves on rteth0. That would either mean that the other nodes couldn't communicate with App2 or that App2 would "steal" app1 its timeslot. That's what I meant by "two rings" ;) Greets, Nadym ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
