Karl Reichert wrote: > Jan Kiszka wrote: >> Karl Reichert wrote: >>> Hello, >>> >>> I have two stations running RTnet, one as a master and one as a slave. I >> want >>> to measure the time, which a message, sent from master to slave, takes. >> But, >>> I don't want the time of the transmission only, but the complete time of >> all >>> software layers this data is processed through. >>> >>> _______________ _______________ >>> | A | | D | >>> |______________| |______________| >>> | B | | C | >>> |______________| |______________| >>> | RTnet (Master) | | RTnet (Slave) | >>> |______________| |______________| >>> | | >>> |______________| >>> >>> So, I create the data, that should be send, in Layer A (Master) and send >> it >>> over RTnet to Layer D (Slave). >>> >>> I want to take the time when the data leaves A and when it arrives D >> with >>> rtdm_clock_read(). If I have the offset between master and slave, I can >>> calculate the time it took to pass A, B, both RTnet stacks, C and D. >>> >>> As RTnet keeps track of the offset in it's stack, I want to use this >> value. Is >>> it possible via the API? I didn't found anything. Or do I have to >> manipulate >>> the stack to pass the offset to the higher layers (C and D)? >> If RTmac/TDMA is in use, you can obtain the clock offset via >> RTMAC_RTIOC_TIMEOFFSET from the RTDM device "TDMA<x>" (where "<x>" >> corresponds to "rteth<x>"). >> >> Jan >> > > Yes, it is. So I do: > > > > s64_t offset; > struct rtdm_dev_context context; > > tdma_dev_ioctl(&context, NULL, RTMAC_RTIOC_TIMEOFFSET, (void *) &offset); >
Wrong API (actually, this is no API function, its an internal handler). > > The question is, which values does context has to provide? Which elements of > this struct do I have to fill? All? It contains a lot of them. Or which ones > are important? Are you writing a kernel space application? Even if not, use rt_dev_ioctl() & friends for the native skin, and plain ioctl() for POSIX. But if you happen to write another RTDM driver, use rtdm_ioctl(). Arguments are all the same, those different names are just for the sake of consistent interfaces. Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
