Back from holidays, do here we go again ... I will give an abstract about what's going on here with Nadym and me and our problems here:
The problem is, that aren't able to establish a RTnet connection between two desktop PCs. When they act as a master, they send their synchronisation frames at the right time, down to a cycle length of 2 ms (and most probably less then that). When they act as a slave, the fail to sync, because the TDMA cycle number in which they ask for the reply calibration frame lies already in the past. As we're using an Intel Core 2 Duo and an AMD Athlon XP here, we're talking about completly differently harware (including mainboards). IMO we do not face any SMI problems, because as discussed in the xenomai list, latency tests are showing good results and running them as a master works flawless, no delayed or missing sync frames or sth similiar. So I'm asking for suggestions, hints, tricks ... or a roadmap how to track this weird error down. My idea is to get into RTnet sources and use kprintf(). Any better ideas? And suggestion were to start this? Anything I have to keep in mind when using this call? Thanks in advance Karl -- von Karl Reichert Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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
