[EMAIL PROTECTED] wrote:
Hi everybody,
I've some questions for you. I wish to process in Real Time (RT) a UDP packet that i receive in broadcast, by a wireless net, on two pc P1 & P2. The third pc (P3), that send this packet, is not in RT. i've installed on P1 & P2 RTAI 3.4 with RT-Net 0.9.4 (the other versions give me problems with the ridefinition of nanosecs). I've to install

The older the versions, the higher the risk to encounter bugs that have been fixed in the meantime. Or are you locked into RTAI 3.4?

rtnet only to use the rt-receive, but the driver that i use are the not rt driver, the normal driver, because P3 is not in rt and, i think, is not possible to implement the tdma policy. In your opinion i'm making same mistake or it is possible? I've tryed to compile the

I guess you want to use P1&2 for measuring purpose with precise timestamping. Sounds feasible.

rt_rt2500 driver, but:
1) in rtnet0.9.4 in /driver/experimental/rt2500 the .h file are missing, so i've copied it from 0.9.9, and it compile. 2) when i make the insmode of the driver (insmod rt_rt2x00core.ko insmod rt_rt2500pci.ko) i don't know how the device is called. if i make iwconfig, or ./rtiwconfig no such wireless devices is found. why?

What does the kernel report (dmesg)?

3) on the pc i've the wireless pci card, and the ethernet card. i've to plugout the ethernet card? or there are something to change into the /etc/config file, in order to declare that there are 2 card, but how i can say that i want use the wireless card?

ENOPARSE. What is 'pc' now? Is RTnet involved on this side?

Jan

Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
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

Reply via email to